Title page
1350 OMS | 9.6 1350 OMS PKT Guide 8DG42227DAAA Issue 3 | December 2012
Legal notice Legal notice
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein. Copyright © 2012 Alcatel-Lucent. All rights reserved. Notice
Every effort was made to ensure that the information in this document was complete and accurate at the time of printing. However, information is subject to change. Warranty
Alcatel-Lucent provides a limited warranty for this product. For more information, consult your local Alcatel-Lucent customer support team. Ordering information
The ordering number for this document is 8DG42227DAAA. To order 1350 OMS information products, contact your local Alcatel-Lucent customer support team. Technical support
For technical support, contact your local customer support team. You can reach them through the Web at the Alcatel-Lucent Customer Support web site (http://www. alcatel-lucent.com/support) or the customer support telephone number listed at the Alcatel-Lucent Contact Us web site (http://www.alcatellucent.com/contact). Information product support
For questions or concerns about this or any other Alcatel-Lucent information product, please contact us at one of the following numbers: (888) 727-3615 (for the continental United States), +1 (630) 713-5000 (for all countries).
Contents
About this document Purpose
......................................................................................................................................................................................... lxix lxix
Reason for reissue ..................................................................................................................................................................... lxix lxix Safety information
.................................................................................................................................................................... lxix lxix
Intended audience
...................................................................................................................................................................... lxx lxx
How to use this information product ................................................................................................................................... lxx Related documentation ......................................................................................................................................................... lxxiii lxxiii Ordering information How to comment
............................................................................................................................................................ lxxiii lxxiii
.................................................................................................................................................................... lxxiv lxxiv
Part I: Introduction 1
Product Overview Overview ...................................................................................................................................................................................... 1-1 1-1 1350 OMS Overview ............................................................................................................................................................... 1-2 1-2 1350 OMS Modules for System Resiliency and Northbound Communication ................................................. 1-5 1-5
2
Introduction to Administration Application Administration ................................................................................................................................................... 2-1 2-1 View Application Release Information ............................................................................................................................. 2-4 2-4
Part II: Administration 3
1350 OMS PKT Configuration Overview ...................................................................................................................................................................................... 3-1 3-1 1350 OMS PKT Configuration ............................................................................................................................................ 3-2 3-2 Access the System Configuration Window and Configure 1350 OMS PKT
..................................................... 3-3 3-3
.................................................................................................................................................................................................................................... 1350 OMS iii 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Integrate the 1350 OMS PKT with Other NMSs
.......................................................................................................... 3-8 3-8
Integrate 1350 OMS PKT Client Workstations with the Master Workstation .................................................... 3-9 3-9 4
1350 OMS PKT Process Monitoring Overview ...................................................................................................................................................................................... 4-1 4-1 Process Monitoring Overview .............................................................................................................................................. 4-2 4-2 Run Levels ................................................................................................................................................................................... 4-5 4-5
5
1350 OMS PKT User Management Overview ...................................................................................................................................................................................... 5-1 5-1 User Profiles
............................................................................................................................................................................... 5-2 5-2
Construction Macro Functions and Default User Profiles ......................................................................................... 5-3 5-3 MPLS Macro Functions and Default User Profiles ...................................................................................................... 5-7 5-7 Ethernet Macro Functions and Default User Profiles .................................................................................................. 5-9 5-9 6
1350 OMS PKT System Log Management Overview ...................................................................................................................................................................................... 6-1 6-1 SMF/Commands/Event Log File Overview
................................................................................................................... 6-2 6-2
Failure Management Log File Overview ......................................................................................................................... 6-5 6-5 Trace Management Overview 7
.............................................................................................................................................. 6-6 6-6
1350 OMS PKT Parameters Overview ...................................................................................................................................................................................... 7-1 7-1 Parameter Overview
................................................................................................................................................................ 7-2 7-2
1350 OMS PKT Parameters for Core NMA ................................................................................................................... 7-3 7-3 1350 OMS PKT Parameters for GUI NMA .................................................................................................................... 7-4 7-4 1350 OMS PKT Parameters for MW-INT ....................................................................................................................... 7-5 7-5 1350 OMS PKT Parameters for Oracle Management ................................................................................................. 7-6 7-6 Set PKT Parameters
................................................................................................................................................................. 7-7 7-7
1350 OMS PKT Parameter List ........................................................................................................................................... 7-9 7-9 8
1350 OMS PKT Ethernet Multi-Manager Management Configurations Overview ...................................................................................................................................................................................... 8-1 8-1
.................................................................................................................................................................................................................................... 1350 OMS iv 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Multi-Manager Management Overview ........................................................................................................................... 8-2 8-2 Operational Guidelines 9
........................................................................................................................................................... 8-3 8-3
1350 OMS PKT MIB Realignment and the ISA Board Overview ...................................................................................................................................................................................... 9-1 9-1 MIB Alignment and ISA Board Overview
...................................................................................................................... 9-2 9-2
Realign an ISA Board MIB ................................................................................................................................................... 9-4 9-4 10
1350 OMS PKT AlignDBSDHPathID Tool Overview
................................................................................................................................................................................... 10-1 10-1
AlignDBSDHPathID Overview ........................................................................................................................................ 10-2 10-2 Run AlignDBSDHPathID Tool
......................................................................................................................................... 10-3 10-3
Part III: Basic Functions 11
Generalities Overview
................................................................................................................................................................................... 11-1 11-1
About 1350 OMS PKT application Main features ............................................................................................................................................................................ 11-3 11-3 Management Layers
.............................................................................................................................................................. 11-5 11-5
Main concepts .......................................................................................................................................................................... 11-6 11-6 Network architecture overview
......................................................................................................................................... 11-7 11-7
Ethernet Services Attributes ............................................................................................................................................. 11-12 11-12 Classification of Ethernet Services ................................................................................................................................ 11-15 11-15 Definition of Ethernet Services by MEF ..................................................................................................................... 11-27 11-27 Network Topology Description ....................................................................................................................................... 11-30 11-30 How to access the application Web access .............................................................................................................................................................................. 11-38 11-38 The graphical interface (MS-GUI)
................................................................................................................................ 11-39 11-39
Confirm the action ............................................................................................................................................................... 11-40 11-40 The application interfaces Software interfaces .............................................................................................................................................................. 11-42 11-42 .................................................................................................................................................................................................................................... 1350 OMS v 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Multi-Manager environment ............................................................................................................................................ 11-44 11-44 Functional Domain Overview about functional domains Network Topology Construction
............................................................................................................................. 11-45 11-45
.................................................................................................................................... 11-47 11-47
Traffic Management ............................................................................................................................................................ 11-53 11-53 MPLS Management
............................................................................................................................................................ 11-65 11-65
Maintenance Management ................................................................................................................................................ 11-69 11-69 User Profile Management 12
................................................................................................................................................. 11-71 11-71
Managing your Network Overview
................................................................................................................................................................................... 12-1 12-1
Network configuration Create the network objects .................................................................................................................................................. 12-3 12-3 External Network Reference ............................................................................................................................................ 12-14 12-14 Create Physical Connection
............................................................................................................................................. 12-20 12-20
Create LAG ............................................................................................................................................................................ 12-24 12-24 Create Domain Create Domain
...................................................................................................................................................................... 12-27 12-27
Assign resource to Domain
.............................................................................................................................................. 12-31 12-31
Define NE ............................................................................................................................................................................... 12-35 12-35 Traffic categories Create Traffic Descriptor ................................................................................................................................................... 12-39 12-39 Create Traffic Classifier ..................................................................................................................................................... 12-43 12-43 L2 Encapsulation .................................................................................................................................................................. 12-46 12-46 NML-EML synchronization 1350 OMS PKT resynchronization ............................................................................................................................... 12-60 12-60 Alignment after deletion and recreation of SDH Path ............................................................................................ 12-61 12-61 VPWS Ethernet PM management procedure PM feature for the ISA ES1 1.0 board
......................................................................................................................... 12-62 12-62
.................................................................................................................................................................................................................................... 1350 OMS vi 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Provider network operating as a distributed MAC Bridge Single-Customer, No-VLAN, RSTP provisioning Provisioning procedure (MAC-SC-NV-RSTP)
................................................................................... 12-67 12-67
.................................................................................................. 12-69 12-69
........................................................................................................ 12-70 12-70
VLAN configuration scenario VLAN configuration ........................................................................................................................................................... 12-75 12-75 MAC Bridge Network Configuration MAC Bridge Basics ............................................................................................................................................................ 12-77 12-77 13
Network Organization Management Overview
................................................................................................................................................................................... 13-1 13-1
Managing Subnetworks Overview about Subnetworks ............................................................................................................................................ 13-5 13-5 View the list of subnetworks .............................................................................................................................................. 13-7 13-7 Create a Subnetwork
............................................................................................................................................................. 13-8 13-8
Modify a Subnetwork ......................................................................................................................................................... 13-10 13-10 Delete a Subnetwork ........................................................................................................................................................... 13-13 13-13 View the details of the subnetworks
............................................................................................................................. 13-14 13-14
Managing Domains Overview about Domains
................................................................................................................................................. 13-15 13-15
View the list of Domains ................................................................................................................................................... 13-17 13-17 Description of the list of Domains ................................................................................................................................. 13-18 13-18 Create a Domain ................................................................................................................................................................... 13-20 13-20 Modify a Domain ................................................................................................................................................................. 13-22 13-22 Delete a Domain ................................................................................................................................................................... 13-24 13-24 View the details of the domain ........................................................................................................................................ 13-25 13-25 Details of a Domain
............................................................................................................................................................ 13-26 13-26
Assign resources to a Domain ......................................................................................................................................... 13-27 13-27 Assign a NE to a Domain .................................................................................................................................................. 13-29 13-29 Deassign a NE from a Domain
....................................................................................................................................... 13-30 13-30
.................................................................................................................................................................................................................................... 1350 OMS vii 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
View the inventory of NE in a Domain
....................................................................................................................... 13-31 13-31
View the inventory of Transport Links in a Domain
.............................................................................................. 13-32 13-32
View the inventory of VT Queue Profiles in a Domain ......................................................................................... 13-33 13-33 Create Topological View in a Domain
......................................................................................................................... 13-34 13-34
Assign an Ethernet Physical Port to a Domain
......................................................................................................... 13-35 13-35
Deassign an Ethernet Physical Port from a Domain ............................................................................................... 13-36 13-36 Managing service nodes Overview about service nodes
........................................................................................................................................ 13-37 13-37
View the inventory of NE in a Service Node
............................................................................................................ 13-38 13-38
View the list of service nodes .......................................................................................................................................... 13-39 13-39 Managing Network Elements Overview about Network Elements
.............................................................................................................................. 13-40 13-40
View the list of Network Elements ................................................................................................................................ 13-42 13-42 Define a NE ............................................................................................................................................................................ 13-43 13-43 Add a NE to a Subnetwork ............................................................................................................................................... 13-46 13-46 Modify a NE
.......................................................................................................................................................................... 13-49 13-49
View the details of the NEs .............................................................................................................................................. 13-52 13-52 View the list of available Network Elements ............................................................................................................. 13-53 13-53 Upload the Ethernet physical ports Upload the TDM terminations
............................................................................................................................... 13-54 13-54
........................................................................................................................................ 13-57 13-57
Upload the Links Over TDM ........................................................................................................................................... 13-59 13-59 Audit the TDM terminations ............................................................................................................................................ 13-62 13-62 Synchronize the TDM terminations .............................................................................................................................. 13-64 13-64 View the list of TDM terminations ................................................................................................................................ 13-66 13-66 View the details of the TDM terminations .................................................................................................................. 13-67 13-67 Acknowledge the NE LAC state .................................................................................................................................... 13-68 13-68 Show the equipment view ................................................................................................................................................. 13-70 13-70 View the inventory of VT Queue Profiles in a NE .................................................................................................. 13-73 13-73 Upload the Links Over Cable .......................................................................................................................................... 13-74 13-74 .................................................................................................................................................................................................................................... 1350 OMS viii 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Upload the Radio Ports ...................................................................................................................................................... 13-75 13-75 Create VT Queue Profile ................................................................................................................................................... 13-76 13-76 Create Topological View from NE or ENE ................................................................................................................ 13-77 13-77 Managing External Network Elements Overview about External Network Elements
............................................................................................................ 13-78 13-78
View the list of External Network Elements .............................................................................................................. 13-80 13-80 Description of the list of ENE ......................................................................................................................................... 13-81 13-81 Create an ENE ....................................................................................................................................................................... 13-82 13-82 Modify an ENE ..................................................................................................................................................................... 13-85 13-85 Delete an ENE ....................................................................................................................................................................... 13-87 13-87 View the details of the ENEs ........................................................................................................................................... 13-88 13-88 Details of an ENE ................................................................................................................................................................ 13-89 13-89 View the list of ETPs .......................................................................................................................................................... 13-90 13-90 Description of the list of ETPs ........................................................................................................................................ 13-91 13-91 Create an ETP
....................................................................................................................................................................... 13-92 13-92
Delete an ETP
....................................................................................................................................................................... 13-94 13-94
Managing Ethernet Physical ports View the list of Ethernet Physical ports ....................................................................................................................... 13-96 13-96 Description of the list of Ethernet physical ports ..................................................................................................... 13-97 13-97 Configure an Ethernet physical port Modify an Ethernet Physical Port
............................................................................................................................. 13-99 13-99
.............................................................................................................................. 13-104 13-104
Assign a Port to Network Access Domain
............................................................................................................... 13-106 13-106
View the details of the Ethernet physical ports
...................................................................................................... 13-108 13-108
Details of an Ethernet Physical Port ........................................................................................................................... 13-109 13-109 View the list of Equipment ports .................................................................................................................................. 13-111 13-111 Description of the list of Equipment ports
............................................................................................................... 13-112 13-112
Managing Link Aggregation (LAG) ports Description of Link Aggregation (LAG) function ................................................................................................. 13-113 13-113 View the list of LAG ports ............................................................................................................................................. 13-116 13-116 .................................................................................................................................................................................................................................... 1350 OMS ix 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Description of the list of LAG ports ........................................................................................................................... 13-117 13-117 Create a LAG port ............................................................................................................................................................. 13-118 13-118 Modify a LAG port ........................................................................................................................................................... 13-120 13-120 Assign LAG port to Network Access Domain
....................................................................................................... 13-125 13-125
View the details of the LAG ports ............................................................................................................................... 13-126 13-126 Details of a LAG port
...................................................................................................................................................... 13-127 13-127
View the ports member of a LAG
............................................................................................................................... 13-128 13-128
Description of the list of LAG ports ........................................................................................................................... 13-129 13-129 Network Access Domain (NAD) Management View the list of NADs ...................................................................................................................................................... 13-130 13-130 Description of the list of NADs Create a NAD
................................................................................................................................... 13-131 13-131
..................................................................................................................................................................... 13-132 13-132
Modify a NAD .................................................................................................................................................................... 13-133 13-133 Delete a NAD
..................................................................................................................................................................... 13-134 13-134
Managing Jumbo Frames (through NAV) Overview about Jumbo Frames
.................................................................................................................................. 13-135 13-135
Workflow to configure Interfaces for Jumbo Traffic ............................................................................................ 13-137 13-137 Particular configuration procedures Managing ports on 1678MCC Network Elements ................................................................................................ 13-140 13-140 ISA BCE Ethernet Board ................................................................................................................................................ 13-146 13-146 14
Transport Link Management Overview
................................................................................................................................................................................... 14-1 14-1
Overview about Transport links Transport link definition
...................................................................................................................................................... 14-4 14-4
Transport link classification
............................................................................................................................................... 14-5 14-5
Concatenated VC management ....................................................................................................................................... 14-11 14-11 Setting parameters of Transport Links ......................................................................................................................... 14-12 14-12 Implicit configuration ......................................................................................................................................................... 14-14 14-14 .................................................................................................................................................................................................................................... 1350 OMS x 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Managing Links Over TDM Overview ................................................................................................................................................................................. 14-17 14-17 Introduction ............................................................................................................................................................................ 14-18 14-18 View the list of Links Over TDM .................................................................................................................................. 14-19 14-19 Create Link Over TDM
..................................................................................................................................................... 14-21 14-21
Delete a Link Over TDM .................................................................................................................................................. 14-24 14-24 Configure a Link Over TDM ........................................................................................................................................... 14-25 14-25 Get the Link Over TDM Extremities ............................................................................................................................ 14-27 14-27 Remove inconsistent TDM paths ................................................................................................................................... 14-29 14-29 Assign a Link Over TDM to a Domain
....................................................................................................................... 14-30 14-30
Deassign a Link Over TDM from a Domain Assign NAccess Domain
............................................................................................................. 14-31 14-31
.................................................................................................................................................. 14-32 14-32
View the details of the Links Over TDM .................................................................................................................... 14-34 14-34 Get the Fault Localization
................................................................................................................................................ 14-36 14-36
Managing Links Over Cable Overview about Link Over Cables ................................................................................................................................ 14-38 14-38 View the list of Links Over Cables ................................................................................................................................ 14-41 14-41 Create a Link Over Cable
................................................................................................................................................. 14-42 14-42
Modify a Link Over Cable Delete a Link Over Cable
............................................................................................................................................... 14-44 14-44
................................................................................................................................................. 14-46 14-46
Get the Link Over Cable extremities ............................................................................................................................ 14-48 14-48 View the details of the Link Over Cables
................................................................................................................... 14-50 14-50
Link Over Cable Split/Join ............................................................................................................................................... 14-52 14-52 Configure Split/Join ............................................................................................................................................................ 14-54 14-54 Configure a Link Over Cable
.......................................................................................................................................... 14-57 14-57
Assign NAD ........................................................................................................................................................................... 14-58 14-58 Get the Fault Localization
................................................................................................................................................ 14-59 14-59
Assign a Link Over Cable to a Domain ....................................................................................................................... 14-60 14-60 Deassign a Link Over Cable from a Domain ............................................................................................................. 14-61 14-61 .................................................................................................................................................................................................................................... 1350 OMS xi 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Managing LAG Links Over Cable View the list of LAG Links Over Cables .................................................................................................................... 14-62 14-62 Create a LAG Link Over Cable from extremities .................................................................................................... 14-63 14-63 Create a LAG Link Over Cable from Links ............................................................................................................... 14-66 14-66 Create a LAG Link VCG from extremities ................................................................................................................ 14-69 14-69 Create a LAG Link VCG from Links ........................................................................................................................... 14-72 14-72 Modify a LAG Link Over Cable .................................................................................................................................... 14-75 14-75 Delete a LAG Link Over Cable ...................................................................................................................................... 14-77 14-77 Get the LAG Link Over Cable extremities ................................................................................................................. 14-79 14-79 View the details of the LAG Link Over Cables ........................................................................................................ 14-80 14-80 Details of the list of LAG Link Over Cables ............................................................................................................. 14-81 14-81 Managing links over WDM Overview about links over WDM .................................................................................................................................. 14-82 14-82 View the list of links over WDM ................................................................................................................................... 14-83 14-83 Get the Link Over WDM extremities ........................................................................................................................... 14-84 14-84 Description of a Link Over WDM Extremities ......................................................................................................... 14-85 14-85 View the details of the links over WDM ..................................................................................................................... 14-86 14-86 Managing links over MPLS Overview about links over MPLS
................................................................................................................................. 14-88 14-88
View the list of links over MPLS ................................................................................................................................... 14-89 14-89 Get the Link Over MPLS extremities ........................................................................................................................... 14-90 14-90 View the details of the links over MPLS ..................................................................................................................... 14-91 14-91 Managing Link over Radio View the list of links over Radio .................................................................................................................................... 14-93 14-93 Managing links over T-MPLS Overview about links over T-MPLS
............................................................................................................................. 14-94 14-94
View the list of links over T-MPLS ............................................................................................................................... 14-95 14-95 Get the Link Over T-MPLS extremities ....................................................................................................................... 14-96 14-96 View the details of the links over T-MPLS
................................................................................................................ 14-97 14-97
.................................................................................................................................................................................................................................... 1350 OMS xii 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Managing MPLS/T-MPLS infrastructure Overview about MPLS/T-MPLS infrastructure ........................................................................................................ 14-99 14-99 View the list of T-MPLS sections ................................................................................................................................ 14-100 14-100 Get the T-MPLS section extremities ........................................................................................................................... 14-101 14-101 View the details of the links over T-MPLS .............................................................................................................. 14-102 14-102 Managing Transport Links by Domain View the list of Transport Links ................................................................................................................................... 14-104 14-104 15
MPLS Provisioning Management Overview
................................................................................................................................................................................... 15-1 15-1
Managing Traffic Descriptors (MPLS) ....................................................................................................................................................................................................... 15-4 15-4
Overview about Traffic Descriptors (MPLS) ............................................................................................................... 15-5 15-5 View the list of Traffic Descriptors (MPLS) ................................................................................................................ 15-6 15-6 Description of the list of Traffic Descriptors ................................................................................................................ 15-7 15-7 Create a Traffic Descriptor (MPLS) ................................................................................................................................ 15-8 15-8 Modify a Traffic Descriptor (MPLS) ............................................................................................................................ 15-12 15-12 Delete a Traffic Descriptor (MPLS) .............................................................................................................................. 15-15 15-15 View the details of the Traffic Descriptors (MPLS) ................................................................................................ 15-16 15-16 Details of a Traffic Descriptor ......................................................................................................................................... 15-17 15-17 Get the Traffic Descriptor inventory list (MPLS) .................................................................................................... 15-18 15-18 Description of the Traffic Descriptor inventory
....................................................................................................... 15-19 15-19
Managing Transport Links (MPLS) Overview ................................................................................................................................................................................. 15-20 15-20 Overview about Transport Links .................................................................................................................................... 15-21 15-21 View the list of Transport Links ..................................................................................................................................... 15-23 15-23 Define the Transport Link characteristics ................................................................................................................... 15-25 15-25 Get the Transport Link extremities ................................................................................................................................ 15-28 15-28 Description of the list of Transport Link Extremities ............................................................................................. 15-30 15-30 .................................................................................................................................................................................................................................... 1350 OMS xiii 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
View the details of the Transport Links ....................................................................................................................... 15-31 15-31 Details of a Transport Link ............................................................................................................................................... 15-32 15-32 View the bandwidth load of Transport Links View the inventory of Transport Links
........................................................................................................... 15-33 15-33
........................................................................................................................ 15-36 15-36
Description of the Transport Link Inventory ............................................................................................................. 15-38 15-38 Managing LSP Tunnels (MPLS) Overview ................................................................................................................................................................................. 15-39 15-39 Overview about LSP Tunnels .......................................................................................................................................... 15-40 15-40 View the list of LSP tunnels ............................................................................................................................................. 15-41 15-41 Description of the list of LSP Tunnels Create an LSP tunnel
.......................................................................................................................................................... 15-43 15-43
Modify an LSP tunnel Delete an LSP tunnel Allocate LSP tunnel
......................................................................................................................... 15-42 15-42
........................................................................................................................................................ 15-45 15-45
.......................................................................................................................................................... 15-47 15-47
............................................................................................................................................................ 15-48 15-48
Deallocate LSP tunnel ........................................................................................................................................................ 15-51 15-51 List the constraints of an LSP tunnel
........................................................................................................................... 15-53 15-53
Description of constraints of LSP tunnel Add a constraint to an LSP tunnel
.................................................................................................................... 15-55 15-55
................................................................................................................................. 15-56 15-56
Delete a constraint from an LSP tunnel ....................................................................................................................... 15-58 15-58 View the details of the LSP tunnel constraints .......................................................................................................... 15-60 15-60 Details of a LSP Tunnel Constraint ............................................................................................................................... 15-62 15-62 View the list of cross connections .................................................................................................................................. 15-63 15-63 Description of the list of LSP cross connections ...................................................................................................... 15-64 15-64 Implement an LSP tunnel .................................................................................................................................................. 15-65 15-65 Get the LSP tunnel extremities
....................................................................................................................................... 15-67 15-67
Description of the list of LSP Tunnel Extremities
.................................................................................................. 15-69 15-69
View the details of the LSP tunnels ............................................................................................................................... 15-70 15-70 Details of a LSP Tunnel ..................................................................................................................................................... 15-71 15-71 View the inventory of VC-LSPs ..................................................................................................................................... 15-72 15-72 .................................................................................................................................................................................................................................... 1350 OMS xiv 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Description of the LSP Tunnel Inventory
................................................................................................................... 15-73 15-73
View the bandwidth load of LSPs .................................................................................................................................. 15-74 15-74 View the route of LSP Tunnels
...................................................................................................................................... 15-77 15-77
View the list of the Transport Links related to an LSP Tunnel
........................................................................... 15-79 15-79
Description of the LSP Tunnel inventory .................................................................................................................... 15-80 15-80 Managing VC-LSP (MPLS) Overview ................................................................................................................................................................................. 15-81 15-81 Overview about VC-LSP
.................................................................................................................................................. 15-82 15-82
View the list of VC-LSPs .................................................................................................................................................. 15-83 15-83 Description of the list of VC-LSPs ................................................................................................................................ 15-84 15-84 Create a VC-LSP .................................................................................................................................................................. 15-85 15-85 Modify a VC-LSP ................................................................................................................................................................ 15-89 15-89 Delete a VC-LSP .................................................................................................................................................................. 15-91 15-91 Implement a VC-LSP
......................................................................................................................................................... 15-92 15-92
De-implement a VC-LSP .................................................................................................................................................. 15-94 15-94 Commission a VC-LSP ...................................................................................................................................................... 15-96 15-96 De-commission a VC-LSP
............................................................................................................................................... 15-98 15-98
Get the VC-LSP extremities ............................................................................................................................................. 15-99 15-99 Description of the list of VC-LSP Extremities
....................................................................................................... 15-101 15-101
View the details of the VC-LSPs ................................................................................................................................. 15-102 15-102 Details of a VC-LSP ......................................................................................................................................................... 15-103 15-103 16
T-MPLS Provisioning Management Overview
................................................................................................................................................................................... 16-1 16-1
Managing T-MPLS PHB profile Overview about PHB profile management View the list of PHB profiles (T-MPLS)
.................................................................................................................. 16-5 16-5
....................................................................................................................... 16-6 16-6
Description of the list of T-MPLS PHB Profiles Create a PHB profile (T-MPLS)
........................................................................................................ 16-7 16-7
....................................................................................................................................... 16-8 16-8
Modify a PHB profiles (T-MPLS)
................................................................................................................................... 16-9 16-9
.................................................................................................................................................................................................................................... 1350 OMS xv 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Delete a PHB profile (T-MPLS) ..................................................................................................................................... 16-11 16-11 View the details of the PHB profiles (T-MPLS)
...................................................................................................... 16-13 16-13
Managing Transport Links (T-MPLS) Overview about Transport Links .................................................................................................................................... 16-14 16-14 View the list of Transport Links ..................................................................................................................................... 16-16 16-16 Description of the list of T-MPLS Transport Links ................................................................................................. 16-17 16-17 Define the Transport Link characteristics ................................................................................................................... 16-18 16-18 Get the Transport Link extremities ................................................................................................................................ 16-20 16-20 Description of the list of Transport Link Extremities ............................................................................................. 16-22 16-22 View the details of the Transport Links ....................................................................................................................... 16-23 16-23 Details of a T-MPLS Transport Link
............................................................................................................................ 16-24 16-24
View the bandwidth load of Transport Links View the inventory of Transport Links
........................................................................................................... 16-25 16-25
........................................................................................................................ 16-28 16-28
Description of the inventory of Transport Links ...................................................................................................... 16-30 16-30 Managing Virtual Transport (T-MPLS) Overview about Virtual Transports
............................................................................................................................... 16-31 16-31
View the list of Virtual Transports ................................................................................................................................. 16-33 16-33 Description of the list of Virtual Transports ............................................................................................................... 16-34 16-34 Create a Virtual Transport ................................................................................................................................................. 16-35 16-35 Modify a Virtual Transport ............................................................................................................................................... 16-37 16-37 Delete a Virtual Transport ................................................................................................................................................. 16-39 16-39 View the details of the Virtual Transport ..................................................................................................................... 16-40 16-40 Details of a Virtual Transport
.......................................................................................................................................... 16-41 16-41
Configuration of a Virtual Transport Implement a Virtual Transport
........................................................................................................................... 16-42 16-42
........................................................................................................................................ 16-44 16-44
De-implement a Virtual Transport ................................................................................................................................. 16-46 16-46 View the Virtual Transport extremities ........................................................................................................................ 16-48 16-48 Description of the list of Virtual Transports ............................................................................................................... 16-49 16-49
.................................................................................................................................................................................................................................... 1350 OMS xvi 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Managing Pseudo Wires (T-MPLS) Overview about Pseudo Wires
........................................................................................................................................ 16-50 16-50
View the list of Pseudo Wires .......................................................................................................................................... 16-51 16-51 Description of the list of Pseudo Wires ........................................................................................................................ 16-52 16-52 Create a Pseudo Wire .......................................................................................................................................................... 16-53 16-53 Modify a PseudoWire ......................................................................................................................................................... 16-55 16-55 Delete a Pseudo Wire .......................................................................................................................................................... 16-57 16-57 View the details of the Pseudo Wires
........................................................................................................................... 16-58 16-58
Details of a Pseudo Wire ................................................................................................................................................... 16-59 16-59 Configuration of the route of a Pseudo Wire ............................................................................................................. 16-60 16-60 Delete a constraint from a Pseudo Wire
...................................................................................................................... 16-62 16-62
Configuration of PHB profile of a Pseudo Wire ....................................................................................................... 16-64 16-64 Configuration of Layer-2 encapsulation of a Pseudo Wire ................................................................................... 16-66 16-66 Allocate Pseudo Wire ......................................................................................................................................................... 16-67 16-67 De-allocate Pseudo Wire ................................................................................................................................................... 16-70 16-70 Implement a Pseudo Wire ................................................................................................................................................. 16-72 16-72 De-implement a Pseudo Wire .......................................................................................................................................... 16-74 16-74 List the constraints of a Pseudo Wire
.......................................................................................................................... 16-76 16-76
Description of the list of Pseudo Wire Constraints .................................................................................................. 16-77 16-77 View the details of the Pseudo Wire constraints ....................................................................................................... 16-78 16-78 Details of a Pseudo Wire Constraint ............................................................................................................................. 16-79 16-79 View the list of cross connections .................................................................................................................................. 16-80 16-80 Description of the list of PW Cross Connections ..................................................................................................... 16-81 16-81 View the Pseudo Wire extremities ................................................................................................................................. 16-82 16-82 Description of the list of PW Extremities ................................................................................................................... 16-83 16-83 View the section inventory from Pseudo Wire .......................................................................................................... 16-84 16-84 Description of the T-MPLS section Inventory
.......................................................................................................... 16-85 16-85
View the bandwidth load of Pseudo Wire ................................................................................................................... 16-86 16-86 View the route of Pseudo Wires
.................................................................................................................................... 16-87 16-87
.................................................................................................................................................................................................................................... 1350 OMS xvii 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
View the Pseudo Wires crossing a Pseudo Wire ....................................................................................................... 16-88 16-88 Description of the list of Pseudo Wires ........................................................................................................................ 16-89 16-89 T-MPLS tunnel schema T-MPLS tunnel schema
..................................................................................................................................................... 16-90 16-90
Ethernet Services in the T-MPLS Domain
................................................................................................................ 16-93 16-93
Managing T-MPLS tunnels T-MPLS tunnel description
.............................................................................................................................................. 16-97 16-97
View the list of T-MPLS tunnels .................................................................................................................................... 16-99 16-99 Description of the list of T-MPLS tunnels
............................................................................................................... 16-100 16-100
Create a T-MPLS tunnel .................................................................................................................................................. 16-101 16-101 Modify a T-MPLS tunnel ................................................................................................................................................ 16-104 16-104 Delete a T-MPLS tunnel .................................................................................................................................................. 16-106 16-106 View the details of the T-MPLS tunnels
................................................................................................................... 16-107 16-107
Details of a T-MPLS tunnel ........................................................................................................................................... 16-108 16-108 Configuration of the route of a T-MPLS tunnel ..................................................................................................... 16-109 16-109 Delete a constraint from a T-MPLS tunnel ............................................................................................................... 16-111 16-111 Configuration of PHB profile of a T-MPLS tunnel ............................................................................................... 16-113 16-113 Configuration of Layer-2 encapsulation of a tunnel ............................................................................................. 16-115 16-115 Allocate T-MPLS tunnel
................................................................................................................................................. 16-117 16-117
De-allocate T-MPLS tunnel ........................................................................................................................................... 16-120 16-120 Implement a T-MPLS tunnel ......................................................................................................................................... 16-122 16-122 De-implement a T-MPLS tunnel .................................................................................................................................. 16-124 16-124 List the constraints of a T-MPLS tunnel
.................................................................................................................. 16-126 16-126
Description of the list of T-MPLS tunnel Constraints .......................................................................................... 16-127 16-127 View the details of the T-MPLS tunnel constraints ............................................................................................... 16-128 16-128 Details of a T-MPLS tunnel Constraint ..................................................................................................................... 16-129 16-129 View the list of cross connections ............................................................................................................................... 16-130 16-130 Description of the list of T-MPLS tunnel Cross Connections ........................................................................... 16-131 16-131 View the T-MPLS tunnel extremities ......................................................................................................................... 16-132 16-132 .................................................................................................................................................................................................................................... 1350 OMS xviii 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Description of the list of T-MPLS tunnel Extremities
......................................................................................... 16-133 16-133
View the section inventory from T-MPLS tunnel .................................................................................................. 16-134 16-134 Description of the Inventory of sections ................................................................................................................... 16-135 16-135 View the bandwidth load of T-MPLS tunnel ........................................................................................................... 16-136 16-136 View the route of T-MPLS tunnels
............................................................................................................................ 16-137 16-137
View the Pseudo Wires crossing a T-MPLS tunnel ............................................................................................... 16-138 16-138 Description of the list of Pseudo Wires ..................................................................................................................... 16-139 16-139 Tunnel protection Tunnel protection create .................................................................................................................................................. 16-140 16-140 T-MPLS Routing display ................................................................................................................................................ 16-144 16-144 Tunnel switch commands ............................................................................................................................................... 16-147 16-147 Other info on T-MPLS routing display ...................................................................................................................... 16-152 16-152 MAC Flushing Protection Overview
.............................................................................................................................................................................. 16-156 16-156
MAC flushing protection description
........................................................................................................................ 16-157 16-157
MAC flushing protection creation ............................................................................................................................... 16-158 16-158 MAC flushing protection list
........................................................................................................................................ 16-160 16-160
Attributes of MAC-flushing protection ..................................................................................................................... 16-161 16-161 Interconnection Scheme list ........................................................................................................................................... 16-162 16-162 Attributes of Interconnection Schemes
..................................................................................................................... 16-163 16-163
TMPLS EVC: Force MAC flushing ........................................................................................................................... 16-164 16-164 Tunnel Redundancy Overview
.............................................................................................................................................................................. 16-165 16-165
Description ........................................................................................................................................................................... 16-166 16-166 Create one-to-one-open protection .............................................................................................................................. 16-173 16-173 Create Dual-point-to-point Protection
....................................................................................................................... 16-175 16-175
Create MAC Flushing Protection Schema EVC setup
.............................................................................................................. 16-177 16-177
............................................................................................................................................................................ 16-178 16-178
.................................................................................................................................................................................................................................... 1350 OMS xix 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
17
EVC over T-MPLS Overview
................................................................................................................................................................................... 17-1 17-1
Create T-MPLS Structure Create Link over Cable T-MPLS tunnel create
........................................................................................................................................................ 17-2 17-2
........................................................................................................................................................ 17-14 17-14
T-MPLS-Create PW ............................................................................................................................................................ 17-21 17-21 EVC on T-MPLS Create EVC over T-MPLS wizard ................................................................................................................................. 17-27 17-27 List the T-MPLS EVC ........................................................................................................................................................ 17-32 17-32 Description of the list of T-MPLS EVC
...................................................................................................................... 17-33 17-33
Create EVC over T-MPLS EVPL bottom up ............................................................................................................. 17-34 17-34 Create EVC over T-MPLS EVPL top down ............................................................................................................... 17-55 17-55 Create EVC over T-MPLS EVPLAN ........................................................................................................................... 17-72 17-72 Create EVC over T-MPLS BTV ..................................................................................................................................... 17-86 17-86 Create EVC over T-MPLS HSI ....................................................................................................................................... 17-90 17-90 Alarms EVC T-MPLS
........................................................................................................................................................ 17-94 17-94
Delete NE with EVC over T-MPLS What to do deleting a NE .................................................................................................................................................. 17-97 17-97 Delete NE detailed procedure .......................................................................................................................................... 17-98 17-98 Verify create EVC over T-MPLS Verify create EVC over T-MPLS ................................................................................................................................. 17-114 17-114 18
End to End Ethernet Provisioning Management Overview
................................................................................................................................................................................... 18-1 18-1
IP DSCP/TOS and EtherType Classification of the frames ................................................................................................................................................ 18-6 18-6 Managing Customer Overview about Customer
.................................................................................................................................................. 18-8 18-8
Display the Customer List ................................................................................................................................................... 18-9 18-9 .................................................................................................................................................................................................................................... 1350 OMS xx 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Description of the list of Customers
............................................................................................................................. 18-10 18-10
Create a Customer ................................................................................................................................................................ 18-11 18-11 Modify a Customer Delete a Customer
............................................................................................................................................................. 18-12 18-12
............................................................................................................................................................... 18-14 18-14
Get Details of the Customer ............................................................................................................................................. 18-15 18-15 Details of a Customer ......................................................................................................................................................... 18-16 18-16 Managing Ethernet Services Overview about Ethernet Services
................................................................................................................................ 18-17 18-17
Display the Service List ..................................................................................................................................................... 18-20 18-20 Description of the list of Services .................................................................................................................................. 18-21 18-21 Create a Service .................................................................................................................................................................... 18-22 18-22 Service Setup ......................................................................................................................................................................... 18-24 18-24 Modify a Service .................................................................................................................................................................. 18-30 18-30 Delete a Service .................................................................................................................................................................... 18-32 18-32 Get details of the Service Details of a Service
.................................................................................................................................................. 18-33 18-33
............................................................................................................................................................. 18-35 18-35
Display the Services of a Customer
.............................................................................................................................. 18-36 18-36
Managing ETS Ethernet Virtual Connections (EVC) Overview about ETS Ethernet Virtual Connections ................................................................................................ 18-37 18-37 Resource Reservation for Private Services ................................................................................................................. 18-39 18-39 Display the list of Connection Oriented EVC ........................................................................................................... 18-42 18-42 Description of the list of EVCs ....................................................................................................................................... 18-43 18-43 Create a Connection Oriented EVC .............................................................................................................................. 18-44 18-44 Modify an ETS EVC Delete an ETS EVC
.......................................................................................................................................................... 18-47 18-47
............................................................................................................................................................ 18-49 18-49
Get the EVC properties ...................................................................................................................................................... 18-51 18-51 Details of a EVC
.................................................................................................................................................................. 18-53 18-53
Allocate ETS EVC
.............................................................................................................................................................. 18-54 18-54
Deallocate ETS EVC .......................................................................................................................................................... 18-55 18-55 .................................................................................................................................................................................................................................... 1350 OMS xxi 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Implement ETS EVC .......................................................................................................................................................... 18-56 18-56 Deimplement ETS EVC .................................................................................................................................................... 18-57 18-57 Commission ETS EVC ...................................................................................................................................................... 18-58 18-58 Decommission ETS EVC
................................................................................................................................................. 18-59 18-59
List the EVC terminations ................................................................................................................................................ 18-60 18-60 Description of the list of terminations .......................................................................................................................... 18-61 18-61 Delete an EVC Termination ............................................................................................................................................. 18-62 18-62 Get the EVC termination properties .............................................................................................................................. 18-63 18-63 Details of a Termination
.................................................................................................................................................... 18-65 18-65
Add an EVC termination ................................................................................................................................................... 18-66 18-66 EVC Fault Localization ..................................................................................................................................................... 18-68 18-68 Description of the list of Fault Localization Description of the list of Alarms Start PM on an EVC
.............................................................................................................. 18-69 18-69
.................................................................................................................................... 18-70 18-70
........................................................................................................................................................... 18-71 18-71
Stop PM on an EVC ............................................................................................................................................................ 18-72 18-72 Synchronize PM on an EVC ............................................................................................................................................ 18-73 18-73 Show PM on an EVC
......................................................................................................................................................... 18-74 18-74
View the Routing Display on an EVC
......................................................................................................................... 18-75 18-75
Managing End-to-End Ethernet Virtual Connections (E2E EVC) Overview about E2E Ethernet Virtual Connections ................................................................................................ 18-76 18-76 Display the list of E2E EVC ............................................................................................................................................ 18-78 18-78 Description of the list of EVCs ....................................................................................................................................... 18-79 18-79 Create an E2E EVC ............................................................................................................................................................. 18-80 18-80 Create a full E2E EVC ....................................................................................................................................................... 18-84 18-84 Create a raw E2E EVC
...................................................................................................................................................... 18-86 18-86
Modify a full E2E EVC ..................................................................................................................................................... 18-87 18-87 Join E2E EVC
....................................................................................................................................................................... 18-89 18-89
Managing an E2E EVC
..................................................................................................................................................... 18-91 18-91
.................................................................................................................................................................................................................................... 1350 OMS xxii 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
EVC over SDH Structure for EVC over SDH ........................................................................................................................................... 18-93 18-93 Assign ports to domain .................................................................................................................................................... 18-102 18-102 EVC over SDH ................................................................................................................................................................... 18-106 18-106 Alarms EVC T-MPLS ...................................................................................................................................................... 18-118 18-118 Full EVC Takeover Overview about Full EVC Takeover procedure ..................................................................................................... 18-121 18-121 Full EVC Takeover Procedure ...................................................................................................................................... 18-122 18-122 T-MPLS Takeover T-MPLS Takeover description ...................................................................................................................................... 18-130 18-130 Takeover procedure for T-MPLS ................................................................................................................................. 18-131 18-131 Managing Color Profiles Overview about Color Profiles ..................................................................................................................................... 18-133 18-133 Display the Color Profile list ......................................................................................................................................... 18-134 18-134 Create a Color Profile
...................................................................................................................................................... 18-135 18-135
Modify a Color Profile Delete a Color Profile
.................................................................................................................................................... 18-136 18-136
...................................................................................................................................................... 18-139 18-139
Get the Color Profile Properties ................................................................................................................................... 18-140 18-140 Managing Traffic Descriptors Overview about Traffic Descriptor
............................................................................................................................. 18-142 18-142
Display the Traffic Descriptor list ............................................................................................................................... 18-144 18-144 Description of the list of Traffic Descriptors ........................................................................................................... 18-145 18-145 Create a Traffic Descriptor ............................................................................................................................................. 18-146 18-146 Modify a Traffic Descriptor ........................................................................................................................................... 18-149 18-149 Delete a Traffic Descriptor ............................................................................................................................................. 18-152 18-152 Get the Traffic Descriptor Properties Details of a Traffic Descriptor
......................................................................................................................... 18-153 18-153
...................................................................................................................................... 18-155 18-155
.................................................................................................................................................................................................................................... 1350 OMS xxiii 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Managing Traffic Classifiers Overview about Traffic Classifiers
............................................................................................................................. 18-156 18-156
Display the Traffic Classifier list ................................................................................................................................. 18-158 18-158 Description of the list of Traffic Classifiers ............................................................................................................. 18-159 18-159 Create a Traffic Classifier ............................................................................................................................................... 18-160 18-160 Modify a Traffic Classifier ............................................................................................................................................. 18-162 18-162 Delete a Traffic Classifier ............................................................................................................................................... 18-164 18-164 Get the Traffic Classifier Properties ........................................................................................................................... 18-165 18-165 Details of a Traffic Classifier ........................................................................................................................................ 18-167 18-167 Managing Ethernet ETS Edge Physical Ports Overview about Ethernet edge physical ports
....................................................................................................... 18-168 18-168
Display the ETS edge port list ...................................................................................................................................... 18-169 18-169 Modify an edge port
......................................................................................................................................................... 18-170 18-170
Configure an ETS Edge Port ......................................................................................................................................... 18-172 18-172 Get the ETS Edge Port Properties ............................................................................................................................... 18-175 18-175 Display the traffic parameter list .................................................................................................................................. 18-177 18-177 Description of the list of Traffic Parameters
........................................................................................................... 18-178 18-178
Details of Traffic Parameters ......................................................................................................................................... 18-179 18-179 Navigation to equipment ................................................................................................................................................. 18-180 18-180 Show PM on an Edge Port ............................................................................................................................................. 18-182 18-182 Show External Termination Point
............................................................................................................................... 18-183 18-183
Managing Ethernet Transport Links Overview about Ethernet Transport Links
............................................................................................................... 18-184 18-184
Display the Ethernet ETS Transport Link list ......................................................................................................... 18-186 18-186 Description of the list of ETS Transport Links ....................................................................................................... 18-187 18-187 Configure an ETS Transport Link ............................................................................................................................... 18-188 18-188 Get the Transport Link extremities Get the Transport Link properties
............................................................................................................................. 18-190 18-190
............................................................................................................................... 18-193 18-193
Details of ETS Transport Links .................................................................................................................................... 18-195 18-195 .................................................................................................................................................................................................................................... 1350 OMS xxiv 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Display the Transport Link bandwidth load
............................................................................................................ 18-196 18-196
Managing Ethernet Segments Overview about Ethernet Segments Display the Ethernet Segment list
........................................................................................................................... 18-197 18-197
............................................................................................................................... 18-199 18-199
Description of the list of Ethernet Segments ........................................................................................................... 18-200 18-200 Create an Ethernet Segment
.......................................................................................................................................... 18-202 18-202
Modify an Ethernet Segment Delete an Ethernet Segment
........................................................................................................................................ 18-205 18-205
.......................................................................................................................................... 18-208 18-208
Associate a Traffic Classifier to an Ethernet Segment ......................................................................................... 18-209 18-209 Disassociate a Traffic Classifier to an Ethernet Segment Add a constraint to an Ethernet Segment
................................................................................... 18-211 18-211
................................................................................................................. 18-213 18-213
List the constraints related to an Ethernet Segment .............................................................................................. 18-216 18-216 Description of the list of Constraints .......................................................................................................................... 18-217 18-217 Delete an Ethernet Segment Constraint
.................................................................................................................... 18-218 18-218
Get the Ethernet Segment Constraint Properties .................................................................................................... 18-219 18-219 Details of an Ethernet Segment Constraint .............................................................................................................. 18-221 18-221 Modify a Constraint .......................................................................................................................................................... 18-222 18-222 VLAN Push/Pop at ETS NNI Interface
.................................................................................................................... 18-225 18-225
Allocate an Ethernet Segment ....................................................................................................................................... 18-226 18-226 Deallocate an Ethernet Segment
................................................................................................................................. 18-227 18-227
Implement an Ethernet Segment .................................................................................................................................. 18-229 18-229 Deimplement an Ethernet Segment Configure an Ethernet Segment
............................................................................................................................ 18-231 18-231
................................................................................................................................... 18-233 18-233
Get the Ethernet Segment extremities ........................................................................................................................ 18-235 18-235 Description of the list of Ethernet Segment Extremities ..................................................................................... 18-239 18-239 Get the Ethernet Segment properties .......................................................................................................................... 18-240 18-240 Details of an Ethernet Segment .................................................................................................................................... 18-241 18-241 Display the route of an Ethernet Segment ................................................................................................................ 18-242 18-242 Display the connectivity view of an Ethernet Segment ....................................................................................... 18-244 18-244 .................................................................................................................................................................................................................................... 1350 OMS xxv 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Managing VLAN types Overview about VLAN types
....................................................................................................................................... 18-246 18-246
Display the VLAN type list ........................................................................................................................................... 18-247 18-247 Create a VLAN type ......................................................................................................................................................... 18-248 18-248 Modify a VLAN type ....................................................................................................................................................... 18-251 18-251 Delete a VLAN type ......................................................................................................................................................... 18-253 18-253 19
Bridge Network Management Overview
................................................................................................................................................................................... 19-1 19-1
Connection Less Networks Bridge Network Management ............................................................................................................................................ 19-4 19-4 Bridge Traffic Management ................................................................................................................................................ 19-6 19-6 Spanning Tree Instance Management ............................................................................................................................. 19-8 19-8 VLAN management ............................................................................................................................................................ 19-10 19-10 EVC Data Plane .................................................................................................................................................................... 19-11 19-11 The EVC life cycle .............................................................................................................................................................. 19-13 19-13 Layer-2 Control Protocol Processing ............................................................................................................................ 19-16 19-16 Bandwidth Profile per UNI
.............................................................................................................................................. 19-18 19-18
View the list of bridge NEs
.............................................................................................................................................. 19-22 19-22
Description of the list of Bridge NEs View the list of bridge ENEs
........................................................................................................................... 19-23 19-23
........................................................................................................................................... 19-24 19-24
Description of the list of Bridge ENEs
........................................................................................................................ 19-25 19-25
View the Provider Bridge Flows of an EVC .............................................................................................................. 19-26 19-26 Connection Less Transport Link Management Display the Ethernet Bridge Transport Link list ....................................................................................................... 19-27 19-27 Description of the list of Bridge Transport Links Configure a transport Link
.................................................................................................... 19-29 19-29
............................................................................................................................................... 19-30 19-30
Get the Transport Link extremities ................................................................................................................................ 19-34 19-34 Description of the list of Transport Link extremities .............................................................................................. 19-37 19-37 Get the Transport Link properties .................................................................................................................................. 19-38 19-38 .................................................................................................................................................................................................................................... 1350 OMS xxvi 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Details of an ETB Transport Link .................................................................................................................................. 19-40 19-40 Activate a Bridge Transport Link ................................................................................................................................... 19-41 19-41 Deactivate a Bridge Transport Link .............................................................................................................................. 19-42 19-42 View the list of Bridge Edge Ports
................................................................................................................................ 19-43 19-43
Description of the list of Bridge Edge Ports Activate a Bridge Edge Port
.............................................................................................................. 19-44 19-44
............................................................................................................................................ 19-45 19-45
Deactivate a Bridge Edge Port ........................................................................................................................................ 19-46 19-46 Connection Less EVC Management View the Connection Less EVC list .............................................................................................................................. 19-47 19-47 Description of the list of Bridge EVCs ........................................................................................................................ 19-48 19-48 Create a Bridge EVC .......................................................................................................................................................... 19-49 19-49 Modify a Bridge EVC ........................................................................................................................................................ 19-53 19-53 Delete a Bridge EVC .......................................................................................................................................................... 19-56 19-56 Get the EVC properties ...................................................................................................................................................... 19-58 19-58 Details of a Bridge EVC .................................................................................................................................................... 19-60 19-60 Configure a Bridge or an ETS EVC .............................................................................................................................. 19-61 19-61 Add bridge Transport Link to EVC ............................................................................................................................... 19-62 19-62 Remove bridge Transport Link to EVC ....................................................................................................................... 19-63 19-63 Inventory of bridge Transport Links of an EVC ....................................................................................................... 19-64 19-64 EVC Fault Localization ..................................................................................................................................................... 19-65 19-65 Description of the list of Fault Localization Description of the list of Alarms
.............................................................................................................. 19-68 19-68
.................................................................................................................................... 19-69 19-69
Navigation to AS .................................................................................................................................................................. 19-70 19-70 Bridge EVC Termination Management View the list of EVC terminations ................................................................................................................................. 19-72 19-72 Description of the list of EVC Terminations
............................................................................................................. 19-73 19-73
Add Connection Less EVC Termination ..................................................................................................................... 19-74 19-74 Delete a Bridge EVC Termination ................................................................................................................................. 19-81 19-81 Configure a Bridge EVC Termination .......................................................................................................................... 19-83 19-83 .................................................................................................................................................................................................................................... 1350 OMS xxvii 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Get the EVC termination properties .............................................................................................................................. 19-85 19-85 Details of an EVC Termination ....................................................................................................................................... 19-87 19-87 Workflow for Bridge Management Overview about Workflow
.............................................................................................................................................. 19-88 19-88
Create a Domain ................................................................................................................................................................... 19-90 19-90 Add NE to a Domain
.......................................................................................................................................................... 19-91 19-91
Domain Configuration Domain Modification
....................................................................................................................................................... 19-94 19-94
......................................................................................................................................................... 19-96 19-96
Configure a Network Element
........................................................................................................................................ 19-98 19-98
Link Over TDM configuration
..................................................................................................................................... 19-100 19-100
NE Ethernet Physical Port Configuration ................................................................................................................. 19-102 19-102 Create a Customer ............................................................................................................................................................. 19-104 19-104 Create an Ethernet Service ............................................................................................................................................. 19-107 19-107 Traffic Descriptor Definition ......................................................................................................................................... 19-109 19-109 EVC Allocation and Implementation
......................................................................................................................... 19-111 19-111
EVC Bandwidth Management Dynamic change capability ............................................................................................................................................ 19-112 19-112 Function Description ........................................................................................................................................................ 19-113 19-113 Service Delimiting Vlan Push/Pop On Provider Bridge UNI/IWI Management
............................................................................. 19-117 19-117
Spanning Tree Show the Spanning Tree Instance of EVC ............................................................................................................... 19-119 19-119 Show the Spanning Tree Instance
............................................................................................................................... 19-120 19-120
Spanning Tree Instance configuration
....................................................................................................................... 19-121 19-121
Spanning Tree Instance Implementation ................................................................................................................... 19-123 19-123 Spanning Tree Instance Deimplementation ............................................................................................................. 19-124 19-124 20
Provider Backbone Bridge Network Management Overview
................................................................................................................................................................................... 20-1 20-1
.................................................................................................................................................................................................................................... 1350 OMS xxviii 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Provider Backbone Bridge (PBB) Networks Provider Backbone Bridge Management ....................................................................................................................... 20-5 20-5 PBB EVC provisioning ........................................................................................................................................................ 20-8 20-8 Ethernet Ring Protocol (ERP) ......................................................................................................................................... 20-10 20-10 Network Configuration Network Configuration ...................................................................................................................................................... 20-11 20-11 PBB Domain Create ............................................................................................................................................................ 20-12 20-12 Define NE ............................................................................................................................................................................... 20-14 20-14 Provisioning Provisioning hardware reference .................................................................................................................................... 20-17 20-17 Transport link
....................................................................................................................................................................... 20-20 20-20
Create Ethernet Physical Connection
........................................................................................................................... 20-21 20-21
Assign Link over Cable to PBB domain
..................................................................................................................... 20-24 20-24
ERP configuration Create ERP Ring
.................................................................................................................................................................. 20-30 20-30
Create an ERP Instance ...................................................................................................................................................... 20-38 20-38 Backbone VLAN ID B-VID configuration ........................................................................................................................................................... 20-46 20-46 EVC-EVPLAN Service in PBB/ERP Additional Info on PBB/ERP Service
.......................................................................................................................... 20-52 20-52
PBB EVC Termination Management Add PBB EVC Termination ............................................................................................................................................. 20-56 20-56 Remove PBB EVC Termination ..................................................................................................................................... 20-59 20-59 Provider Backbone Bridge EVC Management Overview ................................................................................................................................................................................. 20-60 20-60 View the PBB EVC list ...................................................................................................................................................... 20-61 20-61 Description of the list of PBB EVCs ............................................................................................................................ 20-62 20-62 Create PBB EVC .................................................................................................................................................................. 20-63 20-63 .................................................................................................................................................................................................................................... 1350 OMS xxix 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Allocate PBB EVC .............................................................................................................................................................. 20-65 20-65 Deallocate PBB EVC
......................................................................................................................................................... 20-67 20-67
Implement PBB EVC ......................................................................................................................................................... 20-68 20-68 Deimplement PBB EVC .................................................................................................................................................... 20-70 20-70 Add Termination on implemented PBB EVC
........................................................................................................... 20-71 20-71
Remove Termination on implemented EVC .............................................................................................................. 20-72 20-72 Configure PBB EVC
.......................................................................................................................................................... 20-73 20-73
Bridge Flows of PBB EVC
.............................................................................................................................................. 20-74 20-74
PBB EVC Broadcast Domain Containment ............................................................................................................... 20-76 20-76 Enable Broadcast Domain Containment
..................................................................................................................... 20-77 20-77
Disable Broadcast Domain Containment .................................................................................................................... 20-78 20-78 Automatic association UNI port - default VT ........................................................................................................... 20-79 20-79 Manual association UNI port - user VT
...................................................................................................................... 20-80 20-80
Configuration of the DEI bit ............................................................................................................................................ 20-81 20-81 B-VID Management Overview ................................................................................................................................................................................. 20-82 20-82 View the B-VID list
............................................................................................................................................................ 20-83 20-83
Create PBB B-VID .............................................................................................................................................................. 20-84 20-84 Delete PBB B-VID .............................................................................................................................................................. 20-86 20-86 Allocate PBB B-VID .......................................................................................................................................................... 20-87 20-87 Deallocate PBB B-VID ...................................................................................................................................................... 20-88 20-88 Implement PBB B-VID
..................................................................................................................................................... 20-89 20-89
Deimplement PBB B-VID ................................................................................................................................................ 20-91 20-91 Domain Wide VID distribution ....................................................................................................................................... 20-93 20-93 Ring Association to a B-VID ........................................................................................................................................... 20-95 20-95 Ring Dissociation from B-VID ....................................................................................................................................... 20-97 20-97 Change ERP of a B-VID
................................................................................................................................................... 20-99 20-99
List ERP instances of a B-VID ..................................................................................................................................... 20-101 20-101 Association of Transport Link to B-VID .................................................................................................................. 20-102 20-102 .................................................................................................................................................................................................................................... 1350 OMS xxx 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Dissociation of Transport Link to B-VID ................................................................................................................. 20-104 20-104 Ethernet Ring Protection (ERP) Management Overview
.............................................................................................................................................................................. 20-107 20-107
View the ERP ring list
..................................................................................................................................................... 20-108 20-108
Description of the list of ERP ....................................................................................................................................... 20-109 20-109 Create/delete ERP Ring ................................................................................................................................................... 20-110 20-110 Implement/deimplement the ERP ERP Switch Command
............................................................................................................................... 20-112 20-112
.................................................................................................................................................... 20-113 20-113
ERP Switch Command From Port ............................................................................................................................... 20-114 20-114 Add/remove Transport Link in a Ring ....................................................................................................................... 20-115 20-115 Add/remove Node in a Ring .......................................................................................................................................... 20-116 20-116 Create/delete ERP Ring bundle .................................................................................................................................... 20-117 20-117 Add/remove ERP Ring in a bundle ............................................................................................................................. 20-118 20-118 ERP Instance Management Overview
.............................................................................................................................................................................. 20-120 20-120
View the ERP instance list
............................................................................................................................................. 20-121 20-121
Description of the list of ERP instances .................................................................................................................... 20-122 20-122 Create/delete ERP instance ............................................................................................................................................ 20-123 20-123 Implement/deimplement the ERP instance Associate OAM to the ERP instance
............................................................................................................. 20-125 20-125
......................................................................................................................... 20-126 20-126
Get a graphical view of the ERP instance
............................................................................................................... 20-127 20-127
Modify Defined ERP instance ...................................................................................................................................... 20-129 20-129 Modify implemented ERP instance
............................................................................................................................ 20-131 20-131
PBB Fault Management Overview
.............................................................................................................................................................................. 20-133 20-133
PBB Fault Localization and navigation to AS ........................................................................................................ 20-134 20-134 Workflow for PBB Management Overview about Workflow
............................................................................................................................................ 20-135 20-135
Create a PBB Domain ...................................................................................................................................................... 20-137 20-137 .................................................................................................................................................................................................................................... 1350 OMS xxxi 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Add NE to a Domain ........................................................................................................................................................ 20-138 20-138 Add Transport Link to a Domain ................................................................................................................................. 20-139 20-139 ERP provisioning ............................................................................................................................................................... 20-141 20-141 Configure B-VID
............................................................................................................................................................. 20-143 20-143
Create a PBB EVC ............................................................................................................................................................ 20-144 20-144 PBB EVC traffic classification ..................................................................................................................................... 20-153 20-153 Traffic Descriptor Definition ......................................................................................................................................... 20-154 20-154 EVC Allocation and Implementation ......................................................................................................................... 20-155 20-155 In Band Management Overview
.............................................................................................................................................................................. 20-156 20-156
Address Configuration of the Network Elements .................................................................................................. 20-157 20-157 Lag Port Creation (Via Zic) ........................................................................................................................................... 20-165 20-165 NMS Start Supervision (NE Not Defined On NMS) 21
........................................................................................... 20-183 20-183
Broadcast TV Service Management Overview
................................................................................................................................................................................... 21-1 21-1
Section I: Introduction Overview
................................................................................................................................................................................... 21-3 21-3
Overview about Broadcast TV
.......................................................................................................................................... 21-4 21-4
Managing Broadcast TV Elements
.................................................................................................................................. 21-5 21-5
View the list of Broadcast TV Elements ........................................................................................................................ 21-6 21-6 Create a BTV Element .......................................................................................................................................................... 21-8 21-8 Modify a BTV Element
..................................................................................................................................................... 21-11 21-11
Delete a BTV Element ....................................................................................................................................................... 21-14 21-14 View the details of the BTV Elements ......................................................................................................................... 21-16 21-16 Details of a BTV Elements
............................................................................................................................................. 21-17 21-17
View the list of ETPs belonging to a BTV Element ................................................................................................ 21-18 21-18 Description of the list of BTV ENE inventory .......................................................................................................... 21-19 21-19 Create an ETP in a BTV Element
.................................................................................................................................. 21-20 21-20
Delete an ETP in a BTV Element
.................................................................................................................................. 21-22 21-22
.................................................................................................................................................................................................................................... 1350 OMS xxxii 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Section II: Workflow for BTV construction Overview ................................................................................................................................................................................. 21-24 21-24 Create path on 1350 OMS SDH application .............................................................................................................. 21-25 21-25 Create Broadcast TV Element ......................................................................................................................................... 21-26 21-26 Create Link Broadcast TV ................................................................................................................................................ 21-29 21-29 Section III: Workflow for BTV Service Management Overview ................................................................................................................................................................................. 21-33 21-33 Create a Customer
.............................................................................................................................................................. 21-34 21-34
Create Ethernet Service
..................................................................................................................................................... 21-35 21-35
Create a Connection Oriented EVC .............................................................................................................................. 21-37 21-37 Section IV: Bridge Based BTV Service Overview ................................................................................................................................................................................. 21-40 21-40 Overview about the Services
........................................................................................................................................... 21-41 21-41
IGMP Snooping Management ......................................................................................................................................... 21-42 21-42 IGMP Snooping State Management .............................................................................................................................. 21-44 21-44 22
Network Supervision Overview
................................................................................................................................................................................... 22-1 22-1
Managing alarms Overview about alarms ......................................................................................................................................................... 22-2 22-2 Alarms from ISA E/FE/GE board Alarms from ISA ES1/4 board
.................................................................................................................................... 22-3 22-3
.......................................................................................................................................... 22-4 22-4
Alarms from ISA ES16 board ............................................................................................................................................ 22-6 22-6 Alarms or Events on SDH paths from 1350 OMS SDH .......................................................................................... 22-8 22-8 Alarm status management ................................................................................................................................................... 22-9 22-9 Alarm correlation and generation toward AS
............................................................................................................ 22-11 22-11
Managing Fault Localization Display the Fault Localization list ................................................................................................................................. 22-12 22-12 Description of Fault Localization
.................................................................................................................................. 22-14 22-14
.................................................................................................................................................................................................................................... 1350 OMS xxxiii 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Manual Synchronization of Alarms on NE
................................................................................................................ 22-15 22-15
Specific Behavior Client Signal Fail Alarm Management ......................................................................................................................... 22-16 22-16 23
Network Utilities Overview
................................................................................................................................................................................... 23-1 23-1
Audit, Alignment, Reservation, Recovery Overview
................................................................................................................................................................................... 23-2 23-2
The AAR procedure
............................................................................................................................................................. 23-3 23-3
NE Audit tool ........................................................................................................................................................................... 23-6 23-6 Results of Audit ....................................................................................................................................................................... 23-8 23-8 Reservation tool .................................................................................................................................................................... 23-13 23-13 Align Up of Ethernet Domain Data ............................................................................................................................... 23-15 23-15 Start the audit, alignment, reserve procedure
............................................................................................................ 23-16 23-16
Stop the audit, alignment, reserve procedure ............................................................................................................. 23-17 23-17 View the list of auditable NEs ......................................................................................................................................... 23-18 23-18 Description of the list of auditable NEs ....................................................................................................................... 23-19 23-19 Perform an audit on a NE .................................................................................................................................................. 23-20 23-20 View the list of Audited NEs
........................................................................................................................................... 23-22 23-22
Description of the list of Audited NEs ......................................................................................................................... 23-23 23-23 View the results of an audit .............................................................................................................................................. 23-24 23-24 Perform an alignment on a NE ........................................................................................................................................ 23-26 23-26 NE Alignment tool Overview ................................................................................................................................................................................. 23-27 23-27 Workflow to align up Ethernet Data
............................................................................................................................. 23-28 23-28
ISA Board Replacement Procedure ............................................................................................................................... 23-30 23-30 Perform a reservation on a NE ........................................................................................................................................ 23-32 23-32 Restore procedure for ISA board .................................................................................................................................... 23-33 23-33
.................................................................................................................................................................................................................................... 1350 OMS xxxiv 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
24
Operation, Administration, and Maintenance (OAM) Management Overview
................................................................................................................................................................................... 24-1 24-1
Ethernet OAM OAM main functions
............................................................................................................................................................ 24-3 24-3
Create OAM Domain ............................................................................................................................................................ 24-7 24-7 List OAM Domains
............................................................................................................................................................... 24-8 24-8
Description of the list of OAM MD OAM Domain Properties
................................................................................................................................ 24-9 24-9
.................................................................................................................................................. 24-10 24-10
Details of OAM MD ........................................................................................................................................................... 24-11 24-11 Modify OAM Domain
....................................................................................................................................................... 24-12 24-12
Configure OAM Domain
.................................................................................................................................................. 24-13 24-13
Deimplement OAM Domain
........................................................................................................................................... 24-14 24-14
Inventory of OAM items from MD ............................................................................................................................... 24-15 24-15 Inventory of OAM monitored objects from MD ...................................................................................................... 24-16 24-16 Maintenance Association (MA) Maintenance Associations
................................................................................................................................................ 24-17 24-17
List Maintenance Association (MA) ............................................................................................................................. 24-18 24-18 Description of the list of OAM MA .............................................................................................................................. 24-19 24-19 Properties of Maintenance Association (MA) ........................................................................................................... 24-20 24-20 Details of the OAM MA .................................................................................................................................................... 24-21 24-21 Modify Maintenance Association (MA) ...................................................................................................................... 24-22 24-22 Configure Maintenance Association (MA)
............................................................................................................... 24-23 24-23
Enable/Disable Continuity Check (CC) ....................................................................................................................... 24-24 24-24 Deimplement OAM MA
................................................................................................................................................... 24-25 24-25
Inventory of OAM items from MA ............................................................................................................................... 24-26 24-26 Inventory of OAM monitored objects from MA ...................................................................................................... 24-27 24-27 Maintenance Activation Maintenance Activation on EVC
................................................................................................................................... 24-28 24-28
.................................................................................................................................................................................................................................... 1350 OMS xxxv 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Loopback Loopback activation ............................................................................................................................................................ 24-29 24-29 Linktrace Linktrace activation ............................................................................................................................................................. 24-31 24-31 Delay measurement and Loss measurement Overview ................................................................................................................................................................................. 24-33 24-33 Packet Delay measurement
.............................................................................................................................................. 24-34 24-34
Packet Loss measurement ................................................................................................................................................. 24-35 24-35 Configure Maintenance End Points ............................................................................................................................... 24-36 24-36 List the OAM ETH DM Tool
.......................................................................................................................................... 24-38 24-38
List the OAM ETH SLM Tool ........................................................................................................................................ 24-40 24-40 Create ETH DM Tool ......................................................................................................................................................... 24-42 24-42 Create ETH SLM Tool ....................................................................................................................................................... 24-44 24-44 Activate/Deactivate OAM ETH DM Tool .................................................................................................................. 24-46 24-46 Activate/Deactivate OAM ETH SLM Tool ................................................................................................................ 24-47 24-47 Inventory from OAM ETH DM Tool ........................................................................................................................... 24-48 24-48 Inventory from OAM ETH SLM Tool ......................................................................................................................... 24-49 24-49 Configure OAM ETH DM Tool ..................................................................................................................................... 24-50 24-50 Configure OAM ETH SLM Tool ................................................................................................................................... 24-52 24-52 25
Circuit Emulation Service Management Overview
................................................................................................................................................................................... 25-1 25-1
CES Overview Circuit Emulation Services definition ............................................................................................................................. 25-4 25-4 TDM client synchronization ............................................................................................................................................... 25-8 25-8 Protection setup after link creation
.................................................................................................................................. 25-9 25-9
CAC tolerance and modulation mode
.......................................................................................................................... 25-11 25-11
Resource assignment to Packet Radio domain .......................................................................................................... 25-12 25-12 Resource assignment to T-MPLS domain ................................................................................................................... 25-14 25-14 .................................................................................................................................................................................................................................... 1350 OMS xxxvi 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Packet Radio domain OAM and protections Packet Radio performance monitoring
............................................................................................................. 25-17 25-17
........................................................................................................................ 25-19 25-19
Packet Radio protection group ........................................................................................................................................ 25-20 25-20 Loopback management ...................................................................................................................................................... 25-21 25-21 T-MPLS domain OAM and protections ....................................................................................................................... 25-22 25-22 Packet Radio domain QoS management
..................................................................................................................... 25-24 25-24
Packet Radio domain inter-working .............................................................................................................................. 25-25 25-25 T-MPLS domain inter-working ....................................................................................................................................... 25-26 25-26 Circuit Emulation Service Management
..................................................................................................................... 25-27 25-27
MEF8 CES terminated service ........................................................................................................................................ 25-33 25-33 Generic Circuit Emulation implementation
............................................................................................................... 25-36 25-36
MEF8 Circuit Emulation Service implementation
.................................................................................................. 25-38 25-38
SATOP Circuit Emulation Service implementation ................................................................................................ 25-43 25-43 Generic Circuit Emulation Service OAM and protections ................................................................................... 25-45 25-45 MEF8 Circuit Emulation Service OAM and protections ...................................................................................... 25-46 25-46 SATOP Circuit Emulation Service OAM and protections
................................................................................... 25-48 25-48
Circuit Emulation AAR Network Operation .............................................................................................................. 25-50 25-50 CES Takeover description
................................................................................................................................................ 25-52 25-52
CES Procedures .................................................................................................................................................................................................... 25-53 25-53
Circuit Emulation Service graphical inventory ......................................................................................................... 25-55 25-55 View the list of CES Domains (Packet Radio) .......................................................................................................... 25-58 25-58 View the details of CES Domain (Packet Radio) ..................................................................................................... 25-59 25-59 Inventory from CES Domain (Packet Radio) ............................................................................................................ 25-60 25-60 Create CES Domain (Packet Radio) ............................................................................................................................. 25-61 25-61 Assign/Deassign resources to Packet Radio Domain ............................................................................................. 25-62 25-62 Assign/Deassign resources to T-MPLS Domain
...................................................................................................... 25-63 25-63
View the list of CES NEs .................................................................................................................................................. 25-64 25-64 Description of the list of CES NEs ................................................................................................................................ 25-65 25-65 .................................................................................................................................................................................................................................... 1350 OMS xxxvii 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
View the details of CES NE ............................................................................................................................................. 25-66 25-66 Details of CES NE ............................................................................................................................................................... 25-67 25-67 Inventory from CES NE .................................................................................................................................................... 25-68 25-68 Inventory from Protection Group ................................................................................................................................... 25-70 25-70 View the list of CES Transport Links ........................................................................................................................... 25-71 25-71 Description of the list of CES Transport Links ......................................................................................................... 25-72 25-72 View the details of CES Transport Link ...................................................................................................................... 25-73 25-73 Details of the CES Transport Link
................................................................................................................................ 25-74 25-74
Inventory from CES Transport Link ............................................................................................................................. 25-75 25-75 Inventory from CES Transport Link extremity ......................................................................................................... 25-76 25-76 View the list of CES PDH Ports ..................................................................................................................................... 25-78 25-78 Description of the list of CES PDH Ports ................................................................................................................... 25-79 25-79 View the details of CES PDH Port ................................................................................................................................ 25-82 25-82 Details of CES PDH Port .................................................................................................................................................. 25-83 25-83 Inventory from CES PDH Port List CES Edge Ports
....................................................................................................................................... 25-84 25-84
........................................................................................................................................................... 25-85 25-85
Description of the list of CES Port ................................................................................................................................ 25-86 25-86 View the details of CES Edge Port ................................................................................................................................ 25-87 25-87 Details of CES Port ............................................................................................................................................................. 25-88 25-88 Inventory from CES Edge Port ....................................................................................................................................... 25-89 25-89 View the list of CES Links Over Radio ....................................................................................................................... 25-90 25-90 Description of the list of CES Links Over Radio ..................................................................................................... 25-91 25-91 View the details of CES Link Over Radio .................................................................................................................. 25-92 25-92 Details of CES Link Over Radio .................................................................................................................................... 25-93 25-93 Inventory from CES Link Over Radio ......................................................................................................................... 25-94 25-94 Synchronization of CES Link Over Radio
................................................................................................................. 25-96 25-96
View the list of CES Radio Ports ................................................................................................................................... 25-97 25-97 Description of the list of CES Radio Ports ................................................................................................................. 25-98 25-98 View the details of CES Radio Port .............................................................................................................................. 25-99 25-99 .................................................................................................................................................................................................................................... 1350 OMS xxxviii 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Details of CES Radio Port .............................................................................................................................................. 25-100 25-100 Inventory from CES Radio Port ................................................................................................................................... 25-101 25-101 View the list of CES VLAN Paths
.............................................................................................................................. 25-102 25-102
Description of the list of CES VLAN Paths ............................................................................................................ 25-103 25-103 Join CES tunnels ................................................................................................................................................................ 25-104 25-104 Stitch CES tunnels
............................................................................................................................................................ 25-105 25-105
View the list of Circuit Emulation Services ............................................................................................................. 25-106 25-106 Description of the list of Circuit Emulation Services
.......................................................................................... 25-107 25-107
View the list of CES Terminations .............................................................................................................................. 25-114 25-114 Description of the list of CES Terminations ............................................................................................................ 25-115 25-115 Create Circuit Emulation Service ................................................................................................................................ 25-122 25-122 Inventory from CES Configure CES
........................................................................................................................................................ 25-126 25-126
.................................................................................................................................................................. 25-127 25-127
Routing display of CES ................................................................................................................................................... 25-130 25-130 Configure CES terminations
......................................................................................................................................... 25-131 25-131
Takeover procedure for MEF8 CES ........................................................................................................................... 25-132 25-132 Takeover procedure for SATOP CES ......................................................................................................................... 25-134 25-134
Part IV: Advanced Functions 26
TSS-320 versus TSS-40 with packet ring Overview
................................................................................................................................................................................... 26-1 26-1
Create T-MPLS Tunnel and PW (SNI) Create T-MPLS tunnel 320-40 (SNI) .............................................................................................................................. 26-2 26-2 Create T-MPLS PW 320-40 (SNI) ................................................................................................................................. 26-14 26-14 Create T-MPLS Tunnel and PW (DNI) Create T-MPLS tunnel 320-40 (DNI) ........................................................................................................................... 26-21 26-21 Create T-MPLS PW 320-40 (DNI) ................................................................................................................................ 26-33 26-33 Create EVC over T-MPLS 320-40 Create EVC over T-MPLS 320-40 ................................................................................................................................. 26-40 26-40 .................................................................................................................................................................................................................................... 1350 OMS xxxix 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Verify creation of EVC over T-MPLS 320-40 ........................................................................................................... 26-58 26-58 27
Performance Monitoring Overview
................................................................................................................................................................................... 27-1 27-1
PM in EVC create PM in EVC create
.................................................................................................................................................................. 27-2 27-2
Performance Monitoring activate PM activate ............................................................................................................................................................................... 27-7 27-7 PM consistency PM consistency ..................................................................................................................................................................... 27-12 27-12 PM Reports create PM Reports create
............................................................................................................................................................... 27-15 27-15
PM report generate PM report generate .............................................................................................................................................................. 27-19 27-19 28
Enhanced Procedures Overview
................................................................................................................................................................................... 28-1 28-1
TSS 5 In Band Management Overview
................................................................................................................................................................................... 28-3 28-3
T-MPLS Subnetwork topology .......................................................................................................................................... 28-4 28-4 In-band configuration
........................................................................................................................................................... 28-8 28-8
Resources reservation for In fiber Inband ................................................................................................................... 28-11 28-11 Ethernet Linear Protection Overview ................................................................................................................................................................................. 28-16 28-16 Link Over EVC ..................................................................................................................................................................... 28-18 28-18 Link over EVC: unlock EVC
.......................................................................................................................................... 28-20 28-20
Link over EVC creation ..................................................................................................................................................... 28-22 28-22 Link over EVC deletion ..................................................................................................................................................... 28-24 28-24 Link over EVC: Alarms ..................................................................................................................................................... 28-25 28-25 Link over EVC: OAM ........................................................................................................................................................ 28-26 28-26 .................................................................................................................................................................................................................................... 1350 OMS xl 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
Link over EVC: assign and deassign ............................................................................................................................ 28-27 28-27 Link over EVC: Transport Link configuration .......................................................................................................... 28-28 28-28 Link over EVC: activation and deactivation .............................................................................................................. 28-29 28-29 Link over EVC: Usage within an EVC
....................................................................................................................... 28-30 28-30
Link over EVC: AAR ......................................................................................................................................................... 28-31 28-31 Link over EVC: Routing Display
.................................................................................................................................. 28-32 28-32
Link over EVC: Inventory ................................................................................................................................................ 28-33 28-33 Ethernet Linear Protection (ELP)
.................................................................................................................................. 28-34 28-34
Add protection to PB EVC ............................................................................................................................................... 28-39 28-39 Remove protection from EVC
........................................................................................................................................ 28-41 28-41
Configure protection ........................................................................................................................................................... 28-42 28-42 ELP Protection properties
................................................................................................................................................ 28-43 28-43
Description of the properties
........................................................................................................................................... 28-44 28-44
Send APS command to protection group
.................................................................................................................... 28-45 28-45
Manual alignment of protection group ......................................................................................................................... 28-47 28-47 Implement a protected EVC ............................................................................................................................................. 28-48 28-48 Deimplement a protected EVC ....................................................................................................................................... 28-49 28-49 Disabled operations ............................................................................................................................................................. 28-50 28-50 Alarm propagation for protected EVCs ....................................................................................................................... 28-51 28-51 OAM on protected EVC .................................................................................................................................................... 28-52 28-52 Inventory of Transport Link from protected EVC ................................................................................................... 28-54 28-54 Inventory of MA from protected EVC ......................................................................................................................... 28-55 28-55 Routing Display of protected EVC A
............................................................................................................................... 28-56 28-56
Use script changeNeShOperatorLabel.sh Use the script changeNeShOperatorLabel.sh to change NEShOperator
B
............................................................ A-1 A-1
Application Limits Limits ............................................................................................................................................................................................ B-1 B-1
.................................................................................................................................................................................................................................... 1350 OMS xli 8DG42227DAAA 9.6 Issue 3 December 2012
Contents ....................................................................................................................................................................................................................................
C
List of Abbreviations Abbreviations
............................................................................................................................................................................ C-1 C-1
Index
.................................................................................................................................................................................................................................... 1350 OMS xlii 8DG42227DAAA 9.6 Issue 3 December 2012
List of tables
11-1
EVPL /ETS and ETB Provider Bridge .......................................................................................................... 11-16
11-2
EVPL /ETB Virtual Bridge
11-3
EVPL /ETB MAC Bridge .................................................................................................................................. 11-16
11-4
EPTL /ETS
11-5
EPTL /ETB Provider Bridge ............................................................................................................................. 11-17
11-6
EPTL /ETB Virtual Bridge
11-7
EPTL /ETB MAC Bridge
11-8
EPL /ETS and ETB Provider Bridge
11-9
EPL /ETB Virtual Bridge
.............................................................................................................................................................. 11-17 11-17
11-10 EPL /ETB MAC Bridge 11-11
............................................................................................................................... 11-16
................................................................................................................................ 11-17
.................................................................................................................................. 11-17 ............................................................................................................. 11-18
................................................................................................................................... 11-18
..................................................................................................................................... 11-18
EVPLAN /ETS and ETB Provider Bridge
11-12 EVPLAN /ETB Virtual Bridge 11-13 EVPLAN /ETB MAC Bridge
.................................................................................................. 11-19
........................................................................................................................ 11-19
.......................................................................................................................... 11-19
11-14 Extended EVPL /ETS and ETB Provider Bridge ...................................................................................... 11-20 11-15 Extended EVPL /ETB Virtual Bridge 11-16 Extended EVPL /ETB MAC Bridge
........................................................................................................... 11-20
.............................................................................................................. 11-20
11-17 Extended EVPLAN /ETS and ETB Provider Bridge 11-18 Extended EVPLAN /ETB Virtual Bridge 11-19 Extended EVPLAN /ETB MAC Bridge
.............................................................................. 11-21
.................................................................................................... 11-21
...................................................................................................... 11-21
11-20 HSI /ETS and ETB Provider Bridge .............................................................................................................. 11-22 11-21 HSI /ETS Multicast
.............................................................................................................................................. 11-23 11-23
11-22 HSI /ETB Virtual Bridge .................................................................................................................................... 11-23 .................................................................................................................................................................................................................................... 1350 OMS xliii 8DG42227DAAA 9.6 Issue 3 December 2012
List of tables ....................................................................................................................................................................................................................................
11-23 HSI /ETB MAC Bridge 11-24 BTV /ETS Multicast
...................................................................................................................................... 11-23
............................................................................................................................................ 11-24 11-24
11-25 BTV /ETB Provider Bridge 11-26 BTV /ETB Virtual Bridge 11-27 BTV /ETB MAC Bridge 11-28 Broadcast /ETS
.............................................................................................................................. 11-24
.................................................................................................................................. 11-25
.................................................................................................................................... 11-25
...................................................................................................................................................... 11-26 11-26
11-29 Broadcast /ETB Provider Bridge 11-30 Broadcast /ETB Virtual Bridge 11-31 Broadcast /ETB MAC Bridge
.................................................................................................................... 11-26
........................................................................................................................ 11-26
.......................................................................................................................... 11-26
13-1
Network Elements supporting the Link Aggregation ............................................................................ 13-114
15-1
MPLS traffic contract and traffic parameter dependencies
15-2
ISA boards and MPLS traffic parameter dependencies
18-1
Connection Oriented Service Type relations
18-2
Class of services and traffic parameters dependencies ......................................................................... 18-142
18-3
ISA boards and Ethernet traffic parameters dependencies .................................................................. 18-143
18-4
Allowed combination of Traffic Classification criteria ........................................................................ 18-156
19-1
L2 Control Protocols
19-2
Service Type, Type, Resource Sharing relations
22-1
ISA E/FE/GE alarms
22-2
ISA ES1/4 alarms or events ................................................................................................................................. 22-4
22-3
ISA ES16 alarms or events
22-4
SDH Path Alarm management
24-1
Terminology Mapping
25-1
Allowed interface type, depending on link technology
25-2
Relation between CES transport type and encapsulation type
25-3
CoS supported vs. T-MPLS PHB Profile
25-4
E1 service bandwidth occupation for MPR R1.3/R1.4 ........................................................................... 25-34
25-5
E1 service bandwidth occupation since MPR R2.1
25-6
MEF8 CES termination alarms ........................................................................................................................ 25-46
..................................................................... 15-8
............................................................................ 15-8
............................................................................................. 18-40
........................................................................................................................................... 19-16 ....................................................................................... 19-49
.............................................................................................................................................. 22-3 22-3
.................................................................................................................................. 22-6 ........................................................................................................................... 22-8
........................................................................................................................................... 24-4 .......................................................................... 25-25 ............................................................. 25-29
..................................................................................................... 25-29
................................................................................. 25-35
.................................................................................................................................................................................................................................... 1350 OMS xliv 8DG42227DAAA 9.6 Issue 3 December 2012
List of tables ....................................................................................................................................................................................................................................
25-7
SATOP CES termination alarms
25-8
Generic Tunnel attributes.
25-9
Packet Radio Tunnel attributes
..................................................................................................................... 25-48
................................................................................................................................. 25-55 ........................................................................................................................ 25-56
25-10 Generic Tunnel segment attributes 25-11 Generic Tunnel Xconn attributes 25-12 CE transport link attributes
................................................................................................................. 25-56
.................................................................................................................... 25-57
............................................................................................................................... 25-74
25-13 9500MPR PDH port attributes ......................................................................................................................... 25-79 25-14 TSS-5C PDH port attributes
............................................................................................................................. 25-80
25-15 The CES port attributes
...................................................................................................................................... 25-86
25-16 Ethernet port attributes
....................................................................................................................................... 25-88 25-88
25-17 Link over radio attributes ................................................................................................................................... 25-91 25-18 Link over radio attributes ................................................................................................................................... 25-93 25-19 radio port properties ............................................................................................................................................. 25-98 25-20 radio port properties
.......................................................................................................................................... 25-100
25-21 Generic CES attributes 25-22 MEF8 CES attributes
..................................................................................................................................... 25-108
........................................................................................................................................ 25-109
25-23 SATOP CES attributes
...................................................................................................................................... 25-110
25-24 Generic CES termination attributes 25-25 MEF8 CES termination attributes
............................................................................................................. 25-115
................................................................................................................ 25-116
25-26 SATOP CES termination attributes .............................................................................................................. 25-117 28-1
EVC attributes for ELP
...................................................................................................................................... 28-36
B-1
Limits for Subnetworks
.......................................................................................................................................... B-1
B-2
Limits for Service Nodes
B-3
Limits for Domains
B-4
Limits for NEs
B-5
Limits for ENEs
B-6
Limits for ETPs in an ENE
B-7
Limits for LSPs .......................................................................................................................................................... B-2 B-2
B-8
Limits for Customers ............................................................................................................................................... B-2 B-2
....................................................................................................................................... B-1
.................................................................................................................................................. B-1 B-1
........................................................................................................................................................... B-1 B-1 ........................................................................................................................................................ B-2 B-2 ................................................................................................................................... B-2
.................................................................................................................................................................................................................................... 1350 OMS xlv 8DG42227DAAA 9.6 Issue 3 December 2012
List of tables ....................................................................................................................................................................................................................................
B-9
Limits for Ethernet Services
................................................................................................................................. B-2
B-10
Limits for Ethernet Virtual Connections
B-11
Limits for Ethernet Transport Links
B-12
Limits for Ethernet Segments ............................................................................................................................... B-3
B-13
Limits for Ethernet edge physical ports ............................................................................................................ B-3
B-14
Limits for Ethernet Traffic Descriptors
............................................................................................................ B-3
B-15
Limits for Ethernet Traffic Classifiers
.............................................................................................................. B-3
B-16
Limits for Ethernet Color Profiles
B-17
Limits for Ethernet switches
B-18
Limits for VLAN Types
B-19
Limits for MPLS Transport Links
B-20
Limits for MPLS Traffic Descriptors
B-21
Limits for MPLS VC-LSPs
B-22
Limits for each board
.......................................................................................................... B-2
.................................................................................................................. B-2
...................................................................................................................... B-3
................................................................................................................................. B-3
......................................................................................................................................... B-4 ...................................................................................................................... B-4 ................................................................................................................ B-4
................................................................................................................................... B-4
.............................................................................................................................................. B-4 B-4
.................................................................................................................................................................................................................................... 1350 OMS xlvi 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures
4-1
Process Monitoring Window
................................................................................................................................. 4-2
11-1
Global Network view ............................................................................................................................................. 11-8
11-2
Example of Bundling ........................................................................................................................................... 11-12
11-3
Example of Service Multiplexing on UNI A
11-4
Point to Point Topology
11-5
Hub & spoke Topology ....................................................................................................................................... 11-32
11-6
Hub & spoke with multi level aggregation topology ............................................................................... 11-33
11-7
Full meshed topology
11-8
Ring Topology
11-9
Interface description
.............................................................................................. 11-14
...................................................................................................................................... 11-30
.......................................................................................................................................... 11-34
....................................................................................................................................................... 11-36 11-36 ............................................................................................................................................ 11-42 11-42
11-10 Ethernet Service delivered using different technologies 11-11
Inner ENE
........................................................................ 11-45
................................................................................................................................................................ 11-49 11-49
11-12 Customer Edge ....................................................................................................................................................... 11-50 11-50 11-13 Ethernet Frame Format
....................................................................................................................................... 11-54
11-14 Q-Tag Prefix Format ............................................................................................................................................ 11-55 11-15 Ethernet Frame Hierarchy
................................................................................................................................. 11-56
11-16 Customer VLAN Removal
................................................................................................................................ 11-59
11-17 Provider VLAN Removal
.................................................................................................................................. 11-60
11-18 Provider VLAN Addition ................................................................................................................................... 11-60 11-19 Provider VLAN Addition and Removal 11-20 Provider Tunneling Mode
....................................................................................................... 11-61
.................................................................................................................................. 11-61
11-21 Customer Tunneling Mode ................................................................................................................................ 11-62 .................................................................................................................................................................................................................................... 1350 OMS xlvii 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures ....................................................................................................................................................................................................................................
11-22 Protocol Type configuration for multiple destinations ............................................................................ 11-63 11-23 Low Cost solution ................................................................................................................................................. 11-63 11-63 11-24 Protocol Type configuration for single destination
.................................................................................. 11-64
12-1
Actions>Create Subnetwork
............................................................................................................................... 12-4
12-2
Create Subnetwork box ......................................................................................................................................... 12-5
12-3
Create Subnetwork: Assign Children Nodes ................................................................................................. 12-6
12-4
Node to assign to subnetwork ............................................................................................................................. 12-7
12-5
Confirm subnetwork creation
12-6
Subnetwork present in the map
12-7
Actions>Modify subnetwork ............................................................................................................................ 12-10
12-8
Modify subnetwork
12-9
Select the node to add
............................................................................................................................. 12-8 .......................................................................................................................... 12-9
.............................................................................................................................................. 12-11 ......................................................................................................................................... 12-12
12-10 Modify subn: adding a node
............................................................................................................................. 12-13
12-11 Actions>Physical>Create External Network .............................................................................................. 12-14 12-12 Create Ext Netw. dialog box ............................................................................................................................. 12-15 12-13 Actions>Modify subnetwork ............................................................................................................................ 12-16 12-14 Modify subnetwork .............................................................................................................................................. 12-17 12-15 Modify Subn box: new added node 12-16 New added node in the target map 12-17 Create>Physical Connection 12-18 Physcon create
............................................................................................................... 12-18
................................................................................................................. 12-19
............................................................................................................................ 12-20
....................................................................................................................................................... 12-21 12-21
12-19 Physcon create: port selection .......................................................................................................................... 12-22 12-20 Physcon list: Eth physcon defined .................................................................................................................. 12-23 12-21 Link over Cable list .............................................................................................................................................. 12-23 12-23 12-22 Actions>Packet>Construction>Create LAG Port ..................................................................................... 12-24 12-23 Create LAG Port
................................................................................................................................................... 12-25 12-25
12-24 LAG port and LAG port detail
........................................................................................................................ 12-26
12-25 Actions>Packet>Construction>Create Domain 12-26 Create Domain MAC-802.1D
........................................................................................ 12-27
.......................................................................................................................... 12-28
.................................................................................................................................................................................................................................... 1350 OMS xlviii 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures ....................................................................................................................................................................................................................................
12-27 Create Domain
....................................................................................................................................................... 12-29 12-29
12-28 Search>Packet>Construction>Domains
...................................................................................................... 12-29
12-29 Domain list .............................................................................................................................................................. 12-30 12-30 12-30 Search>Packet>Construction>Network Elements>Defined NEs ....................................................... 12-31 12-31 NE: Search>Ethernet Physical Ports 12-32 Eth Ports: the port is now busy
............................................................................................................. 12-32
........................................................................................................................ 12-32
12-33 LoC: Actions>Assign Resources to Domain 12-34 Assign Resources to Domain 12-35 Defined NEs list
.............................................................................................. 12-33
........................................................................................................................... 12-34
.................................................................................................................................................... 12-35 12-35
12-36 Port Administrative state=DOWN .................................................................................................................. 12-36 12-37 Actions>Packet>Construction>Define Network Element ..................................................................... 12-37 12-38 Define Network Element
................................................................................................................................... 12-38
12-39 Actions>Packet>Services>Create Traffic Descriptor .............................................................................. 12-40 12-40 Create Traffic Descriptor:Regulated
.............................................................................................................. 12-41
12-41 Create Traffic Descriptor: Best Effort
........................................................................................................... 12-42
12-42 Actions>Packet>Services>Create Traffic Classifier 12-43 Create Traffic Classifier 12-44 Traffic Classifier list
............................................................................... 12-43
..................................................................................................................................... 12-44 12-44
............................................................................................................................................ 12-45 12-45
12-45 Create T-MPLS Tunnel step1
........................................................................................................................... 12-47
12-46 Create T-MPLS Tunnel step2
........................................................................................................................... 12-48
12-47 Tunnel list
................................................................................................................................................................ 12-49 12-49
12-48 Tunnel:Search>T-MPLS Segments ................................................................................................................ 12-49 12-49 T-MPLS segment:Search>T-MPLS L2 Encapsulation Profiles ........................................................... 12-50 12-50 Default L2 Encapsulation profile .................................................................................................................... 12-50 12-51 Actions>Packet>T-MPLS>Create T-MPLS L2 Encapsulation Profile ............................................. 12-51 12-52 Create T-MPLS L2 Encapsulation Profile 12-53 L2 Encapsulation Profiles list
................................................................................................... 12-52
.......................................................................................................................... 12-53
12-54 T-MPLS Segment: Actions>Configure ......................................................................................................... 12-53 12-55 T-MPLS Segment configuration
..................................................................................................................... 12-54
.................................................................................................................................................................................................................................... 1350 OMS xlix 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures ....................................................................................................................................................................................................................................
12-56 Segment:Search>T-MPLS L2 Encapsulation Profiles
............................................................................ 12-55
12-57 L2 Encapsulation Profiles list
.......................................................................................................................... 12-55
12-58 Create T-MPLS Pseudo Wire
........................................................................................................................... 12-56
12-59 Create T-MPLS PW step2 12-60 PW list
................................................................................................................................. 12-57
...................................................................................................................................................................... 12-57 12-57
12-61 PW: Search>T-MPLS Segments
..................................................................................................................... 12-58
12-62 PW segment: Actions>Configur
..................................................................................................................... 12-58
12-63 T-MPLS Segment configuration box for PW 12-64 T-MPLS L2 Encapsulation Profiles for PW
............................................................................................. 12-59
............................................................................................... 12-59
12-65 Provider network operating as a distributed MAC Bridge
.................................................................... 12-67
12-66 Provider network operating as a distributed MAC Bridge
.................................................................... 12-68
12-67 Single-Customer, No-VLAN, RSTP-enabled
............................................................................................ 12-69
13-1
Subnetwork levels ................................................................................................................................................... 13-5 13-5
13-2
Subnetwork Creation window
13-3
Subnetwork Modification window
13-4
Domain management chain ............................................................................................................................... 13-16
13-5
Domain management chain ............................................................................................................................... 13-18
13-6
Define a Network Element ................................................................................................................................ 13-44
13-7
NE Adding window
13-8
Network Element Modification window ...................................................................................................... 13-50
13-9
Show Equipment View
............................................................................................................................ 13-9 ................................................................................................................. 13-11
............................................................................................................................................. 13-47
....................................................................................................................................... 13-71
13-10 ENE management chain
..................................................................................................................................... 13-79
13-11 External Network Element Creation window 13-12 ETP Creation window
............................................................................................ 13-83
......................................................................................................................................... 13-93
13-13 Ethernet Physical Port Config. window (for PR EA or ES16 electrical board) 13-14 Ethernet Physical Port Config. window (for ES1 or ES4 electrical board)
.......................... 13-101
.................................. 13-102
13-15 Ethernet Physical Port Config. window (for ES1 or ES4 optical board) ....................................... 13-103 13-16 Ethernet Physical Port Assign NAD window 13-17 Scheme of a Link Aggregation
.......................................................................................... 13-107
...................................................................................................................... 13-114
.................................................................................................................................................................................................................................... 1350 OMS l 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures ....................................................................................................................................................................................................................................
13-18 Jumbo frame configuration pattern .............................................................................................................. 13-135 13-19 Jumbo frame configuration pattern .............................................................................................................. 13-138 13-20 Create a port on 1678MCC NE ..................................................................................................................... 13-142 13-21 Remove port on 1678MCC NE ..................................................................................................................... 13-144 14-1
Link Over TDM between Q3 NEs
14-2
Link Over TDM between Q3 NE and SNMP NE
14-3
Link Over TDM between 2 SNMP NEs
14-4
Link Over Cable between SNMP NE and ENE ........................................................................................... 14-8
14-5
Link Over MPLS between 2 SNMP NEs
14-6
Link Over MPLS between SNMP NE and ENE based on VC-LSP
14-7
Network Element Supervision: Concatenated VC management
14-8
SDH Path Creation window .............................................................................................................................. 14-22
14-9
Link Over TDM Configuration window
14-10 Assign NAD window
.................................................................................................................... 14-6
......................................................................................................... 14-7
....................................................................................................... 14-9 .................................................. 14-10
......................................................... 14-11
...................................................................................................... 14-26
.......................................................................................................................................... 14-33
14-11 Link Over Cable Modification window 14-12 Link Over Cable Extremities window 14-13 Start Join window
....................................................................................... 14-6
....................................................................................................... 14-45
.......................................................................................................... 14-49
................................................................................................................................................. 14-53 14-53
14-14 Configure Split window
..................................................................................................................................... 14-55
14-15 Link Over Cable Creation window
................................................................................................................ 14-64
14-16 Link Over Cable Creation window
................................................................................................................ 14-67
14-17 Link VCG Creation window ............................................................................................................................. 14-70 14-18 LAG Link VCG Creation window
................................................................................................................. 14-73
15-1
Traffic Descriptor management chain
............................................................................................................. 15-5
15-2
Traffic Descriptor Creation window
15-3
Traffic Descriptor Modification window
15-4
MPLS Transport Link management chain ................................................................................................... 15-22
15-5
TL Characteristic Definition window (based on Link Over Cable)
15-6
TL Characteristic Definition window (based on Link Over TDM) .................................................... 15-27
15-7
Transport Link Extremities window
.............................................................................................................. 15-10 ..................................................................................................... 15-13
................................................... 15-26
.............................................................................................................. 15-29
.................................................................................................................................................................................................................................... 1350 OMS li 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures ....................................................................................................................................................................................................................................
15-8
Transport Link Over TDM Bandwidth Load window
............................................................................ 15-34
15-9
Transport Link Over Cable Bandwidth Load window ............................................................................ 15-35
15-10 Transport Link Inventory List window ......................................................................................................... 15-37 15-11 27 LSP Tunnel management chain
................................................................................................................. 15-40
15-12 LSP Tunnel Modification window (for an LSP tunnel defined) .......................................................... 15-46 15-13 Constraint List related to an LSP tunnel
...................................................................................................... 15-54
15-14 Add Constraint to an LSP tunnel window
................................................................................................... 15-57
15-15 LSP Tunnel Constraint Properties window 15-16 LSP Tunnel Implementation window 15-17 The LSP Tunnel Extremity window
................................................................................................. 15-61
............................................................................................................ 15-66
.............................................................................................................. 15-68
15-18 LSP Tunnel (Best Effort) Bandwidth Load window ................................................................................ 15-75 15-19 LSP Tunnel (Assured Forwarding) Bandwidth Load window
............................................................. 15-75
15-20 LSP Tunnel (Expedited Forwarding) Bandwidth Load window 15-21 LSP Tunnel Route window
......................................................... 15-76
............................................................................................................................... 15-78
15-22 VC-LSP management chain .............................................................................................................................. 15-82 15-23 VC-LSP Creation window ................................................................................................................................. 15-87 15-24 VC-LSP Modification window ........................................................................................................................ 15-90 15-25 VC-LSP Extremities window
........................................................................................................................ 15-100
16-1
T-MPLS Transport Link management chain
.............................................................................................. 16-15
16-2
Transport Link Extremities window
16-3
Transport Link Over TDM Bandwidth Load window
16-4
Transport Link Over Cable Bandwidth Load window ............................................................................ 16-27
16-5
Transport Link Inventory List window ......................................................................................................... 16-29
16-6
Layering
16-7
Tunnel entities ........................................................................................................................................................ 16-91 16-91
16-8
PW entities
16-9
DH EVPLINE infrastructure
.............................................................................................................. 16-21 ............................................................................ 16-26
................................................................................................................................................................... 16-90 16-90
.............................................................................................................................................................. 16-92 16-92 ........................................................................................................................... 16-95
16-10 Tunnel MAIN: Actions>T-MPLS Tunnel Protection Management ................................................. 16-141 16-11 T-MPLS Tunnel Protection Management .................................................................................................. 16-142 .................................................................................................................................................................................................................................... 1350 OMS lii 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures ....................................................................................................................................................................................................................................
16-12 T-MPLS tunnel list
............................................................................................................................................ 16-143 16-143
16-13 T-MPLS tunnel: Search>Routing display
................................................................................................. 16-143
16-14 Search>Packet>T-MPLS>T-MPLS>Tunnels ........................................................................................... 16-144 16-15 T-MPLS tunnel: Actions menu ...................................................................................................................... 16-145 16-16 T-MPLS tunnel: Search>Routing display 16-17 T-MPLS Protection Group 16-18 Tunnel Switch: Actions
................................................................................................. 16-146
.............................................................................................................................. 16-147
.................................................................................................................................... 16-148
16-19 Tunnel:Actions>Remove Protection(keeping Main)
............................................................................ 16-149
16-20 Spare tunnel routing display ........................................................................................................................... 16-149 16-21 Don't care protection role and protection state 16-22 Main tunnel routing display
........................................................................................ 16-150
........................................................................................................................... 16-151
16-23 T-MPLS Node PHB Profile ............................................................................................................................ 16-152 16-24 T-MPLS Node Traffic Descriptor ................................................................................................................. 16-153 16-25 T-MPLS Segment ............................................................................................................................................... 16-154 16-26 T-MPLS Port
........................................................................................................................................................ 16-155 16-155
16-27 Tunnel Redundancy Reference network
.................................................................................................... 16-166
17-1
Physical map
............................................................................................................................................................. 17-3 17-3
17-2
Search>Packet>Construction>Network Elements>Defined NEs
17-3
NE: Search>Ethernet Physical Ports ................................................................................................................ 17-4
17-4
Ethernet Physical Ports
17-5
Create Physcon-basic ............................................................................................................................................. 17-6 17-6
17-6
Create Physcon: End Points
17-7
Physcon list
17-8
Search>Packet>Construction>Transport Links>Link over Cable
17-9
Link over Cable list
......................................................... 17-4
......................................................................................................................................... 17-5 17-5
................................................................................................................................ 17-7
............................................................................................................................................................... 17-8 17-8 ........................................................ 17-8
................................................................................................................................................ 17-9 17-9
17-10 Actions>Packet>Construction>Create Link over Cable ........................................................................... 17-9 17-11 Create Link over Cable ....................................................................................................................................... 17-10 17-12 Actions>Assign Resources to Domain
......................................................................................................... 17-11
17-13 Assign Resources to Domain box ................................................................................................................... 17-12 .................................................................................................................................................................................................................................... 1350 OMS liii 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures ....................................................................................................................................................................................................................................
17-14 Search>Packet>T-MPLS>T-MPLS Sections .............................................................................................. 17-13 17-15 T-MPLS Section list
............................................................................................................................................ 17-13 17-13
17-16 Actions>Packet>T-MPLS>Create T-MPLS tunnel 17-17 Create T-MPLS tunnel:Constraints
................................................................................................................ 17-15
17-18 Create T-MPLS tunnel: Quality of Service 17-19 Create T-MPLS tunnel: OAM
.................................................................................. 17-14
................................................................................................. 17-16
.......................................................................................................................... 17-17
17-20 Create T-MPLS tunnel: Protection
................................................................................................................. 17-18
17-21 Search>Packet>T-MPLS>T-MPLS Tunnels ............................................................................................... 17-19 17-22 Tunnel list
................................................................................................................................................................ 17-19 17-19
17-23 Actions>Implement T-MPLS Tunnel 17-24 The tunnel is implemented
............................................................................................................ 17-20
................................................................................................................................ 17-20
17-25 Actions>Packet>T-MPLS>Create T-MPLS Pseudo Wire 17-26 Create T-MPLS Pseudo Wire: Constraints
..................................................................... 17-21
.................................................................................................. 17-22
17-27 Create T-MPLS Pseudo Wire: Quality of Service
.................................................................................... 17-23
17-28 Search>Packet>T-MPLS>T-MPLS Pseudo Wire
..................................................................................... 17-24
17-29 T-MPLS Pseudo Wires ........................................................................................................................................ 17-24 17-30 PW Implementation
............................................................................................................................................. 17-25 17-25
17-31 T-MPLS Pseudo wire implemented
............................................................................................................... 17-25
17-32 Search>Packet>Services>T-MPLS>T-MPLS Transport Links 17-33 T-MPLS Transport Links
........................................................... 17-26
................................................................................................................................... 17-26
17-34 Actions>Packet>Services>T-MPLS>Create T-MPLS EVC
................................................................. 17-34
17-35 Create T-MPLS EVC: Specific ........................................................................................................................ 17-36 17-36 Create T-MPLS EVC: Detail 17-37 Create T-MPLS EVC: PM
............................................................................................................................ 17-37
................................................................................................................................. 17-38
17-38 Create T-MPLS EVC: Terminations Selection 17-39 Terminations Selection
.......................................................................................... 17-39
....................................................................................................................................... 17-40 17-40
17-40 Termination Settings ............................................................................................................................................ 17-42 17-42 17-41 Ingress flow create
............................................................................................................................................... 17-44 17-44
17-42 Ingress Flow: create monitoring ...................................................................................................................... 17-45 .................................................................................................................................................................................................................................... 1350 OMS liv 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures ....................................................................................................................................................................................................................................
17-43 Egress Flow: Push
................................................................................................................................................ 17-47 17-47
17-44 Create Egress monitoring
.................................................................................................................................. 17-48
17-45 Create Ingress node A
......................................................................................................................................... 17-49
17-46 Create Egress node A
.......................................................................................................................................... 17-50
17-47 Transport Link selection
.................................................................................................................................... 17-51
17-48 Select the transport link
...................................................................................................................................... 17-52
17-49 Pseudo Wire selected ........................................................................................................................................... 17-53 17-53 17-50 T-MPLS EVC Allocate and Implement
........................................................................................................ 17-54
17-51 EVPL reference network .................................................................................................................................... 17-55 17-52 Actions>Packet>Services>Create Traffic Descriptor .............................................................................. 17-56 17-53 Create Traffic Descriptor
................................................................................................................................... 17-57
17-54 Actions>Packet>Services>T-MPLS>Create T-MPLS EVC
................................................................. 17-58
17-55 Create T-MPLS EVC: Specific ........................................................................................................................ 17-59 17-56 Terminations Selection 17-57 Ingress Flow: create 17-58 Egress Flow: Push
....................................................................................................................................... 17-61 17-61
............................................................................................................................................. 17-63 17-63
................................................................................................................................................ 17-65 17-65
17-59 Transport Link selection
.................................................................................................................................... 17-67
17-60 Search>Packet>T-MPLS>T-MPLS Pseudo Wires
................................................................................... 17-68
17-61 PW list before EVC TD create ......................................................................................................................... 17-68 17-62 T-MPLS EVC Allocate and Implement 17-63 PW list after EVC TD create
........................................................................................................ 17-69
............................................................................................................................ 17-70
17-64 Search>Packet>T-MPLS>T-MPLS EVCs ................................................................................................... 17-70 17-65 EVC list: EVPL EVC allocate
......................................................................................................................... 17-71
17-66 EVC goes implemented ...................................................................................................................................... 17-71 17-67 EVPLAN reference network (3-nodes)
........................................................................................................ 17-72
17-68 EVPLAN network (4-nodes) ............................................................................................................................ 17-73 17-69 Create T-MPLS EVC: Specific ........................................................................................................................ 17-75 17-70 Terminations Selection
....................................................................................................................................... 17-77 17-77
17-71 EVPLAN: Ingress Flow: create ....................................................................................................................... 17-79 .................................................................................................................................................................................................................................... 1350 OMS lv 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures ....................................................................................................................................................................................................................................
17-72 EVPLAN:Egress Flow
....................................................................................................................................... 17-81
17-73 Transport Link selection
.................................................................................................................................... 17-83
17-74 T-MPLS EVC Allocate and Implement 17-75 PW list after EVC TD create
........................................................................................................ 17-84
............................................................................................................................ 17-85
17-76 EVC goes implemented ...................................................................................................................................... 17-85 17-77 BTV reference network
..................................................................................................................................... 17-86
17-78 HSI reference network
....................................................................................................................................... 17-90
17-79 T-MPLS EVC list: Availability ........................................................................................................................ 17-94 17-80 EVC: Search>Fault Localization
.................................................................................................................... 17-95
17-81 Navigation to Transport Section ...................................................................................................................... 17-95 17-82 Navigate to Link over Cable ............................................................................................................................. 17-96 17-83 Search>Packet>Services>T-MPLS>T-MPLS EVCs 17-84 T-MPLS EVC:Actions>Deimplement 17-85 T-MPLS EVC:Actions>Deallocate
............................................................................... 17-98
.......................................................................................................... 17-99
................................................................................................................ 17-99
17-86 T-MPLS EVC: Search>T-MPLS Transport Links
................................................................................. 17-100
17-87 T-MPLS Transport Links ................................................................................................................................. 17-100 17-88 Search>Packet>T-MPLS>T-MPLS Pseudo Wires ................................................................................. 17-101 17-89 T-MPLS Pseudo Wire: Search>T-MPLS Tunnels
.................................................................................. 17-102
17-90 T-MPLS Tunnel: Search>T-MPLS Protection Involved Tunnel ....................................................... 17-103 17-91 T-MPLS Tunnel Routing Display
................................................................................................................ 17-103
17-92 Tunnel spare: Actions>Remove Protection keeping Main .................................................................. 17-104 17-93 Routing Display after Remove Protection 17-94 Tunnel: Search>T-MPLS Pseudo Wires
................................................................................................ 17-104
.................................................................................................... 17-105
17-95 T-MPLS EVC: Actions>Delete ..................................................................................................................... 17-105 17-96 EVC deletion evidence ..................................................................................................................................... 17-106 17-97 Pseudo Wires: Actions>Deimplement 17-98 Pseudo Wires: Actions>Delete 17-99 Delete Tunnel SPARE
........................................................................................................ 17-106
...................................................................................................................... 17-107
...................................................................................................................................... 17-107
17-100 Tunnel: Search>T-MPLS Section List ........................................................................................................ 17-108 .................................................................................................................................................................................................................................... 1350 OMS lvi 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures ....................................................................................................................................................................................................................................
17-101 Tunnel related Section
...................................................................................................................................... 17-108
17-102 Delete T-MPLS tunnel ...................................................................................................................................... 17-109 17-103 Tunnel deletion evidence ................................................................................................................................. 17-109 17-104 Deassign LoC from Domain 17-105 Field Domain is deleted
.......................................................................................................................... 17-110
................................................................................................................................... 17-110
17-106 The associated Section is automatically deleted
..................................................................................... 17-111
17-107 Defined Node: Search>Ethernet Physical Ports
...................................................................................... 17-111
17-108 Deassign UNI port from the domain 17-109 Field domain is empty
........................................................................................................... 17-112
...................................................................................................................................... 17-112
17-110 Delete the NE ....................................................................................................................................................... 17-113 17-113 17-111 Search>Packet>Services>T-MPLS>T-MPLS EVCs ............................................................................. 17-114 17-112 T-MPLS EVCs
.................................................................................................................................................... 17-115 17-115
17-113 Allocate the EVC ................................................................................................................................................ 17-115 17-115 17-114 Implement the EVC
........................................................................................................................................... 17-116 17-116
18-1
Ethernet service containment tree ................................................................................................................... 18-19
18-2
EVPL/EPTL/EPL/Extended EVPL service creation wizard
18-3
Ethernet Service Properties window .............................................................................................................. 18-34
18-4
EVCs and Edge Ports relationships
18-5
EVC Modification window ............................................................................................................................... 18-48
18-6
EVC Properties window ..................................................................................................................................... 18-52
18-7
EVC Termination Properties window
18-8
Add EVC Termination window
18-9
Network schema for E2E connection
................................................................ 18-26
............................................................................................................... 18-38
........................................................................................................... 18-64
....................................................................................................................... 18-67 ............................................................................................................ 18-91
18-10 Search>Packet>Construction>Transport Links>Links over TDM(Sdh/Sonet) ............................. 18-93 18-11 Links over TDM(Sdh/Sonet)
............................................................................................................................ 18-94
18-12 Search>Packet>Construction>Network Elements>Defined NEs ....................................................... 18-94 18-13 Defined NE:Search>Ethernet Physical Ports 18-14 Port:Actions>Assign Resource to Domain 18-15 ETS Domain selection
............................................................................................. 18-95
................................................................................................. 18-95
........................................................................................................................................ 18-96
.................................................................................................................................................................................................................................... 1350 OMS lvii 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures ....................................................................................................................................................................................................................................
18-16 Assign port to ETS domain ............................................................................................................................... 18-97 18-17 Link over TDM (path): Actions>Assign Resources to Domain
.......................................................... 18-98
18-18 Select ETS domain ............................................................................................................................................... 18-98 18-98 18-19 Confirm the assignment
..................................................................................................................................... 18-99
18-20 Search>Packet>Services>Connection Oriented>ETS Transport Link ........................................... 18-100 18-21 Path commissioning
.......................................................................................................................................... 18-100
18-22 Path included in the Links over TDM 18-23 Transport Links
........................................................................................................ 18-101
................................................................................................................................................... 18-101 18-101
18-24 Port: Assign resources to Domain
................................................................................................................ 18-103
18-25 Assign resources to Domain ........................................................................................................................... 18-104 18-26 Search>Packet>Services>T-MPLS>T-MPLS Edge Ports ................................................................... 18-105 18-27 UNI ports became edge ports
........................................................................................................................ 18-105
18-28 Actions>Packet>Services>Connection Oriented(ETS)>Create EVC 18-29 EVC over SDH: EVC definition 18-30 Far end edge port selection
............................................ 18-106
.................................................................................................................. 18-107
............................................................................................................................. 18-108
18-31 Ethernet Segments definition ......................................................................................................................... 18-109 18-32 Search>Packet>Services>Connection Oriented(ETS) 18-33 ETS EVCs
......................................................................... 18-110
............................................................................................................................................................. 18-110 18-110
18-34 ETS EVC: Search>Ethernet Segments ....................................................................................................... 18-111 18-35 Ethernet segment list
......................................................................................................................................... 18-111 18-111
18-36 Actions>Add Constraints to an Ethernet Service 18-37 Add Constraints to an Ethernet Service
................................................................................... 18-112
..................................................................................................... 18-113
18-38 Segment:Actions>Associate to Traffic Classifier ................................................................................... 18-114 18-39 Traffic Classifier list .......................................................................................................................................... 18-114 18-114 18-40 Associate Traffic Classifier ............................................................................................................................. 18-115 18-41 Allocate the segment
......................................................................................................................................... 18-116 18-116
18-42 Implement the segment
.................................................................................................................................... 18-116
18-43 Both segments are implemented 18-44 EVC-ETS implemented
................................................................................................................... 18-117
................................................................................................................................... 18-117
.................................................................................................................................................................................................................................... 1350 OMS lviii 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures ....................................................................................................................................................................................................................................
18-45 T-MPLS EVC list: Availability
..................................................................................................................... 18-118
18-46 EVC: Search>Fault Localization .................................................................................................................. 18-119 18-47 Navigation to Transport Section 18-48 Navigate to Link over Cable 18-49 Create Domain 18-50 Define NE
................................................................................................................... 18-119
.......................................................................................................................... 18-120
.................................................................................................................................................... 18-123 18-123
............................................................................................................................................................. 18-124 18-124
18-51 Create EVC
.......................................................................................................................................................... 18-125 18-125
18-52 Align Up window ............................................................................................................................................... 18-127 18-53 Enable Takeover
................................................................................................................................................. 18-128 18-128
18-54 Color Profile Modification window 18-55 Color Profile Properties window
............................................................................................................ 18-137
.................................................................................................................. 18-141
18-56 Traffic Descriptor Modification window ................................................................................................... 18-150 18-57 Traffic Descriptor (Ethernet Management) Properties window 18-58 Traffic Classifier Modification window 18-59 Traffic Classifier Properties window
........................................................ 18-154
.................................................................................................... 18-163
.......................................................................................................... 18-166
18-60 Edge Port Modification window ................................................................................................................... 18-171 18-61 Edge Port Configuration window ................................................................................................................. 18-173 18-62 Edge Port Properties window 18-63 Show Equipment window
........................................................................................................................ 18-176
............................................................................................................................... 18-181
18-64 Transport Link Extremities window ............................................................................................................ 18-191 18-65 Transport Link Properties window
.............................................................................................................. 18-194
18-66 Ethernet Segment representation
.................................................................................................................. 18-197
18-67 Ethernet Segment representation
.................................................................................................................. 18-200
18-68 Ethernet Segment Modification window
................................................................................................... 18-206
18-69 Traffic Classifier Association (to an Ethernet Segment) window
.................................................... 18-210
18-70 Traffic Classifier disassociation (from an Ethernet Segment) window 18-71 Add Constraint to an Ethernet Segment window (Pop) 18-72 Ethernet Segment constraint properties window
.......................................... 18-212
....................................................................... 18-214
.................................................................................... 18-220
18-73 Constraint Modification window .................................................................................................................. 18-223 .................................................................................................................................................................................................................................... 1350 OMS lix 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures ....................................................................................................................................................................................................................................
18-74 Ethernet Segment Configuration window 18-75 Ethernet Segment Extremities window
................................................................................................. 18-234
...................................................................................................... 18-236
18-76 Ethernet Segment Extremity Modification window (Origin)
............................................................ 18-237
18-77 Ethernet Segment Extremity Modification window (Destination) 18-78 Route Display - Ethernet Segment window
............................................................................................. 18-243
18-79 Connectivity view - Ethernet Segment window 18-80 VLAN Type Creation window
.................................................. 18-238
..................................................................................... 18-245
...................................................................................................................... 18-249
18-81 VLAN Type Modification window
............................................................................................................. 18-252
19-1
Connection Less Transport Link List
............................................................................................................ 19-28
19-2
Transport Link Configuration window
19-3
Transport Link Extremities window
19-4
Transport Link Properties window ................................................................................................................. 19-39
19-5
EVC Modification window (Details)
19-6
EVC Properties window ..................................................................................................................................... 19-59
19-7
EVC Fault Localization window
19-8
Show Equipment from EVC Fault Localization
19-9
AS window for EVC Alarms ............................................................................................................................ 19-71
......................................................................................................... 19-32
.............................................................................................................. 19-35
............................................................................................................ 19-54
.................................................................................................................... 19-66 ....................................................................................... 19-67
19-10 Add EVC termination window (General Panel) ........................................................................................ 19-75 19-11 Add EVC termination window (Egress Flow)
........................................................................................... 19-78
19-12 Add EVC termination window (L2 Control Protocol Panel)
............................................................... 19-80
19-13 EVC Termination Configuration window .................................................................................................... 19-84 19-14 EVC Termination Properties window
........................................................................................................... 19-86
19-15 Provider Domain Configuration window
.................................................................................................... 19-95
19-16 Domain Modification window ......................................................................................................................... 19-97 19-17 Network Element Configure window
........................................................................................................... 19-99
19-18 Client Type Selection ........................................................................................................................................ 19-101 19-101 19-19 Ethernet Physical Port
...................................................................................................................................... 19-102
19-20 Ethernet Physical Port Configuration window
........................................................................................ 19-103
19-21 Customer Creation window ............................................................................................................................ 19-105 .................................................................................................................................................................................................................................... 1350 OMS lx 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures ....................................................................................................................................................................................................................................
19-22 Spanning Tree Instance Configuration window ...................................................................................... 19-122 20-1
PBB EVC provisioning ......................................................................................................................................... 20-8
20-2
Actions>Packet>Construction>Create Domain
20-3
Create PBB Domain
20-4
Search>Packet>Construction>Network Elements>Available NEs
20-5
Available NE: Actions>Define Network Element
20-6
Define Network Element dialog box
20-7
Defined NE list
20-8
Show Equipment view
20-9
Show Equipment: select the termination
20-10 Module setting
........................................................................................ 20-12
............................................................................................................................................ 20-13 20-13 .................................................... 20-14
.................................................................................... 20-15
............................................................................................................. 20-15
...................................................................................................................................................... 20-16 20-16 ....................................................................................................................................... 20-17 ..................................................................................................... 20-18
....................................................................................................................................................... 20-18 20-18
20-11 Show Equipment view of the terminating NE
........................................................................................... 20-19
20-12 Node: Actions>Physical>Synchronize>Synchronize NE 20-13 Actions>Physical>Create Physical Connection 20-14 Create Physical Connection
...................................................................... 20-19
....................................................................................... 20-21
.............................................................................................................................. 20-22
20-15 Create> Physical Connection step2
............................................................................................................... 20-23
20-16 Search>Packet>Construction>Transport Links>Links over Cable .................................................... 20-24 20-17 Links over Cable list ............................................................................................................................................ 20-25 20-25 20-18 Link over Cable: Actions>Assign Resources to Domain ....................................................................... 20-25 20-19 Assign Resources to Domain
........................................................................................................................... 20-26
20-20 Link over Cable list .............................................................................................................................................. 20-27 20-27 20-21 Link over Cable:Actions>Delete
.................................................................................................................... 20-28
20-22 Physical Connection:Actions>Remove
........................................................................................................ 20-28
20-23 Actions>Packet>ERP>Create ERP Ring 20-24 Create ERP Ring
..................................................................................................... 20-30
................................................................................................................................................... 20-31 20-31
20-25 Bridge Transport Links ....................................................................................................................................... 20-32 20-26 Create ERP Ring
................................................................................................................................................... 20-33 20-33
20-27 Search>Packet>ERP>Rings 20-28 List of ERP Rings
............................................................................................................................. 20-34
................................................................................................................................................. 20-34 20-34
.................................................................................................................................................................................................................................... 1350 OMS lxi 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures ....................................................................................................................................................................................................................................
20-29 ERP ring: Actions>Implement ERP Ring 20-30 ERP Ring implemented
.................................................................................................... 20-35
...................................................................................................................................... 20-35
20-31 ERP Ring:Search>Nodes
................................................................................................................................... 20-36
20-32 Nodes belonging to the ring .............................................................................................................................. 20-36 20-33 ERP Ring:Search>Physical Links
.................................................................................................................. 20-36
20-34 Physcons belonging to the ring ........................................................................................................................ 20-37 20-35 ERP ring: Search>ERP Instances 20-36 Search of the ERP instances
................................................................................................................... 20-38
............................................................................................................................. 20-39
20-37 PBB domain:Search>ERP Instances
............................................................................................................. 20-39
20-38 Actions>Packet>ERP>Create ERP Instance 20-39 Create ERP Instance: General 20-40 Create ERP Instance: Timers
.............................................................................................. 20-40
.......................................................................................................................... 20-41
............................................................................................................................ 20-42
20-41 Create ERP Instance: Failures .......................................................................................................................... 20-43 20-42 Create ERP Instance
............................................................................................................................................ 20-44 20-44
20-43 ERP Instance: Actions>Implement ERP Instance
.................................................................................... 20-44
20-44 Actions>Packet>Services>ConnectionLess(Bridge)>Create B-VID ................................................ 20-46 20-45 Create B-VID wizard step1 ............................................................................................................................... 20-47 20-46 B-VID:Transport Links selection 20-47 Create B-VID 20-48 B-VID list
................................................................................................................... 20-48
......................................................................................................................................................... 20-49 20-49
................................................................................................................................................................ 20-50 20-50
20-49 B-VID: Actions>Implement
............................................................................................................................. 20-50
20-50 B-VID partially implemented (few secs)
..................................................................................................... 20-51
20-51 MIP creation policy .............................................................................................................................................. 20-53 20-53 20-52 Traffic Descriptor create step1 ......................................................................................................................... 20-54 20-53 Traffic Descriptor create step2 ......................................................................................................................... 20-55 20-54 EVC Termination list ........................................................................................................................................... 20-56 20-56 20-55 Actions> Add Connection Less EVC Termination
.................................................................................. 20-57
20-56 Add Connection Less EVC Termination dialog box 20-57 The new termination has been added
............................................................................... 20-58
............................................................................................................ 20-58
.................................................................................................................................................................................................................................... 1350 OMS lxii 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures ....................................................................................................................................................................................................................................
20-58 ERP Graphical View example
....................................................................................................................... 20-128
20-59 Create PBB EVC: Termination Selection .................................................................................................. 20-146 20-60 Create PBB EVC: Termination Settings 20-61 Ingress flow create
.................................................................................................... 20-147
............................................................................................................................................. 20-148 20-148
20-62 Ingress Flow: create monitoring
................................................................................................................... 20-149
20-63 Egress Flow: Push .............................................................................................................................................. 20-150 20-64 EVC Allocate and Implement ........................................................................................................................ 20-151 20-65 Search>Packet>Connection Less(Bridge)>Bridge EVC
..................................................................... 20-152
20-66 Bridge EVC list ................................................................................................................................................... 20-152 20-152 20-67 TSS160C System ID Configuration
............................................................................................................ 20-157
20-68 TSS160C System ID Configuration form
................................................................................................. 20-158
20-69 TSS160C Q LAN Configuration (Gateway NE)
.................................................................................... 20-159
20-70 TSS160C Export of the Route ....................................................................................................................... 20-160 20-71 Tss160C OSI Routing Configuration .......................................................................................................... 20-161 20-72 TSS10 System ID Configuration .................................................................................................................. 20-162 20-73 TSS10 System IP Address ............................................................................................................................... 20-163 20-74 Tss10 LAN Interface Details .......................................................................................................................... 20-164 20-75 TSS160C Link Aggregation Group Management 20-76 Tss160C LAG Configuration (Client Type)
.................................................................................. 20-166
............................................................................................. 20-167
20-77 Tss160C LAG Configuration (Administration State) 20-78 Tss160C In Fiber In Band
.......................................................................... 20-168
............................................................................................................................... 20-169
20-79 Tss160C In Fiber In Band (OSPF) ............................................................................................................... 20-170 20-80 Tss160C In Fiber In Band Activate
............................................................................................................. 20-171
20-81 Tss160C port member of LAG ...................................................................................................................... 20-172 20-82 Tss160C port member of LAG configuration 20-83 Tss160C port member of LAG Actor
.......................................................................................... 20-173
......................................................................................................... 20-174
20-84 TSS10 Link Aggregation Group Management ........................................................................................ 20-176 20-85 Tss10 Enable the In Band Management ..................................................................................................... 20-177 20-86 TSS60 In Fiber In Band Configuration
...................................................................................................... 20-178
.................................................................................................................................................................................................................................... 1350 OMS lxiii 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures ....................................................................................................................................................................................................................................
20-87 Tss10 portInLAG ................................................................................................................................................ 20-179 20-88 Tss10 port member of LAG configuration ................................................................................................ 20-180 20-89 Tss10_portInLAGconfigActor 20-90 Tss10_portInLAGadminState 20-91 NMS Start Supervision 20-92 NMS Synchronize NE
...................................................................................................................... 20-181
........................................................................................................................ 20-182
.................................................................................................................................... 20-183
...................................................................................................................................... 20-184
20-93 NMS add Node In Map .................................................................................................................................... 20-185 20-94 NMS Create Physical Connection ................................................................................................................ 20-186 20-95 NMS Create Physical Connection wizard ................................................................................................. 20-187 20-96 NMS Define NE
................................................................................................................................................. 20-188
20-97 NMS Ethernet Physical Port list
................................................................................................................... 20-189
20-98 Create LAG Link over Cable ......................................................................................................................... 20-190 20-99 Create Link Over Cable
................................................................................................................................... 20-191
20-100 NMS Link Over LAG list
............................................................................................................................... 20-192
21-1
BTV Element management chain
..................................................................................................................... 21-5
21-2
Broadcast TV Element List window
21-3
Broadcast TV Element Creation window ....................................................................................................... 21-9
21-4
External Network Element Modification window .................................................................................... 21-12
21-5
ETP Creation window
21-6
Path on 1350 OMS SDH .................................................................................................................................... 21-25
21-7
Broadcast TV Element Creation window
21-8
Link Over TDM Broadcast TV Creation window
21-9
1350 OMS SDH Path Id ..................................................................................................................................... 21-31
................................................................................................................ 21-7
......................................................................................................................................... 21-21
21-10 Create Ethernet Service
.................................................................................................... 21-27 .................................................................................... 21-30
...................................................................................................................................... 21-36 21-36
21-11 EVC Any to any Creation window ................................................................................................................. 21-38 22-1
Alarm status management
................................................................................................................................. 22-10
22-2
Alarm correlation
25-1
Mobile back-hauling scenario
25-2
Network layers in case of unterminated CE service ................................................................................... 25-5
.................................................................................................................................................. 22-11 22-11 ............................................................................................................................ 25-4
.................................................................................................................................................................................................................................... 1350 OMS lxiv 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures ....................................................................................................................................................................................................................................
25-3
Transport Layer representation
.......................................................................................................................... 25-6
25-4
CES 9500 MPR Protection schemes
25-5
CES Relation between CAC tolerance and modulation mode
25-6
Horizontal and vertical alarm correlation in Packet Radio domain
25-7
Horizontal and vertical alarm correlation in T-MPLS domain ............................................................. 25-22
25-8
CES after join ......................................................................................................................................................... 25-28 25-28
25-9
CES after stich
............................................................................................................. 25-10 ............................................................. 25-11 ................................................... 25-17
....................................................................................................................................................... 25-28 25-28
25-10 CES routing display
............................................................................................................................................ 25-31
25-11 Tunnel routing display
........................................................................................................................................ 25-32
25-12 SNMP MIB relationships between E1 and PW tables
............................................................................ 25-36
26-1
Reference Network
................................................................................................................................................. 26-2 26-2
26-2
Actions>Packet>T-MPLS>Create T-MPLS tunnel
26-3
Create T-MPLS tunnel ........................................................................................................................................... 26-4 26-4
26-4
Point to point Packet Ring bidir protected T-MPLS tunnel
26-5
Selection of the port
26-6
Select the second extremity (node) ................................................................................................................... 26-7
26-7
P2P bid prot T-MPLS tunnel: selected extremities
26-8
P2P: constraint
26-9
P2P bid prot T-MPLS tunnel: selected extremities and constraint
..................................................................... 26-5
............................................................................................................................................... 26-6 26-6
..................................................................................... 26-8
......................................................................................................................................................... 26-9 26-9
26-10 Search>Packet>T-MPLS>T-MPLS Tunnels 26-11 Tunnel list
.................................................................................... 26-3
..................................................... 26-10
............................................................................................... 26-11
................................................................................................................................................................ 26-12 26-12
26-12 Actions>Implement T-MPLS Tunnel 26-13 The tunnel is implemented
............................................................................................................ 26-12
................................................................................................................................ 26-13
26-14 Actions>Packet>T-MPLS>Create T-MPLS Pseudo Wire 26-15 Create T-MPLS Pseudo Wire
..................................................................... 26-14
........................................................................................................................... 26-15
26-16 Point to Point Bidirectional T-MPLS PW .................................................................................................... 26-17 26-17 Search>Packet>T-MPLS>T-MPLS Pseudo Wire
..................................................................................... 26-18
26-18 T-MPLS Pseudo Wires ........................................................................................................................................ 26-18 26-19 PW Implementation
............................................................................................................................................. 26-19 26-19
.................................................................................................................................................................................................................................... 1350 OMS lxv 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures ....................................................................................................................................................................................................................................
26-20 T-MPLS Pseudo wire implemented 26-21 Reference Network
............................................................................................................... 26-19
.............................................................................................................................................. 26-21 26-21
26-22 Actions>Packet>T-MPLS>Create T-MPLS tunnel 26-23 Create T-MPLS tunnel
.................................................................................. 26-22
........................................................................................................................................ 26-23
26-24 Point to point Packet Ring bidir protected T-MPLS tunnel open sink
.............................................. 26-24
26-25 Selection of the port ............................................................................................................................................. 26-25 26-25 26-26 Select the second extremity (node)
................................................................................................................ 26-26
26-27 P2P bid prot T-MPLS tunnel open sink: selected extremities
.............................................................. 26-27
26-28 P2P open sink: constraint ................................................................................................................................... 26-28 26-29 P2P bid prot T-MPLS tunnel open sink: selected extremities and constraint
................................. 26-29
26-30 Search>Packet>T-MPLS>T-MPLS Tunnels ............................................................................................... 26-30 26-31 Tunnel list
................................................................................................................................................................ 26-31 26-31
26-32 Actions>Implement T-MPLS Tunnel 26-33 The tunnel is implemented
............................................................................................................ 26-31
................................................................................................................................ 26-32
26-34 Actions>Packet>T-MPLS>Create T-MPLS Pseudo Wire 26-35 Create T-MPLS Pseudo Wire
..................................................................... 26-33
........................................................................................................................... 26-34
26-36 Dual Point to Point Bidirectional T-MPLS PW ......................................................................................... 26-36 26-37 Search>Packet>T-MPLS>T-MPLS Pseudo Wire
..................................................................................... 26-37
26-38 T-MPLS Pseudo Wires ........................................................................................................................................ 26-37 26-39 PW Implementation
............................................................................................................................................. 26-38 26-38
26-40 T-MPLS Pseudo wire implemented
............................................................................................................... 26-38
26-41 Actions>Packet>Services>T-MPLS>Create T-MPLS EVC
................................................................. 26-40
26-42 Create T-MPLS EVC: Specific ........................................................................................................................ 26-42 26-43 Create T-MPLS EVC: Terminations Selection 26-44 Terminations Selection
.......................................................................................... 26-43
....................................................................................................................................... 26-44 26-44
26-45 Termination Settings ............................................................................................................................................ 26-46 26-46 26-46 Ingress flow create
............................................................................................................................................... 26-48 26-48
26-47 Ingress Flow: create monitoring ...................................................................................................................... 26-49 26-48 Egress Flow: Push
................................................................................................................................................ 26-51 26-51
.................................................................................................................................................................................................................................... 1350 OMS lxvi 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures ....................................................................................................................................................................................................................................
26-49 Create Egress monitoring
.................................................................................................................................. 26-52
26-50 Spoke Transport Link selection
....................................................................................................................... 26-53
26-51 Create Ingress node A
......................................................................................................................................... 26-54
26-52 Create Egress node A
.......................................................................................................................................... 26-55
26-53 Select the transport link
...................................................................................................................................... 26-56
26-54 T-MPLS EVC Allocate and Implement
........................................................................................................ 26-57
26-55 Search>Packet>Services>T-MPLS>T-MPLS EVCs
............................................................................... 26-58
26-56 T-MPLS EVCs ....................................................................................................................................................... 26-59 26-59 26-57 Allocate the EVC
.................................................................................................................................................. 26-59 26-59
26-58 EVC implemented
................................................................................................................................................ 26-59 26-59
27-1
EVC definition: PM folder
.................................................................................................................................. 27-3
27-2
EVC definition: PM policy .................................................................................................................................. 27-4
27-3
Create Measure
27-4
Measure: Actions menu options ......................................................................................................................... 27-7
27-5
Search>PM>PM domains
27-6
Ethernet domain: Search menu
27-7
Ethernet domain: Actions menu ......................................................................................................................... 27-9
27-8
PM transport: Actions menu
27-9
PM TP list
........................................................................................................................................................ 27-5 27-5
.................................................................................................................................... 27-8 .......................................................................................................................... 27-8
............................................................................................................................... 27-9
................................................................................................................................................................ 27-10 27-10
27-10 Start TP dialog box ............................................................................................................................................... 27-10 27-11 Stop TP dialog box
............................................................................................................................................... 27-11
27-12 Measure consistency ............................................................................................................................................ 27-13 27-13 27-13 NE: Actions>Generate Audit ............................................................................................................................ 27-13 27-14 Generate Audit
....................................................................................................................................................... 27-14 27-14
27-15 Create Report Profile ........................................................................................................................................... 27-16 27-16 27-16 Correlation Measure with Report Profile ..................................................................................................... 27-17 27-17 Uncorrelation Measure with Report Profile ................................................................................................ 27-18 27-18 PM TP Actions menu
.......................................................................................................................................... 27-19
27-19 Export TPs to CSV file
....................................................................................................................................... 27-20
.................................................................................................................................................................................................................................... 1350 OMS lxvii 8DG42227DAAA 9.6 Issue 3 December 2012
List of figures ....................................................................................................................................................................................................................................
27-20 Generate Measure PM Report to CSV file
.................................................................................................. 27-21
27-21 Generate PM tabular report ............................................................................................................................... 27-22 28-1
TSS-5 interworking with TSS160/320
............................................................................................................ 28-8
28-2
Create Domain
28-3
Define NE ................................................................................................................................................................ 28-14 28-14
....................................................................................................................................................... 28-13 28-13
.................................................................................................................................................................................................................................... 1350 OMS lxviii 8DG42227DAAA 9.6 Issue 3 December 2012
About this document About this document
Purpose
This preface provides information about how to use this document, which is the 1350 OMS PKT Guide. The purpose of the 1350 OMS PKT Guide is to explain the administration and provisioning features of the 1350 OMS PKT application for the 1350 OMS 9.6 release. This document describes how to use, administer, and maintain the 1350 OMS PKT application for configuring and for monitoring Ethernet or MPLS networks. Reason for reissue
This document has been reissued to support the 1350 OMS 9.6. The revision history of this document is shown in the following table: Location
Revision
Issue
1350 OMS PKT Guide
Document reflects the changes made to the 1350 OMS release 9.6.
Issue 2, May 2012
1350 OMS PKT Guide
Document changes reflect the new 9.6 release of the 1350 OMS.
Issue 1, March 2012
Safety information
This document does not contain any safety information (cautions or warnings) because the 1350 OMS is a software product. Important! When working with any hardware that is associated with any piece of software, always refer to the safety information that the hardware manufacturer provides for that particular piece of hardware. For example, when working with an HP ® server, refer to safety information that is provided in the HP ® documentation for that server. When working with any Alcatel-Lucent network element, refer to safety information that is provided in the Alcatel-Lucent documentation for that particular NE.
................................................................................................................................................................................................................................... 1350 OMS lxix 8DG42227DAAA 9.6 Issue 3 December 2012
About this document ....................................................................................................................................................................................................................................
Intended audience
The 1350 OMS PKT Guide is written primarily for the advanced users of the 1350 OMS, who typically are systems engineers, programmers, and system administrators who must configure and monitor Ethernet or MPLS networks. This document can be used by anyone who needs specific administration or provisioning information about the features, applications, and operations of the 1350 OMS PKT component of the 1350 OMS. These people are you, its users. The 1350 OMS PKT Guide assumes that the user is familiar with the function of telecommunication networks and has had some exposure to the X.org Foundation X-Window ® and Microsoft Windows ® environments. How to use this information product Conceptual and task content
In the broadest sense, this document contains the following types of content: •
•
Conceptual content, which is background information, is given so users can better understand the tasks that must be performed. The presentation of conceptual information varies according to the topic being explained—sections, subsections, tables, figures, and screen captures can be commonly found. Task content, which includes step-by-step instructions, is provided so users can administer, provision, and maintain the system. The task information is typically presented as series of tasks that follows the conceptual information.
The conceptual information complements and enhances the step-by-step instructions that are found in each task. To optimize the use of the conceptual and task content, users should consider the following: •
•
•
The conceptual information should be used to broaden your general knowledge of the network management system. It is best if you read all conceptual information and have a good understanding of the concepts being presented before undertaking the step-by-step instructions given in any task. The conceptual and task portions of the document have extensive hyperlinks. Use these links to toggle between the two types of information presented so you can access all pertinent information related to particular concepts and tasks. The task information is based on a user needs analysis that has been performed for each management system user job; therefore, use the task information to get the job at hand done quickly and with minimal system impact.
Format of task content
Each task consists of sections that are called When to use, Related information, Before you begin, and Task. The intent of these sections is self-explanatory—they explain when you should use the task, any related information that you would need to know while doing the task, and what you need to consider or do before you start the task. When a task does not have any related information that must be considered before it is started, the Related information section for that task states the following: This task does not have any related information. .................................................................................................................................................................................................................................... 1350 OMS lxx 8DG42227DAAA 9.6 Issue 3 December 2012
About this document ....................................................................................................................................................................................................................................
When a task does not have any conditions that must be considered before it is started, the Before you begin section for that task states the following: This task does not have any preconditions. Each Task section consists of steps. The completion of all steps, which are sequentially numbered, is required for the entire task to be completed successfully. In some instances, a step might be prefaced with the wording Optional, which indicates that the step can be skipped and the task can still be completed successfully. A task is considered to be completed when all of its steps are completed and when the wording End of Steps appears. Many times, the management system affords users with multiple ways to accomplish the same task. In these instances, this type of task gives the user several Methods of how to accomplish the same set of steps successfully. Typographical conventions used for content
This document uses the following typographical conventions: •
User input or path navigation on the administration and application GUIs is identified with this type.
•
User input in the UNIX® environment is identified with this type.
•
System output in the UNIX® environment is identified with this type..
• •
GUI fields/parameters and their options are identified with this type. Document titles or words that are being defined or emphasized are identified with this type.
Marking conventions used for content
The following convention is used to indicate a path, which is a flow of buttons and/or menu items that you must navigated through to arrive at a destination on the GUI: Search > EML > Network Elements
This same convention is also used to show a path through a series of menu items, for example: Click the filtering tool and select Node > Node Type. All mouse selections are presumed to be left clicks. Right click mouse selections are indicated as the following: Right click the highlighted item and follow the path: Search > Clients. Or, if brevity is needed, the same path could be documented as: RClick item > Search > Clients.
Occasionally, a set of 1350 OMS features is not supported for all NEs or for all operating components and/or environments. This set of features is clearly marked to show these exceptions.
.................................................................................................................................................................................................................................... 1350 OMS lxxi 8DG42227DAAA 9.6 Issue 3 December 2012
About this document ....................................................................................................................................................................................................................................
Technical content
In general, the technical content in this document is augmented by technical content that is provided in other documents in this documentation set and/or in the document set of the particular network element (NE ) or piece of hardware in the network configuration. It is the user's responsibility to read all pertinent material in all documentation sets in order to understand a particular concept or procedure and/or to implement the procedure in his or her working environment. This document contains information on the complete line of NEs that the 1350 OMS supports. Each release of the 1350 OMS and its applications supports certain NEs within the Alcatel-Lucent family of optical NEs. Mention of NEs or specific NE features in the text of this document, or any document in the 1350 OMS documentation set, that are not supported in this particular product release can apply to prior or future product releases. Such material may not be currently visible or operable on the GUI and/or the server and has been added only as a convenience for our customers. This material is subject to change. For a list of NEs that are supported in the 1350 OMS 9.6, contact your Alcatel-Lucent local customer service support team. This document, or any document in the 1350 OMS documentation set, may contain information that is related to features, service packs (SPs), maintenance releases, or other updates that our product and its applications supported in prior releases or is to support in the near future. This material may not be visible or operable on the supported servers and/or GUI, and has been added only as a convenience for our customers. This material is subject to change. For a list of all supported features for a particular release, contact your Alcatel-Lucent local customer service support team. Treatment of terms
A term that is presented in the text of this document, along with any used abbreviation for the term, is typically defined where the term is initially introduced. Many of the more generic terms that are defined in this document, along with the terms that are defined in other documents in this documentation set, are also defined in the Glossary, which is part of the 1350 OMS Getting Started Guide. We encourage our users to rely on the Glossary for a comprehensive set of terms and any abbreviations of the terms. Document formats
This document is available for use in HTML format and PDF. The on-line HTML version of the document has a search capability, a table of contents in the front matter of the document, a partial table of contents in each chapter, and an index. The PDF version can be viewed on-line; or it, or portions of it, can be printed locally at the user's discretion. On-line help
The 1350 OMS help systems are designed to consider the task that the user is performing and to help the user complete the task.
.................................................................................................................................................................................................................................... 1350 OMS lxxii 8DG42227DAAA 9.6 Issue 3 December 2012
About this document ....................................................................................................................................................................................................................................
Contact sensitive help, which defines many GUI fields, is available; and other types of help can be accessed from the GUI menu. Related documentation
The following documents are related to the 1350 OMS PKT Guide: 1. The 1350 OMS Getting Started Guide (8DG42227AAAA) explains the look-and-feel of the user and administration GUIs to new users. This document contains a complete explanation of the 1350 OMS information product set and a glossary of terms that is applicable to the entire documentation set. 2. The 1350 OMS Administration Guide explains how to use the tools and the administration GUIs to administer and maintain the element management layer, network management layer, and service management layer of the 1350 OMS. This document consists of the following volumes: • The 1350 OMS Administration Guide, Vol 1: Common Tools and Processes (8DG42227LAAA-Vol1) explains how to administer and maintain the common tools and processes that are associated with the 1350 OMS. •
The 1350 OMS Administration Guide, Vol 2: Common GUI Functions (8DG42227LAAA-Vol2) explains how to administer and maintain the common administration GUIs that are associated with the 1350 OMS. 3. The 1350 OMS EML Guide (8DG42227BAAA) explains how to administer and provision the 1350 OMS EML application of the 1350 OMS, which is the element management layer of the 1350 OMS. 4. The1350 OMS SDH Guide (8DG42227CAAA) explains how to administer and provision the Synchronous Digital Hierarchy (SDH) network management layer of the 1350 OMS. 5. The 1350 OMS WDM Guide (8DG42227QAAA) explains how to administer and provision the 1350 OMS WDM, which provides the Wavelength Division Multiplexing (WDM) and Dense Wavelength Division Multiplexing (DWDM) network management layer for the 1350 OMS. 6. The 1350 OMS Service Assurance Guide (8DG42227FAAA) explains how to maintain the 1350 OMS in terms of activities such as alarm clearing and performance monitoring. 7. The 1350 OMS CLI Reference (8DG42227KAAA) provides detailed reference material on the Command Line Interface for the advanced user of the 1350 OMS. The 1350 OMS 9.6 also supports modules for system resiliency and northbound communication. These modules are explained in the following documents: • •
1350 OMS HA Guide (8DG42227GAAA) explains how to install, administer, and use the High Availability feature. 1350 OMS OI Guide (8DG42227HAAA) explains how to install, administer, and use the Open Interfaces that are supported for the 1350 OMS.
Ordering information
The ordering number for this particular document is 8DG42227DAAA. Contact your local Alcatel-Lucent local customer service support team for details. .................................................................................................................................................................................................................................... 1350 OMS lxxiii 8DG42227DAAA 9.6 Issue 3 December 2012
About this document ....................................................................................................................................................................................................................................
In addition, to order the 1350 OMS and/or any of its applications, add-on features or upgrades, contact your local Alcatel-Lucent local customer service support team. How to comment
To comment on this document, go to the Online Comment Form (http://infodoc.alcatellucent.com/comments/) or e-mail your comments to the Comments Hotline (
[email protected]).
.................................................................................................................................................................................................................................... 1350 OMS lxxiv 8DG42227DAAA 9.6 Issue 3 December 2012
Part I: Introduction
Overview Purpose
This part contains a general description about the 1350 OMS product and introduce the user to the activity of administration and maintenance of the 1350 OMS PKT application. Contents Chapter 1, Product Overview
1-1
Chapter 2, Introduction to Administration
2-1
................................................................................................................................................................................................................................... 1350 OMS I-1 8DG42227DAAA 9.6 Issue 3 December 2012
Introduction
Overview
....................................................................................................................................................................................................................................
.................................................................................................................................................................................................................................... 1350 OMS I-2 8DG42227DAAA 9.6 Issue 3 December 2012
1
Product Overview 1
Overview Purpose
This chapter provides an overview of the 1350 OMS PKT and the user functions that are required to provision the application. Contents 1350 OMS Overview
1-2
1350 OMS Modules for System Resiliency and Northbound Communication
1-5
................................................................................................................................................................................................................................... 1350 OMS 1-1 8DG42227DAAA 9.6 Issue 3 December 2012
Product Overview
1350 OMS Overview
....................................................................................................................................................................................................................................
1350 OMS Overview 1350 OMS and its supported management layers
The 1350 OMS is a network management system that supports three layers of management to accommodate and grow with the optical network of the Customers. The Element Management Layer, or EML, provides the functionality that is needed to access any Alcatel-Lucent supported network elements (NEs) that are deployed in a customer network. The EML provides a single access point for communication with an NE. The Network Management Layer, or NML, provides the functionality that is needed to commission, provision, and supervise the network that is deployed in a customer premise. The Service Management Layer, or SML, provides the functionality that is needed to commission, provision, and supervise a Virtual Private Network (VPN) that an Alcatel-Lucent customer deploys to its end users or to its customers. 1350 OMS and its applications
The 1350 OMS is the Alcatel-Lucent converged and unified network management system. It manages the complete portfolio of Alcatel-Lucent active network elements (NEs) and it maintains the complete portfolio of Alcatel-Lucent legacy NEs. The 1350 OMS consists of the following set of integrated, licensed applications: •
“1350 OMS EML” (p. 1-2).
•
“1350 OMS PKT” (p. 1-3).
•
“1350 OMS SDH” (p. 1-3).
•
“1350 OMS WDM” (p. 1-3).
Refer to the 1350 OMS Getting Started Guide for a more detailed system description. 1350 OMS EML
The 1350 OMS EML application provides element level management (EML) capabilities for both Alcatel-Lucent ANSI and ETSI NEs. Its set of protocol adapters supports basic NE functions such as NE MIB backup/restore and software downloads. Because the 1350 OMS provides all of the element layer functions that are required to manage the deployed network, it requires to deploy also the 1350 OMS EML application. Refer to the following documents and contact your Alcatel-Lucent local customer service support team for additional details: • •
1350 OMS EML Guide. 1350 OMS Service Assurance Guide.
.................................................................................................................................................................................................................................... 1350 OMS 1-2 8DG42227DAAA 9.6 Issue 3 December 2012
Product Overview
1350 OMS Overview
....................................................................................................................................................................................................................................
1350 OMS PKT
The 1350 OMS PKT application provides Ethernet network management layer support along with provisioning, alarm correlation, and historical PM data services. Ethernet services include Multi-Protocol Label Switching (MPLS), Transport-Multi-Protocol Label Switching (T-MPLS), bridging, Connection Oriented traffic, and packet rings. Refer to the following documents and contact your Alcatel-Lucent local customer service support team for additional details: • •
1350 OMS PKT Guide. 1350 OMS Service Assurance Guide.
1350 OMS SDH
The 1350 OMS SDH application provides the Synchronous Digital Hierarchy (SDH) network management layer along with provisioning, alarm correlation, and PM correlation capabilities. The 1350 OMS SDH functions as a client for the 1350 OMS WDM application and as a server for the 1350 OMS PKT application. Refer to the following documents and contact your Alcatel-Lucent local customer service support team for additional details: •
1350 OMS CLI Reference.
•
1350 OMS Service Assurance Guide.
1350 OMS WDM
The 1350 OMS WDM application provides Wavelength Division Multiplexing (WDM) and Dense Wavelength Division Multiplexing (DWDM) support along with provisioning, alarm correlation, and historical PM correlation capabilities. Refer to the following documents and contact your Alcatel-Lucent local customer service support team for additional details: •
1350 OMS WDM Guide.
•
1350 OMS Service Assurance Guide.
1350 OMS software and the Web
1350 OMS is run through an Internet browser-based Graphical User Interface (GUI). It supports the standard web features that a browser offers, such as bookmarks, back, forward, reload, and print. The Web Desktop is the available mechanism that both system administrators and users can use to access the 1350 OMS GUI. It provides a central access point from which both system administrators and users are authenticated and from which they can navigate to the Web Portal to access the 1350 OMS applications.
.................................................................................................................................................................................................................................... 1350 OMS 1-3 8DG42227DAAA 9.6 Issue 3 December 2012
Product Overview
1350 OMS Overview
....................................................................................................................................................................................................................................
The Web Portal is a Java application that is started when the administrator or user logs in from the Web Desktop. The Web Portal provides the administrator with a view of all 1350 OMS applications and manages GUI navigation between the subsystem components. The Web Portal also provides various methods of navigation—such as menus, icons, and a left tree navigation area—between applications and tools. From the 1350 OMS Web Portal, administrators can set up each application and its users, and users can access the network and element level applications that enable the family of Alcatel-Lucent NEs to be provisioned. Refer to the 1350 OMS Getting Started Guide for a more detailed description of the look and feel of the software and for a glossary of terms and acronym list. 1350 OMS supported NEs
The 1350 OMS supports the Alcatel-Lucent family of optical network elements (NEs). To accommodate the world of optical transmission standards, these NEs operate using different transport structures and they support different native command languages. Contact your local customer support team for a list of NEs that are supported by the 1350 OMS and its particular applications.
.................................................................................................................................................................................................................................... 1350 OMS 1-4 8DG42227DAAA 9.6 Issue 3 December 2012
Product Overview
1350 OMS Modules for System Resiliency and Northbound Communication
....................................................................................................................................................................................................................................
1350 OMS Modules for System Resiliency and Northbound Communication 1350 OMS HA
The 1350 OMS supports High Availability (HA) as an added value module, which is referred to as the 1350 OMS HA. The 1350 OMS HA software package is installed on top of an already installed and configured NML and EML platform and independently of any other application such as the 1350 OMS SDH, 1350 OMS PKT, or 1350 OMS WDM, or any element manager such as the 1350 OMS EML or 1350 OMS eOMS. As its name suggests, the 1350 OMS HA provides high availability to these applications whose main task is to manage transport networks. It protects the 1350 OMS applications and its HP® server platform against hardware and software failures that could be caused by system failures (such as the failure of the system power supply or a system component), a site failure (such as a natural disaster or fire), a backplane failure, a processor failure, or any unplanned outage. The 1350 OMS HA is explained in detail in the 1350 OMS HA Guide (8DG42227GAAA). This document includes installation, administration, and user information for the 1350 OMS High Availability (HA) feature. Contact your Alcatel-Lucent local customer service support team for additional details. 1350 OMS OI
The 1350 OMS OI software package is installed on top of an already installed and configured MW-INT platform and independently of any other application such as the 1350 OMS SDH, 1350 OMS PKT, 1350 OMS WDM, or any element manager such as the 1350 OMS EML or 1350 OMS eOMS. The 1350 OMS OI enables the 1350 OMS applications to export or import data to multiple external operation systems (OSs). The 1350 OMS OI is a flexible, powerful, and effective set of generic OS-to-OS interfaces (GENOS) that allow an external OS to synchronize alarms, performance monitoring, network inventory, and remote inventory data with any of the 1350 OMS applications. The 1350 OMS OI is explained in detail in the 1350 OMS OI Guide (8DG42227HAAA). This document includes installation, administration, and user information for the Open Interfaces (OIs) that are supported for the 1350 OMS. Contact your Alcatel-Lucent local customer service support team for additional details.
.................................................................................................................................................................................................................................... 1350 OMS 1-5 8DG42227DAAA 9.6 Issue 3 December 2012
Product Overview
1350 OMS Modules for System Resiliency and Northbound Communication
....................................................................................................................................................................................................................................
.................................................................................................................................................................................................................................... 1350 OMS 1-6 8DG42227DAAA 9.6 Issue 3 December 2012
2
I2ntroduction to Administration
Application Administration MW-INT as the building block
The MW-INT, which is the middleware interface, is the building block of the 1350 OMS architecture; and as such, it is the platform for all 1350 OMS components and its features. The MW-INT enables the administrator to install a single product or several different products, as well as different instances of the same product on one hardware platform. The 1350OMS applications are installed and configured on top of the MW-INT platform. The MW-INT provides the following functionality: •
Process management
• • •
Subsystem configuration Installation/integration and customization System management
Application instances
The 1350 OMS supports the 1350 OMS PKT application, and each occurrence of this application in the management system is referred to as an instance. Each application instance is managed by the MW-INT. Refer to the 1350 OMS Administration Guide, Vol 1: Common Tools and Processes for details. Process Monitoring
Process Monitoring is the graphical representation of the system processes and their actual status. The Process Monitoring Control application is the graphic interface of the MW-INT application that allows the user to have an overall control of the IM subsystem of the selected System Instance. The PMC graphic interface is composed of a common window dedicated to display information and to execute commands for the management of all the processes (agents) of the selected System Instance. The processes are collected in groups (for example Database processes, Alarms processes,...) and each group is represented in the PMC window through an icon which color informs the user of the group functional state. Exactly the group icon gives the summarized information about the functional state of all the processes and their children included in the group itself. ................................................................................................................................................................................................................................... 1350 OMS 2-1 8DG42227DAAA 9.6 Issue 3 December 2012
Introduction to Administration
Application Administration
....................................................................................................................................................................................................................................
Refer to the 1350 OMS Administration Guide, Vol 2: Common GUI Functions for details. The Web Desktop
Much of the administration of the 1350 OMS PKT application occurs through the Web Desktop of the 1350 OMS. The Web Desktop provides a central access point from which both system administrators and users are authenticated and from which they can navigate to the Web Portal to access the 1350OMS applications. Refer to the 1350 OMS Administration Guide, Vol 2: Common GUI Functions for details. SEC User Administration and SEC User Authentication
The 1350 OMS uses its two SEC (Security) GUIs to administer and maintain security: • •
The 1350 OMS enables administrators to create and maintain user accounts through its SEC User Administration GUI. Functional area domains (FADs), object access domains (OADs), and combinations of these domains along with user profiles and the declaration and discarding of user accounts are administered through its SEC Authentication GUI.
Both the SEC User Administration GUI and the SEC User Authentication GUI are explained in the 1350 OMS Administration Guide, Vol 2: Common GUI Functions. Full system backups
The 1350 OMS enables administrators to perform a full system backup and recovery. For details, refer to the 1350 OMS Administration Guide, Vol 1: Common Tools and Processes, which details full system backups and recoveries, single volume backups, and mirror configurations. Troubleshooting information is also included. Application backup and restore
The 1350 OMS enables administrators to backup and restore a particular 1350 OMS application and to schedule a backup of a particular 1350 OMS application. For details, refer to the 1350 OMS Administration Guide, Vol 2: Common GUI Functions, which details how use the SMF Scheduler to schedule a full backup or a backup of just the network data, the alarm data, the performance monitoring data, the log data, user data, or the system configuration. PM Administration
Through its Data Management facilities, the 1350 OMS enables administrators to view the performance monitoring statistics of a particular PM database. For details, refer to the 1350 OMS Administration Guide, Vol 2: Common GUI Functions.
.................................................................................................................................................................................................................................... 1350 OMS 2-2 8DG42227DAAA 9.6 Issue 3 December 2012
Introduction to Administration
Application Administration
....................................................................................................................................................................................................................................
Logs, Command Log, and Command Log Administration
Log files are files that consist of records that are created by the various tools (scripts) and processes. Administrators use log files to track any and/or all meaningful operations that occur within the application or when a tool is executed. The 1350 OMS supports security logs, command logs, and system logs. These logs are explained in detail in the 1350 OMS Administration Guide, Vol 2: Common GUI Functions. The Command Log enables administrators to parse a command log or a set of command logs from a list of command logs. Once that list of command logs has been parsed, the Command Log enables administrators to extract log records from target command log files by using filters and to output that extracted list to a browser or to a table, called the Command Result List, which is a tabular display that can be printed. For details, refer to the 1350 OMS Administration Guide, Vol 2: Common GUI Functions. Command Log Administration enables the administrator to edit the command output template. In addition, the Command Log Administration function then allows the administrator to view, parse, and filter the Command Log. For details, refer to the 1350 OMS Administration Guide, Vol 2: Common GUI Functions.
.................................................................................................................................................................................................................................... 1350 OMS 2-3 8DG42227DAAA 9.6 Issue 3 December 2012
Introduction to Administration
View Application Release Information
....................................................................................................................................................................................................................................
View Application Release Information When to use
Use this task to view release information about an application. Related information
See the following topic in this document: •
“Application Administration” (p. 2-1)
Before you begin
Open a Terminal session on the server machine. Task
Complete the following steps to view release information about an application. ...................................................................................................................................................................................................
Type the following command after the command prompt :
1
/alu/Kernel/bin/Info.pl -sys PKT -inst -9.1.0 Result: The System Information window is displayed. ...................................................................................................................................................................................................
The release information for the application is similar to the following
2
General Information on System: System Version Instance Role
: : : : Master Ws : LOCAL OSK -ENGINE: Master Kernal Type: Master OSK-ENGINE Interface Version: Info ...
: *
Last Configuration Update: Local Time: Local Customization Update: Local Time: .................................................................................................................................................................................................................................... 1350 OMS 2-4 8DG42227DAAA 9.6 Issue 3 December 2012
Introduction to Administration
View Application Release Information
....................................................................................................................................................................................................................................
Composition ...................................................................................................................................................................................................
3
Press the Dismiss button to close the window. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 2-5 8DG42227DAAA 9.6 Issue 3 December 2012
Introduction to Administration
View Application Release Information
....................................................................................................................................................................................................................................
.................................................................................................................................................................................................................................... 1350 OMS 2-6 8DG42227DAAA 9.6 Issue 3 December 2012
Part II: Administration
Overview Purpose
This document part provides to system and network administrators information and procedures to administer and to maintain the 1350 OMS PKT. Contents Chapter 3, 1350 OMS PKT Configuration
3-1
Chapter 4, 1350 OMS PKT Process Monitoring
4-1
Chapter 5, 1350 OMS PKT User Management
5-1
Chapter 6, 1350 OMS PKT System Log Management
6-1
Chapter 7, 1350 OMS PKT Parameters
7-1
Chapter 8, 1350 OMS PKT Ethernet Multi-Manager Management Configurations
8-1
Chapter 9, 1350 OMS PKT MIB Realignment and the ISA Board
9-1
Chapter 10, 1350 OMS PKT AlignDBSDHPathID Tool
10-1
................................................................................................................................................................................................................................... 1350 OMS II-1 8DG42227DAAA 9.6 Issue 3 December 2012
Administration
Overview
....................................................................................................................................................................................................................................
.................................................................................................................................................................................................................................... 1350 OMS II-2 8DG42227DAAA 9.6 Issue 3 December 2012
3
3350 OMS PKT 1 Configuration
Overview Purpose
This chapter provides the administrator with the conceptual information and the associated tasks that pertain to the configuration of the overall 1350 OMS PKT application. Contents 1350 OMS PKT Configuration
3-2
Access the System Configuration Window and Configure 1350 OMS PKT
3-3
Integrate the 1350 OMS PKT with Other NMSs
3-8
Integrate 1350 OMS PKT Client Workstations with the Master Workstation
3-9
................................................................................................................................................................................................................................... 1350 OMS 3-1 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT Configuration
1350 OMS PKT Configuration
....................................................................................................................................................................................................................................
1350 OMS PKT Configuration Administrator log in
The administrator must log into the 1350 OMS PKT configuration from the log in mask as alcatel. Important! We strongly recommend that you do not log in as bmml to start the 1350 OMS PKT session. The default administrator log in is alcatel, which is available since the first customization. If needed, you can create additional administrator log using SMF. Any security warnings that appear should be ignored. Application Configuration through SystemConfig
Open a Unix Terminal window starting from the Unix Server machine to activate the System Configuration Window: The System Configuration window is divided into the following two panes: •
The Instantiable Subsystems pane is on the left. This pane contains a list of system processes, which are listed as proxies, that can have multiple instances. The administrator can use the arrow to move one or more system processes, which in this scenario are proxies, from the Instantiable Subsystems list to the Subsystems List, which moves the particular process or processes over to the static list and adds an instance number to the process.
•
The Subsystems List pane is on the right. This pane contains a static list of processes that cannot have multiple instances. In addition, this pane can contain one or more system processes from the Instantiable Subsystems pane on the left. The list of processes in the Subsystems List will be system instance processes.
System Configuration is used to configure processes in a system instance. The processes are configured into groups. A group of processes is called entity, which is used to configure, in a single step, processes that have the same configuration properties. The group definition is a System (NMS) configuration property. Each NMA has a specific configuration file that is used to configure its processes; this configuration file contains specific data and parameters. Process configuration enables processes to be configured in the following ways: •
A static list of processes can be defined that can belong to the System Instance.
•
A variable list of processes can be defined that can have multiple instances within the System Instance.
A configuration file can define the ID category of the multiple instances off-line.
.................................................................................................................................................................................................................................... 1350 OMS 3-2 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT Configuration
Access the System Configuration Window and Configure 1350 OMS PKT
....................................................................................................................................................................................................................................
Access the System Configuration Window and Configure 1350 OMS PKT When to use
Use this task to access the system configuration window and to configure the 1350 OMS PKT. Related information
See the following topic in this document: •
“Access the System Configuration Window and Configure 1350 OMS PKT” (p. 3-3)
Before you begin
You cannot add a proxy to the system configuration while the system is running. When configuring proxies, the system must be down. Task
Complete the following steps to configure a 1350 OMS application, such as the 1350 OMS PKT. ...................................................................................................................................................................................................
1
The system must be brought down. ...................................................................................................................................................................................................
2
On the CDE front panel, press the terminal icon to start a Unix terminal application. Result: The terminal window is displayed. ...................................................................................................................................................................................................
3
Login as root user. ...................................................................................................................................................................................................
4
Open a telnet session on the server machine. ...................................................................................................................................................................................................
5
Set the export the of the display: export DISPLAY=: ...................................................................................................................................................................................................
6
Insert following command after the prompt : /alu/Install_Wizard/Install.sh –config
and select PKT as the system to configure.
.................................................................................................................................................................................................................................... 1350 OMS 3-3 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT Configuration
Access the System Configuration Window and Configure 1350 OMS PKT
....................................................................................................................................................................................................................................
Result: The System Configuration window is displayed. The left pane of the window displays Instantiable Subsystems. The right pane of the window displays a Subsystems List. ...................................................................................................................................................................................................
7
To configure the EMLIM_PROXY, do the following: In the Instantiable Subsystems list, click on EMLIM_PROXY. If you want to add one EMLIM_PROXY, enter a 1 in the next ID field. Click the right arrow to move the EMLIM_PROXY from the Instantiable Subsystems list to the Subsystems List. Result:
EMLIM_PROXY_1 now appears on the Subsystems List.
In the Subsystem List, click on EMLIM_PROXY_1 to configure it. Result: The tool displays the Parameters Definition pop-up window.
In the Parameters Definition window, select the following to configure each of the parameters: For USE_CDN, select False, which is the default, if the proxy is to be an SNMP-type. If the proxy is not to be an SNMP-type, select True. For EML_NAME, enter a name given to the EML proxy. The name can be 1 to 10 characters in length. It cannot contain spaces (blanks). In addition, do not use any characters that will conflict with the UNIX ps command. For NM_INSTANCE_NAME_TO_USE, enter the complete EML system instance name. For example: 1353NM_1-7.4 where the EML is configured. If USE_CDN is true, this value must be the value of the SDH. ...................................................................................................................................................................................................
8
To configure the proxy for the NML, do the following: In the Instantiable Subsystems list, click on NMLIM_PROXY. If you want to add one NMLIM_PROXY, enter a 1 in the next ID field. Remember! Only one 1350 OMS PKT can manage one NML proxy.
Click the right arrow to move the NMLIM_PROXY from the Instantiable Subsystems list to the Subsystems List. Result:
NMLIM_PROXY_1 now appears on the Subsystems List.
In the Subsystem List, click on NMLIM_PROXY_1 to configure it. Result: The tool displays the Parameters Definition pop-up window.
In the Parameters Definition window, select the following to configure each of the parameters: For NML_NAME, enter a name given to the NML proxy. The name can be 1 to 10 characters in length. It cannot contain spaces (blanks). In addition, do not use any characters that conflict with the UNIX® ps command. .................................................................................................................................................................................................................................... 1350 OMS 3-4 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT Configuration
Access the System Configuration Window and Configure 1350 OMS PKT
....................................................................................................................................................................................................................................
For RM_INSTANCE_NAME_TO_USE, enter the complete 1350OMS-RM system instance name. For example: 1350OMSRM_1-7.4.5. Follow this path to exit: Actions > Apply & Exit ...................................................................................................................................................................................................
9
To configure the SNA_EMLIM_PROXY, do the following: In the Instantiable Subsystems list, click on SNA_EMLIM_PROXY. The value to enter in the ID field is the ID value assigned to the adapter TL1 configured on EML application. Click the right arrow to move the SNA_EMLIM_PROXY from the Instantiable Subsystems list to the Subsystems List. Result:
SNA_EMLIM_PROXY_x now appears on the Subsystems List.
In the Subsystem List, click on SNA_EMLIM_PROXY_x to configure it. Result: The tool displays the Parameters Definition pop-up window.
In the Parameters Definition window, select the following to configure each of the parameters: For EML_NAME, enter a name given to the EML proxy. The name can be 1 to 10 characters in length. It cannot contain spaces (blanks). In addition, do not use any characters that will conflict with the UNIX ps command. For NM_INSTANCE_NAME_TO_USE, enter the complete EML system instance name. For example: EML_2-9.1.0 where the adapter TL1 is configured. ...................................................................................................................................................................................................
10
To configure the NMA for the CORE_IM, do the following: In the Subsystem List, look for and click on _CORE_IM. Under TMP_REMOTENAMINGFILE in the Actions pane of the Parameters Definition window, specify the name of the 1350OMS-EML naming file. Example: /tmp/naming.ref Under TMP_NE_UNDER_1354RM Management, indicate by specify 1 for yes or 0 for no if all NEs that are managed by the 1350 OMS PKT are also under 1350 OMS SDH management. For migrations, if NEs are already defined in the 1350 OMS PKT database and if these NEs were under 1350OMS-RM mangement, you cannot specify a 0 for no. If you do, the 1350 OMS SDH cannot be started. For the remaining fields, select all default values. Follow this path to exit: Actions > Apply & Exit ...................................................................................................................................................................................................
11
To configure the NMA for the CORE_UM, do the following:
.................................................................................................................................................................................................................................... 1350 OMS 3-5 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT Configuration
Access the System Configuration Window and Configure 1350 OMS PKT
....................................................................................................................................................................................................................................
In the Subsystem List, look for and click on _CORE_USM. Under UI_LANGUAGE in the Actions pane of the Parameters Definition window, specify the user interface language to be English. Under PRINTER, specify the name of the default system printer even if the system printer is not yet installed. This field is mandatory.. Follow this path to exit: Actions > Apply & Exit ...................................................................................................................................................................................................
12
To configure NMC system tuning, do the following: In the Subsystem List, look for and click on System_Tuning. Result: The Parameters Definition window is displayed.
Leave the default values, which are 100 for SYSTEM_TUNING_VAL and 30 for SYS_START_WAIT_VAL. Follow this path to exit: Actions > Apply & Exit ...................................................................................................................................................................................................
13
To configure the NMC Oracle database, do the following: In the Subsystem List, look for and click on ORACLE-DB. Result: The Parameters Definition window is displayed.
Under MIB in the Actions pane of the Parameters Definition window, specify NEW to create a new database. Under DB_SIZE in the Actions pane of the Parameters Definition window, specify the size of the new database to be one of the following. (The DB_SIZE is linked to the kind of instance that you selected at OS_CONF predisposition time.) •
small
If you selected IM_Small instance, you must select small as the DB_SIZE. •
medium (the default)
If you selected IM_Medium instance, you must select small or medium as the DB_SIZE. •
large
If you selected IM_Large instance, you can select small, medium, or large as the DB_SIZE. Follow this path to exit: Actions > Apply & Exit ...................................................................................................................................................................................................
14
To configure NMC TAO_Interface Repository, do the following: In the Subsystem List, look for and click on TAO_InterfaceRepository. Result: The Parameters Definition window is displayed.
.................................................................................................................................................................................................................................... 1350 OMS 3-6 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT Configuration
Access the System Configuration Window and Configure 1350 OMS PKT
....................................................................................................................................................................................................................................
Under IFRREP in the Actions pane of the Parameters Definition window, specify NEW, the default, to create a new persistent file. Follow this path to exit: Actions > Apply & Exit ...................................................................................................................................................................................................
15
To execute the configuration, do the following: In the System Configuration window, follow this path: Main > UpdateConfig Result: The Parameters Definition window is displayed. If the parameter New was
selected to create a new database, the database creation takes about 20 minutes. When the configuration is finished, the System Configuration Log is output. Ignore the warning messages. Click the Dismiss button to close the window. Follow this path to exit from the System Configuration window: Main > Quit. Result: The system asks you if you really want to quit.
Select Yes to quit. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 3-7 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT Configuration
Integrate the 1350 OMS PKT with Other NMSs
....................................................................................................................................................................................................................................
Integrate the 1350 OMS PKT with Other NMSs When to use
Use this task to integrate an instance of the 1350 OMS PKT with other network management systems (NMSs), such as the 1350 OMS SONET, 1350 OMS SDH, or 1350 OMS WDM. Related information
See the following topic in this document: •
“Access the System Configuration Window and Configure 1350 OMS PKT” (p. 3-3)
Before you begin
This task is to be used if an instance (master or client) of the 1350 OMS PKT is co-located with other NMSs, such as the 1350 OMS SONET, 1350 OMS SDH, or 1350 OMS WDM. This task validates inter-system navigation; that is, navigation from one NMS to another NMS. It also enables CORBA communication between NMSs. Task
Complete the following steps to integrate an instance of the 1350 OMS PKT with other network management systems (NMSs), such as the the 1350 OMS SONET, 1350 OMS SDH, or 1350 OMS WDM. ...................................................................................................................................................................................................
1
Log in as root. ...................................................................................................................................................................................................
2
Enter the following command to start the global integration tool: ...,sys,root # /alcatel/Kernel/script/UpdateNeworkConnection.pl [Enter] Result: This tool validates the inter-system navigation and enables CORBA
communications between NMS. ...................................................................................................................................................................................................
3
Choose yes when integrating PKT with EML/SDH/NPR for both PLT and NAV integration and yes when integrating eOMS only for PLT part. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 3-8 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT Configuration
Integrate 1350 OMS PKT Client Workstations with the Master Workstation
....................................................................................................................................................................................................................................
Integrate 1350 OMS PKT Client Workstations with the Master Workstation When to use
Use this task to integrate each the 1350 OMS PKT client workstation with its 1350 OMS PKT master workstation. Related information
See the following topic in this document: •
“Access the System Configuration Window and Configure 1350 OMS PKT” (p. 3-3)
Before you begin
Execute this task for each 1350 OMS PKT client workstation that must be integrated with its 1350 OMS PKT master workstation. Task
Complete the following steps to integrate each the 1350 OMS PKT client workstation with its 1350 OMS PKT master workstation. ...................................................................................................................................................................................................
1
Log in as root. ...................................................................................................................................................................................................
2
Enter the following command to start the global integration tool: ...,sys,root # /alcatel/Kernel/script/UpdateNeworkConnection.pl [Enter] E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 3-9 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT Configuration
Integrate 1350 OMS PKT Client Workstations with the Master Workstation
....................................................................................................................................................................................................................................
.................................................................................................................................................................................................................................... 1350 OMS 3-10 8DG42227DAAA 9.6 Issue 3 December 2012
4
4350 OMS PKT Process 1 Monitoring
Overview Purpose
This chapter provides the administrator with the conceptual information and the associated tasks that pertain to the process monitoring of the overall 1350 OMS PKT application. Contents Process Monitoring Overview
4-2
Run Levels
4-5
................................................................................................................................................................................................................................... 1350 OMS 4-1 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT Process Monitoring
Process Monitoring Overview
....................................................................................................................................................................................................................................
Process Monitoring Overview Groups
Processes are collected in groups, such as the database group, alarms group, or adapters group. Figure 4-1 Process Monitoring Window
.................................................................................................................................................................................................................................... 1350 OMS 4-2 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT Process Monitoring
Process Monitoring Overview
....................................................................................................................................................................................................................................
The follow table lists the groups of the processes. Process Groups Group name
Process Name
Function
Database
oracle_monitor_process
Manages the ORACLE processes.
Alarms
AS_Current_IM
Manages the AS current alarms.
AS_Historic_IM
Manages the AS historical alarms.
AlmAdapter
Manages the communication with EML/SDH for the alarms.
EmlAdapter
Manages the communication with EML (through Proxy processes).
NmlAdapter
Manages the communication with SDH (through Proxy processes).
c_FaultManagement
Manages the alarms for the CORE entities.
c_DataManagement
Manages the access to the database for the CORE entities.
c_TopologyManagement
Manages the topology of the network.
c_EquipmentTopology
Manages the equipment defined in EMLs/IM.
c_AuditAlignRecovery
Manages Audit/Alignment/Recovery utilities
c_Scheduler
Manages scheduled reports generation
m_FaultManagement
Manages the alarms for the MPLS entities.
m_NetworkManagement
Manages the network entities.
m_ TrafficProfileManagement
Manages the traffic profiles.
m_DataManagement
Manages the access to the database for the MPLS entities.
m_AuditAlignRecovery
Manages Audit/Alignment/Recovery utilities (MPLS entities)
Adapters
Core
Mpls
.................................................................................................................................................................................................................................... 1350 OMS 4-3 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT Process Monitoring
Process Monitoring Overview
....................................................................................................................................................................................................................................
Process Groups Group name Eot
Process Name
Function
e_DataManagement
Manages the access to the database for the MPLS entities.
e_FaultManagement
Manages the alarms for the MPLS entities.
e_ProfileManagement
Manages the profiles.
e_ServiceManagement
Manages the services.
e_TrafficManagement
Manages the traffic profiles.
e_AuditAlignRecovery
Manages Audit/Alignment/Recovery utilities (EOT entities)
e_Facility
Add on for VPWS Ethernet Service Creation.
e_Bridge
Manages the Bridge.
e_PM
Manages Performance Monitoring on Ethernet services
Session
SessionManagement
Manages the interface of all IM processes of the 1350 OMS PKT and the GUI(s) or CLI(s).
Nbi
NbiManagement
Manages the Northbound Interface.
EML_Proxies
Proxy_E_EML_NAME
Manages each configured Eml Proxy with EML_NAME
Proxy_E_SNA_NAME
Manages each configured SNA Eml Proxy with SNA_EML_NAME
NML_Proxies
Proxy_N_NML_NAME
Manages configured Nml Proxy (one and only one can be configured) with NML_NAME
E2E
e2e_manager
Manages the e2e Ethernet services
e2e_data
Manages the access to database for e2e entities
e2e_indirect
Manages indirect eOMS services
tmpls_adaconfig
Manages the Adapter configuration
tmpls_dom
Manages the domains
tmpls_inventory
Inventory management
tmpls_lsp
Lsp Management
EthOperatorLog
Managing the log on operator
Tmpls
OperatorLogger
.................................................................................................................................................................................................................................... 1350 OMS 4-4 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT Process Monitoring
Run Levels
....................................................................................................................................................................................................................................
Run Levels Run levels 0 through 4
The 1350 OMS PKT has the following run levels: Run Level
Name
Information
0
FullFunctionality
Run the entire application.
1
BackupMode
Subsystem runs to allow a backup job to run without conflicting problems. Only processes configured for this run level should be run.
2
RestoreMode
Subsystem runs to allow a restore job to run without conflicting problems. Only processes configured for this run level should be run.
3
ADAPTERS
Run the ADAPTERS part.
4
DB_Only
Needed for OS resilience. Run ORACLE Database processes.
.................................................................................................................................................................................................................................... 1350 OMS 4-5 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT Process Monitoring
Run Levels
....................................................................................................................................................................................................................................
.................................................................................................................................................................................................................................... 1350 OMS 4-6 8DG42227DAAA 9.6 Issue 3 December 2012
5
5350 OMS PKT User 1 Management
Overview Purpose
This chapter provides the administrator with the conceptual information and the associated tasks that pertain to the user management of the overall 1350 OMS PKT application. Contents User Profiles
5-2
Construction Macro Functions and Default User Profiles
5-3
MPLS Macro Functions and Default User Profiles
5-7
Ethernet Macro Functions and Default User Profiles
5-9
................................................................................................................................................................................................................................... 1350 OMS 5-1 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT User Management
User Profiles
....................................................................................................................................................................................................................................
User Profiles Default operator profiles
The 1350OMS default operator profiles are the following: •
An administrator can perform every function on the particular 1350OMS application.
•
A constructor can manage the topology of the network, which includes subnetworks, NEs, ENEs, LOS, LOC, and LOM. The constructor can perform every function on maps and NEs; however, the constructor cannot perform certain administration functions. For example: a constructor cannot add or remove operators or perform a backup and restore of the system. An operator can create local maps, import saved maps, and manage services such as Ethernet; however, the operator cannot manage NEs (start/stop supervision) or manage the global inventory. In addition, an operator cannot perform certain administration functions. For example: an operator cannot add or remove operators or perform a backup and restore of the system. A viewer can view lists of data and can view the maps. In general, a viewer can only look at data; a viewer has limited access and privileges.
•
•
When a new operator is created through the Create User function, that operator must be assigned to one of the default profiles. The default profiles names cannot be changed and the profiles themselves cannot be reconfigured.
.................................................................................................................................................................................................................................... 1350 OMS 5-2 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT User Management
Construction Macro Functions and Default User Profiles
....................................................................................................................................................................................................................................
Construction Macro Functions and Default User Profiles TMPLS management TMPLS Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
T-Mpls Domain, Nodes, Sections, Tunnels, Pseudo Wires list
✓
✓
✓
✓
Services
✓
✓
T-Mpls deletion
✓
✓
T-Mpls modification
✓
✓
T-Mpls properties
✓
✓
✓
✓
Administrator
Constructor
Operator
Viewer
Domain list / search
✓
✓
✓
✓
Domain creation
✓
✓
Domain deletion
✓
✓
Domain modification
✓
✓
Domain properties
✓
✓
✓
✓
Domain inventory
✓
✓
✓
✓
T-Mpls EVC creation
Domain management Domain Management ✓ is Allowed Macro Function
Service node management Service Node Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
Service node list / search
✓
✓
✓
✓
Service node properties
✓
✓
✓
✓
Service node inventory
✓
✓
✓
✓
.................................................................................................................................................................................................................................... 1350 OMS 5-3 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT User Management
Construction Macro Functions and Default User Profiles
....................................................................................................................................................................................................................................
NE management NE Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
NE list / search
✓
✓
✓
✓
NE available list/ search
✓
✓
NE definition
✓
✓
NE deletion
✓
✓
NE modification
✓
✓
NE properties
✓
✓
✓
✓
NE acknowledge
✓
✓
✓
✓
NE configuration
✓
✓
NE assign to domain
✓
✓
NE de-assign from domain
✓
✓
ENE management ENE Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
ENE list / search
✓
✓
✓
✓
ENE creation
✓
✓
ENE deletion
✓
✓
ENE modification
✓
✓
ENE properties
✓
✓
✓
✓
SDH termination management SDH Termination Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
SDH termination synchronization
✓
✓
SDH termination audit
✓
✓
SDH termination upload
✓
✓
SDH termination properties
✓
✓
✓
✓
SDH termination list / search
✓
✓
✓
✓
.................................................................................................................................................................................................................................... 1350 OMS 5-4 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT User Management
Construction Macro Functions and Default User Profiles
....................................................................................................................................................................................................................................
Ethernet physical port management Ethernet Physical Port Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
Ethernet physical port upload
✓
✓
Ethernet physical port modification
✓
✓
Ethernet physical port configuration
✓
✓
Ethernet physical port properties
✓
✓
✓
✓
Ethernet physical port list / search
✓
✓
✓
✓
Operator
Viewer
External termination management External Termination Management ✓ is Allowed Macro Function
Administrator
Constructor
ETP creation
✓
✓
ETP deletion
✓
✓
ETP properties
✓
✓
✓
✓
ETP list/ search
✓
✓
✓
✓
Operator
Viewer
Link over SDH management Link over SDH Management ✓ is Allowed Macro Function
Administrator
Constructor
Link over SDH creation
✓
✓
Link over SDH creation (nav on RM)
✓
✓
Link over SDH deletion
✓
✓
Link over SDH deletion (nav on RM)
✓
✓
Link over SDH modification
✓
✓
Link over SDH properties
✓
✓
✓
✓
Link over SDH extremities
✓
✓
✓
✓
Link over SDH list / search
✓
✓
✓
✓
.................................................................................................................................................................................................................................... 1350 OMS 5-5 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT User Management
Construction Macro Functions and Default User Profiles
....................................................................................................................................................................................................................................
Link over SDH Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
✓
Link over SDH configuration
Viewer
✓
Link over MPLS management Link over MPLS Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
Link over MPLS properties
✓
✓
✓
✓
Link over MPLS extremities
✓
✓
✓
✓
Link over MPLS list / search
✓
✓
✓
✓
Operator
Viewer
Link over cable management Link over Cable Management ✓ is Allowed Macro Function
Administrator
Constructor
Link over cable creation
✓
✓
Link over cable deletion
✓
✓
Link over cable modification
✓
✓
Link over cable properties
✓
✓
✓
✓
Link over cable extremities
✓
✓
✓
✓
Link over cable list / search
✓
✓
✓
✓
Utilities management Utilities Management ✓ is Allowed Utilities Management
Administrator
Start/End Procedure
✓
Audit NE
✓
Display NE Audit
✓
Align NE
✓
Reserve
✓
Constructor
Operator
Viewer
.................................................................................................................................................................................................................................... 1350 OMS 5-6 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT User Management
MPLS Macro Functions and Default User Profiles
....................................................................................................................................................................................................................................
MPLS Macro Functions and Default User Profiles Transport Link management Transport Link Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
Characteristics definition
✓
✓
Transport Link bandwidth load indication
✓
✓
✓
✓
Transport Link extremities
✓
✓
✓
✓
Transport Link list / search
✓
✓
✓
✓
Transport link properties
✓
✓
✓
✓
Transport link inventory
✓
✓
✓
✓
Operator
Viewer
Traffic descriptor management Transport Descriptor Management ✓ is Allowed Macro Function
Administrator
Constructor
Traffic descriptor creation
✓
✓
Traffic descriptor deletion
✓
✓
Traffic descriptor properties
✓
✓
✓
✓
Traffic descriptor list / search
✓
✓
✓
✓
Traffic descriptor modification
✓
✓
Traffic descriptor inventory
✓
✓
✓
✓
LSP Tunnel management LSP Tunnel Management ✓ is Allowed Macro Function
Administrator
Constructor
LSP Tunnel creation
✓
✓
LSP Tunnel deletion
✓
✓
LSP Tunnel allocation
✓
✓
LSP Tunnel de-allocation
✓
✓
LSP Tunnel implementation
✓
✓
LSP Tunnel de-implementation
✓
✓
Operator
Viewer
.................................................................................................................................................................................................................................... 1350 OMS 5-7 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT User Management
MPLS Macro Functions and Default User Profiles
....................................................................................................................................................................................................................................
LSP Tunnel Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
LSP Tunnel constraint adding
✓
✓
LSP Tunnel constraint removing
✓
✓
LSP Tunnel bandwidth load indication
✓
✓
✓
✓
LSP Tunnel list / search
✓
✓
✓
✓
LSP Tunnel inventory
✓
✓
✓
✓
LSP Tunnel extremities
✓
✓
✓
✓
LSP Tunnel constraint list
✓
✓
✓
✓
LSP tunnel modification
✓
✓
LSP Tunnel route
✓
✓
✓
✓
LSP Tunnel Properties
✓
✓
✓
✓
Clipboard
✓
✓
VC LSP management VC LSPManagement ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
VC LSP creation
✓
✓
VC LSP deletion
✓
✓
VC LSP implementation
✓
✓
VC LSP de-implementation
✓
✓
VC LSP commission
✓
✓
VC LSP de-commission
✓
✓
VC LSP list /search
✓
✓
✓
✓
VC LSP extremities
✓
✓
✓
✓
VC LSP modification
✓
✓
VC LSP properties
✓
✓
✓
✓
.................................................................................................................................................................................................................................... 1350 OMS 5-8 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT User Management
Ethernet Macro Functions and Default User Profiles
....................................................................................................................................................................................................................................
Ethernet Macro Functions and Default User Profiles Customer management Customer Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
Customer list / search
✓
✓
✓
✓
Customer create
✓
✓
Customer modify
✓
✓
Customer properties
✓
Customer delete
✓
Inventory of services
✓
✓
✓
✓
✓ ✓
✓
✓
Service management Service Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
Service list
✓
✓
✓
✓
Service create
✓
✓
Service modify
✓
✓
Service properties
✓
Service delete
✓
✓
✓
✓
✓
EVC management EVC Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
EVC list
✓
✓
✓
✓
EVC create
✓
✓
EVC modify
✓
✓
EVC properties
✓
EVC delete
✓
✓
EVC Termination add
✓
✓
EVC Termination delete
✓
✓
✓
✓
✓
.................................................................................................................................................................................................................................... 1350 OMS 5-9 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT User Management
Ethernet Macro Functions and Default User Profiles
....................................................................................................................................................................................................................................
Ethernet Traffic Descriptor management Ethernet Traffic Descriptor Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
Ethernet Traffic Descriptor list
✓
✓
✓
✓
Ethernet Traffic Descriptor create
✓
✓
Ethernet Traffic Descriptor modify
✓
✓
Ethernet Traffic Descriptor properties
✓
Ethernet Traffic Descriptor delete
✓
✓
✓
✓
✓
Ethernet Traffic Classifier management Ethernet Traffic Classifier Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
Ethernet Traffic Classifier list
✓
✓
✓
✓
Ethernet Traffic Classifier create
✓
✓
Ethernet Traffic Classifier modify
✓
✓
Ethernet Traffic Classifier properties
✓
Ethernet Traffic Classifier delete
✓
✓
✓
✓
✓
Ethernet Edge Physical Port management Ethernet Edge Physical Port Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
Ethernet Edge Physical Port properties
✓
✓
✓
✓
Ethernet Edge Physical Port add to EVC
✓
✓
Ethernet Edge Physical Port modification VLANs
✓
✓
.................................................................................................................................................................................................................................... 1350 OMS 5-10 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT User Management
Ethernet Macro Functions and Default User Profiles
....................................................................................................................................................................................................................................
Ethernet Edge Physical Port Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
Ethernet Edge Physical Ports list
✓
✓
✓
✓
Ethernet Transport Segment management Ethernet Transport Segment Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
Inventory of Ethernet Segments
✓
✓
✓
✓
Ethernet Transport segment bandwidth load
✓
✓
✓
✓
Ethernet Transport Segment list
✓
✓
✓
✓
Ethernet Transport Segment properties
✓
✓
✓
✓
Ethernet Segment management Ethernet Segment Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
Ethernet Segment list
✓
✓
✓
✓
Ethernet Segment create
✓
✓
Ethernet Segment modify
✓
✓
Ethernet Segment properties
✓
Ethernet Segment delete
✓
✓
Ethernet Segment configure
✓
✓
Ethernet Constraint add
✓
✓
Ethernet Constraint list
✓
Ethernet Constraint delete
✓
✓
Ethernet VLAN Constraint add
✓
✓
Ethernet VLAN Constraint remove
✓
✓
✓
✓
✓
✓
✓
✓
.................................................................................................................................................................................................................................... 1350 OMS 5-11 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT User Management
Ethernet Macro Functions and Default User Profiles
....................................................................................................................................................................................................................................
Ethernet Segment Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
Ethernet VLAN Constraint list
✓
✓
Ethernet Segment allocate
✓
✓
Ethernet Segment de-allocate
✓
✓
Ethernet Segment implement
✓
✓
Ethernet Segment de-implement
✓
✓
Ethernet Segment show EVC
✓
✓
✓
✓
Ethernet Segment extremities
✓
✓
✓
✓
Ethernet Segment alarm history
✓
✓
✓
✓
Ethernet Segment failure localization
✓
✓
Color Profile Management Color Profile Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
Color Profile list
✓
✓
✓
✓
Color Profile create
✓
✓
Color Profile modify
✓
✓
Color Profile properties
✓
Color Profile delete
✓
✓
✓
✓
✓
Transport Link Management Transport Link Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
Transport Link list
✓
✓
✓
✓
Transport Link properties
✓
✓
✓
✓
Transport Link extremities
✓
✓
✓
✓
Transport Link bandwidth load
✓
✓
✓
✓
.................................................................................................................................................................................................................................... 1350 OMS 5-12 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT User Management
Ethernet Macro Functions and Default User Profiles
....................................................................................................................................................................................................................................
Transport Link Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer ✓
Transport Link list supported Ethernet segments
✓
✓
Transport Link configure
✓
✓
VLAN Type Management VLAN Type Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
VLAN type list
✓
✓
✓
✓
VLAN type creation
✓
✓
VLAN type deletion
✓
✓
VLAN type modification
✓
✓
VLAN type properties
✓
✓
✓
✓
Provider Network Management Provider Network Management ✓ is Allowed Macro Function
Administrator
Constructor
Operator
Viewer
Ethernet Traffic Classifier list
✓
✓
✓
✓
Ethernet Traffic Classifier modify
✓
✓
.................................................................................................................................................................................................................................... 1350 OMS 5-13 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT User Management
Ethernet Macro Functions and Default User Profiles
....................................................................................................................................................................................................................................
.................................................................................................................................................................................................................................... 1350 OMS 5-14 8DG42227DAAA 9.6 Issue 3 December 2012
6
6350 OMS PKT System Log 1 Management
Overview Purpose
This chapter provides the administrator with the conceptual information and the associated tasks that pertain to the system log management of the overall 1350 OMS PKT application. Contents SMF/Commands/Event Log File Overview
6-2
Failure Management Log File Overview
6-5
Trace Management Overview
6-6
................................................................................................................................................................................................................................... 1350 OMS 6-1 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT System Log Management
SMF/Commands/Event Log File Overview
....................................................................................................................................................................................................................................
SMF/Commands/Event Log File Overview SMF/Commands/Event log file locations
The log files for SMF, commands, and/or events are stored in the following locations: •
/usr/Systems/_/maintenance/log
•
/usr/Systems/_/SMF/tools/log/data
•
/usr/Systems/_/ORACLE/databases/dbnml/admin/create
•
/usr/Systems/_/ORACLE/databases/dbnml/admin/logbook
•
/usr/Systems/_/ORACLE/databases/dbnml/admin/bdump
•
/usr/Systems/_/ORACLE/databases/network
•
/usr/Systems/_/TAO/maintenance/trace
•
/usr/Systems/_/databases/dbbmml/data
Log file suffixes
The system log files have the following suffixes: •
.log
•
.data
•
.dataflow
maintenance/log files
The following table lists all files that are in the /usr/Systems/_/maintenance/log directory. Log files in /usr/Systems/_/maintenance/log Filename
Contents
smf.log
Main source of SMF information.
pmc2.log
Main source of PMC information.
JacORB.log
Main source of JABORB information.
PMCStart.log
Information about the startup of the processes managed in PMC.
1354BM.log
Main information source for all IMs processes of the 1350OMS PKT.
EMLStart.log
Information source for the startup of the EML adapter and its proxies.
NMLStart.log
Information source for the startup of the NML adapter and its proxies.
*_dbi.log
Log files for the 1350 OMS PKT for the processes that used the DBI.
.................................................................................................................................................................................................................................... 1350 OMS 6-2 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT System Log Management
SMF/Commands/Event Log File Overview
....................................................................................................................................................................................................................................
Log files in /usr/Systems/_/maintenance/log Filename
Contents
*Gui.log
Main information source for all USMs processes of the 1350 OMS PKT.
ascurusm.log
Information source for the AS USM.
BmAdaptationModifyTrace.log
File logging adaptation information for the dynamic trace level changing tool.
BmCoreModifyTrace.log
File logging bmcore information for the dynamic trace level changing tool.
BmMplsModifyTrace.log
File logging mpls information for the dynamic trace level changing tool.
EotModifyTrace.log
File logging eot information for dynamic trace level changing tool.
allTracesModify.log
File logging information for the dynamic trace level changing tool invoked from the Set BM Parameter GUI.
SMF/tools/log/data file
The /usr/Systems/_/SMF/tools/log/data directory contains the traceDebug.log, which is the log file for debugging. ORACLE/databases/dbnml/admin/create file
The /usr/Systems/_/ORACLE/databases/dbnml/admin/create directory contains the crdb_phase.log, which is the log file that is created during the creation of the database. ORACLE/databases/dbnml/admin/logbook file
The /usr/Systems/_/ORACLE/databases/dbnml/admin/logbook directory contains the start_db.log and stop_db.log files, which is the log files that log
the start and the stopping of the database. ORACLE/admin/dbump file
The /usr/Systems/_/ORACLE/databases/dbnml/admin/bdump directory contains the alert_dbbmml1.log file, which is the log file that contains
information on the ORACLE errors.
.................................................................................................................................................................................................................................... 1350 OMS 6-3 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT System Log Management
SMF/Commands/Event Log File Overview
....................................................................................................................................................................................................................................
ORACLE/databases/network file
The /usr/Systems/_/ORACLE/databases/network directory contains the dbbmml1listener.log file, which is the log file that contains information on the listener process of ORACLE. TAO/maintenance/trace file
The /usr/Systems/_/TAO/maintenance/trace directory contains the ORBStart.log file, which is the log file that contains information on the ORB TAP startup. databases/dbbmml/data
The /usr/Systems/_/databases/dbbmml/data directory contains the redo.log file, which is the log file that contains information on the ORACLE redo log files.
.................................................................................................................................................................................................................................... 1350 OMS 6-4 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT System Log Management
Failure Management Log File Overview
....................................................................................................................................................................................................................................
Failure Management Log File Overview Failure management log file location
The failure management log files are in the /usr/Systems/_/maintenance/trace directory. Failure management log file suffixes
The failure management log files have the following suffixes: •
.err
•
.outerr
.................................................................................................................................................................................................................................... 1350 OMS 6-5 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT System Log Management
Trace Management Overview
....................................................................................................................................................................................................................................
Trace Management Overview Trace management log file location
The failure management log files are in the following directories: •
/usr/Systems/_/maintenance/trace
•
/usr/Systems/_/PMC2/trace
Trace management log file suffixes
The failure management log files have the following suffixes: •
.data
•
.data.lck
•
.dataflow
•
.dataflow.lck
•
.trc
•
trc.old
•
.trace
•
.out
.................................................................................................................................................................................................................................... 1350 OMS 6-6 8DG42227DAAA 9.6 Issue 3 December 2012
7
1350 OMS PKT Parameters 7
Overview Purpose
This chapter provides the administrator with the conceptual information that pertains to the parameters for the 1350 OMS PKT application. Contents Parameter Overview
7-2
1350 OMS PKT Parameters for Core NMA
7-3
1350 OMS PKT Parameters for GUI NMA
7-4
1350 OMS PKT Parameters for MW-INT
7-5
1350 OMS PKT Parameters for Oracle Management
7-6
Set PKT Parameters
7-7
1350 OMS PKT Parameter List
7-9
................................................................................................................................................................................................................................... 1350 OMS 7-1 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT Parameters
Parameter Overview
....................................................................................................................................................................................................................................
Parameter Overview Parameter functional definition
The parameters can be defined for the 1350 OMS PKT application during the initial installation of the application or after the installation of the application through the SMF interface.
.................................................................................................................................................................................................................................... 1350 OMS 7-2 8DG42227DAAA 9.6 Issue 3 December 2012
1350 OMS PKT Parameters
1350 OMS PKT Parameters for Core NMA
....................................................................................................................................................................................................................................
1350 OMS PKT Parameters for Core NMA TMP_NE_UNDER_ Packet > Services. Result: The menu of the Services is shown. ...................................................................................................................................................................................................
2
Select Service. Result: The list window is displayed.
See the following topic in this document: “Description of the list of Services” (p. 18-21) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-20 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Services
Description of the list of Services
....................................................................................................................................................................................................................................
Description of the list of Services Attributes of a Service
The attributes displayed for each service are: •
User Label.
•
Customer User Label.
•
Type (EPL, EVPL, EVPLAN, Extended EVPL, Extended EVPLAN, HSI, Broadcast, BTV).
•
Working State (Normal, Configuring, Removing).
•
Service State (Not in service, In service, Upgrading).
•
Availability Status (Normal, Degraded, In Failure, Not Meaningful).
.................................................................................................................................................................................................................................... 1350 OMS 18-21 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Services
Create a Service
....................................................................................................................................................................................................................................
Create a Service When to use
This function allows creating an Ethernet Service. Related Information
If this creation window is required from the Customer List, the Customer field of the creation window is automatically filled with the selected value. For more information about Services, refer to “Ethernet Service description” (p. 18-17). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • •
At least, one customer must previously be defined. The User Label must be different from the existing ones.
Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Action > Packet > Services > Create Ethernet Service. ...................................................................................................................................................................................................
2
On the Create Service Window. To create a service define following data: •
Enter a Service User label.
•
•
Choose the Customer from the list (this field is automatically filled if this window is required from the Customer List). Select a Service Type (EVPL, EPTL, EPL, EVPLAN, Extended EVPL, Extended EVPLAN, HSI, BTV, or Broadcast). Enter the Reference SLA(string optional).
•
Enter a Comment (optional).
•
...................................................................................................................................................................................................
3
Click Ok.
.................................................................................................................................................................................................................................... 1350 OMS 18-22 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Services
Create a Service
....................................................................................................................................................................................................................................
Result: The service is created.
A correlation with the selected customer is created. Then, the tree area and the Ethernet Service List are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-23 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Services
Service Setup
....................................................................................................................................................................................................................................
Service Setup When to use
The wizard creates and configure at once: Service, EVC, and Ethernet Segment. Related Information
For more information about Services, refer to “Ethernet Service description” (p. 18-17). wizard results
For EVPL, EPTL, EPL, and Extended EVPL connectivity only an Automatic Setup function can be chosen. The wizard creates at once: • • • •
a new service. a Point-to-Point Bi-directional EVC (named " _EVC_ "),. two Ethernet Segments (named " _ESG_A_Z_ " and " _ESG_Z_A_ "). associate a Traffic Descriptor and a Traffic Classifier to Ethernet Segments.
Service states
The Ethernet service is created into the 1350 OMS PKT with the following state: • •
Working State: Normal. Service State: Not In Service.
•
Availability Status: depending on the availability status of created EVC.
A correlation with the selected customer is created. Then, the tree area and the Ethernet Service List are updated. EVC states
One EVC is created into the 1350 OMS PKT with the following attributes: •
User Label: _EVC_.
•
Type: Point to Point.
•
Traffic type: Unicast.
•
Directionality: Bidir.
•
Service Level: Gold.
•
Provisioning State: Defined.
•
Working State: Normal.
A correlation with the Service is created. Then, the EVC is allocated and then, implemented (Provisioning State set to Implemented). At the end, the tree area and the EVC List are updated.
.................................................................................................................................................................................................................................... 1350 OMS 18-24 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Services
Service Setup
....................................................................................................................................................................................................................................
Ethernet Segment states
Two Ethernet Segments are created into the 1350 OMS PKT with the following attributes: • • •
User Label: _ESG_A_Z_ and
_ESG__Z_A_. Subnetwork: NE Subnetwork. Provisioning State: Defined.
•
Working State: Normal.
•
Traffic type: Unicast.
•
Policy Mode: Color Blind.
•
Color Profile: "No associated Color Profile".
Final settings
If the Transport Link is chosen by the user (case NE are not E/FE/GE), that Transport Link is used as a constraint. If the Transport Link is not chosen by the user, the Transport Link must be derived by one of the two ports. Then, the retrieved Transport Link is used as constraint. A correlation with the EVC is created. Then, the two Ethernet Segments are allocated and then, implemented Provisioning State set to Implemented). At the end, the tree area and the Ethernet Segment List are updated. A correlation with the default Traffic Descriptor is created. Correlation is based on bandwidth parameter. At the end, the Service State of the Ethernet service is set to 'In Service'. Recovery consideration in case of error
In case of error, no global rollback is provided. The execution is immediately stopped at the last useful step (and a message is returned to the user to describe the occurred problem. The function can be split in term of other sub functions (create Service, create EVC, ….) and consider each sub function as atomic. so when a sub function fails, the operation fails but for all previous sub functions and no rollback is possible. In case of any negative result, the user has two possibilities: • •
Continue manually supplying all missing operations proceeding step by step. Invoke a manual deletion of the partially built tree starting from the Ethernet Service.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. .................................................................................................................................................................................................................................... 1350 OMS 18-25 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Services
Service Setup
....................................................................................................................................................................................................................................
Conditions
To get a positive result: •
No more service is related to the customer to be deleted.
Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Action > Packet > Services > Create Ethernet Service. Result: The wizard EVPL/EPTL/EPL/Extended EVPL Automatic Setup is shown. Figure 18-2 EVPL/EPTL/EPL/Extended EVPL service creation wizard
...................................................................................................................................................................................................
2
In the panel insert: •
Enter a Service User label.
•
Choose the Customer by using the sensitive help (this field is automatically filled if this window is required from the Customer List). Select the Service Type (EPTL, EVPL, EPL, or Extended EVPL). If you insert EVPL or Extended EVPL Service Type. Refer to: “Task for EVPL or Extended EVPL” (p. 18-28).
•
.................................................................................................................................................................................................................................... 1350 OMS 18-26 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Services
Service Setup
....................................................................................................................................................................................................................................
• • • •
Select a NAD Value from the list. Enter the Reference SLA (a string) (optional). The Class of Service is Guaranteed. Enter a Comment (optional).
•
Click Next. Result: The wizard goes to the next step.
...................................................................................................................................................................................................
3
Fill the following fields: •
Select Resources section (by using the sensitive help and menu).
•
Select a NE or ENE for the "A" end by using sensitive help.
•
Select an Edge Port A by using sensitive help.
.................................................................................................................................................................................................................................... 1350 OMS 18-27 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Services
Service Setup
....................................................................................................................................................................................................................................
• • • • • •
Select a NE or ENE for the "Z" end by using sensitive help. Select an Edge Port Z by using sensitive help. Select if free Transport Link (by checking the box). Select the Transport Link (by using the sensitive help; in the case of E/FE/GE NE, the Transport Link is automatically determined by the 1350 OMS PKT). Click Next. On the next panel click the Finish button. Result: The wizard creates and configure at once: Service, EVC, and Ethernet
Segment. E................................................................................................................................................................................................... N D O F S T E P S
Task for EVPL or Extended EVPL ...................................................................................................................................................................................................
1
If you insert EVPL or Extended EVPL Service Type, the following panel is displayed: •
Enter a Service User label.
• • •
Choose the Customer by using the sensitive help (this field is automatically filled if this window is required from the Customer List). Select the Service Type (EVPL, Extended EVPL). Enter the Reference SLA (a string) (optional).
•
Enter a Comment (optional).
•
In the Traffic Descriptor tab: The Traffic Descriptor can be selected from the already created list, or checking the box Create, insert the Traffic Descriptor characteristics: – Class of Service: Guaranteed, Regulated, Best Effort. –
•
•
CIR, PIR, CES, PBS values.
In the Traffic Classifier tab: The Traffic Classifier can be selected from the already created list, or checking the box Create, insert the Traffic Classifier characteristics: –
Vlan Id.
–
Priority Id.
–
Priority Max.
–
Vlan Max.
Click Next. Result: The wizard goes to the next step.
...................................................................................................................................................................................................
2
Fill Resources section (by using the sensitive help and menu): this panel has the same layout as the EPLINE Service panel. On the panel click the Finish button.
.................................................................................................................................................................................................................................... 1350 OMS 18-28 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Services
Service Setup
....................................................................................................................................................................................................................................
Result: The wizard creates and configure at once: Service, EVC, and Ethernet Segment. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-29 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Services
Modify a Service
....................................................................................................................................................................................................................................
Modify a Service When to use
The function modifies Service characteristics. Related Information
For more information about Services, refer to “Ethernet Service description” (p. 18-17). The service modification gives the possibility to modify one or all the following parameters: •
Service User Label.
• •
Service Type (only if no EVCs are currently associated to the Ethernet service).
•
Comment.
Reference SLA.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • •
No operation is pending on the Ethernet service. If modified, the new User Label must be different from the existing ones.
Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Services. ...................................................................................................................................................................................................
2
On the Service List Window, select the Service to modify. Click the right mouse button and select Modify on the popup menu. ...................................................................................................................................................................................................
3
The Modify Service window is displayed. To modify an Ethernet service: •
Enter a new User Label (optional).
•
Modify the Service Type (optional).
.................................................................................................................................................................................................................................... 1350 OMS 18-30 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Services
Modify a Service
....................................................................................................................................................................................................................................
• •
Modify the Reference SLA (optional). Modify the Comment (optional).
...................................................................................................................................................................................................
4
Click Ok. Result: The service is modified.
If the Service User Label is modified, after confirmation of the modification: the tree area (in customer section) and the Service List are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-31 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Services
Delete a Service
....................................................................................................................................................................................................................................
Delete a Service When to use
This function consists in deleting an Ethernet service from the 1350 OMS PKT supervision. Related Information
For more information about Services, refer to “Ethernet Service description” (p. 18-17). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
No more EVC related to the Service to be deleted.
Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Services. ...................................................................................................................................................................................................
2
On the Service List Window, select the service to delete. Select Action > Service > Delete from the Action menu. ...................................................................................................................................................................................................
3
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: The service is deleted.
After confirmation, the services are removed. The Service List is updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-32 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Services
Get details of the Service
....................................................................................................................................................................................................................................
Get details of the Service When to use
This function gets information about an Ethernet service. Related Information
For more information about Services, refer to “Ethernet Service description” (p. 18-17). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Services. ...................................................................................................................................................................................................
2
On the Service List Window, select a Service. Select Properties from the popup menu activated using the mouse right button.
.................................................................................................................................................................................................................................... 1350 OMS 18-33 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Services
Get details of the Service
....................................................................................................................................................................................................................................
Result: The Properties window is displayed.
See the following topic in this document: “Details of a Service” (p. 18-35) Figure 18-3 Ethernet Service Properties window
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-34 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Services
Details of a Service
....................................................................................................................................................................................................................................
Details of a Service Attributes of a Service
The attributes displayed for each service are: •
Id
• •
User Label.
•
Customer User Label.
•
Service Type (EPL, EVPL, EVPLAN, Extended EVPL, Extended EVPLAN, HSI, Broadcast, BTV).
•
Reference SLA
•
Comment
•
Action Type
•
Action Date
• •
Working State (Normal, Configuring, Removing).
•
Availability Status (Normal, Degraded, In Failure, Not Meaningful).
•
ETS ID label
•
ETS LABEL label
Customer Id label User Label.
Service State (Not in service, In service, Upgrading).
.................................................................................................................................................................................................................................... 1350 OMS 18-35 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Services
Display the Services of a Customer
....................................................................................................................................................................................................................................
Display the Services of a Customer When to use
The function lists all the Ethernet services belonging to a Customer. Related Information
The list can be required in different manners: • • •
If the list is required from Main Menu, all the Ethernet Services are displayed. If the list is required from the Customer List, only the Ethernet services associated to the selected customer are displayed. If the list is required from Ethernet Transport Link List, only the Ethernet services associated to the selected Ethernet Transport Links are displayed.
For more information about Services, refer to “Ethernet Service description” (p. 18-17). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The menu of the Services is shown. ...................................................................................................................................................................................................
2
Select Service. Result: The list window is displayed.
See the following topic in this document: “Description of the list of Services” (p. 18-21) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-36 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Overview about ETS Ethernet Virtual Connections
....................................................................................................................................................................................................................................
Managing ETS Ethernet Virtual Connections (EVC) Overview about ETS Ethernet Virtual Connections EVC description
The Ethernet Virtual Connection (EVC) specifies the connectivity among two or more Ethernet Edge Terminations (UNIs). If they belong to the same Metro Ethernet Network, the association of Ethernet Edge Termination is implicitly specified, too. The following main rules govern the EVC: The EVC is common to Connection Oriented and Connection Less management • • •
a frame sent in the EVC can be delivered to one or more egress EVC Termination (Ethernet Edge Termination). a frame sent in the EVC cannot be delivered back to the ingress EVC Termination. a frame sent in the EVC cannot be delivered to another EVC.
Every EVC is terminated by Edge Ports. The same Edge Port can be used by different EVCs. EVC topologies
The EVC can be used in different topologies and can have different properties. In particular, the EVC can be: • •
•
Point-to-point (PtoP): It connects exactly two points (that is, two Ethernet Edge Ports). It can be unidirectional or bidirectional. It supports only Unicast traffic. Rooted-multipoint (RMP): A multipoint EVC in which each UNI is designated as either a Root or a Leaf. Ingress Service Frames at a Root UNI can be delivered to one or more of any of the other UNIs in the EVC. Ingress Service Frames at a Leaf UNI can only be delivered to one or more Root UNIs in the EVC. Multipoint-to-multipoint (MPtoMP): It connects two or more points. It can be unidirectional or bidirectional. It supports only traffic Unicast.
The Role of Edge Port
Depending on the EVC topology, every Edge Port used by a given EVC assumes a specific Role. • • •
In PtoP topology, the two ports assume the "both" role (that is, root + leaf). In PtoMP topology, one port assumes the "root" role while all the others assume the "leaf" role. In MPtoMP topology, all ports assume the "both" role (that is, root + leaf).
.................................................................................................................................................................................................................................... 1350 OMS 18-37 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Overview about ETS Ethernet Virtual Connections
....................................................................................................................................................................................................................................
The following figure summarizes the role assumed by Edge Port for different EVCs. Figure 18-4 EVCs and Edge Ports relationships
.................................................................................................................................................................................................................................... 1350 OMS 18-38 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Resource Reservation for Private Services
....................................................................................................................................................................................................................................
Resource Reservation for Private Services Overview
When the user defines a new Service Type, an important aspect is to define the expected usage of physical resources. In particular, the management of Resource Sharing attribute introduced at EVC level. This parameter defines the global policy, in terms of privacy/sharing of UNI (Edge Ports) and Transport Links. To manage the issue related to Shared or Dedicated Transport Link usage, the Resource Sharing attribute at EVC Level can assume following values. •
Full: the EVC Service under definition can use every resource without any restriction.
•
Private UNI: the EVC Service under definition must use Private UNI, that is UNI
• •
uniquely used by that EVC Service. Private Link: The EVC Service under definition must use Private Links, that is Transport Links uniquely used by that EVC Service. Private UNI and LINK: The EVC Service under definition must use Private UNI and Private Links, that is chosen Transport Links and UNIs are uniquely used by that EVC Service.
Resource Sharing
The following table reports the possible choices of Resource Sharing respect to Service Type and respect to crossed technological domain. Service Type.
Resource Sharing. Full.
Private UNI.
Private Link.
Private UNI and Link.
UNKNOWN. EVPL.
ETS. Provider Bridge.
EPTL.
ETS.
EPL.
ETS. Provider Bridge.
EVPLAN.
Extended EVPL.
Extended EVPLAN.
ETS.
ETS.
Provider Bridge.
Provider Bridge.
ETS.
ETS.
ETS.
ETS.
Provider Bridge.
Provider Bridge.
Provider Bridge.
Provider Bridge.
ETS.
ETS.
ETS.
ETS.
Provider Bridge.
Provider Bridge.
Provider Bridge.
Provider Bridge.
.................................................................................................................................................................................................................................... 1350 OMS 18-39 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Resource Reservation for Private Services
....................................................................................................................................................................................................................................
Service Type. HSI.
Resource Sharing. ETS. Provider Bridge.
BTV.
ETS. Provider Bridge.
BROADCAST.
ETS.
ETS.
Connection Oriented Service Type relations Table 18-1
Connection Oriented Service Type relations
Service Type.
Type.
Traffic Type.
Resource Sharing.
EVPL.
Point-to-Point.
Unicast.
Full.
EPTL.
Point-to-Point.
Unicast.
Private UNI and Link.
EPL.
Point-to-Point.
Unicast.
Private UNI.
EVPLAN.
Any-to-Any.
Unicast.
Full. Private UNI. Private UNI and Link. 1
Extended EVPL.
Point-to-Point.
Unicast.
.
Full. Private UNI. Private UNI and Link. 1
Extended EVPLAN.
Any-to-Any.
Unicast.
Full.
Rooted Multipoint.
Multicast.
Private UNI.
1
HSI.
Private UNI and Link.
.
Rooted Multipoint.
1
Unicast.
Rooted Multipoint.
Rooted Multipoint.
Full.
.
Unicast.
Full.
Multicast. 1
Broadcast.
.
Multicast. 1
BTV.
.
.
Unicast.
Full. Private UNI. Private UNI and Link. 1
.
.................................................................................................................................................................................................................................... 1350 OMS 18-40 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Resource Reservation for Private Services
....................................................................................................................................................................................................................................
Notes:
1.
This case allows a selection of the parameters.
Frame delivery
Frame delivery types are the following: •
•
•
Unicast Service Frame Delivery: MAC ACL configuration on Edge Ports can
influence the behavior. It verifies if the MAC ACL can be used to filter all unicast address. For Connection Oriented EVCs transporting Unicast frames, the default value is assumed always equal to Deliver Unconditionally. For Connection Less EVCs, the default value is Deliver Conditionally (depending on filtering set on UNI). The default value is modifiable and it does not affect real traffic due to the fact that MAC ACL is not known to 1350 OMS PKT. The MAC ACL is managed through Navigation, The full compliancy is in the user hands. Multicast Service Frame Delivery: MAC ACL configuration on Edge Ports can influence the behavior. It must be verified if the MAC ACL can be used to filter all multicast address. For Connection Oriented EVCs transporting Multicast Frames, the default value is assumed always equal to Deliver Unconditionally. For Connection Less EVCs or when IGMP is used, the default value is Deliver Conditionally (depending on filtering set on UNI). The MAC ACL is managed through Navigation. The full compliancy is in the user hands. Broadcast Service Frame Delivery: MAC ACL configuration on Edge Ports can influence the behavior. It must be verified if the MAC ACL can be used to filter all broadcast address. For Connection Oriented EVCs, the default value is assumed always equal to Deliver Unconditionally. For Connection Less EVCs, the default value is Conditional (depending on filtering set on UNI). The MAC ACL is managed through Navigation. The full compliancy is in the user hands.
C-VLAN and CoS Preservation
C-VLAN and CoS Preservation: •
C-VLAN Preservation ensures that each packet exiting the EVC has the same VLAN
Id information that it had when it entered the EVC. The following relation is respected: VLAN Id Egress UNI = VLAN IdIngress UNI. C-VLAN Preservation attribute must be defined at EVC definition and is modifiable
before EVC allocation. •
C-VLAN CoS Preservation ensures that each packet exiting the EVC has the same Priority Bits information that it had when it entered the EVC.
The following relation is respected: Priority Bit at ingress = Priority Bit at egress .
.................................................................................................................................................................................................................................... 1350 OMS 18-41 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Display the list of Connection Oriented EVC
....................................................................................................................................................................................................................................
Display the list of Connection Oriented EVC When to use
The Ethernet Virtual Connection List window presents all the EVCs and their attributes. Related Information
This list can be required also from the Ethernet Service List, from the Ethernet Segment List, or from the Ethernet Transport Link List. In These cases, only the EVCs associated to the selected object are displayed. For more information about EVC, refer to “EVC description” (p. 18-37). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUIMain view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The menu of the Services is shown. ...................................................................................................................................................................................................
2
Select ConnectionOriented > ETS EVCs. Result: The list window is displayed.
See the following topic in this document: “Description of the list of EVCs” (p. 18-43) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-42 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Description of the list of EVCs
....................................................................................................................................................................................................................................
Description of the list of EVCs Attributes of a EVC
The attributes displayed for each EVC are: •
User Label.
•
Ethernet Service User Label.
•
Type (Point to point, Routed multi-point, Any to any).
•
Traffic Type (Unicast, Multicast).
•
Working State (Normal, Configuring, Allocating, De-allocating, Implementing,
•
De-implementing, Commissioning, De-commissioning, Termination adding, Termination removing, Constraint adding, Constraint removing, removing). Provisioning State (Defined, Partially allocated, Allocated, Partially implemented, Implemented, Commissioned). Service State (Not in Service, In Service).
• •
Availability Status (Normal, Degraded, In Failure, Not Meaningful).
.................................................................................................................................................................................................................................... 1350 OMS 18-43 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Create a Connection Oriented EVC
....................................................................................................................................................................................................................................
Create a Connection Oriented EVC When to use
This function allows creating a Connection Oriented Ethernet Virtual Connection. Related Information
For more information about EVC, refer to “EVC description” (p. 18-37). If the EVC Creation window is required from the Service List, the Ethernet Service field is filled with the selected value. When no Ethernet Service reference is supplied a dummy service is created. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • •
The User Label must be not in use. Only one Root termination is authorized.
•
The EVC Type must be compatible with the service type of the associated Ethernet Service. The EVC Type must be compatible with the selected Traffic Type. The role of each EVC termination must be compatible with the EVC Type.
• • Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Action > Packet > Services > ConnectionOriented > Create EVC. Result: The EVC Creation window is displayed. ...................................................................................................................................................................................................
2
On the General Panel insert following data: •
Enter an EVC User Label.
•
Insert the Ethernet Service.
.................................................................................................................................................................................................................................... 1350 OMS 18-44 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Create a Connection Oriented EVC
....................................................................................................................................................................................................................................
•
Two different choices are possible: – Choose an already created Ethernet Service selecting it from the available list. The list is displayed clicking in the field. If this window is required from the Service List, this field is automatically filled. – Choose a Service Type (EVPL, EPTL, EPL, EVPLAN, Extended EVPL, Extended EVPLAN, HSI, BTV, Broadcast). The parameters: Type, Traffic Type, and Resource Sharing are assigned according to the chosen Service Type as indicated in: Table 18-1, “Connection Oriented Service Type relations ” (p. 18-40). Execute the following steps: – Select a Service Level (Premium, Gold, Silver, Bronze). –
Resource Sharing: (Full, Private UNI, Private Link, Private UNI and LINK).
See: “Overview” (p. 18-39). •
C-VLAN Preservation: check it to keep the VLAN Id through the EVC.
(see: “C-VLAN and CoS Preservation” (p. 18-41)). •
C-VLAN CoS Preservation: check it to keep the Priority Bits through the EVC.
(see: “C-VLAN and CoS Preservation” (p. 18-41)). •
Enter a NAD value for the EVC.
•
Enter a Comment (optional).
•
Enter an External Mark (optional). It can be used to identify external systems having relations with the EVC (for example an ownership).
...................................................................................................................................................................................................
3
On the Detail Panel. Set the Frame Delivery: •
•
Select the Frame Delivery parameters (see “Frame delivery” (p. 18-41)) –
Unicast Service Frame Delivery.
–
Multicast Service Frame Delivery.
– Broadcast Service Frame Delivery. Select the standard Vlan Type (8100).
...................................................................................................................................................................................................
4
On PM Panel. Select the following parameters • • •
Under PM: select True if the Performance Monitoring is applied on the EVC, if true is selected the following parameters are activated. Granularity: select the required type of granularity (15 min, 1 h, 24 h, Not Meaningful). Report Output Type: select the desired output type (No Report, CSV Delta, CSV Raw, Performance Counter Tabular, Performance Counter Graphical, Delta Counter Tabular, Delta Counter Graphical, Not Meaningful).
.................................................................................................................................................................................................................................... 1350 OMS 18-45 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Create a Connection Oriented EVC
....................................................................................................................................................................................................................................
•
Report Output Frequency: select the desired frequency for the output report (15 min, 1 h, 24 h, 1 Week, 1 Month, 1 Year, Not Meaningful).
•
Report Output Name: type a significant name for the output report.
•
Policy: select the policy for the output report management (Keep, Purge on Stop, Purge on Delete, Not Meaningful).
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-46 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Modify an ETS EVC
....................................................................................................................................................................................................................................
Modify an ETS EVC When to use
The function modifies EVC characteristics. Related Information
For more information about EVC, refer to “EVC description” (p. 18-37). The EVC modification function allow the user to modify: • • • •
EVC User Label. C-VLAN Preservation (Yes/No). C-VLAN CoS Preservation (Yes/No). NAD Value.
• •
Comment. External Mark.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
If the User Label is modified, the new User Label must be different from other already used by another EVC.
Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > ETS EVCs. ...................................................................................................................................................................................................
2
Select the EVC to modify in the list. ...................................................................................................................................................................................................
3
Click the right mouse button and select from the popup menu Modify.
.................................................................................................................................................................................................................................... 1350 OMS 18-47 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Modify an ETS EVC
....................................................................................................................................................................................................................................
Result: The EVC modification window is displayed. Figure 18-5 EVC Modification window
...................................................................................................................................................................................................
4
On the modification window to modify an EVC. Following parameters can be modified: •
Enter a new User Label (optional).
•
C-VLAN Preservation: check it to keep the VLAN Id through the EVC.
(see: “C-VLAN and CoS Preservation” (p. 18-41)). •
C-VLAN CoS Preservation: check it to keep the Priority Bits through the EVC.
(see: “C-VLAN and CoS Preservation” (p. 18-41)). •
Modify the NAD Value.
•
Modify the Comment (optional).
•
Modify the External Mark (optional).
Then, the EVC list, and the opened graphical views are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-48 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Delete an ETS EVC
....................................................................................................................................................................................................................................
Delete an ETS EVC When to use
This function allows deleting an ETS EVC from the 1350 OMS PKT supervision. Related Information
For more information about EVC, refer to “EVC description” (p. 18-37). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • • •
The provisioning state of the EVC must be defined. No operation is pending on the EVC. No Ethernet Segment is referring the EVC.
Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > ETS EVCs. ...................................................................................................................................................................................................
2
Select the element to delete in the list. ...................................................................................................................................................................................................
3
Click the right mouse button and select from the popup menu Action from ETS EVC > Delete. Result: A confirmation box is displayed. ...................................................................................................................................................................................................
4
Confirm the deletion operation. After confirmation: • • •
the 1350 OMS PKT checks that no Ethernet Segment is referring the EVCs. the EVCs are dissociated from the related service (if no more EVC are associated to the service, the service is also removed). the EVCs are removed.
.................................................................................................................................................................................................................................... 1350 OMS 18-49 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Delete an ETS EVC
....................................................................................................................................................................................................................................
The EVC list, and the opened graphical views are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-50 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Get the EVC properties
....................................................................................................................................................................................................................................
Get the EVC properties When to use
This function gets information about an Ethernet Virtual Connection. Related Information
For more information about EVC, refer to “EVC description” (p. 18-37). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > ETS EVCs. ...................................................................................................................................................................................................
2
Select an element in the list. ...................................................................................................................................................................................................
3
Click the right mouse button and select from the popup menu Properties.
.................................................................................................................................................................................................................................... 1350 OMS 18-51 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Get the EVC properties
....................................................................................................................................................................................................................................
Result: The EVC properties window is displayed.
See the following topic in this document: “Details of a EVC” (p. 18-53) Figure 18-6 EVC Properties window
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-52 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Details of a EVC
....................................................................................................................................................................................................................................
Details of a EVC Attributes of an EVC
The attributes displayed for each EVC are: •
Id.
•
User Label.
•
Service Id Label.
•
Ethernet Service User Label.
•
Type (Point to point, Routed multi-point, Any to any).
•
Traffic Type (Unicast, Multicast).
•
Directionality.
•
Service Level.
• •
Comment.
•
Action Type.
•
Action Date.
•
Working State (Normal, Configuring, Allocating, De-allocating, Implementing, De-implementing, Commissioning, De-commissioning, Termination adding, Termination removing, Constraint adding, Constraint removing, removing).
•
Provisioning State (Defined, Partially allocated, Allocated, Partially implemented, Implemented, Commissioned).
•
Service State (Not in Service, In Service).
•
Availability Status (Normal, Degraded, In Failure, Not Meaningful).
•
ETS Id Label.
•
ETS LABEL label.
•
Vlan Type.
•
Resource sharing.
• •
Domain Id.
•
VLAN distribution.
•
S-VLAN Id.
External Mark.
Domain.
.................................................................................................................................................................................................................................... 1350 OMS 18-53 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Allocate ETS EVC
....................................................................................................................................................................................................................................
Allocate ETS EVC When to use
This function allocates a Connection Oriented EVC. Related Information
For more information about EVC, refer to “EVC description” (p. 18-37). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the menu path Search > Packet > Services > Connection Oriented (ETS) > ETS EVCs. Result: The ETS EVC list is displayed. ...................................................................................................................................................................................................
2
Select the EVC in the list and follow the path Action > ETS EVC > Allocate. Result: The confirmation box is displayed. ...................................................................................................................................................................................................
3
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: The EVC is allocated.
The EVC list, the tree area, and the opened graphical views are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-54 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Deallocate ETS EVC
....................................................................................................................................................................................................................................
Deallocate ETS EVC When to use
This function deallocates a Connection Oriented EVC. Related Information
For more information about EVC, refer to “EVC description” (p. 18-37). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the menu path Search > Packet > Services > Connection Oriented (ETS) > ETS EVCs. Result: The ETS EVC list is displayed. ...................................................................................................................................................................................................
2
Select the EVC in the list and follow the path Action > ETS EVC > Deallocate. Result: The confirmation window is displayed. ...................................................................................................................................................................................................
3
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: The EVC is deallocated.
The EVC list, the tree area, and the opened graphical views are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-55 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Implement ETS EVC
....................................................................................................................................................................................................................................
Implement ETS EVC When to use
This function implements a Connection Oriented EVC. Related Information
For more information about EVC, refer to “EVC description” (p. 18-37). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the menu path Search > Packet > Services > Connection Oriented (ETS) > ETS EVCs. Result: The ETS EVC list is displayed. ...................................................................................................................................................................................................
2
Select the EVC in the list and follow the path Action > ETS EVC > Implement. Result: The confirmation box is displayed. ...................................................................................................................................................................................................
3
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: The EVC is Implemented.
The EVC list, the tree area, and the opened graphical views are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-56 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Deimplement ETS EVC
....................................................................................................................................................................................................................................
Deimplement ETS EVC When to use
This function deimplements a Connection Oriented EVC. Related Information
For more information about EVC, refer to “EVC description” (p. 18-37). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the menu path Search > Packet > Services > Connection Oriented (ETS) > ETS EVCs. Result: The ETS EVC list is displayed. ...................................................................................................................................................................................................
2
Select the EVC in the list and follow the path Action > ETS EVC > Deimplement. Result: The confirmation window is displayed. ...................................................................................................................................................................................................
3
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: The EVC is deallocated.
The EVC list, the tree area, and the opened graphical views are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-57 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Commission ETS EVC
....................................................................................................................................................................................................................................
Commission ETS EVC When to use
This function commissions a Connection Oriented EVC. Related Information
For more information about EVC, refer to “EVC description” (p. 18-37). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the menu path Search > Packet > Services > Connection Oriented (ETS) > ETS EVCs. Result: The ETS EVC list is displayed. ...................................................................................................................................................................................................
2
Select the EVC in the list and follow the path Action > ETS EVC > Commission. Result: The confirmation box is displayed. ...................................................................................................................................................................................................
3
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: The EVC is commissioned.
The EVC list, the tree area, and the opened graphical views are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-58 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Decommission ETS EVC
....................................................................................................................................................................................................................................
Decommission ETS EVC When to use
This function decommissions a Connection Oriented EVC. Related Information
For more information about EVC, refer to “EVC description” (p. 18-37). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the menu path Search > Packet > Services > Connection Oriented (ETS) > ETS EVCs. Result: The ETS EVC list is displayed. ...................................................................................................................................................................................................
2
Select the EVC in the list and follow the path Action > ETS EVC > Decommission. Result: The confirmation window is displayed. ...................................................................................................................................................................................................
3
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: The EVC is decommissioned.
The EVC list, the tree area, and the opened graphical views are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-59 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
List the EVC terminations
....................................................................................................................................................................................................................................
List the EVC terminations When to use
The EVC Termination List window presents all the terminations of the selected EVC and their attributes. Related Information
If this list is required from the Ethernet Service List or from the EVC List, only the EVC terminations associated to the selected item are displayed. For more information about EVC, refer to “EVC description” (p. 18-37). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > ETS EVCs. ...................................................................................................................................................................................................
2
Select the EVC to modify in the list. ...................................................................................................................................................................................................
3
Select Search > Inventory from ETS EVC > List EVC Terminations. Result: The list of the EVC terminations is displayed.
See the following topic in this document: “Description of the list of terminations” (p. 18-61) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-60 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Description of the list of terminations
....................................................................................................................................................................................................................................
Description of the list of terminations Attributes of a termination
The attributes displayed for each EVC termination are: •
EVC Termination User Label.
•
Rate.
•
Network Element.
•
EVC User Label.
•
Role (Root, Leaf, Both).
•
Usage State.
•
Ethernet Service.
•
VLAN Type.
.................................................................................................................................................................................................................................... 1350 OMS 18-61 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Delete an EVC Termination
....................................................................................................................................................................................................................................
Delete an EVC Termination When to use
This function allows deleting an ETS EVC termination from the 1350 OMS PKT supervision. Related Information
For more information about EVC, refer to “EVC description” (p. 18-37). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • •
The specified EVC termination is not used as Ethernet Segment extremity. No operation is pending on the selected EVC termination.
Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > ETS EVCs. ...................................................................................................................................................................................................
2
Select the element to delete in the list. ...................................................................................................................................................................................................
3
Click the right mouse button and select from the popup menu Action from ETS EVC Termination > Delete. Result: A confirmation box is displayed. ...................................................................................................................................................................................................
4
Confirm the deletion operation. After confirmation: • •
the EVC terminations are dissociated from the related EVC. the EVC terminations are removed.
The EVC Termination list is updated. E................................................................................................................................................................................................... N D O F S T E P S .................................................................................................................................................................................................................................... 1350 OMS 18-62 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Get the EVC termination properties
....................................................................................................................................................................................................................................
Get the EVC termination properties When to use
This function shows all the termination attributes. Related Information
For more information about EVC, refer to “EVC description” (p. 18-37). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > ETS EVCs. ...................................................................................................................................................................................................
2
Select the EVC in the list. ...................................................................................................................................................................................................
3
Follow the menu path Search > Inventory from ETS EVC > List EVC Terminations. ...................................................................................................................................................................................................
4
Select the termination in the list. ...................................................................................................................................................................................................
5
Click the right mouse button and select from the popup menu Properties.
.................................................................................................................................................................................................................................... 1350 OMS 18-63 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Get the EVC termination properties
....................................................................................................................................................................................................................................
Result: The properties window is displayed.
See the following topic in this document: “Details of a Termination” (p. 18-65) Figure 18-7 EVC Termination Properties window
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-64 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Details of a Termination
....................................................................................................................................................................................................................................
Details of a Termination Attributes of a Termination
The attributes displayed for each EVC termination are: •
EVC Termination User Label.
•
Rate.
•
Network Element.
•
EVC User Label.
•
Role (Root, Leaf, Both).
•
Usage State.
•
Ethernet Service.
•
VLAN Type.
.................................................................................................................................................................................................................................... 1350 OMS 18-65 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Add an EVC termination
....................................................................................................................................................................................................................................
Add an EVC termination When to use
This function add a termination to an EVC. Related Information
In case of Connection Oriented EVCs, the bandwidth profiles defined for each EVC termination have to be intended in the following way: • •
It represents the bandwidth profile for the traffic at "ingress" of that UNI (Profile is immediately checked). It must be reflected to the corresponding Ethernet Segments (that is to the Ethernet Segment starting from that UNI).
The affects along the Ethernet Segment route is evaluated at Ethernet Segment allocation. This function consists in adding a new termination to an existing EVC. For more information about EVC, refer to “EVC description” (p. 18-37). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • • • •
No operation is pending on the selected EVC. The EVC provisioning state must be set to Defined. EVC Termination Role must be congruent with the EVC topology. Only one termination can have "Root" role.
Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > ETS EVCs. ...................................................................................................................................................................................................
2
Select the EVC in the list. ...................................................................................................................................................................................................
3
Follow the menu path Action > ETS EVC > Add Connection Oriented EVC Termination.
.................................................................................................................................................................................................................................... 1350 OMS 18-66 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Add an EVC termination
....................................................................................................................................................................................................................................
Result: The add termination window is displayed. Figure 18-8 Add EVC Termination window
...................................................................................................................................................................................................
4
To add a termination: •
Select a NE or ENE by using sensitive help.
•
Select an Edge Port by using sensitive help.
•
Select the termination Role (Root, Leaf, Both).
...................................................................................................................................................................................................
5
Click Ok button. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-67 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
EVC Fault Localization
....................................................................................................................................................................................................................................
EVC Fault Localization When to use
This function displays the localization of the fault present for the selected EVC. Related Information
This function is active when EVC or Ethernet Segment associated are implemented. For more information about EVC, refer to “EVC description” (p. 18-37). For details about Fault Localization, see: “Fault Localization” (p. 11-69). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > ETS EVCs. ...................................................................................................................................................................................................
2
Select the EVC and issue Search > Fault Localization. Result: The list window is displayed.
See the following topic in this document: “Description of the list of Fault Localization” (p. 18-69) The list is not refreshed automatically, click Actualize button to refresh it. ...................................................................................................................................................................................................
3
Selecting an item in the Fault Localization list, using the popup menu the user visualize the alarm list of the selected item. Select one EVC in the list and click Search > External Navigation to > AS . Result: The Fault Management window is displayed with selected EVC alarm list.
See the following topic in this document: “Description of the list of Alarms” (p. 18-70) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-68 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Description of the list of Fault Localization
....................................................................................................................................................................................................................................
Description of the list of Fault Localization Attributes of a Fault Localization
The Fault Localization window displays: •
The User Label of the alarmed entity.
•
The Entity Type of the alarmed entity.
•
The Network Element (if any) of the alarmed entity.
•
The Alarm Status.
•
The Event Date.
•
The Operator Label (if any). Note: The list is not refreshed automatically, click Actualize button to refresh it.
.................................................................................................................................................................................................................................... 1350 OMS 18-69 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Description of the list of Alarms
....................................................................................................................................................................................................................................
Description of the list of Alarms Attributes of an Alarm
The alarm list window displays: •
The Perceived Severity.
•
The Event Date & Time.
•
The Friendly Name.
•
The Alarm Type.
•
The Probable Cause.
.................................................................................................................................................................................................................................... 1350 OMS 18-70 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Start PM on an EVC
....................................................................................................................................................................................................................................
Start PM on an EVC When to use
This function starts Performance Monitoring (PM) on a Connection Oriented EVC or Connection Less EVC. Related Information
For more information about EVC, refer to “EVC description” (p. 18-37). For more information about PM, refer to “Quality of service: PM management ” (p. 11-69). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The Service menu is shown. ...................................................................................................................................................................................................
2
Select Connection Oriented (ETS) > ETS EVCs or Connection Less (Bridge) > Bridge EVCs. Result: The EVC list is displayed. ...................................................................................................................................................................................................
3
Select the EVC in the list and follow the path Action > EVC > Start PM. Result: The PM is started on the EVC. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-71 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Stop PM on an EVC
....................................................................................................................................................................................................................................
Stop PM on an EVC When to use
This function Stops Performance Monitoring (PM) on a Connection Oriented EVC or Connection Less EVC. Related Information
For more information about EVC, refer to “EVC description” (p. 18-37). For more information about PM, refer to “Quality of service: PM management ” (p. 11-69). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The Service menu is shown. ...................................................................................................................................................................................................
2
Select Connection Oriented (ETS) > ETS EVCs or Connection Less (Bridge) > Bridge EVCs. Result: The EVC list is displayed. ...................................................................................................................................................................................................
3
Select the EVC in the list and follow the path Action > EVC > Stop PM. Result: The PM is Stopped on the EVC. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-72 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Synchronize PM on an EVC
....................................................................................................................................................................................................................................
Synchronize PM on an EVC When to use
This function Synchronizes Performance Monitoring (PM) on a Connection Oriented EVC or Connection Less EVC. Related Information
For more information about EVC, refer to “EVC description” (p. 18-37). For more information about PM, refer to “Quality of service: PM management ” (p. 11-69). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The Service menu is shown. ...................................................................................................................................................................................................
2
Select Connection Oriented (ETS) > ETS EVCs or Connection Less (Bridge) > Bridge EVCs. Result: The EVC list is displayed. ...................................................................................................................................................................................................
3
Select the EVC in the list and follow the path Action > EVC > Synchronize PM. Result: The PM is Synchronized on the EVC. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-73 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
Show PM on an EVC
....................................................................................................................................................................................................................................
Show PM on an EVC When to use
This function Shows Performance Monitoring (PM) on a Connection Oriented EVC or Connection Less EVC. Related Information
For more information about EVC, refer to “EVC description” (p. 18-37). For more information about PM, refer to “Quality of service: PM management ” (p. 11-69). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The Service menu is shown. ...................................................................................................................................................................................................
2
Select Connection Oriented (ETS) > ETS EVCs or Connection Less (Bridge) > Bridge EVCs. Result: The EVC list is displayed. ...................................................................................................................................................................................................
3
Select the EVC in the list and follow the path Search > EVC > Show > PM. Result: The PM related to the EVC is shown. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-74 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing ETS Ethernet Virtual Connections (EVC)
View the Routing Display on an EVC
....................................................................................................................................................................................................................................
View the Routing Display on an EVC When to use
This function starts Routing Display on a Connection Oriented EVC or Connection Less EVC. Related Information
For more information about EVC, refer to “EVC description” (p. 18-37). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The Service menu is shown. ...................................................................................................................................................................................................
2
Select Connection Oriented (ETS) > ETS EVCs or Connection Less (Bridge) > Bridge EVCs. Result: The EVC list is displayed. ...................................................................................................................................................................................................
3
Select the EVC in the list and follow the path Search > EVC > Routing Display. Result: The Routing Display is started on the EVC. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-75 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Overview about E2E Ethernet Virtual Connections Managing End-to-End Ethernet Virtual Connections (E2E EVC) ....................................................................................................................................................................................................................................
Managing End-to-End Ethernet Virtual Connections (E2E EVC) Overview about E2E Ethernet Virtual Connections Introduction to End to End EVC connection
The following two modalities can be used in creating an End to End EVC connection: • •
bottom-up. This modality requires the separate creation of the EVCs within their domains, then the user will join the different EVCs. top-down. This modality is completely automatic. The user creates the full EVC over different domains and all relevant commands are forwarded to the subordinate network.
Managing Extended Ethernet Virtual Connection
Ethernet Virtual Connections (EVC) span over only one domain, ETB or ETS, at a time. It is possible to create an End-To-End EVC (E2E EVC), crossing one ETB domain and one ETS domain, which are connected by Inter-Domain-Links. E2E EVC Categories
The categories of E2E EVCs are: •
“Full E2E EVC ” (p. 18-76)
•
“Raw E2E EVC ” (p. 18-76)
Full E2E EVC
Full E2E EVC is a E2E EVC that is created in the top-down way, it is defined by end points and other EVC parameters, and the fragment EVCs are created then accordingly. Full E2E EVC must be consistent, its fragment EVCs must match each other and the E2E EVC itself. If, for any reason, the consistency is not kept, it becomes a raw E2E EVC. Raw E2E EVC
Raw E2E EVC is an E2E EVC that is created in the bottom-up way, there are fragment EVCs, which are joined to create the raw E2E EVC. It is used mainly in the Takeover, having in the network already existing groups of EVCs, which can be joined into E2E EVCs. Raw E2E EVC does not have to be consistent with its fragment EVCs. Raw E2E EVC can be created also from a full E2E EVC, which is not consistent any more. If a raw E2E EVC reaches a level of full consistency, it can become a full E2E EVC.
.................................................................................................................................................................................................................................... 1350 OMS 18-76 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Overview about E2E Ethernet Virtual Connections Managing End-to-End Ethernet Virtual Connections (E2E EVC) ....................................................................................................................................................................................................................................
EVC Prevented Actions
When an EVC is a part of a Full E2E EVC, any direct modification of its attributes may affect the E2E EVC it belongs to, and also other fragment EVCs that belong to the same E2E EVC. Therefore only the EVC attributes User Label, Comment and External Mark can be modified. The EVC cannot be deleted. In order to do any of these actions, directly to the EVC, the parent E2E EVC must be changed to be a Raw E2E EVC, and then all the actions are allowed.
.................................................................................................................................................................................................................................... 1350 OMS 18-77 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Display the list of E2E EVC Managing End-to-End Ethernet Virtual Connections (E2E EVC) ....................................................................................................................................................................................................................................
Display the list of E2E EVC When to use
The Ethernet Virtual Connection List window presents all the EVCs and their attributes. Related Information
This list can be required also from the Ethernet Service List, from the Ethernet Segment List, or from the Ethernet Transport Link List. In These cases, only the EVCs associated to the selected object are displayed. For more information about EVC, refer to “EVC description” (p. 18-37). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUIMain view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The menu of the Services is shown. ...................................................................................................................................................................................................
2
Select E2E EVCs. Result: The list window is displayed.
See the following topic in this document: “Description of the list of EVCs” (p. 18-79) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-78 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Description of the list of EVCs Managing End-to-End Ethernet Virtual Connections (E2E EVC) ....................................................................................................................................................................................................................................
Description of the list of EVCs Attributes of an EVC
The attributes displayed for each EVC are: •
User Label.
•
Ethernet Service User Label.
•
Type (Point to point, Routed multi-point, Any to any).
•
Traffic Type (Unicast, Multicast).
•
Working State (Normal, Configuring, Allocating, De-allocating, Implementing, De-implementing, Commissioning, De-commissioning, Termination adding, Termination removing, Constraint adding, Constraint removing, Removing).
•
Provisioning State (Defined, Partially allocated, Allocated, Partially implemented, Implemented, Commissioned).
•
Service State (Not in Service, In Service).
•
Availability Status (Normal, Degraded, In Failure, Not Meaningful).
.................................................................................................................................................................................................................................... 1350 OMS 18-79 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Create an E2E EVC Managing End-to-End Ethernet Virtual Connections (E2E EVC) ....................................................................................................................................................................................................................................
Create an E2E EVC When to use
This function create an Ethernet Virtual Connection in an end to end way. Related Information
Related information can be found in “EVC description” (p. 18-37). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the Multi Service GUI Main view: ...................................................................................................................................................................................................
1
Select Action > Packet > Services > Create E2E EVC. Result: The Create E2E EVC window is displayed. ...................................................................................................................................................................................................
2
Select the General panel. Fill the following data: •
Enter an EVC User Label.
•
Set the Service associated to the EVC: To set the service the user can do one of the following steps: – Choose an existing Ethernet Service by using the sensitive help. If this window is required from the Service List, this field is automatically filled. – Choose a Service Type (EVPL, EPTL, EPL, EVPLAN, Extended EVPL, Extended EVPLAN, HSI, BTV, Broadcast). According to the choice, Type, Traffic Type, and Resource Sharing are assigned as indicated in Table 18-1, “Connection Oriented Service Type relations ” (p. 18-40).
• • •
Select a Type (Point to Point, Routed Multipoint, Any to Any (also called Multipoint to multipoint)). if allowed. Select a Traffic Type (Unicast, Multicast), the selection of the parameter depends on the selected type. Select a Resource Sharing (Full, Private UNI, Private Link, Private UNI and LINK). See “Overview” (p. 18-39).
•
Select a Domain Label by using the sensitive help.
.................................................................................................................................................................................................................................... 1350 OMS 18-80 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Create an E2E EVC Managing End-to-End Ethernet Virtual Connections (E2E EVC) .................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
3
Select the Detail panel. Fill the following data: •
Enter Vlan Distribution (Full mesh, Not full mesh).
•
Enter a Vlan Bundle in the range of the local Vlan.
•
Enter s-Vlan Id the range of the VLAN over SDH path, an equal value can go on the same domain. Select the Standard Vlan Type (8100). Select the Frame Delivery parameters (see “Frame delivery” (p. 18-41))
• •
–
Unicast Service Frame Delivery.
– –
Multicast Service Frame Delivery. Broadcast Service Frame Delivery.
•
Select the standard Vlan Type (8100).
•
Define IGMP Snooping State (Not Meaningful, Enabled, Disabled). This option is enabled only for EVPLAN, Extended EVPLAN and BTV EVC types and can optionally be defined. The possible values are: –
Enabled: to remind that the IGMP snooping protocol is not used on top of the created EVC: enable the IGMP snooping immediately after having implemented the EVC. disable the IGMP snooping immediately before de-implemented the EVC.
–
Disabled: to remind that the IGMP snooping protocol is not used on the created EVC.
...................................................................................................................................................................................................
4
Select the Layer-2 Control Protocol panel. Fill the following data: •
To set all the fields in the form with the same value at once: Select Put entire set to and choose one of the following values: –
Default: all the set is put to Tunnel.
–
Not Meaningful: all the set is put to Not Meaningful.
–
Free: every value can be different.
•
Set the Data Frames.
•
Set the Customer BPDU.
•
Set the Provider BPDU.
•
Set the Slow Protocols.
•
Set the 802.1X PAE.
•
Set the Provider GVRP.
•
Set the Bridge Management.
.................................................................................................................................................................................................................................... 1350 OMS 18-81 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Create an E2E EVC Managing End-to-End Ethernet Virtual Connections (E2E EVC) ....................................................................................................................................................................................................................................
• •
Set the Customer GMRP. Set the Customer GVRP. User chooses which control Protocol must be tunneled or discarded. The configuration is propagated to all EVC terminations to ensure that all EVC terminations use the same Tunneling criteria. A check is needed also toward Layer-2 Control Protocol Processing defined at UNI level. This check allows a congruent management of Control protocols crossing the EVC. The single L2 protocol can have different values. User can select a value for each protocol between Tunnel, Not Meaningful and Discard.
...................................................................................................................................................................................................
5
Select the PM panel. Fill the following data: •
Select Under PM (True, False).
•
Choose the Granularity.
•
Choose the Report Output Type.
•
Choose the Report Output Frequency.
•
Set the Report Output Name.
•
Choose the Policy.
...................................................................................................................................................................................................
6
Select the Miscellaneous panel. Fill the following data: •
Select a Service Level (Premium, Gold, Silver, Bronze).
•
C-VLAN Preservation: check it to keep the VLAN Id through the EVC.
(see: “C-VLAN and CoS Preservation” (p. 18-41)). •
C-VLAN CoS Preservation: check it to keep the Priority Bits through the EVC.
(see: “C-VLAN and CoS Preservation” (p. 18-41)). •
NAD: select a NAD value from the list.
•
Enter an External Mark (optional). It can be used to identify external systems having relations with the EVC (for example an ownership). Enter Comment (optional).
•
...................................................................................................................................................................................................
7
Click Next to set the EVC terminations. ...................................................................................................................................................................................................
8
Click Next to define the EVC. ...................................................................................................................................................................................................
9
Click Ok.
.................................................................................................................................................................................................................................... 1350 OMS 18-82 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Create an E2E EVC Managing End-to-End Ethernet Virtual Connections (E2E EVC) ....................................................................................................................................................................................................................................
Result: A check is performed. If the check succeeded, the EVC is created. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-83 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Create a full E2E EVC Managing End-to-End Ethernet Virtual Connections (E2E EVC) ....................................................................................................................................................................................................................................
Create a full E2E EVC When to use
This function consists in creating a full end to end Ethernet Virtual Connection. Related Information
Related information can be found in “EVC description” (p. 18-37). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the Multi Service GUI Main view: ...................................................................................................................................................................................................
1
Select Action > Packet > Services > Create Full E2E EVC. Result: The E2E EVC Full Creation window is displayed. ...................................................................................................................................................................................................
2
Select the General panel. Fill the following data: •
Enter an EVC User Label.
•
Set the Service Type associated to the EVC: To set the service the user can do one of the following steps: – Choose an existing Ethernet Service by using the sensitive help. If this window is required from the Service List, this field is automatically filled. – Choose a Service Type (EVPL, EPTL, EPL, EVPLAN, Extended EVPL, Extended EVPLAN, HSI, BTV, Broadcast). According to the choice, Type, Traffic Type, and Resource Sharing are assigned as indicated in Table 18-1, “Connection Oriented Service Type relations ” (p. 18-40).
• • • •
Select a Type (Point to Point, Routed Multipoint, Any to Any (also called Multipoint to multipoint)). if allowed. Select a Traffic Type (Unicast, Multicast), the selection of the parameter depends on the selected type. Select a Service Level (Premium, Gold, Silver, Bronze). Select a Resource Sharing (Full, Private UNI, Private Link, Private UNI and LINK). See “Overview” (p. 18-39).
.................................................................................................................................................................................................................................... 1350 OMS 18-84 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Create a full E2E EVC Managing End-to-End Ethernet Virtual Connections (E2E EVC) ....................................................................................................................................................................................................................................
•
Select a C-VLAN Preservation to keep the VLAN Id through the EVC. (see: “C-VLAN and CoS Preservation” (p. 18-41)).
•
Select a C-VLAN CoS Preservation to keep the Priority Bits through the EVC. (see: “C-VLAN and CoS Preservation” (p. 18-41)).
•
Select a NAD value from the list.
•
Enter an External Mark (optional). It can be used to identify external systems having relations with the EVC (for example an ownership). Enter Comment (optional).
•
...................................................................................................................................................................................................
3
Select the Detail panel. Fill the following data: •
Enter the Directionality (Unidirectional, Bidirectional).
•
Define the IGMP Snooping State (Not Meaningful, Enabled, Disabled).
•
Select the Standard Vlan Type (8100).
•
Enter a value for the VLAN Bundle or a range for the parameter.
...................................................................................................................................................................................................
4
Select the Termination panel. Fill the following data: •
Select the Domain Label by using the sensitive help.
• • •
Select the NE or the ENE user label by using the sensitive help. (The NEs belonging to the selected domain are listed). Select an Edge Port user label by using the sensitive help. Select the Role of the termination (Root, Leaf, Both).
•
Enter a list of EVC terminations by using Add EVC Termination button.
...................................................................................................................................................................................................
5
Click Ok. Result: A check is performed. If the check succeeded, the EVC is created. The tree area and the EVC List are updated.
The EVC is created with the following states: Provisioning State set to Defined, Working State set to Normal. A correlation with the Service is created. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-85 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Create a raw E2E EVC Managing End-to-End Ethernet Virtual Connections (E2E EVC) ....................................................................................................................................................................................................................................
Create a raw E2E EVC When to use
This function consists in creating a raw end to end Ethernet Virtual Connection. Related Information
Related information can be found in “EVC description” (p. 18-37). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the Multi Service GUI Main view: ...................................................................................................................................................................................................
1
Select Action > Packet > Services > Create Raw E2E EVC. Result: The E2E EVC Raw Creation window is displayed. ...................................................................................................................................................................................................
2
Fill the following data: •
Enter the EVC User Label.
•
Enter Comment (optional).
•
Enter an External Mark (optional). It can be used to identify external systems having relations with the EVC (for example an ownership). Enter a list of EVC terminations by using Add EVC Termination button. The EVC can be Connection Oriented or Connection Less. To remove an EVC from the list, use the Remove EVC button.
•
...................................................................................................................................................................................................
3
Click Ok. Result: A check is performed. If the check succeeded, the EVC is created. The tree
area and the EVC List are updated. The EVC is created with the following states: Provisioning State set to Defined, Working State set to Normal. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-86 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Modify a full E2E EVC Managing End-to-End Ethernet Virtual Connections (E2E EVC) ....................................................................................................................................................................................................................................
Modify a full E2E EVC When to use
The function allows the user to modify EVC characteristics. Related Information
Related information can be found in “EVC description” (p. 18-37). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
If the User Label is modified, the new User Label must be different from other already used by another EVC.
Task
From the Multi Service GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > E2E EVCs. Result: The list window is displayed. ...................................................................................................................................................................................................
2
Select the EVC to modify in the list. ...................................................................................................................................................................................................
3
Click the right mouse button and select from the popup menu Modify. Result: The EVC modification window is displayed. ...................................................................................................................................................................................................
4
To modify an EVC, modify one or more of the following items: •
Modify the EVC User Label.
• • •
Modify the C-VLAN Preservation. Modify the C-VLAN CoS Preservation. Modify the NAD Value.
• •
Modify the Comment. Modify the External Mark.
.................................................................................................................................................................................................................................... 1350 OMS 18-87 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Modify a full E2E EVC Managing End-to-End Ethernet Virtual Connections (E2E EVC) .................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
5
Click Ok. Result: The EVC list, the tree area, and the opened graphical views are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-88 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Join E2E EVC Managing End-to-End Ethernet Virtual Connections (E2E EVC) ....................................................................................................................................................................................................................................
Join E2E EVC When to use
This function joins two or more Ethernet Virtual Connections. Related Information
Related Information can be found in “EVC description” (p. 18-37). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the Multi Service GUI Main view, follow the path Action > Packet > Services > Join E2E EVC. Result: The Join E2E EVC window is displayed. ...................................................................................................................................................................................................
2
To join two or more EVCs: •
Enter a User Label.
•
Enter the Comment (optional).
•
Enter the External Mark (optional).
•
Select the EVCs to be joined. Select an EVC domain (Connection Oriented, Connection Less, T-MPLS, eOMS) –
Click the EVC List icon to list all the EVCs defined into the domain.
– –
Select the one or more EVCs in the list. Click the confirmation icon.
Note: The EVCs can be added to or removed from the list by the icons under EVC List menu. Note: Repeat this step for all the needed EVC. Result: Selected EVCs are listed in the Join E2E EVC window. ...................................................................................................................................................................................................
3
Click Ok.
.................................................................................................................................................................................................................................... 1350 OMS 18-89 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Join E2E EVC Managing End-to-End Ethernet Virtual Connections (E2E EVC) ....................................................................................................................................................................................................................................
Result: A check is performed. If the check succeeded, the join is accomplished. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-90 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing an E2E EVC Managing End-to-End Ethernet Virtual Connections (E2E EVC) ....................................................................................................................................................................................................................................
Managing an E2E EVC When to use
The scope of this procedure is to create an End to End EVC connection. With reference to the below schema. Figure 18-9 Network schema for E2E connection
Related Information
This task does not have any related information. Before you begin
This task does not have any preconditions. Task ...................................................................................................................................................................................................
1
Create LoC between NE-B and NE-C ...................................................................................................................................................................................................
2
Assign port B1 to Domain ETS ...................................................................................................................................................................................................
3
Assign port C1 to Domain T-MPLS ...................................................................................................................................................................................................
4
After the assignment of port B1 to Domain ETS and port C1 to Domain T-MPLS, • the Loc between NE-B and NE-C becomes IWI (it was generic) • ports B1 and port C1 become UNI (Edge port in their domains)
.................................................................................................................................................................................................................................... 1350 OMS 18-91 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing an E2E EVC Managing End-to-End Ethernet Virtual Connections (E2E EVC) .................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
5
Assign port B2 to Domain ETS ...................................................................................................................................................................................................
6
Create EVC ETS (from B1 to B2) ...................................................................................................................................................................................................
7
Create EVC T-MPLS (from C1 to C2) ...................................................................................................................................................................................................
8
From the main bar select Actions>Packet>Service>Join E2E EVC ...................................................................................................................................................................................................
9
Select domain C.O. Select EVC Select domain T-MPLS Select EVC Click on OK to confirm. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-92 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
Structure for EVC over SDH
....................................................................................................................................................................................................................................
EVC over SDH Structure for EVC over SDH When to use
The scope of this procedure is Related Information
This task does not have any related information. Before you begin
All needed conditions are detailed along the procedure. Task ...................................................................................................................................................................................................
1
From the main menu bar select Search > Packet > Construction > Transport Links > Links over TDM(Sdh/Sonet) Figure 18-10 Search>Packet>Construction>Transport Links>Links over TDM(Sdh/Sonet)
...................................................................................................................................................................................................
2
The list of Links over TDM(Sdh/Sonet) is displayed.
.................................................................................................................................................................................................................................... 1350 OMS 18-93 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
Structure for EVC over SDH
....................................................................................................................................................................................................................................
This list contains an Ethernet path, created on SDH, which will be used Figure 18-11 Links over TDM(Sdh/Sonet)
...................................................................................................................................................................................................
3
From the bar select Search>Packet>Construction>Network Elements>Defined NEs Figure 18-12 Search>Packet>Construction>Network Elements>Defined NEs
...................................................................................................................................................................................................
4
The list of the Defined NEs is displayed.
.................................................................................................................................................................................................................................... 1350 OMS 18-94 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
Structure for EVC over SDH
....................................................................................................................................................................................................................................
Select the relevant NE and issue Search > Ethernet Physical Ports Figure 18-13 Defined NE:Search>Ethernet Physical Ports
...................................................................................................................................................................................................
5
Select the Ethernet port and issue Actions > Assign Resource to Domain Figure 18-14 Port:Actions>Assign Resource to Domain
.................................................................................................................................................................................................................................... 1350 OMS 18-95 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
Structure for EVC over SDH
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
6
Click on button Domains. From the domain list select the ETS Domain and click on V. Figure 18-15 ETS Domain selection
.................................................................................................................................................................................................................................... 1350 OMS 18-96 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
Structure for EVC over SDH
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
7
Click on OK to assign the port to ETS domain. Figure 18-16 Assign port to ETS domain
...................................................................................................................................................................................................
8
Execute the assignment for the far end port on TSS-B. (Port:Actions>Assign Resource to Domain) ...................................................................................................................................................................................................
9
From the main menu bar select Search>Packet>Construction>Transport Links>Links over TDM(Sdh/Sonet)
.................................................................................................................................................................................................................................... 1350 OMS 18-97 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
Structure for EVC over SDH
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
10
Select the relevant Link over TDM (path) and issue Actions>Assign Resources to Domain Figure 18-17 Link over TDM (path): Actions>Assign Resources to Domain
...................................................................................................................................................................................................
11
Select ETS domain. Figure 18-18 Select ETS domain
.................................................................................................................................................................................................................................... 1350 OMS 18-98 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
Structure for EVC over SDH
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
12
Click on OK to confirm the assignment. Figure 18-19 Confirm the assignment
...................................................................................................................................................................................................
13
From the bar select Search>Packet>Services>Connection Oriented>ETS Transport Link
.................................................................................................................................................................................................................................... 1350 OMS 18-99 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
Structure for EVC over SDH
....................................................................................................................................................................................................................................
The path, when assigned, is now an ETS Transport Link Figure 18-20 Search>Packet>Services>Connection Oriented>ETS Transport Link
...................................................................................................................................................................................................
14
Since we do not find the path in the list of ETS Transport Links, this is due to the fact that we forgive to commission the path. Figure 18-21 Path commissioning
.................................................................................................................................................................................................................................... 1350 OMS 18-100 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
Structure for EVC over SDH
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
15
After path commissioning the path is included in the Links over TDM list. Figure 18-22 Path included in the Links over TDM
...................................................................................................................................................................................................
16
And in the Transport Links, accordingly. Figure 18-23 Transport Links
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-101 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
Assign ports to domain
....................................................................................................................................................................................................................................
Assign ports to domain When to use
The scope of this procedure is to assign ports to domain Related Information
This task does not have any related information. Before you begin
This task does not have any preconditions. Task ...................................................................................................................................................................................................
1
From the main menu bar select Search > Packet > Construction > Network Elements > Defined NEs ...................................................................................................................................................................................................
2
Select a Defined Network Element from the list and using the right mouse button, select from the popup menu, Search > Ethernet Physical Ports
.................................................................................................................................................................................................................................... 1350 OMS 18-102 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
Assign ports to domain
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
3
Port: Assign resources to Domain Figure 18-24 Port: Assign resources to Domain
.................................................................................................................................................................................................................................... 1350 OMS 18-103 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
Assign ports to domain
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
Assign resources to Domain. Click on Apply. Figure 18-25 Assign resources to Domain
.................................................................................................................................................................................................................................... 1350 OMS 18-104 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
Assign ports to domain
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
5
From the main menu bar select Search > Packet > Services > T-MPLS > T-MPLS Edge Ports. Figure 18-26 Search>Packet>Services>T-MPLS>T-MPLS Edge Ports
...................................................................................................................................................................................................
6
The list of the edge ports is displayed. Figure 18-27 UNI ports became edge ports
...................................................................................................................................................................................................
7
Assign the other UNI port. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-105 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
EVC over SDH
....................................................................................................................................................................................................................................
EVC over SDH When to use
The scope of this procedure is to Create EVC over SDH. Related Information
This task does not have any related information. Before you begin
All needed coditions are detailed along the procedure. Task ...................................................................................................................................................................................................
1
From the main bar select Actions > Packet > Services > Connection Oriented(ETS) > Create EVC. Figure 18-28 Actions>Packet>Services>Connection Oriented(ETS)>Create EVC
...................................................................................................................................................................................................
2
Complete following data on the Create EVC window : • name • service type=EVPL • ethernet service:automatically selected • select the domain: ETS • type=point to point automatically selected
.................................................................................................................................................................................................................................... 1350 OMS 18-106 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
EVC over SDH
....................................................................................................................................................................................................................................
• traffic type=unicast • resource sharing=unicast Select the NE Select the Edge Port Figure 18-29 EVC over SDH: EVC definition
.................................................................................................................................................................................................................................... 1350 OMS 18-107 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
EVC over SDH
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
3
Select the far end edge port. Click on Next. Figure 18-30 Far end edge port selection
...................................................................................................................................................................................................
4
Select the traffic descriptor to associate.
.................................................................................................................................................................................................................................... 1350 OMS 18-108 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
EVC over SDH
....................................................................................................................................................................................................................................
Click on Apply Figure 18-31 Ethernet Segments definition
.................................................................................................................................................................................................................................... 1350 OMS 18-109 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
EVC over SDH
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
5
From the main menu bar select Search > Packet > Services > Connection Oriented(ETS) Figure 18-32 Search>Packet>Services>Connection Oriented(ETS)
...................................................................................................................................................................................................
6
The ETS EVC is created as defined. Figure 18-33 ETS EVCs
.................................................................................................................................................................................................................................... 1350 OMS 18-110 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
EVC over SDH
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
7
Select the ETS EVC and issue Search > Ethernet Segments. Figure 18-34 ETS EVC: Search>Ethernet Segments
...................................................................................................................................................................................................
8
The list of the Ethernet segments is shown below. Figure 18-35 Ethernet segment list
.................................................................................................................................................................................................................................... 1350 OMS 18-111 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
EVC over SDH
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
9
You may select an Ethernet Segment from the list and using the right mouse button, select from the popup menu Actions > Add Constraints to an Ethernet Service Figure 18-36 Actions>Add Constraints to an Ethernet Service
...................................................................................................................................................................................................
10
Select as constraint the transport link
.................................................................................................................................................................................................................................... 1350 OMS 18-112 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
EVC over SDH
....................................................................................................................................................................................................................................
Click on Apply. Figure 18-37 Add Constraints to an Ethernet Service
.................................................................................................................................................................................................................................... 1350 OMS 18-113 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
EVC over SDH
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
11
Select the Ethernet Segment in the list and using the right mouse button follow the path Actions > Associate Traffic Classifier Figure 18-38 Segment:Actions>Associate to Traffic Classifier
...................................................................................................................................................................................................
12
From the list select the Traffic Classifier. Figure 18-39 Traffic Classifier list
.................................................................................................................................................................................................................................... 1350 OMS 18-114 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
EVC over SDH
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
13
Click on Apply to launch the association. Figure 18-40 Associate Traffic Classifier
.................................................................................................................................................................................................................................... 1350 OMS 18-115 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
EVC over SDH
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
14
Allocate the segment. Figure 18-41 Allocate the segment
...................................................................................................................................................................................................
15
Implement the segment. Figure 18-42 Implement the segment
.................................................................................................................................................................................................................................... 1350 OMS 18-116 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
EVC over SDH
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
16
Allocate and implement the other segment. Figure 18-43 Both segments are implemented
Result: The EVC-ETS is implemented Figure 18-44 EVC-ETS implemented
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-117 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
Alarms EVC T-MPLS
....................................................................................................................................................................................................................................
Alarms EVC T-MPLS When to use
The scope of this procedure is to detect a fault condition on a T-MPLS EVC. Related Information
This task does not have any related information. Before you begin
This task does not have any preconditions. Task ...................................................................................................................................................................................................
1
From the T-MPLS EVC list attribute Availability is marked In Failure. Figure 18-45 T-MPLS EVC list: Availability
.................................................................................................................................................................................................................................... 1350 OMS 18-118 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
Alarms EVC T-MPLS
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
2
From the T-MPLS EVC issue Search>Fault Localization Figure 18-46 EVC: Search>Fault Localization
...................................................................................................................................................................................................
3
The Transport Section is In Failure. Figure 18-47 Navigation to Transport Section
.................................................................................................................................................................................................................................... 1350 OMS 18-119 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management EVC over SDH
Alarms EVC T-MPLS
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
You can navigate to Link over Cable Figure 18-48 Navigate to Link over Cable
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-120 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Full EVC Takeover
Overview about Full EVC Takeover procedure
....................................................................................................................................................................................................................................
Full EVC Takeover Overview about Full EVC Takeover procedure Overview about Takeover procedure
Takeover manages the profile configuration in the network. It manages profile creation on domain basis. The creation affects PKT database only.
.................................................................................................................................................................................................................................... 1350 OMS 18-121 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Full EVC Takeover
Full EVC Takeover Procedure
....................................................................................................................................................................................................................................
Full EVC Takeover Procedure When to use
When the PKT is deployed in a network where Network Elements and Ethernet Connectivity (network wide) are already in place, then the need to take in charge such Ethernet Connectivity is a must for PKT Network Manager. Related information
The Full EVC Takeover Online procedure is applicable to all kind of Connection Oriented, Connection Less and T-MPLS based EVCs and covers all managed topologies. 1. Connection Oriented EVC: The Takeover is applied at Ethernet Segment Level. The Takeover is applied on all Ethernet Segments types, unicast and multicast : the EVC which contains them are automatically updated; 2. Connection Less EVC: The Takeover is applied directly to the desired EVC. The Takeover is done on all EVC types 3. Connection T-MPLS EVC: The Takeover is applied directly to the desired EVC. The Takeover is done on all EVC types Note: The usage of the Offline Takeover procedure forces the shutdown and the subsequent restart of PKT processes in order to let the Takeover Procedure work. Using this procedure, there is no need to shutdown the services. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. Procedure
Following steps should be done to execute correctly the Takeover with online command: From MS-GUI main window: ...................................................................................................................................................................................................
1
Create one or more domains that corresponds to the scenario already acting in field : from the Construction application Select Action > Packet > Costruction > Create Domain.
.................................................................................................................................................................................................................................... 1350 OMS 18-122 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Full EVC Takeover
Full EVC Takeover Procedure
....................................................................................................................................................................................................................................
Insert the User Label, Domain Type, Bridge Type and STP Type compliant with the attributes already present. Figure 18-49 Create Domain
Result: The list Domain window is shown with new Domain. ...................................................................................................................................................................................................
2
Define the Network Elements to the PKT environment : from the Construction application. Select Action > Packet > Costruction > Define NE.
.................................................................................................................................................................................................................................... 1350 OMS 18-123 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Full EVC Takeover
Full EVC Takeover Procedure
....................................................................................................................................................................................................................................
Insert the User Label, Working Mode and STP Type compliant with the attributes already present. Figure 18-50 Define NE
Select the Network Elements to be added from the list, click the confirm button. The Defined Network Element List updated. When the NEs are added, assign the resources already present or create them. Select Action > Packet > Costruction > Assign Resources to Domain. Result: The list Network Element window is shown with new NE. ...................................................................................................................................................................................................
3
If the Customer is not yet created, create it now, repeat the same operation for Traffic Description and Traffic Classifier Select Action > Packet > Services> Create Customer.
.................................................................................................................................................................................................................................... 1350 OMS 18-124 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Full EVC Takeover
Full EVC Takeover Procedure
....................................................................................................................................................................................................................................
Select Action > Packet > Services> Create Traffic Descriptor. Select Action > Packet > Services> Create Traffic Classifier. Insert the information compliant with the attributes already present. Result: The Customer list is shown with new elements. ...................................................................................................................................................................................................
4
Create one or more EVC (with the Service in automatic mode) that corresponds to the scenario already acting in field : Select Action > Packet > Services > (ETS,ETB and T-MPLS)> Create EVC. Insert the parameters compliant with the attributes already present. Important! Define one or more allocated services that should Takeover, the service must have exactly the same characteristics as the service to Takeover. Figure 18-51 Create EVC
Important! End the operation in the state of allocated EVC. Note: If the EVCs are T-MPLS, to do the Discovery of the Tunnel and Pseudo-Wire.
.................................................................................................................................................................................................................................... 1350 OMS 18-125 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Full EVC Takeover
Full EVC Takeover Procedure
....................................................................................................................................................................................................................................
Result: The list EVC window is shown with new EVC. ...................................................................................................................................................................................................
5
Perform the Audit and Reservation on all interested Network Elements : select the interested NEs and from the main menu Select Action > Packet > Audit Align Reservation> Start AAR procedure. Insert the information compliant with the attributes already present. ...................................................................................................................................................................................................
6
Perform the Audit and Reservation on all interested Network Elements : from the NEs for Auditlist select the interested NEs and start NE Audit. Select all interested NEs:Search > Packet > Audit Align Reservation> NEs for Audit>Start NE Audit. Insert the information compliant with the attributes already present. Perform the same operation for Reservation. ...................................................................................................................................................................................................
7
Perform the Align Up procedure for the Takeover on the involved ports.
.................................................................................................................................................................................................................................... 1350 OMS 18-126 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Full EVC Takeover
Full EVC Takeover Procedure
....................................................................................................................................................................................................................................
Select Action > Packet > Audit Align Reservation> Service Align Up. Figure 18-52 Align Up window
Insert the information compliant with the attributes already present. Note: Execute the Align Up procedure maintaining the Audit window from the Construction application open. ...................................................................................................................................................................................................
8
Stop Audit, Align and Reservation procedure. Select Action > Packet > Audit Align Reservation> Stop AAR procedure. ...................................................................................................................................................................................................
9
The Ethernet Segments involved or the EVCs in case of connection less connection should be in Allocated state.
.................................................................................................................................................................................................................................... 1350 OMS 18-127 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Full EVC Takeover
Full EVC Takeover Procedure
....................................................................................................................................................................................................................................
Start the Takeover procedure: Select Action > Packet > Services> Takeover>Enable Takeover. Figure 18-53 Enable Takeover
Result: The full Takeover online procedure runs on the allocated services created in
the previous steps. ...................................................................................................................................................................................................
10
Implement the Ethernet Segments or EVCs to complete the Takeover procedure: From the Ethernet Management application. ...................................................................................................................................................................................................
11
Verify that the Takeover is successfully done, the service should be now in Implemented state. Note: Verify that the Takeover is successfully done, the service should be now in Implemented state. ...................................................................................................................................................................................................
12
Stop the Takeover procedure:
.................................................................................................................................................................................................................................... 1350 OMS 18-128 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Full EVC Takeover
Full EVC Takeover Procedure
....................................................................................................................................................................................................................................
Select Action > Packet > Services> Takeover>Disable Takeover. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-129 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management T-MPLS Takeover
T-MPLS Takeover description
....................................................................................................................................................................................................................................
T-MPLS Takeover T-MPLS Takeover description T-MPLS Takeover Key features:
T-MPLS Takeover procedure is aimed to discover existing T-MPLS infrastructure (i.e. tunnels and pseudo-wires) from the network, and import it into PKT database. physical connectivity must be described Circuit correctness checks – only tunnel/PWs defined coherently in all the NE’s involved are uploaded (e.g., two terminations must be found; traffic descriptor parameters must be equal along the circuit; T-MPLS in-labels must match the out-labels, etc). Takeover of 1+1 protected tunnels Takeover of 1+1 APS Protections Groups defined in the NE’s when tunnels are already in PKT database. Takeover of T-MPLS profiles (Traffic Descriptor, PHB, L2-encapsulation). Takeover of all tunnels/PWs OR only tunnels/PWs terminating in a node. Description of main steps
Define via NPR the physical/logical connectivity supporting T-MPLS, i.e., ethernet physical-connections or SDH paths. This will result in the definition of links-over-cable / links-over-SDH in PKT. Assign via PKT these links to T-MPLS domain. This will result in the definition of T-MPLS nodes and sections inside PKT database. Start Takeover operation from T-MPLS domain OR, if only a small part of the network is involved, from one of the T-MPLS nodes (in this latter case, choice is left to operator whether to discover all circuits or only those terminating in the node). This will result (if the circuit were defined correctly in the network) in the tunnels/PWs objects (in implemented state) inside PKT database. Check in the lists that tunnels/PWs have been uploaded
.................................................................................................................................................................................................................................... 1350 OMS 18-130 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management T-MPLS Takeover
Takeover procedure for T-MPLS
....................................................................................................................................................................................................................................
Takeover procedure for T-MPLS When to use
The procedure permit to take in charge Network Elements and Connectivity when the PKT is deployed in a network where (network wide) such connectivity is already in place. Related information
For more information refer to: “T-MPLS Takeover description” (p. 18-130) For general procedure description, refer to: “Description of main steps” (p. 18-130) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. Conditions
The topology of the network must be already defined. Task for T-MPLS
From MS-GUI main window: ...................................................................................................................................................................................................
1
Create a T-MPLS Domain. Select Action > Packet > Construction > Create Domain. For details refer to the procedure “Create a Domain” (p. 13-20). Result: The T-MPLS domain is created. ...................................................................................................................................................................................................
2
Select Search > Packet > Construction > Link Over Cable. Assign Links Over Cable to T-MPLS domain. For details refer to the procedure “Assign a Link Over Cable to a Domain” (p. 14-60). Result: The selected Links Over Cable are assigned to T-MPLS domain ...................................................................................................................................................................................................
3
Execute the T-MPLS PW Takeover: Select Search > Packet > T-MPLS > T-MPLS domain.. Select the T-MPLS domain. Select Action > T-MPLS > Takeover All Note: In a large network the Takeover from the domain requires a long time to execute. The user can start the Takeover only from involved nodes.
.................................................................................................................................................................................................................................... 1350 OMS 18-131 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management T-MPLS Takeover
Takeover procedure for T-MPLS
....................................................................................................................................................................................................................................
Result: T-MPLS Tunnels and PseudoWires are discovered and created in the PKT
DB. To check the object creation, refer to the procedure “View the list of T-MPLS tunnels” (p. 16-99). To check the object creation, refer to the procedure “View the list of Pseudo Wires” (p. 16-51). E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-132 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Color Profiles
Overview about Color Profiles
....................................................................................................................................................................................................................................
Managing Color Profiles Overview about Color Profiles Color Profile description
The Color Profile allows the user to define a priority in accepting or rejecting incoming frames (Red/Yellow/Green). This rule applies when Traffic Descriptor is Regulated and Policy Control is not Color Blind.
.................................................................................................................................................................................................................................... 1350 OMS 18-133 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Color Profiles
Display the Color Profile list
....................................................................................................................................................................................................................................
Display the Color Profile list When to use
The Color Profile List window presents all the Color Profiles and their attributes. Related Information
If this list is required from the Ethernet Segment List, only the Color Profiles associated to the selected Ethernet Segment are displayed. For more information, refer to “Overview about Color Profiles” (p. 18-133). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUIMain view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The menu of the Services is shown. ...................................................................................................................................................................................................
2
Select Color Profile. Result: The list window is displayed.
The attributes displayed for each Color Profile are: • User Label. • Color Profile Mode (Priority, DSCP). E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-134 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Color Profiles
Create a Color Profile
....................................................................................................................................................................................................................................
Create a Color Profile When to use
This function consists in defining a Color Profile used to describe the flow of Ethernet frames over an Ethernet Segment. Related Information
For more information, refer to “Overview about Color Profiles” (p. 18-133). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The maximum number of Color Profiles must not be reached.
•
The User Label must be different as one which exists.
Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Action > Packet > Services > Create Color Profile. ...................................................................................................................................................................................................
2
On the Create Color Profile Window, the following data must be entered. To create a customer: •
Enter a User Label.
•
Select the Color Profile Mode (Priority, DSCP).
•
If Priority Mode is selected, Priority Tab must be set up.
•
If DSCP Mode is selected, Code Point 1 to Code Point 4 Tabs must be set up, selecting a color (Green, Yellow, or Red).
...................................................................................................................................................................................................
3
Click Ok button. Result: The Color Profile is created.
The Color Profile list is updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-135 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Color Profiles
Modify a Color Profile
....................................................................................................................................................................................................................................
Modify a Color Profile When to use
The function modifies Color Profile characteristics. Related Information
For more information, refer to “Overview about Color Profiles” (p. 18-133). The Color Profile modification gives the possibility to modify one or all the following parameters: • •
Color Profile User Label,. Color of each priority.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
If the User Label is modified, the new User Label must be different as one which is already used by another Color Profile.
•
The Color Profile must not be associated to any Ethernet Segment or could be associated to Ethernet Segments in Defined provisioning state.
Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Color Profiles. ...................................................................................................................................................................................................
2
On the Color Profile List, select the Color Profile to modify. Select with the right mouse button the path Action from Color Profile > Color Profile Modification.
.................................................................................................................................................................................................................................... 1350 OMS 18-136 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Color Profiles
Modify a Color Profile
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
3
The Modify Color Profile window is displayed. Figure 18-54 Color Profile Modification window
To modify a Color Profile: •
Enter a new User Label (optional).
•
If Priority Mode is selected, Priority Tab must be set up.
•
If DSCP Mode is selected, Code Point 1 to Code Point 4 Tabs must be set up, selecting a color (Green, Yellow, or Red).
...................................................................................................................................................................................................
4
Click Ok button.
.................................................................................................................................................................................................................................... 1350 OMS 18-137 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Color Profiles
Modify a Color Profile
....................................................................................................................................................................................................................................
Result: The Color Profile is modified.
The Color Profile list is updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-138 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Color Profiles
Delete a Color Profile
....................................................................................................................................................................................................................................
Delete a Color Profile When to use
This function consists in deleting a Color Profile from the supervision. Related Information
For more information, refer to “Overview about Color Profiles” (p. 18-133). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The Color Profile must not be associated to any Ethernet Segment or could be associated to Ethernet Segments in Defined provisioning state.
Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Color Profiles. ...................................................................................................................................................................................................
2
On the Color Profile List Window, select the Color Profile to delete. Select with the right mouse button from the popup menu Action from Color Profile > Delete. ...................................................................................................................................................................................................
3
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: The Color Profile is deleted.
After confirmation, the Color Profiles are removed and the Color Profile List is updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-139 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Color Profiles
Get the Color Profile Properties
....................................................................................................................................................................................................................................
Get the Color Profile Properties When to use
This function gets information about a Color Profile. Related Information
For more information, refer to “Overview about Color Profiles” (p. 18-133). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Color Profiles. ...................................................................................................................................................................................................
2
On the Color Profile List Window, select a Color. Select with the right mouse button from the popup menu Properties. ...................................................................................................................................................................................................
3
The Properties window is displayed. The attributes displayed for each Color Profile are: •
Id
•
User Label.
.................................................................................................................................................................................................................................... 1350 OMS 18-140 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Color Profiles
Get the Color Profile Properties
....................................................................................................................................................................................................................................
• •
Priority 0… Priority 7. Color Profile Mode (Priority, DSCP).
Figure 18-55 Color Profile Properties window
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-141 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management
Overview about Traffic Descriptor
....................................................................................................................................................................................................................................
Managing Traffic Descriptors Overview about Traffic Descriptor Traffic Descriptor description
The Traffic Descriptors describes the characteristics of an Ethernet Segment in term of Class of Service (CoS) and bandwidth. Another step toward the MEF alignment is provided by possibility to display bandwidth parameters following both IETF definitions (as already available) and MEF definitions. For reminder, the following definitions are applicable for IETF: CIR, PIR, PBS, CBS while the following one are applicable for MEF: CIR, EIR, CBS, EBS. The existing relationships are described as in the following: • •
EIR = PIR – CIR . EBS = PBS – CBS .
Three Traffic Descriptors are created by default during the 1350 OMS PKT installation. Class of services dependencies Table 18-2
Class of services and traffic parameters dependencies Class of Service.
Traffic Descriptor parameters.
CIR.
Best Effort.
Guaranteed.
Regulated.
0.
(CIR = PIR) & (CIR > 0).
(CIR = 0). if (CIR > 0), (CBS > 0). if (CIR = 0), (CBS=0).
PIR.
> 0.
(PIR = CIR) & (PIR > 0).
(PIR > = CIR) & (PIR > 0).
CBS.
0.
(CBS = PBS) & (CBS > 0).
(CBS > = 0) & (CBS 0), (CIR > 0). if (CBS = 0), (CIR=0).
PBS.
> 0.
(PBS = CBS) & (PBS > 0).
(PBS > 0) & (PBS > =CBS).
.................................................................................................................................................................................................................................... 1350 OMS 18-142 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Traffic Descriptors
Overview about Traffic Descriptor
....................................................................................................................................................................................................................................
Table 18-3
ISA boards and Ethernet traffic parameters dependencies ISA ES1 / ES4.
ISA PR EA / ISA ES16.
Minimum.
Maximum.
Minimum.
Maximum.
CIR.
0 or 8.
Up to PIR.
0 or 64.
Up to PIR.
PIR.
8.
Up to ELR.
64.
Up to ELR.
CBS.
0.
16384.
0.
Min (16384, 500/3*CIR).
PBS.
> 0.
16384.
> 0.
Min (65335, 500/3*PIR).
.................................................................................................................................................................................................................................... 1350 OMS 18-143 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Traffic Descriptors
Display the Traffic Descriptor list
....................................................................................................................................................................................................................................
Display the Traffic Descriptor list When to use
The Traffic Descriptor List window presents all the Traffic Descriptors and their attributes. Related Information
If this list is required from the Ethernet Segment List, only the Traffic Descriptors associated to the selected Ethernet Segment are displayed. For more information, refer to “Traffic Descriptor description” (p. 18-142). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUIMain view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The menu of the Services is shown. ...................................................................................................................................................................................................
2
Select Traffic Descriptors. Result: The list window is displayed.
See the following topic in this document: “Description of the list of Traffic Descriptors” (p. 18-145) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-144 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Traffic Descriptors
Description of the list of Traffic Descriptors
....................................................................................................................................................................................................................................
Description of the list of Traffic Descriptors Attributes of a Traffic Descriptor
The attributes displayed for each Traffic Descriptor are: •
User Label.
•
Class of Service (Guaranteed, Regulated, Best Effort, Guaranteed2, Regulated1, Regulated3, Regulated4, Background).
•
CIR (Committed Information Rate).
•
PIR (Peak Information Rate).
•
CBS (Committed Burst Size).
•
PBS (Peak Burst Size).
.................................................................................................................................................................................................................................... 1350 OMS 18-145 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Traffic Descriptors
Create a Traffic Descriptor
....................................................................................................................................................................................................................................
Create a Traffic Descriptor When to use
This function consists in defining a Traffic Descriptor. Related Information
Traffic Descriptor is used to describe the flow of the Ethernet frames over an Ethernet Segment. For more information, refer to “Traffic Descriptor description” (p. 18-142). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The maximum number of Traffic Descriptors must not be reached.
•
The traffic parameters of the Traffic Descriptor must be different from an existing ones Traffic Descriptor. The User Label must be different from the already used by other Traffic Descriptors.
• Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Action > Packet > Services > Traffic Descriptor Creation.
.................................................................................................................................................................................................................................... 1350 OMS 18-146 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Traffic Descriptors
Create a Traffic Descriptor
....................................................................................................................................................................................................................................
Result: The Creation window opens.
...................................................................................................................................................................................................
2
On the Create Traffic Descriptor Window, the following data must be entered. To create a Traffic Descriptor: •
Enter a User Label.
•
Select the Class of Service (Best Effort, Guaranteed, Regulated, Guaranteed2, Regulated1, Regulated3, Regulated4, Background). Enter a CIR value (set automatically to '0' if the selected Class of Service is 'Best Effort'). Enter a PIR value.
• • • •
Enter a CBS value (set automatically to '0' if the selected Class of Service is 'Best Effort'). Enter a PBS value (if the selected Class of Service is 'Guaranteed', PBS value is automatically set to CBS value - but could be modified).
.................................................................................................................................................................................................................................... 1350 OMS 18-147 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Traffic Descriptors
Create a Traffic Descriptor
....................................................................................................................................................................................................................................
See CIR/PIR/CBS/PBSdependencies in “Class of services dependencies” (p. 18-142). The relationship remains unchanged for the two Guaranteed as well as for the four Regulated. ...................................................................................................................................................................................................
3
Click Ok button. Result: After checking the coherence of the traffic parameters values, the Traffic Descriptor is created.
The Traffic Descriptor List is updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-148 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Traffic Descriptors
Modify a Traffic Descriptor
....................................................................................................................................................................................................................................
Modify a Traffic Descriptor When to use
The function modifies Traffic Descriptor characteristics. Related Information
For more information, refer to “Traffic Descriptor description” (p. 18-142). The Traffic Descriptor modification gives the possibility to modify: • • •
Traffic Descriptor User Label. Class of Service. CIR, PIR, CBS and/or PBS.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • •
If the User Label is modified, the new User Label must be different from the one used by another Traffic Descriptor. The Traffic Descriptor must not be associated to any Ethernet Segment or could be associated to Ethernet Segments in Defined provisioning state.
Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Traffic Descriptors. ...................................................................................................................................................................................................
2
On the Traffic Descriptor List, select the Traffic Descriptor to modify. Select with the right mouse button the path Modify.
.................................................................................................................................................................................................................................... 1350 OMS 18-149 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Traffic Descriptors
Modify a Traffic Descriptor
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
3
The Modify Traffic Descriptor window is displayed. Figure 18-56 Traffic Descriptor Modification window
To modify a Traffic Descriptor: •
Enter a new User Label (optional).
• •
Modify the Class of Service (optional). Modify the ClR (optional).
•
Modify the PIR (optional).
•
Modify the CBS (optional).
•
Modify the PBS (optional).
...................................................................................................................................................................................................
4
Click Ok button.
.................................................................................................................................................................................................................................... 1350 OMS 18-150 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Traffic Descriptors
Modify a Traffic Descriptor
....................................................................................................................................................................................................................................
Result: After confirmation of the modification, 1350 OMS PKT checks the consistence of the traffic parameter values and then, the Traffic Descriptor list is updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-151 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Traffic Descriptors
Delete a Traffic Descriptor
....................................................................................................................................................................................................................................
Delete a Traffic Descriptor When to use
This function consists in deleting a Traffic Descriptor. Related Information
For more information, refer to “Traffic Descriptor description” (p. 18-142). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The Traffic Descriptor must not be associated to any Ethernet Segment or could be associated to Ethernet Segments in Defined provisioning state.
Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Traffic Descriptors. ...................................................................................................................................................................................................
2
On the traffic descriptor List Window, select the traffic descriptor to delete. Select with the right mouse button from the popup menu Action from Traffic Descriptor > Delete. ...................................................................................................................................................................................................
3
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: After confirmation, the Traffic Descriptors are removed.
The Traffic Descriptor list is updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-152 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Traffic Descriptors
Get the Traffic Descriptor Properties
....................................................................................................................................................................................................................................
Get the Traffic Descriptor Properties When to use
This function gets information about a Traffic Descriptor. Related Information
For more information, refer to “Traffic Descriptor description” (p. 18-142). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Traffic Descriptors. ...................................................................................................................................................................................................
2
On the Traffic Descriptor List Window, select a TD. Select with the right mouse button from the popup menu Properties. ...................................................................................................................................................................................................
3
The Properties window is displayed.
.................................................................................................................................................................................................................................... 1350 OMS 18-153 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Traffic Descriptors
Get the Traffic Descriptor Properties
....................................................................................................................................................................................................................................
See the following topic in this document: “Details of a Traffic Descriptor” (p. 18-155) Figure 18-57 Traffic Descriptor (Ethernet Management) Properties window
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-154 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Traffic Descriptors
Details of a Traffic Descriptor
....................................................................................................................................................................................................................................
Details of a Traffic Descriptor Attributes of a Traffic Descriptor
The attributes displayed for each Traffic Descriptor are: •
Id
• •
User Label.
•
PIR (Peak Information Rate).
•
CBS (Committed Burst Size).
•
PBS (Peak Burst Size).
•
Class of Service (Guaranteed, Regulated, Best Effort, Guaranteed2, Regulated1, Regulated3, Regulated4, Background).
CIR (Committed Information Rate).
.................................................................................................................................................................................................................................... 1350 OMS 18-155 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Traffic Classifiers
Overview about Traffic Classifiers
....................................................................................................................................................................................................................................
Managing Traffic Classifiers Overview about Traffic Classifiers Traffic Classifier description
The 1350OMS-PKT realizes a flow classification. The 1350OMS-PKT is capable to distinguish different flows that are passing through the same port or transport link using a Traffic Classifier The Traffic Classifier describes the characteristics of an Ethernet frames on an Ethernet Segment. Ethernet frames can be either tagged or untagged. Three Traffic Classifiers are created by default during the 1350 OMS PKT installation. The classification can be done with one or more of the following criteria: • • •
Vlan Tag + Priority IP DSCP/TOS EtherType
When a VlanTag+Priority criteria is defined two flows are considered different if they have different (or different sets of) VLAN Ids and/or VLAN Priorities. A classification with IP DSCP/TOS criteria allows to identify distinct flows (at UNI/IWI) basing on IPv4 frame. The EthertType classification criteria is based on type/len field of Ethernet frame when it assumes the Type meaning. Each Ethernet Segment is characterized by a set of Traffic Classifiers that, in combination with classification mode (Priority/DSCP), univocally determine which frames belongs to it. Each Provider Bridge Ingress Flow is characterized by a set of Traffic Classifiers that, in combination with Classification Mode ("Priority"/"DSCP"), univocally determine which frames passes through it. See also “IP DSCP/TOS and EtherType” (p. 18-6) Classification criteria are not mutually excluded therefore some combinations of they are allowed Table 18-4 Vlan
Priority
Specific or Range
Specific or Range
Allowed combination of Traffic Classification criteria
DSCP
EtherType
Don'tCare Any value
Note Priority
Classification Type SPECIFIC VLAN CLASSIFIER SPECIFIC VLAN CLASSIFIER + ETHTYPE
.................................................................................................................................................................................................................................... 1350 OMS 18-156 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Traffic Classifiers
Overview about Traffic Classifiers
....................................................................................................................................................................................................................................
Table 18-4 Vlan Any value (except Don't care)
Priority
Allowed combination of Traffic Classification criteria
DSCP
Don'tCareSpecific or Range
EtherType IP (0x0800)
Note Dscp
(continued)
Classification Type UNTAGGED + SPECIFIC RANGE DSCP + IP SPECIFIC VLAN + SPECIFIC RANGE DSCP + ETHTYPE
Don'tCare Don'tCareSpecific or Range or NotIpPacket Untagged
Untagged
Any value (except Don't care)
Don'tCareNotIpPacket
Any value
Don'tCare Any value
Tagged
TAGGED + SPECIFIC RANGE DSCP TAGGED + NO IP TAGGED + NO IP + ETHTYPE
Untagged
UNTAGGED CLASSIFIER UNTAGGED CLASSIFIER + ETHTYPE
NotIpPacket
UNTAGGED + NO IP CLASSIFIER UNTAGGED + NO IP CLASSIFIER + ETHTYPE SPECIFIC VLAN + NO IP SPECIFIC VLAN + NO IP + ETHTYPE
Don'tCare Don'tCareDon'tCare Don'tCare Default (Don'tCare)
Default
VLAN admitted values
For the VLAN, the following values/ranges are admitted: •
Specific VLAN (0 Traffic Classifier > Delete. ...................................................................................................................................................................................................
3
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: After confirmation, the Traffic Classifier are removed.
The Traffic Classifier list is updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-164 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Traffic Classifiers
Get the Traffic Classifier Properties
....................................................................................................................................................................................................................................
Get the Traffic Classifier Properties When to use
This function gets information about a Traffic Classifier. Related Information
For more information, refer to “Traffic Classifier description” (p. 18-156). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUIMain view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Traffic Classifiers. ...................................................................................................................................................................................................
2
On the Traffic Classifier List Window, select a Traffic Classifier. Select with the right mouse button from the popup menu Properties. ...................................................................................................................................................................................................
3
The Properties window is displayed.
.................................................................................................................................................................................................................................... 1350 OMS 18-165 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Traffic Classifiers
Get the Traffic Classifier Properties
....................................................................................................................................................................................................................................
See the following topic in this document: “Details of a Traffic Classifier” (p. 18-167) Figure 18-59 Traffic Classifier Properties window
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-166 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Traffic Classifiers
Details of a Traffic Classifier
....................................................................................................................................................................................................................................
Details of a Traffic Classifier Attributes of a Traffic Classifier
The attributes displayed for each Traffic Classifier are: •
Id.
•
User Label.
•
Ethernet Segment Id.
•
Ethernet Segment.
•
VLAN Id.
•
VLAN Max.
•
Priority Identifier.
•
Priority Max.
•
EVC Port Id Label
•
ESG Port Id Label
• •
DSCP (Differentiated Services Code Point).
•
EtherType.
DSCP Max.
.................................................................................................................................................................................................................................... 1350 OMS 18-167 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet ETS Edge Physical Ports
Overview about Ethernet edge physical ports
....................................................................................................................................................................................................................................
Managing Ethernet ETS Edge Physical Ports Overview about Ethernet edge physical ports Ethernet edge physical ports description
The Ethernet edge physical ports represent the border of the network managed by the 1350 OMS PKT. They are the extremities of Ethernet Services, EVCs, and Ethernet Segments and they represent UNIs and IWIs. An Ethernet edge physical port is in the Ethernet Domain, the image of an Ethernet Physical Port (PPT) or an External Termination Point (ETP) in the Construction Domain. Ethernet edge physical port attributes
The fundamental attributes of an Ethernet physical edge port are: • •
The Activation State that tells whether the port is active or not. If active, the port can carry traffic/is carrying traffic. The VLAN Type (that identifies the VLAN Tag protocol Type used to distinguish tagged and untagged frames and to form new VLAN Tags using push operations).
Ethernet edge physical port cannot be explicitly created or deleted by the user: Port is automatically created when a proper PPT or ETP is created. Port is automatically deleted when the related Construction object is deleted. Ethernet edge physical port and VLAN
Whenever a new Ethernet edge physical port is created, it comes with an Activation State and a VLAN Type that is aligned with what defined in the NE to which the Edge port belongs. If the edge port is ETP then the Activation State is Down and the VLAN Type is the default one (that is, 8100 hexadecimal). In the scope of MEF alignment, a set of attributes is added to Ethernet Edge Port (intended as UNI). The Edge ports support the VLAN Type according to the board they belong to. The boards like ISA PR EA supports any VLAN Type. The boards like ISA PR ES supports only the standard VLAN. The boards like ISA E/FE/GE and ISA ES1/4 do not support any VLAN.
.................................................................................................................................................................................................................................... 1350 OMS 18-168 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet ETS Edge Physical Ports
Display the ETS edge port list
....................................................................................................................................................................................................................................
Display the ETS edge port list When to use
The Edge Port List window presents all the edge ports and their attributes. Related Information
For more information, refer to “Ethernet edge physical ports description” (p. 18-168). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUIMain view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The menu of the Services is shown. ...................................................................................................................................................................................................
2
Select Connection Oriented (ETS) > ETS Edge Ports. Result: The list window is displayed.
The attributes displayed for each edge port are: • User Label. • Network Element. • Usage State (Busy, Reserved, Not Meaningful, Idle). •
Rate.
•
Activation State (Down, Up).
•
VLAN Type.
•
Interface Type.
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-169 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet ETS Edge Physical Ports
Modify an edge port
....................................................................................................................................................................................................................................
Modify an edge port When to use
This function allows to modify the characteristics of a selected edge port. Related Information
For more information, refer to “Ethernet edge physical ports description” (p. 18-168). Details when modifying the edge port characteristics: •
Max Number of EVC: the number of EVC that must be allowed on that UNI. ( > = 1).
•
Service Multiplexing: new attribute for all Edge ports.
Default value: – Yes for ETS, ETS_P, ETB (Virt). –
No for ETB (MAC).
–
Modifiable in all cases except ETB (MAC).
This attribute is checked against the other attributes like: Max Number of EVC, Bundling and AllToOneBundling. The check is performed at attribute set and at UNI usage. •
Bundling: checked if the EVC can be mapped with one or more VLAN, not checked
•
if one EVC can be mapped only with one VLAN. All to one Bundling: checked if the EVC maps all VLAN existing on that UNI (that is, one EVC only on that UNI), not checked if the mapping is performed differently.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The edge port must be not active (for example: activation state equal to Down).
• •
The edge port must not be an ENE edge port. The edge port can be involved in defined Ethernet Segments only.
Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > ETS Edge Ports.
.................................................................................................................................................................................................................................... 1350 OMS 18-170 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet ETS Edge Physical Ports
Modify an edge port
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
2
On the Edge Port List, select the Edge Port to modify. Select with the right mouse button the path Modify or Action > Modify from the main menu. ...................................................................................................................................................................................................
3
The Modify Edge Port window is displayed. Figure 18-60 Edge Port Modification window
To modify the edge port characteristics: •
Max Number of EVC.
•
Service Multiplexing.
•
Bundling.
•
All to one Bundling.
...................................................................................................................................................................................................
4
Click Ok button. Result: After confirmation of the modification: the new attribute values are
downloaded to the NE at the implementation time. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-171 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet ETS Edge Physical Ports
Configure an ETS Edge Port
....................................................................................................................................................................................................................................
Configure an ETS Edge Port When to use
This function consists in configuring the VLAN type of a selected edge port. Related Information
For more information, refer to “Ethernet edge physical ports description” (p. 18-168). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • • •
The edge port must not be active (for example: activation state equal to Down). The edge port can be involved in defined Ethernet Segments only. The edge port must not be an ENE edge port.
Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > ETS Edge Ports. ...................................................................................................................................................................................................
2
On the Traffic Classifier List, select the Traffic Classifier to modify. Follow the path Action > ETS Edge Port > Edge Port Configuration.
.................................................................................................................................................................................................................................... 1350 OMS 18-172 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet ETS Edge Physical Ports
Configure an ETS Edge Port
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
3
The Edge Port configuration window is displayed. Figure 18-61 Edge Port Configuration window
To modify the edge port characteristics: •
Vlan Type: Insert the Vlan Type selecting it from the defined Vlan type list.
...................................................................................................................................................................................................
4
Click Ok button.
.................................................................................................................................................................................................................................... 1350 OMS 18-173 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet ETS Edge Physical Ports
Configure an ETS Edge Port
....................................................................................................................................................................................................................................
Result: After confirmation of the modification: the VLAN type is downloaded to the NE at the implementation time. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-174 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet ETS Edge Physical Ports
Get the ETS Edge Port Properties
....................................................................................................................................................................................................................................
Get the ETS Edge Port Properties When to use
This function gets information about an ETS edge port. Related Information
For more information, refer to “Ethernet edge physical ports description” (p. 18-168). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > ETS Edge Ports. ...................................................................................................................................................................................................
2
On the ETS Edge Port List Window, select an Edge Port. Select with the right mouse button from the popup menu Properties. ...................................................................................................................................................................................................
3
The Properties window is displayed. The attributes displayed for each edge port are: •
User Label.
•
Network Element.
•
Usage State (Busy, Reserved, Not Meaningful, Idle).
•
Rate.
•
Activation State (Down, Up).
.................................................................................................................................................................................................................................... 1350 OMS 18-175 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet ETS Edge Physical Ports
Get the ETS Edge Port Properties
....................................................................................................................................................................................................................................
• •
VLAN Type. Interface Type.
Figure 18-62 Edge Port Properties window
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-176 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet ETS Edge Physical Ports
Display the traffic parameter list
....................................................................................................................................................................................................................................
Display the traffic parameter list When to use
The Traffic Parameter List window presents all the information about the traffic parameters of the selected edge port. Related Information
This list is filled only when the Edge port is involved in an Ethernet Segment and contains Traffic Classifier and Traffic Descriptor. For more information, refer to “Ethernet edge physical ports description” (p. 18-168). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > ETS Edge Ports. ...................................................................................................................................................................................................
2
On the ETS Edge Port List Window, select an Edge Port. Select with the right mouse button from the popup menu Action from Ets Edge Port > Traffic Parameter List. Result: The Traffic Parameter List window is displayed.
See the following topic in this document: “Description of the list of Traffic Parameters” (p. 18-178) ...................................................................................................................................................................................................
3
Selecting a Traffic Parameter in the list, the corresponding properties window can be displayed selecting with the right mouse button the item Properties from the popup menu. Result: The property window is displayed.
See the following topic in this document: “Details of Traffic Parameters” (p. 18-179) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-177 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet ETS Edge Physical Ports
Description of the list of Traffic Parameters
....................................................................................................................................................................................................................................
Description of the list of Traffic Parameters Attributes of a Traffic Parameter
The attributes displayed for each traffic parameter are: •
Ethernet Flow.
•
Edge port Role.
•
Class of Service (Best Effort, Guaranteed, Regulated).
•
Traffic Descriptor associated to the Ethernet Segment.
•
CIR.
•
PIR.
•
EIR.
•
Traffic Classifier associated to the Ethernet Segment.
• •
VLAN Identifier.
•
Priority Identifier.
•
Priority Range.
VLAN Range.
.................................................................................................................................................................................................................................... 1350 OMS 18-178 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet ETS Edge Physical Ports
Details of Traffic Parameters
....................................................................................................................................................................................................................................
Details of Traffic Parameters Attributes of a Traffic Parameter
The attributes displayed for each traffic parameter are: •
Ethernet Flow.
•
Edge port Role.
•
Class of Service (Best Effort, Guaranteed, Regulated).
•
Traffic Descriptor associated to the Ethernet Segment.
•
CIR.
•
PIR.
•
EIR.
•
Traffic Classifier associated to the Ethernet Segment.
• •
VLAN Identifier.
•
Priority Identifier.
•
Priority Range.
VLAN Range.
.................................................................................................................................................................................................................................... 1350 OMS 18-179 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet ETS Edge Physical Ports
Navigation to equipment
....................................................................................................................................................................................................................................
Navigation to equipment When to use
This procedure permits to navigate to the Equipment starting from Edge Port List, with port selection. Related Information
For more information about Edge Port, refer to “Ethernet edge physical ports description” (p. 18-168). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. Note: The navigation does not run if the address of the target server is not defined in the file hosts of the PC where the MS-GUI is running. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > ETS Edge Ports. Result: The list window is shown. ...................................................................................................................................................................................................
2
Select one Edge Port in the list. ...................................................................................................................................................................................................
3
Select Search > Inventory from Edge Port > External Navigation to > GUI.
.................................................................................................................................................................................................................................... 1350 OMS 18-180 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet ETS Edge Physical Ports
Navigation to equipment
....................................................................................................................................................................................................................................
Result: The Show Equipment window is shown. Figure 18-63 Show Equipment window
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-181 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet ETS Edge Physical Ports
Show PM on an Edge Port
....................................................................................................................................................................................................................................
Show PM on an Edge Port When to use
This function Shows Performance Monitoring (PM) on a Connection Oriented Edge Port or Connection Less Edge Port. Related Information
For more information about Edge Port, refer to “Ethernet Edge Port management” (p. 11-51). For more information about PM, refer to “Quality of service: PM management ” (p. 11-69). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The Service menu is shown. ...................................................................................................................................................................................................
2
Select Connection Oriented (ETS) > ETS Edge Ports or Connection Less (Bridge) > Bridge Edge Ports. Result: The Edge Ports list is displayed. ...................................................................................................................................................................................................
3
Select the Edge Ports in the list and follow the path Search > Edge Port > Show > PM. Result: The PM related to the Edge Port is shown. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-182 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet ETS Edge Physical Ports
Show External Termination Point
....................................................................................................................................................................................................................................
Show External Termination Point When to use
This procedure show the Edge Port External Termination Points. Related Information
For more information about Edge Port, refer to “Ethernet edge physical ports description” (p. 18-168). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > ETS Edge Ports. Result: The list window is shown. ...................................................................................................................................................................................................
2
Select one Edge Port in the list. ...................................................................................................................................................................................................
3
Select Search > Edge Port > Show > External Termination Point. Result: The External Termination Point list is shown. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-183 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Transport Links
Overview about Ethernet Transport Links
....................................................................................................................................................................................................................................
Managing Ethernet Transport Links Overview about Ethernet Transport Links Ethernet Transport Link description
The Ethernet Transport Link represents the elementary link that supports the connectivity provisioned by the Ethernet Traffic Management Domain, that is, Ethernet links (and by extensions EVCs and Services). An Ethernet Transport Link is the image, on the Ethernet Domain, of a Transport Link of the Construction Domain. The Ethernet Transport Link cannot be explicitly created or deleted by the user. The Ethernet Transport Link is automatically created when a Transport Link dedicated to Ethernet is created and is automatically deleted when the related Transport Link is deleted. Transport Link attributes
Important attributes for a Transport Link are the Configuration State and, considering its extremities, the Activation State and the VLAN Type. To be able to transport Ethernet traffic, the extremities of the Transport Link must be "activated", that is, a specific configuration must be performed on the NEs that host terminations to activate them. For this reason, at creation time, the Activation State of the Transport Link terminations is checked (uploading it from the corresponding NEs) and each non-active termination is activated. To manage VLAN tagged frames, a port (and in particular an end point of a Transport Link) must be configured with a proper VLAN Tag Protocol Type (used to distinguish tagged and untagged frames and to form new VLAN Tags using push operations). The VLAN Type attribute of the Transport Link extremities is managed in two ways: •
•
at creation time, the VLAN Tag Protocol Type for each Transport Link extremity is uploaded from the related NEs and the VLAN Type attribute is set. If in the 1350 OMS PKT there is no VLAN Type equivalent of the uploaded VLAN Tag Protocol Type, a new VLAN Type (with a proper user label) is created to model the latter. an operation is provided to configure the VLAN Tag Protocol Type of the extremities of a Transport Link after its creation.
.................................................................................................................................................................................................................................... 1350 OMS 18-184 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Transport Links
Overview about Ethernet Transport Links
....................................................................................................................................................................................................................................
Transport Link states
At any time, the configuration state of an Ethernet Transport Link could be recalculated and set to: •
Configured: If both extremities are active and are configured with the same VLAN
Tag protocol type. •
Partially Configured: If only one extremity is active or when both extremities are
•
active but are configured with two different VLAN Tag protocol types. Not Configured: If both extremities are not active.
.................................................................................................................................................................................................................................... 1350 OMS 18-185 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Transport Links
Display the Ethernet ETS Transport Link list
....................................................................................................................................................................................................................................
Display the Ethernet ETS Transport Link list When to use
The Ethernet Transport Link List window presents all the Ethernet Transport Links and their attributes. Related Information
If this list is required from the Ethernet Segment List, only the Transport Links associated to the selected Ethernet Segment is displayed. If this list is required from the VLAN type list, only Transport Links whose edge ports are associated to the selected VLAN type is displayed. For details see “Overview about Ethernet Transport Links” (p. 18-184). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • •
The Transport Link must not be in use by an Ethernet Segment (Its usage state must be Idle). The Transport Link must have a SDH or Cable technology.
Task
From the MS-GUIMain view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The menu of the Services is shown. ...................................................................................................................................................................................................
2
Select Connection Oriented (ETS) > ETS Transport Links. Result: The list window is displayed.
See the following topic in this document: “Description of the list of ETS Transport Links” (p. 18-187) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-186 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Transport Links
Description of the list of ETS Transport Links
....................................................................................................................................................................................................................................
Description of the list of ETS Transport Links Attributes of an ETS Transport Link
The attributes displayed for each Transport Link are: •
User Label.
•
Subnetwork.
•
Technology (MPLS, SDH, Cable).
•
Guaranteed Bandwidth.
•
Best Effort Bandwidth.
•
Usage State (Idle, Busy, Reserved, Not Meaningful).
•
Working State (Normal, Configuring, Removing).
•
Configuration State (Configured, Partially Configured, Not Configured).
.................................................................................................................................................................................................................................... 1350 OMS 18-187 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Transport Links
Configure an ETS Transport Link
....................................................................................................................................................................................................................................
Configure an ETS Transport Link When to use
This function permits to change the VLAN Protocol Type of Transport Link extremities. Related Information
The VLAN Type is not an attribute of the Transport Link. The VLAN Type is an attribute of its extremities (that is, Transport Link terminations). So, VLAN Type is displayed in the extremity window of the Transport Link. For these reasons, while the Edge port modification command acts on one Edge port (and its attributes), the Transport Link configuration command acts only on the Transport Link terminations (that is, a shortcut for the user, to avoid him to configure separately the two terminations. For details see “Overview about Ethernet Transport Links” (p. 18-184). Transport Link states
After confirmation, the Configuration state of the Transport Link is recalculated and set to: •
Configured: if both extremities are active and are configured with the same VLAN
Tag Protocol Type. •
Partially Configured: if only one extremity is active (while the other is not active) or
•
when both extremities are active but are configured with two different VLAN Tag Protocol Types. Not Configured: if both extremities are not active.
Transport Link VLAN
The ports at the extremities of the Transport Link are active and configured with the VLAN Type: • •
They recognize as tagged only the Ethernet frames that are tagged with the same VLAN type. Any push operation (that is, VLAN constraint of type "Push") defined on them uses the specified VLAN type to create (and push) new VLAN tags.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode.
.................................................................................................................................................................................................................................... 1350 OMS 18-188 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Transport Links
Configure an ETS Transport Link
....................................................................................................................................................................................................................................
Conditions
To get a positive result: • •
The Transport Link must not be in use by an Ethernet Segment (Its usage state must be Idle). The Transport Link must have a SDH or Cable technology.
Task
From the MS-GUIMain view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > ETS Transport Links. ...................................................................................................................................................................................................
2
On the Traffic Classifier List, select the Traffic Classifier to modify. Follow the path Action > Transport Link > Transport Link Configuration. ...................................................................................................................................................................................................
3
The Transport Link configuration window is displayed. To configure a Transport Link: •
Select a Service Type (by using the sensitive help).
•
Select a VLAN Type (by using the sensitive help) or select True for the Set standard VLAN Type (8100).
...................................................................................................................................................................................................
4
Click Ok button. Result: The Transport Link configuration state is changed. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-189 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Transport Links
Get the Transport Link extremities
....................................................................................................................................................................................................................................
Get the Transport Link extremities When to use
This function gets information about the extremities of a Transport Link. Related Information
For details see “Overview about Ethernet Transport Links” (p. 18-184). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • •
The Transport Link must not be in use by an Ethernet Segment (Its usage state must be Idle). The Transport Link must have a SDH or Cable technology.
Task
From the MS-GUIMain view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > ETS Transport Links. ...................................................................................................................................................................................................
2
On the Traffic Classifier List, select the Traffic Classifier to modify. Follow the path Action > Transport Link > Extremities.
.................................................................................................................................................................................................................................... 1350 OMS 18-190 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Transport Links
Get the Transport Link extremities
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
3
The Transport Link Extremities window is displayed. Figure 18-64 Transport Link Extremities window
The window allows to modify: •
The Network Element.
•
The NE Type (by using the sensitive help).
• •
The Termination User Label (by using the sensitive help). The Activation State (by using the sensitive help).
...................................................................................................................................................................................................
4
Click Ok button.
.................................................................................................................................................................................................................................... 1350 OMS 18-191 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Transport Links
Get the Transport Link extremities
....................................................................................................................................................................................................................................
Result: After confirmation the extremities data are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-192 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Transport Links
Get the Transport Link properties
....................................................................................................................................................................................................................................
Get the Transport Link properties When to use
This function gets information about a Transport Link. Related Information
For details see “Overview about Ethernet Transport Links” (p. 18-184). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUIMain view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > ETS Transport Links. ...................................................................................................................................................................................................
2
On the Transport Link List, select the Transport Link to see the properties. Follow the path Action > Properties.
.................................................................................................................................................................................................................................... 1350 OMS 18-193 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Transport Links
Get the Transport Link properties
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
3
The Transport Link Properties window is displayed. Figure 18-65 Transport Link Properties window
...................................................................................................................................................................................................
4
Click the window Close button. Result: The properties window is closed. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-194 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Transport Links
Details of ETS Transport Links
....................................................................................................................................................................................................................................
Details of ETS Transport Links Attributes of an ETS Transport Link
The attributes displayed for each Transport Link are: •
Id.
•
User Label.
•
Subnetwork Id Label.
•
Subnetwork.
•
Technology (MPLS, SDH, Cable).
•
Directionality.
•
Ethernet Segment Id.
•
Ethernet Segment.
• •
Usage State (Idle, Busy, Reserved, Not Meaningful).
•
A END Id label.
•
Z END Id label.
•
A END Type label.
•
Z END Type label.
•
Forward cost.
•
Backward cost.
•
Guaranteed Bandwidth.
•
Best Effort Bandwidth.
•
Transport Link Label.
•
Consistency State.
•
Configuration State (Configured, Partially Configured, Not Configured).
•
VLAN Id.
•
VLAN Type.
•
NAD.
Working State (Normal, Configuring, Removing).
.................................................................................................................................................................................................................................... 1350 OMS 18-195 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Transport Links
Display the Transport Link bandwidth load
....................................................................................................................................................................................................................................
Display the Transport Link bandwidth load When to use
This function gets information about the bandwidth load of a Transport Link. Related Information
For details see “Overview about Ethernet Transport Links” (p. 18-184). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUIMain view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > ETS Transport Links. ...................................................................................................................................................................................................
2
On the Traffic Classifier List, select the Traffic Classifier to modify. Follow the path Action Transport Link > Bandwidth Load. ...................................................................................................................................................................................................
3
The Transport Link Bandwidth Load window is displayed. ...................................................................................................................................................................................................
4
Click the window Close button. Result: The properties window is closed. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-196 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Overview about Ethernet Segments
....................................................................................................................................................................................................................................
Managing Ethernet Segments Overview about Ethernet Segments Ethernet Segment description
An Ethernet Segment is a unidirectional end-to-end connection between two Ethernet physical ports (that is, between two PEs). Every Ethernet Segment is terminated by means of two Ethernet Edge ports which represent the terminations in the Provider Edges (where the Ethernet traffic "enter in"/"exit from" the managed network). An Ethernet Edge Physical port can support different Ethernet traffics. Each Ethernet Segment is built by means of a series of Ethernet Links. Ethernet Links (Transport Links) are unidirectional connections terminated by means of two Ethernet Link Terminations. The conjunction between two Ethernet Links is made by a cross connection named Ethernet Switch. Ethernet Segment representation Figure 18-66 Ethernet Segment representation
.................................................................................................................................................................................................................................... 1350 OMS 18-197 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Overview about Ethernet Segments
....................................................................................................................................................................................................................................
Bandwidth check for Transport Links
The following bandwidth checks are executed for SDH and Cable Transport Link: •
• •
The sum of all CIR of Ethernet Segments allocated using the Transport Link must be less or equal the total bandwidth of the Transport Link; this check is executed separately for forward and backward direction. The PIR of Ethernet Segment must be less than or equal to of the total bandwidth. The number of best effort Ethernet Segments must be less than or equal to the configuration limit.
Bandwidth check for MPLS connections
For MPLS Transport Link: •
The PIR, CIR, CBS and PBS of Ethernet Segment must be less than or equal to the same values associated to Transport Link.
Bandwidth check for multicast connections
The bandwidth check for multicast connections is executed taking this connection type in account. If more Ethernet Segments use the same Transport Link, the bandwidth reservation is considered only for one Ethernet Segment. For the extremities of the Ethernet Segment, the following bandwidth checks are executed: •
For Aend and Zend: The sum of CIR of the Ethernet Segment that uses the port as Aend/Zend + the CIR of the Ethernet Segment that is allocating Packet > Services. Result: The menu of the Services is shown. ...................................................................................................................................................................................................
2
Select Connection Oriented (ETS) > Ethernet Segments. Result: The list window is displayed.
See the following topic in this document: “Description of the list of Ethernet Segments” (p. 18-200) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-199 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Description of the list of Ethernet Segments
....................................................................................................................................................................................................................................
Description of the list of Ethernet Segments Ethernet Segment description
An Ethernet Segment is a unidirectional end-to-end connection between two Ethernet physical ports (that is, between two PEs). Every Ethernet Segment is terminated by means of two Ethernet Edge ports which represent the terminations in the Provider Edges (where the Ethernet traffic "enter in"/"exit from" the managed network). An Ethernet Edge Physical port can support different Ethernet traffics. Each Ethernet Segment is built by means of a series of Ethernet Links. Ethernet Links (Transport Links) are unidirectional connections terminated by means of two Ethernet Link Terminations. The conjunction between two Ethernet Links is made by a cross connection named Ethernet Switch. Ethernet Segment representation Figure 18-67 Ethernet Segment representation
Attributes of a Ethernet Segment
The attributes displayed for each Ethernet Segment are: •
User Label.
•
Subnetwork.
•
EVC.
.................................................................................................................................................................................................................................... 1350 OMS 18-200 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Description of the list of Ethernet Segments
....................................................................................................................................................................................................................................
• •
Policy Mode (Color Blind, Color Aware, Disabled).
•
Provisioning State (Defined, Partially Allocated, Allocated, Partially Implemented, Implemented).
•
Availability Status (Normal, Degraded, In Failure, Not Meaningful).
Working State (Normal, Configuring, Allocating, De-allocating, Implementing, De-implementing, Commissioning, De-commissioning, Constraint adding, Constraint removing).
.................................................................................................................................................................................................................................... 1350 OMS 18-201 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Create an Ethernet Segment
....................................................................................................................................................................................................................................
Create an Ethernet Segment When to use
This function consists in creating an Ethernet Segment. Related Information
See “Ethernet Segment description” (p. 18-197). Policy Mode Policy Mode values and meaning:
•
Disabled: no policy applies.
•
Color Blind: Policy is enabled and based only on Traffic Descriptor parameters.
•
Color Aware: Policy is enabled and based both on Traffic Descriptor parameters and on Color Profile.
Color Profile
Color Profile depends on the selected Policy Mode: •
Policy Mode = Disabled: Color Profile can be defined.
•
Policy Mode = Color Aware: Color Profile must be defined.
•
Policy Mode = Color Blind: Color Profile cannot be defined.
Traffic Descriptor
Traffic Descriptor depends on the selected Policy Mode: •
Policy Mode = Disabled: No Traffic Descriptor.
•
Policy Mode = Color Aware: the Traffic Descriptor must be Regulated.
•
Policy Mode = Color Blind: the Traffic Descriptor must be Best Effort or Guaranteed.
Priority Mode Priority Mode depends on the Policy Mode:
• •
If Policy Mode is Color Blind, choose the Priority Id value between 0 and 7, Untagged, Do not care. The Priority Id is priority of all the packets after the push. If Policy Mode is Color Aware, choose Green Priority and Yellow Priority for all green and yellow outgoing packets.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode.
.................................................................................................................................................................................................................................... 1350 OMS 18-202 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Create an Ethernet Segment
....................................................................................................................................................................................................................................
Conditions
To get a positive result: • • •
At least, one EVC, one Color Profile, one Traffic Descriptor, and two Edge Physical Ports must exist. The User Label must be not in use. The Edge Physical Port can be in use by another Ethernet Segment provided that it belongs to the same Ethernet service.
Task
From the MS-GUIMain view: ...................................................................................................................................................................................................
1
Select Action > Packet > Services > Connection Oriented (ETS) > Create Ethernet Segment. ...................................................................................................................................................................................................
2
To create an Ethernet Segment: On the Ethernet Segment Creation window General Panel •
Enter an Ethernet Segment User label.
•
Enter the EVC the Ethernet Segment belongs to.
•
•
Choose the EVC Termination or ENE on side "A" and on side "Z" by using the sensitive help (each termination is composed of 'Network Element'+'User Label'+'Role'). Choose a Traffic Descriptor by using the sensitive help. See “Traffic Descriptor” (p. 18-202). Select a Policy Mode (Disabled, Color Blind, Color Aware). See “Policy Mode” (p. 18-202). Define a Color Profile by using the sensitive help (Regulated, Best Effort, Guaranteed). See “Color Profile” (p. 18-202). Select the Classification Mode (Priority, DSCP).
•
Enter a Comment (optional).
• • •
...................................................................................................................................................................................................
3
On the Pop Panel enter following data: Execute the following steps: •
Specify a list of Traffic Classifiers references by using the icon that lists the Traffic Classifier.
•
Select one or more Traffic Classifier.
...................................................................................................................................................................................................
4
On the Push Panel enter following data:
.................................................................................................................................................................................................................................... 1350 OMS 18-203 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Create an Ethernet Segment
....................................................................................................................................................................................................................................
Execute the following steps: •
Enter the VLAN Id to be pushed.
•
Select a Policy Mode (Disabled, Color Blind, Color Aware). See “Policy Mode” (p. 18-202). Select the Priority Id (0, …,7, Untagged, Do not care,Green Priority,Yellow Priority).
•
...................................................................................................................................................................................................
5
Click Ok. Result: The Ethernet Segment is created into the 1350 OMS PKT with the following
state: •
Provisioning State: Defined.
•
Availability Status: Normal.
•
Working State: Normal.
If the usage state of each EVC termination is idle, the usage state is marked busy. The tree area, the Ethernet Segment list, and the EVC list are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-204 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Modify an Ethernet Segment
....................................................................................................................................................................................................................................
Modify an Ethernet Segment When to use
The function modifies Ethernet Segment characteristics. Related Information
See “Ethernet Segment description” (p. 18-197). See “Color Profile” (p. 18-202). See “Traffic Descriptor” (p. 18-202). The Ethernet modification gives the possibility to modify one or all the following parameters: • • •
Ethernet Segment User Label. Color Profile. Traffic Descriptor.
•
Comment.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • • •
If the User Label is modified, the new User Label must not be in use by another Ethernet Segment. Traffic Descriptor is modifiable only when Ethernet Segment provisioning state is Defined. Color Profile is modifiable only when Ethernet Segment provisioning state is Defined or Allocated.
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > Ethernet Segments. ...................................................................................................................................................................................................
2
On the Ethernet Segment List Window, select the Segment to modify. Click the right mouse button and select Modify on the popup menu.
.................................................................................................................................................................................................................................... 1350 OMS 18-205 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Modify an Ethernet Segment
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
3
The Modify Segment window is displayed. Figure 18-68 Ethernet Segment Modification window
To modify an Ethernet Segment: •
Enter a new User Label.
• • •
Choose a new Traffic Descriptor by using the sensitive help, according to the Policy Mode. Modify the Color Profile, by using the sensitive help, according to the Policy Mode. Modify the Classification Mode (Priority, DSCP).
•
Modify the Comment (optional).
.................................................................................................................................................................................................................................... 1350 OMS 18-206 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Modify an Ethernet Segment
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
Click Ok. Result: The segment is modified.
If the Ethernet User Label is modified, the tree area, the Ethernet Segment list, and the opened graphical views are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-207 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Delete an Ethernet Segment
....................................................................................................................................................................................................................................
Delete an Ethernet Segment When to use
This function consists in deleting an Ethernet Segment from the 1350 OMS PKT supervision. Related Information
See “Ethernet Segment description” (p. 18-197). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The Ethernet Segment Provisioning state must be Defined.
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > Ethernet Segments. ...................................................................................................................................................................................................
2
On the Traffic Classifier List Window, select the traffic descriptor to delete. Select with the right mouse button from the popup menu Action > Ethernet Segment > Delete. ...................................................................................................................................................................................................
3
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: After confirmation, the Ethernet Segments are deleted.
If the Ethernet Edge Physical Port terminating the deleted Ethernet Segments is no more used by any other Ethernet Segment, the Ethernet Edge Physical Port is marked as "not busy" (Usage State set to idle). The provisioning state of parent EVC is recalculated. The Ethernet Segment list, the tree area, and the opened graphical views are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-208 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Associate a Traffic Classifier to an Ethernet Segment
....................................................................................................................................................................................................................................
Associate a Traffic Classifier to an Ethernet Segment When to use
This function consists in associating a Traffic Classifier to an Ethernet Segment. Related Information
One or more Traffic Classifier can be associated to an Ethernet Segment. If two Ethernet Segments share the same Edge port, the Traffic Classifiers associated to them must refer different VLAN Bit and Priority Bit. See “Ethernet Segment description” (p. 18-197). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The Ethernet Segment Provisioning state must be Defined.
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
From the Multi Service GUI Main view, follow the path Search > Packet > Services > Connection Oriented (ETS) > Ethernet Segments. ...................................................................................................................................................................................................
2
Select the Ethernet Segment in the list. ...................................................................................................................................................................................................
3
Follow the path Action > ETS Ethernet Segment > Associate Traffic Classifier.
.................................................................................................................................................................................................................................... 1350 OMS 18-209 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Associate a Traffic Classifier to an Ethernet Segment
....................................................................................................................................................................................................................................
Result: The corresponding windows opens. Figure 18-69 Traffic Classifier Association (to an Ethernet Segment) window
...................................................................................................................................................................................................
4
To associate a Traffic Classifier to an Ethernet Segment: •
Choose a Traffic Classifier by using the sensitive help.
•
Click Ok button. Result: After confirmation, the Traffic Classifier is associated to the Ethernet
Segment. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-210 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Disassociate a Traffic Classifier to an Ethernet Segment
....................................................................................................................................................................................................................................
Disassociate a Traffic Classifier to an Ethernet Segment When to use
This function consists in disassociating a Traffic Classifier from an Ethernet Segment. Related Information
See “Ethernet Segment description” (p. 18-197). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The Ethernet Segment Provisioning state must be Defined.
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > Ethernet Segments. ...................................................................................................................................................................................................
2
Select the Ethernet Segment in the list. ...................................................................................................................................................................................................
3
Follow the path Action > ETS Ethernet Segment > Disassociate Traffic Classifier.
.................................................................................................................................................................................................................................... 1350 OMS 18-211 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Disassociate a Traffic Classifier to an Ethernet Segment
....................................................................................................................................................................................................................................
Result: The corresponding windows opens. Figure 18-70 Traffic Classifier disassociation (from an Ethernet Segment) window
...................................................................................................................................................................................................
4
To disassociate a Traffic Classifier from an Ethernet Segment: • •
Choose a Traffic Classifier by using the sensitive help (only the associated Traffic Classifiers to the concerned Ethernet Segment are displayed). Click Ok button. Result: After confirmation, the Traffic Classifier is disassociated from the Ethernet
Segment. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-212 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Add a constraint to an Ethernet Segment
....................................................................................................................................................................................................................................
Add a constraint to an Ethernet Segment When to use
This function consists in adding an allocation constraint to an Ethernet Segment. Related Information
See “Ethernet Segment description” (p. 18-197). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The Ethernet Segment Provisioning state must be Defined.
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Oriented (ETS) > Ethernet Segments. ...................................................................................................................................................................................................
2
Select the Ethernet Segment in the list. ...................................................................................................................................................................................................
3
Follow the path Action > ETS Ethernet Segment > Add Constraint to an Ethernet Segment.
.................................................................................................................................................................................................................................... 1350 OMS 18-213 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Add a constraint to an Ethernet Segment
....................................................................................................................................................................................................................................
Result: The corresponding windows opens. Figure 18-71 Add Constraint to an Ethernet Segment window (Pop)
.................................................................................................................................................................................................................................... 1350 OMS 18-214 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Add a constraint to an Ethernet Segment
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
To add a constraint to an Ethernet Segment: •
Choose a Transport Link by using the sensitive help.
•
On the Push Panel, execute the following steps: – Enter the VLAN Id to be pushed. –
•
Select a Policy Mode (Disabled, Color Blind, Color Aware). See “Policy Mode” (p. 18-202). – Select the Priority Id (0, …,7, Untagged, Do not care,Green Priority,Yellow Priority). Click Ok button. Result: If the Constraint List is opened, this window is updated with the new added
constraint. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-215 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
List the constraints related to an Ethernet Segment
....................................................................................................................................................................................................................................
List the constraints related to an Ethernet Segment When to use
This function consists in getting the list of constraints related to an Ethernet Segment. Related Information
See “Ethernet Segment description” (p. 18-197). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The Ethernet Segment Provisioning state must be Defined.
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > Ethernet Segments. ...................................................................................................................................................................................................
2
Select the Ethernet Segment in the list. ...................................................................................................................................................................................................
3
Select Search > Inventory from Ethernet Segment > List Constraints. Result: The list window is displayed.
See the following topic in this document: “Description of the list of Constraints” (p. 18-217) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-216 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Description of the list of Constraints
....................................................................................................................................................................................................................................
Description of the list of Constraints Attributes of a Constraint
The attributes displayed for each constraint are: •
Constraint Entity User Label (= user label of the Transport Link).
•
Constraint Type (Use, Not Use, Use For Multicast).
.................................................................................................................................................................................................................................... 1350 OMS 18-217 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Delete an Ethernet Segment Constraint
....................................................................................................................................................................................................................................
Delete an Ethernet Segment Constraint When to use
This function consists in deleting a constraint associated to an Ethernet Segment. Related Information
See “Ethernet Segment description” (p. 18-197). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • •
The Ethernet Segment Provisioning state must be Defined. No operation is pending on the selected Ethernet Segment.
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Oriented (ETS) > Ethernet Segments. ...................................................................................................................................................................................................
2
On the traffic Ethernet Segment list Window, select the Ethernet Segment to which the constraint belongs. Follow the path Search > Inventory from Ethernet Segment > List Constraints. ...................................................................................................................................................................................................
3
Select the constraint to delete. ...................................................................................................................................................................................................
4
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: After confirmation, the Ethernet Segment constraints are dissociated from the
related Ethernet Segment and removed. The Ethernet Segment Constraint list is updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-218 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Get the Ethernet Segment Constraint Properties
....................................................................................................................................................................................................................................
Get the Ethernet Segment Constraint Properties When to use
This function consists in getting information about a constraint associated to an Ethernet Segment. Related Information
See “Ethernet Segment description” (p. 18-197). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The Ethernet Segment Provisioning state must be Defined.
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Oriented (ETS) > Ethernet Segments. ...................................................................................................................................................................................................
2
On the Traffic Classifier List Window, select the Ethernet Segment. ...................................................................................................................................................................................................
3
Follow the path Search > Inventory from Ethernet Segment > List Constraints, select the constraint in the list. ...................................................................................................................................................................................................
4
Select with the right mouse button from the popup menu Properties. ...................................................................................................................................................................................................
5
The Properties window is displayed.
.................................................................................................................................................................................................................................... 1350 OMS 18-219 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Get the Ethernet Segment Constraint Properties
....................................................................................................................................................................................................................................
See the following topic in this document: “Details of an Ethernet Segment Constraint” (p. 18-221) Figure 18-72 Ethernet Segment constraint properties window
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-220 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Details of an Ethernet Segment Constraint
....................................................................................................................................................................................................................................
Details of an Ethernet Segment Constraint Attributes of an Ethernet Segment Constraint
The attributes displayed for each constraint are: •
Id.
•
Constrained Class.
•
Constrained Class Id Label.
•
Constrained Entity User Label.
•
Constraint Class.
•
Constraint Class Id Label.
•
Constraint Entity User Label (= user label of the Transport Link).
•
Constraint Type (Use, Not Use, Use For Multicast).
• •
Replication Factor.
•
Yellow Priority.
•
Green Priority.
•
Priority Mode.
•
Number of Traffic Classifiers.
VLAN Id.
.................................................................................................................................................................................................................................... 1350 OMS 18-221 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Modify a Constraint
....................................................................................................................................................................................................................................
Modify a Constraint When to use
The function modifies Ethernet Segment Constraint characteristics. Related Information
See “Ethernet Segment description” (p. 18-197). The Constraint modification gives the possibility to modify one or all the constraint parameters: • • •
VLAN Identifier. Policy Mode. Priority Id.
• •
Green Priority. Yellow Priority.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • •
The Ethernet Segment Provisioning state must be Defined. No operation is pending on the selected Ethernet Segment.
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Oriented (ETS) > Ethernet Segments. ...................................................................................................................................................................................................
2
On the Ethernet Segment List Window, select the Ethernet Segment. ...................................................................................................................................................................................................
3
Follow the path Search > Inventory from Ethernet Segment > List Constraints, select the constraint in the list. ...................................................................................................................................................................................................
4
Select with the right mouse button from the popup menu Modify.
.................................................................................................................................................................................................................................... 1350 OMS 18-222 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Modify a Constraint
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
5
The Properties window is displayed. Figure 18-73 Constraint Modification window
...................................................................................................................................................................................................
6
To modify a constraint, modify one or all the following parameters: •
On Pop Panel. Execute the following step: –
•
Choose a Traffic Classifier by using the sensitive help and Add button to insert it.
On Push Panel.
.................................................................................................................................................................................................................................... 1350 OMS 18-223 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Modify a Constraint
....................................................................................................................................................................................................................................
Execute the following steps: – Enter a new VLAN Id. – Modify Policy Mode (Color Blind or Color Aware). – Modify Priority Id, Green Priority and/or Yellow Priority. ...................................................................................................................................................................................................
7
Confirm the modifications with Ok button. Result: If the VLAN Id is modified, after modification, the VLAN Constraint list is
updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-224 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
VLAN Push/Pop at ETS NNI Interface
....................................................................................................................................................................................................................................
VLAN Push/Pop at ETS NNI Interface Overview
The Vlan Push/Pop mechanism is extended to ETS domain, to allow the encapsulation of untagged or C-Vlan Tagged Ethernet frames, with a Provider VLAN Tag. This behavior is used to route the traffic in segregated way either only internally to the managed network or for inter-working purpose. The difference for this operation is that the definition of VLAN constraint is performed before the segment allocation. Early definition allows the VLAN stacking on NNI. See “Ethernet Segment description” (p. 18-197). Sequence of operations
The new sequence of operations is: • • • • • •
Create an Ethernet Segment. Associate a Traffic Classifier. Definition of route Constraints (allowing to define the full routes of Ethernet traffic). Definition of VLAN Constraints, defining the points where the Push/Pop on NNI must be performed. Allocation of the Ethernet Segment. Implementation.
.................................................................................................................................................................................................................................... 1350 OMS 18-225 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Allocate an Ethernet Segment
....................................................................................................................................................................................................................................
Allocate an Ethernet Segment When to use
This function consists in finding a route between the end physical ports of the Ethernet Segment. Related Information
See “Ethernet Segment description” (p. 18-197). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • • • •
The Ethernet Segment Provisioning state must be Defined. A list of constraints containing all Transport Links used is associated to the Ethernet Segment. Traffic profile, Traffic Descriptor, and Traffic Classifier must be associated to the Ethernet Segment. No operation is pending on the Ethernet Segment.
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > Ethernet Segments. ...................................................................................................................................................................................................
2
Select the Ethernet Segment in the list. ...................................................................................................................................................................................................
3
Follow the path Action > Ethernet Segment > Allocate. Result: A confirmation box is displayed.
The 1350 OMS PKT checks the 'validation' of the Transport Links to be used in term of traffic type, bandwidth, and continuity of the chosen Transport Links. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-226 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Deallocate an Ethernet Segment
....................................................................................................................................................................................................................................
Deallocate an Ethernet Segment When to use
This function consists in finding a route between the end physical ports of the Ethernet Segment. Related Information
See “Ethernet Segment description” (p. 18-197). After confirmation: • • • • •
deletion of the VLAN constraints related to each Ethernet Segment is done (no more VLAN constraint is associated to them). Then the Ethernet Segment List is updated with provisioning state set to Defined. The provisioning state of related EVC is updated in Defined or Partially Allocated. The bandwidth parameters of all involved Transport Links are updated taken into account the bandwidth freed by the de-allocation. If the de-allocated segment is the last using the Transport Link, the Transport Link usage state is set to Idle.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The Ethernet Segment Provisioning state must be Defined.
•
No operation is pending on the Ethernet Segment.
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > Ethernet Segments. ...................................................................................................................................................................................................
2
Select the Ethernet Segment in the list. ...................................................................................................................................................................................................
3
Follow the path Action > Ethernet Segment > Deallocate.
.................................................................................................................................................................................................................................... 1350 OMS 18-227 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Deallocate an Ethernet Segment
....................................................................................................................................................................................................................................
Result: A confirmation box is displayed.
The 1350 OMS PKT checks the 'validation' of the Transport Links to be used in term of traffic type, bandwidth, and continuity of the chosen Transport Links. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-228 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Implement an Ethernet Segment
....................................................................................................................................................................................................................................
Implement an Ethernet Segment When to use
This function establishes an Ethernet flow over an Ethernet Segment. Related Information
See “Ethernet Segment description” (p. 18-197). In case of correct execution, all the Ethernet Segment connections inside the NE are implemented. The Ethernet Segment is updated into the 1350 OMS PKT with the following states: •
Provisioning State: Implemented.
•
Consistency State: Consistent.
•
Availability Status: Available.
In case of errors, the Ethernet Segment is set to: •
Provisioning State: Partially Implemented.
•
Consistency State: Not Consistent.
•
Availability Status: Not Available.
The provisioning state of the related EVC is also updated to Implemented or Partially Implemented. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • • •
The Ethernet Segment provisioning state must be set to Implemented or Partially Implemented. The NE extremities must not be locked (that is, audit/alignment/reserve not in progress). No operation is pending on the Ethernet Segment.
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > Ethernet Segments.
.................................................................................................................................................................................................................................... 1350 OMS 18-229 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Implement an Ethernet Segment
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
2
Select the Ethernet Segment in the list. ...................................................................................................................................................................................................
3
Select Action > Ethernet Segment > Implement. Result: A confirmation box is displayed. ...................................................................................................................................................................................................
4
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: After confirmation, the 1350 OMS PKT implements the Ethernet Segments.
The Ethernet Segment List is updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-230 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Deimplement an Ethernet Segment
....................................................................................................................................................................................................................................
Deimplement an Ethernet Segment When to use
This function removes an Ethernet flow over an Ethernet Segment. Related Information
See “Ethernet Segment description” (p. 18-197). In case of correct execution, all the Ethernet Segment connections inside the NE are de-implemented. The Ethernet Segment is updated into the 1350 OMS PKT with the following states: •
Provisioning State: Allocated.
•
Consistency State: Not Meaningful.
•
Availability Status: Not Meaningful.
In case of errors, the Ethernet Segment is set to: •
Provisioning State: Partially Implemented.
•
Consistency State: Not Consistent.
•
Availability Status: Not Available.
The provisioning state of the related EVC is also updated in Allocated or Partially Implemented. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The Ethernet Segment provisioning state must be set to Allocated.
•
The NE extremities must not be locked (that is, audit/alignment/reserve not in progress). No operation is pending on the Ethernet Segment.
• Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Oriented (ETS) > Ethernet Segments.
.................................................................................................................................................................................................................................... 1350 OMS 18-231 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Deimplement an Ethernet Segment
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
2
Select the Ethernet Segment in the list. ...................................................................................................................................................................................................
3
Follow the path Action > Ethernet Segment > Deimplement. Result: A confirmation box is displayed. ...................................................................................................................................................................................................
4
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: After confirmation, the 1350 OMS PKT de-implements the Ethernet Segments.
The Ethernet Segment List is updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-232 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Configure an Ethernet Segment
....................................................................................................................................................................................................................................
Configure an Ethernet Segment When to use
This function consists in configuring an Ethernet Segment, that is, assigning a traffic descriptor to the Ethernet Segment. Related Information
See “Ethernet Segment description” (p. 18-197). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The Ethernet Segment provisioning state must be set to Implemented or Partially Implemented.
Task
From the Multi Service GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Oriented (ETS) > Ethernet Segments. ...................................................................................................................................................................................................
2
On the Ethernet Segment List Window, select the Ethernet Segment. ...................................................................................................................................................................................................
3
Follow the path Action > Ethernet Segment > Configure.
.................................................................................................................................................................................................................................... 1350 OMS 18-233 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Configure an Ethernet Segment
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
The Configuration window is displayed. Figure 18-74 Ethernet Segment Configuration window
...................................................................................................................................................................................................
5
To configure the selected Ethernet Segment: •
Choose a Traffic Descriptor by using the sensitive help.
•
Click Ok button. Result: After confirmation, the traffic descriptor is associated to the Ethernet
Segment. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-234 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Get the Ethernet Segment extremities
....................................................................................................................................................................................................................................
Get the Ethernet Segment extremities When to use
This function gets information about the extremities of an Ethernet Segment. Related Information
See “Ethernet Segment description” (p. 18-197). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
No operation is pending on the selected Ethernet Segment.
Task
From the Multi Service GUI Main view ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Oriented (ETS) > Ethernet Segments. ...................................................................................................................................................................................................
2
On the Ethernet Segment List Window, select the Ethernet Segment. ...................................................................................................................................................................................................
3
Follow the path Search > Inventory from Ethernet Segment > Extremities. ...................................................................................................................................................................................................
4
The Extremities window is displayed.
.................................................................................................................................................................................................................................... 1350 OMS 18-235 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Get the Ethernet Segment extremities
....................................................................................................................................................................................................................................
See the following topic in this document: “Description of the list of Ethernet Segment Extremities” (p. 18-239) Figure 18-75 Ethernet Segment Extremities window
...................................................................................................................................................................................................
5
To modify a segment extremity Click Modify Button, for the Origin A following window is displayed.
.................................................................................................................................................................................................................................... 1350 OMS 18-236 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Get the Ethernet Segment extremities
....................................................................................................................................................................................................................................
Result: The Extremities modification window is displayed. Figure 18-76 Ethernet Segment Extremity Modification window (Origin)
...................................................................................................................................................................................................
6
Choose a Traffic Classifier by using the sensitive help and Add button to insert it. ...................................................................................................................................................................................................
7
Click Modify button for the Destination Z.
.................................................................................................................................................................................................................................... 1350 OMS 18-237 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Get the Ethernet Segment extremities
....................................................................................................................................................................................................................................
Result: Following window is displayed. Figure 18-77 Ethernet Segment Extremity Modification window (Destination)
...................................................................................................................................................................................................
8
Execute the following steps: •
Enter a new VLAN Id.
•
Modify Priority Mode (Color Blind or Color Aware).
•
Modify Priority Id, Green Priority and/or Yellow Priority.
...................................................................................................................................................................................................
9
Confirm with Ok button. Result: Ethernet Segment Extremities characteristics change. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-238 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Description of the list of Ethernet Segment Extremities
....................................................................................................................................................................................................................................
Description of the list of Ethernet Segment Extremities Attributes of an Ethernet Segment Extremity
The attributes displayed for each object are: •
User Label.
•
User Label (A).
•
Committed Rate (A).
•
Rate (A).
•
Network Element (A).
•
Usage State (A).
•
Vlan Type (A).
•
User Label (Z).
• •
Committed Rate (Z).
•
Network Element (Z).
•
Usage State (Z).
•
Vlan Type (Z).
•
VLAN Id.
•
Priority Mode.
•
Green Priority.
Rate (Z).
The attributes displayed for each Ethernet Segment extremity are: Origin (A), Destination (Z): • • • •
User Label. Committed Rate. Rate. Network Element.
• •
Usage State (Idle, Busy). Vlan Type.
.................................................................................................................................................................................................................................... 1350 OMS 18-239 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Get the Ethernet Segment properties
....................................................................................................................................................................................................................................
Get the Ethernet Segment properties When to use
This function gets information about an Ethernet Segment. Related Information
See “Ethernet Segment description” (p. 18-197). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
No operation is pending on the selected Ethernet Segment.
Task
From the Multi Service GUI Main view ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Oriented (ETS) > Ethernet Segments. ...................................................................................................................................................................................................
2
On the Ethernet Segment List Window, select the Ethernet Segment. ...................................................................................................................................................................................................
3
Follow the path Action > Properties. Result: The Properties window is displayed.
See the following topic in this document: “Details of an Ethernet Segment” (p. 18-241) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-240 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Details of an Ethernet Segment
....................................................................................................................................................................................................................................
Details of an Ethernet Segment Attributes of a Ethernet Segment
The attributes displayed for each Ethernet Segment are: •
User Label.
•
Subnetwork.
•
EVC.
•
Policy Mode (Color Blind, Color Aware, Disabled).
•
Working State (Normal, Configuring, Allocating, De-allocating, Implementing, De-implementing, Commissioning, De-commissioning, Constraint adding, Constraint removing).
•
Provisioning State (Defined, Partially Allocated, Allocated, Partially Implemented, Implemented).
•
Availability Status (Normal, Degraded, In Failure, Not Meaningful).
.................................................................................................................................................................................................................................... 1350 OMS 18-241 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Display the route of an Ethernet Segment
....................................................................................................................................................................................................................................
Display the route of an Ethernet Segment When to use
This function gets graphical information about the Transport Links used (crossed) by an Ethernet Segment. Related Information
See “Ethernet Segment description” (p. 18-197). The following commands are available from the graphical view, depending on the selected object and its position on the route: • •
With no selection: Begin of Route and End of Route commands allow to highlight the NE used for the beginning or the end of the route. With a selected entity (NE, Transport Link, ENE, Off page connector): Begin of Route and End of Route commands are completed by other commands depending on the selected entity.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the Multi Service GUI Main view ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Oriented (ETS) > Ethernet Segments. ...................................................................................................................................................................................................
2
On the Ethernet Segment List Window, select the Ethernet Segment. ...................................................................................................................................................................................................
3
Follow the path Display Route.
.................................................................................................................................................................................................................................... 1350 OMS 18-242 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Display the route of an Ethernet Segment
....................................................................................................................................................................................................................................
Result: The Route Display window is displayed.
The Transport Links used by the Ethernet Segment appears in blue. Figure 18-78 Route Display - Ethernet Segment window
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-243 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Display the connectivity view of an Ethernet Segment
....................................................................................................................................................................................................................................
Display the connectivity view of an Ethernet Segment When to use
This function gets graphical information about the connectivity view of an Ethernet Segment. Related Information
See “Ethernet Segment description” (p. 18-197). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the Multi Service GUI Main view ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Oriented (ETS) > Ethernet Segments. ...................................................................................................................................................................................................
2
On the Ethernet Segment List Window, select the Ethernet Segment. ...................................................................................................................................................................................................
3
Follow the path Connectivity view.
.................................................................................................................................................................................................................................... 1350 OMS 18-244 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing Ethernet Segments
Display the connectivity view of an Ethernet Segment
....................................................................................................................................................................................................................................
Result: The Connectivity view window is displayed. Figure 18-79 Connectivity view - Ethernet Segment window
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-245 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing VLAN types
Overview
....................................................................................................................................................................................................................................
Managing VLAN types Overview about VLAN types VLAN types description
The VLAN type entity models the VLAN Tag Protocol Type allowing the user to give a name (user label) to a specific VLAN Tag Protocol Type (either standard or not) to ease its subsequent usage in the scope of VLAN management. The VLAN can be associated to an Ethernet edge port or a Provider Network before the creation of the Ethernet Segment (mapping model). If VLAN is associated to an Ethernet Segment (tunneling model), association induces the propagation to the edge ports. A VLAN Protocol type value could be duplicated according to its usage. Note: The creation and modification of a VLAN Tag Protocol Type over an active Ethernet interface has an influence on the active traffic. Only if the Ethernet Interface is not affected by Active traffic, this operation is allowed. The provisioning state of all EVCs and all Ethernet Segments using the interface is checked.
.................................................................................................................................................................................................................................... 1350 OMS 18-246 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing VLAN types
Display the VLAN type list
....................................................................................................................................................................................................................................
Display the VLAN type list When to use
This function gets graphical information about the connectivity view of an Ethernet Segment. Related Information
See “Overview about VLAN types” (p. 18-246). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The menu of the Services is shown. ...................................................................................................................................................................................................
2
Select VLAN. Result: The list window is displayed.
The attributes displayed for each VLAN Type are: • User Label. • Protocol Type (VLAN Id in hexadecimal value). • Role (Customer, Provider). E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-247 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing VLAN types
Create a VLAN type
....................................................................................................................................................................................................................................
Create a VLAN type When to use
This function consists in defining a VLAN Type and a user label to identify it (for example in the operations of association to Edge Ports). Related Information
To give maximum flexibility to the user, creation of two or more VLAN types with the same VLAN Tag Protocol Type is possible. See “Overview about VLAN types” (p. 18-246). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • •
The User Label must be different from the existing ones. The maximum number of VLAN types must not be reached.
Task
From the Multi Service GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > VLANs. ...................................................................................................................................................................................................
2
Follow the path Action > Add VLAN.
.................................................................................................................................................................................................................................... 1350 OMS 18-248 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing VLAN types
Create a VLAN type
....................................................................................................................................................................................................................................
Result: The creation window is displayed. Figure 18-80 VLAN Type Creation window
...................................................................................................................................................................................................
3
To create a VLAN type: •
Enter a VLAN type User label.
•
Enter a VLAN Tag Protocol Type (hexadecimal value between 05dd a ffff ).
.................................................................................................................................................................................................................................... 1350 OMS 18-249 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing VLAN types
Create a VLAN type
....................................................................................................................................................................................................................................
If Protocol Type is equal to 8100 (hex), Role attribute is set to Customer otherwise Role is set to Provider. ...................................................................................................................................................................................................
4
Confirm the modifications with Ok button. Result: The VLAN Type is created and the VLAN Type List is updated.
. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-250 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing VLAN types
Modify a VLAN type
....................................................................................................................................................................................................................................
Modify a VLAN type When to use
The function modifies VLAN type characteristics. Related Information
See “Overview about VLAN types” (p. 18-246). The VLAN type modification gives the possibility to modify one or all the following parameters: • •
VLAN type User Label. VLAN Tag Protocol Type (hexadecimal value).
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
If the User Label is modified, the new User Label must be not in use by another VLAN Type.
•
The VLAN type must not be not in use by any Provider Network, Edge Port, Transport link, or Transport link end point.
Task
From the Multi Service GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > VLANs. ...................................................................................................................................................................................................
2
On the VLAN List Window, select the VLAN Type to modify. ...................................................................................................................................................................................................
3
Follow the path Action > Modify.
.................................................................................................................................................................................................................................... 1350 OMS 18-251 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing VLAN types
Modify a VLAN type
....................................................................................................................................................................................................................................
Result: The modification window is displayed. Figure 18-81 VLAN Type Modification window
...................................................................................................................................................................................................
4
To modify a VLAN type: •
Enter a new User Label (optional).
•
Modify the VLAN Tag Protocol Type value (optional).
If new VLAN Tag Protocol Type is equal to 8100 (hex), Role attribute is set to Customer otherwise Role is set to Provider. ...................................................................................................................................................................................................
5
Confirm the modifications with Ok button. Result: After confirmation of the modification: the VLAN Type List is updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-252 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management Managing VLAN types
Delete a VLAN type
....................................................................................................................................................................................................................................
Delete a VLAN type When to use
This function consists in deleting a VLAN type from the 1350 OMS PKT supervision. Related Information
See “Overview about VLAN types” (p. 18-246). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The VLAN type must not be used. It must not be associated to any provider network, edge port, or Transport Link end point.
Task
From the Multi Service GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > VLANs. ...................................................................................................................................................................................................
2
On the traffic VLAN list Window, select the VLAN Type to delete. ...................................................................................................................................................................................................
3
Follow the path Action > Delete. ...................................................................................................................................................................................................
4
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: After confirmation, the VLAN types are removed and the VLAN Type List is
updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 18-253 8DG42227DAAA 9.6 Issue 3 December 2012
End to End Ethernet Provisioning Management
Delete a VLAN type
....................................................................................................................................................................................................................................
.................................................................................................................................................................................................................................... 1350 OMS 18-254 8DG42227DAAA 9.6 Issue 3 December 2012
19
19 Bridge Network Management
Overview Purpose
This chapter describes how to set up a Connection Less network (Provider Bridge). Contents Connection Less Networks
19-4
Bridge Network Management
19-4
Bridge Traffic Management
19-6
Spanning Tree Instance Management
19-8
VLAN management
19-10
EVC Data Plane
19-11
The EVC life cycle
19-13
Layer-2 Control Protocol Processing
19-16
Bandwidth Profile per UNI
19-18
View the list of bridge NEs
19-22
Description of the list of Bridge NEs
19-23
View the list of bridge ENEs
19-24
Description of the list of Bridge ENEs
19-25
View the Provider Bridge Flows of an EVC
19-26
Connection Less Transport Link Management
19-27
Display the Ethernet Bridge Transport Link list
19-27
Description of the list of Bridge Transport Links
19-29
Configure a transport Link
19-30
Get the Transport Link extremities
19-34
Description of the list of Transport Link extremities
19-37
Get the Transport Link properties
19-38
................................................................................................................................................................................................................................... 1350 OMS 19-1 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management
Overview
....................................................................................................................................................................................................................................
Details of an ETB Transport Link
19-40
Activate a Bridge Transport Link
19-41
Deactivate a Bridge Transport Link
19-42
View the list of Bridge Edge Ports
19-43
Description of the list of Bridge Edge Ports
19-44
Activate a Bridge Edge Port
19-45
Deactivate a Bridge Edge Port
19-46
Connection Less EVC Management
19-47
View the Connection Less EVC list
19-47
Description of the list of Bridge EVCs
19-48
Create a Bridge EVC
19-49
Modify a Bridge EVC
19-53
Delete a Bridge EVC
19-56
Get the EVC properties
19-58
Details of a Bridge EVC
19-60
Configure a Bridge or an ETS EVC
19-61
Add bridge Transport Link to EVC
19-62
Remove bridge Transport Link to EVC
19-63
Inventory of bridge Transport Links of an EVC
19-64
EVC Fault Localization
19-65
Description of the list of Fault Localization
19-68
Description of the list of Alarms
19-69
Navigation to AS
19-70
Bridge EVC Termination Management
19-72
View the list of EVC terminations
19-72
Description of the list of EVC Terminations
19-73
Add Connection Less EVC Termination
19-74
Delete a Bridge EVC Termination
19-81
Configure a Bridge EVC Termination
19-83
Get the EVC termination properties
19-85
Details of an EVC Termination
19-87
Workflow for Bridge Management
19-88
Overview about Workflow
19-88
Create a Domain
19-90
Add NE to a Domain
19-91
.................................................................................................................................................................................................................................... 1350 OMS 19-2 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management
Overview
....................................................................................................................................................................................................................................
Domain Configuration
19-94
Domain Modification
19-96
Configure a Network Element
19-98
Link Over TDM configuration
19-100
NE Ethernet Physical Port Configuration
19-102
Create a Customer
19-104
Create an Ethernet Service
19-107
Traffic Descriptor Definition
19-109
EVC Allocation and Implementation
19-111
EVC Bandwidth Management
19-112
Dynamic change capability
19-112
Function Description
19-113
Service Delimiting
19-117
Vlan Push/Pop On Provider Bridge UNI/IWI Management Spanning Tree
19-117 19-119
Show the Spanning Tree Instance of EVC
19-119
Show the Spanning Tree Instance
19-120
Spanning Tree Instance configuration
19-121
Spanning Tree Instance Implementation
19-123
Spanning Tree Instance Deimplementation
19-124
.................................................................................................................................................................................................................................... 1350 OMS 19-3 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
Bridge Network Management
....................................................................................................................................................................................................................................
Connection Less Networks Bridge Network Management Bridge network description
The aim of bridge network management is to provide support for emerging Ethernet-based Connection Less services like the virtual private LAN service (EVPLAN) connecting in a transparent way various customer sites across a metropolitan network (Metro-Ethernet). An Ethernet switch learns the MAC addresses of end-hosts and associates them with appropriate ports on which the end-host frames arrive. In case of mesh networks, loop-free connectivity is assured by a distributed computation carried through control frames and resulting in a spanning tree. In the context of Metro-Ethernet, a customer network is a collection of multiple networks (LANs) that are physically connected by means of a service provider network and operate as if all those multiple networks are connected (virtually) as a single LAN. Ethernet infrastructure participating to switching can be partitioned into virtual LANs possibly overlapping and each one identified by a VLAN-Id. The Q-tag inserted in the Ethernet frames can be used to limit packet broadcasting to the switches participating to the VLAN. Packets tagged with a VLAN are never sent to interfaces that are not part in the VLAN and therefore traffic segregation is achieved. This way, VLAN-Ids allow additional pruning of the loop-free logical connectivity provided by the spanning tree. Provider bridge added value
A provider bridge network brings the following main added values with respect to a virtual bridge one: •
If different customers use the same C-VLAN, for each customer a different P-VLAN is stacked over that C-VLAN. Stacking segregates the traffic sourced by one customer from the one sourced by the other, inside the provider network.
•
It is possible to perform in the NE traffic classification and traffic description of the ingress frames at the edge of the provider domain: – –
Traffic classification allows sharing an IWI interface among different customers. Traffic description allows enhanced quality of service management.
The introduction of the ISA ES family allows offering Ethernet bridging functionality over SDH network and cables. Bridge network functional areas
Bridge network management is based on the following functional areas: • •
Network construction. Bridge infrastructure management including: Transport link activation/deactivation.
.................................................................................................................................................................................................................................... 1350 OMS 19-4 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
Bridge Network Management
....................................................................................................................................................................................................................................
•
Bridge traffic management including: – EVC association to bridge infrastructure.
•
– Manual or automatic VLAN distribution inside 1350 OMS PKT resources. – STP parameters set-up inside 1350 OMS PKT resources. – VLAN and STP provisioning to the NE. – QoS management. Maintenance management.
•
Utilities.
.................................................................................................................................................................................................................................... 1350 OMS 19-5 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
Bridge Traffic Management
....................................................................................................................................................................................................................................
Bridge Traffic Management Overview
The traffic management is related to the elementary EVC management based on Connection Less networks (MAC Bridge, Virtual Bridge, or Provider Bridge). Bridge Traffic management handles the set-up of data traffic toward the customer edge, STP tuning and VLAN distribution inside and at the edge of the domain. Following main functions are in the scope of the bridge traffic management. • • • •
EVC association to bridge infrastructure. Manual or automatic VLAN distribution inside 1350 OMS PKT resources. STP parameters set-up inside 1350 OMS PKT resources. VLAN and STP provisioning to the NE.
Bridge EVC
One EVC is an elementary EVC that spans the scope of a single bridge domain. In case of MAC domain, no VLAN are managed and there exists at most only one EVC for the domain. In case of Virtual or Provider domain, more EVC can insist on the same domain. The EVC is associated to a set of edge ports of a bridge domain. EVC association to domain is automatic for MAC or when the edge ports are specified at EVC creation-time: the terminations of one EVC must correspond to edge ports belonging to the same bridge domain. All or a subset of the domain edge ports can be selected as EVC terminations (all by default in a MAC domain). In case of Virtual or Provider domain, one EVC is optionally characterized by one VLAN bundle, that is, a group of VLAN. Moreover, in case of Provider domain, we have to distinguish the outer VLAN, that is, the C-VLAN, from the inner VLAN carried inside the domain, namely the P-VLAN. This distinction is expressed by means of a C-VLAN/P-VLAN mapping. The C-VLAN/P-VLAN mapping is defined at EVC level since it must be uniform for all EVC terminations. Any given inner VLAN can be associated to only one EVC supported by the same domain. EVC Terminations
The EVC Termination is a: • • •
MAC Bridge Termination if it uses a MAC Bridge Port. Virtual Bridge Termination if it uses a Virtual Bridge Port. Provider Bridge Termination if it uses a Provider Bridge Customer Port.
.................................................................................................................................................................................................................................... 1350 OMS 19-6 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
Bridge Traffic Management
....................................................................................................................................................................................................................................
The EVC Termination is conceptually associated to: • •
•
One Ethernet interface (either local or remote) in case of MAC Bridge Termination. One set of ETB virtual ports insisting on the same Ethernet interface in case of Virtual Bridge Termination. This set the set of ETB virtual ports corresponding to the C-VLAN of the EVC ( One ETB virtual port correspond to one C-VLAN). One ETS flow or set of ETS flows in case of Provider Bridge Termination. The flow or set of flows referenced by the Traffic Classifiers is associated with the C-VLAN of the EVC.
.................................................................................................................................................................................................................................... 1350 OMS 19-7 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
Spanning Tree Instance Management
....................................................................................................................................................................................................................................
Spanning Tree Instance Management Network robustness
In Connection Less networks based on Bridge solution, the risk of network loop and packet flooding can lead to network congestion. The usage of Spanning Tree Protocols adds robustness to the network, as the active topology is automatically recalculated by the ISA boards after the detection of one of the following conditions: • • •
Alarms on Transport Links or edge ports. Add/remove of NE or Transport Links in the Domain. Tuning of STP parameters (for example: bridge priority) by management system.
STI tree topology
Network congestion can be avoided supplying a tree topology to the internal used resources. The tree topology can be obtained in two different ways: • •
Manually by the user: the user statically shapes a tree in the network manually configuring Transport Links to be used. Automatically by ISA Boards: the user configures and enables the usage of Spanning Tree Protocols inside a given Domain (STP/RSTP/PVSTP/MSTP) to let ISA Boards to autonomously determine an active tree shape (also called active topology) inside the network.
STI resources
The spanning tree instance (STI) is the set of NE, ENE and Ports carrying control frames (BPDU) that participate to the same distributed computation. The spanning tree NE (ST-NE) represents the image of one NE or ENE in the scope of the STI. Each ST-Termination is characterized by a port state and a port forced state. The port state tells whether the port is forwarding or discarding data frames in the scope of the STI. The port forced state tells whether the control on the port state is delegated to the network (dynamic forced state) or manually constrained by user (blocked or forwarding forced state). The ST-termination port forced state can be configured acting on the ST-link, that means, configuring both end-points with one single operation. Port configuration
On a per-STI basis, configuring the port forced state to forced blocking. One or more ST-links can be manually excluded from the data forwarding process. On the other hand, configuring the port forced state to forced forwarding implies that the ST-link is constrained to participate to packet forwarding. In both cases, either configuring the port forced state to forced blocking or forwarding, the ST-links are manually excluded from the network computation: these links belong or not to a static tree topology due to the constraints of the user. A failure on forced forwarding links is not recovered by the spanning tree protocol.
.................................................................................................................................................................................................................................... 1350 OMS 19-8 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
Spanning Tree Instance Management
....................................................................................................................................................................................................................................
The active STI is constituted by NE, ENE and Ports carrying both BPDU and customer data frames. The Ports belonging to the spanning tree instance (STI) are NNI interfaces carrying control frames (BPDU): the active NNI interfaces carry both customer data frames and control frames. A distributed computation (control frame forwarding) determines dynamically which interfaces must actually forward data frames. The active spanning tree is a dynamic snapshot of the network status. Static tree topology
A static tree topology is a subset of the active STI, built by user forcing manually the control plane port forced state to forwarding for all ST-Terminations in the tree. The user can statically determine part or all of the STI active topology. A static tree topology can introduce loops in the network. The number of spanning tree instances for a domain depends on the associated STP type: • • •
None - no spanning tree instance. STP/RSTP - only one spanning tree instance for all VLAN. PVSTP - one spanning tree instance per-VLAN.
•
MSTP - one spanning tree instance per set of VLAN.
Each STI represents a control plane, namely a virtual infrastructure dedicated to the transport of control frames (that is, the BPDU carrying the spanning tree computation). A dedicated set of BPDU is exchanged for each STI. By design choice, the EVC is always associated to a single spanning tree instance (STI), whatever STP type is running. to have a service exploiting different spanning tree instances, we must define different EVC for that service. The associated STI can be shared with other EVC. As a consequence, in case of PVSTP, the EVC must be characterized by a single VLAN.
.................................................................................................................................................................................................................................... 1350 OMS 19-9 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
VLAN management
....................................................................................................................................................................................................................................
VLAN management Overview
Virtual LANs are introduced for segmenting the network into different broadcast (or multicast) domains. The VLAN-Id is used to forward Ethernet traffic only toward those Ethernet ports (UNI) that are members of a given VLAN, ensuring that the tagged frames are only accessible by the proper end-user and therefore realizing traffic segregation. 4096 different VLAN can be used in one Ethernet network. VLAN management helps solving security and privacy, bandwidth management, and increasing the performance. The use of VLAN
VLAN can be used anyway to switch traffic in different contexts: • •
•
• •
•
Defining Ethernet VPNs (EVPLAN service in Connection Less networks). Switching broadband access traffic to the selected ISP. For instance, the use of customer-based VLAN for routing purposes in the network couples the operational aspects of the customer and network user domain. Allowing inter-working the provider network characterized by its own VLAN tag with the network of another provider using not standard VLAN tag. This inter-working is achieved by means of VLAN push and pop operations. Provider network inter-working at the Layer-2 control protocol level can follow a transit model (tunneling) or a peer-to-peer model (mapping mode). In the scope of Virtual Bridge management, the VLAN assume the meaning of Customer VLAN (C-VLAN). In the scope of Provider Bridge management, the VLAN assume the meaning of Provider VLAN (P-VLAN). A scalable solution design can be designed mapping the received Customer VLAN on one internally defined P-VLAN. Both in case of Virtual and Provider Bridge management, Ethernet frames can flow in the network only after having properly provisioned the required VLAN inside the network (C-VLAN for Virtual and P-VLAN for Provider).
.................................................................................................................................................................................................................................... 1350 OMS 19-10 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
EVC Data Plane
....................................................................................................................................................................................................................................
EVC Data Plane Overview
Each EVC spanning the scope of a bridge domain has an associated data plane and active topology. The EVC data plane is the set of NE, ENE and Ports enabled to carry user data frames belonging to that EVC. It contains the set of NE and Ports where the set of VLAN characterizing the EVC has to be distributed. The EVC active topology is the set of NE, ENE and Ports belonging to the same Domain and actually carrying user data frames. For example, the active topology differs from the data plane when a link is blocked by the spanning tree computation to avoid loops. In fact, the EVC active topology is actually the projection of the EVC data plane onto the active topology of the STI supporting the EVC: the data path for the EVC is therefore obtained keeping into account both the VLAN distribution and the dynamic computation of the associated STI. The EVC data plane and active topology are also virtual entities since they are specific for the VLAN bundle characterizing the EVC and, therefore, are specific for that EVC. Data frames characterized by different VLAN Id can generally follow different data paths across the bridge network, but data frames belonging to same EVC are constrained, by design choice, to follow the same data path to allow QoS management on a per-EVC basis. When edge ports (that is, UNI or IWI interfaces) are associated to the EVC, they belong to the EVC data plane but not to the active STI topology, since control frames coming from CE or from another domain must be filtered or tunneled. UNI and IWI interfaces are not allowed to enter the active STI topology. On the other hand, NNI Transport Links can belong to both EVC data plane and active STI topology: they can carry both data frames and control frames. Active topology
The Ports belonging to the EVC active topology are therefore characterized by: • •
The VLAN characterizing the EVC are in the Port member set. Forced port state equal to forced forwarding (namely they are part of the STI static active Topology) or.
•
Forced port state equal to dynamic and port state equal to forwarding (namely, they are part of the STI dynamic active topology).
Following table summarizes the port forced-state relation with EVC active topology. Forced-state/ Plane.
Control frame forwarding.
Data frame forwarding.
EVC Active Topology.
Forced-blocking.
No.
No.
No.
Forced-forwarding.
No.
Yes.
Yes.
.................................................................................................................................................................................................................................... 1350 OMS 19-11 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
EVC Data Plane
....................................................................................................................................................................................................................................
Forced-state/ Plane.
Control frame forwarding.
Dynamic.
Yes.
Data frame forwarding. Decided by network computation.
EVC Active Topology. Decided by network computation.
.................................................................................................................................................................................................................................... 1350 OMS 19-12 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
The EVC life cycle
....................................................................................................................................................................................................................................
The EVC life cycle Overview
The EVC life cycle is tightly related to the life cycle of the associated EVC data plane and that of the supporting STI. At Domain activation time, the default STP protocol type is enabled on all NE and also the NNI Ports are activated. This activations implies that control frames are allowed to flow in the network. In case of STP/RSTP/MSTP, the default STI is therefore implemented in the network. The default STI is referred as the CIST (Common Instance Spanning Tree) in case of MSTP. We extend this terminology also to the case of STP/RSTP, where it represents the only instance available. In case of MAC Domain, only one EVC is created automatically by the system at Domain activation time. In case of Virtual or Provider Domain, the EVC must be explicitly created by user and more than one EVC can insist on the same Domain. EVC creation or modification
At creation/modification time, the EVC is associated to a set of edge ports and, in case of Virtual or Provider Domain, to a set of VLAN. Association to edge ports implies the automatic association with the underlying Domain. The EVC is characterized by a full-mesh/ not full-mesh attribute used to drive the VLAN distribution inside 1350 OMS PKT resources (at EVC data plane allocation time). In case of Provider Bridge, user must specify a C-VLAN/P-VLAN mapping. At EVC Termination creation/modification time, user can optionally specify a default user priority on a per-Port basis (in case of MAC Bridge or Virtual Bridge edge port). In case of Virtual Bridge only, the user can also specify an 801.2p priority bit regeneration table. The EVC data plane is one-to-one with the EVC and is automatically defined at EVC creation time. Similarly, the EVC data plane is automatically deleted at EVC deletion time. to allow EVC allocation, the EVC data plane must be allocated first. EVC data plane allocation means defining the physical infrastructure for the data plane. The system must include the VLAN in the EVC bundle in the VLAN member set of the ports that are part of the virtual data plane specific for that EVC. All VLANs in the EVC share the same virtual data plane. EVC data plane allocation implies VLAN distribution to Edge Ports, corresponding to the VLAN distributed on EVC Terminations. The UNI/IWI association to EVC data plane is therefore automatically established by the system. The VLAN of each EVC Termination is allocated on the respective UNI/IWI. The VLAN in the EVC bundle have to be uniformly allocated to the NNI. The NNI association is performed either manually (not full-mesh case) or automatically (full-mesh case).
.................................................................................................................................................................................................................................... 1350 OMS 19-13 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
The EVC life cycle
....................................................................................................................................................................................................................................
In case of full-mesh, the association is performed at EVC data plane allocation-time: the system automatically distributes the VLAN in 1350 OMS PKT MIB to all Transport Links (that is, NNI Ports) in the Domain. In case of not full-mesh, the user must use a specific function to add/remove a set of Transport Links to the allocated EVC data plane. EVC allocation
To summarize, when a full-mesh EVC Data Plane is allocated, all VLAN in the bundle are distributed to all edge ports and Transport Links in the domain. In case of not full-mesh, the allocation operates only on edge ports, while the user has to add the selected set of Transport Links; then the system automatically and uniformly distributes all VLAN in the bundle to the selected Transport Links. to perform a non-uniform VLAN allocation over the Transport Links used by a service, the user is therefore required to use different EVC. EVC allocation means to select a supporting STI and to associate the selected STI to the set of VLAN characterizing the EVC. The way to select a STI for the EVC depends on the domain STP type: • • • •
None: spanning tree instance is not supported and the infrastructure must be a tree topology. The user must ensure that the topology is loop-free. STP/RSTP: the default spanning tree instance (the CIST) is implicitly selected by the system. The CIST is automatically implemented at domain activation time. PVSTP: for the single VLAN characterizing the EVC, a new STI is automatically allocated by the system at EVC allocation time. MSTP. In this case, the user has two possibilities: – –
Allocate the EVC over an existing STI (the CIST by default). Require to allocate the EVC over a new STI to be automatically created and allocated by the system.
Provisioning details
EVC de-allocation implies losing the relation with the supporting STI. If the STI is not the CIST, at de-allocation time of the last EVC, the supporting STI is automatically deleted. The CIST is automatically de-implemented at bridge domain deactivation time. The EVC Data Plane de-allocation can be performed individually or cascaded automatically after EVC de-allocation. The EVC Data Plane de-allocation is a pre-condition for EVC deletion. The EVC Data Plane de-allocation consists in removing of the VLAN characterizing the EVC from the Edge Ports (that is, UNI/IWI Ports) and from all associated Transport Links (that is, NNI Ports). Therefore, the EVC data plane de-allocation behaves in the same way both in case of full-mesh and not full-mesh EVC. In case of not full-mesh EVC, the user can remove one or more Transport Links from the allocated EVC data plane, before implementing it. To allow EVC implementation, the supporting STI and the EVC data plane must be implemented first. .................................................................................................................................................................................................................................... 1350 OMS 19-14 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
The EVC life cycle
....................................................................................................................................................................................................................................
STI implementation means that any new STI is instantiated on the ISA NE (only in case of MSTI) and that the STP parameters are provisioned on the ISA NE (only NNI Ports). The CIST is automatically implemented at bridge domain activation time.
.................................................................................................................................................................................................................................... 1350 OMS 19-15 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
Layer-2 Control Protocol Processing
....................................................................................................................................................................................................................................
Layer-2 Control Protocol Processing Overview
The user optionally defines, on EVC basis, which control Protocol must be tunneled or discarded. Such configuration must be propagated to all EVC terminations to ensure that all EVC terminations use the same Tunneling criteria. A check is needed also toward Layer-2 Control Protocol Processing defined at UNI level. This check allows a congruent management of Control protocols crossing the EVC. In case of Connection Oriented EVC, the value defined for the EVC is predefined to Tunnel for all L2 Control Protocols and this value is propagated to contained Ethernet Segments. In case of Provider Bridge based EVC, the value can be freely defined by the user for the EVC. The value is propagated to all EVC Terminations. In case of MAC Bridge or Virtual Bridge based EVC, the EVC is always tunneling (the UNI setting is fully operative). If the Layer-2 Protocol Processing is not defined at EVC level, then this definition is delegated to each single EVC Termination (for Provider Bridge Based EVCs) while for Ethernet Segment (Connection Oriented EVCs) is fixed to Tunnel for all L2 Protocols. This way to operate is maintained as backward compatible with previous 1350 OMS PKT releases but is not considered as MEF compliant because do not ensure that at EVC level a common policy on Control Protocols is applied. During EVC Definition, for each used UNI, a check is performed respect to the Max Number of EVC defined on each UNI. L2 Control Protocols
For the List of L2 Control Protocols, refer to the following table: Table 19-1
L2 Control Protocols
Control Protocol.
Discard.
Tunnel (default for all protocols).
Data Frames.
Yes.
Yes.
Customer BPDU (STP, RSTP, MSTP).
Yes.
Yes.
Provider BPDU (STP, RSTP, MSTP).
Yes.
Yes.
Slow Protocols.
Yes.
Yes.
802.1X PAE.
Yes.
Yes.
Notes.
At EVC level, it is allowed to Tunnel or Discard also Data Frames.
.................................................................................................................................................................................................................................... 1350 OMS 19-16 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
Layer-2 Control Protocol Processing
....................................................................................................................................................................................................................................
Table 19-1
L2 Control Protocols
Control Protocol.
(continued)
Discard.
Tunnel (default for all protocols).
Provider GVRP.
Yes.
Yes.
Bridge Management.
Yes.
Yes.
Customer GMRP.
Yes.
Yes.
Customer GVRP.
Yes.
Yes.
Notes.
Bandwidth profiles
The bandwidth profiles defined for each EVC termination have to be intended in the following way: •
In case of Connection Less EVCs based on Provider Bridge, the bandwidth profiles defined for each EVC termination represents the bandwidth profile for the traffic at the ingress of that UNI (and it is immediately checked).
•
In case of Connection Less EVCs based on Virtual Bridge, the bandwidth profiles defined for each EVC are automatically defined as Best Effort Class Of Service having the PIR fully equal to the UNI rate. In case of Connection Less EVCs based on MAC Bridge, the bandwidth profiles defined for each EVC are automatically inherited from UNI characteristics (in fact all UNI of a MAC Bridge supports only the Bandwidth Profile per UNI) and the traffic parameters.
•
.................................................................................................................................................................................................................................... 1350 OMS 19-17 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
Bandwidth Profile per UNI
....................................................................................................................................................................................................................................
Bandwidth Profile per UNI Overview
Each Bandwidth Profile configured on a given UNI represent the way the traffic entering in ingress to that UNI is shaped and managed in term of Bandwidth. The following possible values for Bandwidth Profile are manageable at UNI level: • •
•
“Bandwidth Profile per UNI” (p. 19-18). Bandwidth description is shared for all connection starting from this ingress UNI. “Bandwidth Profile per EVC” (p. 19-18). Bandwidth description is shared for all connection starting from this UNI in the scope of this EVC. Each EVC has one or a group of VLAN. “Bandwidth Profile per CoS” (p. 19-18). The bandwidth applies to traffic defined by one or a group of VLAN and one Priority bit.
Bandwidth Profile per UNI
The Bandwidth Profile is configured with a bandwidth description on the edge port before having created any service on this port. In this case, all the services that start on this UNI share this bandwidth (in the limits described in the profile). The provisioning is accomplished by means of the management of the FlowGroup concept. For each EVC Connection Oriented based starting from this UNI, the UNI Bandwidth profile is propagated along the used route (the pseudo CAC implemented at 1350 OMS PKT level takes into account either current per flow Traffic Descriptors and FlowGroup Traffic Descriptor). In case of UNI belonging to MAC bridges, traffic parameters are automatically defined as Best Effort CoS with the PIR value equal to the UNI rate. Bandwidth Profile per EVC
The bandwidth profile is supplied during each termination addition describing the bandwidth usable and shared for all the connection of the considered EVC. This setting applies on the added termination only; that is, one port used by the EVC can work in per EVC mode and another port used by the same EVC can work in per Cos mode. The provisioning is accomplished by means of the management of the FlowGroup concept. For each EVC Connection Oriented based starting from this UNI, the UNI Bandwidth profile is propagated along the used route (the pseudo CAC implemented at 1350 OMS PKT level takes into account either current per flow Traffic Descriptors and FlowGroup Traffic Descriptor). Bandwidth Profile per CoS
The bandwidth profile is described by one VLAN or group and one Priority bit or set of bits. This profile is applicable for one EVC termination: so the EVC termination is used per Cos or is used per EVC. The description of the bandwidth profile is done by the way of one Traffic Descriptor composed of Bandwidth profile attributes (CIR, PIR, CBS, PBS) and also one QoS attribute, standing for the description of the PHB (Per Hop
.................................................................................................................................................................................................................................... 1350 OMS 19-18 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
Bandwidth Profile per UNI
....................................................................................................................................................................................................................................
Behavior), that is, the internal NE mode for managing the traffic. The PHB (Per Hop Behavior), represents, on equipment base, the QoS expected by a Customer at EVC level (that is, on Per Network Behavior). The QoS definition
The QoS attribute can be automatically determined by the 1350 OMS PKT from the bandwidth parameter values supplied in the profile. This behavior is the default behavior but, to remain as flexible as the equipment (introducing 8 QoS following the same formula for the profile values), the user can force this value to a specific one according to the equipment formula. In addition to the Traffic Descriptor, two other concepts complete the QoS definition: • •
the Policy mode: such management is today aligned with IETF and whose extension in the scope of MEF compliancy is in the scope of 1350 OMS PKT. The Color Profile: such management is aligned with IETF concepts for Color Aware traffic management. This management is not considered MEF. The Color Profile management, is maintained unchanged in respect to previous 1350 OMS PKT releases. The user must plan the usage or not.
Bandwidth Profile Per UNI attributes
The Bandwidth Profile per UNI is one of the possible management definable on UNI basis relatively to MEF compliancy. The Bandwidth Profile Per UNI is described by the following attributes: • • • •
Committed Information Rate (CIR). Excess Information Rate (EIR). Committed Burst Size (CBS). Excess Burst Size (EBS).
• •
Color Mode (CM). Coupling Flag (CF).
Manual and default operations
This management is mutually exclusive with the two other possible management (Bandwidth Profile per EVC and Bandwidth Profile per EVC per Cos). The Bandwidth Profile per UNI must be defined on a given UNI in two ways: • •
By the user through a manual operation before the port is used. Automatically as the default value for a given UNI depending on restrictions existing on specific NE configurations.
.................................................................................................................................................................................................................................... 1350 OMS 19-19 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
Bandwidth Profile per UNI
....................................................................................................................................................................................................................................
The following table reports the known operations at NE configuration or at Port upload. Table specify the manual operation needed or the predefined default operation. UNI Configuration.
Bandwidth (BWD) Profile allowed.
Default Value.
Modification Allowed.
ETS.
Per UNI, Per EVC, Per CoS.
/.
Yes, Bwd Per UNI only before UNI usage.
ETS (Provider Bridge).
Per UNI, Per EVC, Per CoS.
/.
Yes, Bwd Per UNI only before UNI usage.
ETB (MAC Bridge).
Per UNI.
CIR=PIR=Port Rate.
NO.
ETB (Virtual Bridge).
Per UNI.
CIR=PIR=Port Rate.
NO.
After having configured a UNI supporting a Bandwidth Profile per UNI, each EVC using that port inherits, from that UNI the same Bandwidth profile for traffic entering from that UNI. All the EVCs instantiated as entering from that UNI use the same Bandwidth profile). From the traffic point of view, all traffic entering in a UNI (from a CE) is in competition with other traffics for the probability to be transmitted in the transport network. An EVC using a UNI being configured with a Bandwidth Profile per UNI can use other UNIs having different Bandwidth Profiles configured (either per UNI, Per EVC, Per CoS). EVC provisioning
It is important to differentiate the expected management behavior (particularly for allocation and provisioning steps) in the various cases of Connection Oriented (ETS) or Connection Less (ETB) management. ETS Case:
When an EVC lying on an ETS domain uses a UNI defined to support a Bandwidth Profile per UNI, the Ethernet Segment starting from that UNI inherits (as Traffic Descriptor Definition) the information defined in that Bandwidth profile. When the EVC is allocated, this implying the allocation of contained Ethernet Segments, that TD (reflecting the BwdProfilePerUNI) is propagated along the route of the Ethernet Segment. When the EVC is Implemented, this implying the implementation of contained Ethernet Segments, that TD (reflecting the BwdProfilePerUNI) is provisioned on all affected NEs along the route of the Ethernet Segment. In terms of Provisioning, the SNMP objects to be provisioned is a FlowGroup (reflecting that EVC on the UNI) with associated a Traffic Descriptor.
.................................................................................................................................................................................................................................... 1350 OMS 19-20 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
Bandwidth Profile per UNI
....................................................................................................................................................................................................................................
ETB Provider Bridge Case:
When an EVC lying on an ETB Provider Bridge domain uses a UNI defined to support a Bandwidth Profile per UNI, the EVC Termination (reflecting the traffic entering from that UNI) inherits (as Traffic Descriptor Definition) the information defined in that Bandwidth profile. This “inheritance” can happen both at EVC Definition and during EVC Termination Adding. The Traffic Descriptor reflecting the BwdProfilePerUNI is defined and associated to the EVC Termination. When the EVC is Implemented, this implying the implementation of EVC Termination, the TD that reflects the BwdProfilePerUNI, is provisioned on the affected NEs. ETB Virtual and MAC Bridge Case:
When an EVC lying on an ETB Virtual or MAC Bridge domain uses a UNI defined to support a Bandwidth Profile per UNI, the EVC Termination (reflecting the traffic entering from that UNI) inherits (as Traffic Descriptor Definition) the information defined in that Bandwidth profile. This “inheritance” can happen both at EVC Definition and during EVC Termination Adding. The TD reflecting the BwdProfilePerUNI is defined and associated to that EVC Termination. When the EVC is Implemented, nothing happens on NEs, because in the scope of Virtual and MAC bridge no provisioning is possible in terms of Traffic Descriptors.
.................................................................................................................................................................................................................................... 1350 OMS 19-21 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
View the list of bridge NEs
....................................................................................................................................................................................................................................
View the list of bridge NEs When to use
This function lists the Network Elements of connection less type. Related Information
For information, see: “Overview about Workflow ” (p. 19-88). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Less (Bridge). Result: The Connection Less menu is shown. ...................................................................................................................................................................................................
2
Bridge NEs Result: The list window is displayed.
See the following topic in this document: “Description of the list of Bridge NEs” (p. 19-23) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-22 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
Description of the list of Bridge NEs
....................................................................................................................................................................................................................................
Description of the list of Bridge NEs Attributes of a Bridge NE
The attributes displayed for each Bridge (Connection less) NE are: •
User Label.
•
Working State (Normal, Configuring, Removing).
•
STP Type(MSTP, RSTP).
•
Domain.
•
MAC Address.
•
Network Element.
•
Spanning Tree Instance.
•
Provider Bridge Operation Mode(Not Meaningful, 5P3D).
•
PTM Name.
.................................................................................................................................................................................................................................... 1350 OMS 19-23 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
View the list of bridge ENEs
....................................................................................................................................................................................................................................
View the list of bridge ENEs When to use
This function lists the External Network Elements of connection less type. Related Information
For information, see: “Overview about Workflow ” (p. 19-88). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Less (Bridge). Result: The Connection Less menu is shown. ...................................................................................................................................................................................................
2
Bridge External NEs Result: The list window is displayed.
See the following topic in this document: “Description of the list of Bridge ENEs” (p. 19-25) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-24 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
Description of the list of Bridge ENEs
....................................................................................................................................................................................................................................
Description of the list of Bridge ENEs Attributes of an ENE
The attributes displayed for each Bridge (Connection less) ENE are: •
User Label.
•
Working State (Normal, Configuring, Removing).
•
STP Type(MSTP, RSTP).
•
Domain.
•
MAC Address.
•
Network Element.
•
Spanning Tree Instance.
•
Provider Bridge Operation Mode(Not Meaningful, 5P3D).
•
PTM Name.
.................................................................................................................................................................................................................................... 1350 OMS 19-25 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Networks
View the Provider Bridge Flows of an EVC
....................................................................................................................................................................................................................................
View the Provider Bridge Flows of an EVC When to use
This function shows the provider bridge Flows of an EVC. Related Information
For information about Connection Less EVC, see: “Bridge Traffic Management” (p. 19-6). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. Result: The EVC list is shown. ...................................................................................................................................................................................................
2
Select the Bridge EVC and select the path Search > Bridge EVC > Provider bridge Flows. Result: The list shows the flows belonging to the selected EVC. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-26 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Transport Link Management
Display the Ethernet Bridge Transport Link list
....................................................................................................................................................................................................................................
Connection Less Transport Link Management Display the Ethernet Bridge Transport Link list When to use
The Ethernet Transport Link List window presents all the Ethernet Transport Links and their attributes. Related Information
If this list is required from the VLAN type list, only Transport Links whose edge ports are associated to the selected VLAN type, are displayed. For general information about Transport Links, see: “Transport link management” (p. 11-50). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The Transport Link must not be in use by an Ethernet Segment (Its usage state must be Idle).
•
The Transport Link must have an SDH or Cable technology.
Task
From the Multi Service GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The menu of the Services is shown. ...................................................................................................................................................................................................
2
Select Connection Less > Transport Link.
.................................................................................................................................................................................................................................... 1350 OMS 19-27 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Transport Link Management
Display the Ethernet Bridge Transport Link list
....................................................................................................................................................................................................................................
Result: The list window is displayed.
See the following topic in this document: “Description of the list of Bridge Transport Links” (p. 19-29) Figure 19-1 Connection Less Transport Link List
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-28 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Transport Link Management
Description of the list of Bridge Transport Links
....................................................................................................................................................................................................................................
Description of the list of Bridge Transport Links Attributes of a Bridge Transport Link
The attributes displayed for each Bridge (Connection less) Transport Link are: •
User Label.
•
Subnetwork.
•
Technology (MPLS, SDH, Cable).
•
Total Bandwidth.
•
Usage State (Idle, Busy, Reserved, Not Meaningful).
•
Working State (Normal, Configuring, Removing).
•
Configuration State (Configured, Partially Configured, Not Configured).
•
Domain.
•
Domain Type.
.................................................................................................................................................................................................................................... 1350 OMS 19-29 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Transport Link Management
Configure a transport Link
....................................................................................................................................................................................................................................
Configure a transport Link When to use
This function permits to change the VLAN Protocol Type of Transport Link extremities. Related Information
For information about Transport Link management, see: “Overview about Transport links ” (p. 14-4). The VLAN Type is not an attribute of the Transport Link. The VLAN Type is an attribute of its extremities (that is, Transport Link terminations). So, VLAN Type is displayed in the extremity window of the Transport Link. For these reasons, while the Edge port modification command acts on one Edge port (and its attributes), the Transport Link configuration command acts only on the Transport Link terminations. The command is a shortcut for the user, not to configure separately the two terminations. The ports at the extremities of the Transport Link are active and configured with the VLAN Type and, hence: •
They recognize as tagged only the Ethernet frames that are tagged with this VLAN type.
•
Any push operation (that is, VLAN constraint of type "Push") defined on them uses the specified VLAN type to create (and push) new VLAN tags.
PCP Table Profile compliant with NE
PCP Table Profile possible values are As Container, 5P3D, 6P2D, 7P1D, 8P0D; to be assigned in compliance with the NE, as listed: • • • •
On node basis, ES1/4 admits the values: 5P3D (default on node basis), 8P0D. On node basis, ES16 admits the values: 5P3D (default on node basis), 8P0D. On port basis, ES1/4 does not admit any PCP Port table profile. On port basis, ES16 admits the values: as Container (This value is the default on Port Basis [default=0] mirroring the value defined on Node basis), 5P3D, 6P2D, 7P1D, 8P0D.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode.
.................................................................................................................................................................................................................................... 1350 OMS 19-30 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Transport Link Management
Configure a transport Link
....................................................................................................................................................................................................................................
Conditions
To get a positive result: • •
The Transport Link must not be in use by an Ethernet Segment (Its usage state must be Idle). The Transport Link must have an SDH or Cable technology.
Task
From the Multi Service GUI Main view: ...................................................................................................................................................................................................
1
follow the path Search > Packet > Services > Connection Less > Transport Link. ...................................................................................................................................................................................................
2
Select the Transport Link in the list. ...................................................................................................................................................................................................
3
Follow the path Action > Configure..
.................................................................................................................................................................................................................................... 1350 OMS 19-31 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Transport Link Management
Configure a transport Link
....................................................................................................................................................................................................................................
Result: The configuration window is displayed. Figure 19-2 Transport Link Configuration window
...................................................................................................................................................................................................
4
To configure a Transport Link: •
Acceptable Frame Type (All, ONLY VLAN tagged):
•
PVID.
•
Enable Ingress Filtering.
•
Priority bit mapping.
•
Default User Priority.
.................................................................................................................................................................................................................................... 1350 OMS 19-32 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Transport Link Management
Configure a transport Link
....................................................................................................................................................................................................................................
• •
PCP Table Profile. See “PCP Table Profile compliant with NE” (p. 19-30).
Select a VLAN Type (by using the sensitive help) or set the Set standard VLAN Type (8100) value to true.
...................................................................................................................................................................................................
5
Click Ok button. Result: After confirmation, the Configuration state of the Transport Link is
recalculated and set to: • •
•
Configured: if both extremities are active and are configured with the same
VLAN Tag Protocol Type. Partially Configured: if only one extremity is active (while the other is not active) or when both extremities are active but are configured with two different VLAN Tag Protocol Types. Not Configured: if both extremities are not active.
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-33 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Transport Link Management
Get the Transport Link extremities
....................................................................................................................................................................................................................................
Get the Transport Link extremities When to use
This function gets information about the extremities of a Transport Link. This function permits optionally to modify extremity characteristics. Related Information
For information about Transport Link management, see: “Overview about Transport links ” (p. 14-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the Multi Service GUI Main view: ...................................................................................................................................................................................................
1
Follow the path: Search > Packet > Services > Connection Less > Transport Link. ...................................................................................................................................................................................................
2
Select the Transport Link in the list. ...................................................................................................................................................................................................
3
Follow the path Search > Inventory from Transport Link > Extremities.
.................................................................................................................................................................................................................................... 1350 OMS 19-34 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Transport Link Management
Get the Transport Link extremities
....................................................................................................................................................................................................................................
Result: The extremities window is displayed.
See the following topic in this document: “Description of the list of Transport Link extremities” (p. 19-37) Figure 19-3 Transport Link Extremities window
...................................................................................................................................................................................................
4
Change parameters.
.................................................................................................................................................................................................................................... 1350 OMS 19-35 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Transport Link Management
Get the Transport Link extremities
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
5
Click Ok button. Result: The Transport Link extremities attributes are changed consequently. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-36 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Transport Link Management
Description of the list of Transport Link extremities
....................................................................................................................................................................................................................................
Description of the list of Transport Link extremities Attributes of a Transport Link extremity
The attributes shown are: •
Network Element.
•
Network Element type.
•
Termination user label.
•
Activation State.
•
VLAN Type.
•
Acceptable Frame Type.
•
PVID.
•
Enable Ingress Filtering.
• •
Default User Priority.
•
PCP Table Profile.
Priority bit mapping.
.................................................................................................................................................................................................................................... 1350 OMS 19-37 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Transport Link Management
Get the Transport Link properties
....................................................................................................................................................................................................................................
Get the Transport Link properties When to use
This function gets information about the properties of a Transport Link. Related Information
For information about Transport Link management, see: “Overview about Transport links ” (p. 14-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the Multi Service GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Less > Transport Link. ...................................................................................................................................................................................................
2
Select the Transport Link in the list. ...................................................................................................................................................................................................
3
Follow the path Action > Properties.
.................................................................................................................................................................................................................................... 1350 OMS 19-38 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Transport Link Management
Get the Transport Link properties
....................................................................................................................................................................................................................................
Result: The properties window is displayed.
See the following topic in this document: “Details of an ETB Transport Link” (p. 19-40) Figure 19-4 Transport Link Properties window
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-39 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Transport Link Management
Details of an ETB Transport Link
....................................................................................................................................................................................................................................
Details of an ETB Transport Link Attributes of an ETB Transport Link
The attributes displayed for each Transport Link are: •
Id.
•
User Label.
•
Subnetwork Id Label.
•
Subnetwork.
•
Technology (MPLS, SDH, Cable).
•
Usage State (Idle, Busy, Reserved, Not Meaningful).
•
Working State (Normal, Configuring, Removing).
•
A END Id label.
• •
Z END Id label.
•
Z END Type label.
•
Transport Link Label.
•
Configuration State (Configured, Partially Configured, Not Configured).
•
VLAN Id.
•
VLAN Type.
•
Domain Id.
•
Domain.
•
Domain Type.
•
STI Id label.
•
STI User Label.
•
EVC Id.
•
EVC User Label.
•
Total Bandwidth.
•
NAD.
A END Type label.
.................................................................................................................................................................................................................................... 1350 OMS 19-40 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Transport Link Management
Activate a Bridge Transport Link
....................................................................................................................................................................................................................................
Activate a Bridge Transport Link When to use
This function activates a Bridge Transport Link. Related Information
For information about Connection Less EVC, see: “Bridge Traffic Management” (p. 19-6). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Less (Bridge) > Bridge Transport Links. Result: The list window is displayed. ...................................................................................................................................................................................................
2
Select the Transport Links in the list. ...................................................................................................................................................................................................
3
Select Action > Bridge Transport Link > Activate. Result: The Transport Link is activated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-41 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Transport Link Management
Deactivate a Bridge Transport Link
....................................................................................................................................................................................................................................
Deactivate a Bridge Transport Link When to use
This function deactivates a Bridge Transport Link. Related Information
For information about Connection Less EVC, see: “Bridge Traffic Management” (p. 19-6). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Less (Bridge) > Bridge Transport Links. Result: The list window is displayed. ...................................................................................................................................................................................................
2
Select the Transport Links in the list. ...................................................................................................................................................................................................
3
Select Action > Bridge Transport Link > Deactivate. Result: The Transport Link is deactivated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-42 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Transport Link Management
View the list of Bridge Edge Ports
....................................................................................................................................................................................................................................
View the list of Bridge Edge Ports When to use
This function lists Bridge Edge Ports. Related Information
For information about Connection Less EVC, see: “Bridge Traffic Management” (p. 19-6). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Less (Bridge). Result: The Bridge menu is displayed. ...................................................................................................................................................................................................
2
Select Bridge Edge Port. Result: The list window is displayed.
See the following topic in this document: “Description of the list of Bridge Edge Ports” (p. 19-44) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-43 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Transport Link Management
Description of the list of Bridge Edge Ports
....................................................................................................................................................................................................................................
Description of the list of Bridge Edge Ports Attributes of a Bridge Edge Port
The attributes displayed for each Bridge Edge Port are: •
User Label.
•
Rate.
•
Network Element.
•
EVC User Label.
•
Role (Root, Leaf, Both).
•
Usage State.
•
VLAN Type.
.................................................................................................................................................................................................................................... 1350 OMS 19-44 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Transport Link Management
Activate a Bridge Edge Port
....................................................................................................................................................................................................................................
Activate a Bridge Edge Port When to use
This function activates a Bridge Edge Port. Related Information
For information about Connection Less EVC, see: “Bridge Traffic Management” (p. 19-6). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Less (Bridge) > Bridge Edge Ports. Result: The list window is displayed. ...................................................................................................................................................................................................
2
Select the Edge Port in the list. ...................................................................................................................................................................................................
3
Select Action > Bridge Edge Port > Activate. Result: The Port is activated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-45 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less Transport Link Management
Deactivate a Bridge Edge Port
....................................................................................................................................................................................................................................
Deactivate a Bridge Edge Port When to use
This function deactivates a Bridge Edge Port. Related Information
For information about Connection Less EVC, see: “Bridge Traffic Management” (p. 19-6). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Less (Bridge) > Bridge Edge Ports. Result: The list window is displayed. ...................................................................................................................................................................................................
2
Select the Edge Port in the list. ...................................................................................................................................................................................................
3
Select Action > Bridge Edge Port > Deactivate. Result: The Port is deactivated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-46 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
View the Connection Less EVC list
....................................................................................................................................................................................................................................
Connection Less EVC Management View the Connection Less EVC list When to use
The Ethernet Virtual Connection List window presents all the EVCs and their attributes. Related Information
If this list is required from the Ethernet Service List (or from the Ethernet Segment List or from the Ethernet Transport Link List), only the EVCs associated to the selected service (or Ethernet Segment or Ethernet Transport Link) are displayed. For information about Connection Less EVC, see: “Bridge Traffic Management” (p. 19-6). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The menu of the Services is shown. ...................................................................................................................................................................................................
2
Select Connection Less > Bridge EVCs. Result: The list window is displayed.
See the following topic in this document: “Description of the list of Bridge EVCs” (p. 19-48) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-47 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
Description of the list of Bridge EVCs
....................................................................................................................................................................................................................................
Description of the list of Bridge EVCs Attributes of a Bridge EVC
The attributes displayed for each EVC are: •
User Label.
•
Ethernet Service User Label.
•
Type (Point to point, Routed multi-point, Any to any).
•
Service Type.
•
Traffic Type (Unicast, Multicast).
•
Domain.
•
Bridge Type.
•
Working State (Normal, Configuring, Allocating, De-allocating, Implementing, De-implementing, Commissioning, De-commissioning, Termination adding, Termination removing, Constraint adding, Constraint removing, removing).
•
Provisioning State (Defined, Partially allocated, Allocated, Partially implemented, Implemented, Commissioned).
•
Service State.
•
Availability Status (Normal, Degraded, In Failure, Not Meaningful).
•
Domain.
For more attributes, refer to “EVC attributes to support ELP” (p. 28-36).
.................................................................................................................................................................................................................................... 1350 OMS 19-48 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
Create a Bridge EVC
....................................................................................................................................................................................................................................
Create a Bridge EVC When to use
This function consists in creating a Connection Less Ethernet Virtual Connection. Related Information
If this action is required from the Service List, the Ethernet Service field of the EVC Creation window, is filled with the service selected in the Service List. For information about Connection Less EVC, see: “Bridge Traffic Management” (p. 19-6). Service Type, Type, Resource Sharing relations Table 19-2
Service Type, Type, Resource Sharing relations
Service Type.
Type.
Traffic Type.
Resource Sharing.
EVPL.
Point-to-Point.
Unicast.
Full.
EPTL.
Point-to-Point.
Unicast.
Private UNI and Link.
EPL.
Point-to-Point.
Unicast.
Private UNI.
EVPLAN.
Any-to-Any.
Unicast.
Full. Private UNI. Private Link. Private UNI and Link. 1
Extended EVPL.
Point-to-Point.
Unicast.
.
Full. Private UNI. Private Link. Private UNI and Link. 1
Extended EVPLAN.
Any-to-Any.
Unicast.
Full.
Rooted Multipoint.
Multicast.
Private UNI.
1
Private Link.
.
Private UNI and Link. 1
HSI.
Rooted Multipoint.
Unicast.
Rooted Multipoint.
.
Full.
Multicast. 1
BTV.
.
.
Unicast.
Full.
Multicast. 1
.
.................................................................................................................................................................................................................................... 1350 OMS 19-49 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
Create a Bridge EVC
....................................................................................................................................................................................................................................
Table 19-2
Service Type, Type, Resource Sharing relations
Service Type. Broadcast.
Type. Rooted Multipoint.
Traffic Type. Unicast.
(continued)
Resource Sharing. Full. Private UNI. Private Link. Private UNI and Link. 1
.
Notes:
1.
This case allows a selection of the parameters.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • • •
The User Label must be different from any in use by another EVC. Only one Root termination is authorized. The EVC Type must be compatible with the service type of the associated Ethernet Service.
• •
The EVC Type must be compatible with the selected Traffic Type. The role of each EVC termination must be compatible with the EVC Type.
Task
From the Multi Service GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Action > Packet > Services > Connection Less (Bridge) > Create Bridge EVC. Result: The creation window is displayed. ...................................................................................................................................................................................................
2
General Panel.
Following data can be filled in the General Panel: •
Enter an EVC User Label.
•
Service:
.................................................................................................................................................................................................................................... 1350 OMS 19-50 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
Create a Bridge EVC
....................................................................................................................................................................................................................................
• •
Two different choices are possible: – Choose an already created Ethernet Service by using the sensitive help (this field is automatically filled if this window is required from the Service List). – Choose a Service Type (EVPL, EPTL, EPL, EVPLAN, Extended EVPL, Extended EVPLAN, HSI, BTV, Broadcast). The parameters: Type and Resource Sharing are assigned according to the chosen Service Type as indicated in: Table 19-2, “Service Type, Type, Resource Sharing relations” (p. 19-49). Select a Type (Point to Point, Routed Multipoint, Any to Any (=Multipoint to multipoint)). if allowed. Select a Traffic Type (Unicast, Multicast), the selection of the parameter depends on the selected type. Select a Service Level (Premium, Gold, Silver, Bronze). Resource Sharing: to manage the issue related to Shared or Dedicated Transport Link usage, the Resource Sharing attribute at EVC Level can assume following values. – Full: the EVC Service under definition can use every resource without any restriction. – Private UNI: the EVC Service under definition must use Private UNI, that is, the UNI is uniquely used by the EVC Service. – Private Link: The EVC Service under definition must use Private Links, that is, Transport Links uniquely used by the EVC Service. – Private UNI and LINK: The EVC Service under definition must use Private UNI and Private Links, that is, chosen Transport Links and UNIs are uniquely used by that EVC Service. Select a Domain Label. Select a Service Level (Premium, Gold, Silver, Bronze).
•
C-VLAN Preservation: check it to keep the VLAN Id through the EVC.
•
• • •
(see: “C-VLAN and CoS Preservation” (p. 18-41)). •
C-VLAN CoS Preservation: check it to keep the Priority Bits through the EVC.
(see: “C-VLAN and CoS Preservation” (p. 18-41)). •
NAD: select a NAD value from the list.
•
Enter a Comment (optional).
•
Enter an External Mark (optional). It can be used to identify external systems having relations with the EVC (for example an ownership).
...................................................................................................................................................................................................
3
Detail Panel.
Following data can be filled in the Detail Panel: •
Enter Vlan Distribution (Full mesh, Not full mesh).
•
Enter s-Vlan Id the range of the VLAN over SDH path, an equal value can go on the same domain. Define IGMP Snooping State (Not Meaningful, Enabled, Disabled).
•
.................................................................................................................................................................................................................................... 1350 OMS 19-51 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
Create a Bridge EVC
....................................................................................................................................................................................................................................
•
This option is available only for EVPLAN, Extended EVPLAN and BTV EVC types and can optionally be defined as: – Enabled: to remind that the IGMP snooping protocol is used on top of the created EVC. The IGMP is enabled immediately after the implementation of the EVC and the IGMP is disabled immediately before the de-implementation the EVC. – Disabled: to remind that the IGMP snooping protocol is not used on the created EVC. Select the Frame Delivery parameters (see “Frame delivery” (p. 18-41)) – Unicast Service Frame Delivery. –
Multicast Service Frame Delivery.
•
– Broadcast Service Frame Delivery. Select the standard Vlan Type (8100).
•
Enter a Vlan Bundle in the range of the local Vlan.
...................................................................................................................................................................................................
4
Layer-2 Control Protocol Panel.
If the entire set has the same value, then select the first parameter Put entire set to • • •
Default, all the set is put to Tunnel. Not Meaningful, all the set is put to Not Meaningful. Free, every value can be different.
Select which control Protocol must be tunneled or discarded. Such configuration is propagated to all EVC terminations (this configuration ensures that all EVC terminations use the same Tunneling criteria). A check is needed also toward Layer-2 Control Protocol Processing defined at UNI level. This check allows a congruent management of Control protocols crossing the EVC. The default value is Tunnel. Checking the Set to Default box all values are set to Tunnel. Checking the Set to Not Meaningful box all values are set to Not Meaningful. The single L2 protocol can have different values, select a value for each protocol selecting between Tunnel, Not Meaningful, and Discard. ...................................................................................................................................................................................................
5
Confirm the EVC creation with OK button. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-52 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
Modify a Bridge EVC
....................................................................................................................................................................................................................................
Modify a Bridge EVC When to use
The EVC modification gives the possibility to modify parameters and relative values. Related Information
If the User Label is modified, the new User Label must be different from the one which is already used by another EVC. For information about Connection Less EVC, see: “Bridge Traffic Management” (p. 19-6). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. Result: The Connection Less EVC list window is displayed. ...................................................................................................................................................................................................
2
Select the element to modify in the list. ...................................................................................................................................................................................................
3
Click the right mouse button and select Modify from the popup menu. ...................................................................................................................................................................................................
4
To modify an EVC (Ingress Flow): •
Enter a new User Label (optional).
•
C-VLAN Preservation: check it to keep the VLAN Id through the EVC.
(see: “C-VLAN and CoS Preservation” (p. 18-41)). •
C-VLAN CoS Preservation: check it to keep the Priority Bits through the EVC.
(see: “C-VLAN and CoS Preservation” (p. 18-41)).
.................................................................................................................................................................................................................................... 1350 OMS 19-53 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
Modify a Bridge EVC
....................................................................................................................................................................................................................................
• •
Modify the Comment (optional). Modify the External Mark (optional).
Figure 19-5 EVC Modification window (Details)
To modify an EVC (Details Panel): •
Modify VLAN distribution (optional).
•
Modify S-Vlan Id value (optional).
•
Modify Unicast Service Frame Delivery (optional).
•
Modify Multicast Service Frame Delivery (optional).
• •
Modify Broadcast Service Frame Delivery (optional). Modify VLAN Type (optional).
•
Modify VLAN Bundle (optional).
.................................................................................................................................................................................................................................... 1350 OMS 19-54 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
Modify a Bridge EVC
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
5
Click Ok button to confirm the changes. Result: Then, the EVC list, the tree area, and the opened graphical views are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-55 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
Delete a Bridge EVC
....................................................................................................................................................................................................................................
Delete a Bridge EVC When to use
This function consists in deleting an EVC from the 1350 OMS PKT supervision. Related Information
For information about Connection Less EVC, see: “Bridge Traffic Management” (p. 19-6). After confirmation, the following checks are performed: • • •
the 1350 OMS PKT checks that no Ethernet Segment is referring the EVCs. the EVCs are dissociated from the related service (if no more EVC are associated to the service, the service is also removed). the EVCs are removed.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • • •
The provisioning state of the EVC must be defined. No Ethernet Segment is referring the EVC. No operation is pending on the EVC.
Task
From the Multi Service GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. ...................................................................................................................................................................................................
2
On the Bridge EVCsr List Window, select the EVC to delete. Select Action > Bridge EVC > Delete from the Action menu. ...................................................................................................................................................................................................
3
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40).
.................................................................................................................................................................................................................................... 1350 OMS 19-56 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
Delete a Bridge EVC
....................................................................................................................................................................................................................................
Result: The EVC is deleted.
The EVC list, the tree area, and the opened graphical views are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-57 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
Get the EVC properties
....................................................................................................................................................................................................................................
Get the EVC properties When to use
This function gets information about an Ethernet Virtual Connection. Related Information
For general information about Transport Links, see: “Transport link management” (p. 11-50). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the Multi Service GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. Result: The Bridge EVC list is displayed. ...................................................................................................................................................................................................
2
Select a Bridge EVC element from the list. ...................................................................................................................................................................................................
3
From the Main Menu follow the path Action > Properties.
.................................................................................................................................................................................................................................... 1350 OMS 19-58 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
Get the EVC properties
....................................................................................................................................................................................................................................
Result: The Bridge EVC Properties window is displayed.
See the following topic in this document: “Details of a Bridge EVC” (p. 19-60) Figure 19-6 EVC Properties window
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-59 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
Details of a Bridge EVC
....................................................................................................................................................................................................................................
Details of a Bridge EVC Attributes of a Bridge EVC
The attributes displayed for each EVC are: •
Id.
•
User Label.
•
Service Id Label.
•
Ethernet Service User Label.
•
Type (Point to point, Routed multi-point, Any to any).
•
Traffic Type (Unicast, Multicast).
•
Directionality.
•
Service Level.
• •
Comment.
•
Action Type.
•
Action Date.
•
Working State (Normal, Configuring, Allocating, De-allocating, Implementing, De-implementing, Commissioning, De-commissioning, Termination adding, Termination removing, Constraint adding, Constraint removing, removing).
•
Provisioning State (Defined, Partially allocated, Allocated, Partially implemented, Implemented, Commissioned).
•
Service State (Not in Service, In Service).
•
Availability Status (Normal, Degraded, In Failure, Not Meaningful).
•
ETS Id Label.
•
ETS LABEL label.
•
Vlan Type.
•
Resource sharing.
• •
Domain Id.
•
VLAN distribution.
•
S-VLAN Id.
External Mark.
Domain.
.................................................................................................................................................................................................................................... 1350 OMS 19-60 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
Configure a Bridge or an ETS EVC
....................................................................................................................................................................................................................................
Configure a Bridge or an ETS EVC When to use
The configuration of an EVC consists in associating a Traffic Descriptor to the EVC. This function is available for Connection Oriented and Connection Less EVCs. Related Information
See “EVC Management” (p. 11-53). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the Multi Service GUI Main view: ...................................................................................................................................................................................................
1
Select one the following commands: •
Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs
•
Search > Packet > Services > Connection Oriented (ETS) > ETS EVCs Result: The EVC list window is displayed.
...................................................................................................................................................................................................
2
Select the EVC in the list. ...................................................................................................................................................................................................
3
Follow the path Action > Bridge EVC > EVC Configuration. Result: The EVC Configuration window is displayed. ...................................................................................................................................................................................................
4
Select a Traffic Descriptor using the sensitive help. ...................................................................................................................................................................................................
5
Click Ok. Result: The Traffic Descriptor is assigned to the EVC.
A correlation with the EVC is created. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-61 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
Add bridge Transport Link to EVC
....................................................................................................................................................................................................................................
Add bridge Transport Link to EVC When to use
This function adds a Transport Link to a Connection Less EVC. Related Information
For information about Connection Less EVC, see: “Bridge Traffic Management” (p. 19-6). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • •
The EVC provisioning state must be set to Defined. No operation is pending on the selected EVC.
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. ...................................................................................................................................................................................................
2
Select the Bridge EVC. ...................................................................................................................................................................................................
3
Select the path Action > Bridge EVC > Add Transport Link to EVC. ...................................................................................................................................................................................................
4
Click Ok button to save the operation. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-62 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
Remove bridge Transport Link to EVC
....................................................................................................................................................................................................................................
Remove bridge Transport Link to EVC When to use
This function disassociates a Transport Link from a Connection Less EVC. Related Information
For information about Connection Less EVC, see: “Bridge Traffic Management” (p. 19-6). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • •
The EVC provisioning state must be set to Defined. No operation is pending on the selected EVC.
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. Result: The EVC list is shown. ...................................................................................................................................................................................................
2
Select the Bridge EVC and select the path Search > Bridge EVC > Transport Link. Result: The list shows the Transport Links belonging to the selected EVC. ...................................................................................................................................................................................................
3
Select a Transport Link. ...................................................................................................................................................................................................
4
Select the path Action > Transport Link > Remove Transport Link from EVC. ...................................................................................................................................................................................................
5
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: If the command is confirmed, The Transport Link is disassociated from EVC. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-63 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
Inventory of bridge Transport Links of an EVC
....................................................................................................................................................................................................................................
Inventory of bridge Transport Links of an EVC When to use
This function shows a Transport Links from a Connection Less EVC. Related Information
For information about Connection Less EVC, see: “Bridge Traffic Management” (p. 19-6). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • •
The EVC provisioning state must be set to Defined. No operation is pending on the selected EVC.
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. Result: The EVC list is shown. ...................................................................................................................................................................................................
2
Select the Bridge EVC and select the path Search > Bridge EVC > Transport Link. Result: The list shows the Transport Links belonging to the selected EVC. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-64 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
EVC Fault Localization
....................................................................................................................................................................................................................................
EVC Fault Localization When to use
This function allows the user to display the localization of alarms on an EVC. Related Information
The function is available for implemented EVCs. For more information about EVC, refer to “EVC description” (p. 18-37). For details about Fault Localization, see: “Fault Localization” (p. 11-69). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the Multi Service GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. ...................................................................................................................................................................................................
2
Select the EVC in the list. ...................................................................................................................................................................................................
3
Follow the path Search > Fault Localization.
.................................................................................................................................................................................................................................... 1350 OMS 19-65 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
EVC Fault Localization
....................................................................................................................................................................................................................................
Result: The Bridge EVC Fault Localization window is displayed.
See the following topic in this document: “Description of the list of Fault Localization” (p. 19-68) Figure 19-7 EVC Fault Localization window
...................................................................................................................................................................................................
4
Select an alarmed port on the list, navigate to the Equipment View of the NE by issuing Search > External Navigation to > USM.
.................................................................................................................................................................................................................................... 1350 OMS 19-66 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
EVC Fault Localization
....................................................................................................................................................................................................................................
Result: The NE User Interface window is displayed. Figure 19-8 Show Equipment from EVC Fault Localization
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-67 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
Description of the list of Fault Localization
....................................................................................................................................................................................................................................
Description of the list of Fault Localization Attributes of a Fault Localization
The Fault Localization window displays: •
The User Label of the alarmed entity.
•
The Entity Type of the alarmed entity.
•
The Alarm /Availability State.
•
The Specific Fault Date.
•
The Probable Cause.
•
The Operator Label.
•
The NE User Label
•
The Global Alarm Date. Note: The list is not refreshed automatically, click Actualize button to refresh it.
.................................................................................................................................................................................................................................... 1350 OMS 19-68 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
Description of the list of Alarms
....................................................................................................................................................................................................................................
Description of the list of Alarms Attributes of an Alarm
The alarm list window displays: •
The Perceived Severity.
•
The Event Date & Time.
•
The Friendly Name.
•
The Alarm Type.
•
The Probable Cause.
.................................................................................................................................................................................................................................... 1350 OMS 19-69 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
Navigation to AS
....................................................................................................................................................................................................................................
Navigation to AS When to use
Starting from an implemented EVC, the corresponding alarm list can be displayed in AS window. Related Information
The function is available for implemented EVCs. For general information about Fault Localization, see: “Fault Localization” (p. 11-69). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the Multi Service GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. ...................................................................................................................................................................................................
2
Select the EVC in the list. ...................................................................................................................................................................................................
3
Follow the path from the popup menu Search > External Navigation to > AS.
.................................................................................................................................................................................................................................... 1350 OMS 19-70 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Connection Less EVC Management
Navigation to AS
....................................................................................................................................................................................................................................
Result: The Fault Management window is displayed with the alarms concerning the selected EVC. Figure 19-9 AS window for EVC Alarms
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-71 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Bridge EVC Termination Management
View the list of EVC terminations
....................................................................................................................................................................................................................................
Bridge EVC Termination Management View the list of EVC terminations When to use
The EVC Termination List window presents all the terminations of the selected EVC and their attributes. Related Information
From list, the user displays the extremity of an EVC or deletes EVC. If the list is required from the Ethernet Service List (or from the EVC List), only the EVC terminations associated to the selected service (or EVC) are displayed. For information about Connection Less EVC, see: “Bridge Traffic Management” (p. 19-6). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. ...................................................................................................................................................................................................
2
Select the bridge EVC in the list. ...................................................................................................................................................................................................
3
Select the path Search > Inventory from Bridge EVC > List EVC Terminations. Result: The list window is displayed.
See the following topic in this document: “Description of the list of EVC Terminations” (p. 19-73) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-72 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Bridge EVC Termination Management
Description of the list of EVC Terminations
....................................................................................................................................................................................................................................
Description of the list of EVC Terminations Attributes of a EVC Termination
The attributes displayed for each EVC termination are: •
EVC Termination User Label.
•
Rate.
•
Network Element.
•
EVC User Label.
•
Role (Root, Leaf, Both).
•
Usage State.
•
VLAN Type.
.................................................................................................................................................................................................................................... 1350 OMS 19-73 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Bridge EVC Termination Management
Add Connection Less EVC Termination
....................................................................................................................................................................................................................................
Add Connection Less EVC Termination When to use
This function consists in adding terminations to a Connection Less EVC. Related Information
For information about Connection Less EVC, see: “Bridge Traffic Management” (p. 19-6). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • • • •
The EVC provisioning state must be set to Defined. Only one termination can have "Root" role. EVC Termination Role must be congruent with the EVC topology. No operation is pending on the selected EVC.
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. ...................................................................................................................................................................................................
2
Select the Bridge EVC in the list where the termination must be added. ...................................................................................................................................................................................................
3
Select the path Action > Bridge EVC > Add Connection Less EVC Termination.
.................................................................................................................................................................................................................................... 1350 OMS 19-74 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Bridge EVC Termination Management
Add Connection Less EVC Termination
....................................................................................................................................................................................................................................
Result: The Add Termination window is displayed. Figure 19-10 Add EVC termination window (General Panel)
...................................................................................................................................................................................................
4
The Add Termination window has four different panels: General, Ingress Flow, Egress Flow, and Layer-2 Control Protocol.
.................................................................................................................................................................................................................................... 1350 OMS 19-75 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Bridge EVC Termination Management
Add Connection Less EVC Termination
....................................................................................................................................................................................................................................
On the General Panel, insert following data: •
Select a NE or ENE using the popup list window with available NEs.
•
Select an Edge Port using the popup list window with available Edge Ports.
•
Select the termination Role (Root, Leaf, Both).
...................................................................................................................................................................................................
5
On the Ingress Flow panel insert following data: At least one Input Ethernet Flow OR at least one Output Ethernet Flow must be defined: this allowing to cover following cases: • • •
To define some Source EVC Termination point in Broadcasting Topologies only Input Ethernet Flows are defined. To define some Sink EVC Termination point in Broadcasting Topologies only Output Ethernet Flows are defined. To define some Bidirectional EVC Termination point in PTP, Rooted MultiPoint or Multi Point To Multi Point topologies, Input Ethernet Flows, and Output Ethernet Flows are defined; such point can be either balanced (that is, having equal I/O characteristics) or Unbalanced (that is, having Input characteristics different from output characteristics both in term of classification, bandwidth, Qos, and so forth).
Execute the following steps: • •
Select a Traffic Descriptor. Select Color Profile and Policy Mode (optional).
•
Check or clear the Vlan Pop Enabled.
.................................................................................................................................................................................................................................... 1350 OMS 19-76 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Bridge EVC Termination Management
Add Connection Less EVC Termination
....................................................................................................................................................................................................................................
• •
Select the Classification Mode (Priority, DSCP). Select a Traffic Classifier clicking the button that displays the available Traffic Classifier list.
...................................................................................................................................................................................................
6
On the Egress Flow panel insert following data:
.................................................................................................................................................................................................................................... 1350 OMS 19-77 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Bridge EVC Termination Management
Add Connection Less EVC Termination
....................................................................................................................................................................................................................................
Execute following steps: • •
Select the Class of Service (if Same as Ingress Flow not selected). Insert the VLAN and Priority for the Push operation.
Figure 19-11 Add EVC termination window (Egress Flow)
.................................................................................................................................................................................................................................... 1350 OMS 19-78 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Bridge EVC Termination Management
Add Connection Less EVC Termination
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
7
On the Layer-2 Control Protocol Panel the control protocol is set for the termination. The selection which control Protocol must be tunneled or discarded can be made also at termination level. If the entire set has the same value, then select the first parameter Put entire set to • • •
Default, all the set is put to Tunnel. Not Meaningful, all the set is put to Not Meaningful. Free, every value can be different.
A check is needed also toward Layer-2 Control Protocol Processing defined at UNI level. This check allows a congruent management of Control protocols crossing the EVC.
.................................................................................................................................................................................................................................... 1350 OMS 19-79 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Bridge EVC Termination Management
Add Connection Less EVC Termination
....................................................................................................................................................................................................................................
The single L2 protocol can have different values. Select a value for each protocol selecting between Tunnel, Not Meaningful, and Discard. Figure 19-12 Add EVC termination window (L2 Control Protocol Panel)
...................................................................................................................................................................................................
8
Click Ok button to save the operation. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-80 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Bridge EVC Termination Management
Delete a Bridge EVC Termination
....................................................................................................................................................................................................................................
Delete a Bridge EVC Termination When to use
This function consists in deleting an EVC termination from the 1350 OMS PKT supervision. Related Information
For information about Connection Less EVC, see: “Bridge Traffic Management” (p. 19-6). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • •
The specified EVC termination is not used as Ethernet Segment extremity. No operation is pending on the selected EVC termination.
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. Result: The bridge EVC list window is displayed. ...................................................................................................................................................................................................
2
Select the bridge EVC in the list where the termination is to delete. ...................................................................................................................................................................................................
3
Select the path Search > Inventory from Bridge EVC > List EVC Terminations. Result: The EVC termination list window is displayed. ...................................................................................................................................................................................................
4
On the Bridge EVCs termination List Window, select the EVC termination to delete. Select Action > EVC Port > Delete from the Action menu. ...................................................................................................................................................................................................
5
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40).
.................................................................................................................................................................................................................................... 1350 OMS 19-81 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Bridge EVC Termination Management
Delete a Bridge EVC Termination
....................................................................................................................................................................................................................................
Result: The EVC termination is deleted.
After confirmation: • the EVC terminations are dissociated from the related EVC. • the EVC terminations are removed. The EVC Termination list is updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-82 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Bridge EVC Termination Management
Configure a Bridge EVC Termination
....................................................................................................................................................................................................................................
Configure a Bridge EVC Termination When to use
This function consists in configuring an Ethernet Virtual Connection termination. Related Information
For information about Connection Less EVC, see: “Bridge Traffic Management” (p. 19-6). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. Result: The EVC list window is displayed. ...................................................................................................................................................................................................
2
Select the EVC in the list. ...................................................................................................................................................................................................
3
Select the path Search > Inventory from Bridge EVC > List EVC Terminations. Result: The EVC Termination list window is displayed. ...................................................................................................................................................................................................
4
Select the termination to configure in the list and follow the path Action > EVC Port > EVC Termination Configuration.
.................................................................................................................................................................................................................................... 1350 OMS 19-83 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Bridge EVC Termination Management
Configure a Bridge EVC Termination
....................................................................................................................................................................................................................................
Result: The EVC Port Configuration window is displayed. Figure 19-13 EVC Termination Configuration window
...................................................................................................................................................................................................
5
On the Configuration Window. To configure the EVC termination: •
Select a Traffic Descriptor using the list of the available Traffic Descriptors displayed.
...................................................................................................................................................................................................
6
Click Ok. Result: The Traffic Descriptor is assigned to the EVC termination.
A correlation with the EVC is created. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-84 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Bridge EVC Termination Management
Get the EVC termination properties
....................................................................................................................................................................................................................................
Get the EVC termination properties When to use
This function gets information about an Ethernet Virtual Connection termination. Related Information
For information about Connection Less EVC, see: “Bridge Traffic Management” (p. 19-6). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. Result: The Bridge EVC list is displayed. ...................................................................................................................................................................................................
2
Select a Bridge EVC element from the list. ...................................................................................................................................................................................................
3
To display the EVC terminations, select the path Search > Inventory from Bridge EVC > List EVC Terminations. Result: The EVC Termination list window is displayed. ...................................................................................................................................................................................................
4
From the Main Menu follow the path Action > Properties.
.................................................................................................................................................................................................................................... 1350 OMS 19-85 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Bridge EVC Termination Management
Get the EVC termination properties
....................................................................................................................................................................................................................................
Result: The Bridge EVC termination Properties window is displayed.
See the following topic in this document: “Details of an EVC Termination” (p. 19-87) Figure 19-14 EVC Termination Properties window
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-86 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Bridge EVC Termination Management
Details of an EVC Termination
....................................................................................................................................................................................................................................
Details of an EVC Termination Attributes of an EVC Termination
The attributes displayed for each EVC termination are: •
Id.
•
EVC Termination User Label.
•
Rate.
•
NE Id Label
• •
Network Element.
• •
EVC User Label.
• •
Usage State.
•
Service Id Label
•
Ethernet Service
•
VLAN Id
• •
VLAN Type.
•
VLAN Bundle
•
Policy Mode
•
Traffic Descriptor
•
Color Profile
•
VLAN Pop
•
Class Of Service
•
VLAN Id
•
Green Priority
•
Yellow Priority
EVC Id Role (Root, Leaf, Both). Type
VLAN Protocol Type
.................................................................................................................................................................................................................................... 1350 OMS 19-87 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
Overview about Workflow
....................................................................................................................................................................................................................................
Workflow for Bridge Management Overview about Workflow Description
The workflow to manage bridge is part of the more general workflow for the Ethernet Service management. For information about bridge network, see: “Bridge Network Management” (p. 19-4). Spanning Tree Protocol is a control protocol running inside a Bridge Network able to build tree based Active Topologies. The following Spanning Tree Protocols are available: STP, RSTP, PVSTP, MISTP. For information about Spanning Tree, see: “Spanning Tree Instance Management” (p. 19-8). Domain definition
A Domain is a distributed infrastructure made of NE, ENE, Transport Links and Edge Ports managed together to supply a Connection Less infrastructure. Its main properties are the bridge type (MAC, Virtual or Provider) and the STP type (STP, RSTP, PVSTP, MSTP or none). For Connection Oriented infrastructures, a default domain encompassing all such entities is considered existing by definition. There can be two ways of defining a domain: • •
Define a unique domain that includes all the NE and ENE that supplies the same service or. Define more domains that includes NE and ENE that supplies the same service, but are subdivided for example by customer.
The ETS domain is the default domain and is equal to the MAC domain. The Domain List window presents all the domains and their attributes. The domain ETS is created by defaults and cannot be deleted. Domain configuration
The Provider Bridge operation Mode allows to define the global QoS policy to be applied to all Ethernet Ports of a given Provider Bridge. Such value is mirrored on all Ports when each Port has configured the PCP Port Table Profile with its default value (that is, 0). The Provider Bridge Operation Mode can be configured on NE basis. The new attribute Provider Bridge Operation Mode (5P3D, 8P0D, 7P1D, 6P2D, CustomerDefined) is added to the Domain.
.................................................................................................................................................................................................................................... 1350 OMS 19-88 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
Overview about Workflow
....................................................................................................................................................................................................................................
The value is derived from the corresponding value set at NE level, from all NEs contained in the Provider Bridge Domain. In particular, if all NEs have a homogeneous configuration of Provider Bridge Operation Mode, then the Domain reflects a real value, in all other cases, the value for the domain is set to "None". The Attribute can be configured at any time, this implying the automatic provisioning of the chosen value on all NEs contained in the Provider Bridge Domain. This operation forces all the ETB ports present in each Provider Bridge to be reset at the same Bridge NE PbOperationMode value and must be made paying attention. This attribute is meaningful only in case of Domain configured as Provider Bridge. The management performed at Domain level, ensures that all NEs contained inside the Provider Bridge domain really use the same QoS management. In fact, when all NEs are defined to use the same Priority Code Point All incoming Ethernet frames are interpreted in the same way: a defined meaning is assigned to each received sequence of Priority bits and such meaning/behavior is made common to a whole domain. NE configuration
The Provider Bridge operation Mode allows to define the global QoS policy to be applied to all Ethernet Ports of a given Provider Bridge. Such value is mirrored on all Ports when each Port has configured the PCP (priority code point) Port Table Profile with its default value (that is, 0). The Provider Bridge Operation Mode can be configured on NE basis. The configuration of the Provider Bridge Operation Mode on a Network Element is possible as described in the procedure“Configure a Network Element” (p. 19-98).
.................................................................................................................................................................................................................................... 1350 OMS 19-89 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
Create a Domain
....................................................................................................................................................................................................................................
Create a Domain When to use
This function allows the operator to define a domain in the managed network. Related Information
For information, see: “Overview about Workflow ” (p. 19-88). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The maximum number of domains must not be reached.
•
The User Label must be not in use by another domain.
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Action > Packet > Construction > Create Domain. ...................................................................................................................................................................................................
2
On the Create Domain Window. To create a domain: •
Enter a User Label.
•
Enter a Bridge Type (None, MAC, Virtual, Provider, Not Meaningful, No Bridge).
•
Enter an STP Type (None, MSTP, PVSTP, RSTP, STP, Disabled).
•
Enter a Comment (optional).
...................................................................................................................................................................................................
3
Click Ok. Result: The domain is created.
The Domain list is updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-90 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
Add NE to a Domain
....................................................................................................................................................................................................................................
Add NE to a Domain When to use
The user adds a NE to a domain to manage the NE in that domain. Related Information
For information, see: “Overview about Workflow ” (p. 19-88). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Construction > Network Elements > Defined NEs. ...................................................................................................................................................................................................
2
Select the NE in the list. ...................................................................................................................................................................................................
3
Follow the path Action > Network Element > Assign Network Element to Domain.
.................................................................................................................................................................................................................................... 1350 OMS 19-91 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
Add NE to a Domain
....................................................................................................................................................................................................................................
Result: The assign window is displayed.
...................................................................................................................................................................................................
4
Click the Bridge Domain field.
.................................................................................................................................................................................................................................... 1350 OMS 19-92 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
Add NE to a Domain
....................................................................................................................................................................................................................................
Result: The list of available bridge domain is displayed.
...................................................................................................................................................................................................
5
Select the desired domain and Click the check sign to confirm it. ...................................................................................................................................................................................................
6
Click Ok. Result: The NE is assigned to the Domain previously created. This operation is
repeated for all the NEs that must be assigned to a domain. The domain must be the same or a different domain as explained in previous paragraph. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-93 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
Domain Configuration
....................................................................................................................................................................................................................................
Domain Configuration When to use
This function allows the configuration of the Provider Bridge Operation mode of a provider domain. Related Information
For information, see: “Domain configuration” (p. 19-88). For information, see: “Overview about Workflow ” (p. 19-88). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Less (Bridge) > Bridge Domains. ...................................................................................................................................................................................................
2
Select the Domain in the list. ...................................................................................................................................................................................................
3
Follow the path Action > Domain > Configure Domain.
.................................................................................................................................................................................................................................... 1350 OMS 19-94 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
Domain Configuration
....................................................................................................................................................................................................................................
Result: The configuration window is displayed. Figure 19-15 Provider Domain Configuration window
...................................................................................................................................................................................................
4
Select the Provider Bridge Operation Mode from the list. ...................................................................................................................................................................................................
5
If the Operation mode must be propagated to NEs belonging to the domain, select true; otherwise, select false. ...................................................................................................................................................................................................
6
Click Ok. Result: The Domain is configured consequently. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-95 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
Domain Modification
....................................................................................................................................................................................................................................
Domain Modification When to use
This function modifies the VLAN Type for the domain. Related Information
For information, see: “Overview about Workflow ” (p. 19-88). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Less (Bridge) > Bridge Domains. ...................................................................................................................................................................................................
2
Select the Domain in the list. ...................................................................................................................................................................................................
3
Follow the path Action > Modify.
.................................................................................................................................................................................................................................... 1350 OMS 19-96 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
Domain Modification
....................................................................................................................................................................................................................................
Result: The modification window is displayed. Figure 19-16 Domain Modification window
...................................................................................................................................................................................................
4
If the Set Standard VLAN Type (8100) is set to False, select the VLAN TYPE from the list of defined VLAN Types. ...................................................................................................................................................................................................
5
If the Set Standard VLAN Type (8100) is set to True, the VLAN TYPE is already set. ...................................................................................................................................................................................................
6
Click Ok. Result: The Domain is modified consequently. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-97 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
Configure a Network Element
....................................................................................................................................................................................................................................
Configure a Network Element When to use
Configure the Provider Bridge Operation Mode on NE basis. Related Information
For information, see: “Overview about Workflow ” (p. 19-88). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Services > Connection Less (Bridge) > Bridge NEs. ...................................................................................................................................................................................................
2
Select the Network Element in the list. ...................................................................................................................................................................................................
3
Follow the path Action > Network Element > Configure.
.................................................................................................................................................................................................................................... 1350 OMS 19-98 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
Configure a Network Element
....................................................................................................................................................................................................................................
Result: The configuration window is displayed. Figure 19-17 Network Element Configure window
...................................................................................................................................................................................................
4
To configure a Network Element: • •
Choose the Provider Bridge Operation Mode (As Container, 5P3D, 8P0D). If the operation mode must be propagated to the edge ports associated to NE, choose True for Propagate to Edge Ports parameter; in any other case, choose False.
...................................................................................................................................................................................................
5
Click Ok. Result: The Network Element is configured consequently. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-99 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
Link Over TDM configuration
....................................................................................................................................................................................................................................
Link Over TDM configuration When to use
Configure the Link Over TDM. Related Information
For information, see: “Overview about Workflow ” (p. 19-88). For Link Over TDM, see: “Managing Links Over TDM” (p. 14-17). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Construction > Link Over TDM. ...................................................................................................................................................................................................
2
Select the Link Over TDM in the list. ...................................................................................................................................................................................................
3
Follow the path Action > Link Over TDM > Configure.
.................................................................................................................................................................................................................................... 1350 OMS 19-100 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
Link Over TDM configuration
....................................................................................................................................................................................................................................
Result: The configuration window is displayed. Figure 19-18 Client Type Selection
...................................................................................................................................................................................................
4
Select the Client Type ETB in the Configuration window. ...................................................................................................................................................................................................
5
Click Ok. Result: The Link Over TDM is configured consequently. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-101 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
NE Ethernet Physical Port Configuration
....................................................................................................................................................................................................................................
NE Ethernet Physical Port Configuration When to use
The NE Ethernet physical ports (local ports) are configured as ETS-P in a provider bridge configuration. Related Information
For information, see: “Overview about Workflow ” (p. 19-88). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Construction > Network Elements > Defined NEs. ...................................................................................................................................................................................................
2
Select the Network Element in the list. ...................................................................................................................................................................................................
3
Follow the path Search > Inventory from Network Element > Ethernet Physical Port List. Result: The Ethernet Physical port list window is displayed. Figure 19-19 Ethernet Physical Port
.................................................................................................................................................................................................................................... 1350 OMS 19-102 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
NE Ethernet Physical Port Configuration
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
The Ethernet Physical Port list of the selected Network Element is displayed, select the port to configure and from the popup menu the item Configure. Result: The configuration window is displayed. Figure 19-20 Ethernet Physical Port Configuration window
...................................................................................................................................................................................................
5
Select the Client Type ETS-P and confirm with OK Button. Result: The Ethernet Physical Port is configured consequently. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-103 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
Create a Customer
....................................................................................................................................................................................................................................
Create a Customer When to use
This function allows the user to define the characteristics of the owner (=customer) of one or more NE(s) to allow the usage of services defined across the boundaries of the managed network. Related Information
The first step to perform in EOT User Interface is the Customer creation to be able to create the desired Ethernet Service. For information, see: “Overview about Workflow ” (p. 19-88). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The maximum number of customers must not be reached.
•
The User Label must be not in use by another customer.
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Action > Packet > Services > Create Customer.
.................................................................................................................................................................................................................................... 1350 OMS 19-104 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
Create a Customer
....................................................................................................................................................................................................................................
Result: The customer creation window opens. Figure 19-21 Customer Creation window
...................................................................................................................................................................................................
2
On the Create Customer Window insert the required data.
.................................................................................................................................................................................................................................... 1350 OMS 19-105 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
Create a Customer
....................................................................................................................................................................................................................................
To create a customer: •
Enter a User Label.
•
Enter a Company (optional).
•
Enter an Address (optional).
•
Enter a Comment (optional).
...................................................................................................................................................................................................
3
Click Ok. Result: The customer is created.
The tree area and the Customer list are updated. The user can define services related to this customer. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-106 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
Create an Ethernet Service
....................................................................................................................................................................................................................................
Create an Ethernet Service When to use
This function allows creating an Ethernet Service (related to a selected customer). Related Information
If this list is required from the Customer List, the Customer field of this creation window is automatically filled with the customer value selected in the Customer List. For general information, see: “Overview about Workflow ” (p. 19-88). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • •
Before the action, define one customer at least. The User Label must be not in use by another service.
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Action > Packet > Services > Create Ethernet Service. ...................................................................................................................................................................................................
2
On the Create Service Window. Execute the following steps: •
Enter a Service User label.
•
Select the Customer from the available customer list, which opens when you enter the Customer field. Select the Service Type Extended EVPL. No other data are required. Click Ok.
• • •
...................................................................................................................................................................................................
3
Click Ok. Result: The service is created.
A correlation with the selected customer is created. .................................................................................................................................................................................................................................... 1350 OMS 19-107 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
Create an Ethernet Service
....................................................................................................................................................................................................................................
Then, the tree area and the Ethernet Service List are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-108 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
Traffic Descriptor Definition
....................................................................................................................................................................................................................................
Traffic Descriptor Definition When to use
Creation of the Traffic Descriptor. Related Information
For information, see: “Overview about Workflow ” (p. 19-88). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Action > Packet > Services > Create Traffic Descriptor. Result: The creation window is displayed. ...................................................................................................................................................................................................
2
On the Create Traffic Descriptor Window. To create a Traffic Descriptor: •
Enter a User Label.
•
Select the Class of Service (Best Effort, Guaranteed, Regulated, Regulated1, Regulated3, Regulated4, Guaranteed2, Background). Enter a CIR value (set automatically to '0' if the selected Class of Service is 'Best Effort'). Enter a PIR value. Enter a CBS value (set automatically to '0' if the selected Class of Service is 'Best Effort'). Enter a PBS value (if the selected Class of Service is 'Guaranteed', PBS value is automatically set to CBS value - but could be modified).
• • • •
...................................................................................................................................................................................................
3
Click Ok. Result: The Traffic Descriptor is created.
A correlation with the selected customer is created.
.................................................................................................................................................................................................................................... 1350 OMS 19-109 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
Traffic Descriptor Definition
....................................................................................................................................................................................................................................
Then, the tree area and the Ethernet Service List are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-110 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Workflow for Bridge Management
EVC Allocation and Implementation
....................................................................................................................................................................................................................................
EVC Allocation and Implementation When to use
To complete the Provider Bridge Workflow: create a Connection Less EVC, allocate, and implement it. Related Information
For information, see: “Overview about Workflow ” (p. 19-88). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the menu path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. Result: The Bridge EVC list window is displayed. ...................................................................................................................................................................................................
2
Select the EVC in the list and follow the path Action > Bridge EVC > Allocate. Result: The allocation window is displayed. ...................................................................................................................................................................................................
3
Click Ok. Result: The EVC is allocated.
The Provisioning State is changed to Allocated. ...................................................................................................................................................................................................
4
Select again the EVC in the list and follow the path Action > Bridge EVC > Implement. Result: The implementation window is displayed. ...................................................................................................................................................................................................
5
Click Ok. Result: The EVC is implemented.
The Provisioning State is changed to Implemented. E................................................................................................................................................................................................... N D O F S T E P S .................................................................................................................................................................................................................................... 1350 OMS 19-111 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management
Dynamic change capability
....................................................................................................................................................................................................................................
EVC Bandwidth Management Dynamic change capability Object applicability
The possibility to change dynamically the bandwidth assigned to an active (that is, implemented) Ethernet connectivity is one of the most important capabilities in the scope of Data Network Management. The dynamic change (increment/decrement) of bandwidth is possible for: •
Connection Oriented EVC: for Connection Oriented Networks, in the following cases: – The EVC is multicast, the traffic is broadcasted from one source UNI to leaves UNI. – All contained Ethernet Segment are balanced that is, have the same bandwidth parameters definitions. – All contained Ethernet Segment are not balanced that is, have different bandwidth parameters definitions; new parameters can cause the increment for one or more Ethernet Segment and the reduction for others.
•
Connection Less EVC: for Networks based on Provider Bridge, in the following cases: –
• •
All EVC Terminations are balanced that is, have the same bandwidth parameters definitions. – All EVC Terminations are not balanced that is, have different bandwidth parameters definitions; in this case it is possible that new parameters cause the bandwidth increment for some EVC termination and the reduction for some other. Ethernet Segments for Connection Oriented Networks, when the bandwidth of a single specific flow is changed.
•
EVC Terminations for Connection Less Networks, Provider Bridge based when the bandwidth of a specific EVC termination is changed. LSP Tunnel for MPLS networks, when the LSP Tunnel bandwidth is changed.
•
VC-LSP for MPLS networks, when the VC-LSP bandwidth is changed.
.................................................................................................................................................................................................................................... 1350 OMS 19-112 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management EVC Bandwidth Management
Function Description
....................................................................................................................................................................................................................................
Function Description Object status applicability
The applicability of the Bandwidth management is restricted to the following cases: • • • • • •
Implemented and allocated EVC (Connection Oriented Networks) which automatically affects all contained Ethernet Segments. Implemented and allocated EVC (Connection Less Networks) which automatically affects all contained EVC Terminations. Implemented and allocated Ethernet Segments (Connection Oriented Networks). EVC Terminations of Implemented and allocated EVCs (Connection Less Networks, Provider Bridge based). Implemented and Allocated LSP Tunnels. Implemented and Allocated VC-LSPs.
The Bandwidth management can also be requested on Allocated resources. Implemented Object applicability
Consider the following cases: •
“EVC Connection Oriented Based (Implemented)” (p. 19-113).
•
“EVC Connection Oriented Based (Allocated)” (p. 19-114).
•
“EVC Connection Less Based (Implemented or Allocated)” (p. 19-114).
•
“Ethernet Segments (Implemented)” (p. 19-115).
•
“Ethernet Segments (Allocated)” (p. 19-116).
EVC Connection Oriented Based (Implemented)
When all contained Ethernet Segments are implemented, acting at EVC level significantly simplifies the effort for the user that is requested to provide only once the new bandwidth parameters, either to enlarge or to reduce current values. Acting at EVC level, the bandwidth change is propagated to all contained Ethernet Segments; in particular: • • • •
The EVC must be implemented, all Ethernet Segments must be implemented. The bandwidth change is applied on each Ethernet Segment. When the bandwidth change is successfully propagated to all Ethernet Segments, the EVC continue to be Implemented. The new Class of Service must be compliant with the one in use by contained Ethernet Segments (in particular, if the EVC is realized by non homogeneous Class Of Services, then to avoid errors, the user must proceed on Ethernet Segment basis).
.................................................................................................................................................................................................................................... 1350 OMS 19-113 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management EVC Bandwidth Management
Function Description
....................................................................................................................................................................................................................................
•
In case of errors, the procedure is immediately stopped and one of the following situation are identified: – the EVC provisioning state is put in partially Implemented: this case occurs when at least one Ethernet Segment become partially Implemented because of unrecoverable errors during provisioning. – The EVC provisioning state remain as implemented: this case occurs when an Ethernet Segment has no room to allocate new bandwidth parameters. In this case the Ethernet Segment remain implemented with old bandwidth parameters.
EVC Connection Oriented Based (Allocated)
When all contained Ethernet Segments are Allocated, acting at EVC level significantly simplifies the effort for the user that is requested to provide only once the new bandwidth parameters, either to enlarge or to reduce current values. Acting at EVC level, the bandwidth change is propagated to all contained Ethernet Segments; in particular: • •
The EVC must be Allocated (this implying that all Ethernet Segments are allocated). The bandwidth change is applied on each Ethernet Segment.
EVC Connection Less Based (Implemented or Allocated)
Acting at EVC level significantly simplifies the effort for the user that is requested to provide only once the new bandwidth parameters, either to enlarge or to reduce current values. Acting at EVC level, the bandwidth change is propagated to all contained EVC Terminations; in particular: •
•
• •
Care must be taken about the new Class of Service that must be compliant with the one in use by contained EVC Terminations. If the EVC is realized by non homogeneous Class Of Services, then to avoid errors, the user must proceed on EVC Termination basis. The EVC can be implemented, if all EVC Terminations are activated, or allocated, if the bandwidth change for EVC Terminations is accomplished only inside 1350 OMS PKT database. The bandwidth change is applied on each contained EVC Termination. In case of errors, the procedure is immediately stopped. The EVC provisioning state remain with the previous provisioning state. The following situation is identified: – if provisioning state was implemented, it remains implemented. This case occurs when the provisioning for an EVC termination fails (that is the EVC termination remain active with old bandwidth parameters). In this case the EVC become made by “non homogeneous” (in terms of bandwidth) EVC Termination. –
if provisioning state was allocated, it remains allocated. The EVC become made with non homogeneous EVC terminations Bandwidth characteristics.
.................................................................................................................................................................................................................................... 1350 OMS 19-114 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management EVC Bandwidth Management
Function Description
....................................................................................................................................................................................................................................
Ethernet Segments (Implemented)
This case covers Implemented Ethernet Segments on Connection Oriented Networks; • •
• •
The bandwidth change is only admitted in the scope of the same QoS (for example: change from BE to Guaranteed is not allowed as well as other mixed possibilities). The bandwidth change is performed through the Ethernet Segment modification: the parameter modified is the Traffic Descriptor reference, so allowing the Ethernet Segment to point toward another TD. The bandwidth change is allowed, without restrictions, on all Transport Links types (that is Link Over TDM, Link Over Cable and Link Over MPLS). In case of increment, an internal check is performed along the Ethernet Segment following the current routing verifying that enough bandwidth is available. In particular: – In case of positive check,. - The Ethernet Segments starts pointing to another TD that reflects the new bandwidth parameters. - The values of used/available bandwidth values must be updated on used Transport Links and Edge Ports if an increment on Guaranteed parameter is required. - The behavior for bandwidth increment is performed on the Network, starting from last NE and proceeding in reverse way along the Ethernet Segment routing. - In case of error during provisioning operation, the global operation is stopped and the Provisioning state is set to partially implemented. –
In case of Negative check: The operation is stopped, a specific error message is displayed indicating the error reason. The Provisioning state remains set to implemented.
•
In case of reduction, no internal checks are needed and the operation is accepted; In particular: – – – –
The Ethernet Segments starts pointing to another Traffic Descriptor, that reflects the new bandwidth parameters. If a reduction on Guaranteed parameter is required, the values of used/available bandwidth values are updated on used Transport Links and Edge Ports. The behavior for bandwidth reduction is performed on the Network, starting from first NE and proceeding in forward way along the Ethernet Segment routing. In case of error during provisioning operation, the global operation is stopped and the Provisioning state is set to partially implemented.
.................................................................................................................................................................................................................................... 1350 OMS 19-115 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management EVC Bandwidth Management
Function Description
....................................................................................................................................................................................................................................
Ethernet Segments (Allocated)
The bandwidth change is: • •
• •
only admitted in the scope of the same QoS (for example: change from BE to Guaranteed is not allowed as well as other mixed possibilities). performed through the Ethernet Segment modification: the parameter modified is the Traffic Descriptor reference, so allowing the Ethernet Segment to point toward another Traffic Descriptor. allowed, without restrictions, on all Transport Links types (that is Link Over TDM, Link Over Cable and Link Over MPLS). In case of increment, an internal check is performed along the Ethernet Segment following the current routing, verifying that enough bandwidth is available. In particular: – In case of positive check,. - The Ethernet Segments starts pointing to a Traffic Descriptor that reflects the new bandwidth parameters. - The values of used/available bandwidth values must be updated on used Transport Links and Edge Ports if an increment on Guaranteed parameter is required.
•
In case of reduction, no internal checks are needed and the operation is accepted; In particular: – The Ethernet Segments starts pointing to a Traffic Descriptor that reflects the new bandwidth parameters. – The values of used/available bandwidth values must be updated on used Transport Links and Edge Ports if a reduction on Guaranteed parameter is required.
EVC Terminations
The terminations are Activated EVC Terminations belonging to Implemented or Allocated EVCs based on Connection Less Networks. The same behavior is performed both for bandwidth increments and for bandwidth reduction, no internal checks are needed and the operation is accepted; In particular: • • • • •
The EVC Termination starts pointing to another Traffic Descriptor that reflects the new bandwidth parameters. Only in case of Implemented EVCs, a specific behavior is started to propagate the modification toward NEs. The behavior for bandwidth change is performed on the Network, acting on the NE containing the EVC Termination. On NEs, a specific Traffic Descriptor creation is needed if a reusable one compliant with new bandwidth characteristics not exist. In case of error during provisioning operation, the global operation is stopped and the Provisioning state of the EVC does not change.
.................................................................................................................................................................................................................................... 1350 OMS 19-116 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Service Delimiting
Vlan Push/Pop On Provider Bridge UNI/IWI Management
....................................................................................................................................................................................................................................
Service Delimiting Vlan Push/Pop On Provider Bridge UNI/IWI Management Definition
The Service Delimiting allows the finalization of Vlan Push/Pop operations also at EVCs UNI/IWI based on Provider Bridge technology. This function enhances EVC Termination characteristics definition. For this reason, all the following consideration must be taken into account: •
•
•
For each EVC termination, the user can define, in addition to existing characteristics, an optional POP operation to be performed on Ethernet Traffic in the Provider Bridge Domain at ingress (that is, at UNI/IWI). For each EVC termination, the user can define, for traffic egress the Provider Bridge domain (that is, at UNI/IWI): Define in following way: – One or more Cos. – A PUSH operation for a given Cos. For each EVC termination, the user must define at least one Input Ethernet Flow or at least one Output Ethernet Flow. This operation allowing to cover all following cases: – Definition of "Source" EVC Termination point in Broadcasting Topologies in case that only Input Ethernet Flows are defined. – –
Definition of "Sink" EVC Termination point in Broadcasting Topologies, in case that only Output Ethernet Flows are defined. Definition of Bidirectional EVC Termination point in Point-to-point, Rooted-MultiPoint, or MultiPoint-To-MultiPoint topologies. In case that both Input Ethernet Flows and Output Ethernet Flows are defined, Termination point can be either balanced or unbalanced. Balanced means having equal I/O characteristics. Unbalanced means having Input characteristics different from output characteristics. Characteristics are classification, bandwidth, Qos, and so forth.
Operation and expected behavior
Operation and expected behavior in service delimiting are: •
EVC Definition (Provider Bridge). At EVC definition, EVC Terminations can optionally be supplied. For each EVC Termination, the user can define Input or Output Ethernet Flows characteristics. If the created EVC is empty, then all EVC Termination characteristics definition is delegated to the operation: “Add EVC Termination”.
•
Add EVC Termination (Provider Bridge).
.................................................................................................................................................................................................................................... 1350 OMS 19-117 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Service Delimiting
Vlan Push/Pop On Provider Bridge UNI/IWI Management
....................................................................................................................................................................................................................................
When the user wants to add a new EVC Termination to an existing EVC, for each EVC Termination the user must define Input or Output Ethernet Flows characteristics. •
Get EVC Extremities (Provider Bridge). For the selected EVC, this inventory must report the generic characteristics of all EVC Terminations, Input Ethernet Flows, and Output Ethernet Flows included.
•
Modify EVC Termination (Provider Bridge). After having defined the characteristics of an EVC termination, the user can change such characteristics for example adding or removing a POP or a PUSH.
•
Get Properties - EVC Termination (Provider Bridge). For the selected EVC Termination, this inventory must report the relevant characteristics, Input and Output Characteristics included.
.................................................................................................................................................................................................................................... 1350 OMS 19-118 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Spanning Tree
Overview
....................................................................................................................................................................................................................................
Spanning Tree Show the Spanning Tree Instance of EVC When to use
This function shows Spanning Tree Instance of a Connection Less EVC. Related Information
For information, see: “Spanning Tree Instance Management” (p. 19-8). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: • •
The EVC provisioning state must be set to Defined. No operation is pending on the selected EVC.
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. Result: The EVC list is shown. ...................................................................................................................................................................................................
2
Select the Bridge EVC and select the path Search > Bridge EVC > Show Spanning Tree Instance. Result: The Spanning Tree Instance belonging to the selected EVC is shown. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-119 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Spanning Tree
Show the Spanning Tree Instance
....................................................................................................................................................................................................................................
Show the Spanning Tree Instance When to use
This function shows Spanning Tree Instances. Related Information
For information about STI, see: “Spanning Tree Instance Management” (p. 19-8). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge). Result: The Connection Less menu is shown. ...................................................................................................................................................................................................
2
Select Show Spanning Tree Instance. Result: The Spanning Tree Instance belonging is shown. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-120 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Spanning Tree
Spanning Tree Instance configuration
....................................................................................................................................................................................................................................
Spanning Tree Instance configuration When to use
This function configures a Spanning Tree Instance. Related Information
For information, see: “Spanning Tree Instance Management” (p. 19-8). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the menu path Search > Packet > Services > Connection Less (Bridge) > Spanning Tree Instance. Result: The Spanning Tree Instance list window is displayed. ...................................................................................................................................................................................................
2
Select the Spanning Tree Instance in the list and follow the path Action > Spanning Tree Instance > Configure.
.................................................................................................................................................................................................................................... 1350 OMS 19-121 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Spanning Tree
Spanning Tree Instance configuration
....................................................................................................................................................................................................................................
Result: The Spanning Tree configuration window is displayed. Figure 19-22 Spanning Tree Instance Configuration window
...................................................................................................................................................................................................
3
Select one of the options then click OK. Result: The Spanning Tree Instance is configured. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-122 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Spanning Tree
Spanning Tree Instance Implementation
....................................................................................................................................................................................................................................
Spanning Tree Instance Implementation When to use
This function Implement a Spanning Tree Instance. Related Information
For information, see: “Spanning Tree Instance Management” (p. 19-8). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the menu path Search > Packet > Services > Connection Less (Bridge) > Spanning Tree Instance. Result: The Spanning Tree Instance list window is displayed. ...................................................................................................................................................................................................
2
Select the Spanning Tree Instance in the list and follow the path Action > Spanning Tree Instance > Implement. ...................................................................................................................................................................................................
3
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: If the command is confirmed, the Spanning Tree Instance is Implemented. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-123 8DG42227DAAA 9.6 Issue 3 December 2012
Bridge Network Management Spanning Tree
Spanning Tree Instance Deimplementation
....................................................................................................................................................................................................................................
Spanning Tree Instance Deimplementation When to use
This function Deimplement a Spanning Tree Instance . Related Information
For information, see: “Spanning Tree Instance Management” (p. 19-8). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the menu path Search > Packet > Services > Connection Less (Bridge) > Spanning Tree Instance . Result: The Spanning Tree Instance list window is displayed. ...................................................................................................................................................................................................
2
Select the Spanning Tree Instance in the list and follow the path Action > Spanning Tree Instance > Deimplement. ...................................................................................................................................................................................................
3
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: If the command is confirmed, the Spanning Tree Instance is Deimplemented. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 19-124 8DG42227DAAA 9.6 Issue 3 December 2012
20
20 Provider Backbone Bridge Network Management
Overview Purpose
This chapter describes how to set up a Provider Backbone Bridge (PBB) network. Contents Provider Backbone Bridge (PBB) Networks
20-5
Provider Backbone Bridge Management
20-5
PBB EVC provisioning
20-8
Ethernet Ring Protocol (ERP) Network Configuration
20-10 20-11
Network Configuration
20-11
PBB Domain Create
20-12
Define NE
20-14
Provisioning
20-17
Provisioning hardware reference
20-17
Transport link
20-20
Create Ethernet Physical Connection
20-21
Assign Link over Cable to PBB domain
20-24
ERP configuration
20-30
Create ERP Ring
20-30
Create an ERP Instance
20-38
Backbone VLAN ID
20-46
B-VID configuration
20-46
EVC-EVPLAN Service in PBB/ERP
20-52
Additional Info on PBB/ERP Service
20-52
PBB EVC Termination Management
20-56
................................................................................................................................................................................................................................... 1350 OMS 20-1 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management
Overview
....................................................................................................................................................................................................................................
Add PBB EVC Termination
20-56
Remove PBB EVC Termination
20-59
Provider Backbone Bridge EVC Management
20-60
View the PBB EVC list
20-61
Description of the list of PBB EVCs
20-62
Create PBB EVC
20-63
Allocate PBB EVC
20-65
Deallocate PBB EVC
20-67
Implement PBB EVC
20-68
Deimplement PBB EVC
20-70
Add Termination on implemented PBB EVC
20-71
Remove Termination on implemented EVC
20-72
Configure PBB EVC
20-73
Bridge Flows of PBB EVC
20-74
PBB EVC Broadcast Domain Containment
20-76
Enable Broadcast Domain Containment
20-77
Disable Broadcast Domain Containment
20-78
Automatic association UNI port - default VT
20-79
Manual association UNI port - user VT
20-80
Configuration of the DEI bit
20-81
B-VID Management
20-82
View the B-VID list
20-83
Create PBB B-VID
20-84
Delete PBB B-VID
20-86
Allocate PBB B-VID
20-87
Deallocate PBB B-VID
20-88
Implement PBB B-VID
20-89
Deimplement PBB B-VID
20-91
Domain Wide VID distribution
20-93
Ring Association to a B-VID
20-95
Ring Dissociation from B-VID
20-97
Change ERP of a B-VID
20-99
List ERP instances of a B-VID
20-101
Association of Transport Link to B-VID
20-102
Dissociation of Transport Link to B-VID
20-104
.................................................................................................................................................................................................................................... 1350 OMS 20-2 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management
Overview
....................................................................................................................................................................................................................................
Ethernet Ring Protection (ERP) Management
20-107
View the ERP ring list
20-108
Description of the list of ERP
20-109
Create/delete ERP Ring
20-110
Implement/deimplement the ERP
20-112
ERP Switch Command
20-113
ERP Switch Command From Port
20-114
Add/remove Transport Link in a Ring
20-115
Add/remove Node in a Ring
20-116
Create/delete ERP Ring bundle
20-117
Add/remove ERP Ring in a bundle
20-118
ERP Instance Management
20-120
View the ERP instance list
20-121
Description of the list of ERP instances
20-122
Create/delete ERP instance
20-123
Implement/deimplement the ERP instance
20-125
Associate OAM to the ERP instance
20-126
Get a graphical view of the ERP instance
20-127
Modify Defined ERP instance
20-129
Modify implemented ERP instance
20-131
PBB Fault Management PBB Fault Localization and navigation to AS Workflow for PBB Management
20-133 20-134 20-135
Overview about Workflow
20-135
Create a PBB Domain
20-137
Add NE to a Domain
20-138
Add Transport Link to a Domain
20-139
ERP provisioning
20-141
Configure B-VID
20-143
Create a PBB EVC
20-144
PBB EVC traffic classification
20-153
Traffic Descriptor Definition
20-154
EVC Allocation and Implementation
20-155
In Band Management Address Configuration of the Network Elements
20-156 20-157
.................................................................................................................................................................................................................................... 1350 OMS 20-3 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management
Overview
....................................................................................................................................................................................................................................
Lag Port Creation (Via Zic)
20-165
NMS Start Supervision (NE Not Defined On NMS)
20-183
.................................................................................................................................................................................................................................... 1350 OMS 20-4 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge (PBB) Networks
Provider Backbone Bridge Management
....................................................................................................................................................................................................................................
Provider Backbone Bridge (PBB) Networks Provider Backbone Bridge Management PBB description
Provider Backbone Bridges (PBB) is a networking standard approved by IEEE as 802.1ah standard. Provider Backbone Bridges is a set of architecture and protocols for routing of a customer network over a provider's network Provider Backbone Bridges allows interconnection of multiple Provider Bridge Networks without losing each customer's individually defined VLANs. Provider Backbone Bridges offers a complete separation of customer and provider domains. Objectives of Provider Backbone Bridging
PBB is designed to address limitations of Provider Bridge: •
VID-space scalability. A 24-bit field is added to each frame to contain an enlarged space for customer service identification. 16 M services.
•
FDB-size scalability. The MAC addresses of all customer equipment that passes through a core node must be learned and/or looked-up in the FDB. If FDB is “full”, addresses cannot be learned, so return traffic is flooded and not unicasted: Bandwidth inefficiency. A ‘backbone’ MAC destination and source address pair is added to each frame for forwarding between PBB Nodes. This header “hides” the Customer Destination Address and Customer Source Address fields.
PBB frames
The PBB header may take multiple different forms, but the main components of the header are: •
•
Backbone component: – Backbone destination address (B-DA) (six bytes). – Backbone source address (B-SA) (six bytes). – EtherType 0x88A8 (two bytes). – B-TAG/B-VID (two bytes), this is the backbone VLAN indicator. Service encapsulation: – EtherType 0x88E7 (two bytes). – Flags that contain priority, DEI and indication, if there are no customer addresses present (e.g. OAM frames). – I-SID, the service identifier (three bytes).
.................................................................................................................................................................................................................................... 1350 OMS 20-5 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge (PBB) Networks
Provider Backbone Bridge Management
....................................................................................................................................................................................................................................
•
Original customer frame: – Customer source address (six bytes). – – – – –
Customer destination address (six bytes). EtherType 0x8100 (two bytes). Customer VLAN identifier (two bytes). EtherType (e.g. 0x0800). Customer payload.
Bridges learn based on the B-SA and ingress port value and hence is completely unaware of the customer MAC addresses. I-SID allows to distinguish the services within a PBB domain. PBB Services Types
A service is identified by a Backbone Service Instance Identifier (I-SID). The Service Type is determined by the mapping of Customer Network Port traffic to a particular I-SID. Service Types (IEEE 802.1ah): •
Port based: All untagged and priority tagged frames ↔I-SID. This service type can be used to connect 802.1Q or 802.1D bridges to a CNP. All S-Tagged frames are dropped.
• •
S-tagged one-to-one: Frames with a single specific S-VID ↔I-SID. S-tagged bundled many-to-one: Frames with an S-VID in a specific set of N values ↔I-SID. S-tagged bundled all-to-one: Frames with any non-zero S-VID ↔I-SIDcomplement of “Port Based” service.
•
Note: 1350 OMS implementation of some service types is less rigid. For example “Port-based” does not necessarily discard all S-tagged frames. PBB Services Multiplexing
The frames are split in more than one “service”, each mapped to its own I-SID. Service Types that are incompatible with Service Multiplexing: • •
Port Based Service S-Tagged Service –All-to-One
Service Types that can be used with Service Multiplexing • •
S-Tagged Service –1:1. S-Tagged Service –N:1 Note: A given S-VID can map to only a single I-SID.
Mapping single S-VID to multiple I-SIDs is not allowed: • •
Can create an unintentional loop in the PBB network. Loop cannot be guarded by xSTP: PIP-CBP barrier for STPDUs
.................................................................................................................................................................................................................................... 1350 OMS 20-6 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge (PBB) Networks
Provider Backbone Bridge Management
....................................................................................................................................................................................................................................
PBB Ethernet Virtual Connection
MEF defines Ethernet Virtual Connection (EVC) services: •
EVC: Transparent connection service between a set of UNIs
•
In a PBB context the UNI is a CNP port
The EVCs have been classified in three Service Types: • •
E-Line: Point-to-point EVC. Connects 2 UNIs bi-directionally. E-LAN: Multipoint EVC. Connects more than 2 UNIs bi-directionally.
•
E-Tree: Rooted-multipoint EVC. Connects at least one “Root” UNI and at least two “Leaf” UNIs bi-directionally, but blocking direct traffic between “Leaf” UNIs
The following Service Types are supported: • •
E-Line: Any Port-based or S-tagged service can be supported over E-LINE. E-LAN: Any Port-based or S-tagged service can be supported over E-LAN.
•
E-Tree: Not supported within PBB: Requires non-standard additions to PBB toolset. E-TREE service requires that traffic between ‘Leaves’ is blocked. Service Multiplexing: E-LINE and E-LAN services can be multiplexed on same CNP port. Restriction: S-VID to I-SID mapping constraints.
•
.................................................................................................................................................................................................................................... 1350 OMS 20-7 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge (PBB) Networks
PBB EVC provisioning
....................................................................................................................................................................................................................................
PBB EVC provisioning PBB EVC provisioning description Figure 20-1 PBB EVC provisioning
.................................................................................................................................................................................................................................... 1350 OMS 20-8 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge (PBB) Networks
PBB EVC provisioning
....................................................................................................................................................................................................................................
The figure shows that the only provisioning needed to implement an EVC over PBB is the one done at its EVC Terminations (both the one directly related to the EVC Termination itself and the one related to the association of the I-SID to the B-VID that is perfomed on the NNIs of the B-VID in the same NE of the EVC Termination). “Ethernet Ring Protocol (ERP)” (p. 20-10) To implement an EVC over PBB, the system only perform provisioning on the NEs that host EVC Terminations for that EVC. This is true only if the EVC is not under OAM. If the EVC is under OAM, things are different. In general, OAM is possible for the I-SID (to monitor the single EVC) and for the B-VID (in order to monitor the virtual infrastructure common to more EVCs). I-SID monitoring, as for the standard, only takes into account the points where the EVC is provisioned. This means that internal points are not taken into consideration: link trace is not so meaningful in that case. The choice done for PKT is a bit different: we choose to monitor only the I-SID (so, no B-VID monitoring) but, willing to see also the intermediate points in the network, we provision the I-SID also wherever the B-VID is, so that a link trace, for example, will report all the NEs crossed by the traffic. The provisioning of an EVC under OAM requires the distribution of the I-SID to all the places wherever the B-VID is distributed (for example: to all the NNIs in the network that are in NEs that do not host any Termination of the monitored EVC). The distribution of the I-SID is done in addition to any other I-SID distribution.
.................................................................................................................................................................................................................................... 1350 OMS 20-9 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge (PBB) Networks
Ethernet Ring Protocol (ERP)
....................................................................................................................................................................................................................................
Ethernet Ring Protocol (ERP) ERP Objectives
Suitable to operate in the Ethernet transport plane, which implies Connectionless forwarding Automatic address learning Ageing and flushing mechanisms Ethernet Ring Protection (Switching) –ERP(S) – is standardized by ITU-T to establish a “Carrier Class” protection switching mechanism in the Ethernet transport plane. Main objectives: • • •
Protect single ring and more complicated topologies. Fast: 50 ms traffic restoration time (Compared with multiple seconds for xSTP). Suitable to operate in the Ethernet transport plane. Operate in the Ethernet transport plane implies: – Connection less forwarding. – Automatic address learning. – Ageing and flushing mechanisms.
ERP Protocol Tuning
ERP Protocol Tuning parameters explanation: •
Switch behavior [Revertive/Not Revertive]: revert or not to the main resource when failure clears.
•
Wait Time to Restore [0..12 Minutes in step of 1 minute]: meaningful only in case the swicthing behavior is revertive, is the time the main resource must be free of failures before reverting to. Hold-Off time [0..1000 millisec in step of 10 millisec]: time to wait, after failure detection, before starting protection in order to see if other protection recovers the failure Guard Time [10..2000 millisec in step of 10 millisec]: during guard time RPL owner discards the received R-APS OAM frames. It s started according to the ERP state machine specifications (see ERP specifications for more details)
•
•
.................................................................................................................................................................................................................................... 1350 OMS 20-10 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Network Configuration
Network Configuration
....................................................................................................................................................................................................................................
Network Configuration Network Configuration PBB Introduction
PBB is a type of Bridge domain: No specific PBB provisioning attributes is necessary. Control protocol is ERP. Inside PBB domain there are no Provider Bridge NEs. Control protocol is based on ERP only. In theory there could be a mix of xSTP (Spanning Tree Protocol) and ERP.
.................................................................................................................................................................................................................................... 1350 OMS 20-11 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Network Configuration
PBB Domain Create
....................................................................................................................................................................................................................................
PBB Domain Create When to use
The scope of this procedure is to create a PBB Domain. In Connection Less Networks, the Domain represents an homogeneous set of Network Elements dedicated to MAC, Virtual Provider or Provider Backbone Bridging. Related Information
A Domain is a distributed infrastructure made of NE, External-Network (aka virtual NE), Transport Links and Edge Ports managed together to supply a Connection Less infrastructure. Its main properties are the domain type (ETS, Bridge, T-MPLS), bridge type (MAC, Virtual, Provider or Provider Backbone Bridge) and the Control Plane Type (ERP, STP, RSTP, PVSTP, MSTP or none) The list of possible Control protocols depends on the selected Bridge Type. In case of PBB the only possible choice for Control Protocol is ERP. Before you begin
This task does not have any preconditions. Task ...................................................................................................................................................................................................
1
From the main menu bar select Actions > Packet > Construction > Create Domain. Figure 20-2 Actions>Packet>Construction>Create Domain
.................................................................................................................................................................................................................................... 1350 OMS 20-12 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Network Configuration
PBB Domain Create
....................................................................................................................................................................................................................................
Result: The Create PBB Domain window is displayed. ...................................................................................................................................................................................................
2
In the Create PBB Domain window enter following data: •
User Label : a friendly name identifying the Domain
•
Domain Type: select the value Bridge
•
Bridge Type: select the value PBB
•
Control Protocol Type: select the value ERP
•
Reserved B-VIDs for ERP: insert a range
Click Apply or OK button to confirm the operation. Figure 20-3 Create PBB Domain
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-13 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Network Configuration
Define NE
....................................................................................................................................................................................................................................
Define NE When to use
The scope of this procedure is to assign a Network Element to PBB domain. Related Information
This procedure applies to all NEs belonging to PBB domain. Before you begin
This task does not have any preconditions. Task ...................................................................................................................................................................................................
1
Issue a search of the NEs available following the path Search > Packet > Construction > Network Elements > Available NEs. Figure 20-4 Search>Packet>Construction>Network Elements>Available NEs
...................................................................................................................................................................................................
2
The list of the available NEs is displayed.
.................................................................................................................................................................................................................................... 1350 OMS 20-14 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Network Configuration
Define NE
....................................................................................................................................................................................................................................
Select the involved Network Element and follow the path Actions > Define Network Element from the popup menu. Figure 20-5 Available NE: Actions>Define Network Element
Result: The Define Network Element window is displayed. ...................................................................................................................................................................................................
3
Enter or select following data: •
User Label: a friendly name for the Network Element to be defined.
•
Working Mode: select PBB
•
STP type: select disabled
Click Apply or OK to confirm the operation. Figure 20-6 Define Network Element dialog box
...................................................................................................................................................................................................
4
From the main menu bar select Search> Packet > Construction > Network Elements > Defined NEs.
.................................................................................................................................................................................................................................... 1350 OMS 20-15 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Network Configuration
Define NE
....................................................................................................................................................................................................................................
The list of the defined NEs is displayed. Figure 20-7 Defined NE list
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-16 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provisioning
Provisioning hardware reference
....................................................................................................................................................................................................................................
Provisioning Provisioning hardware reference When to use
The scope of this procedure is to give a reference for port create. For more detail refer to the equipment User Provisioning Guide Related Information
The involved NEs are defined in PBB domain. Before you begin
Insert the port terminations in the correct position. Task ...................................................................................................................................................................................................
1
Once 1850 TSS is supervised, navigation to the ZIC GUI management application is allowed selecting the TSS Network Element in the list and from the popup menu Search > Show Equipment
Access the Show Equipment view of the originating NE. Figure 20-8 Show Equipment view
.................................................................................................................................................................................................................................... 1350 OMS 20-17 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provisioning
Provisioning hardware reference
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
2
In the Show Equipment, navigate the left-h-side tree and select the termination. The physical real image is shown in the right-h-side after bar down scrolling. Figure 20-9 Show Equipment: select the termination
...................................................................................................................................................................................................
3
Click twice on the termination. In the right-hand box click Save to confirm. Figure 20-10 Module setting
.................................................................................................................................................................................................................................... 1350 OMS 20-18 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provisioning
Provisioning hardware reference
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
Access the Show Equipment view of the terminating NE. The module setting is the same as above described for the originating NE. Figure 20-11 Show Equipment view of the terminating NE
...................................................................................................................................................................................................
5
From the Node list select the node involved in hardware recent change and follow the path Actions > Physical > Synchronize > Synchronize NE Figure 20-12 Node: Actions>Physical>Synchronize>Synchronize NE
E................................................................................................................................................................................................... N D O F S T E P S .................................................................................................................................................................................................................................... 1350 OMS 20-19 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provisioning
Transport link
....................................................................................................................................................................................................................................
Transport link Transport link introduction
The transport infrastructure is named Transport Link. The Transport Link can be supported by: •
•
A TDM path. The link is called Link Over TDM. It carries directly Ethernet Segments, Tunnels or PWs. A Tunnel/PW. The link is called Link Over (T-)MPLS. A Link Over TDM or a Link Over Cable (Martini) carries it. An Ethernet cable. The link is called Link Over Cable.
•
A WDM link. The link is called Link Over WDM.
•
.................................................................................................................................................................................................................................... 1350 OMS 20-20 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provisioning
Create Ethernet Physical Connection
....................................................................................................................................................................................................................................
Create Ethernet Physical Connection When to use
The scope of this procedure is to create an Ethernet Physical Connection Related Information
The involved ports have already been provisioned. Before you begin
This task does not have any preconditions. Task ...................................................................................................................................................................................................
1
From the map view, select the nodes to connect and follow the path Actions > Physical > Create Physical Connection Figure 20-13 Actions>Physical>Create Physical Connection
Result: The Create Physical connection window is displayed. ...................................................................................................................................................................................................
2
Set the following attributes: •
Enter a User Label to identify the transport link.
•
Select Connection type equal to Ethernet
•
Choose the Transport Alarm Enabling Rule (On Definition)
•
Only for TDM, select Implement rule
•
Only for TDM, select allocation cost
.................................................................................................................................................................................................................................... 1350 OMS 20-21 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provisioning
Create Ethernet Physical Connection
....................................................................................................................................................................................................................................
Click Next button. Figure 20-14 Create Physical Connection
...................................................................................................................................................................................................
3
The second step is customized according to the “Connection Type” selected (here below Ethernet physical link creation window is shown): Only NEs with Ethernet Ports are proposed as possible choices to user.
.................................................................................................................................................................................................................................... 1350 OMS 20-22 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provisioning
Create Ethernet Physical Connection
....................................................................................................................................................................................................................................
Only free ports of selected NE and with rate compatible with the link rate are proposed as possible choices to user. •
Select the Physical Connection Rate of Ethernet link
•
Select the end nodes, if not already selected, click on A-node and Z-node empty box, then select the node from the selection list.
•
Select the end ports, by means of the usual selection mechanism.
Figure 20-15 Create> Physical Connection step2
...................................................................................................................................................................................................
4
Click OK or Apply to confirm the creation. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-23 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provisioning
Assign Link over Cable to PBB domain
....................................................................................................................................................................................................................................
Assign Link over Cable to PBB domain When to use
The scope of this procedure is to assign a Link over Cable to PBB domain. Related Information
The involved ports have already been provisioned. Before you begin
The Physical connection to assign has been created. Task ...................................................................................................................................................................................................
1
From the main menu bar follow the path Search > Packet > Construction > Transport Links > Links over Cable Figure 20-16 Search>Packet>Construction>Transport Links>Links over Cable
.................................................................................................................................................................................................................................... 1350 OMS 20-24 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provisioning
Assign Link over Cable to PBB domain
....................................................................................................................................................................................................................................
Result: The Links over Cable list is displayed. Figure 20-17 Links over Cable list
...................................................................................................................................................................................................
2
Select the Link over Cable to assign and follow the path Actions > Assign Resources to Domain Figure 20-18 Link over Cable: Actions>Assign Resources to Domain
Result: The Assign Resources to Domain window is displayed. ...................................................................................................................................................................................................
3
Click the selection list icon (right side of the window). From the list select the relevant PBB domain.
.................................................................................................................................................................................................................................... 1350 OMS 20-25 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provisioning
Assign Link over Cable to PBB domain
....................................................................................................................................................................................................................................
Click Apply or OK to confirm. Figure 20-19 Assign Resources to Domain
.................................................................................................................................................................................................................................... 1350 OMS 20-26 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provisioning
Assign Link over Cable to PBB domain
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
In the Link over Cable list you can verify that the relevant Link over Cable has the domain attribute accordingly. Figure 20-20 Link over Cable list
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-27 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provisioning
Assign Link over Cable to PBB domain
....................................................................................................................................................................................................................................
Delete Transport Link ...................................................................................................................................................................................................
1
Select the Link over Cable to delete in the list and follow the path from the popup menu Actions > Delete. Figure 20-21 Link over Cable:Actions>Delete
...................................................................................................................................................................................................
2
Select the related Physical Connection and follow the path from the popup menu Actions > Remove. Figure 20-22 Physical Connection:Actions>Remove
.................................................................................................................................................................................................................................... 1350 OMS 20-28 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provisioning
Assign Link over Cable to PBB domain
....................................................................................................................................................................................................................................
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-29 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP configuration
Create ERP Ring
....................................................................................................................................................................................................................................
ERP configuration Create ERP Ring When to use
The scope of this procedure is to configure major ring and sub-rings by selecting the links in the map. Related Information
This task does not have any related information. Before you begin
From the physical topology view (physical map) the user configures major ring and sub-rings by selecting the links in the map. Task ...................................................................................................................................................................................................
1
From the main menu bar follow the path Actions > Packet > ERP > Create ERP Ring. Figure 20-23 Actions>Packet>ERP>Create ERP Ring
...................................................................................................................................................................................................
2
In the Create ERP window enter or select following data: • •
ERP User Label Ring type : select Major or Subring
•
Activation status [active/not active] : this value is used to enable or disable the ERP protocol.
.................................................................................................................................................................................................................................... 1350 OMS 20-30 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP configuration
Create ERP Ring
....................................................................................................................................................................................................................................
With the usual selection mechanism, select the PBB domain. Figure 20-24 Create ERP Ring
...................................................................................................................................................................................................
3
Select the Transport Links to associate to ERP ring. Click the selection icon, the following list is displayed. Select all Transport Links.
.................................................................................................................................................................................................................................... 1350 OMS 20-31 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP configuration
Create ERP Ring
....................................................................................................................................................................................................................................
Note: The multiple selection is allowed by means of the mouse small wheel. Figure 20-25 Bridge Transport Links
Click OK to confirm the selection. ...................................................................................................................................................................................................
4
The selected Transport Links are now displayed in the Create ERP Ring main window.
.................................................................................................................................................................................................................................... 1350 OMS 20-32 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP configuration
Create ERP Ring
....................................................................................................................................................................................................................................
Click OK to confirm the creation. Figure 20-26 Create ERP Ring
.................................................................................................................................................................................................................................... 1350 OMS 20-33 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP configuration
Create ERP Ring
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
5
To verify the successful creation follow the path Search > Packet > ERP > Rings Figure 20-27 Search>Packet>ERP>Rings
...................................................................................................................................................................................................
6
The list of the ERP Rings is shown below, containing the ERP ring which has been just created. Figure 20-28 List of ERP Rings
.................................................................................................................................................................................................................................... 1350 OMS 20-34 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP configuration
Create ERP Ring
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
7
Select the ring which has just been created and follow the path from the popup menu Actions > Implement ERP Ring Figure 20-29 ERP ring: Actions>Implement ERP Ring
...................................................................................................................................................................................................
8
The ERP Ring has been implemented. Figure 20-30 ERP Ring implemented
.................................................................................................................................................................................................................................... 1350 OMS 20-35 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP configuration
Create ERP Ring
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
9
From the ERP Ring you can search the nodes on the ring. Figure 20-31 ERP Ring:Search>Nodes
...................................................................................................................................................................................................
10
The list of the nodes belonging to the ring is displayed. Figure 20-32 Nodes belonging to the ring
...................................................................................................................................................................................................
11
From the ERP Ring you can search the physical links belonging to the ring. Figure 20-33 ERP Ring:Search>Physical Links
.................................................................................................................................................................................................................................... 1350 OMS 20-36 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP configuration
Create ERP Ring
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
12
The list of the physical connections belonging to the ring is displayed. Figure 20-34 Physcons belonging to the ring
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-37 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP configuration
Create an ERP Instance
....................................................................................................................................................................................................................................
Create an ERP Instance When to use
The scope of this procedure is to create an ERP instance. Related Information
The ERP ring has been configured and implemented. Before you begin
The ERP ring has been configured and implemented Task ...................................................................................................................................................................................................
1
Before creating a new instance, it is opportune to search the existing instances on the involved ring. On the same ERP ring many instances can be created, according to the customer traffic needs. Select the ERP ring in the list and follow the path on the popup menu Search > ERP Instances. Figure 20-35 ERP ring: Search>ERP Instances
...................................................................................................................................................................................................
2
A search of the ERP instances can be done also fro Show Equipment of an involved NE.
.................................................................................................................................................................................................................................... 1350 OMS 20-38 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP configuration
Create an ERP Instance
....................................................................................................................................................................................................................................
Select folder Ethernet Ring protection. Figure 20-36 Search of the ERP instances
ERP 1 has 2 instances, one per port and one per VLAN. ERP2 has no instance. ...................................................................................................................................................................................................
3
The user can display the ERP Instances for a PBB domain. Select the PBB domain in the domain list and follow the path on the popup menu Search > ERP Instances. Figure 20-37 PBB domain:Search>ERP Instances
.................................................................................................................................................................................................................................... 1350 OMS 20-39 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP configuration
Create an ERP Instance
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
From the main menu bar follow the path Actions > Packet > ERP > Create ERP Instance Figure 20-38 Actions>Packet>ERP>Create ERP Instance
...................................................................................................................................................................................................
5
The Create ERP Instance window is displayed. Folder General is already selected. Enter instance User Label and select the following attributes: • • • • • •
R-APS VLAN ID Insert a value between 1 and 4093, the value is unique per ring or
group of interconnected rings R-APS PCP [0..7] this is the priority bits value for R-APS. Maintenance Entity Level [0..7] this is an integer value indicating the OAM level
assigned to R-APS- ring autoprotection switch. Scope of ERP instance . You can select per port or per VLAN PBB domain. Select the target PBB domain. ERP Ring: the ring to which the instance will be applied.
.................................................................................................................................................................................................................................... 1350 OMS 20-40 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP configuration
Create an ERP Instance
....................................................................................................................................................................................................................................
• •
RPL (ring protection link) Owner It is the NE that has the master role on ERP instance RPL (East/west link that is Blocked by RPL owner in nominal conditions)
Figure 20-39 Create ERP Instance: General
...................................................................................................................................................................................................
6
Select folder Timers and proceed with Protocol Tuning: • •
Switch behavior [Revertive/Not Revertive] : revert or not to the main resource when failure clears Wait Time to Restore [0..12 Minutes,steps of 1] : meaningful only in case the swicthing behavior is revertiv. It is the time the main resource must be free of failures before reverting to.
.................................................................................................................................................................................................................................... 1350 OMS 20-41 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP configuration
Create an ERP Instance
....................................................................................................................................................................................................................................
• •
Hold-Off time [0..1000 millisec, steps of 10]: time to wait, after failure detection, before starting protection in order to see if other protection recovers the failure. Guard Time [10..2000 millisec, steps of 10] : during guard time RPL owner discards the received R-APS OAM frames. It is started according to the ERP status state.
Figure 20-40 Create ERP Instance: Timers
...................................................................................................................................................................................................
7
Select folder Failures Optional Alarms that can be included/excluded in the list of Switch Criteria: • • • •
Signal Degrade Partial Loss of Capacity (if ring ports are LAG) Loss Of Continuity (CCM) defect Link OAM Critical Events
.................................................................................................................................................................................................................................... 1350 OMS 20-42 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP configuration
Create an ERP Instance
....................................................................................................................................................................................................................................
Note: If Loss of Continuity defect or Link OAM Critical Events are used as Switch Criteria it is necessary to assign Down MEPs to Ring Ports (on all the NEs inside the ring) Figure 20-41 Create ERP Instance: Failures
.................................................................................................................................................................................................................................... 1350 OMS 20-43 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP configuration
Create an ERP Instance
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
8
In the Create ERP Instance wizard, click Apply or OK to confirm the creation. Figure 20-42 Create ERP Instance
...................................................................................................................................................................................................
9
Select the ERP Instance and follow the path on the popup menu Actions > Implement ERP Instance Figure 20-43 ERP Instance: Actions>Implement ERP Instance
.................................................................................................................................................................................................................................... 1350 OMS 20-44 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP configuration
Create an ERP Instance
....................................................................................................................................................................................................................................
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-45 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Backbone VLAN ID
B-VID configuration
....................................................................................................................................................................................................................................
Backbone VLAN ID B-VID configuration When to use
The scope of this procedure is to define a B-VID in a PBB domain and to associate it to the ERP instance: The B-VID is the VLAN. Related Information
The related descriptions are contained in the previous procedures. Before you begin
The configuration of NEs, Transport Links, ERP ring, ERP Instance has been previously completed with success. Task ...................................................................................................................................................................................................
1
From the main menu bar follow the path Actions > Packet > Services > ConnectionLess(Bridge) > Create B-VID Figure 20-44 Actions>Packet>Services>ConnectionLess(Bridge)>Create B-VID
...................................................................................................................................................................................................
2
In the B-VID creation wizard window enter or select following data: •
User Label. Enter the userlabel to identify the B-VID.
•
Domain. Select the domain.
.................................................................................................................................................................................................................................... 1350 OMS 20-46 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Backbone VLAN ID
B-VID configuration
....................................................................................................................................................................................................................................
• •
•
VLAN ID. Select a unique number.
VLAN distribution You can select: – Manual. In this case the user will specify all relevant Transports Links. – Domain Wide. In this case the VLAN is distributed over all Transport Links of all rings belonging to the Domain. Select Manual.
Click ERP. Select the ERP ring to which the B-VID is to be assigned. Select the ERP instance. The selected ERP instance is now contained in the bottom box. Figure 20-45 Create B-VID wizard step1
...................................................................................................................................................................................................
3
Click Transport Links.
.................................................................................................................................................................................................................................... 1350 OMS 20-47 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Backbone VLAN ID
B-VID configuration
....................................................................................................................................................................................................................................
Select the Transport/s to which the B-VID is assigned Figure 20-46 B-VID:Transport Links selection
.................................................................................................................................................................................................................................... 1350 OMS 20-48 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Backbone VLAN ID
B-VID configuration
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
After selecting all ERP and Transport Links, click Apply or OK to confirm the creation. Figure 20-47 Create B-VID
...................................................................................................................................................................................................
5
To verify the successful creation, from the main menu bar follow the path Search > Packet > Services > Connection Less(Bridge) > B-VIDs ...................................................................................................................................................................................................
6
The B-VID list is displayed, containing the B-VID which has been just created (status = defined).
.................................................................................................................................................................................................................................... 1350 OMS 20-49 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Backbone VLAN ID
B-VID configuration
....................................................................................................................................................................................................................................
Select the B-VID which has been just created and follow the path from the popup menu Actions > Allocate. Figure 20-48 B-VID list
...................................................................................................................................................................................................
7
The B-VID Provisioning State changes to allocated. Select the B-VID from the list and follow the path from the popup menu Actions > Implement.. Figure 20-49 B-VID: Actions>Implement
.................................................................................................................................................................................................................................... 1350 OMS 20-50 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Backbone VLAN ID
B-VID configuration
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
8
The B-VID Provisioning State changes to implemented passing thorough intermediate status partially implemented. Figure 20-50 B-VID partially implemented (few secs)
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-51 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management EVC-EVPLAN Service in PBB/ERP
Additional Info on PBB/ERP Service
....................................................................................................................................................................................................................................
EVC-EVPLAN Service in PBB/ERP Additional Info on PBB/ERP Service When to use
The scope of this procedure is to define Additional Info on PM, QoS and Managing Traffic Descriptor. Related Information
Refer to“PBB Ethernet Virtual Connection” (p. 20-7) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Additional Info on PM ...................................................................................................................................................................................................
1
MEG (maint-entity-grp) is characterized by: •
MEG Identifier: made by a Format and a Name. Format can be (to be confirmed by NE which will be implemented).
• • • • •
String Dns-Like Name MAC Address integer Associated Maintenance Domain
•
MIP creation policy [none, All points, Lower-level MEP exists]: which policy is used inside MEG for MIP Creation. Default is inherited from Maintenance Domain. See next step. CC Interval [1 sec(Default), 10 sec, 1 min, 10 min] (interval between CCM PDUs) CC Priority [0..7]( Class-of-Service to be used for CCM PDU). The Monitored Resource is automatically determined by NMS from domain type: in case of PBB.
• • • •
S-VLAN in case of Provider Bridge. C-VLAN in case of Virtual Bridge.
.................................................................................................................................................................................................................................... 1350 OMS 20-52 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management EVC-EVPLAN Service in PBB/ERP
Additional Info on PBB/ERP Service
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
2
MIP creation policy can be illustrated by an example: •
MEG#1, MEG#2, MEG#3 all refers to a given EVC.
• •
MEG#3 is created with “none”, so no MIPs are created. MEG#2 is created with “All points”, so MIPs are created in all the points (ports) where the EVC is passing through. MEG#1 is created with “Lower-level MEP exists”, so MIPs are present only where MEP of MEG#2 and MEG#3 are present.
•
Figure 20-51 MIP creation policy
...................................................................................................................................................................................................
3
For each EVC termination the user defines the traffic classification rules by associating a Traffic Classifier and QoS attributes. Traffic Classifier allows to specify classification rules based on: •
VLAN (single or range)
• • •
Priority bit (single or range) IP DSCP (single or range) Payload type
• • •
QoS attributes are: Policing mode [color blind, color aware, none] Colour profile (applicable if policing mode is color blind or color aware) CoS and bandwidth profile are specified associating a Traffic Descriptor
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-53 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management EVC-EVPLAN Service in PBB/ERP
Additional Info on PBB/ERP Service
....................................................................................................................................................................................................................................
QoS – Managing Traffic Descriptor
The Traffic Descriptor describes the characteristics of an Ethernet segment in term of Class of Service (CoS) and bandwidth. ...................................................................................................................................................................................................
1
Another step towards the MEF alignment is provided by possibility to display bandwidth parameters following both IETF definitions (as already available) and MEF definitions. For reminder, the following definitions are applicable for IETF: CIR, PIR, PBS, CBS while the following one are applicable for MEF: CIR, EIR, CBS, EBS. The existing relationships are described as in the following: • •
EIR = PIR – CIR. EBS = PBS – CBS.
Figure 20-52 Traffic Descriptor create step1
...................................................................................................................................................................................................
2
The range of the supported classes of service (CoS, also named forwarding classes) is extended from the basic set (best effort, regulated and guaranteed) to the enhanced set (best effort and background, four types of regulated, two types of guaranteed).
.................................................................................................................................................................................................................................... 1350 OMS 20-54 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management EVC-EVPLAN Service in PBB/ERP
Additional Info on PBB/ERP Service
....................................................................................................................................................................................................................................
The frame association to a CoS is performed at the ingress port. Differentiated quality of service (QoS) management is implemented mapping each CoS to a specific output queue at the egress port. Color management allows also frame prioritization within a given forwarding class. The frame per hop behavior (PHB) is therefore implemented by CoS and color management. Figure 20-53 Traffic Descriptor create step2
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-55 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management PBB EVC Termination Management
Add PBB EVC Termination
....................................................................................................................................................................................................................................
PBB EVC Termination Management Add PBB EVC Termination When to use
This function consists in adding terminations to a implemented PBB EVC. Related Information
For information about PBB EVC, Refer to “PBB Ethernet Virtual Connection” (p. 20-7) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the Bridge EVC list select the EVC to which a termination must be added and follow the path on the popup menu Search > EVC Termination.. The list of the terminations is displayed. Figure 20-54 EVC Termination list
.................................................................................................................................................................................................................................... 1350 OMS 20-56 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management PBB EVC Termination Management
Add PBB EVC Termination
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
2
From the Bridge EVC list select the EVC to which a termination must be added and follow the path on the popup menu Actions > Add Connection Less EVC Termination.. Figure 20-55 Actions> Add Connection Less EVC Termination
...................................................................................................................................................................................................
3
In the Add Connection Less EVC Termination window the EVC is already selected.
.................................................................................................................................................................................................................................... 1350 OMS 20-57 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management PBB EVC Termination Management
Add PBB EVC Termination
....................................................................................................................................................................................................................................
By means of the usual selection mechanism select the Network Element and the Edge Port to add. Figure 20-56 Add Connection Less EVC Termination dialog box
Click OK/Apply to confirm. ...................................................................................................................................................................................................
4
To verify that the new termination has been added successfully, refresh the EVC Terminations list. The new termination is displayed. Figure 20-57 The new termination has been added
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-58 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management PBB EVC Termination Management
Remove PBB EVC Termination
....................................................................................................................................................................................................................................
Remove PBB EVC Termination When to use
This function consists in removing terminations to a implemented PBB EVC. Related Information
For information about PBB EVC, Refer to“PBB Ethernet Virtual Connection” (p. 20-7) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the EVC Termination list select the termination to remove and issue the pop-up menu Actions> Delete. ...................................................................................................................................................................................................
2
A confirmation box is presented. Click OK to confirm the delete operation. Result: The termination is removed and no longer present. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-59 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
Overview
....................................................................................................................................................................................................................................
Provider Backbone Bridge EVC Management Overview Purpose
This section describes how to manage Provider Backbone Bridge EVC. Contents View the PBB EVC list
20-61
Description of the list of PBB EVCs
20-62
Create PBB EVC
20-63
Allocate PBB EVC
20-65
Deallocate PBB EVC
20-67
Implement PBB EVC
20-68
Deimplement PBB EVC
20-70
Add Termination on implemented PBB EVC
20-71
Remove Termination on implemented EVC
20-72
Configure PBB EVC
20-73
Bridge Flows of PBB EVC
20-74
PBB EVC Broadcast Domain Containment
20-76
Enable Broadcast Domain Containment
20-77
Disable Broadcast Domain Containment
20-78
Automatic association UNI port - default VT
20-79
Manual association UNI port - user VT
20-80
Configuration of the DEI bit
20-81
.................................................................................................................................................................................................................................... 1350 OMS 20-60 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
View the PBB EVC list
....................................................................................................................................................................................................................................
View the PBB EVC list When to use
The PBB Ethernet Virtual Connection List window presents all the PBB EVCs and their attributes. Related Information
For information about PBB EVC, Refer to “PBB Ethernet Virtual Connection” (p. 20-7) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The menu of the Services is shown. ...................................................................................................................................................................................................
2
Select Connection Less (Bridge) > Bridge EVCs. Result: The list window is displayed.
See the following topic in this document: “Description of the list of PBB EVCs” (p. 20-62) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-61 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
Description of the list of PBB EVCs
....................................................................................................................................................................................................................................
Description of the list of PBB EVCs Attributes of a PBB EVC
The attributes displayed for each EVC are: •
User Label.
•
Ethernet Service User Label.
•
Topology (Point to point, Routed multi-point, Any to any).
•
Service Type.(EVPL, EPL, EVPLAN, Broadcast).
•
Traffic Type (Unicast, Multicast).
•
Domain Type.(Backbone)
•
Working State (Normal, Configuring, Allocating, De-allocating, Implementing, De-implementing, Commissioning, De-commissioning, Termination adding, Termination removing, Constraint adding, Constraint removing, removing).
•
Provisioning State (Defined, Partially allocated, Allocated, Partially implemented, Implemented, Commissioned).
•
Service State.(In Service, Not In service)
•
Availability Status (Normal, Degraded, In Failure, Not Meaningful).
•
B-VID
•
Broadcast Domain Containment (Enabled, Disabled)
.................................................................................................................................................................................................................................... 1350 OMS 20-62 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
Create PBB EVC
....................................................................................................................................................................................................................................
Create PBB EVC When to use
The function creates a PBB Ethernet Virtual Connection. Related Information
The user specifies the characteristics of the EVC (userlabel, type, terminations, flows, etc.) and, in addition: • • •
I-VID I-SID Broadcast Domain Containment. (Enabled, Disabled). Refer to “PBB EVC Broadcast Domain Containment” (p. 20-76)
The specified B-VID must: •
exist;
• •
be in the Domain specified for the EVC; have been created by the operator (B-VIDs created by ERP BB are not allowed).
The I-SID must not have been already used by another EVC in the same Domain. The allowed values for the Resource Sharing attribute are FULL or PRIVATE UNI. The allowed types for a PBB EVC are: •
EPL
•
EVPL
•
EPLAN
•
EVPLAN
•
BROADCAST
If the specified B-VID has a non empty I-SID Bundle, the I-SID specified for the EVC must be within that bundle. The creation of the EVC is similar to the creation of PB EVC, except for the fact that the association between the EVC, I-SID and B-VID is stored. For information about PBB EVC, Refer to“PBB Ethernet Virtual Connection” (p. 20-7). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode.
.................................................................................................................................................................................................................................... 1350 OMS 20-63 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
Create PBB EVC
....................................................................................................................................................................................................................................
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Action > Packet > Services. Result: The menu of the Services is shown. ...................................................................................................................................................................................................
2
Select Connection Less (Bridge) > Create PBB EVC. See workflow “Create a PBB EVC” (p. 20-144) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-64 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
Allocate PBB EVC
....................................................................................................................................................................................................................................
Allocate PBB EVC When to use
To allocate a PBB EVC Related Information
The allocation of a PBB EVC is possible only if the B-VID is at least allocated and is rejected in all other cases (i.e. when the B-VID is defined). In no case, a PBB EVC can have an EVC Termination on one NE that is not embraced by it's B-VID (either through a TL or through a ring). In other words: if no TL or ring associated to a B-VID reaches/crosses a NE, the latter can't host any EVC Termination served by that B-VID. Since no private use of Transport Links is allowed (Resource Sharing only admitted values are FULL and PRIVATE UNI), no check on Transport Links sharing is performed. The allocation, that for the most part (EVC Terminations and Flows) is identical to the one of a PB EVC, specifically concerns: •
the allocation of the association between each Port supporting an EVC Termination and the I-SID
•
the allocation of the association between the B-VID, the I-SID and all the NNIs, belonging to NEs where there are EVC Terminations, associated to the B-VID of the EVC; for each flow, the allocation of a cross connection that has, as a server at one side, the I-SID; if the EVC is under OAM, the I-SID has to be distributed also in all the places where the B-VID is.
• •
For information, Refer to“PBB Ethernet Virtual Connection” (p. 20-7). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the menu path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs.
.................................................................................................................................................................................................................................... 1350 OMS 20-65 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
Allocate PBB EVC
....................................................................................................................................................................................................................................
Result: The Bridge EVC list window is displayed. ...................................................................................................................................................................................................
2
Select the EVC in the list and follow the path Action > Bridge EVC > Allocate. ...................................................................................................................................................................................................
3
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: The EVC is allocated.
The Provisioning State is changed to Allocated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-66 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
Deallocate PBB EVC
....................................................................................................................................................................................................................................
Deallocate PBB EVC When to use
To deallocate PBB EVC. Related Information
The deallocation, that for the most part (EVC Terminations and Flows) is identical to the one of a PB EVC, specifically concerns: • • •
the deallocation of the associations between the Ports of the EVC Terminations and the I-SID; the deallocation of the associations between the B-VID, the I-SID and the NNIs associated to the B-VID of the EVC; if the EVC is under OAM, its I-SID has to be un-distributed also in all the places where the B-VID has been.
For information, Refer to“PBB Ethernet Virtual Connection” (p. 20-7). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the menu path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. Result: The Bridge EVC list window is displayed. ...................................................................................................................................................................................................
2
Select the EVC in the list and follow the path Action > Bridge EVC > Deallocate. ...................................................................................................................................................................................................
3
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: The EVC is deallocated.
The Provisioning State is changed to Defined. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-67 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
Implement PBB EVC
....................................................................................................................................................................................................................................
Implement PBB EVC When to use
To implement PBB EVC. Related Information
The implementation of a PBB EVC is possible only if the B-VID is implemented and is rejected in all other cases (included partially implemented B-VID). The implementation, that for the most part (EVC Terminations and Flows) is identical to the one of a PB EVC, specifically concerns: • •
•
•
the implementation of the association between each Port supporting an EVC Termination and the I-SID (opticsIMPbbInstanceTable); the implementation of the association between the B-VID, the I-SID and all the NNIs, belonging to NEs where there are EVC Terminations, associated to the B-VID of the EVC (opticsIMPbbInstanceTable); for each flow, the implementation of a cross connection that has as a server at one side the I-SID (i.e. opticsIMETSInFlowServiceType = PBB and opticsIMETSInFlowServiceID = index of row of opticsIMPbbInstanceTable for the I-SID, for either opticsIMETSInFlowTable or opticsIMETSOutFlowTable); if the EVC is under OAM, the I-SID has to be distributed also in all the places where the B-VID is.
For information: Refer to“PBB Ethernet Virtual Connection” (p. 20-7). Refer to “PBB EVC provisioning” (p. 20-8). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the menu path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. Result: The Bridge EVC list window is displayed. ...................................................................................................................................................................................................
2
Select the EVC in the list and follow the path Action > Bridge EVC > Implement.
.................................................................................................................................................................................................................................... 1350 OMS 20-68 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
Implement PBB EVC
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
3
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: The EVC is implemented.
The Provisioning State is changed to Implemented. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-69 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
Deimplement PBB EVC
....................................................................................................................................................................................................................................
Deimplement PBB EVC When to use
To deimplement PBB EVC. Related Information
The deimplementation, that for the most part (EVC Terminations and Flows) is identical to the one of a PB EVC, specifically concerns: • •
•
the deimplementation of the association between each Port supporting an EVC Termination and the I-SID (opticsIMPbbInstanceTable); the deimplementation of the association between the B-VID, the I-SID and all the NNIs, belonging to NEs where there are EVC Terminations, associated to the B-VID of the EVC (opticsIMPbbInstanceTable); if the EVC is under OAM, its I-SID has to be un-distributed also in all the places where the B-VID has been.
For information, Refer to“PBB Ethernet Virtual Connection” (p. 20-7). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the menu path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. Result: The Bridge EVC list window is displayed. ...................................................................................................................................................................................................
2
Select the EVC in the list and follow the path Action > Bridge EVC > deimplement. ...................................................................................................................................................................................................
3
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: The EVC is deimplemented.
The Provisioning State is changed to Allocated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-70 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
Add Termination on implemented PBB EVC
....................................................................................................................................................................................................................................
Add Termination on implemented PBB EVC When to use
This function consists in adding terminations to a implemented PBB EVC. Related Information
Termination addition means I-SID distribution. In no case an EVC Termination can be added on a NE that is not used by the EVC's B-VID. In particular: • •
implementation of the association between the Termination's Port supporting and the I-SID (opticsIMPbbInstanceTable); (only if does not exist an implemented Termination of the same EVC in the same NE) implementation of the association between the B-VID, the I-SID and all the NNIs, belonging to the Termination's NE, associated to the B-VID of the EVC (opticsIMPbbInstanceTable).
For information, Refer to“PBB Ethernet Virtual Connection” (p. 20-7). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. ...................................................................................................................................................................................................
2
Select the EVC in the list where the termination must be added. ...................................................................................................................................................................................................
3
Select the path Action > Bridge EVC > Add Connection Less EVC Termination. Result: The Add Termination window is displayed. ...................................................................................................................................................................................................
4
Click Ok. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-71 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
Remove Termination on implemented EVC
....................................................................................................................................................................................................................................
Remove Termination on implemented EVC When to use
This function consists in removing terminations to an implemented PBB EVC. Related Information
Termination removal means undo of I-SID distribution. In no case an EVC Termination can be added on a NE that is not used by the EVC's B-VID. In particular: • •
deimplementation of the association between the Termination's Port supporting and the I-SID (opticsIMPbbInstanceTable); (only if this is the last implemented Termination of the same EVC in the same NE) deimplementation of the association between the B-VID, the I-SID and all the NNIs, belonging to the Termination's NE, associated to the B-VID of the EVC (opticsIMPbbInstanceTable).
For information about PBB EVC, Refer to“PBB Ethernet Virtual Connection” (p. 20-7). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. ...................................................................................................................................................................................................
2
Select the EVC in the list where the termination must be removed. ...................................................................................................................................................................................................
3
Select the path Action > Bridge EVC > Remove Connection Less EVC Termination. ...................................................................................................................................................................................................
4
Click Ok. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-72 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
Configure PBB EVC
....................................................................................................................................................................................................................................
Configure PBB EVC When to use
This function changes attributes of PBB EVC. Related Information
For information, Refer to“PBB Ethernet Virtual Connection” (p. 20-7). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. ...................................................................................................................................................................................................
2
Select the PBB EVC in the list . ...................................................................................................................................................................................................
3
Select the path Action > Bridge EVC > Configure PBB EVC. Result: The Configuration window is displayed. The user can change:
• •
EVC. Traffic descriptor.
...................................................................................................................................................................................................
4
Click Ok. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-73 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
Bridge Flows of PBB EVC
....................................................................................................................................................................................................................................
Bridge Flows of PBB EVC When to use
This function shows bridge flows of a PBB EVC. Related Information
For information, Refer to“PBB Ethernet Virtual Connection” (p. 20-7). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. ...................................................................................................................................................................................................
2
Select the PBB EVC in the list . ...................................................................................................................................................................................................
3
Select the path Action > Bridge EVC > Bridge Flows. Result: The List Bridge Flow is displayed.
• • – – –
EVC Bridge Ingress Flows Id Network Element Edge Port
– – –
Policy Mode Traffic Descriptor Color Profile
– – •
VLAN Pop Classification Bridge Egress Flows
– – –
Id Network Element Edge Port
.................................................................................................................................................................................................................................... 1350 OMS 20-74 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
Bridge Flows of PBB EVC
....................................................................................................................................................................................................................................
– –
Class Of Service VLAN Id
– – –
Priority Mode Green Priority Yellow Priority
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-75 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
PBB EVC Broadcast Domain Containment
....................................................................................................................................................................................................................................
PBB EVC Broadcast Domain Containment Definition
Broadcast domain containment is implemented through the provisioning of I-SID instances also in intermediate nodes. Algorithm to determine the involved NEs and ports in a broadcast domain containment for an EVC: •
• •
get all the EVC Terminations and determine the paths between each pair of them (in other words: given a pair of EVC Terminations, determine a path between them (inside the involved B-VID, of course), in terms of the rings and/or single TLs that must be crossed to reach one from the other); enrich the set of rings and TLs, determined at the previous step, by adding all the main rings for any sub-ring that is already included in the set; take all the NEs of the rings and TLs of the set and provision the I-SID there (if not yet provisioned because of an EVC Termination) associating to it the NNI ports of the involved B-VID in that NE that are linked to another NE of the set.
Broadcast domain containment provisioning is alternative to I-SID for OAM provisioning: if broadcast domain containment is enabled no I-SID for OAM is provisioned.
.................................................................................................................................................................................................................................... 1350 OMS 20-76 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
Enable Broadcast Domain Containment
....................................................................................................................................................................................................................................
Enable Broadcast Domain Containment When to use
This function activates the broadcast domain containment on an EVC , regardless of EVC Provisioning State. Related Information
The operator may enable the broadcast domain containment on an EVC by simply invoking the modify (in case of defined or allocated EVC) or the configure (in all other cases) of the EVC. Within the form of modify/configure the operator is able to change the Broadcast Domain Containment attribute from "Disabled" to "Enabled". If the EVC is in defined or allocated state, the impacts are only within the PKT (i.e. DB). If the EVC is in implemented state, the impacts are both on DB and on the involved NEs. Refer to“PBB EVC Broadcast Domain Containment” (p. 20-76). If the EVC is under OAM, the I-SID modifications/provisioning for broadcast domain containment replace the ones existing for OAM. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. ...................................................................................................................................................................................................
2
Select The EVC in the list ...................................................................................................................................................................................................
3
Select the path Action > Bridge EVC> Modify. ...................................................................................................................................................................................................
4
Select the tab Details and set Enable Broadcast Domain Containment to Enabled. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-77 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
Disable Broadcast Domain Containment
....................................................................................................................................................................................................................................
Disable Broadcast Domain Containment When to use
This function deactivates the broadcast domain containment on an EVC , regardless of EVC Provisioning State. Related Information
The operator may disable the broadcast domain containment on an EVC by simply invoking the modify (in case of defined or allocated EVC) or the configure (in all other cases) of the EVC. Within the form of modify/configure the operator is able to change the Broadcast Domain Containment attribute from "Enabled" to "Disabled". If the EVC is in defined or allocated state, the impacts are only within the PKT (i.e. DB). If the EVC is in implemented state, the impacts are both on DB and on the involved NEs. Refer to “PBB EVC Broadcast Domain Containment” (p. 20-76). If the EVC is under OAM, the I-SID situation on DB/NE is restored as if on the EVC was just put under OAM. This is needed since previous broadcast domain containment enabling could have removed some of the I-SID instances on some NE and modified other ones. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. ...................................................................................................................................................................................................
2
Select The EVC in the list ...................................................................................................................................................................................................
3
Select the path Action > Bridge EVC> Modify. ...................................................................................................................................................................................................
4
Select the tab Details and set Enable Broadcast Domain Containment to Disabled. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-78 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
Automatic association UNI port - default VT
....................................................................................................................................................................................................................................
Automatic association UNI port - default VT Automatic association of the default VT to an EVC Termination
At EVC definition time, by default, the EVC termination is associated to the default VT, only for those cards that support VT management. The operator can specify at EVC definition time or modify at EVC configuration time, the reserved bandwidth (ISID-CIR/ISID-PIR) associated to a given EVC termination. If the reserved bandwidth (ISID-CIR/ISID-PIR) has been not specified by operator at EVC definition time, then the system assumes: •
ISID-CIR = 0
•
ISID-PIR = VT-PR
At allocation time, each egress I-SID is automatically associated to the default VT of the ETS-P UNI interface. When a PBB EVC is allocated, the reserved VT-CR of the default VT is automatically increased by an amount equal to: ISID-CIR The reserved VT-PR of the default VT is automatically updated to take into account the contribution of: ISID-PIR For the default VT, VT-CR, VT-Reserved-CR, VT-PR and VT-Reserved-PR are automatically computed according to ANY aggregation criterion in Table 2 of PKT 9.1 QOS Management Technical Functional Specification.
.................................................................................................................................................................................................................................... 1350 OMS 20-79 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
Manual association UNI port - user VT
....................................................................................................................................................................................................................................
Manual association UNI port - user VT Manual association of the user VT to an EVC Termination
The operator is allowed to manually define (during EVC definition) or modify (during EVC configuration) the association between the I-SID and the VT at the ETS-P UNI (i.e. the association between an EVC Termination and a VT). The operator has to specify at EVC definition time and can modify at EVC configuration time, the reserved bandwidth (ISID-CIR/ISID-PIR) associated to a given EVC termination. By default, the system assumes that: •
ISID-CIR = 0
•
ISID-PIR = VT-PR
The system checks that the required bandwidth is available on the user VT. When a PBB EVC is allocated, the reserved VT-CR of the user VT is automatically increased by an amount equal to: •
ISID-CIR
The reserved VT-PR of the user VT is automatically updated to take into account the contribution of: •
ISID-PIR
For the user VT, VT-Reserved-CR and VT-Reserved-PR are automatically computed according to the following parameters checks: •
VT-CR >= VT-Reserved-CR = ΣFixed-VT ISID-CIRi , over all ISID using the VT.
•
VT-PR>= VT-Reserved-PR = Max (ISID-PIRi) , over all ISID using the VT.
.................................................................................................................................................................................................................................... 1350 OMS 20-80 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Provider Backbone Bridge EVC Management
Configuration of the DEI bit
....................................................................................................................................................................................................................................
Configuration of the DEI bit Configuration of the DEI bit support on PBB NNI ports
The operator specifies a PBB NNI port (PNP client type) and tells whether he wants to activate or deactivate the DEI bit support. The system configures the port accordingly. Activating the DEI bit support means that from that port will be possible to manage 8 CoS each with two colors (green and yellow), thus giving a different meaning to the PCP attribute on the same port: 8P0D means, in fact, 8P8D. Activating the DEI bit is meaningful (and useful) only for PCP = 8P0D .
.................................................................................................................................................................................................................................... 1350 OMS 20-81 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Overview
....................................................................................................................................................................................................................................
B-VID Management Overview Purpose
This section describes how to manage B-VID. Contents View the B-VID list
20-83
Create PBB B-VID
20-84
Delete PBB B-VID
20-86
Allocate PBB B-VID
20-87
Deallocate PBB B-VID
20-88
Implement PBB B-VID
20-89
Deimplement PBB B-VID
20-91
Domain Wide VID distribution
20-93
Ring Association to a B-VID
20-95
Ring Dissociation from B-VID
20-97
Change ERP of a B-VID
20-99
List ERP instances of a B-VID
20-101
Association of Transport Link to B-VID
20-102
Dissociation of Transport Link to B-VID
20-104
.................................................................................................................................................................................................................................... 1350 OMS 20-82 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
View the B-VID list
....................................................................................................................................................................................................................................
View the B-VID list When to use
The PBB B-VID List window presents all the B-VIDand their attributes. Related Information
For information about PBB EVC, Refer to“PBB Ethernet Virtual Connection” (p. 20-7). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The menu of the Services is shown. ...................................................................................................................................................................................................
2
Select Connection Less (Bridge) > B-VIDs. Result: The list window is displayed.
The attributes displayed for each B-VID are: • User Label. • Domain (must be a PBB Domain). • VLAN Id • •
Provisioning state.(Defined, Allocated, Partially implemented, Implemented, ) Availability State(Normal)
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-83 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Create PBB B-VID
....................................................................................................................................................................................................................................
Create PBB B-VID When to use
The function creates a PBB B-VID. B-VID is used as an infrastructure for EVCs. Related Information
About the parameters: •
Domain must be PBB Domain.
•
I-SID spcify the bundle of I-SIDs allowed to be supported by this B-VID. An empty
•
•
•
set means no restrictions apply. VLAN ID must not be already assigned to another B-VID in the Domain. Specified VID must be: – If the request is from ERP BB: specified VID must be in the R-APS B-VID VLAN Bundle of the Domain. – If the request is not from ERP BB: specified VID must not be in the R-APS B-VID VLAN Bundle of the Domain. VLAN Distribution is Manual means the Rings and the Transport Links to be associated to the B-VID must be explicitly chosen by the operator. Optionally the operator can choose the ERP instance of each chosen Ring to be associated to the B-VID. For each chosen Ring for which no ERP instance has been specified the per-Port ERP instance is automatically chosen. If no ERP instance is specified for a ring and that ring has no per-Port ERP instance, the creation of the B-VID fails and a detailed error is reported to the operator. If VLAN distribution is Manual, the user specify: – a subset of the Rings of the Domain and for each Ring, optionally, the ERP instance to be used; – a subset of the Transport Links of the Domain that do not already belong to a Ring VLAN Distribution is Domain Wide means that, once created, the B-VID will have all the Rings and the Transport Links of the Domain associated to it. In this case the per-Port ERP of each chosen ring is automatically associated to the B-VID. If no per-Port ERP exists for at least one ring of the Domain, the creation of the B-VID fails and a detailed error is reported to the operator.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode.
.................................................................................................................................................................................................................................... 1350 OMS 20-84 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Create PBB B-VID
....................................................................................................................................................................................................................................
Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Action > Packet > Services. Result: The menu of the Services is shown. ...................................................................................................................................................................................................
2
Select Connection Less (Bridge) > Create B-VID. ...................................................................................................................................................................................................
3
Enter the following parameters: •
Enter a Userlabel.
•
Select a Domain from list. Must be aPBB Domain.
•
Enter VLAN ID. (A value from 1 to 4094, a unique value in the Domain).
•
VLAN distribution. (Manual, Domain Wide)
•
Click ERP and select one or more rings from list.
•
For each ring, select one or more ERP instances from list.
•
Click Transport link and select one or more Transport links from list.
...................................................................................................................................................................................................
4
Click Ok. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-85 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Delete PBB B-VID
....................................................................................................................................................................................................................................
Delete PBB B-VID When to use
The function deletes a PBB B-VID. B-VID is used as an infrastructure for EVCs. Related Information
A B-VID can only be deleted when is in Defined state and does not support any EVC. A B-VID created by ERP BB can only be deleted by ERP BB. A B-VID created by the USM can only be deleted by the USM. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > B-VIDs. ...................................................................................................................................................................................................
2
Select the object in the list. ...................................................................................................................................................................................................
3
Select the path Action > B-VIDs > Delete. ...................................................................................................................................................................................................
4
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-86 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Allocate PBB B-VID
....................................................................................................................................................................................................................................
Allocate PBB B-VID When to use
The function allocates resources for a PBB B-VID. Related Information
This phase consists in the creation, on DB, of the VLAN Distribution information (for each NE on which terminates/passes a TL/Ring associated to the B-VID). A B-VID created by ERP BB can only be allocated by ERP BB. A B-VID created by the USM can only be allocated by the USM. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > B-VIDs. ...................................................................................................................................................................................................
2
Select the object in the list. ...................................................................................................................................................................................................
3
Select the path Action > B-VIDs > Allocate. ...................................................................................................................................................................................................
4
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-87 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Deallocate PBB B-VID
....................................................................................................................................................................................................................................
Deallocate PBB B-VID When to use
The function de-allocates resources for a PBB B-VID. Related Information
This phase consists in the removal of the DB objects created during the allocation . A B-VID can't be de-allocated if it supports one or more EVCs that are allocated: all the EVCs supported by a B-VID (if any) must be all in defined state in order for the B-VID to be deallocated. A B-VID created by ERP BB can only be de-allocated by ERP BB. A B-VID created by the USM can only be de-allocated by the USM. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > B-VIDs. ...................................................................................................................................................................................................
2
Select the object in the list. ...................................................................................................................................................................................................
3
Select the path Action > B-VIDs > Deallocate. ...................................................................................................................................................................................................
4
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-88 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Implement PBB B-VID
....................................................................................................................................................................................................................................
Implement PBB B-VID When to use
The function provisions the elementary objects involved with a PBB B-VID. Related Information
Provisioning on the involved NEs (i.e. the ones identified during the allocation phase) of the (in this order): 1. creation of the B-VID instance and of the associations B-VID - Port; 2. associations B-VID - ERP (for any non-per-Port ERP). Step 1 involves the creation of a row in the opticsIMPbbInstanceTable, in each involved NE, that contains among the other things the ports to be associated to the B-VID instance (i.e. the ports, in that NE, belonging to TLs or Rings associated to the B-VID). This provisioning is requested by EoT to Adaptation. Step 2 involves the request to ERP BB to perform the association for each involved ERP (only in case of per-VLAN ERP). Step 2 is not performed for B-VIDs created by ERP BB (the association, in fact, is provisioned by the ERP BB before invoking the B-VID implementation; This avoids deadlocks between ERP BB and EoT BB (both being single threaded processes). A complete failure on step 1 causes the B-VID to remain in Allocated state. A partial failure on step 1 or a failure during step 2 causes the B-VID to go in Partially Implemented state. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > B-VIDs. ...................................................................................................................................................................................................
2
Select the object in the list. ...................................................................................................................................................................................................
3
Select the path Action > B-VIDs > Implement.
.................................................................................................................................................................................................................................... 1350 OMS 20-89 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Implement PBB B-VID
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-90 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Deimplement PBB B-VID
....................................................................................................................................................................................................................................
Deimplement PBB B-VID When to use
The function releses the elementary objects involved with a PBB B-VID. Related Information
Un-provisioning on the involved NEs (i.e. the ones identified during the allocation phase) of the objects provisioned during the implementation with the same interactions of EoT with other BBs. This means: 1. removal of associations B-VID - ERP (for any non-per-Port ERP), requested to ERP BB by EoT BB; 2. removal of the B-VID instance (with automatic removal of B-VID - Port associations) performed by Adaption on behalf of EoT. Step 1 is not performed for B-VIDs created by ERP BB (the association, in fact, is un-provisioned by the ERP BB after invoking the B-VID de-implementation; This avoids deadlocks between ERP BB and EoT BB (both being single threaded processes). A complete failure on step 1 causes the B-VID to remain in Implemented state. A partial failure on step 1 or a failure during step 2 causes the B-VID to go in Partially Implemented state. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > B-VIDs. ...................................................................................................................................................................................................
2
Select the object in the list. ...................................................................................................................................................................................................
3
Select the path Action > B-VIDs > Deimplement.
.................................................................................................................................................................................................................................... 1350 OMS 20-91 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Deimplement PBB B-VID
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-92 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Domain Wide VID distribution
....................................................................................................................................................................................................................................
Domain Wide VID distribution When to use
The function associates all the Rings and Transport Links of a Domain to a B-VID. Related Information
This procedure applies to any provisioning state. Defined case
This procedure applies when the operator requires an existing B-VID in Defined state to be Domain-Wide distributed. This operation causes the B-VID to be associated to all the Rings and TLs of the Domain, as if it was been created with VLAN Distribution = "Domain Wide". Allocated case
This procedure applies when the operator requires an existing B-VID in Allocated or Partially Implemented state (in any case, no provisioning is performed) to be Domain-Wide distributed. This operation causes the B-VID to be associated to all the Rings and TLs of the Domain, as if it was created with VLAN Distribution = "Domain Wide" and then immediately allocated. This operation could also be seen as an equivalent of a series of ring association (allocated case) and transport link association (allocated case) in order to associate all TLs and Rings (only one Ring per Bundle) not associated to the B-VID. Implemented case
This procedure applies when the operator requires an existing B-VID in Implemented state to be Domain-Wide distributed. This operation causes the B-VID to be associated to all the Rings and TLs of the Domain, as if it was been created with VLAN Distribution = "Domain Wide" and then immediately allocated and implemented. This operation could also be seen as an equivalent of a series of ring association (implemented case) and transport link association (implemented case) in order to associate all TLs and Rings (only one Ring per Bundle) not associated to the B-VID. As a result of this operation the B-VID can be either in Implemented (if each TL/Ring association either failed completely or succeeded) or Partially Implemented (if at least one TL/Ring association failed half-way) and can be associated to all Rings and TLs of the Domains or not (in case at least one TL/Ring associated failed completely). In case of unsuccessful operation the operator is informed of which TLs/Rings where not associated properly or not associated at all.
.................................................................................................................................................................................................................................... 1350 OMS 20-93 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Domain Wide VID distribution
....................................................................................................................................................................................................................................
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > B-VIDs. ...................................................................................................................................................................................................
2
Select the object in the list. ...................................................................................................................................................................................................
3
Select the path Action > B-VIDs > Distribute VID domain-wide. Result: VLAN ID is distributed in the domain. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-94 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Ring Association to a B-VID
....................................................................................................................................................................................................................................
Ring Association to a B-VID When to use
The function associates a Ring and an ERP instance to a B-VID. Related Information
This function applies to any provisioning state. Defined case
To add a Ring to a B-VID, the operator must specify: • • •
the B-VID the Ring an ERP instance on that Ring
For a Ring to be associated to a B-VID, the following must be true: •
• •
no other Ring of the same Bundle is already associated to the B-VID (a Ring can't be associated to a B-VID if another Ring of the same Bundle is already associated to it: only one ring per bundle can be associate to a B-VID) B-VID and Ring must belong to the same Domain B-VID and Ring must not be already associated
If all checks are ok the B-VID is associated to the specified Ring and ERP instance. Allocated case
This is almost the same case of ring association defined case, in addition the allocation of the B-VID - Ring association is performed: • •
allocation on DB of the VLAN Distribution information (for each NE involved, the two involved Ports are associated to the B-VID) allocation on DB of the I-SID Distribution information, for each allocated EVC that is supported by the B-VID: – in case the EVC is not under OAM: the I-SID must be distributed in all the NEs, of the newly associated ring, that contain at least one EVC Termination – in case the EVC is under OAM: the I-SID must be distributed in all the NEs of the newly associated ring.
This case applies both to allocated and partially implemented B-VIDs (in any case, no provisioning is performed). Implemented case
This is almost the same case of ring association in allocated case, in addition part of the implementation of the B-VID and of all the implemented EVCs that the former supports is performed: • •
for each NE of the Ring in which the B-VID instance has not yet been provisioned: creation of the B-VID instance and of the associations B-VID - Port for each NE of the Ring in which the B-VID instance already exists: modification of the member set of the B-VID instance to include the two ports of the Ring for that NE
.................................................................................................................................................................................................................................... 1350 OMS 20-95 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Ring Association to a B-VID
....................................................................................................................................................................................................................................
• •
request to ERP BB to provision the association between the B-VID and the specified ERP (only in case of per-VLAN ERP); for each EVC supported by the B-VID: –
for each implemented EVC Termination residing on a NE crossed by the Ring: provisioning of the association Port - B-VID - I-SID, that can either mean creation of a row in opticsIMPbbInstanceTable (if the row did not existed) or modification of a row in opticsIMPbbInstanceTable (if the row did existed)
–
if the EVC is implemented and under OAM: the I-SID of the EVC has to be provisioned also in all the NEs of the newly added ring that do not contain an implemented EVC Termination.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > B-VIDs. ...................................................................................................................................................................................................
2
Select the object in the list. ...................................................................................................................................................................................................
3
Select the path Action > B-VIDs > Associate/Disassociate Ring. ...................................................................................................................................................................................................
4
In the Associate/Dissociate window: •
Select Select Operation (Associate).
•
Select B-VID from list.
•
Select Erp Ring from list.
•
Select Erp Instance from list.
...................................................................................................................................................................................................
5
Click Ok. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-96 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Ring Dissociation from B-VID
....................................................................................................................................................................................................................................
Ring Dissociation from B-VID When to use
The function dissociates a Ring from a B-VID. Related Information
This function applies to any provisioning state. Defined case
The operator specifies the B-VID and the Ring. B-VID and Ring must be associated. PKT dissociates the B-VID and the Ring (together with the associated ERP instance). Allocated case
This is almost the same case of ring dissociation (defined case); in addition, before the removal of the B-VID - Ring association, its de-allocation is performed: •
de-allocation of the I-SID Distribution information, for each allocated EVC supported by the B-VID in all the NEs that will no longer belong to the B-VID once the ring is removed
•
de-allocation of the VLAN Distribution information (for each NE involved, the two involved Ports are dissociated from the B-VID).
In no case a ring can be dissociated from a B-VID if this action leaves an EVC of the B-VID with an EVC Termination on a NE that is no more used by the B-VID. In other words: if an EVC Termination belonging to the involved B-VID, is on one of the NEs of the ring, and, on that NE, there are no other Transport Links or rings associated to the involved B-VID, the latter can't be dissociated from the ring. Implemented case
This is almost the same case of ring dissociation (allocated case), in addition, before the de-allocation of the B-VID - Ring association, its de-implementation and the de-implementation of the involved part of implemented and partially implemented EVCs supported by that B-VID is performed: •
•
for each EVC supported by the B-VID: – for each implemented or partially implemented EVC Termination residing on a NE crossed by the Ring: un-provisioning of the association Port - B-VID - I-SID, that means modification of a row in opticsIMPbbInstanceTable – if the EVC is implemented or partially implemented, removal of all the I-SID instances in all the NEs that will no longer belong to the B-VID once the ring is removed (that means deletion of a row in opticsIMPbbInstanceTable). This also covers the case of EVC under OAM un-provision the association between the B-VID and the associated ERP on that Ring (only in case of per-VLAN ERP)
.................................................................................................................................................................................................................................... 1350 OMS 20-97 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Ring Dissociation from B-VID
....................................................................................................................................................................................................................................
•
•
for each NE of the Ring in which there are no other NNIs not belonging to the Ring but associated to the B-VID instance: deletion of the B-VID instance and of the associations B-VID - Port for each NE of the Ring in which there's at least another NNI not belonging to the Ring but associated to the B-VID instance: modification of the member set of the B-VID instance to remove the two ports of the Ring for that NE
This case applies both implemented and partially implemented B-VIDs. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > B-VIDs. ...................................................................................................................................................................................................
2
Select the object in the list. ...................................................................................................................................................................................................
3
Select the path Action > B-VIDs > Associate/Disassociate Ring. ...................................................................................................................................................................................................
4
In the Associate/Dissociate window: •
Select Select Operation (Dissociate).
•
Select B-VID from list.
•
Select Erp Ring from list.
•
Select Erp Instance from list.
...................................................................................................................................................................................................
5
Click Ok. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-98 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Change ERP of a B-VID
....................................................................................................................................................................................................................................
Change ERP of a B-VID When to use
The function moves a defined B-VID from a ring of a bundle to another ring of the same bundle. Related Information
This function applies to any provisioning state. The operator specifies: • • •
the B-VID the associated Ring the Ring to be associated
The system checks that: •
the B-VID and the first Ring are associated
•
the two Rings belong to the same Ring Bundle
This procedure is functionally equivalent to a Ring dissociation followed by a Ring association. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > B-VIDs. ...................................................................................................................................................................................................
2
Select the object in the list. ...................................................................................................................................................................................................
3
Select the path Action > B-VIDs > Change ERP instance. ...................................................................................................................................................................................................
4
In the Change ERP window: •
Select B-VID from list.
•
Select Erp Ring from list.
•
Select Erp Instance from list.
.................................................................................................................................................................................................................................... 1350 OMS 20-99 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Change ERP of a B-VID
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
5
Click Ok. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-100 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
List ERP instances of a B-VID
....................................................................................................................................................................................................................................
List ERP instances of a B-VID When to use
The function lists all the ERP instances belonging to a B-VID. Related Information
For information about ERP , see: “Ethernet Ring Protocol (ERP)” (p. 20-10). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > B-VIDs. ...................................................................................................................................................................................................
2
Select the object in the list. ...................................................................................................................................................................................................
3
Select the path Action > B-VIDs > List ERP instances from B-VID. Result: The list window is displayed.
See the following topic in this document: “Description of the list of ERP” (p. 20-109). E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-101 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Association of Transport Link to B-VID
....................................................................................................................................................................................................................................
Association of Transport Link to B-VID When to use
The function adds a Transport Link to a B-VID. Related Information
This function applies to any provisioning state. Defined case
The operator specifies: • •
the B-VID the Transport Link
For a Transport Link to be associated to a B-VID, the following must be true: • •
the TL must not belong to a Ring B-VID and TL must belong to the same Domain
•
B-VID and TL must not be already associated
If all checks are ok the B-VID is associated to the specified Transport Link. Allocated case
This is almost the same case of transport link association (defined case), in addition: •
the allocation of the B-VID - TL association is performed: allocation on DB of the VLAN Distribution information (the two involved Ports of the TL are associated to the B-VID)
•
the allocation on DB of the I-SID Distribution information is performed for each allocated EVC that is supported by the B-VID: – in case the EVC is not under OAM: the I-SID must be distributed at each extremity of the TL that contain at least one EVC Termination – in case the EVC is under OAM: the I-SID must be distributed at each extremity of the TL
This case applies both to allocated and partially implemented B-VIDs (in any case, no provisioning is performed). Implemented case
This is almost the same case of transport link association (allocated case), in addition part of the implementation of the B-VID and of all the implemented EVCs that the former supports is performed: • •
for each NE at the extremities of the TL in which the B-VID instance has not yet been provisioned: creation of the B-VID instance and of the associations B-VID - Port for each NE at the extremities of the TL in which the B-VID instance already exists: modification of the member set of the B-VID instance to include the extremity of the TL in that NE;
.................................................................................................................................................................................................................................... 1350 OMS 20-102 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Association of Transport Link to B-VID
....................................................................................................................................................................................................................................
•
for each EVC supported by the B-VID: – for each implemented EVC Termination residing on a NE at the extremities of the TL: provisioning of the association Port - B-VID - I-SID, that can either mean creation of a row in opticsIMPbbInstanceTable (if the row did not existed) or modification of a row in opticsIMPbbInstanceTable (if the row did existed) – if the EVC is implemented and under OAM: the I-SID of the EVC has to be provisioned also in all the NEs at the extremities of the TL that do not contain an implemented EVC Termination.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > B-VIDs. ...................................................................................................................................................................................................
2
Select the object in the list. ...................................................................................................................................................................................................
3
Select the path Action > B-VIDs > Associate/Disassociate Transport Link. ...................................................................................................................................................................................................
4
In the Associate/Dissociate window: •
Select Select Operation (Associate, Dissociate)
•
Select B-VID from list
•
Select Transport Link from list
...................................................................................................................................................................................................
5
Click Ok. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-103 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Dissociation of Transport Link to B-VID
....................................................................................................................................................................................................................................
Dissociation of Transport Link to B-VID When to use
The function removes a Transport Link from a B-VID. Related Information
This function applies to any provisioning state. Defined case
The operator specifies: • •
the B-VID the Transport Link
For a Transport Link to be dissociated from a B-VID, the following must be true: • •
the TL must not belong to a Ring B-VID and TL must be associated
If all checks are ok the B-VID is dissociated to the specified Transport Link. Allocated case
This is almost the same case of transport link dissociation (defined case), in addition, before the B-VID - TL association is removed, its de-allocation is performed: •
•
de-allocation on DB of the I-SID Distribution information, for each allocated EVC supported by the B-VID in all the NEs that will no longer belong to the B-VID once the TL is removed de-allocation on DB of the VLAN Distribution information (for each NE involved, the involved Port is dissociated from the B-VID).
In no case a TL can be dissociated from a B-VID if this action leaves an EVC of the B-VID with an EVC Termination on a NE that is no more used by the B-VID. In other words: if an EVC Termination ,of an EVC belonging to the involved B-VID, is on one of the NEs at the extremity of the TL, and, on that NE, there are no other Transport Links or rings associated to the involved B-VID, the latter can't be dissociated from the Transport Link.
.................................................................................................................................................................................................................................... 1350 OMS 20-104 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Dissociation of Transport Link to B-VID
....................................................................................................................................................................................................................................
Implemented case
This is almost the same case of transport link dissociation (allocated case), in addition, before the B-VID - TL association is de-allocated, part of the de-implementation of the B-VID and of all the implemented or partially implemented EVCs that the former supports is performed: •
•
•
for each EVC supported by the B-VID: – for each implemented or partially implemented EVC Termination residing on a NE at the extremities of the TL: un-provisioning of the association Port - B-VID I-SID, that means modification of a row in opticsIMPbbInstanceTable – if the EVC is implemented or partially implemented, removal of all the I-SID instances in all the NEs that will no longer belong to the B-VID once the TL is removed (that means deletion of a row in opticsIMPbbInstanceTable). This also covers the case of EVC under OAM. for each NE at the extremities of the TL in which there are no other NNIs associated to the B-VID instance: deletion of the B-VID instance and of the associations B-VID Port for each NE at the extremities of the TL in which there's at least another NNI associated to the B-VID instance: modification of the member set of the B-VID instance to remove the port of the TL for that NE.
This case applies both implemented and partially implemented B-VIDs. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the path Search > Packet > Services > Connection Less (Bridge) > B-VIDs. ...................................................................................................................................................................................................
2
Select the object in the list. ...................................................................................................................................................................................................
3
Select the path Action > B-VIDs > Associate/Disassociate Transport Link.
.................................................................................................................................................................................................................................... 1350 OMS 20-105 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management B-VID Management
Dissociation of Transport Link to B-VID
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
In the Associate/Dissociate window: •
Select Select Operation (Associate, Dissociate)
•
Select B-VID from list
•
Select Transport Link from list
...................................................................................................................................................................................................
5
Click Ok. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-106 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Ethernet Ring Protection (ERP) Management
Overview
....................................................................................................................................................................................................................................
Ethernet Ring Protection (ERP) Management Overview Purpose
This document describes the functionality needed to manage ITU-T G.8032 Ethernet Ring Protection v2 (ERP) protocol inside 1350 OMS PKT product. Contents View the ERP ring list
20-108
Description of the list of ERP
20-109
Create/delete ERP Ring
20-110
Implement/deimplement the ERP
20-112
ERP Switch Command
20-113
ERP Switch Command From Port
20-114
Add/remove Transport Link in a Ring
20-115
Add/remove Node in a Ring
20-116
Create/delete ERP Ring bundle
20-117
Add/remove ERP Ring in a bundle
20-118
.................................................................................................................................................................................................................................... 1350 OMS 20-107 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Ethernet Ring Protection (ERP) Management
View the ERP ring list
....................................................................................................................................................................................................................................
View the ERP ring list When to use
The ERP List window presents all the rings and their attributes. Related Information
For information about ERP , see: “Ethernet Ring Protocol (ERP)” (p. 20-10). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet. Result: The menu of the Packet is shown. ...................................................................................................................................................................................................
2
Select ERP > Rings. Result: The list window is displayed.
See the following topic in this document: “Description of the list of ERP” (p. 20-109). E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-108 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Ethernet Ring Protection (ERP) Management
Description of the list of ERP
....................................................................................................................................................................................................................................
Description of the list of ERP Attributes of a Ring
The attributes displayed for each Ring are: •
User Label.
•
Ring Type (Major, Sub-ring).
•
Closure (Closed, Open).
•
Provisioning State (Defined, Allocated, Implemented).
•
Def.Time.
•
Working State (Normal).
•
Last Operation (None, Allocation, Deallocation, Implementation, Deimplementation).
•
Availability Status. (Normal).
.................................................................................................................................................................................................................................... 1350 OMS 20-109 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Ethernet Ring Protection (ERP) Management
Create/delete ERP Ring
....................................................................................................................................................................................................................................
Create/delete ERP Ring When to use
The function creates ERP Rings. Related Information
Ring Types: • •
A major ring is a ring that is self-containing, i.e. it has no need to use tunneling of R-APS through other rings. A sub-ring is a ring that is closed by a “tunnel connectivity” provided by other rings (either major rings or sub-ring).
A Ring can be created from: •
Links list
• •
Topological view Common Map
A ring can be done by transport link of one only domain. It is possible that the links assigned to a ring are not implementing a closed ring: in this case a warning should be raised to operator. For PKT 9.3 only PBB domains are foreseen. More then one major ring per domain is allowed. A physical ring can be created also if the transport link is already used by traffic. A physical ring can be deleted only when it is not-implemented. No check is done respect to the usage of the links for traffic. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Action > Packet > ERP > Create ERP Ring.
.................................................................................................................................................................................................................................... 1350 OMS 20-110 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Ethernet Ring Protection (ERP) Management
Create/delete ERP Ring
....................................................................................................................................................................................................................................
Result: The creation window is shown. ...................................................................................................................................................................................................
2
Enter: •
Enter the User Label
• •
Select the Ring Type. (Major, Sub) Select the Activation Status
• •
Select the PBB Domain from list Select the Transport Linksfrom list
...................................................................................................................................................................................................
3
Click OK Result: The ring is created E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-111 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Ethernet Ring Protection (ERP) Management
Implement/deimplement the ERP
....................................................................................................................................................................................................................................
Implement/deimplement the ERP When to use
The function implements major ring or sub-ring. Related Information
For information about ERP , see: “Ethernet Ring Protocol (ERP)” (p. 20-10). A physical ring can be deimplemented only if no ERP instances are active on it. No check is done respect to the usage of the links for traffic. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > ERP > Rings. Result: The list is shown. ...................................................................................................................................................................................................
2
Select the ring and select Implement or Deimplement. ...................................................................................................................................................................................................
3
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-112 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Ethernet Ring Protection (ERP) Management
ERP Switch Command
....................................................................................................................................................................................................................................
ERP Switch Command When to use
The function set ERP Switch Command. Related Information
For information about ERP , see: “Ethernet Ring Protocol (ERP)” (p. 20-10). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the menu item: •
Search > Packet > ERP > Rings
•
Search > Packet > ERP > ERP Instances Result: The list window is shown.
...................................................................................................................................................................................................
2
Select an item in the list and select Action > ERP Switch Command. ...................................................................................................................................................................................................
3
Select the following attributes: •
Select ERP Ring from list.
•
Select ERP Instance from list.
•
Select Target node of command from list.
•
Select Adjacent node from list.
•
Select Operator Command (Clear, Manual Switch, Force Switch).
•
Select or unselect Force without Check ring status.
...................................................................................................................................................................................................
4
Click OK E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-113 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Ethernet Ring Protection (ERP) Management
ERP Switch Command From Port
....................................................................................................................................................................................................................................
ERP Switch Command From Port When to use
The function set ERP Switch Command from ERP Port. Related Information
For information about ERP , see: “Ethernet Ring Protocol (ERP)” (p. 20-10). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select the menu item: •
Search > Packet > ERP > ERP Instances Result: The list window is shown.
...................................................................................................................................................................................................
2
Select an item in the list and select Search > ERP Port Inst on NE. Result: The Port list window is shown. ...................................................................................................................................................................................................
3
Right Click the mouse and select the menu item: •
Action > Clear
•
Action > Manual Switch
•
Action > Force Switch
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-114 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Ethernet Ring Protection (ERP) Management
Add/remove Transport Link in a Ring
....................................................................................................................................................................................................................................
Add/remove Transport Link in a Ring When to use
The function add a Transport Link in major ring or sub-ring. Related Information
For information about ERP , see: “Ethernet Ring Protocol (ERP)” (p. 20-10) The function applies to both defined or implemented ring. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > ERP > Rings. Result: The list is shown. ...................................................................................................................................................................................................
2
Select the ring and select Add link. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-115 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Ethernet Ring Protection (ERP) Management
Add/remove Node in a Ring
....................................................................................................................................................................................................................................
Add/remove Node in a Ring When to use
The function add a Node in major ring or sub-ring. Related Information
For information about ERP , see: “Ethernet Ring Protocol (ERP)” (p. 20-10). The function applies to both defined or implemented ring. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > ERP > Rings. Result: The list is shown. ...................................................................................................................................................................................................
2
Select the ring and select Add Node. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-116 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Ethernet Ring Protection (ERP) Management
Create/delete ERP Ring bundle
....................................................................................................................................................................................................................................
Create/delete ERP Ring bundle When to use
The function creates ERP Rings bundle. Related Information
When more rings are present on a given set of NEs, it is necessary to define the “stacked ring bundle” (bundle). Bundle can be composed by major rings or sub-rings (no mix of major and sub ring is possible). PKT automatically creates a bundle of rings as soon as two rings are created on the same set of NEs. Name of the bundle is assigned by default to “Bundle x” where x is a number that univocally identifies the bundle. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Action > Packet > ERP > Create ERP Ring bundle. Result: The creation window is shown. ...................................................................................................................................................................................................
2
Enter: •
Enter the Bundle name
•
Select the ERP Rings
...................................................................................................................................................................................................
3
Click OK Result: The bundle is created E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-117 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Ethernet Ring Protection (ERP) Management
Add/remove ERP Ring in a bundle
....................................................................................................................................................................................................................................
Add/remove ERP Ring in a bundle When to use
The function adds/remove ERP Ring in a bundle. Related Information
Operator can add a new ring to a bundle, given that: • •
•
Ring is on the same set of NEs of already grouped ring(s) Ring is of the same type (major/sub) of already grouped rings (this condition is automatically verified if the previous condition is true, but can be useful to filter the list of rings to be proposed to operator) VLANs registered on the ring cannot be assigned to ring already grouped in the bundle.
• Removal of a ring from a bundle is always possible: operator has to take care of avoiding registering VLAN on the ring after the removal: PKT cannot perform consistency checks to avoid traffic loop. PKT automatically add a ring to an existing bundle created on the same set of NEs. PKT automatically remove a ring from an existing bundle when ring is deleted. This is true independently from the way the ring has been assigned to the bundle (i.e. either manually or automatically). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > ERP > ERP Ring bundle. Result: The creation window is shown. ...................................................................................................................................................................................................
2
Select the Bundle name Select the Action > ERP Bundle > Add Ring ...................................................................................................................................................................................................
3
Click OK
.................................................................................................................................................................................................................................... 1350 OMS 20-118 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Ethernet Ring Protection (ERP) Management
Add/remove ERP Ring in a bundle
....................................................................................................................................................................................................................................
Result: The ring is added. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-119 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP Instance Management
Overview
....................................................................................................................................................................................................................................
ERP Instance Management Overview Purpose
This document describes how to manage ITU-T G.8032 Ethernet Ring Protection v2 (ERP) instances inside 1350 OMS PKT product. Contents View the ERP instance list
20-121
Description of the list of ERP instances
20-122
Create/delete ERP instance
20-123
Implement/deimplement the ERP instance
20-125
Associate OAM to the ERP instance
20-126
Get a graphical view of the ERP instance
20-127
Modify Defined ERP instance
20-129
Modify implemented ERP instance
20-131
.................................................................................................................................................................................................................................... 1350 OMS 20-120 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP Instance Management
View the ERP instance list
....................................................................................................................................................................................................................................
View the ERP instance list When to use
The ERP Instance List window presents all the rings and their attributes. Related Information
For information about ERP , see: “Ethernet Ring Protocol (ERP)” (p. 20-10). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet. Result: The menu of the Packet is shown. ...................................................................................................................................................................................................
2
Select ERP > ERP intances. Result: The list window is displayed.
See the following topic in this document: “Description of the list of ERP instances” (p. 20-122). E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-121 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP Instance Management
Description of the list of ERP instances
....................................................................................................................................................................................................................................
Description of the list of ERP instances Attributes of an ERP instances
The attributes displayed for each ERP instance are: •
User Label.
•
ERP Scope (Per Port, Per VLAN).
•
VLAN Id. VLAN used to tag R-APS PDU for this ERP instance.
•
VLAN Priority. Priority of R-APS PDU for this ERP instance.
•
Hold Off Time. Time to wait, after failure detection, before starting ERP protection.
•
WTR Time. Wait time to restore (minutes) in case of switch mode is revertive. If
• • • • • •
• •
Switch behavior is “revertive” default is 5; If Switch behavior is “not revertive” default is “not meaningful” and not modifiable. Guard Time. During guard time RPL owner discards the received R-APS OAM frames. Switch Behaviour(Revertive, Non Revertive). Behavior of switch following clear of failure. ERP State. (deactivated, idle, protection, manualSwitch, forcedSwitch, pending). Status of the ERP protection. Maintenance Entity Level. Maintenance Entity Level of the ERP instance. Switch On Ploc. (False, True). Include/exclude Partial loss of capacity (LAG) alarm
in the list of ERP Switch Criteria Switch On Cfm Alarm. (False, True). Include/exclude ETH OAM CFM alarms (AIS, Loss Of Continuity (LOC), MisMerge (MMG) , UNexpected Mep (UNM), UNexpected Level (UNL) in the list of ERP Switch Criteria Provisioning State (Defined, Allocated, Implemented). Ring Userlabel.
•
Def.Time.
•
Working State (Normal).
•
Last Operation (None, Allocation, Deallocation, Implementation, Deimplementation).
•
Switch On Anm. (False, True). Include/exclude auto-negotiation mismatch alarm in
the list of ERP Switch Criteria. • •
Comment Availability Status. (Normal, Degraded, Failure).
.................................................................................................................................................................................................................................... 1350 OMS 20-122 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP Instance Management
Create/delete ERP instance
....................................................................................................................................................................................................................................
Create/delete ERP instance When to use
The function creates ERP instances. Related Information
Definition is always possible. Checks to be done: • • •
•
• •
ERP instance user label has to be unique in the system R-APS VLAN Id must be inside the bundle of VLAN assigned to ERP for the domain ERP instance is defined R-APS VLAN id must not be used for in-fiber/in-band management channel: this check could be implicitly passed if management VLAN is not part of bundle of VLAN reserved for ERP. R-APS VLAN Id cannot have already been assigned to other ERP instances on the same ERP physical ring or by ERP instance on sub-rings that uses the current ring to close the virtual channel for R-APS Just one per-port ERP can be defined on a given physical ring If ring Id is different from default it must be unique inside the ERP instances of a given physical ring.
Deletion of ERP instance is possible only after de-implementation. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Action > Packet > ERP > Create ERP instances. Result: The creation window is shown. ...................................................................................................................................................................................................
2
In the General panel: •
Enter the User Label. Unique identifier of ERP instance inside PKT.
•
Enter a Comment. (optional)
•
Select the Activation Status. Enable/disable implementation of ERP instance.
•
Enter theR-APS VLAN Id. VLAN used to tag R-APS PDU for this ERP instance.
•
Enter the R-APS PCP. Priority of R-APS PDU for this ERP instance.
.................................................................................................................................................................................................................................... 1350 OMS 20-123 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP Instance Management
Create/delete ERP instance
....................................................................................................................................................................................................................................
• • • •
Enter the Maintenance Entity Level. Maintenance Entity Level of the ERP instance. Select the Scope. (Per Port, Per VLAN) Select the PBB Domain from list. Domain where ERP instance is defined. Select the ERP Ring from list. Ring to be controlled by ERP instance.
•
Select the RPL Owner from list. NE having the RPL-owner role.
•
Select the RPL from list. Link/Port blocked by the ERP instance in nominal condition.
In the Timers panel: • •
• •
Select the Switch Behaviour. (Revertive, Non Revertive). Behavior of switch following clear of failure. Enter theWait Time To Restore (min). Wait time to restore (minutes) in case of switch mode is revertive. If Switch behavior is “revertive” default is 5; If Switch behavior is “not revertive” default is “not meaningful” and not modifiable. Enter the Hold Off Time (msec). Time to wait, after failure detection, before starting ERP protection. Enter the Guard Time (msec). Range from 10 to 2000 ms, with step of 10 ms. During guard time RPL owner discards the received R-APS OAM frames.
In the Failures panel select or deselect: • • • •
•
Auto-Negotiation Mismatch. Include/exclude auto-negotiation mismatch alarm in the
list of ERP Switch Criteria. (Enabled by default). Partial loss of capacity. Include/exclude Partial loss of capacity (LAG) alarm in the list of ERP Switch Criteria. Signal Degrade. Include/exclude Signal Degrade alarm in the list of ERP Switch Criteria. ETH OAM CFM Alarms. Include/exclude ETH OAM CFM alarms (AIS, Loss Of Continuity (LOC), MisMerge (MMG) , UNexpected Mep (UNM), UNexpected Level (UNL) in the list of ERP Switch Criteria. Link OAM Critical link Events. Include/exclude link OAM critical link events alarm in the list of ERP Switch Criteria
...................................................................................................................................................................................................
3
Click OK Result: The ring is created E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-124 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP Instance Management
Implement/deimplement the ERP instance
....................................................................................................................................................................................................................................
Implement/deimplement the ERP instance When to use
The function implements ERP instance. Related Information
For information about ERP , see: “Ethernet Ring Protocol (ERP)” (p. 20-10) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > ERP > ERP Instances. Result: The list is shown. ...................................................................................................................................................................................................
2
Select the ring and select Implement. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-125 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP Instance Management
Associate OAM to the ERP instance
....................................................................................................................................................................................................................................
Associate OAM to the ERP instance When to use
The function associates OAM to ERP instance. Related Information
For information about ERP , see: “Ethernet Ring Protocol (ERP)” (p. 20-10). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > ERP > ERP Instances. Result: The list is shown. ...................................................................................................................................................................................................
2
Select the ERP Instance and select Associate OAM to ERP Instance. ...................................................................................................................................................................................................
3
For each item in the ERP Link List, select the following attributes: •
Select ERP Link from list.
•
Select OAM MA from list.
•
Click Associate.
...................................................................................................................................................................................................
4
Click OK E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-126 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP Instance Management
Get a graphical view of the ERP instance
....................................................................................................................................................................................................................................
Get a graphical view of the ERP instance When to use
The function show a graphical view of the ERP instance. Related Information
For information about ERP , see: “Ethernet Ring Protocol (ERP)” (p. 20-10). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > ERP > ERP Instances. Result: The list is shown. ...................................................................................................................................................................................................
2
Select the ERP Instance and select ERP Graphical View.
.................................................................................................................................................................................................................................... 1350 OMS 20-127 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP Instance Management
Get a graphical view of the ERP instance
....................................................................................................................................................................................................................................
Result: Figure 20-58 ERP Graphical View example
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-128 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP Instance Management
Modify Defined ERP instance
....................................................................................................................................................................................................................................
Modify Defined ERP instance When to use
The function permit to modify attributes of a defined ERP instance. Related Information
In case the Ring or the scope has to be changed it is necessary to delete the ERP instance and create a new one. As a particular case the modification of RPL Owner requires to reset the RPL, so operator has to select RPL again. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > ERP > ERP instance. Result: The list is shown. ...................................................................................................................................................................................................
2
Select the object and select Modify. ...................................................................................................................................................................................................
3
In the General panel: •
Enter the User Label. Unique identifier of ERP instance inside PKT.
•
Enter a Comment. (optional)
•
Select the Activation Status. Enable/disable implementation of ERP instance.
•
Enter theR-APS VLAN Id. VLAN used to tag R-APS PDU for this ERP instance.
• •
Enter the R-APS PCP. Priority of R-APS PDU for this ERP instance. Enter the Maintenance Entity Level. Maintenance Entity Level of the ERP instance.
•
Select the RPL Owner from list. NE having the RPL-owner role.
•
Select the RPL from list. Link/Port blocked by the ERP instance in nominal condition.
.................................................................................................................................................................................................................................... 1350 OMS 20-129 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP Instance Management
Modify Defined ERP instance
....................................................................................................................................................................................................................................
In the Timers panel: • •
• •
Select the Switch Behaviour. (Revertive, Non Revertive). Behavior of switch following clear of failure. Enter theWait Time To Restore (min). Wait time to restore (minutes) in case of switch mode is revertive. If Switch behavior is “revertive” default is 5; If Switch behavior is “not revertive” default is “not meaningful” and not modifiable. Enter the Hold Off Time (msec). Time to wait, after failure detection, before starting ERP protection. Enter the Guard Time (msec). Range from 10 to 2000 ms, with step of 10 ms. During guard time RPL owner discards the received R-APS OAM frames.
In the Failures panel select or deselect: • • • •
•
Auto-Negotiation Mismatch. Include/exclude auto-negotiation mismatch alarm in the
list of ERP Switch Criteria. Partial loss of capacity. Include/exclude Partial loss of capacity (LAG) alarm in the list of ERP Switch Criteria. Signal Degrade. Include/exclude Signal Degrade alarm in the list of ERP Switch Criteria. ETH OAM CFM Alarms. Include/exclude ETH OAM CFM alarms (AIS, Loss Of Continuity (LOC), MisMerge (MMG) , UNexpected Mep (UNM), UNexpected Level (UNL) in the list of ERP Switch Criteria. Link OAM Critical link Events. Include/exclude link OAM critical link events alarm in the list of ERP Switch Criteria
...................................................................................................................................................................................................
4
Click OK Result: The ring is created E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-130 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP Instance Management
Modify implemented ERP instance
....................................................................................................................................................................................................................................
Modify implemented ERP instance When to use
The function permit to modify attributes of an implemented ERP instance. Related Information
Attributes that can be modified for an implemented ERP instance are attributes that can be changed on the NE with no need to deactivate the ERP instance. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Select Search > Packet > ERP > ERP instance. Result: The list is shown. ...................................................................................................................................................................................................
2
Select the object and select Modify. ...................................................................................................................................................................................................
3
In the General panel: •
Enter the User Label. Unique identifier of ERP instance inside PKT.
•
Enter a Comment. (optional)
•
Select the Activation Status. Enable/disable implementation of ERP instance.
•
Enter the R-APS PCP. Priority of R-APS PDU for this ERP instance.
•
Select the RPL Owner from list. NE having the RPL-owner role.
•
Select the RPL from list. Link/Port blocked by the ERP instance in nominal condition.
In the Timers panel: • •
Select the Switch Behaviour. (Revertive, Non Revertive). Behavior of switch following clear of failure. Enter theWait Time To Restore (min). Wait time to restore (minutes) in case of switch mode is revertive. If Switch behavior is “revertive” default is 5; If Switch behavior is “not revertive” default is “not meaningful” and not modifiable.
.................................................................................................................................................................................................................................... 1350 OMS 20-131 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management ERP Instance Management
Modify implemented ERP instance
....................................................................................................................................................................................................................................
• •
Enter the Hold Off Time (msec). Time to wait, after failure detection, before starting ERP protection. Enter the Guard Time (msec). Range from 10 to 2000 ms, with step of 10 ms. During guard time RPL owner discards the received R-APS OAM frames.
In the Failures panel select or deselect: • • • •
•
Auto-Negotiation Mismatch. Include/exclude auto-negotiation mismatch alarm in the
list of ERP Switch Criteria. Partial loss of capacity. Include/exclude Partial loss of capacity (LAG) alarm in the list of ERP Switch Criteria. Signal Degrade. Include/exclude Signal Degrade alarm in the list of ERP Switch Criteria. ETH OAM CFM Alarms. Include/exclude ETH OAM CFM alarms (AIS, Loss Of Continuity (LOC), MisMerge (MMG) , UNexpected Mep (UNM), UNexpected Level (UNL) in the list of ERP Switch Criteria. Link OAM Critical link Events. Include/exclude link OAM critical link events alarm in the list of ERP Switch Criteria
...................................................................................................................................................................................................
4
Click OK Result: The ring is created E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-132 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management PBB Fault Management
Overview
....................................................................................................................................................................................................................................
PBB Fault Management Overview Purpose
The Fault Localization allows the user to determine the list of elementary alarms affecting a managed resource. Contents PBB Fault Localization and navigation to AS
20-134
.................................................................................................................................................................................................................................... 1350 OMS 20-133 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management PBB Fault Management
PBB Fault Localization and navigation to AS
....................................................................................................................................................................................................................................
PBB Fault Localization and navigation to AS When to use
This function displays information about the fault present on the selected object. Related Information
The function is available for alarmed objects. For more information about Fault Localization, see: “Fault Localization” (p. 11-69). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Show the list of the objects. Select one of the following paths: •
Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. Select
backbone EVCs. • •
Search > Packet > Services > Connection Less (Bridge) > B-VIDs
•
Search > Packet > ERP > ERP Rings
Search > Packet > ERP > ERP Instances
...................................................................................................................................................................................................
2
Select an item in the list and select Search > Fault Localization. Result: The Fault Localization list window is displayed.
See the following topic in this document: “Fault Localization” (p. 11-69). The list is not refreshed automatically, click Actualize button to refresh it. ...................................................................................................................................................................................................
3
Select an item in the list and click Search > External Navigation to > AS . Result: The Fault Management window is displayed with the alarm list.
See the following topic in this document: “Description of the list of Alarms” (p. 19-69) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-134 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management
Overview about Workflow
....................................................................................................................................................................................................................................
Workflow for PBB Management Overview about Workflow Workflow description
The workflow to manage PBB is part of the more general workflow for the Ethernet Service management. Transport Link Overwiew
1350OMS does support the provisioning of the infrastructure in term of TDM Links, WDM and Ethernet cables and (T-)MPLS links. The infrastructure is used for different supported layer (T-)MPLS or Ethernet. The infrastructure is named Transport Link. The Transport Link can be supported by: • • • •
A TDM path. The link is called Link Over TDM. It carries directly Ethernet Segments, Tunnels or PWs. A Tunnel/PW. The link is called Link Over (T-)MPLS. A Link Over TDM or a Link Over Cable (Martini) carries it. An Ethernet cable or a Martini cable. The link is called Link Over Cable. A WDM link. The link is called Link Over WDM.
Domain overview
In Connection Less Networks, the Domain represents an homogeneous set of Network Elements dedicated to MAC, Virtual, Provider or Provider Backbone Bridging. A Domain infrastructure is made of NE, ENE, Transport Links and Edge Ports managed together to supply a Connection Less infrastructure. The user is requested to assign the NE to a specific domain. The NE related resources are automatically uploaded and associated to it. The user is requested to assign the Transport Link to a specific domain. The NE related resources are automatically uploaded and associated to it. Domain main properties are: •
•
the Domain Type: – ETS – Bridge – T-MPLS the Bridge Type: – MAC –
Virtual
.................................................................................................................................................................................................................................... 1350 OMS 20-135 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Workflow for PBB Management
Overview about Workflow
....................................................................................................................................................................................................................................
– – •
Provider Provider backbone Bridge
the Control Plane type: – ERP – STP – RSTP – PVSTP – –
MSTP none
Domain attribute dependencies: • •
The list of possible Bridge types depends on the selected Domain type The list of possible Control protocols depends on the selected Bridge type
•
In case of PBB the only possible choice for Control Protocol is ERP
.................................................................................................................................................................................................................................... 1350 OMS 20-136 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Workflow for PBB Management
Create a PBB Domain
....................................................................................................................................................................................................................................
Create a PBB Domain When to use
This function allows the user to define a domain in the managed network. Related Information
For information, see: “Overview about Workflow ” (p. 20-135). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Action > Packet > Construction > Create Domain. ...................................................................................................................................................................................................
2
On the Create Window. To create a customer: •
Enter a User Label.
•
Enter a Domain Type: Bridge.
•
Enter an Bridge Type: PBB.
•
Enter a Control Protocol Type: ERP.
...................................................................................................................................................................................................
3
Click Ok. Result: The domain is created.
The Domain list is updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-137 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Workflow for PBB Management
Add NE to a Domain
....................................................................................................................................................................................................................................
Add NE to a Domain When to use
The user assign a NE to a domain. Related Information
It is possible to assign a group of NE in a single operation. See Action > Packet > Construction > Assign Resources to Domain
For information, see: “Overview about Workflow ” (p. 20-135). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Construction > Network Elements > Defined NEs. ...................................................................................................................................................................................................
2
Select the NE in the list. ...................................................................................................................................................................................................
3
Follow the path Action > Network Element > Assign Network Element to Domain. Result: The assign window is displayed. ...................................................................................................................................................................................................
4
Click the Bridge Domain field. Result: The list of available bridge domain is displayed. ...................................................................................................................................................................................................
5
Select the PBB domain and Click the check sign to confirm it. ...................................................................................................................................................................................................
6
Click Ok. Result: The NE is assigned to the Domain previously created. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-138 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Workflow for PBB Management
Add Transport Link to a Domain
....................................................................................................................................................................................................................................
Add Transport Link to a Domain When to use
The user assign a Transport Link to a domain. Related Information
It is possible to assign a group of Transport Link in a single operation. See also Action > Packet > Construction > Assign Resources to Domain
When the user assigns Transport Links, the related NE are automatically uploaded and associated to the domain. For information, see: “Overview about Workflow ” (p. 20-135). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Search > Packet > Construction > Transport Link. ...................................................................................................................................................................................................
2
Select the object in the list. ...................................................................................................................................................................................................
3
Follow the path Action >Transport Link> Assign Transport Link to Domain. Result: The assign window is displayed. ...................................................................................................................................................................................................
4
Click the Bridge Domain field. Result: The list of available bridge domain is displayed. ...................................................................................................................................................................................................
5
Select the PBB domain and Click the check sign to confirm it. ...................................................................................................................................................................................................
6
Click Ok.
.................................................................................................................................................................................................................................... 1350 OMS 20-139 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Workflow for PBB Management
Add Transport Link to a Domain
....................................................................................................................................................................................................................................
Result: The NE is assigned to the Domain previously created. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-140 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Workflow for PBB Management
ERP provisioning
....................................................................................................................................................................................................................................
ERP provisioning When to use
The function defines an ERP instance. Related Information
For information, see: “Ethernet Ring Protocol (ERP)” (p. 20-10). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Action > ... > Create ERP. ...................................................................................................................................................................................................
2
Provisioning of ERP INSTANCE properties in the General tab: •
ERP instance User label.
•
comment.
•
Activation status [active/not active] (used to enable/disable the ERP protocol).
•
RING VLAN Tag (used to tag R-APS OAM protocol frames): – R-APS VLAN ID [1..4093] (unique per ring or group of interconnected rings). –
R-APS PCP [0..7] (priority bits value for R-APS).
•
Maintenance Entity Level [0..7] (OAM level assigned to R-APS).
•
Scope of ERP instance [port/VLAN].
•
RPL Owner (NE that has the master role on ERP instance).
•
RPL (East/west link that is Blocked by RPL owner in nominal conditions).
...................................................................................................................................................................................................
3
Provide the Protocol Tuning in the Detail tab: •
Switch behavior [Revertive/Not Revertive].
•
Wait Time to Restore [0..12 Minutes,steps of 1].
•
Hold-Off time [0..1000 millisec, steps of 10].
•
Guard Time [10..2000 millisec, steps of 10].
.................................................................................................................................................................................................................................... 1350 OMS 20-141 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Workflow for PBB Management
ERP provisioning
....................................................................................................................................................................................................................................
•
Optional Alarms that can be included/excluded in the list of Switch Criteria: – Signal Degrade. – Partial Loss of Capacity (if ring ports are LAG). – Loss Of Continuity (CCM) defect. –
Link OAM Critical Events.
•
Ring Port.
•
MEP.
Note: If Loss of Continuity defect or Link OAM Critical Events are used as Switch Criteria it is necessary to assign Down MEPs to Ring Ports (on all the NEs inside the ring). ...................................................................................................................................................................................................
4
Click Ok. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-142 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Workflow for PBB Management
Configure B-VID
....................................................................................................................................................................................................................................
Configure B-VID When to use
The function allows to define a B-VID in a PBB domain and to associate it to the ERP instance. Related Information
For information, see: “Ethernet Ring Protocol (ERP)” (p. 20-10). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Action > Packet > ... > Configure B_VID. Result: The configuration window is displayed. ...................................................................................................................................................................................................
2
Insert the following information: •
B-VID [1..4094]: service group identifier, unique network wide.
•
B-VID distribution:
•
–
Network-wide: B-VID is distributed on all the NEs in the PBB domain.
–
Crossed rings: B-VID is distributed on all the NEs of rings selected by user.
ERP instance, used to protect B-VID, is assigned for each crossed ring.
...................................................................................................................................................................................................
3
Click OK. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-143 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Workflow for PBB Management
Create a PBB EVC
....................................................................................................................................................................................................................................
Create a PBB EVC When to use
This function consists in creating a PBB Ethernet Virtual Connection. Related Information
For information about PBB EVC, see: “PBB Ethernet Virtual Connection” (p. 20-7). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the Multi Service GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Action > Packet > Services > Connection Less (Bridge) > Create Bridge EVC. Result: The creation window is displayed. ...................................................................................................................................................................................................
2
Fill the following data in the Specific panel: •
User label.
•
Service Type [EVPL, EPTL, EPL, EPLAN, EVPLAN, HSI, BTV, Broadcast].
•
Ethernet Service (optional): it is used to group together EVCs according to a user-selected criteria. Domain (PBB).
• •
Network Access Domain (optional): Network Access Domain (NAD) can be used to
partition the network into different administrative domains. A possible use is to limit the user to use only a set the of the network’s resources (NEs, ports, links). ...................................................................................................................................................................................................
3
Fill the following data in the Detail panel: •
I-SID [integer] (identifier of service, unique network wide).
•
B-VID [1-4094] (service group identifier, unique network wide).
•
Broadcast Domain Containment (Enabled, Disabled)
•
Set Standard VLAN type (0x8100) [True, False] (identifier for VLAN tagged frames at UNI).
.................................................................................................................................................................................................................................... 1350 OMS 20-144 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Workflow for PBB Management
Create a PBB EVC
....................................................................................................................................................................................................................................
• •
IGMP Snooping State [Not Meaningful, Enabled, Disabled] (to mark if IGMP
snooping is enabled/disabled on the EVC). Configure the Storm Control: Service frame delivery assumes one of the following values: Deliver unconditionally, Deliver conditionally, Discard. Fill the following fields: – Unicast Service Frame Delivery. –
Multicast Service Frame Delivery.
–
Broadcast Service Frame Delivery.
If selected values is “Deliver Conditionally” it is possible to specify the Limitation of rate (per service). ...................................................................................................................................................................................................
4
Select info panel. •
The user can use the fields in the info panel to enter comments or other information.
...................................................................................................................................................................................................
5
Select PM panel. •
Set or unset PM enabled
• •
Select Granularity (24 h, 15 min) Select Involved TPs (All Points)
•
Select CSV Reporting (No Report, 24 h, 2 h)
•
Select purge Policy (Keep, On stop, On delete)
...................................................................................................................................................................................................
6
Select OAM panel. •
Set OAM Enabled. (Enable, Disable). The enabling of Eth OAM: – creates a MA with identifier equal to the EVC user label with “MA_” prefix. – enables CC with default period of 1 second, no intermediate points (MIP).
•
Select Priority.
•
Select Maintenance Domain.
...................................................................................................................................................................................................
7
Select Miscellaneous panel. •
Select C-VLAN Preservation.
•
Select C-VLAN COS Preservation.
When checked, it ensures that each packet exiting the EVC (at some egress UNI) has the same VLAN Id & Priority Bits information that it had when it entered the EVC (at some ingress UNI). This Attribute must be defined at EVC definition and is modifiable before EVC allocation.
.................................................................................................................................................................................................................................... 1350 OMS 20-145 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Workflow for PBB Management
Create a PBB EVC
....................................................................................................................................................................................................................................
These two attributes are not meaningful for the relevant NEs. C-VLAN push/pop is configured on flow level. ...................................................................................................................................................................................................
8
Click Next Result: Figure 20-59 Create PBB EVC: Termination Selection
...................................................................................................................................................................................................
9
Select node and port for both originating and terminating sides. Click Next
.................................................................................................................................................................................................................................... 1350 OMS 20-146 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Workflow for PBB Management
Create a PBB EVC
....................................................................................................................................................................................................................................
Result: Figure 20-60 Create PBB EVC: Termination Settings
...................................................................................................................................................................................................
10
The folderTermination Setting defines the traffic flows. Select the first termination from the upper selection box. • • •
Click traffic descriptor button. Select the traffic descriptor from the selection box and confirm. Select the policy mode. If you select color aware, you will select color profile. Select the classification priority-code 0-7 / DSCP code 0-63.
•
Select VLAN POP disabled.
•
Folder traffic classifier deals on VLAN id.
.................................................................................................................................................................................................................................... 1350 OMS 20-147 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Workflow for PBB Management
Create a PBB EVC
....................................................................................................................................................................................................................................
• •
Folder Leaf Term deals on HSI. Folder Reuse Flows allows to copy and reuse flow characteristics.
...................................................................................................................................................................................................
11
Optionally you can setup Layer 2 Control Protocol. Figure 20-61 Ingress flow create
.................................................................................................................................................................................................................................... 1350 OMS 20-148 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Workflow for PBB Management
Create a PBB EVC
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
12
You can monitor that the Ingress flow has been created: the relevant traffic descriptor is displayed in the bottom of the window Figure 20-62 Ingress Flow: create monitoring
...................................................................................................................................................................................................
13
Select button Egress Flow, folder Push Select following data: • • •
Class of service (guaranteed/best effort/regulated,...) If you select clear all fields, subsequent fields can be ignored. VLAN ID. It is an additional ID added to the stack.
.................................................................................................................................................................................................................................... 1350 OMS 20-149 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Workflow for PBB Management
Create a PBB EVC
....................................................................................................................................................................................................................................
• •
Priority mode. If set to color aware fields green and yellow are active. Click Create Egress
You can monitor that the Egress flow has been created: the relevant traffic descriptor is displayed in the bottom of the window Figure 20-63 Egress Flow: Push
...................................................................................................................................................................................................
14
Create Ingress and Egress flows for the second termination. Click Next. ...................................................................................................................................................................................................
15
Select EVC state (implemented in this example).
.................................................................................................................................................................................................................................... 1350 OMS 20-150 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Workflow for PBB Management
Create a PBB EVC
....................................................................................................................................................................................................................................
Click OK to confirm EVC creation. Figure 20-64 EVC Allocate and Implement
.................................................................................................................................................................................................................................... 1350 OMS 20-151 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Workflow for PBB Management
Create a PBB EVC
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
16
To verify the successful creation, follow the path Search > Packet > Connection Less(Bridge) > Bridge EVC Figure 20-65 Search>Packet>Connection Less(Bridge)>Bridge EVC
Result: The Bridge EVC list is shown. Figure 20-66 Bridge EVC list
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-152 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Workflow for PBB Management
PBB EVC traffic classification
....................................................................................................................................................................................................................................
PBB EVC traffic classification When to use
For each EVC termination, user defines the traffic classification rules by associating a Traffic Classifier and QoS attributes. Related Information
For information, see: “PBB Ethernet Virtual Connection” (p. 20-7). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the menu path Action > Packet > Services > Create Traffic Classifier. ...................................................................................................................................................................................................
2
Specify classification rules based on: •
VLAN (single or range)
•
Priority bit (single or range)
•
IP DSCP (single or range)
•
Payload type
...................................................................................................................................................................................................
3
Specify QoS attributes: •
Policing mode [color blind, color aware, none]
•
Color profile (applicable if policing mode is color blind or color aware)
•
CoS and bandwidth profile are specified associating a Traffic Descriptor. See “Traffic Descriptor Definition” (p. 20-154)
...................................................................................................................................................................................................
4
Click Ok. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-153 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Workflow for PBB Management
Traffic Descriptor Definition
....................................................................................................................................................................................................................................
Traffic Descriptor Definition When to use
The Traffic Descriptors describes the characteristics of an Ethernet segment in term of Class of Service (CoS) and bandwidth. Related Information
For information, see: “Overview about Workflow ” (p. 20-135). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the path Action > Packet > Services > Create Traffic Descriptor. Result: The creation window is displayed. ...................................................................................................................................................................................................
2
On the Create Traffic Descriptor Window. To create a Traffic Descriptor: •
Enter a User Label.
•
Select the Class of Service (Best Effort, Guaranteed, Regulated, Regulated1, Regulated3, Regulated4, Guaranteed2, Background). Enter a CIR value (set automatically to '0' if the selected Class of Service is 'Best Effort'). Enter a PIR value. Enter a CBS value (set automatically to '0' if the selected Class of Service is 'Best Effort'). Enter a PBS value (if the selected Class of Service is 'Guaranteed', PBS value is automatically set to CBS value - but could be modified).
• • • •
...................................................................................................................................................................................................
3
Click Ok. Result: The Traffic Descriptor is created. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-154 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management Workflow for PBB Management
EVC Allocation and Implementation
....................................................................................................................................................................................................................................
EVC Allocation and Implementation When to use
To complete the Provider Bridge Workflow: create a Connection Less EVC, allocate, and implement it. Related Information
For information, see: “PBB Ethernet Virtual Connection” (p. 20-7). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main view: ...................................................................................................................................................................................................
1
Follow the menu path Search > Packet > Services > Connection Less (Bridge) > Bridge EVCs. Result: The Bridge EVC list window is displayed. ...................................................................................................................................................................................................
2
Select the EVC in the list and follow the path Action > Bridge EVC > Allocate. Result: The allocation window is displayed. ...................................................................................................................................................................................................
3
Click Ok. Result: The EVC is allocated.
The Provisioning State is changed to Allocated. ...................................................................................................................................................................................................
4
Select again the EVC in the list and follow the path Action > Bridge EVC > Implement. Result: The implementation window is displayed. ...................................................................................................................................................................................................
5
Click Ok. Result: The EVC is implemented.
The Provisioning State is changed to Implemented. E................................................................................................................................................................................................... N D O F S T E P S .................................................................................................................................................................................................................................... 1350 OMS 20-155 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management
Overview
....................................................................................................................................................................................................................................
In Band Management Overview Purpose
This section describes the procedure for the configuration of the In Band Management for the TSS160C and TSS10 Network Element in the PBB (Provider Backbone Bridge) Network when protected using the ERP protection schema. Contents Address Configuration of the Network Elements
20-157
Lag Port Creation (Via Zic)
20-165
NMS Start Supervision (NE Not Defined On NMS)
20-183
.................................................................................................................................................................................................................................... 1350 OMS 20-156 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Address Configuration of the Network Elements
....................................................................................................................................................................................................................................
Address Configuration of the Network Elements When to use
This function configures IP Address in the NE. Related Information Before you begin
The Network Element is correctly provisioned with the full set of boards required for the configuration of the PBB Core Network. Task
Using the ZIC configure the System ID, the LAN interface (if the NE is a Gateway NE) and (for TSS160C) enable the OSPF for the node. ...................................................................................................................................................................................................
1 Figure 20-67 TSS160C System ID Configuration
.................................................................................................................................................................................................................................... 1350 OMS 20-157 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Address Configuration of the Network Elements
....................................................................................................................................................................................................................................
From Communication > DCN Phys. If > IP Address menu open the view for the configuration of the System ID. ...................................................................................................................................................................................................
2 Figure 20-68 TSS160C System ID Configuration form
In the form fill the IP address field and the Subnet mask field.
.................................................................................................................................................................................................................................... 1350 OMS 20-158 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Address Configuration of the Network Elements
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
3 Figure 20-69 TSS160C Q LAN Configuration (Gateway NE)
If the TSS160C is a Gateway NE, configure and enable also the Q LAN Interface. From Communication > DCN Phys. If > LAN menu open the view and configure the Q LAN. Note the configuration: •
OSI Protocol (Disabled) (N)
•
Internet Protocol (Enabled) (Y)
•
Integrated ISIS (Disabled) (N)
•
• Proxy Address Resolution Protocol (Enabled) (Y)
•
• Channel (MNGPLANE)
•
• OSPF (Disabled) (N) (This parameter refers to the enabling of the OSPF protocol on the LAN interface and as far as we know no OSPF should be configured on that network)
.................................................................................................................................................................................................................................... 1350 OMS 20-159 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Address Configuration of the Network Elements
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4 Figure 20-70 TSS160C Export of the Route
Some network topologies could require the export of routes (or static route) between routing protocols. For example, may need to export the static route to OSPF. To enable the reporting of the routes between different protocol open the ULC view from Communication > OSI ULC Report menu.
.................................................................................................................................................................................................................................... 1350 OMS 20-160 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Address Configuration of the Network Elements
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
5 Figure 20-71 Tss160C OSI Routing Configuration
Once the view is opened enable the reporting you need. If no reporting is required set the parameters in the view as here depicted.
.................................................................................................................................................................................................................................... 1350 OMS 20-161 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Address Configuration of the Network Elements
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
6 Figure 20-72 TSS10 System ID Configuration
.................................................................................................................................................................................................................................... 1350 OMS 20-162 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Address Configuration of the Network Elements
....................................................................................................................................................................................................................................
From Communication > System IP Address menu, configure the System IP Address Figure 20-73 TSS10 System IP Address
.................................................................................................................................................................................................................................... 1350 OMS 20-163 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Address Configuration of the Network Elements
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
7 Figure 20-74 Tss10 LAN Interface Details
If the TSS10 is a Gateway NE, configure and enable also the Q LAN (LAN1) Interface. From Communication > DCN LAN Interface menu open the view and configure the LAN1. Note the configuration: •
Proxy Address Resolution Protocol (ARP) (Enabled) (Flagged on)
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-164 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Lag Port Creation (Via Zic)
....................................................................................................................................................................................................................................
Lag Port Creation (Via Zic) When to use
This function creates a LAG port. Related Information
For the NNI ports that are designed to carry on also the management frame, the LAG port (normally used NNI side to close the Ethernet Ring), must be configured by ZIC (enabling the In Band Management) and uploaded by the NMS once the NE is reachable (the upload is automatically performed during the NE Define action performed by PKT). Refer to the following procedures: •
“Task for TSS160C” (p. 20-166)
•
“Task for TSS160C V1.12.04” (p. 20-174)
• Before you begin
The Network Element is correctly provisioned with the full set of boards required for the configuration of the PBB Core Network.
.................................................................................................................................................................................................................................... 1350 OMS 20-165 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Lag Port Creation (Via Zic)
....................................................................................................................................................................................................................................
Task for TSS160C
TSS160C LAG Port Creation and Configuration: ...................................................................................................................................................................................................
1 Figure 20-75 TSS160C Link Aggregation Group Management
From the Link Aggregation Group Management tab, go to the bottom of the page and fill the fields related to: •
Size (e.g. 2)
•
Name (just the LAG ID, i.e. the numerical identifier) (e.g. 1)
•
Actor Admin Key (e.g. 1)
.................................................................................................................................................................................................................................... 1350 OMS 20-166 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Lag Port Creation (Via Zic)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
2
Once the LAG has been created, select the LAG port and set the Client Type as NNI: Figure 20-76 Tss160C LAG Configuration (Client Type)
.................................................................................................................................................................................................................................... 1350 OMS 20-167 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Lag Port Creation (Via Zic)
....................................................................................................................................................................................................................................
Set the Admin State of the port to enable. Figure 20-77 Tss160C LAG Configuration (Administration State)
.................................................................................................................................................................................................................................... 1350 OMS 20-168 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Lag Port Creation (Via Zic)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
3
Once the port has been enabled configure the In Band Management selecting the In Fiber In Band tab: Figure 20-78 Tss160C In Fiber In Band
.................................................................................................................................................................................................................................... 1350 OMS 20-169 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Lag Port Creation (Via Zic)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
Select Routing Protocol as ospf. Figure 20-79 Tss160C In Fiber In Band (OSPF)
.................................................................................................................................................................................................................................... 1350 OMS 20-170 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Lag Port Creation (Via Zic)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
5
Complete the configuration activating the interface Figure 20-80 Tss160C In Fiber In Band Activate
...................................................................................................................................................................................................
6
Bind the ports in the LAG repeating the following steps for each port that is designed to be member of the LAG:
.................................................................................................................................................................................................................................... 1350 OMS 20-171 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Lag Port Creation (Via Zic)
....................................................................................................................................................................................................................................
Select the local port and set the Client Type as linkagg. Figure 20-81 Tss160C port member of LAG
.................................................................................................................................................................................................................................... 1350 OMS 20-172 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Lag Port Creation (Via Zic)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
7
Click on Configure LAG link in order to open the view for the aggregation of the port to the LAG created before: Figure 20-82 Tss160C port member of LAG configuration
.................................................................................................................................................................................................................................... 1350 OMS 20-173 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Lag Port Creation (Via Zic)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
8
Once the view is opened select the Actor Admin Key of the LAG you want to associate: Figure 20-83 Tss160C port member of LAG Actor
Note: For the TSS160C V1.12.04, note the following: In that release the bind of the port (the action before) fails. In order to bind the ports with the LAG follows the special procedure provided by NE team. See “Task for TSS160C V1.12.04” (p. 20-174) E................................................................................................................................................................................................... N D O F S T E P S
Task for TSS160C V1.12.04
For the TSS160C V1.12.04 note the following: In that release the bind of the port (the action described in “Task for TSS160C” (p. 20-166)) fails. In order to bind the ports with the LAG follows the special procedure provided by NE team. ...................................................................................................................................................................................................
1
Connect to the CLI of the NE using the following command (by an PC or UNIX station that is able to reach the NE):
.................................................................................................................................................................................................................................... 1350 OMS 20-174 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Lag Port Creation (Via Zic)
....................................................................................................................................................................................................................................
telnet ip address of ne 1123 ...................................................................................................................................................................................................
2
Get the physical interface: Cli:admin > int sh Result:
Port InterfaceType ClientType ServiceStatus AdminStatus Traffic =========================================================================== r1sr1sl13d0p1 eth (6) linkagg (3) 0 down (2) down (2) r1sr1sl13d0p2 eth (6) ets (1) 0 down (2) down (2) r1sr1sl13d0p3 eth (6) linkagg (3) 0 up (1) up (1) r1sr1sl13d0p4 eth (6) linkagg (3) 0 up (1) up (1) r1sr1sl13d0p6 eth (6) pnp (5) 0 up (1) up (1) r1sr1sl13d0p7 eth (6) linkagg (3) 0 up (1) up (1) r1sr1sl13d0p8 eth (6) ets (1) 0 down (2) down (2) r1sr1sl13d0p9 eth (6) ets (1) 0 down (2) down (2) r1sr1sl13d0p10 eth (6) ets (1) 0 down (2) down (2) ...................................................................................................................................................................................................
3
Get the lag ports: Cli:admin > linkagg sh Result: lag AdminKey LAG User Label LAG Size Admin State ------- ----------- ---------------------------------------- -------1 1 '' 2 enable (1) 2 2 '' 2 enable (1) 3 3 '' 1 enable (1) ...................................................................................................................................................................................................
4
Bind the port (e.g. ‘r1sr1sl13d0p1’ with ‘lag1’): Cli:admin > linkagg port r1sr1sl13d0p1 bind lag1 Result: .. message: waiting - other CLI command in progress .. message: successful completed command ...................................................................................................................................................................................................
5
Logout from CLI:
.................................................................................................................................................................................................................................... 1350 OMS 20-175 8DG42227DAAA 9.6 Issue 3 December 2012
----
Provider Backbone Bridge Network Management In Band Management
Lag Port Creation (Via Zic)
....................................................................................................................................................................................................................................
Cli:admin > logout E................................................................................................................................................................................................... N D O F S T E P S
Task for TSS10
TSS10 LAG Port Creation and Configuration: ...................................................................................................................................................................................................
1 Figure 20-84 TSS10 Link Aggregation Group Management
From the Link Aggregation Group Management tab, go to the bottom of the page and fill the fields related to: •
Size (e.g. 2)
•
Name (just the LAG ID, i.e. the numerical identifier) (e.g. 1)
•
Actor Admin Key (e.g. 1)
•
Admin State to enable
•
EthClient Type to NNI
.................................................................................................................................................................................................................................... 1350 OMS 20-176 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Lag Port Creation (Via Zic)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
2
Once the port has been created enable the In Band Management: Figure 20-85 Tss10 Enable the In Band Management
.................................................................................................................................................................................................................................... 1350 OMS 20-177 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Lag Port Creation (Via Zic)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
3
Select the In-band Management tab and check the configuration (click on save if you need to modify the Management Plan Label) Figure 20-86 TSS60 In Fiber In Band Configuration
...................................................................................................................................................................................................
4
Bind the ports in the LAG repeating the following steps for each port that is designed to be member of the LAG:
.................................................................................................................................................................................................................................... 1350 OMS 20-178 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Lag Port Creation (Via Zic)
....................................................................................................................................................................................................................................
Select the local port and set the Client Type as LAG: Figure 20-87 Tss10 portInLAG
.................................................................................................................................................................................................................................... 1350 OMS 20-179 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Lag Port Creation (Via Zic)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
5
Click on Configure LAG link in order to open the view for the aggregation of the port to the LAG created before: Figure 20-88 Tss10 port member of LAG configuration
.................................................................................................................................................................................................................................... 1350 OMS 20-180 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Lag Port Creation (Via Zic)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
6
Once the view is opened select the Actor Admin Key of the LAG you want to associate: Figure 20-89 Tss10_portInLAGconfigActor
.................................................................................................................................................................................................................................... 1350 OMS 20-181 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
Lag Port Creation (Via Zic)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
7
Complete the configuration enablig the Admin State of the member port. Figure 20-90 Tss10_portInLAGadminState
Result: The configuration of the Network Element is now complete.
In order to reach the nodes from the NMS it is now required to configure the ip network in the ‘middle’ (between node and NMS) according to the DCN topology and the addresses plan. For a simple test, if the NMS is in the same sub network of the Q LAN interface of a gateway NE (e.g. a TSS160C), is possible to configure a static route on the NE (as explained before) and a static route on the NMS and verify if the node inside the ring are reachable from the NMS (ping). E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-182 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
NMS Start Supervision (NE Not Defined On NMS)
....................................................................................................................................................................................................................................
NMS Start Supervision (NE Not Defined On NMS) When to use
Use this function to start the Supervision on a Network Element. Related Information
This task does not have any related information. Before you begin
Create the Network Elements NE Manager side, set the right addresses and verify that NMS is able to reach the nodes in the ring. Task
Once the Network Elements are reachable via NMS, it is possible to start the Supervision. ...................................................................................................................................................................................................
1 Figure 20-91 NMS Start Supervision
.................................................................................................................................................................................................................................... 1350 OMS 20-183 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
NMS Start Supervision (NE Not Defined On NMS)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
2
Once the supervision starts, select the Nodes Physical Manager side and ask for Synchronize NE. Figure 20-92 NMS Synchronize NE
.................................................................................................................................................................................................................................... 1350 OMS 20-184 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
NMS Start Supervision (NE Not Defined On NMS)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
3
From the Physical Manager, if you need, you can add the node in the MAPs. Figure 20-93 NMS add Node In Map
.................................................................................................................................................................................................................................... 1350 OMS 20-185 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
NMS Start Supervision (NE Not Defined On NMS)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
From the Physical Manager, create the Physical Connections, one for each Link Member of the LAG. Figure 20-94 NMS Create Physical Connection
.................................................................................................................................................................................................................................... 1350 OMS 20-186 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
NMS Start Supervision (NE Not Defined On NMS)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
5
Here the Physical Connection Creation wizard of the Physical Manager: Figure 20-95 NMS Create Physical Connection wizard
Once the full set of Physical Connections related to the Links composing the LAG has been created, the next step is the definition of the nodes PKT side.
.................................................................................................................................................................................................................................... 1350 OMS 20-187 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
NMS Start Supervision (NE Not Defined On NMS)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
6
Select the node you need to define from the Available NE list of the PKT and ask for Define NE. Figure 20-96 NMS Define NE
.................................................................................................................................................................................................................................... 1350 OMS 20-188 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
NMS Start Supervision (NE Not Defined On NMS)
....................................................................................................................................................................................................................................
Result: During the Define NE operation the Ethernet Local Ports, the LAG Ports, and
the Physical Links (defined from the Physical Manager on the ports member of the LAGs) will be automatically uploaded. ...................................................................................................................................................................................................
7
For each node, ask for Ethernet Local Ports and verify the presence of the LAG port defined before via ZIC: Figure 20-97 NMS Ethernet Physical Port list
.................................................................................................................................................................................................................................... 1350 OMS 20-189 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
NMS Start Supervision (NE Not Defined On NMS)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
8
In order to build the Link Over LAG, select Action > Packet > Construction > Transport Link > Create LAG Link Over Cable From Ports as depicted in the snapshot: Figure 20-98 Create LAG Link over Cable
.................................................................................................................................................................................................................................... 1350 OMS 20-190 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
NMS Start Supervision (NE Not Defined On NMS)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
9
Select the nodes in the wizard, and the LAG ports extremities of the Link Over LAG and commit the creation: Figure 20-99 Create Link Over Cable
...................................................................................................................................................................................................
10
The Link Over LAG will be created using the LAG ports created before via ZIC and uploaded NMS side.
.................................................................................................................................................................................................................................... 1350 OMS 20-191 8DG42227DAAA 9.6 Issue 3 December 2012
Provider Backbone Bridge Network Management In Band Management
NMS Start Supervision (NE Not Defined On NMS)
....................................................................................................................................................................................................................................
Moreover it will refer to the Links built before using the Physical Manager (the links using as extremities the ports member of the LAG). Figure 20-100 NMS Link Over LAG list
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 20-192 8DG42227DAAA 9.6 Issue 3 December 2012
21
21 Broadcast TV Service Management
Overview Purpose
This chapter describes the BTV service emulation in the scope of Ethernet Connection Oriented and Connection Less management. Contents Section I: Introduction
21-3
Overview about Broadcast TV
21-4
Managing Broadcast TV Elements
21-5
View the list of Broadcast TV Elements
21-6
Create a BTV Element
21-8
Modify a BTV Element
21-11
Delete a BTV Element
21-14
View the details of the BTV Elements
21-16
Details of a BTV Elements
21-17
View the list of ETPs belonging to a BTV Element
21-18
Description of the list of BTV ENE inventory
21-19
Create an ETP in a BTV Element
21-20
Delete an ETP in a BTV Element
21-22
Section II: Workflow for BTV construction
21-24
Create path on 1350 OMS SDH application
21-25
Create Broadcast TV Element
21-26
Create Link Broadcast TV
21-29
Section III: Workflow for BTV Service Management
21-33
Create a Customer
21-34
Create Ethernet Service
21-35
Create a Connection Oriented EVC
21-37
................................................................................................................................................................................................................................... 1350 OMS 21-1 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management
Overview
....................................................................................................................................................................................................................................
Section IV: Bridge Based BTV Service
21-40
Overview about the Services
21-41
IGMP Snooping Management
21-42
IGMP Snooping State Management
21-44
.................................................................................................................................................................................................................................... 1350 OMS 21-2 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section I: Introduction
Overview
....................................................................................................................................................................................................................................
Section I: Introduction Overview Purpose
This section describes the BTV service emulation in the scope of Ethernet Connection Oriented management. Contents Overview about Broadcast TV
21-4
Managing Broadcast TV Elements
21-5
View the list of Broadcast TV Elements
21-6
Create a BTV Element
21-8
Modify a BTV Element
21-11
Delete a BTV Element
21-14
View the details of the BTV Elements
21-16
Details of a BTV Elements
21-17
View the list of ETPs belonging to a BTV Element
21-18
Description of the list of BTV ENE inventory
21-19
Create an ETP in a BTV Element
21-20
Delete an ETP in a BTV Element
21-22
.................................................................................................................................................................................................................................... 1350 OMS 21-3 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section I: Introduction
Overview about Broadcast TV
....................................................................................................................................................................................................................................
Overview about Broadcast TV Broadcast TV description
The user defines an EPLAN or an EVPLAN service. The choice depends on whether the SDH partially terminated path is shared or not with other services. The user is suggested to use the comment field to state that the service is a BTV service. The 1350 OMS PKT user defines an EVC belonging to an EPLAN or an EVPLAN service with the following characteristics: • •
Multipoint to multipoint. Unicast.
•
The EVC termination is chosen among the Ethernet Physical ports available on real NEs ending the SDH broadcast path.
The 1350 OMS PKT user defines a set of Ethernet Segments having common TD, TC, and Color Profile (if needed). The user is requested to define one Ethernet Segment for each Link Over TDM taking care about the assigned directionality: • •
For SDH broadcast path sources: each Ethernet Segment must start from a real NE and must end on the ENE playing the BTV role. For SDH broadcast path sinks: each Ethernet Segment must start from the ENE playing the BTV role and must end on a real NE.
Then, all built Ethernet Segments can be Allocated and Implemented, allowing the Broadcast traffic flowing. Note: Operations are in users hands. No specific congruence checks are performed by 1350 OMS PKT for EPLINE or EVPLINE services emulating BTV services.
.................................................................................................................................................................................................................................... 1350 OMS 21-4 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section I: Introduction
Managing Broadcast TV Elements
....................................................................................................................................................................................................................................
Managing Broadcast TV Elements Overview
The BTV Element management, part of the network construction, consists in: •
performing actions such as:
•
– creating, modifying, deleting BTV Elements. – creating, deleting ETPs. displaying BTV Element information such as: – – –
BTV Element list. ETP list. properties.
The BTV Element management chain gives the order in which the available actions can be performed. Figure 21-1 BTV Element management chain
.................................................................................................................................................................................................................................... 1350 OMS 21-5 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section I: Introduction
View the list of Broadcast TV Elements
....................................................................................................................................................................................................................................
View the list of Broadcast TV Elements When to use
The Broadcast TV Element list presents all the ENEs managed (that is, already defined) by the 1350 OMS PKT, and their attributes. Related information
For a description about BTV Elements, refer to the topic “Managing Broadcast TV Elements” (p. 21-5). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Construction > Network Elements > Defined External NEs. Result: The list window is shown. ...................................................................................................................................................................................................
2
Set the filter condition to Role=BTV and click Filter.
.................................................................................................................................................................................................................................... 1350 OMS 21-6 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section I: Introduction
View the list of Broadcast TV Elements
....................................................................................................................................................................................................................................
Result: The list window is shows all the available ENEs and their attributes according to the filter condition. Figure 21-2 Broadcast TV Element List window
The attributes displayed for each ENE are: • User Label. • •
Parent Subnetwork. ENE Role: BTV.
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 21-7 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section I: Introduction
Create a BTV Element
....................................................................................................................................................................................................................................
Create a BTV Element When to use
This function consists in making visible for the 1350 OMS PKT a NE or a set of NEs not managed by the 1350 OMS PKT. Related information
For a description about BTV Elements, refer to the topic “Managing Broadcast TV Elements” (p. 21-5). The user is authorized to create a BTV Element in the main parent subnetwork (called MEN by default). Not managed NE are NE contained in an adjacent subnetwork not accessible for the 1350 OMS PKT. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
Note: It is authorized to create BTV Element, as an ENE, in the main parent subnetwork (called MEN by default). To get a positive result: • • • •
The parent subnetwork must exist. The Table B-1, “Limits for Subnetworks” (p. B-1) in the selected subnetwork must not be reached. The Table B-5, “Limits for ENEs” (p. B-2) must not be reached. The User Label must be different as one which is already used by another ENE.
Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Action > Packet > Construction > Create External Network Element.
.................................................................................................................................................................................................................................... 1350 OMS 21-8 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section I: Introduction
Create a BTV Element
....................................................................................................................................................................................................................................
Result: Figure 21-3 Broadcast TV Element Creation window
...................................................................................................................................................................................................
2
To create an ENE: •
Enter a BTV Element User Label.
• •
Choose the Parent Subnetwork by using the sensitive help. Enter a Domain: choose a Provider Domain for BTV Service on Provider Bridge in Connection Less networks. Choose the ENE Role: BTV. Enter a Comment (optional).
• •
...................................................................................................................................................................................................
3
Click Ok.
.................................................................................................................................................................................................................................... 1350 OMS 21-9 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section I: Introduction
Create a BTV Element
....................................................................................................................................................................................................................................
Result: The BTV Element is created with an amount of ETPs, which are automatically created. See Table B-6, “Limits for ETPs in an ENE” (p. B-2)
The tree area, the BTV Element list and the opened graphical views are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 21-10 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section I: Introduction
Modify a BTV Element
....................................................................................................................................................................................................................................
Modify a BTV Element When to use
The function modifies BTV Element characteristics. Related information
For a description about BTV Elements, refer to the topic “Managing Broadcast TV Elements” (p. 21-5). The BTV Element modification gives the possibility to modify: • •
BTV Element User Label. Comment.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
If the User Label is modified, the new User Label must be different as one which is already used by another ENE.
Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Construction > Network Elements > Defined External NEs. Result: The list window is shown. ...................................................................................................................................................................................................
2
Set the filter condition to Role=BTV and click Filter. Result: The list window is shows all the available ENEs and their attributes according
to the filter condition. ...................................................................................................................................................................................................
3
Select an item in the list.
.................................................................................................................................................................................................................................... 1350 OMS 21-11 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section I: Introduction
Modify a BTV Element
....................................................................................................................................................................................................................................
Result: Figure 21-4 External Network Element Modification window
...................................................................................................................................................................................................
4
To modify BTV Element: •
Enter a New User Label (optional).
•
Modify the Comment (optional).
.................................................................................................................................................................................................................................... 1350 OMS 21-12 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section I: Introduction
Modify a BTV Element
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
5
Click Ok. Result: Then, the Broadcast TV Element list, the tree area, and the opened graphical
views are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 21-13 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section I: Introduction
Delete a BTV Element
....................................................................................................................................................................................................................................
Delete a BTV Element When to use
This function consists in deleting a BTV Element and its ETPs from the 1350 OMS PKT supervision. Related information
For a description about BTV Elements, refer to the topic “Managing Broadcast TV Elements” (p. 21-5). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The usage state of the ETPs belonging to the BTV Element must be idle.
Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Construction > Network Elements > Defined External NEs. Result: The list window is shown. ...................................................................................................................................................................................................
2
Set the filter condition to Role=BTV and click Filter. Result: The list window is shows all the available ENEs and their attributes according
to the filter condition. ...................................................................................................................................................................................................
3
Select one or more items in the list. ...................................................................................................................................................................................................
4
Select Action > from External Network Element > Delete or right-click the mouse and Select Delete. ...................................................................................................................................................................................................
5
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40).
.................................................................................................................................................................................................................................... 1350 OMS 21-14 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section I: Introduction
Delete a BTV Element
....................................................................................................................................................................................................................................
Result: After confirmation, the BTV Elements and their ETPs are removed.
The Broadcast TV Element list, the tree area, and the opened graphical views are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 21-15 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section I: Introduction
View the details of the BTV Elements
....................................................................................................................................................................................................................................
View the details of the BTV Elements When to use
This function gets information about a BTV Element. Related information
For a description about BTV Elements, refer to the topic “Managing Broadcast TV Elements” (p. 21-5). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Construction > Network Elements > Defined External NEs. Result: The list window is shown. ...................................................................................................................................................................................................
2
Set the filter condition to Role=BTV and click Filter. Result: The list window is shows all the available ENEs and their attributes according
to the filter condition. ...................................................................................................................................................................................................
3
Select the ENE in the list. ...................................................................................................................................................................................................
4
Select Search > Properties. Result: The ENE properties window is displayed.
See the following topic in this document: “Details of a BTV Elements ” (p. 21-17) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 21-16 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section I: Introduction
Details of a BTV Elements
....................................................................................................................................................................................................................................
Details of a BTV Elements Attributes of a BTV Element
The attributes displayed for each ENE are: •
User Label.
•
Parent Subnetwork.
•
Domain.
•
ENE Role: BTV.
•
Comment.
.................................................................................................................................................................................................................................... 1350 OMS 21-17 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section I: Introduction
View the list of ETPs belonging to a BTV Element
....................................................................................................................................................................................................................................
View the list of ETPs belonging to a BTV Element When to use
This function consists in displaying the External Termination Ports of a previously selected BTV Element and their attributes. Related information
For a description about BTV Elements, refer to the topic “Managing Broadcast TV Elements” (p. 21-5). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Construction > Network Elements > Defined External NEs. Result: The list window is shown. ...................................................................................................................................................................................................
2
Set the filter condition to Role=BTV and click Filter. Result: The list window is shows all the available ENEs and their attributes according
to the filter condition. ...................................................................................................................................................................................................
3
Select an item in the list. ...................................................................................................................................................................................................
4
Select Search > Inventory from External Network Element > ETP List. Result: The broadcast TV NE ETP list is displayed.
See the following topic in this document: “Description of the list of BTV ENE inventory” (p. 21-19) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 21-18 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section I: Introduction
Description of the list of BTV ENE inventory
....................................................................................................................................................................................................................................
Description of the list of BTV ENE inventory Attributes of an ETP
The attributes displayed for each ETP are: •
Identifier.
•
Transport Link.
•
Supported Layer (None, Ethernet, MPLS).
•
Interface Rate.
•
Usage State (Not meaningful, Idle, Busy).
•
Manager Control.
•
Client Type (ETS, ETB, ETS-P).
•
NAD.
.................................................................................................................................................................................................................................... 1350 OMS 21-19 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section I: Introduction
Create an ETP in a BTV Element
....................................................................................................................................................................................................................................
Create an ETP in a BTV Element When to use
This function consists in creating ETPs that represent Ethernet ports located in the selected BTV Element. Related information
For a description about BTV Elements, refer to the topic “Managing Broadcast TV Elements” (p. 21-5). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
In the ENE, the amount of ETPs must not exceed the maximum. See Table B-6, “Limits for ETPs in an ENE” (p. B-2) Note: When the BTV Element is created, the ETP is created by default.
Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Construction > Network Elements > Defined External NEs. Result: The list window is shown. ...................................................................................................................................................................................................
2
Set the filter condition to Role=BTV and click Filter. Result: The list window is shows all the available ENEs and their attributes according
to the filter condition. ...................................................................................................................................................................................................
3
Select an item in the list. ...................................................................................................................................................................................................
4
Select Action > External TP > Create ETP.
.................................................................................................................................................................................................................................... 1350 OMS 21-20 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section I: Introduction
Create an ETP in a BTV Element
....................................................................................................................................................................................................................................
Result: The ETP creation window is displayed. Figure 21-5 ETP Creation window
To create ETPs: • Enter the first ETP to create (That is a numerical value corresponding to the first ETP number to be used). • Enter the Number of ETP to create. Valid numerical value is between 1 and the Table B-6, “Limits for ETPs in an ENE” (p. B-2) which can be created on a ENE. See Table B-6, “Limits for ETPs in an ENE” (p. B-2) ...................................................................................................................................................................................................
5
Click Ok button. Result: The ETPs (added after the first ones automatically created at the ENE creation) are always created with Manager Control set to Disabled.
The ETPs are automatically generated by the 1350 OMS PKT and the ETP List is updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 21-21 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section I: Introduction
Delete an ETP in a BTV Element
....................................................................................................................................................................................................................................
Delete an ETP in a BTV Element When to use
This function consists in deleting ETPs from a previously selected BTV Element. Related information
For a description about BTV Elements, refer to the topic “Managing Broadcast TV Elements” (p. 21-5). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The usage state of the ETPs belonging to the ENE must be idle.
Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Construction > Network Elements > Defined External NEs. Result: The list window is shown. ...................................................................................................................................................................................................
2
Set the filter condition to Role=BTV and click Filter. Result: The list window is shows all the available ENEs and their attributes according to the filter condition. ...................................................................................................................................................................................................
3
Select an item in the list. ...................................................................................................................................................................................................
4
Select Search > Inventory from External Network Element > ETP List. Result: The ETP list window is shown. ...................................................................................................................................................................................................
5
Select one or more items in the list. ...................................................................................................................................................................................................
6
Select Action > External TP > Delete or right-click the mouse and Select Delete.
.................................................................................................................................................................................................................................... 1350 OMS 21-22 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section I: Introduction
Delete an ETP in a BTV Element
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
7
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: After confirmation, the ETPs are removed from BTV Element.
The ETP Inventory list is updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 21-23 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section II: Workflow for BTV construction
Overview
....................................................................................................................................................................................................................................
Section II: Workflow for BTV construction Overview Purpose
This section provides information about the workflow that is required for the BTV construction. Contents Create path on 1350 OMS SDH application
21-25
Create Broadcast TV Element
21-26
Create Link Broadcast TV
21-29
.................................................................................................................................................................................................................................... 1350 OMS 21-24 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section II: Workflow for BTV construction
Create path on 1350 OMS SDH application
....................................................................................................................................................................................................................................
Create path on 1350 OMS SDH application Overview
The first operation for BTV Service Management is the path creation on 1350 OMS SDH application. •
The Service Type is Ethernet.
•
The Service Rate is 1-Gb Rate Adaptive.
•
The Transport Rate is AU4-nV.
Figure 21-6 Path on 1350 OMS SDH
.................................................................................................................................................................................................................................... 1350 OMS 21-25 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section II: Workflow for BTV construction
Create Broadcast TV Element
....................................................................................................................................................................................................................................
Create Broadcast TV Element When to use
This function consists in making visible for the 1350 OMS PKT a NE or a set of NEs not managed by the 1350 OMS PKT. Related information
For a description about BTV Elements, refer to the topic “Managing Broadcast TV Elements” (p. 21-5). Not managed NE are NE contained in an adjacent subnetwork not accessible for the 1350 OMS PKT. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
Note: It is authorized to create an ENE in the main parent subnetwork (called by default). To get a positive result: • • • •
The parent subnetwork must exist. The Table B-1, “Limits for Subnetworks” (p. B-1)in the selected subnetwork must not be reached. The Table B-5, “Limits for ENEs” (p. B-2) must not be reached. The User Label must be different as one which is already used by another ENE.
Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Action > Packet > Construction > Create External Network Element.
.................................................................................................................................................................................................................................... 1350 OMS 21-26 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section II: Workflow for BTV construction
Create Broadcast TV Element
....................................................................................................................................................................................................................................
Result: Figure 21-7 Broadcast TV Element Creation window
...................................................................................................................................................................................................
2
To create an ENE: •
Enter a BTV Element User Label.
•
Enter a Domain: choose a Provider Domain for BTV Service on Provider Bridge in Connection Less networks. Choose the ENE Role: Broadcast TV. Enter a Comment (optional).
• •
...................................................................................................................................................................................................
3
Click Ok.
.................................................................................................................................................................................................................................... 1350 OMS 21-27 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section II: Workflow for BTV construction
Create Broadcast TV Element
....................................................................................................................................................................................................................................
Result: The BTV Element is created with an amount of ETPs, which are automatically created. See Table B-6, “Limits for ETPs in an ENE” (p. B-2)
The tree area, the BTV Element list and the opened graphical views are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 21-28 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section II: Workflow for BTV construction
Create Link Broadcast TV
....................................................................................................................................................................................................................................
Create Link Broadcast TV When to use
This function consists in defining a Link Over TDM for BTV. Related information
For a description about BTV Elements, refer to the topic “Managing Broadcast TV Elements” (p. 21-5). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Action > Packet > Construction > Create Link Broadcast TV.
.................................................................................................................................................................................................................................... 1350 OMS 21-29 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section II: Workflow for BTV construction
Create Link Broadcast TV
....................................................................................................................................................................................................................................
Result: The Link Over Broadcast TV creation window is displayed. Figure 21-8 Link Over TDM Broadcast TV Creation window
.................................................................................................................................................................................................................................... 1350 OMS 21-30 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section II: Workflow for BTV construction
Create Link Broadcast TV
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
2
To create a Link Over TDM Broadcast TV: •
Enter a Link User Label.
•
Enter a Comment (optional).
•
Select the Extremity A by using the sensitive help.
•
Select the Extremity A Termination by using the sensitive help (only the terminations with usage state equal to Idle are proposed). Select the Extremity Z by using the sensitive help. Select the Extremity Z Termination by using the sensitive help (only the terminations with usage state equal to Idle are proposed). Choose the Supported Layer: Ethernet. Choose the Transport Concatenation Rate: VC_4.
• • • • • • •
Enter the Concatenation level (priority which allows to increase the flexibility of SDH bandwidth management from 0 to 63). Insert the 1350 OMS SDH Path Id. Choose the Client Type: ETS. The 1350 OMS SDH Path Id is read from 1350 OMS SDH path window selecting the path > Show set attributes > Miscellaneous.
Figure 21-9 1350 OMS SDH Path Id
.................................................................................................................................................................................................................................... 1350 OMS 21-31 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section II: Workflow for BTV construction
Create Link Broadcast TV
....................................................................................................................................................................................................................................
The 1350 OMS SDH Path Id is assigned to every Link Over TDM created for the BTV Service. ...................................................................................................................................................................................................
3
Click Ok. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 21-32 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section III: Workflow for BTV Service Management
Overview
....................................................................................................................................................................................................................................
Section III: Workflow for BTV Service Management Overview Purpose
This section provides information about the workflow for BTV service management. Contents Create a Customer
21-34
Create Ethernet Service
21-35
Create a Connection Oriented EVC
21-37
.................................................................................................................................................................................................................................... 1350 OMS 21-33 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section III: Workflow for BTV Service Management
Create a Customer
....................................................................................................................................................................................................................................
Create a Customer When to use
This function allows the user to define the characteristics of the owner of one or more BTV Elements. Related information
After definition, the owner is permitted to use the services that are defined across the boundaries of the managed network. For a description about BTV Elements, refer to the topic “Managing Broadcast TV Elements” (p. 21-5). For a description about customers, refer to the topic “Customer description” (p. 18-8). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The User Label must be different from the existing ones.
Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Action > Packet > Services > Create Customer. Result: The Customer creation window is displayed.
To create a customer: • Enter a User Label. • Enter a Company (optional). • Enter an Address (optional). •
Enter a Comment (optional).
...................................................................................................................................................................................................
2
Click Ok button. Result: The customer is created.
The tree area and the Customer list are updated. E................................................................................................................................................................................................... N D O F S T E P S .................................................................................................................................................................................................................................... 1350 OMS 21-34 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section III: Workflow for BTV Service Management
Create Ethernet Service
....................................................................................................................................................................................................................................
Create Ethernet Service When to use
This function consists in creating an Ethernet Service related to a selected customer. Related information
For a description about BTV Elements, refer to the topic “Managing Broadcast TV Elements” (p. 21-5). For a description about customers, refer to the topic “Ethernet Service description” (p. 18-17). If the creation action is required from the Customer List, the Customer field of this creation window is automatically filled with the selected Customer. The Ethernet Service can also be created using the wizard. The wizard automatically create the Connection Oriented EVC associated to the service. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
A customer must exist.
•
The User Label must be different from the existing.
Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Action > Packet > Services > Ethernet Service Creation.
.................................................................................................................................................................................................................................... 1350 OMS 21-35 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section III: Workflow for BTV Service Management
Create Ethernet Service
....................................................................................................................................................................................................................................
Result: The Ethernet Service creation window is displayed. Figure 21-10 Create Ethernet Service
Execute the following steps: • Enter a Service User label. •
Select the Customer.
•
Select the Service Type: EVPLINE.
•
In the Comment field, the user indicates that the service is a BTV Service.
...................................................................................................................................................................................................
2
Click Ok button. Result: The Ethernet Service is created.
The tree area and the Ethernet Service list are updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 21-36 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section III: Workflow for BTV Service Management
Create a Connection Oriented EVC
....................................................................................................................................................................................................................................
Create a Connection Oriented EVC When to use
This function consists in creating an Ethernet Virtual Connection. Related information
For a description about BTV Elements, refer to the topic: “Managing Broadcast TV Elements” (p. 21-5). For a description about the Connection Oriented EVC, refer to the topic: “Overview about ETS Ethernet Virtual Connections” (p. 18-37). If this action is required from the Service List, the Ethernet Service field of the EVC Creation window, is filled with the service selected Service. To select the right Ethernet Service and EVC Type fields, report you to the Error! Reference source not found. If Termination part is not or partially filled, the user has the possibility to add EVC terminations from the Add EVC Termination menu. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
At least, one Ethernet Service must exist.
•
The User Label must be not in use.
• •
Only one Root termination is authorized. The EVC Type must be compatible with the service type of the associated Ethernet Service. The EVC Type must be compatible with the selected Traffic Type. The role of each EVC termination must be compatible with the EVC Type.
• • Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Action > Packet > Services > Connection Oriented (ETS) > Create EVC.
.................................................................................................................................................................................................................................... 1350 OMS 21-37 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section III: Workflow for BTV Service Management
Create a Connection Oriented EVC
....................................................................................................................................................................................................................................
Result: The Connection Oriented EVC creation window is displayed. Figure 21-11 EVC Any to any Creation window
.................................................................................................................................................................................................................................... 1350 OMS 21-38 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section III: Workflow for BTV Service Management
Create a Connection Oriented EVC
....................................................................................................................................................................................................................................
Execute the following steps: • Enter an EVC User Label. • Enter Ethernet Service. • Select a Type: Any to any. •
Select a Traffic Type: Unicast.
•
Select a Service Level (Premium, Gold, Silver, Bronze).
•
Enter a Comment (optional).
•
–
Enter an External Mark (optional). It can be used to identify external systems having relations with the EVC (for example an ownership). In Termination part, enter a list of EVC terminations by using Add EVC Termination button. Execute the following steps: Select the NE or ENE user label by using the sensitive help.
–
Select an Edge Port user label by using also the sensitive help.
–
Select the Role of the termination (Root, Leaf, or Both).
•
...................................................................................................................................................................................................
2
Click Ok button. Result: The EVC is created. ...................................................................................................................................................................................................
3
If EVC Type is Point to multipoint or Any to any, Ethernet Segments could be automatically created: In Ethernet part, if Create Ethernet box is selected, select a VLAN Model (Mapping or Tunneling). ...................................................................................................................................................................................................
4
Choose a Traffic Descriptor (by using the sensitive help). ...................................................................................................................................................................................................
5
If the chosen Traffic Descriptor is Regulated, choose a Color Profile (by using the sensitive help) which is associated to each Ethernet Segment. ...................................................................................................................................................................................................
6
Taking into account the EVC Type, the Traffic Type, the directionality, and the number of terminations provided, all the needed Ethernet Segments are automatically created. Result: The Connection Oriented EVC is created and the EVC list consequently
updated. The Ethernet Segment created directly from EVC must be allocated and implemented. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 21-39 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management
Overview
....................................................................................................................................................................................................................................
Section IV: Bridge Based BTV Service Overview Purpose
This section provides information about the Bridge based BTV Service. Contents Overview about the Services
21-41
IGMP Snooping Management
21-42
IGMP Snooping State Management
21-44
.................................................................................................................................................................................................................................... 1350 OMS 21-40 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section IV: Bridge Based BTV Service
Overview about the Services
....................................................................................................................................................................................................................................
Overview about the Services Workflow description
The management of Broadcast TV services, when the network is Connection Less based, is achieved by means of following steps: the building of Ethernet connectivity on the top of Provider Bridge and the optional configuration of IGMP Snooping on the desired Network Elements. The Workflow is the same as that explained in previous paragraphs “Section II: Workflow for BTV construction” (p. 21-24) and “Section III: Workflow for BTV Service Management” (p. 21-33) with following differences: • • •
the BTV Element is assigned to the domain created as provider. the EVC created is of type Connection Less. optionally the IGMP protocol can be configured as explained in following paragraph.
.................................................................................................................................................................................................................................... 1350 OMS 21-41 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section IV: Bridge Based BTV Service
IGMP Snooping Management
....................................................................................................................................................................................................................................
IGMP Snooping Management When to use
This procedure explains how to manage IGMP Snooping. Related information
The Internet Group Management Protocol (IGMP) is a protocol designed to connect users to a multicast tree for multimedia applications. IGMP is carried over IP. The IGMP Snooping is only supported on Domain where the Bridge Type of contained NEs is Provider, Virtual, or MAC Bridge. The IGMP Snooping is managed through navigation toward 1350 OMS EML. Each broadcast-channel supplier has one C-VLAN and one S-VLAN. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
The user workflow to manage IGMP snooping is: ...................................................................................................................................................................................................
1
Define the bridge domain and assign the 1850 TSS 320 equipment to the domain. ...................................................................................................................................................................................................
2
Choose one S-VLAN for each video-service supplier (the C-VLAN is chosen by the router). ...................................................................................................................................................................................................
3
Create the EVC for the video-service supplier. The EVC characteristics are: • •
Virtual resource sharing. Full-meshed VLAN distribution.
• • •
The S-VLAN identifying the video supplier. C-VLAN preservation is not mandatory (because of POP operation). The C-VLAN identifying the video supplier.
.................................................................................................................................................................................................................................... 1350 OMS 21-42 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section IV: Bridge Based BTV Service
IGMP Snooping Management
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
Add one EVC termination for each host or DSLAM served by the video supplier • •
Associate to the termination a Traffic Descriptor that selects the C-VLAN corresponding to the video supplier which the host is subscribed to. For each defined DSLAM, EVC termination can optionally provide the PUSH operation.
...................................................................................................................................................................................................
5
Add one EVC termination for the BSR • •
Associate to the termination a Traffic Descriptor that selects the C-VLAN of the video supplier3. For the defined BSR, EVC termination Must provide the POP operation.
...................................................................................................................................................................................................
6
Allocate and implement the EVC. ...................................................................................................................................................................................................
7
For each 1850 TSS 320 , start the navigation toward 1350 OMS EML: •
Enable the IGMP snooping for the video supplier S-VLAN.
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 21-43 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section IV: Bridge Based BTV Service
IGMP Snooping State Management
....................................................................................................................................................................................................................................
IGMP Snooping State Management IGMP Snooping reminder
This function is evolved to provide a reminder helping the management of services to enable the IGMP Snooping Protocol. This reminder is important to reach two main goals: • •
To remind the user to perform Navigation toward NEs only after having implemented the EVC supporting the IGMP Snooping. To remind the user to perform Navigation toward NEs before De-Implementing an EVC supporting the IGMP Snooping. This action also prevents errors during the de-implementation phase.
EVC Definition
At EVC definition level, the user can optionally define the value of igmpSnooping attribute. This operation is available only for EVPLAN, Extended EVPLAN, and BTV EVC types. In these cases, the possible values are: •
Enabled. Just to remind that the user has the intention to use the IGMP snooping
protocol on top of such EVC. Possible scenarios: – – •
To enable the IGMP snooping immediately after having implemented the EVC. To disable the IGMP snooping immediately before de-implemented the EVC.
Disabled. Just to remind that the user does not want to use the IGMP on that EVC.
EVC Implementation
When the user starts the EVC Implementation operation, and the attribute igmpEnabled is set to Enabled, a pop-up window is raised to remind the user to perform a navigation toward affected NE. This operation is available only for Extended EVPLAN and BTV EVCs. The pop-up window must be acknowledged by the user without further affect the implementation procedure. EVC De-Implementation
When the user starts the EVC De-Implementation operation and the attribute igmpEnabled is set to Enabled, a pop-up window is raised to remind the user to perform a navigation toward affected NE. This operation is available only for Extended EVPLAN and BTV EVC types.
.................................................................................................................................................................................................................................... 1350 OMS 21-44 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management Section IV: Bridge Based BTV Service
IGMP Snooping State Management
....................................................................................................................................................................................................................................
The pop-up window can be: • •
Acknowledged by the user with the option STOP the de-implementation procedure, letting the user complete all the needed navigation. Acknowledged by the user with the option CONTINUE the de-implementation procedure, when the user is aware that all Navigation Issues are already accomplished.
EVC Modification
The Attribute igmpEnabled can be modified in the following cases: •
The EVC ServiceType is EVPLAN, extended EVPLAN or BTV.
•
The EVC provisioningState can have any value. The following situations must be managed: – If the EVC is Implemented, the transition from Disable to Enable triggers the pop-up window. – If the EVC is Implemented, the transition from Enable to Disable triggers the second pop-up window. In all other cases, the modification of the igmpEnabled attribute is not allowed and an explicit exception is returned.
.................................................................................................................................................................................................................................... 1350 OMS 21-45 8DG42227DAAA 9.6 Issue 3 December 2012
Broadcast TV Service Management
IGMP Snooping State Management
....................................................................................................................................................................................................................................
.................................................................................................................................................................................................................................... 1350 OMS 21-46 8DG42227DAAA 9.6 Issue 3 December 2012
22
Network Supervision 22
Overview Purpose
This chapter describes how to manage alarms and performance monitoring. Contents Managing alarms
22-2
Overview about alarms
22-2
Alarms from ISA E/FE/GE board
22-3
Alarms from ISA ES1/4 board
22-4
Alarms from ISA ES16 board
22-6
Alarms or Events on SDH paths from 1350 OMS SDH
22-8
Alarm status management
22-9
Alarm correlation and generation toward AS Managing Fault Localization
22-11 22-12
Display the Fault Localization list
22-12
Description of Fault Localization
22-14
Manual Synchronization of Alarms on NE
22-15
Specific Behavior Client Signal Fail Alarm Management
22-16 22-16
................................................................................................................................................................................................................................... 1350 OMS 22-1 8DG42227DAAA 9.6 Issue 3 December 2012
Network Supervision Managing alarms
Overview about alarms
....................................................................................................................................................................................................................................
Managing alarms Overview about alarms Manage elementary alarms
1350 OMS PKT provides the following services to manage elementary alarms (see “Management Layers” (p. 11-5) and “Network architecture overview” (p. 11-7)): •
Current alarm management (with the history).
•
Fault Localization.
For every alarm raised, a specific clear is sent. In case of packet concatenation, only Packet GFP interface can generate alarms on TDM termination. Alarm probable cause
In the following, is given information about the probable cause of the alarm to understand their meaning and origin: •
LOS (Loss of Signal) alarm covers the defects that occur in the following cases: – Loss of electrical or optical power,. – Failed Auto-negotiation process (LOS defect),. – No synchronization (LOS defect),. – – –
• • • • •
No comma detection (LOF defect),. Card failure or card missing (ISA ES16),. URU alarm in case of incorrect manual provisioning of Ethernet accesses (ISA ES16). ISA NE raises a TSF (Trail Signal Failed) or DEG (trail signal Degraded) alarm after detecting a defect due to failed SDH VCs (TSF or TSD). ISA NE raises a PLM (Pay Load Mismatch) alarm after detecting an SDH VC problem (related to packet or virtual concatenation). ISA NE raises a GTM (GFP Type Mismatch) alarm after detecting a GFP format mismatch. ISA NE raises a LOF (Loss of Frame) alarm after detecting an Ethernet defect. ISA NE raises a CSF (Client Signal Failure) alarm when a failure is detected on one Customer Edge.
.................................................................................................................................................................................................................................... 1350 OMS 22-2 8DG42227DAAA 9.6 Issue 3 December 2012
Network Supervision Managing alarms
Alarms from ISA E/FE/GE board
....................................................................................................................................................................................................................................
Alarms from ISA E/FE/GE board Overview
In the following table is given the list of elementary alarms generated by ISA E/FE/GE boards and the mapping with elementary objects inside 1350 OMS SDH and 1350 OMS PKT. Such alarms must be managed through 1350 OMS SDH. Table 22-1
ISA E/FE/GE alarms
Alarm [Default severity = Path alarm ASAP]. Loss of GFP[MAJ].
Probable Cause.
Loss of frame.
NE object [1350 OMS PKT object]. GDataTransportCTPbid.
1350 OMS SDH Object. NAP.
[TDM termination]. AIS Alarm Indication Signal[NAL].
AIS.
GDataTransportCTPbid.
NAP.
SignalLabelMismatch[MAJ].
SignalLabelMismatch.
GDataTransportCTPbid.
Loss of Signal[MAJ].
Loss of Signal.
GMauTTP[Ethernet Port].
PORT.
URU on Physical Interface[MAJ].
Underlying Resource Unavailable.
GMauTTP[Ethernet Port].
PORT.
[TDM termination]. NAP.
[TDM termination].
.................................................................................................................................................................................................................................... 1350 OMS 22-3 8DG42227DAAA 9.6 Issue 3 December 2012
Network Supervision Managing alarms
Alarms from ISA ES1/4 board
....................................................................................................................................................................................................................................
Alarms from ISA ES1/4 board Overview
In the following table, the list of elementary alarms is given. These alarms are generated by ISA ES1/4 boards. The mapping with elementary objects inside 1350 OMS PKTis also given in the table. Such alarms must be managed directly from NE through SNMP. Table 22-2
ISA ES1/4 alarms or events
Alarm/Notif. [Default severity = Path alarm ASAP].
Board Release.
Loss of GFP[MAJ].
1.0.
TSF[MAJ].
1.0.
Probable Cause.
Loss of frame.
NE object. [1350 OMS PKT object].
GFP interface. [TDM termination].
Trail Signal Fail.
GFP interface. [TDM termination].
TSF[MAJ].
1.0.
Trail Signal Fail.
LAPS interface. [TDM termination].
Loss of Signal.
1.0.
Loss of Signal.
[MAJ].
ETHERNET Local. [Ethernet port].
GTM[MIN].
PLM[MAJ].
PLM[MAJ].
Notes.
1.0.
1.0.
1.0.
GFP Type Mismatch.
GFP interface.
Payload Mismatch.
GFP interface.
Payload Mismatch.
LAPS interface.
When the GFP interface is connected to an SDH Path, a correspondent alarm exists on SDH Path (NB: no SDH path alarm in case of SDH independence). When the LAPS interface is connected to an SDH Path, a correspondent alarm exists on SDH Path (NB: no SDH path alarm in case of SDH independence). It summarizes also URU (until URU is explicitly managed).
[TDM termination]. [TDM termination]. [TDM termination].
.................................................................................................................................................................................................................................... 1350 OMS 22-4 8DG42227DAAA 9.6 Issue 3 December 2012
Network Supervision Managing alarms
Alarms from ISA ES1/4 board
....................................................................................................................................................................................................................................
Table 22-2
ISA ES1/4 alarms or events
Alarm/Notif. [Default severity = Path alarm ASAP]. DEG[NAL].
Board Release.
1.0.
Probable Cause.
Degrade.
(continued) NE object. [1350 OMS PKT object].
GFP interface. [TDM termination].
DEG[NAL].
1.0.
Degrade.
LAPS interface. [TDM termination].
CSF.
1.2.
Client Signal Fail.
GFP interface. [TDM termination].
Notes.
When the GFP interface is connected to an SDH Path, a correspondent Bandwidth Reduced alarm exists on SDH Path (NB: no SDH path alarm in case of SDH independence). When the LAPS interface is connected to an SDH Path, a correspondent Bandwidth Reduced alarm exists on SDH Path (NB: no SDH path alarm in case of SDH independence). The CSF have to be always managed as it highlight problems in case of NE isolation and in case of SDH independence.
.................................................................................................................................................................................................................................... 1350 OMS 22-5 8DG42227DAAA 9.6 Issue 3 December 2012
Network Supervision Managing alarms
Alarms from ISA ES16 board
....................................................................................................................................................................................................................................
Alarms from ISA ES16 board Overview
In the following table is given the list of elementary alarms generated by ISA ES16 board and the mapping with elementary objects inside 1350 OMS PKT. Such alarms must be managed directly from NE (through SNMP). Table 22-3
ISA ES16 alarms or events
Alarm/Notif. [Default severity = Path alarm ASAP].
Board Release.
Loss of GFP[MAJ].
2.0.
TSF[MAJ].
2.0.
Probable Cause.
Loss of frame.
NE object. [1350 OMS PKT object].
GFP interface. [TDM termination].
Trail Signal Fail.
GFP interface. [TDM termination].
TSF[MAJ].
2.0.
Trail Signal Fail.
HDLC interface. [TDM termination].
TSF[MAJ].
2.0.
Trail Signal Fail.
LAPS interface. [TDM termination].
Loss of Signal.
2.0.
Loss of Signal.
[MAJ].
ETHERNET Local. [Ethernet port].
GTM[MIN].
Notes.
2.0.
GFP Type Mismatch.
When the GFP interface is connected to an SDH Path, a correspondent alarm exists on SDH Path (NB: no SDH path alarm in case of SDH independence). When the HDLC interface is connected to an SDH Path, a correspondent alarm exists on SDH Path (NB: no SDH path alarm in case of SDH independence). When the LAPS interface is connected to an SDH Path, a correspondent alarm exists on SDH Path (NB: no SDH path alarm in case of SDH independence). It summarizes also URU (until URU is explicitly managed).
GFP interface. [TDM termination].
.................................................................................................................................................................................................................................... 1350 OMS 22-6 8DG42227DAAA 9.6 Issue 3 December 2012
Network Supervision Managing alarms
Alarms from ISA ES16 board
....................................................................................................................................................................................................................................
Table 22-3
ISA ES16 alarms or events
Alarm/Notif. [Default severity = Path alarm ASAP]. PLM[MAJ].
PLM[MAJ].
PLM[MAJ].
DEG[NAL].
Board Release.
2.0.
2.0.
2.0.
2.0.
Probable Cause.
(continued) NE object. [1350 OMS PKT object].
Payload Mismatch.
GFP interface.
Payload Mismatch.
HDLC interface.
Payload Mismatch.
LAPS interface.
Degrade.
GFP interface.
[TDM termination]. [TDM termination]. [TDM termination]. [TDM termination].
DEG[NAL].
2.0.
Degrade.
HDLC interface. [TDM termination].
DEG[NAL].
2.0.
Degrade.
LAPS interface. [TDM termination].
CSF.
2.1.
Client Signal Fail.
Notes.
GFP interface. [TDM termination].
When the GFP interface is connected to an SDH Path, a correspondent Bandwidth Reduced alarm exists on SDH Path (NB: no SDH path alarm in case of SDH independence). When the HDLC interface is connected to an SDH Path, a correspondent Bandwidth Reduced alarm exists on SDH Path (NB: no SDH path alarm in case of SDH independence. When the LAPS interface is connected to an SDH Path, a correspondent Bandwidth Reduced alarm exists on SDH Path (NB: no SDH path alarm in case of SDH independence). The CSF have to be always managed as it highlight problems in case of NE isolation and in case of SDH independence.
.................................................................................................................................................................................................................................... 1350 OMS 22-7 8DG42227DAAA 9.6 Issue 3 December 2012
Network Supervision Managing alarms
Alarms or Events on SDH paths from 1350 OMS SDH
....................................................................................................................................................................................................................................
Alarms or Events on SDH paths from 1350 OMS SDH Overview
All SDH paths alarms are available on 1350 OMS SDH. Objects directly affected on 1350 OMS PKT are: • •
SDH Path,. Link Over TDM.
Table 22-4
SDH Path Alarm management
Alarm.
1350 OMS SDH Object.
Major.
Path.
Probable Cause.
TransportFailure.
Derived from alarms on 1350 OMS SDH element object. NAP,. Boundary CTP,. DATA PORT.
Major.
Path.
TransportIncomingFailure.
Boundary CTP.
Major.
Path.
ExBer.
NAP.
Major.
Path.
TransportOutgoingFailure.
Boundary CTP,.
Notes.
These three alarms contribute to the management of 1350 OMS SDH operational State.
DATA NAP. Minor.
Path.
BandwidthReduced.
DATA NAP.
Major.
PAth.
LCASProtocolError.
DATA NAP.
Useful to catch bandwidth reduction for path with packet concatenation.
.................................................................................................................................................................................................................................... 1350 OMS 22-8 8DG42227DAAA 9.6 Issue 3 December 2012
Network Supervision Managing alarms
Alarm status management
....................................................................................................................................................................................................................................
Alarm status management Overview
The following figure shows the 1350 OMS PKT entities affected by NE or 1350 OMS SDH alarms.
.................................................................................................................................................................................................................................... 1350 OMS 22-9 8DG42227DAAA 9.6 Issue 3 December 2012
Network Supervision Managing alarms
Alarm status management
....................................................................................................................................................................................................................................
Figure 22-1 Alarm status management
.................................................................................................................................................................................................................................... 1350 OMS 22-10 8DG42227DAAA 9.6 Issue 3 December 2012
Network Supervision Managing alarms
Alarm correlation and generation toward AS
....................................................................................................................................................................................................................................
Alarm correlation and generation toward AS Overview
The following figure is entirely related to 1350 OMS PKT and shows: •
how alarms or events are internally propagated,.
• •
which are the affected entities,. which objects generate alarms toward AS component.
Figure 22-2 Alarm correlation
.................................................................................................................................................................................................................................... 1350 OMS 22-11 8DG42227DAAA 9.6 Issue 3 December 2012
Network Supervision
Display the Fault Localization list
....................................................................................................................................................................................................................................
Managing Fault Localization Display the Fault Localization list When to use
This function consists in displaying alarms for a Link Over TDM, a Link Over Cable, an Ethernet Segment or an LSP Tunnel. Related information
See the following topic in this document:“Fault Localization” (p. 11-69). If the Entity Type is equal to TDM termination (Ethernet Port,Edge Port), Show Alarms command is not available. The 1350 OMS PKT displays up to 100 alarms. When the number of alarms is superior to 100, a confirmation box is displayed. After confirmation, the truncated list is displayed. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Conditions
To get a positive result: •
The Availability status of the entity must be either Degraded or In Failure.
Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select one of the following menus: •
Search > Packet > Construction > Transport Links > Links Over TDM (Sdh/Sonet).
•
Search > Packet > Construction > Transport Links > Links Over Cable.
•
Search > Packet > Services > Connection Oriented (ETS) > Ethernet Segments.
•
Search > Packet > MPLS > LSP Tunnels. Result: The list window is shown.
...................................................................................................................................................................................................
2
Select an item in the list.
.................................................................................................................................................................................................................................... 1350 OMS 22-12 8DG42227DAAA 9.6 Issue 3 December 2012
Network Supervision Managing Fault Localization
Display the Fault Localization list
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
3
Select Search > Fault Localization. Result: The list window is displayed.
See the following topic in this document: “Description of Fault Localization” (p. 22-14) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 22-13 8DG42227DAAA 9.6 Issue 3 December 2012
Network Supervision Managing Fault Localization
Description of Fault Localization
....................................................................................................................................................................................................................................
Description of Fault Localization Attributes of Fault Localization
The attributes displayed for each entity are: •
User Label.
•
Entity type.
•
Alarm / Availability State.
•
Specific Fault Date.
•
Probable Cause.
•
Operator Label
•
NE User Label
•
Global Alarm Date
.................................................................................................................................................................................................................................... 1350 OMS 22-14 8DG42227DAAA 9.6 Issue 3 December 2012
Network Supervision Managing Fault Localization
Manual Synchronization of Alarms on NE
....................................................................................................................................................................................................................................
Manual Synchronization of Alarms on NE When to use
This function allows the user to re-synchronize, on NE basis, all alarms currently existing on a given NE. The operation can be started by the user. Related information
See the following topic in this document:“Fault Localization” (p. 11-69). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Construction > Network Elements > Defined NEs. Result: The list window is shown. ...................................................................................................................................................................................................
2
Select the NE and issue Action > Network Elements > Alarm Synchronization. ...................................................................................................................................................................................................
3
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: If the operation is confirmed, all existing alarms for the selected NE are
resynchronized toward Fault Management application and inside 1350 OMS PKT application. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 22-15 8DG42227DAAA 9.6 Issue 3 December 2012
Network Supervision Specific Behavior
Overview
....................................................................................................................................................................................................................................
Specific Behavior Client Signal Fail Alarm Management When to use
This procedure explains how to manage Client Signal Fail. Related Information
Following conditions must be verified when the CSF alarm feature is activated: • • •
Service is EPLINE, built upon a single SDH path with transparent GFP or EPLAN emulating BTV services. ISA NE at extremities supports CSF alarms and consequent actions (ES1/4 1.2, ES16 2.1). Autonegotiation must be enabled on local ports (Reminder: Autonegotiation is not supported on GE interfaces. In consequence, CSF cannot be enabled if GE is involved). Note: No check is done by the 1350 OMS PKT from this point of view because everything is managed by the user during Navigation.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
The global scenario is in the following provided: ...................................................................................................................................................................................................
1
Select an Ethernet Service. ...................................................................................................................................................................................................
2
Retrieve Edge Ports terminating the Ethernet Service. Result: For each retrieved Edge Port, a Navigation toward 1350 OMS EML is started
to configure the CSF consequent Action (laser shut down enabled). ...................................................................................................................................................................................................
3
Retrieve the Transport Link used by the service.
.................................................................................................................................................................................................................................... 1350 OMS 22-16 8DG42227DAAA 9.6 Issue 3 December 2012
Network Supervision Specific Behavior
Client Signal Fail Alarm Management
....................................................................................................................................................................................................................................
Result: TDM terminations are retrieved.
For each retrieved TDM termination, a Navigation toward 1350 OMS EML is started to configure the CSF Capability Support (CSF bidirectional propagation). In case of BTV service emulation, the TDM termination interested to VC-AIS propagation are connected to Broadcast SDH path acting as Sources. After this scenario, GFP-CSF frame insertion (or VC-AIS propagation) and consequent actions are automatically configured on the PEs accordingly. ...................................................................................................................................................................................................
4
If the service is implemented or commissioned, the CSF feature and consequently action can be enabled or disabled. Service implementation. Result: CSF consequent action disabling (Mandatory for resetting the possible CSF
configuration, already present on the NE). CSF consequent action enabling. ...................................................................................................................................................................................................
5
If the service is de-implemented, the CSF feature and consequently action can be disabled. Result: CSF consequent action disabling.
Service de-implementation. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 22-17 8DG42227DAAA 9.6 Issue 3 December 2012
Network Supervision
Client Signal Fail Alarm Management
....................................................................................................................................................................................................................................
.................................................................................................................................................................................................................................... 1350 OMS 22-18 8DG42227DAAA 9.6 Issue 3 December 2012
23
Network Utilities 23
Overview Purpose
This chapter describes how to use NE audit, alignment, force alignment, reservation, and recovery. Contents Audit, Alignment, Reservation, Recovery
23-2
The AAR procedure
23-3
NE Audit tool
23-6
Results of Audit
23-8
Reservation tool
23-13
Align Up of Ethernet Domain Data
23-15
Start the audit, alignment, reserve procedure
23-16
Stop the audit, alignment, reserve procedure
23-17
View the list of auditable NEs
23-18
Description of the list of auditable NEs
23-19
Perform an audit on a NE
23-20
View the list of Audited NEs
23-22
Description of the list of Audited NEs
23-23
View the results of an audit
23-24
Perform an alignment on a NE
23-26
NE Alignment tool
23-27
Workflow to align up Ethernet Data
23-28
ISA Board Replacement Procedure
23-30
Perform a reservation on a NE
23-32
Restore procedure for ISA board
23-33
................................................................................................................................................................................................................................... 1350 OMS 23-1 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
Overview
....................................................................................................................................................................................................................................
Audit, Alignment, Reservation, Recovery Overview Purpose
This section provides information about the Audit, Alignment, Reservation, and Recovery. Contents The AAR procedure
23-3
NE Audit tool
23-6
Results of Audit
23-8
Reservation tool
23-13
Align Up of Ethernet Domain Data
23-15
Start the audit, alignment, reserve procedure
23-16
Stop the audit, alignment, reserve procedure
23-17
View the list of auditable NEs
23-18
Description of the list of auditable NEs
23-19
Perform an audit on a NE
23-20
View the list of Audited NEs
23-22
Description of the list of Audited NEs
23-23
View the results of an audit
23-24
Perform an alignment on a NE
23-26
.................................................................................................................................................................................................................................... 1350 OMS 23-2 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
The AAR procedure
....................................................................................................................................................................................................................................
The AAR procedure Maintain the consistency of the image of the network
The aim of these tools is to check and maintain the consistency between the network and the 1350 OMS PKT database. The utilities supplied are Audit, Alignment, and Force Alignment, and Reserve and Recovery. • • •
“Audit” (p. 23-3) is in charge of detecting the differences between the network and the databases. “Alignment” (p. 23-4) and “Force Alignment” (p. 23-4) are in charge to fix discrepancies between the network and the databases. “Reservation” (p. 23-4) and “Recovery” (p. 23-5) are in charge to re build in the database, objects created without 1350 OMS PKT or before 1350 OMS PKT installation.
The utilities apply on all the network, one or a set of subnetworks, one or a set of NE. The tools works into a session. The session begins with the Start command and ends with the Stop command. Start procedure: The user has the possibility to start an audit, an alignment, or a
reservation on one or more NEs. At the beginning of an audit, the selected NEs are locked. Locked entities are not modifiable. All the read-only operations are available. Stop procedure: At any time of the audit, alignment, reserve session, the user can close
the session. An “unlock” of the locked NEs is done. Audit
The Audit identify the differences between the NE MIB in the network and the database of the PKT. The Audit reports differences in a text file. The Audit performs comparison on a per-functional domain basis. For each domain comparison is done on a per-elementary object basis. The Audit applies on a NE or list of NEs. Only SNMP board can be Audited. The Audit builds a file that contains all managed entities presenting differences between the network and the database. Differences are detected by NE. The audit file contains: •
The objects that exist in the database but not in the NE.
• •
The objects that exist in NE but not in database. The objects present both in the database and in the NE but having different setting.
The result of the audit procedure is stored in a text file available to the user. The user is in charge to display the results and proceed with the operations of align, force align, reserve, or recovery. For details on Audit tool, refer to “NE Audit tool” (p. 23-6). .................................................................................................................................................................................................................................... 1350 OMS 23-3 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
The AAR procedure
....................................................................................................................................................................................................................................
Alignment
The user can activate the Alignment on the audited NEs. The Alignment procedure does not affect the traffic existing on the network. The alignment procedure downloads to the network the entities contained in 1350 OMS PKT database and not contained in the NE. Force Alignment
The user can activate the Force Alignment on the audited NEs. The Force Alignment procedure affect the traffic existing on the network. The Force Alignment: • • •
Adds to NE the entities contained in 1350 OMS PKT database and not contained in the NE. Deletes the objects in the NE not contained in 1350 OMS PKT. Updates in the NE the objects presenting discrepancies in respect to the 1350 OMS PKT setting.
The Force Alignment aligns the characteristics of Transport Link, Traffic Descriptors, Traffic Classifiers, cross connections, LERconnections, and LSR connections. The specific data, like indexes, related to the NE and stored only in the 1350 OMS PKT database are update in the database. Reservation
The user can activate the Reservation on the audited NEs. Objects created without 1350 OMS PKT are not in the database, however they exist in the network and have resources associated. Reservation prevents the user from using network resources that are in-use but not already known by the 1350 OMS PKT. The network resources (terminations, MPLS labels, Transport Link bandwidth) are reserved. This reservation is visible by the operator by the fact that one or more terminations are no more available for creating new paths (Ethernet Segments, LSPs), and by a portion of reserved bandwidth consumed on the Transport Links. The associated objects are created inside the database (Traffic descriptors (MPLS and Ethernet), Traffic Classifier, Colour Profiles, Ethernet cross connections, LSR connections, and LER connections). A part from the connections, those objects are visible and usable by the operator after the reservation phase. The Reserve provides the discovery of an existing Ethernet network: •
NE and Ethernet physical ports.
•
Link Over TDM (supporting directly Ethernet or MPLS) and TDM termination points.
The NEs are retrieved defining the EML to which 1350 OMS PKT is connected and by 1350 OMS SDH (for E/FE/GE Q3 boards). .................................................................................................................................................................................................................................... 1350 OMS 23-4 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
The AAR procedure
....................................................................................................................................................................................................................................
This information is stored in 1350 OMS PKT database. This information is available for MPLS infrastructure or directly for Ethernet Service usage (Link Over TDM for Ethernet Segments and Ethernet physical ports). MPLS infrastructure is Link Over TDM devoted to MPLS. Ethernet Service usage involves Link Over TDM, Ethernet Segments, and Ethernet physical ports. Note: The Ethernet physical port can be used also to build the cable (or Martini cable or Ethernet cable). For details on Reservation tool, refer to “Reservation tool” (p. 23-13). Recovery
The user ask the Recovery on the reserved NE. The connectivity entities (like Ethernet Segments or MPLS LSP Tunnel) are built and then the discovered connectivity entities are stored in 1350 OMS PKT database. The LSP tunnel and VC-LSP are defined and allocated. The Ethernet Segments and EVCs are defined and allocated. The abstract objects are recovered inside the database. The paths are automatically created. Final provisioning state of LSPs and Ethernet Segment is commissioned. A minimum EVC, Ethernet services and Customers are created for holding the recovered Ethernet Segments. The user can be asked to help the system to recover managed connectivity when complex objects are not automatically recoverable by the system.
.................................................................................................................................................................................................................................... 1350 OMS 23-5 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
NE Audit tool
....................................................................................................................................................................................................................................
NE Audit tool Overview
The NE MIB Audit function available from 1350 OMS PKT can basically detect and then report two categories of misalignments: •
“Delta+” misalignments. “Delta+” misalignments refer to resources existing in 1350 OMS PKT DB but not in the NE MIB. The case occurs when 1350 OMS PKT implements Ethernet Services on a given ISA Board and then the Board itself must be replaced. The case occurs also when a MIB restore is launched to recover a previously stored MIB Backup. Alternatively, the case occurs when 1320CT and 1350 OMS EML users remove services or resources previously provisioned by 1350 OMS PKT.
•
“Delta-” misalignments. “Delta-” misalignments refer to resources existing in the NE MIB but not in 1350 OMS PKT DB. The case occurs when 1350 OMS PKT de-implements Ethernet Services on a given ISA Board and then the Board itself is replaced. The case occurs also when a MIB restore is launched to recover a previously stored MIB Backup. Alternatively, the case occurs the case when 1320CT and 1350 OMS EML users create new services or resources (bypassing security controls).
•
“Delta” misalignments. “Delta” misalignments refer to resources existing in both NE MIB and 1350 OMS PKT DB, but with different attribute values. The case occurs when 1320CT and 1350 OMS EML modify directly services or resources in the NE MIB bypassing security mechanism.
Recovery of the misalignments
If a misalignment exists between the 1350 OMS PKT and NEs, the audit feature provides the user with a means to detect. This situation happens in different cases: •
At installation time of the 1350 OMS PKT upon an existing network.
•
After a long period during which the 1350 OMS PKT has been disconnected from the network. After the local access control (LAC) has been granted on a NE. If the network has been configured without using the 1350 OMS PKT, operating the 1350 OMS EML or the Craft Terminal directly.
• •
The Audit operation consists in comparing the content of the NE MIB with the content of the 1350 OMS PKT database. The user selects one or more NEs and requests the audit. .................................................................................................................................................................................................................................... 1350 OMS 23-6 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
NE Audit tool
....................................................................................................................................................................................................................................
On the basis of the NE data uploaded from the NE MIB and the NE data stored in the database, the 1350 OMS PKT performs a comparison. The differences are classified as follow: 1. Data existing in the NE and missing in 1350 OMS PKT. 2. Data missing in the NE and existing in 1350 OMS PKT. 3. Different data using the same resources in NE and 1350 OMS PKT. The result of the audit procedure is stored in a text file that is made available to the user. On the basis of the information provided in the text file, the user can proceed with one of the following operations: • •
Display the audit result. Reservation-Recovery to resume the situation described in 1.
•
Alignment to resume the situation described in 2.
•
Forced alignment to resume the situation described 3. Alternatively the situation can be resumed as follow: the user can directly manage the conflict operating the 1350 OMS EML or the Craft Terminal.
When an audit is started on a NE, this NE is locked to avoid any modification of its MIB during the procedure life time. On a locked NE: • • • •
It is impossible for any user to delete this NE. Another audit session cannot work with this NE. One NE can be locked only by one audit. From outside the audit, alignment, reserve procedure is impossible to download or upload information into or from the NE MIB. from any session is possible to do any other operation (for example: display properties, allocate Ethernet Segment, create traffic profile …).
The “locked NE” information is stored in database. At the end of the procedure, the NEs locked in this procedure are unlocked. The audit result is stored in a text file in XML format.
.................................................................................................................................................................................................................................... 1350 OMS 23-7 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
Results of Audit
....................................................................................................................................................................................................................................
Results of Audit Per domain comparison
Here are the domains compared during an audit (and for each domain, a list of concerned entities and their compared attributes): •
“Construction domain” (p. 23-8).
•
“Ethernet domain” (p. 23-8).
•
“MPLS domain” (p. 23-10).
•
“T-MPLS domain” (p. 23-11).
Construction domain
Attributes for Construction domain: •
•
•
Attributes of TDM terminations entities: – TDM termination User Label. –
Protocol type.
–
Supported layer.
Attributes of Ethernet Physical Ports entities: – Port User Label. –
Interface type.
–
Interface rate.
–
Duplex mode.
–
Auto Negotiation State.
–
Supported layer.
–
Aggregation Id.
– –
Aggregation Ports. Client type .
Attributes of Network Element entity – Bridge type.
Ethernet domain
Attributes for Ethernet domain: •
•
Attributes of interfaces entities for Edge ports and Ethernet end points: – Interface MIB index. –
Effective bandwidth.
–
Activation status (interface status).
–
VLAN Tag Protocol Type .
Attributes of Traffic Descriptors: –
Identifier.
–
COS.
.................................................................................................................................................................................................................................... 1350 OMS 23-8 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
Results of Audit
....................................................................................................................................................................................................................................
•
•
– –
CIR.
– –
CBS. PBS.
Attributes of Traffic Classifiers entities: – Inflow Identifier. –
Classifier Identifier.
–
VLAN Identifier.
–
VLAN Max.
–
Priority.
– Priority MAX. Color Profiles entities – Color Profile MIB index. –
•
PIR.
Color for priority 0 to 7.
Attributes of Connections, for Inflow: –
Inflow Identifier.
–
Inflow Service type.
–
Inflow Interface index (only if In Service type equal to Ethernet),.
– Inflow MPLS Tunnel index (only if In Service Type equal to MPLS),. – Inflow MPLS Tunnel instance (only if In Service Type equal to MPLS). Attributes of Traffic entities for Inflow: – Traffic Descriptor Identifier. –
Connection cast type.
–
Policy Mode.
–
Color Profile Identifier.
–
VLAN Pop,.
– VLAN push (VLAN Id, Priority mode, Green priority, Yellow priority),. – the “In” and “Out” connection extremities information couple attributes. Attributes of Connections, for Outflow: –
Outflow Identifier.
–
Outflow Service type.
– Outflow Interface index (only if Out Service type equal to Ethernet). – Outflow MPLS Tunnel index (only if Out Service Type equal to MPLS). – in MPLS Tunnel instance (only if Out Service Type equal to MPLS). Attributes of Connections entities for Traffic Descriptor –
Traffic Descriptor MIB index.
–
Traffic type (cast type).
–
Policy mode.
–
Color Profile.
.................................................................................................................................................................................................................................... 1350 OMS 23-9 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
Results of Audit
....................................................................................................................................................................................................................................
– –
VLAN Pop.
–
the “In” and “Out” connection extremities information couple attributes.
VLAN push (VLAN Id, Priority mode, Green priority, Yellow priority).
MPLS domain
Attributes of MPLS domain: •
•
•
•
Attributes of MPLS Interfaces entities –
Interface identifier.
–
Label.
–
Service Type.
–
Effective bandwidth.
–
Static MPLS label range (min and max integers).
–
Activation status (up or down).
Attributes of Traffic Descriptors entities – Traffic Descriptor MIB index. –
Traffic type or Qos (BE, EF, AF, traffic parameters (PIR, CIR, PBS, CBS).
–
Activation status (up or down).
Attributes of LSP tunnel cross connections entities – LSP tunnel identifier. –
MIB indexes (tunnel index and tunnel instance).
–
Type (LSR,LER Ingress, LER Egress).
–
Connection role.
–
Traffic Descriptor MIB index.
–
Cast type.
– –
Policy mode (enabled, disabled).
–
Ingress lower MPLS label.
–
Egress termination identifier.
–
Egress lower MPLS label.
–
Activation status (up or down).
Ingress termination identifier.
For VC-LSP LER connections, the entities are: – VC-LSP identifier. – – – – –
MIB indexes (tunnel index and tunnel instance). Type (LER Ingress or LER Egress). Traffic Descriptor MIB index. Cast type. Policy mode (enabled, disabled).
.................................................................................................................................................................................................................................... 1350 OMS 23-10 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
Results of Audit
....................................................................................................................................................................................................................................
– –
LER connection (termination identifier, Lower PLS label, Upper MPLS label). Activation status (up or down) attributes.
T-MPLS domain
Attributes of T-MPLS domain: •
•
•
•
•
•
Attributes of Nodes: –
Egressing PHB profile.
–
Five Classes.
Attributes of Ports: –
Access ID.
–
Administrative State.
Attributes of T-MPLS Segments: –
Access ID.
–
Administrative State.
–
Segment Dir.
–
Trail Layer.
–
Traffic Descriptor MIB index.
–
In Label.
–
Out Label.
–
Mep Enabling.
Attributes of Cross Connections: –
Access ID.
–
Administrative state.
–
Segment Dir.
– Trail Layer. Attributes of Node TD: –
Access Id.
–
COS.
–
CIR.
–
PIR.
–
CBS.
–
PBS.
Attributes of Mep: –
Access ID.
–
Cv TX.
–
Cv RX.
.................................................................................................................................................................................................................................... 1350 OMS 23-11 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
Results of Audit
....................................................................................................................................................................................................................................
•
Attributes of Protection Groups: – Access ID. – HoldOffTime. – RevertTime.
.................................................................................................................................................................................................................................... 1350 OMS 23-12 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
Reservation tool
....................................................................................................................................................................................................................................
Reservation tool Overview
The reservation operation prevent the use of resources and allow the Recovery tool to insert in the 1350 OMS PKT database the resources discovered in the NE MIB and not present in the 1350 OMS PKT database: • •
Traffic Descriptors. Traffic Classifiers.
• • •
Color Profiles. Ethernet connections. MPLS connections.
Reservation for Ethernet domain
Reservation operation is in charge of reserving Traffic Descriptors, Color Profiles, Traffic Classifiers, and Ethernet cross connections. Entities present in the NE MIB but not known by 1350 OMS PKT, are imported into the 1350 OMS PKT with the special status of “reserved”. The status of “reserved” is used in the Recovery phase to rebuild Ethernet flows and services. All the entities marked as “reserved” are not visible to the user, except for Traffic Descriptors, Color Profiles, and Traffic Classifiers. They are immediately available to the user that can use them. The recovered entities, even if they are associated to flow on the NE (that is not provisioned by the 1350 OMS PKT), are not considered “in use”. For example, they can be deleted from the 1350 OMS PKT without affecting the NE. For Traffic Descriptors, Color Profiles, and Traffic Classifiers no duplicates are created. If a Traffic Descriptor recovered has the same of a Traffic Descriptor that exists into the 1350 OMS PKT, the latter entity is reused. The former one is associated to it. Traffic Descriptor attributes are CoS, CIR, PIR, CBS, PBS. Reservation for MPLS domain
Reservation operation is in charge of reserving MPLS Traffic Descriptors, LSP Tunnels connections, and VC-LSP connections. The NE MIB resources which have not been uploaded, are stored in the 1350 OMS PKT database. The 1350 OMS PKT resources are affected with the consumption of these resources. The user can recover and use the Traffic Descriptor used or not used by connections. The deletion of the Traffic Descriptor removes it from the 1350 OMS PKT database but leave it in the NE. A default user label is generated by the MPLS recovery component.
.................................................................................................................................................................................................................................... 1350 OMS 23-13 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
Reservation tool
....................................................................................................................................................................................................................................
In the LSP Tunnel connections, the used MPLS labels are marked reserved for the Transport Link in the 1350 OMS PKT database. If two connections at the extremities of the path share the same MPLS label, the MPLS label consumed only once. The consuming bandwidth is affected on the corresponding Transport Links. For an LSR, the Transport Links affected are two. For a LER, the Transport Link affected is one. If two connections at the extremities of the path concern the same Transport Link bandwidth is consumed only once. In the VC-LSP connections, the used MPLS labels are marked “reserved” for the Transport Link in the 1350 OMS PKT database. If two connections at the extremities of the same LSP tunnel share the same MPLS label, the MPLS label is consumed only once. The consuming bandwidth is affected on the corresponding LSP tunnel or Transport Link. If two connections at the extremities of the same LSP tunnel share the same Transport Link, the bandwidth is consumed only once.
.................................................................................................................................................................................................................................... 1350 OMS 23-14 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
Align Up of Ethernet Domain Data
....................................................................................................................................................................................................................................
Align Up of Ethernet Domain Data Overview
The Align Up function allows a selective (user driven) realignment between 1350 OMS PKT and NE content. The scope of this function is generic and can be applied in the contexts: • •
after a Network Manager migration to import from NE (overwriting data in the 1350 OMS PKT) the running value of the introduced Attribute. on user demand.
In both cases, the Audit function invocation is a necessary precondition. The function must carefully handle mismatch case. The updating inside 1350 OMS PKT forces the recomputation of EVC, Ethernet Segment, STI provisioning state, and the Transport Link Configuration State. The Align Up operation does not create nor delete new entities inside the 1350 OMS PKT Ethernet database but is only aimed to align attributes. As example see the following case. Suppose that the Activation state of an Edge Port is UP inside 1350 OMS PKT and the same port is DOWN inside the NE. After the Align Up, the Edge Port results with Activation State equal to DOWN also inside 1350 OMS PKT. This status change must be propagated also toward Ethernet connections which are using such Edge Ports (that is Ethernet Segments and/or EVCs). The Align Up function is only applicable on a NE after having performed an Audit on that NE. In particular, the Align Up function can be invoked only inside an AAR context (that is with the corresponding NE locked). After the Audit execution, the Audit result reports to the user all the differences existing between the NE image and the 1350 OMS PKT image. The user can then start the Align Up operation and can decide which objects must be aligned inside 1350 OMS PKT.
.................................................................................................................................................................................................................................... 1350 OMS 23-15 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
Start the audit, alignment, reserve procedure
....................................................................................................................................................................................................................................
Start the audit, alignment, reserve procedure When to use
This function consists in preparing the 1350 OMS PKT to perform audit, alignment, reserve actions. Related information
For a description about Audit, Alignment, and Reservation, refer to the topic “The AAR procedure ” (p. 23-3). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Action > Packet > Audit Align Reserve > Start AAR Procedure. ...................................................................................................................................................................................................
2
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: If the operation is confirmed, a lock of NEs is done just before starting the
audit procedure until the end of audit, alignment, reserve procedure. Once the audit, alignment, reserve procedure is started, in Action > Packet > Audit Align Reserve menu, the following commands are available: •
Network Elements for Audit.
•
Audited Network Elements.
•
Stop Procedure.
All the other 1350 OMS PKT functions are available. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 23-16 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
Stop the audit, alignment, reserve procedure
....................................................................................................................................................................................................................................
Stop the audit, alignment, reserve procedure When to use
This function consists in ending the audit, alignment, reserve procedure. Related information
For a description about Audit, Alignment and, Reservation, refer to the topic “The AAR procedure ” (p. 23-3). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. The AAR procedure must be started “Start the audit, alignment, reserve procedure” (p. 23-16). Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Action > Packet > Audit Align Reserve > Stop AAR Procedure. ...................................................................................................................................................................................................
2
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: If the operation is confirmed, the audited NEs are unlocked. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 23-17 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
View the list of auditable NEs
....................................................................................................................................................................................................................................
View the list of auditable NEs When to use
The function presents all the NEs that are available for audit. Related information
For a description about Audit, Alignment and, Reservation, refer to the topic “The AAR procedure ” (p. 23-3). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Audit Align Reserve. Result: The Audit Align Reserve menu is displayed. ...................................................................................................................................................................................................
2
Select NE for Audit. Result: The Auditable Network Element list window is displayed.
See the following topic in this document: “Description of the list of auditable NEs” (p. 23-19) Note: If a NE is already locked by another user, it does not appears in this list. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 23-18 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
Description of the list of auditable NEs
....................................................................................................................................................................................................................................
Description of the list of auditable NEs Attributes of a auditable NE
The attributes displayed for each NE are: •
User Label.
•
Node User Label.
•
LAC State.
•
Lcation Name.
•
Type.
•
Operational State.
•
Working State.
•
Consistency State.
• •
Bridge Type.
•
Version.
•
IP Address.
•
ACCESS Module Label.
Comment.
.................................................................................................................................................................................................................................... 1350 OMS 23-19 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
Perform an audit on a NE
....................................................................................................................................................................................................................................
Perform an audit on a NE When to use
This function consists in starting the audit on the previously selected NEs. Related information
For a description about Audit, Alignment and, Reservation, refer to the topic “The AAR procedure ” (p. 23-3). For more details about audit on a NE, see: “NE Audit tool” (p. 23-6). For information about attributes compared in an Audit, see “Results of Audit” (p. 23-8). After confirmation, NE per NE, the 1350 OMS PKT uploads the NE MIB content and compares it with the 1350 OMS PKT database. In each domain, if an error occurs, the audit is stopped in this domain nevertheless the audit in the other domains goes on. If an audit is Partially done, the actions alignment and reservation are not available. Only a new audit is possible. During the same session, the user can audit again the same NE; In this case, only the latest audit result is at the user disposal. This new audit allows the user to target a new alignment (the alignment is allowed only once after an audit). The audit results are temporally stored into audit files. They are automatically deleted when the user stops the audit, alignment, reserve procedure. One file per audited NE is stored. The file contains the compared domains. When the audit is completed on all selected NEs, a message is displayed in the status bar. The main steps of the audit are listed into the 1350 OMS PKT Log file. If errors or warning occur, they are listed in this file too and in an error message window. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. The AAR procedure must be started “Start the audit, alignment, reserve procedure” (p. 23-16). Conditions
To get a positive result: • •
The NE must not be an E/FE board or a GE board. The NE LAC state must not be granted.
.................................................................................................................................................................................................................................... 1350 OMS 23-20 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
Perform an audit on a NE
....................................................................................................................................................................................................................................
• •
The NE operational state must be enable. Lock state of selected NEs must be:
– –
Unlocked. Locked (due to an audit, alignment, reserve procedure launched on the NEs by the
user himself). Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Action > Packet > Network Element > Network Element > NE for Audit. Result: The list window is shown. ...................................................................................................................................................................................................
2
Select one or more items in the list. ...................................................................................................................................................................................................
3
Select Action > Network Element > Start NE Audit. ...................................................................................................................................................................................................
4
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: When the audit is in progress on a selected NE, the NE is locked. Operations
that affect the NE are not authorized (For example: delete the NE, delete the transmission paths that has at least one NE concerned by audit, alignment session, …). When the audit is completed on all selected NEs, a message is displayed in the status bar. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 23-21 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
View the list of Audited NEs
....................................................................................................................................................................................................................................
View the list of Audited NEs When to use
After having performed an audit, this function displays the result of this audit. Related information
For a description about Audit, Alignment and, Reservation, refer to the topic “The AAR procedure ” (p. 23-3). When the AAR procedure is stopped, the information about audited NEs is lost. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. The AAR procedure must be started “Start the audit, alignment, reserve procedure” (p. 23-16). The AAR session must be open. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Audit Align Reserve. Result: The Audit Align Reserve menu is displayed. ...................................................................................................................................................................................................
2
Select Audited NEs. Result: The Audited Network Element list window is displayed.
See the following topic in this document: “Description of the list of Audited NEs” (p. 23-23) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 23-22 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
Description of the list of Audited NEs
....................................................................................................................................................................................................................................
Description of the list of Audited NEs Attributes of Audited NE
The attributes displayed for each audited network element are: •
User Label.
•
Creation Date.
•
Audit (Done, Partially Done, Not Done).
•
Alignment (Done, Partially Done, Not Done).
•
Reservation (Done, Partially Done, Not Done).
•
Forced Alignment (Done, Partially Done, Not Done).
•
Preparation (Done, Partially Done, Not Done).
.................................................................................................................................................................................................................................... 1350 OMS 23-23 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
View the results of an audit
....................................................................................................................................................................................................................................
View the results of an audit When to use
This function consists in starting the audit on the previously selected NEs. Related information
For a description about Audit, Alignment and, Reservation, refer to the topic “The AAR procedure ” (p. 23-3). For information about attributes compared in an Audit, see “Results of Audit” (p. 23-8). When the AAR procedure is stopped, the information about audit results is lost. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. The AAR procedure must be started “Start the audit, alignment, reserve procedure” (p. 23-16). The AAR session must be open. Conditions
To get a positive result: • •
The NE must not be an E/FE board or a GE board. The NE LAC state must not be granted.
•
The NE operational state must be enable.
•
Lock state of selected NEs must be:
–
Unlocked.
–
Locked (due to an audit, alignment, reserve procedure launched on the NEs by the
user himself). Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Network Elements > Network Element. Result: The list window is shown. ...................................................................................................................................................................................................
2
Select one or more items in the list.
.................................................................................................................................................................................................................................... 1350 OMS 23-24 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
View the results of an audit
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
3
Select Action > Audited NE > Display Audit File. Result: The Audit NE file is displayed.
The files are automatically deleted when the user stops the audit, alignment, reserve procedure. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 23-25 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities Audit, Alignment, Reservation, Recovery
Perform an alignment on a NE
....................................................................................................................................................................................................................................
Perform an alignment on a NE When to use
This function consists in starting the alignment on the previously audited NEs. Related information
For a description about Audit, Alignment and, Reservation, refer to the topic “The AAR procedure ” (p. 23-3). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. The AAR procedure must be started “Start the audit, alignment, reserve procedure” (p. 23-16). The AAR session must be open. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Construction > Network Elements > Audited NEs. Result: The list window is shown. ...................................................................................................................................................................................................
2
Select one or more items in the list. ...................................................................................................................................................................................................
3
Select Action > Audited NE > Align Down. ...................................................................................................................................................................................................
4
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 23-26 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities NE Alignment tool
Overview
....................................................................................................................................................................................................................................
NE Alignment tool Overview Purpose
This section provides information about the NE alignment tool. Contents Workflow to align up Ethernet Data
23-28
ISA Board Replacement Procedure
23-30
Perform a reservation on a NE
23-32
Restore procedure for ISA board
23-33
.................................................................................................................................................................................................................................... 1350 OMS 23-27 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities NE Alignment tool
Workflow to align up Ethernet Data
....................................................................................................................................................................................................................................
Workflow to align up Ethernet Data When to use
This function consists in starting the alignment on the previously audited NEs. Related information
For a description about Audit, Alignment and, Reservation, refer to the topic “The AAR procedure ” (p. 23-3). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Start the Audit, Align, Reserve session from the Construction GUI. Select Action > Packet > Audit Align Reserve > Start Procedure. ...................................................................................................................................................................................................
2
Choose the NE (or the NEs) to be Audited from the Auditable Network Element List in the Construction GUI and select Start NE Audit from the popup menu. ...................................................................................................................................................................................................
3
Read the differences displaying the Audit file content. Select Search > Packet > Audit Align Reserve > Display Audit File. Result: The audit results are shown. ...................................................................................................................................................................................................
4
If the need is to perform an Align Up operation on Ethernet objects, start the Align Up operation from the Ethernet GUI. Select Action > Packet > Audit Align Reserve > Align Up. Result: The Align Up windows are shown. ...................................................................................................................................................................................................
5
On the Align Up windows, select one or more objects that must be realigned and confirm the choice with OK button.
.................................................................................................................................................................................................................................... 1350 OMS 23-28 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities NE Alignment tool
Workflow to align up Ethernet Data
....................................................................................................................................................................................................................................
Result: At that moment the Align Up function realign the 1350 OMS PKT database to the NE image. ...................................................................................................................................................................................................
6
After having realigned all needed objects, close the Align Up Window from Ethernet GUI. ...................................................................................................................................................................................................
7
End the Audit, Alignment, Reserve session from the Construction GUI. Select Action > Packet > Audit Align Reserve > Stop Procedure. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 23-29 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities NE Alignment tool
ISA Board Replacement Procedure
....................................................................................................................................................................................................................................
ISA Board Replacement Procedure When to use
The procedure describes the main steps needed to replace an ISA board that supports customer service or traffic under the supervision of 1350 OMS EML and 1350 OMS PKT systems. Related information
For a description about Audit, Alignment and, Reservation, refer to the topic “The AAR procedure ” (p. 23-3). For more details, refer to the topic “Align Up of Ethernet Domain Data” (p. 23-15). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
The faulty ISA Board has been replaced with a new one, the MIB is void in the new Board. ...................................................................................................................................................................................................
2
ISA MIB is restored on the new Board through NE. The MIB stored at 1350 OMS EML is not fully aligned with the current status of 1350 OMS PKT DB. ...................................................................................................................................................................................................
3
1350 OMS PKT launches the Audit operation against the involved ISA. The Audit report identifies a set of mismatches. ...................................................................................................................................................................................................
4
Per each D- difference detected in the Audit report the user can: 1. Reserve the resource in the 1350 OMS PKT DB, acknowledging the NE configuration is OK. 2. Remove the resource from NE MIB through NE, acknowledging the NE configuration is not OK.
.................................................................................................................................................................................................................................... 1350 OMS 23-30 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities NE Alignment tool
ISA Board Replacement Procedure
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
5
Per each D difference detected in the Audit report the user can: 1. Perform 1350 OMS PKT operations to realign 1350 OMS PKT to NE, acknowledging the NE configuration is OK. 2. Perform 1350 OMS EML operations to realign NE to 1350 OMS PKT, acknowledging the NE configuration is not OK. ...................................................................................................................................................................................................
6
Per all D+ difference detected in the Audit report the user can: 1. Align Down the 1350 OMS PKT configurations to the NE, acknowledging the 1350 OMS PKT configuration is OK. 2. Remove the resources from 1350 OMS PKT DB (through GUI or DB access), acknowledging the 1350 OMS PKT configuration is not OK. ...................................................................................................................................................................................................
7
Perform a final audit for a further alignment check. If any difference (D+ or D-) is found again, repeat the steps from Step 4 to Step 6 until a full alignment is obtained. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 23-31 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities NE Alignment tool
Perform a reservation on a NE
....................................................................................................................................................................................................................................
Perform a reservation on a NE When to use
This function consists in starting the reservation on the previously selected NEs. Related information
For a description about Audit, Alignment and, Reservation, refer to the topic “The AAR procedure ” (p. 23-3). For more details about the reservation, refer to chapter “Reservation tool” (p. 23-13). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. The AAR procedure must be started “Start the audit, alignment, reserve procedure” (p. 23-16). The AAR session must be open. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Construction > Network Elements > Audited Network Elements. Result: The list window is shown. ...................................................................................................................................................................................................
2
Select one or more items in the list. ...................................................................................................................................................................................................
3
Select Action > Audit NE > NE Resource Reservation. ...................................................................................................................................................................................................
4
Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). Result: The Resources are reserved. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 23-32 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities NE Alignment tool
Restore procedure for ISA board
....................................................................................................................................................................................................................................
Restore procedure for ISA board Overview
The procedure describes the main steps to Restore the MIB for an ISA board that supports customer services or traffic. The board is supposed to be under the supervision of 1350 OMS EML and 1350 OMS PKT systems. The MIB is supposed to be saved in 1350 OMS EML repository. All the actions described in the previous “ISA Board Replacement Procedure” (p. 23-30) are still applicable, except the point Step 1 associated to the physical replacement of the ISA Board.
.................................................................................................................................................................................................................................... 1350 OMS 23-33 8DG42227DAAA 9.6 Issue 3 December 2012
Network Utilities
Restore procedure for ISA board
....................................................................................................................................................................................................................................
.................................................................................................................................................................................................................................... 1350 OMS 23-34 8DG42227DAAA 9.6 Issue 3 December 2012
24
24 Operation, Administration, and Maintenance (OAM) Management
Overview Purpose
This chapter describes how to manage Ethernet Operations, Administration, and Maintenance (OAM). Contents Ethernet OAM
24-3
OAM main functions
24-3
Create OAM Domain
24-7
List OAM Domains
24-8
Description of the list of OAM MD
24-9
OAM Domain Properties
24-10
Details of OAM MD
24-11
Modify OAM Domain
24-12
Configure OAM Domain
24-13
Deimplement OAM Domain
24-14
Inventory of OAM items from MD
24-15
Inventory of OAM monitored objects from MD
24-16
Maintenance Association (MA)
24-17
Maintenance Associations
24-17
List Maintenance Association (MA)
24-18
Description of the list of OAM MA
24-19
Properties of Maintenance Association (MA)
24-20
Details of the OAM MA
24-21
Modify Maintenance Association (MA)
24-22
Configure Maintenance Association (MA)
24-23
Enable/Disable Continuity Check (CC)
24-24
................................................................................................................................................................................................................................... 1350 OMS 24-1 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Management
Overview
....................................................................................................................................................................................................................................
Deimplement OAM MA
24-25
Inventory of OAM items from MA
24-26
Inventory of OAM monitored objects from MA
24-27
Maintenance Activation Maintenance Activation on EVC Loopback Loopback activation Linktrace Linktrace activation Delay measurement and Loss measurement
24-28 24-28 24-29 24-29 24-31 24-31 24-33
Packet Delay measurement
24-34
Packet Loss measurement
24-35
Configure Maintenance End Points
24-36
List the OAM ETH DM Tool
24-38
List the OAM ETH SLM Tool
24-40
Create ETH DM Tool
24-42
Create ETH SLM Tool
24-44
Activate/Deactivate OAM ETH DM Tool
24-46
Activate/Deactivate OAM ETH SLM Tool
24-47
Inventory from OAM ETH DM Tool
24-48
Inventory from OAM ETH SLM Tool
24-49
Configure OAM ETH DM Tool
24-50
Configure OAM ETH SLM Tool
24-52
.................................................................................................................................................................................................................................... 1350 OMS 24-2 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) OAM main functions Management Ethernet OAM ....................................................................................................................................................................................................................................
Ethernet OAM OAM main functions OAM Introduction
The ETH OAM allows the user to manage: • • • •
Maintenance Domains: Creation/modification/deletion. Maintenance Associations: Modification Creation/deletion are done automatically when ETH OAM is enabled on EVC, links, ports. Loopback. Linktrace.
•
List/inventories of related objects.
OAM Continuity Check
The Ethernet OAM Continuity Check (OAM CC) allows determining the reachability between groups of associated Ethernet Resources. The Ethernet OAM CC is a tool for pro-active maintenance; in fact as soon as the OAM CC tool is set up over Ethernet resources, such Ethernet Resources start exchanging autonomously OAM Continuity Check Messages (OAM CC PDU) and specific Alarms are sent by NEs whenever the reach ability between that Ethernet Resources is interrupted. Ethernet OAM Continuity Check is the base for other OAM activities: • •
Link Trace Management Loop Back Management
•
Ethernet MEF Performance management (Jitter and Delay evaluation).
The Set up of Ethernet OAM Continuity Check tool can be done on top of the following Technologies: • • •
Provider Bridge Domains ETS domain for EPTL services. T-MPLS Domains.
•
a combination of the above (E2E)
OAM Continuity Check terminology
The Ethernet OAM CC is realized according to ITU Y.1731 and IEEE 802.1ag Standards.
.................................................................................................................................................................................................................................... 1350 OMS 24-3 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) OAM main functions Management Ethernet OAM ....................................................................................................................................................................................................................................
The terminologies adopted by the two Standards are slightly different, and the following table reports a comparison between the two. Table 24-1
Terminology Mapping
ITU Y.1731 Terminology
IEEE 802.1ag Terminology
MD
Maintenance Domain
MD
Maintenance Domain
MEG
Maintenance Entity Group
MA
Maintenance Association
MEG Level
Maintenance Entity Group Level
MA Level
Maintenance Association Level
MEP
MEG End Point
MEP
MA End Point
OAM Continuity Check model
Ethernet OAM CC objects: •
“Maintenance Domain (MD)” (p. 24-4).
•
“Maintenance Association (MA) or Maintenance Entity Group (MEG)” (p. 24-5).
•
“Maintenance Edge Point (MEP)” (p. 24-5).
•
“Intermediate Maintenance Entity Point (MIP)” (p. 24-6).
Maintenance Domain (MD)
MD is the Network or a Network Portion where Fault on Connectivity is managed. .................................................................................................................................................................................................................................... 1350 OMS 24-4 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) OAM main functions Management Ethernet OAM ....................................................................................................................................................................................................................................
MD can be mapped as STP domain, or ETS domain (PortToPort and EPTL), or T-MPLS domain. For a given Domain it is possible to display all MDs existing in that domain. From a given MD it is possible to retrieve all the contained MA (Connectivity) and related configured MEPs (Connectivity extremities). Maintenance Association (MA) or Maintenance Entity Group (MEG)
MA realizes the association between Maintenance Entities (Maintenance Points) and Maintenance Domain. MA determines also the relationship existing among Maintenance Points The life cycle of MA (Creation/Deletion) is always linked to corresponding Connectivity object (EVC, Transport Link or Edge Port). MA Parameters are visible always contextually to the corresponding Connectivity object. MA Modification/Configuration is always possible from the corresponding Connectivity object. MA is defined by the following main attributes: •
MA name: made by a Format and a Name.
•
Monitored object. Monitored object can be one of the following: – (only for Virtual Bridge, Provider Bridge and ETS) VLAN: it can be the CVLAN in case of Virtual Bridge or the SVLAN in case of Provider Bridge
• • • •
– (only for T-MPLS) Pseudo-Wire or VSI MHF policy: which automatic policy is defined inside the MA for MIP Creation (default=inherited from MD) CCM Interval: delay between sending of CC PDU MEP List Table : list of Maintenance Points making part to the association and their Activation status Row Status: Activation status for the MA entry
Maintenance Edge Point (MEP)
MEP is a Maintenance Point located at the Edge of the Monitored Network. MEP can initiate and terminate OAMPDU frames. OAM activities can be started from MEP MEPs are explicitly created on Operator DemandEach MEP is always linked with PORT or, depending on involved technology, VLANID, PWID. The life cycle of MEP (Creation/Deletion) is always linked to corresponding Connectivity object extremity (or to the Connectivity object itself in the special case of the Edge Port). MEP Parameters are visible always contextually to corresponding Connectivity object extremity. .................................................................................................................................................................................................................................... 1350 OMS 24-5 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) OAM main functions Management Ethernet OAM ....................................................................................................................................................................................................................................
MEP Modification/Configuration is always possible from corresponding Connectivity object extremity. Each MEP is defined by the following main attributes: • • •
Identifier: unique in the MA, in the range 1-8191. Interface Reference: Port identifier (the MAC address of the Port is inherited). Direction : (UP, Down).
• • •
Priority: priority (0-7) to be used in CCM PDU messages. Enable/Disable Flag : aimed to dynamically start/stop OAM CC. Row Status: Activation status for the MEP entry.
•
Other attributes not connected to CC management are not included here and always set to their default value.
Intermediate Maintenance Entity Point (MIP)
MIP is an Intermediate Maintenance Entity Point. MIP can only react to OAMPDU frames (answering and/or forwarding). OAM activities cannot be started from MIP. Each MIP has a Direction concept (UP, Down). MIPs are automatically created depending on criteria defined on MD/MA objects. Monitored Objects
Objects monitored in a Maintenance Domain: • • • •
Ethernet Domain NE E2E EVC EVC
• • • •
EVC termination Transport Link Transport Link Termination Edge Port
.................................................................................................................................................................................................................................... 1350 OMS 24-6 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Create OAM Domain Management Ethernet OAM ....................................................................................................................................................................................................................................
Create OAM Domain When to use
The scope of this procedure is to define an OAM Domain. Related Information
For more information, refer to: “OAM main functions” (p. 24-3) Maintenance domain can be defined by user: • •
To define a domain different from the default one used by all Maintenance associations related to EVCs, links, ports To define maintenance levels different from the one assigned by default (0 on links and edge ports, 2 on EVC)
Maintenance domains provisioning state follows the evolutions of related MAs: •
implemented in the NEs as soon as the first monitored object requires it.
•
Deimplemented when no more monitored object requires it.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the main menu bar select Actions > Packet > OAM CC> Create OAM MD. Result: The creation window is displayed. ...................................................................................................................................................................................................
2
Define the following attributes: •
Name.(User Label of Maintenance Domain, free text).
• •
Level. (8 OAM Levels are standardized). MHF policy.(MIP Half-function creation policy: None: no MIP is created; Explicit: MIPs are created where a lower-level MEP exists; default: MIPs are created on all
intermediate points). Click OK button to confirm the operation. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-7 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) List OAM Domains Management Ethernet OAM ....................................................................................................................................................................................................................................
List OAM Domains When to use
The scope of this procedure is to list all the Maintenance Domains. Related Information
For more information, refer to: “OAM main functions” (p. 24-3) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the main menu bar select Search > Packet > OAM CC> OAM MDs. Result: The list window is displayed.
See the following topic in this document: “Description of the list of OAM MD” (p. 24-9) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-8 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Description of the list of OAM MD Management Ethernet OAM ....................................................................................................................................................................................................................................
Description of the list of OAM MD Attributes of an OAM MD
The attributes displayed for each MD are: •
Name.(User Label of Maintenance Domain, free text).
•
Format
• •
Level. (8 OAM Levels are standardized).
•
MHF policy.(MIP Half-function creation policy: None: no MIP is created; Explicit: MIPs are created where a lower-level MEP exists; default: MIPs are created on all
intermediate points). Provisioning State (Defined, Implemented)
.................................................................................................................................................................................................................................... 1350 OMS 24-9 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) OAM Domain Properties Management Ethernet OAM ....................................................................................................................................................................................................................................
OAM Domain Properties When to use
The scope of this procedure is to list all the Maintenance Domains. Related Information
For more information, refer to: “OAM main functions” (p. 24-3) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the main menu bar select Search > Packet > OAM CC> OAM MDs. Result: The list window is displayed. ...................................................................................................................................................................................................
2
Select one item in the list and select Actions > Properties. Result: The Property window is displayed.
See the following topic in this document: “Details of OAM MD” (p. 24-11) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-10 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Details of OAM MD Management Ethernet OAM ....................................................................................................................................................................................................................................
Details of OAM MD Attributes of an OAM MD
The attributes displayed for each MD are: •
Name.(User Label of Maintenance Domain, free text).
•
Format
• •
Level. (8 OAM Levels are standardized).
• •
MHF policy.(MIP Half-function creation policy: None: no MIP is created; Explicit: MIPs are created where a lower-level MEP exists; default: MIPs are created on all
intermediate points). Provisioning State (Defined, Implemented) Id
.................................................................................................................................................................................................................................... 1350 OMS 24-11 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Modify OAM Domain Management Ethernet OAM ....................................................................................................................................................................................................................................
Modify OAM Domain When to use
The scope of this procedure is to change attributes when MD is not implemented. Related Information
The user can change attributes when MD is not implemented. For more information, refer to: “OAM main functions” (p. 24-3) See also: “Configure OAM Domain” (p. 24-13) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the main menu bar select Search > Packet > OAM CC> OAM MDs. Result: The list window is displayed. ...................................................................................................................................................................................................
2
Select one item in the list and select Actions > Modify. Result: The modify window is displayed. ...................................................................................................................................................................................................
3
Modify one or more of the following attributes: •
Name.(User Label of Maintenance Domain, free text).
•
Level. (8 OAM Levels are standardized).
•
MHF policy.(MIP Half-function creation policy: None: no MIP is created; Explicit: MIPs are created where a lower-level MEP exists; default: MIPs are created on all
intermediate points). Click OK button to confirm the operation. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-12 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Configure OAM Domain Management Ethernet OAM ....................................................................................................................................................................................................................................
Configure OAM Domain When to use
The scope of this procedure is to change attributes when MD is implemented. Related Information
The user can change attributes when MD is implemented. For more information, refer to: “OAM main functions” (p. 24-3) See also: “Modify OAM Domain” (p. 24-12) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the main menu bar select Search > Packet > OAM CC> OAM MDs. Result: The list window is displayed. ...................................................................................................................................................................................................
2
Select one item in the list and select Actions > OAM MD > Configure. Result: The configure window is displayed. ...................................................................................................................................................................................................
3
Modify one or more of the following attributes: •
Maintenance Domain .
•
Level. (8 OAM Levels are standardized).
•
MHF policy.(MIP Half-function creation policy: None: no MIP is created; Explicit: MIPs are created where a lower-level MEP exists; default: MIPs are created on all
intermediate points). Click OK button to confirm the operation. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-13 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Deimplement OAM Domain Management Ethernet OAM ....................................................................................................................................................................................................................................
Deimplement OAM Domain When to use
The scope of this procedure is to deimplement MD. Related Information
The user can change attributes when MD is implemented. For more information, refer to: “OAM main functions” (p. 24-3) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the main menu bar select Search > Packet > OAM CC> OAM MDs. Result: The list window is displayed. ...................................................................................................................................................................................................
2
Select one item in the list and select Actions > OAM MD > Deimplement. Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-14 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Inventory of OAM items from MD Management Ethernet OAM ....................................................................................................................................................................................................................................
Inventory of OAM items from MD When to use
The scope of this procedure is to list OAM items related to a Maintenance Domain. Related Information
For more information, refer to: “OAM main functions” (p. 24-3) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the main menu bar select Search > Packet > OAM CC> OAM MDs. Result: The list window is displayed. ...................................................................................................................................................................................................
2
Select one item in the list and select Search > OAM MD. Result: The search menu is displayed. ...................................................................................................................................................................................................
3
Select one of OAM items related to a Maintenance Domain: • • •
MA MEP MIP Result: The list of the contained objects is displayed.
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-15 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Inventory of OAM monitored objects from MD Management Ethernet OAM ....................................................................................................................................................................................................................................
Inventory of OAM monitored objects from MD When to use
The scope of this procedure is to list objects monitored in a Maintenance Domain. Related Information
For more information, refer to: “OAM main functions” (p. 24-3) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the main menu bar select Search > Packet > OAM CC> OAM MDs. Result: The list window is displayed. ...................................................................................................................................................................................................
2
Select one item in the list and select Search > OAM MD. Result: The search menu is displayed. ...................................................................................................................................................................................................
3
Select the list of the objects monitored in the Maintenance Domain: •
List Bridge EVCs
•
List ETS EVCs
•
List E2E EVCs
•
List T-MPLS EVCs
•
List Bridge NEs Result: The list of the contained objects is displayed.
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-16 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Maintenance Associations Management Maintenance Association (MA) ....................................................................................................................................................................................................................................
Maintenance Association (MA) Maintenance Associations When to use
Maintenance associations are created/deleted following the enabling/disabling of ETH OAM on monitored resources Related Information
For more information, refer to: “OAM main functions” (p. 24-3) Monitored Association (MA) instances: • •
There is one MA instance for each monitored object. The provisioning state of the MA instance follows the evolutions of related monitored object: – Created/implemented in the NEs as soon as the monitoring is enabled and object is implemented. –
Deimplemented/deleted when monitoring is disabled or object is deimplemented/deleted.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the main menu bar, list the object to monitor: • •
EVC Link
•
Edge Port
...................................................................................................................................................................................................
2
Select the object and enable/disable OAM. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-17 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) List Maintenance Association (MA) Management Maintenance Association (MA) ....................................................................................................................................................................................................................................
List Maintenance Association (MA) When to use
The scope of this procedure is to list all the Maintenance Associations. Related Information
For more information, refer to: “OAM main functions” (p. 24-3) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the main menu bar select Search > Packet > OAM CC> OAM MDs. Result: The list window is displayed. ...................................................................................................................................................................................................
2
Select one item then select Search > Packet > OAM MA Result: The OAM MA list is displayed.
See the following topic in this document: “Description of the list of OAM MA” (p. 24-19) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-18 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Description of the list of OAM MA Management Maintenance Association (MA) ....................................................................................................................................................................................................................................
Description of the list of OAM MA Attributes of an OAM MA
The attributes displayed for each MD are: •
Name.(User Label of Maintenance Domain, free text).
•
OAM MD
•
Format
•
MHF policy.(MIP Half-function creation policy: None: no MIP is created; Explicit: MIPs are created where a lower-level MEP exists; default: MIPs are created on all
• •
intermediate points). CCM Interval. Priority.
•
Provisioning State (Defined, Implemented).
•
OAM Enabled.
.................................................................................................................................................................................................................................... 1350 OMS 24-19 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Properties of Maintenance Association (MA) Management Maintenance Association (MA) ....................................................................................................................................................................................................................................
Properties of Maintenance Association (MA) When to use
The scope of this procedure is to list all the Maintenance Associations properties. Related Information
For more information, refer to: “OAM main functions” (p. 24-3) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the main menu bar select Search > Packet > OAM CC> OAM MDs. Result: The list window is displayed. ...................................................................................................................................................................................................
2
Select one item then select Search > Packet > OAM CC> OAM MAs. Result: The list window is displayed. ...................................................................................................................................................................................................
3
Select one item then select Action > Properties Result: The OAM MA property window is displayed.
See the following topic in this document: “Details of the OAM MA” (p. 24-21) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-20 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Details of the OAM MA Management Maintenance Association (MA) ....................................................................................................................................................................................................................................
Details of the OAM MA Attributes of an OAM MA
The attributes displayed for each MD are: •
Name.(User Label of Maintenance Domain, free text).
•
OAM MD
•
Format
•
MHF policy.(MIP Half-function creation policy: None: no MIP is created; Explicit: MIPs are created where a lower-level MEP exists; default: MIPs are created on all
• •
intermediate points). CCM Interval. Priority.
•
Provisioning State (Defined, Implemented).
•
OAM Enabled.
•
Id.
.................................................................................................................................................................................................................................... 1350 OMS 24-21 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Modify Maintenance Association (MA) Management Maintenance Association (MA) ....................................................................................................................................................................................................................................
Modify Maintenance Association (MA) When to use
The scope of this procedure is to change MA attributes. Related Information
For more information, refer to: “OAM main functions” (p. 24-3) See also: “Configure Maintenance Association (MA) ” (p. 24-23) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the main menu bar select Search > Packet > OAM CC> OAM MDs. Result: The list window is displayed. ...................................................................................................................................................................................................
2
Select one item then select Search > Packet > OAM CC> OAM MAs. Result: The list window is displayed. ...................................................................................................................................................................................................
3
Select one item then select Action > Modify Result: The modification window is displayed. ...................................................................................................................................................................................................
4
Modify one or more attributes: •
Name.(User Label of Maintenance Domain, free text).
•
MHF policy.(MIP Half-function creation policy: None: no MIP is created; Explicit: MIPs are created where a lower-level MEP exists; default: MIPs are created on all
• •
intermediate points). CCM Interval. Priority.
Click OK to confirm the operation. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-22 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Configure Maintenance Association (MA) Management Maintenance Association (MA) ....................................................................................................................................................................................................................................
Configure Maintenance Association (MA) When to use
The scope of this procedure is to change MA configuration. Related Information
For more information, refer to: “OAM main functions” (p. 24-3) See also: “Modify OAM Domain” (p. 24-12) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the main menu bar select Search > Packet > OAM CC> OAM MDs. Result: The list window is displayed. ...................................................................................................................................................................................................
2
Select one item then select Search > Packet > OAM CC> OAM MAs. Result: The list window is displayed. ...................................................................................................................................................................................................
3
Select one item then select Action > Configure Result: The Configure OAM MA window is displayed. ...................................................................................................................................................................................................
4
Modify one or more attributes: •
Maintenance Association.
•
VLAN Id (0-4095).
•
MHF policy.(MIP Half-function creation policy: None: no MIP is created; Explicit: MIPs are created where a lower-level MEP exists; default: MIPs are created on all
•
intermediate points). CCM Interval.
Click OK or Apply to confirm the operation. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-23 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Enable/Disable Continuity Check (CC) Management Maintenance Association (MA) ....................................................................................................................................................................................................................................
Enable/Disable Continuity Check (CC) When to use
The scope of this procedure is to Enable or Disable CC. Related Information
The user can change attributes when MA is implemented. For more information, refer to: “OAM main functions” (p. 24-3) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the main menu bar select Search > Packet > OAM CC> OAM MDs. Result: The list window is displayed. ...................................................................................................................................................................................................
2
Select one item then select Search > Packet > OAM CC> OAM MAs. Result: The list window is displayed. ...................................................................................................................................................................................................
3
Select one item then select Action > Enable or Action > Disable. Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-24 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Deimplement OAM MA Management Maintenance Association (MA) ....................................................................................................................................................................................................................................
Deimplement OAM MA When to use
The scope of this procedure is to deimplement MA. Related Information
The user can change attributes when MD is implemented. For more information, refer to: “OAM main functions” (p. 24-3) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the main menu bar select Search > Packet > OAM CC> OAM MDs. Result: The list window is displayed. ...................................................................................................................................................................................................
2
Select one item then select Search > Packet > OAM CC> OAM MAs. Result: The list window is displayed. ...................................................................................................................................................................................................
3
Select one item in the list and select Actions > OAM MA > Deimplement. Select one of the options in the confirmation box. Refer to the procedure “Confirm the action” (p. 11-40). E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-25 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Inventory of OAM items from MA Management Maintenance Association (MA) ....................................................................................................................................................................................................................................
Inventory of OAM items from MA When to use
The scope of this procedure is to list OAM items related to a MA. Related Information
For more information, refer to: “OAM main functions” (p. 24-3) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the main menu bar select Search > Packet > OAM CC> OAM MDs. Result: The list window is displayed. ...................................................................................................................................................................................................
2
Select one item then select Search > Packet > OAM CC> OAM MAs. Result: The list window is displayed. ...................................................................................................................................................................................................
3
Select one item in the list and select Search > OAM MA. Result: The search menu is displayed. ...................................................................................................................................................................................................
4
Select one of OAM items related to a MA: •
MD
• •
MEP MIP Result: The list of the contained objects is displayed.
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-26 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Inventory of OAM monitored objects from MA Management Maintenance Association (MA) ....................................................................................................................................................................................................................................
Inventory of OAM monitored objects from MA When to use
The scope of this procedure is to list objects monitored in a MA. Related Information
For more information, refer to: “OAM main functions” (p. 24-3) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the main menu bar select Search > Packet > OAM CC> OAM MDs. Result: The list window is displayed. ...................................................................................................................................................................................................
2
Select one item then select Search > Packet > OAM CC> OAM MAs. Result: The list window is displayed. ...................................................................................................................................................................................................
3
Select one item in the list and select Search > OAM MA. Result: The search menu is displayed. ...................................................................................................................................................................................................
4
Select one of the objects monitored in the MA: •
NEs
• •
EVC
•
Edge Port
Link Result: The list of the contained objects is displayed.
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-27 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Management
Maintenance Activation on EVC
....................................................................................................................................................................................................................................
Maintenance Activation Maintenance Activation on EVC When to use
This function activates Ethernet OAM on the EVC. Related Information
Ethernet OAM can be activated: •
at EVC creation time
•
on an implemented EVC
Ethernet OAM can be activated on the following objects: •
EVC
• •
Link Edge Port
For more information, refer to: “OAM main functions” (p. 24-3) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the main menu select Search > Packet > Services > Connection Less EVC (Bridge) > Bridge EVCs. ...................................................................................................................................................................................................
2
Select the object and select Action > Start CC. ...................................................................................................................................................................................................
3
Insert the following parameters: •
Priority. (from 0 to 7
•
Select Maintenance Domain
Click OK to confirm the action. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-28 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Management
Loopback activation
....................................................................................................................................................................................................................................
Loopback Loopback activation When to use
The scope of this procedure is to activate loopback. Related Information
For more information, refer to: “OAM main functions” (p. 24-3) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the main menu bar select Actions > Packet > List one of the objects • •
EVC termination Transport Link Termination
•
Edge Port
...................................................................................................................................................................................................
2
Select one item then select Actions > Activate Loopback. Result: The Activate Loopback window is displayed. ...................................................................................................................................................................................................
3
Select the attributes: •
Source EVC Termination.
•
Destination EVC Termination.
•
Use a Transport Link Termination.
•
Transport Link.
•
Transport Link Termination.
•
Priority.
•
Time out.
Click OK or Apply to confirm the operation. .................................................................................................................................................................................................................................... 1350 OMS 24-29 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Loopback activation Management Loopback ....................................................................................................................................................................................................................................
Result: Loopback report is shown. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-30 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Linktrace activation Management Linktrace ....................................................................................................................................................................................................................................
Linktrace Linktrace activation When to use
The scope of this procedure is to activate Linktrace. Related Information
For more information, refer to: “OAM main functions” (p. 24-3) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task ...................................................................................................................................................................................................
1
From the main menu bar select Actions > Packet > List one of the objects: •
EVC termination
...................................................................................................................................................................................................
2
Select one item then select Actions > Activate Linktrace. Result: The Activate Linktrace window is displayed. ...................................................................................................................................................................................................
3
Select the attributes: •
Source EVC Termination.
•
Destination EVC Termination.
•
Use a Transport Link Termination.
•
Time to Live.
Click OK or Apply to confirm the operation. Result: Linktrace report is shown. Link Trace Report attributes:
• •
Date
•
LtmSent
Priority
.................................................................................................................................................................................................................................... 1350 OMS 24-31 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Linktrace activation Management Linktrace ....................................................................................................................................................................................................................................
•
NE UL
• •
Port UL
•
MAC Address
•
Ltm Behaviour
Transport Link UL
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-32 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Overview Management Delay measurement and Loss measurement ....................................................................................................................................................................................................................................
Delay measurement and Loss measurement Overview Purpose
The tool measures the delay time and the packet loss on Ethernet and T-MPLS services. Contents Packet Delay measurement
24-34
Packet Loss measurement
24-35
Configure Maintenance End Points
24-36
List the OAM ETH DM Tool
24-38
List the OAM ETH SLM Tool
24-40
Create ETH DM Tool
24-42
Create ETH SLM Tool
24-44
Activate/Deactivate OAM ETH DM Tool
24-46
Activate/Deactivate OAM ETH SLM Tool
24-47
Inventory from OAM ETH DM Tool
24-48
Inventory from OAM ETH SLM Tool
24-49
Configure OAM ETH DM Tool
24-50
Configure OAM ETH SLM Tool
24-52
.................................................................................................................................................................................................................................... 1350 OMS 24-33 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Packet Delay measurement Management Delay measurement and Loss measurement ....................................................................................................................................................................................................................................
Packet Delay measurement Description
The tool counts the delivery time of packets. For the measurement, the tool uses a specific packet. Since delay depends on packet length, the user can set a packet length value or choose a randomly generated value. For measure accuracy, the Continuity Check (CC) periods must be less than 1 ms before starting the Packet Delay tool. The Packet Delay measurement applies on: • •
EVC T-MPLS Tunnel
The Packet Delay measurement collect data on: •
Forward, Backward, Round-trip time
•
Absolute and delay variation time
The tool uses Performance Monitoring counters. The tool results are reported by CPM. To use DM tool, execute the following main steps: • • • •
Activate the tool Configure the board Start PM on dedicated counters Retrieve results by CPM
.................................................................................................................................................................................................................................... 1350 OMS 24-34 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Packet Loss measurement Management Delay measurement and Loss measurement ....................................................................................................................................................................................................................................
Packet Loss measurement Description
The Packet Loss tool counts lost packets. For the measurement, the tool counts CC packets. Traffic loss is estimated from CC packet loss. For measure accuracy, the Continuity Check (CC) periods must be less than 1 ms before starting the Packet Loss tool. The Packet Loss measurement applies on: • •
Ethernet Services Tunnel T-MPLS
The Packet Loss tool uses Performance Monitoring counters. The Packet Loss tool results are reported by CPM. To use SLM tool, execute the following main steps: • • •
Activate the tool Configure the board Start PM on dedicated counters
•
Retrieve results by CPM
.................................................................................................................................................................................................................................... 1350 OMS 24-35 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Configure Maintenance End Points Management Delay measurement and Loss measurement ....................................................................................................................................................................................................................................
Configure Maintenance End Points When to use
This function Configure Maintenance End Points of T-MPLS Tunnels. Related Information
For more information, refer to “Packet Delay measurement” (p. 24-34). For more information, refer to “Packet Loss measurement” (p. 24-35). For general information about DM/SLM Tool, refer to “Delay measurement and Loss measurement” (p. 24-33). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > MPLS and T-MPLS > T-MPLS Tunnels. Result: The tunnel list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Select Action > Configure Maintenance End Points. Result: The Configure Maintenance End Points window is shown. ...................................................................................................................................................................................................
3
To Configure Tunnel for Connectivity Verification, Packet Loss measurement, set the following attributes: •
Click the box Enable MEPs
•
Select Enable CV/SLM; (none, CV, SLM)
•
Select CV/SLM Direction
•
Select CV/SLM Period
•
Select CV/SLM PHB
•
Select Packet Loss Probability
•
Select SLM PM Granularity
•
Select SLM PM Policy
•
Click the box OAM Signal Degraded
.................................................................................................................................................................................................................................... 1350 OMS 24-36 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Configure Maintenance End Points Management Delay measurement and Loss measurement .................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
To Configure Tunnel for Delay measurement, set the following attributes: •
Click the box Enable DM
•
Select DM Period
•
Select DM PHB
•
Packet Length: Select one of the following options: – Click the box Random Packet Length
•
– Select Packet Length value Select DM Granularity
•
Select DM Policy
...................................................................................................................................................................................................
5
Click Ok button. Result: Tunnel OAM parameters are configured. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-37 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) List the OAM ETH DM Tool Management Delay measurement and Loss measurement ....................................................................................................................................................................................................................................
List the OAM ETH DM Tool When to use
The List window shows all the ETH DM Tools and their attributes. Related Information
For more information, refer to “Packet Loss measurement” (p. 24-35). For general information about DM/SLM Tool, refer to “Delay measurement and Loss measurement” (p. 24-33). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > OAM CC> OAM MDs. Result: The list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Select Search > ETH DM Tools. Result: The list window is displayed.
The attributes displayed for each DM Tool are: • User Label. • EVC. • MD Name •
MA Name
•
CCM Priority
•
CCM Interval
•
Frame Size
•
PM 15M
•
PM 24H
•
PM Policy
.................................................................................................................................................................................................................................... 1350 OMS 24-38 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) List the OAM ETH DM Tool Management Delay measurement and Loss measurement ....................................................................................................................................................................................................................................
•
Provisioning State
•
Availability State
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-39 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) List the OAM ETH SLM Tool Management Delay measurement and Loss measurement ....................................................................................................................................................................................................................................
List the OAM ETH SLM Tool When to use
The List window shows all the ETH SLM Tools and their attributes. Related Information
For more information, refer to “Packet Loss measurement” (p. 24-35). For general information about DM/SLM Tool, refer to “Delay measurement and Loss measurement” (p. 24-33). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > OAM CC> OAM MDs. Result: The list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Select Search > ETH SLM Tools. Result: The list window is displayed.
The attributes displayed for each SLM Tool are: • Session Identifier. • EVC. • MD Name •
MA Name
•
CCM Priority
•
CCM Interval
•
PM Unidir 15M
•
PM Unidir 24H
•
PM Bidir 15M
•
PM Bidir 24H
•
PM Frame Loss 15M
•
PM Frame Loss 24H
.................................................................................................................................................................................................................................... 1350 OMS 24-40 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) List the OAM ETH SLM Tool Management Delay measurement and Loss measurement ....................................................................................................................................................................................................................................
•
PM Policy
• •
Provisioning State Availability State
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-41 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Create ETH DM Tool Management Delay measurement and Loss measurement ....................................................................................................................................................................................................................................
Create ETH DM Tool When to use
This function creates ETH DM Tool for ETH over T-MPLS EVC. Related Information
For more information, refer to “Packet Delay measurement” (p. 24-34). For general information about DM/SLM Tool, refer to “Delay measurement and Loss measurement” (p. 24-33). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Ethernet over T-MPLS > T-MPLS EVCs. Result: The EVC list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Select Action > Create ETH DM Tool. Result: The Create ETH DM Tool window is shown. ...................................................................................................................................................................................................
3
To configure the tool creation, set the following attributes: •
Select Source MEP from list
•
Select Destination MEP from list
•
Select Priority (Value: 0-7)
•
Select Interval (100 ms, 1 s, 10 s, 1 min, 10 min)
•
Frame Length: Select one of the following options: –
Click the box Random Frame Size
•
– Select Frame Size value Select PM 15Min
•
Select PM 24H
•
Select PM Policy (Keep, Purge on Stop, Purge on delete)
.................................................................................................................................................................................................................................... 1350 OMS 24-42 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Create ETH DM Tool Management Delay measurement and Loss measurement .................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
Click Ok button. Result: DM Tool is created. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-43 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Create ETH SLM Tool Management Delay measurement and Loss measurement ....................................................................................................................................................................................................................................
Create ETH SLM Tool When to use
This function creates ETH SLM Tool for ETH over T-MPLS EVC. Related Information
For more information, refer to “Packet Loss measurement” (p. 24-35). For general information about DM/SLM Tool, refer to “Delay measurement and Loss measurement” (p. 24-33). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Ethernet over T-MPLS > T-MPLS EVCs. Result: The EVC list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Select Action > Create ETH SLM Tool. Result: The Create ETH DM Tool window is shown. ...................................................................................................................................................................................................
3
To Configure Tunnel for Connectivity Verification, Packet Loss measurement, set the following attributes: •
Select First MEP from list
•
Select Second MEP from list
•
Select Priority (Value: 0-7)
•
Insert Session Identifier
• •
Select Interval (100 microsec, 500 microsec, 1 ms, 3.33 ms, 10 ms, 100 ms) Click PM Unidir 15Min
•
Click PM Unidir 24H
•
Click PM Bidir 24H
•
Click PM Frame Loss 15Min
.................................................................................................................................................................................................................................... 1350 OMS 24-44 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Create ETH SLM Tool Management Delay measurement and Loss measurement ....................................................................................................................................................................................................................................
•
Click PM Frame Loss 24H
•
Select PM Policy (Keep, Purge on Stop, Purge on delete)
...................................................................................................................................................................................................
4
Click Ok button. Result: SLM Tool is created. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-45 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Activate/Deactivate OAM ETH DM Tool Management Delay measurement and Loss measurement ....................................................................................................................................................................................................................................
Activate/Deactivate OAM ETH DM Tool When to use
This function activates or deactivates ETH DM Tool. Related Information
For more information, refer to “Packet Delay measurement” (p. 24-34). For general information about DM/SLM Tool, refer to “Delay measurement and Loss measurement” (p. 24-33). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > OAM CC> ETH DM Tool. Result: The list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Select Action > Activate. or: Select Action > Deactivate. Result: The DM Tool is activated/Deactivated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-46 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Activate/Deactivate OAM ETH SLM Tool Management Delay measurement and Loss measurement ....................................................................................................................................................................................................................................
Activate/Deactivate OAM ETH SLM Tool When to use
This function activates or deactivates ETH SLM Tool. Related Information
For more information, refer to “Packet Loss measurement” (p. 24-35). For general information about DM/SLM Tool, refer to “Delay measurement and Loss measurement” (p. 24-33). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > OAM CC> ETH SLM Tool. Result: The list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Select Action > Activate. or: Select Action > Deactivate. Result: The SLM Tool is activated/Deactivated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-47 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Inventory from OAM ETH DM Tool Management Delay measurement and Loss measurement ....................................................................................................................................................................................................................................
Inventory from OAM ETH DM Tool When to use
This function shows object related to an ETH DM Tool. Related Information
For more information, refer to “Packet Delay measurement” (p. 24-34). For general information about DM/SLM Tool, refer to “Delay measurement and Loss measurement” (p. 24-33). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > OAM CC> ETH DM Tool. Result: The list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Select Search > Inventory . Result: The list of related resources is shown. ...................................................................................................................................................................................................
3
Select one type of object: •
ETS EVC
•
Bridge EVC
•
T-MPLS EVC
•
EVC Terminations
• •
OAM MA OAM MEP Result: The list of related object is shown
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-48 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Inventory from OAM ETH SLM Tool Management Delay measurement and Loss measurement ....................................................................................................................................................................................................................................
Inventory from OAM ETH SLM Tool When to use
This function shows object related to an ETH SLM Tool. Related Information
For more information, refer to “Packet Loss measurement” (p. 24-35). For general information about DM/SLM Tool, refer to “Delay measurement and Loss measurement” (p. 24-33). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > OAM CC> ETH SLM Tool. Result: The list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Select Search > Inventory . Result: The list of related resources is shown. ...................................................................................................................................................................................................
3
Select one type of object: •
ETS EVC
•
Bridge EVC
•
T-MPLS EVC
•
EVC Terminations
• •
OAM MA OAM MEP Result: The list of related object is shown
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-49 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Configure OAM ETH DM Tool Management Delay measurement and Loss measurement ....................................................................................................................................................................................................................................
Configure OAM ETH DM Tool When to use
This function configures ETH DM Tool. Related Information
For more information, refer to “Packet Delay measurement” (p. 24-34). For general information about DM/SLM Tool, refer to “Delay measurement and Loss measurement” (p. 24-33). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > OAM CC> ETH DM Tool. Result: The list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Select Action > Configure. Result: The Configure ETH DM Tool window is shown. ...................................................................................................................................................................................................
3
To configure the tool, set the following attributes: •
The field ETH-DM Tool is not modifiable.
•
The field Source MEP is not modifiable.
•
Select Destination MEP from list
•
Select Interval (100 ms, 1 s, 10 s, 1 min, 10 min)
•
Frame Length: Select one of the following options: –
Click the box Random Frame Size
•
– Select Frame Size value Select PM 15Min
•
Select PM 24H
.................................................................................................................................................................................................................................... 1350 OMS 24-50 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Configure OAM ETH DM Tool Management Delay measurement and Loss measurement .................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
Click Ok button. Result: DM Tool is modified. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-51 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Configure OAM ETH SLM Tool Management Delay measurement and Loss measurement ....................................................................................................................................................................................................................................
Configure OAM ETH SLM Tool When to use
This function configures ETH SLM Tool. Related Information
For more information, refer to “Packet Loss measurement” (p. 24-35). For general information about DM/SLM Tool, refer to “Delay measurement and Loss measurement” (p. 24-33). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > OAM CC> ETH SLM Tool. Result: The list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Select Action > Configure. Result: The Configure ETH SLM Tool window is shown. ...................................................................................................................................................................................................
3
To configure the tool, set the following attributes: •
Select ETH-SLM Tool from list
•
The field Interval is not modifiable
•
The field Session Identifier is not modifiable
•
Click PM Unidir 15Min
• •
Click PM Unidir 24H Click PM Bidir 24H
•
Click PM Frame Loss 15Min
•
Click PM Frame Loss 24H
...................................................................................................................................................................................................
4
Click Ok button.
.................................................................................................................................................................................................................................... 1350 OMS 24-52 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Configure OAM ETH SLM Tool Management Delay measurement and Loss measurement ....................................................................................................................................................................................................................................
Result: SLM Tool is modified. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 24-53 8DG42227DAAA 9.6 Issue 3 December 2012
Operation, Administration, and Maintenance (OAM) Management
Configure OAM ETH SLM Tool
....................................................................................................................................................................................................................................
.................................................................................................................................................................................................................................... 1350 OMS 24-54 8DG42227DAAA 9.6 Issue 3 December 2012
25
25 Circuit Emulation Service Management
Overview Purpose
This document describes the management of circuit emulation capable devices in the scope of packet transport networks. Contents CES Overview
25-4
Circuit Emulation Services definition
25-4
TDM client synchronization
25-8
Protection setup after link creation
25-9
CAC tolerance and modulation mode
25-11
Resource assignment to Packet Radio domain
25-12
Resource assignment to T-MPLS domain
25-14
Packet Radio domain OAM and protections
25-17
Packet Radio performance monitoring
25-19
Packet Radio protection group
25-20
Loopback management
25-21
T-MPLS domain OAM and protections
25-22
Packet Radio domain QoS management
25-24
Packet Radio domain inter-working
25-25
T-MPLS domain inter-working
25-26
Circuit Emulation Service Management
25-27
MEF8 CES terminated service
25-33
Generic Circuit Emulation implementation
25-36
MEF8 Circuit Emulation Service implementation
25-38
SATOP Circuit Emulation Service implementation
25-43
Generic Circuit Emulation Service OAM and protections
25-45
................................................................................................................................................................................................................................... 1350 OMS 25-1 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management
Overview
....................................................................................................................................................................................................................................
MEF8 Circuit Emulation Service OAM and protections
25-46
SATOP Circuit Emulation Service OAM and protections
25-48
Circuit Emulation AAR Network Operation
25-50
CES Takeover description
25-52
CES Procedures
25-53
Circuit Emulation Service graphical inventory
25-55
View the list of CES Domains (Packet Radio)
25-58
View the details of CES Domain (Packet Radio)
25-59
Inventory from CES Domain (Packet Radio)
25-60
Create CES Domain (Packet Radio)
25-61
Assign/Deassign resources to Packet Radio Domain
25-62
Assign/Deassign resources to T-MPLS Domain
25-63
View the list of CES NEs
25-64
Description of the list of CES NEs
25-65
View the details of CES NE
25-66
Details of CES NE
25-67
Inventory from CES NE
25-68
Inventory from Protection Group
25-70
View the list of CES Transport Links
25-71
Description of the list of CES Transport Links
25-72
View the details of CES Transport Link
25-73
Details of the CES Transport Link
25-74
Inventory from CES Transport Link
25-75
Inventory from CES Transport Link extremity
25-76
View the list of CES PDH Ports
25-78
Description of the list of CES PDH Ports
25-79
View the details of CES PDH Port
25-82
Details of CES PDH Port
25-83
Inventory from CES PDH Port
25-84
List CES Edge Ports
25-85
Description of the list of CES Port
25-86
View the details of CES Edge Port
25-87
Details of CES Port
25-88
Inventory from CES Edge Port
25-89
View the list of CES Links Over Radio
25-90
.................................................................................................................................................................................................................................... 1350 OMS 25-2 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management
Overview
....................................................................................................................................................................................................................................
Description of the list of CES Links Over Radio
25-91
View the details of CES Link Over Radio
25-92
Details of CES Link Over Radio
25-93
Inventory from CES Link Over Radio
25-94
Synchronization of CES Link Over Radio
25-96
View the list of CES Radio Ports
25-97
Description of the list of CES Radio Ports
25-98
View the details of CES Radio Port
25-99
Details of CES Radio Port
25-100
Inventory from CES Radio Port
25-101
View the list of CES VLAN Paths
25-102
Description of the list of CES VLAN Paths
25-103
Join CES tunnels
25-104
Stitch CES tunnels
25-105
View the list of Circuit Emulation Services
25-106
Description of the list of Circuit Emulation Services
25-107
View the list of CES Terminations
25-114
Description of the list of CES Terminations
25-115
Create Circuit Emulation Service
25-122
Inventory from CES
25-126
Configure CES
25-127
Routing display of CES
25-130
Configure CES terminations
25-131
Takeover procedure for MEF8 CES
25-132
Takeover procedure for SATOP CES
25-134
.................................................................................................................................................................................................................................... 1350 OMS 25-3 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Circuit Emulation Services definition
....................................................................................................................................................................................................................................
CES Overview Circuit Emulation Services definition Supported network scenarios
Circuit emulation services are typically deployed in the scope of mobile back-hauling network scenarios. Figure 25-1 Mobile back-hauling scenario
The packet radio domain covers the access network, while the aggregation network can be: •
an SDH/SONET network inter-working at TDM level
•
another packet domain (e.g. T-MPLS, ETS) inter-working at Ethernet level
Network layering
The circuit emulation layer is a service layer that uses the Ethernet layer as underlying transport layer in the access network, where the physical transport is based on microwaves.
.................................................................................................................................................................................................................................... 1350 OMS 25-4 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Circuit Emulation Services definition
....................................................................................................................................................................................................................................
Figure 25-2 Network layers in case of unterminated CE service
PKT manages both E1 terminated services covering the first scenario and also unterminated services covering the latter. When the access network does not need radio links, the T-MPLS domain may cover both the access and the aggregation networks. CES infrastructure
Circuit Emulation Services can be transported over Packet Radio technology or, over T-MPLS technology. To prepare the transport infrastructure, the user has to assign the transport resources (links or ports) to the relevant transport domain (Packet Radio or T-MPLS). Then, the system automatically configures the resources for Circuit Emulation Service support. The resources available as infrastructure at the CES layer, are shown as follows: • • •
the Packet Radio or T-MPLS domain is mirrored into CES domain the Link over Radio/Link over Cable or Link over T-MPLS is mirrored into CES transport link the PDH or Ethernet Port is mirrored into CES port
.................................................................................................................................................................................................................................... 1350 OMS 25-5 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Circuit Emulation Services definition
....................................................................................................................................................................................................................................
Figure 25-3 Transport Layer representation
Supported External Products
Circuit Emulation Services supports the following products: •
•
9500 MPR family products: – 9500 MPR R1.3 – 9500 MPR R1.4 – 9500 MPR R2.1 TSS family products: – – –
TSS-5C R1.0 TSS-5C R7.x TSS-320 R4.0
.................................................................................................................................................................................................................................... 1350 OMS 25-6 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Circuit Emulation Services definition
....................................................................................................................................................................................................................................
External Interfaces
PKT handles the following management interfaces: •
towards 9500 MPR
•
– NMD-IM Q3 (for the NE equipment) – CSG IDL (for port synchronization, transmission alarms and service provisioning) towards TSS – –
NMD-IM SNMP (for the equipment) CSG IDL (for port synchronization, transmission alarms and service provisioning)
TDM traffic encapsulation
The packetized TDM traffic is encapsulated according to one of the following standards: • •
MEF 8 IETF SAToP
MEF 8 vs. SAToP encapsulation
Comparing MEF8 and SATOP encapsulation types, it is clear that - from the switching point of view - the ECID label plays the role of the PW label, while the SVLAN plays the role of the LSP tunnel label. The transport of end-to-end TDM service in the Packet Radio network is based on MEF 8 encapsulation. In case of MEF8 encapsulation, the ECID identifies the emulated circuit being carried. This separates the identification of the emulated circuit from the Ethernet layer. ECID have local significance only, and are associated with a specific MAC address. In case of MEF8 over Packet Radio, the mapping between ECID and VLAN is 1:1.In case of MEF8 over 802.1ad, the packet can have single or double VLAN tag In case of MEF8 over T-MPLS, the packet can be untagged or single-tagged.
.................................................................................................................................................................................................................................... 1350 OMS 25-7 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
TDM client synchronization
....................................................................................................................................................................................................................................
TDM client synchronization Synchronization between CES terminations
Synchronization between CES terminations is needed at the termination where the TDM signal is reconstructed from the packets, using the following alternative options: • • •
clock recovered from the TDM network interface (TDM line timing) external reference clock source (External timing) recovering the clock from the packet network interface (Packet line timing). Timing recovery from Packet line relies on Synchronous Ethernet boards
Timing information is extracted from: •
the TDM network interface we have “synchronous” timing, where TDM clients must be traceable to the same synchronization source. In synchronous timing, synchronization network clock is available at TDM client (TDM end systems), not from the packet transport network (PTN). No TDM frequency transparency is required over the PTN
•
the packet network interface we have: –
–
“differential timing”, where the clock is recovered from a combination of data contained in the frames, and knowledge of a reference clock common to both CES edge nodes. In differential timing method, synchronization clock is available at node edges of PTN (CES edge nodes) and requires TDM frequency transparency through the PTN “adaptive timing”, where the clock is recovered from data in the frames, and the arrival time of the frames. The adaptive timing is required when no common clock is available for CES edge nodes or TDM clients. This method relies on the measuring the mean rate of packet arrivals to establish the rate of TDM interface at egress and does not require network synchronization or timing protocols (i.e. RTP), but requires TDM frequency transparency through the PTN
.................................................................................................................................................................................................................................... 1350 OMS 25-8 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Protection setup after link creation
....................................................................................................................................................................................................................................
Protection setup after link creation Workaround to setup the protection after link creation
Because of the change in the port naming rule, the user is recommended to avoid setting up protections before the radio links are taken in charge by NMS. If it is required to setup the protection after link creation in the NMS, the following user procedure must be used as workaround: • • • • •
Manually deassign the radio link from CE domain (automatic unlock sent to NPR) Manually remove the radio link from NPR (object deletion sent by NPR to PKT) -> if needed, PKT automatically deletes the radio link Manually resynchronize ports from NPR: unprotected port is deleted and protecting port is created Manually resynchronize ports from PKT: unprotected port is deleted and protecting port is created Manually create radio link in NPR (object creation sent by NPR to PKT): PKT automatically creates the protecting radio link (since it is a protecting one, assignment to CE domain is forbidden)
Protection schemes
There are two protection schemes: • •
1+1 HSB (hot standby) 1+1 FD (frequency diversity)
.................................................................................................................................................................................................................................... 1350 OMS 25-9 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Protection setup after link creation
....................................................................................................................................................................................................................................
Figure 25-4 CES 9500 MPR Protection schemes
.................................................................................................................................................................................................................................... 1350 OMS 25-10 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
CAC tolerance and modulation mode
....................................................................................................................................................................................................................................
CAC tolerance and modulation mode Relation between CAC tolerance and modulation mode
The modification of the CAC tolerance implies to update the homonymous attribute on all domain nodes. The modification of the CAC tolerance impacts the way CAC checks are performed on radio ports, in accordance with the modulation mode, as summarized by the following picture. Figure 25-5 CES Relation between CAC tolerance and modulation mode
The loose CAC tolerance is meaningful only in case of adaptive radio modulation mode. In such case, CAC for TDM2TDM and TDM2ETH traffic is performed with respect to the peak bandwidth. In case of loose CAC tolerance, if the effective bandwidth is reduced to the minimum capacity, all TDM2TDM and TDM2ETH traffic is disconnected and only ETH2ETH traffic is preserved. In case of adaptive modulation mode and strict CAC tolerance, CAC for TDM2TDM and TDM2ETH traffic is performed with respect to the 4QAM bandwidth, while the peak bandwidth is exploited only by ETH2ETH services. In all cases, ifSpeed reports the correct capacity value for CAC.
.................................................................................................................................................................................................................................... 1350 OMS 25-11 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Resource assignment to Packet Radio domain
....................................................................................................................................................................................................................................
Resource assignment to Packet Radio domain Port assignment to Packet Radio domain
The user selects one MPR PDH or Ethernet port and assigns it to Packet Radio domain. The assigned port is automatically inserted in the scope of the Packet Radio domain as edge port. In case of Ethernet physical port, it is automatically activated by the system. The following table summarizes the port technologies that can be assigned at the edge of a Packet Radio domain. Port technology
Can be assigned as edge port
Ethernet
Yes
Radio
No
PDH
Yes
Port deassignment from Packet Radio domain
The user selects one MPR PDH or Ethernet port and deassigns it from Packet Radio domain. The deassigned port is automatically removed from the scope of the Packet Radio domain as edge port. PKT checks that there are no supported services using that port, i.e. that the used bandwidth is zero for this port. The used bandwidth is set by the manager that is responsible for service provisioning on this port. Transport Link assignment to Packet Radio domain
The user selects one link over radio or link over cable and assigns it to Packet Radio domain. The assigned link is automatically inserted in the scope of the Packet Radio domain as transport link. One protecting radio link (as recognized by means of the naming rule) cannot be assigned to the Packet Radio domain. In case of link over cable, its Ethernet terminations are automatically activated by the system (if not already active). When the manager allocates one service over the TL, it increments the link reserved CIR in order to lock the link and prevent its deletion. Transport Link deassignment from Packet Radio domain
The user selects one link over radio or link over cable and deassigns it from Packet Radio domain. The deassigned link is automatically removed from the scope of the Packet Radio domain as transport link. PKT checks that no services use that transport link. In case of link over cable, its Ethernet terminations are not automatically deactivated by the system, since it is not known if they support inband DCN.
.................................................................................................................................................................................................................................... 1350 OMS 25-12 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Resource assignment to Packet Radio domain
....................................................................................................................................................................................................................................
Transport Link manual synchronization
PKT supports the manual synchronization of the CE transport link: •
in case of cable transport technology, the synchronize command is disabled
•
in case of radio transport technology, the synchronize command is enabled and uploads the available bandwidth from both radio ports: in case of mismatch, the minimum value is reported on the transport link and a warning message is returned to the user
DCN inband management
MPR does not manage opticsIMIfDataManagementPlaneLabel MIB object. Currently inband DCN is configured at commissioning time via dedicated VLAN that MPR does not recognizes as dedicated to DCN. The CPU is connected to one Ethernet physical port that has been characterized as DCN port via proprietary tables
.................................................................................................................................................................................................................................... 1350 OMS 25-13 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Resource assignment to T-MPLS domain
....................................................................................................................................................................................................................................
Resource assignment to T-MPLS domain TSS-5C PDH Port assignment to T-MPLS domain
The user selects one TSS-5C PDH port and assigns it to T-MPLS domain; then it is inserted as CES port under the T-MPLS domain. No change with respect to common TSS behavior is foreseen about the assignment of TSS-5C Ethernet physical ports and SDH terminations to T-MPLS domain. TSS-5C ETH Port assignment to T-MPLS domain
In case of Ethernet physical port, it is a port shared for Ethernet and CE services and therefore it is inserted both as ETH edge port and CES port under the T-MPLS domain. PKT manages the reserved bandwidth for Ethernet and CE services: • •
CIR allocated for EVC CIR allocated for CES
PKT sums up the reserved CIR allocated by each manager and locks the port preventing deassignment from T-MPLS domain. It is up to the user to ensure that the bandwidth reserved for EVC and for CES do not exceed the interface rate. The following table summarizes the different services that are supported at the edge of a T-MPLS domain Port technology
When assigned to T-MPLS domain, it must inserted into
Ethernet
T-MPLS edge port list, CES port list
PDH
CES port list
TSS-5C Port deassignment from T-MPLS domain
The user selects one TSS-5C PDH or Ethernet port and deassigns it from T-MPLS domain. PKT checks that there are no supported services using that port. The deassigned port is automatically removed from the scope of the T-MPLS domain as: •
CES port and T-MPLS edge port, in case of Ethernet physical port
•
CES port, in case of PDH port
Link over T-MPLS reservation for CES
When one T-MPLS PW gets implemented, it is automatically inserted in the list of Links over T-MPLS. Each link over T-MPLS must be used alternatively either for EVC or for CES. The management of the following attributes must be introduced in the Link over T-MPLS: •
Supported service: EVC, CES
.................................................................................................................................................................................................................................... 1350 OMS 25-14 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Resource assignment to T-MPLS domain
....................................................................................................................................................................................................................................
The link over T-MPLS is inserted in: • •
when the supported service is EVC: it is inserted in the Ethernet transport link list when the supported service is CES: it is inserted in the CES transport link list and T-MPLS PW terminations are inserted into CES port list (with interface type = T-MPLS)
When allocating the CES over the Link over T-MPLS, PKT updates the reserved CIR/PIR/CBS/PBS as follows: • •
reserved PIR = reserved CIR = ΣCES CIR , where the sum extends to all CES allocated over this Link reserved PBS = reserved CBS = ΣCES CBS , where the sum extends to all CES allocated over this Link
When the reserved bandwidth parameters are different from zero, the T-MPLS PW can not be deimplemented, therefore preventing CES transport link removal. Management of T-MPLS PW control word and supported service
The following attributes are introduced in the T-MPLS PW: • •
Supported service: EVC (default), CES Control word: disabled (default), enabled
The supported service can be configured by user at any time, even when the T-MPLS PW is implemented. The supported service is meaningful only inside PKT scope: •
when the supported service is EVC, the corresponding Link over T-MPLS is notified only to Ethernet manager
•
when the supported service is CES, the corresponding Link over T-MPLS is notified only to CES manager
From PKT architecture point of view, changing the supported service implies to move the Link over T-MPLS from one manager’s scope to the other. Therefore, the supported service cannot be modified if any of the Link over T-MPLS bandwidth parameters (reserved CIR, reserved PIR, reserved CBS, reserved PBS) is different from zero. When the supported service is EVC, the user has the option to configure also the control word enabling/disabling, independently of the T-MPLS PW’s configuration status (allocated or implemented). When the supported service is CES, then: • •
the control word is automatically enabled by PKT the PW bandwidth parameters are pre-filled by PW creation wizard with the following default values (the user can modify them): –
CIR = PIR = 2432 Kbit/s
–
CBS = PBS = 2900 bytes (2*MTU as suggested value)
The above values allow to support one CE service for all possible values of payload size (independently from the underlying layer).
.................................................................................................................................................................................................................................... 1350 OMS 25-15 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Resource assignment to T-MPLS domain
....................................................................................................................................................................................................................................
The control word is provisioned to the NE via TL1 only to the T-MPLS PW termination segments. TSS-5C NE configure timestamp frequency
The system supports the configuration of the RTP timestamp frequency, used by CE services with differential timing mode and RTP enabled. The system checks that there are no implemented CES on the TSS NE to be configured. The TSS-5C timestamp frequency supported range is: • • •
77.76 MHz 25 MHz (default) 16.384 MHz
.................................................................................................................................................................................................................................... 1350 OMS 25-16 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Packet Radio domain OAM and protections
....................................................................................................................................................................................................................................
Packet Radio domain OAM and protections Alarm correlation
PKT manages reports the elementary alarms generated by MPR and also correlates them to transport resources. The alarm correlation can be: • •
horizontal: the originating alarmed resource is an elementary object and the correlated resource is a transport object at the same layer vertical: the originating alarmed is resource is a transport object and the correlated resource is a transport object at the client layer
Figure 25-6 Horizontal and vertical alarm correlation in Packet Radio domain
Both horizontal and vertical correlation are always enabled on Packet Radio domain. The availability status of the client transport object has the value: •
transport failure, in case of horizontal correlation
•
server transport failure, in case of vertical correlation
.................................................................................................................................................................................................................................... 1350 OMS 25-17 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Packet Radio domain OAM and protections
....................................................................................................................................................................................................................................
MPR R1.4 URU alarm management
Since R1.4 MPR sends URU in the following cases and on the following objects: •
All E1 TTP in case of PDH card failure
• •
All Radio TTP in case of Radio card failure All E1 TTP, radio TTP and MAU entries in case of Core card failure (apart from radio TTP involved only in MPT to MPT connections switched by the same RAD_ACC) The involved MAU entry in case of SFP failure
•
PKT correlates the URU to the impacted CE services according to the following propagation chain: •
Horizontal: URU on PDH port (PDH card failure) -> CES transport failure
•
Vertical: URU on Radio/ETH port (Radio card failure or SFP failure) -> Radio/Cable link transport failure -> VLAN tunnel server transport failure -> CES server transport failure
Elementary alarms on 9500MPR PDH ports
PKT receives via CSG the elementary alarms on PDH ports and persists them in database. At PKT startup the PDH elementary alarms are automatically resynchronized. The Underlying Resource Unavailable (URU) alarm represents equipment failures (e.g. card missing) that affect services. Alarms on PDH ports are synchronized from active problem table PKT correlates horizontally the PDH port failure to the impacted CES •
LOS on PDH port -> CES transport failure
Since MPR R2.1, the LosCesFrame alarm is supported on PDH port. The LosCesFrame alarm replaces the LOF alarm on CES termination supported by MPR R1.4. Elementary alarms on 9500MPR radio ports
PKT receives via CSG the elementary alarms on radio ports and persists them in database. At PKT startup the radio elementary alarms are automatically resynchronized. PKT correlates vertically the Radio elementary alarms to the impacted CE services according to the following propagation chain: •
alarm (e.g. cableLoss) on Radio port -> Radio link transport failure -> VLAN tunnel server transport failure -> CES server transport failure
.................................................................................................................................................................................................................................... 1350 OMS 25-18 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Packet Radio performance monitoring
....................................................................................................................................................................................................................................
Packet Radio performance monitoring 9500MPR PDH port performance monitoring
The operator can enable PM on a given CES at creation time or manually later, specifying the desired granularity: 15min or 24h. The enabling is performed via navigation to JUSM. MPR supports current and historical counters on the PDH ports for monitoring both the incoming and outgoing E1 signal. They are persisted in NE agent cache memory. The management has to start/stop one counter for each direction. So PM counters are available to monitor the signal in both directions at the edge of the MPR network in case of PDH edge port. PDH measures are currently stored by NMS in the same database as SDH measures, different from the Ethernet database. An architectural evolution of the CPM component for PKT is required to manage PDH PM. 9500MPR Radio port performance monitoring
Managed via navigation to JUSM. MPR supports 15min/24h maintenance counters on radio ports. EMLIM elaborates historical counters via periodic samples. At radio level it is possible to monitor both the single radio link termination and the radio link protected termination. It is also possible to monitor the Ethernet packets enqueued in the queues assigned to pass-through Ethernet services. MPR supports only free running maintenance counters on Ethernet queues of radio ports. All these counters are available only in transmission. PKT is not requested to manage PM counters on radio ports. 9500MPR Ethernet port performance monitoring
Managed via navigation to JUSM. MPR supports only free running maintenance counters on Ethernet ports. EMLIM currently does not elaborate historical counters via periodic samples. These counters are available both in transmission and reception. PKT not requested to manage maintenance counters.
.................................................................................................................................................................................................................................... 1350 OMS 25-19 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Packet Radio protection group
....................................................................................................................................................................................................................................
Packet Radio protection group Radio protection group switch commands via navigation
The operation of the radio protection group switch position is managed via navigation to JUSM Switch position synchronization of single radio protection group
The operator is allowed to select one protection group and to start manually the synchronization operation of the switch position for the selected protection group. PKT retrieves and updates the current active switch position, the current switch command, the current switch criteria and re-triggers alarm correlation for the involved radio links and supported services.
.................................................................................................................................................................................................................................... 1350 OMS 25-20 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Loopback management
....................................................................................................................................................................................................................................
Loopback management 9500MPR Loopback management
PDH loopback is a loop and continue -> only one traffic direction is impacted. When the PDH loopback is activated, MPR sends an event telling which is the involved port, the direction and the type (internal, external). Radio loopback is a simple loop -> both traffic directions are affected. When the Radio loopback is activated on ODU300 access, MPR sends an event telling which is the involved radio port, the direction and the type (internal, external). In order to alert the operator that the loopback operation has affected the traffic: •
In case of simple loop, MPR sends LOF on the CES termination that does not receive the signal (loop and AIS insertion - so that AIS alarm would be raised on egress PDH port - is not supported)
•
In case of loop and continue, no alarm is raised but the port state reports on JUSM the active loopback (the loopback activation event is not managed by PKT)
Switch position synchronization of single radio protection group
The operator is allowed to select one protection group and to start manually the synchronization operation of the switch position for the selected protection group. PKT retrieves and updates the current active switch position, the current switch command, the current switch criteria and re-triggers alarm correlation for the involved radio links and supported services.
.................................................................................................................................................................................................................................... 1350 OMS 25-21 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
T-MPLS domain OAM and protections
....................................................................................................................................................................................................................................
T-MPLS domain OAM and protections TSS-5C PDH Port assignment to T-MPLS domain
PKT manages reports the elementary alarms generated by TSS and also correlates them to transport resources. The alarm correlation can be: • •
horizontal: the originating alarmed resource is an elementary object and the correlated resource is a transport object at the same layer vertical: the originating alarmed is resource is a transport object and the correlated resource is a transport object at the client layer
Figure 25-7 Horizontal and vertical alarm correlation in T-MPLS domain
Vertical correlation is always enabled on T-MPLS domain: • •
from PW to MPLS Tunnel from ETH CES port to CES
Horizontal correlation is always enabled on T-MPLS domain: • •
from PDH CES port to CES from CES Termination to CES
The availability status of the client transport object has the value: •
transport failure, in case of horizontal correlation
•
server transport failure, in case of vertical correlation
.................................................................................................................................................................................................................................... 1350 OMS 25-22 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
T-MPLS domain OAM and protections
....................................................................................................................................................................................................................................
TSS-5C NE configure PDH degrade thresholds
The system supports the configuration of the degrade thresholds, that are used to generate and clear the degrade alarm on PDH ports. The system checks that there are no implemented CES on the TSS NE to be configured. The supported ranges and default values are: • • • •
PDH degrade observation interval range: 2-10 seconds PDH degrade observation interval default: 5 seconds PDH degrade raise threshold range: 0-1000 errors PDH degrade raise threshold default: 30 errors
• •
PDH degrade clear threshold range: 0-1000 errors PDH degrade clear threshold default: 20 errors
The raise threshold must be strictly higher than the clear threshold. Elementary alarms on TSS-5C PDH ports
PKT receives via CSG the elementary alarms on PDH ports and persists them in database. At PKT startup the PDH elementary alarms are automatically resynchronized. PKT correlates horizontally the PDH port failure to the impacted CES, e.g.: •
LOS on PDH port -> CES transport failure
Elementary alarms on TSS-5C Ethernet ports
PKT receives via CSG the elementary alarms on Ethernet ports and persists them in database. At PKT startup the Ethernet elementary alarms are automatically resynchronized. PKT correlates vertically the ETH elementary alarms to the impacted CE services according to the following propagation chain: • •
Edge port: alarm (e.g. LOS) on ETH port -> CES server transport failure Link over cable : alarm (e.g. LOS) on ETH port -> Cable link transport failure -> Tunnel server transport failure -> CES server transport failure
Correlation of elementary alarms to link over PDH
PKT correlates elementary PDH interface alarms to link over PDH, if any.
.................................................................................................................................................................................................................................... 1350 OMS 25-23 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Packet Radio domain QoS management
....................................................................................................................................................................................................................................
Packet Radio domain QoS management Provisioning of ports (via navigation)
The configuration of specific PDH interface characteristics that are independent of the CE service are supported via navigation to MPR JUSM. The configuration of all Radio interface characteristics that are independent of the CE service are supported via navigation to MPR JUSM.
.................................................................................................................................................................................................................................... 1350 OMS 25-24 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Packet Radio domain inter-working
....................................................................................................................................................................................................................................
Packet Radio domain inter-working inter-working
The Packet Radio domain can physically interwork with other domains either at the PDH or Ethernet level. Table 25-1
Allowed interface type, depending on link technology
Link technology
Interface type NNI
IWI
Link over radio
Yes
No
Link over cable
Yes
Yes
Link over PDH
No
Yes
In particular, a link over cable or a link over PDH can be used as the domain inter-working interface in the cases described by the following RATS. • • • •
PKT is requested to manage inter-working Ethernet cable links between Packet Radio domain and ETS domain. PKT is requested to manage inter-working Ethernet cable links between Packet Radio domain and T-MPLS domain. PKT is requested to manage inter-working Ethernet cable links between Packet Radio domain and PB domain. PKT is requested to manage inter-working PDH cable links between Packet Radio domain and SDH domain. The SDH domain is managed by SDH application. The PDH IWI cable is uploaded from NPR.
E2E PDH: Manual synchronization of PDH inter-working links
PKT manages the upload via NPR-NBI of PDH links that terminate e.g. on 9500MPR or on TSS NE’s. The upload is triggered manually by operator, as in the link over cable case. NPR creates the PDH IWI link characterizing it with PDH technology. The NPR message response contains, for each extremity, the node userlabel and the port userlabel. PKT ensures that in DB both nodes that terminate the PDH link are present: one of them is e.g. the MPR/TSS NE, while the other could be any OMSN NE or other not-managed NE. PKT gets via NPR-NBI also the NE type and Node ID of the not-managed NE. E2E PDH: Management of network role on PDH port
When the operator assigns one PDH port as edge port to the Packet Radio domain, the network role has the following values: •
UNI -> when there is not PDH IWI link
•
E-NNI -> when the PDH port is the termination of a PDH IWI link
CE manager must be aware of the PDH network role since this network role is reported in the CES routing display. .................................................................................................................................................................................................................................... 1350 OMS 25-25 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
T-MPLS domain inter-working
....................................................................................................................................................................................................................................
T-MPLS domain inter-working Management of inter-domain link: T-MPLS domain – SDH domain
PKT is requested to manage inter-working PDH cable links between T-MPLS domain and SDH domain. The SDH domain is managed by SDH application. The PDH IWI cable is uploaded from NPR.
.................................................................................................................................................................................................................................... 1350 OMS 25-26 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Circuit Emulation Service Management
....................................................................................................................................................................................................................................
Circuit Emulation Service Management Circuit Emulation Service security
PKT supports the capability to prevent the setup of misconnections. Port segregation
Port segregation is supported by MPR both on Ethernet and radio ports. If more than two ports must be segregated, one MIB entry is created for each segregated port pair. Generic Circuit Emulation Service creation and allocation
A Circuit Emulation Service is a transport connection between remote E1 ports, where the PDH stream is segmented and encapsulated into Ethernet packets. The service can be terminated by PDH ports at both ends or unterminated: in the latter case the PDH stream is not reconstructed at one service termination and the PDH traffic is forwarded to the client equipment either encapsulated into Ethernet packets or into channelized STM-n. The service CIR is automatically computed by PKT: •
based on interface type, service profile and clock source in case of MEF-8
•
based on payload size in case of SATOP, CBS is not managed in case of MEF-8.
Manual join a tunnel to a CES
The Tunnel is the object that represents the transport route within a given domain. The CES itself is the transport object that can represent the routing across different domains: • •
The different domains are the nodes of the routing graph The Tunnel is the connectivity inside one graph node
Two different Tunnels associated to distinct domains (no e2e Tunnel is created) can be manually joined or stitched to the CES in order to realize one e2e CES: •
Join is possible if one Tunnel already supporting CES and the Tunnel being joined are connected by one transport link
•
Stitch is possible if one Tunnel already supporting CES and the Tunnel being stitched share one logical port
Because of Tunnel join or stitching, one CES can be supported by one or many Tunnels and one Tunnel can support one or more CES. Tunnel joined to CES: after join, the CES is supported by one tunnel in each crossed domain and the two tunnels are connected by one transport link
.................................................................................................................................................................................................................................... 1350 OMS 25-27 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Circuit Emulation Service Management
....................................................................................................................................................................................................................................
Figure 25-8 CES after join
Tunnel stitched to CES: after stitching, the CES is supported by one tunnel in each crossed domain and the two tunnels share the same logical E1 port Figure 25-9 CES after stich
.................................................................................................................................................................................................................................... 1350 OMS 25-28 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Circuit Emulation Service Management
....................................................................................................................................................................................................................................
After tunnel join or stich, no new e2e CES object is created, but the e2e CES preserves the identity of the CES across a single domain: • •
When the CES is supported by one single Tunnel, then it is a CES fragment When the CES is supported by many Tunnels (i.e. it joins or stitches different Tunnel fragments), then it is an e2e CES
The Tunnel is created in PKT database when the service is created. At service creation time, PKT creates one pair of Tunnel segments in each crossed NE. At service creation time, PKT creates one XC in each crossed NE. Management of CES CoS and encapsulation type
The following new attributes are introduced on CES: •
CoS: G, G2, R1, R, R3, R4, BE, BK
• •
Encapsulation type: MEF8, SATOP Transport type: CesOverPacketRadio, CesOverT-MPLS
The Class of Service (CoS) is configurable only in case of CesOverT-MPLS. The encapsulation type and transport type are automatically computed by PKT depending on the underlying transport domain: Table 25-2
Relation between CES transport type and encapsulation type
Domain
Transport type
Encapsulation type
Packet Radio
CesOverPacketRadio
MEF8
T-MPLS
CesOverT-MPLS
SATOP
CES CoS compatibility check with T-MPLS PW PHB Profile
The CES CoS specified by operator at CES creation time must be compatible with the PHB Profile of the supporting T-MPLS PW – aka Link over T-MPLS. In fact, if a 5-classes PHB Profile was associated to the T-MPLS PW, then not all CoS are not supported. Table 25-3
CoS supported vs. T-MPLS PHB Profile
CoS
Supported in PHB Profile #1
Supported in PHB Profile #2
G
Y
Y
G2
Y
Y
R1
N
Y
R(2)
Y
Y
R3
N
Y
R4
Y
Y
BE
Y
Y
.................................................................................................................................................................................................................................... 1350 OMS 25-29 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Circuit Emulation Service Management
....................................................................................................................................................................................................................................
Table 25-3
CoS supported vs. T-MPLS PHB Profile
(continued)
CoS
Supported in PHB Profile #1
Supported in PHB Profile #2
BK
N
Y
PKT does not check that: • •
the requested CES CoS is compatible with the supported CoS of the selected Link over T-MPLS (bottom-up CES creation) the automatically created Link over T-MPLS supports the requested CES CoS (top-down CES creation)
If the operator chooses one CoS that is not supported by the T-MPLS PW, then the CES traffic will be treated as belonging to the nearest lower supported CoS when forwarded in the T-MPLS network. Management of tunnel type
The Tunnel creation: • • •
in case of MEF8 over Packet Radio domain, PKT creates Packet-Radio Tunnel in case of SATOP over T-MPLS domain, PKT creates T-MPLS Tunnel in case of MEF8 over 802.1ad or T-MPLS domain (where it corresponds to one p2p EVC), PKT creates Ethernet Tunnel
•
in case of PDH over SDH domain (where it corresponds to one SDH Path), PKT creates SDH Tunnel
Therefore the Tunnel is characterized by a type that is automatically computed by PKT according to the underlying transport technology: Packet-Radio, T-MPLS, ETH, SDH. Routing display of CES
The operator can open the graphical routing display of one CES. PKT shows the CES routing display in two layers: •
CES (i.e. PW) layer: it shows the crossed Tunnel
•
Tunnel layer: it shows all crossed link over radio or link over cable or link over T-MPLS
At the CES layer, the following resources are displayed: •
Edge nodes (A and Z)
• • •
Edge ports (PDH port or physical Ethernet) CES terminations Tunnel termination segments
•
Tunnel
.................................................................................................................................................................................................................................... 1350 OMS 25-30 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Circuit Emulation Service Management
....................................................................................................................................................................................................................................
At the Tunnel layer, the following resources are displayed: • • • • •
Edge and transit nodes NNI ports (Radio port or physical Ethernet or logical T-MPLS PW terminations) of edge and transit nodes Radio links (in case of 1+1 protection, the radio link with working protection role is displayed) or cable links or T-MPLS links: Tunnel segments (termination and intermediate) Cross-connections between tunnel segments
PKT shows graphically the above resources by means of a dedicated icon: clicking on the icon, the resource properties are displayed. Figure 25-10 CES routing display
.................................................................................................................................................................................................................................... 1350 OMS 25-31 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Circuit Emulation Service Management
....................................................................................................................................................................................................................................
Figure 25-11 Tunnel routing display
Manual deallocation and deletion of CES
PKT manages the unreservation of database resources for selected CE service and the CE service removal from database. The CES deallocation triggers the automatic Tunnel deallocation. The CES deletion triggers the automatic Tunnel deletion.
.................................................................................................................................................................................................................................... 1350 OMS 25-32 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
MEF8 CES terminated service
....................................................................................................................................................................................................................................
MEF8 CES terminated service Basic creation and allocation over Packet Radio
PKT is requested to support the following service profiles (corresponding to a particular radio compression): • •
TDM2TDM TDM2ETH
TDM services are switched on local MAC address basis (each PDH board is assigned an internal MAC address). The default service profile that is proposed to the operator is: • •
TDM2TDM for terminated services TDM2ETH for unterminated services
In case of underlying radio infrastructure, the operator can select any service profile. In case of underlying Ethernet physical infrastructure (link over cable or edge port), only the TDM2ETH service profile is admitted. The TDM2TDM service is characterized by one specific VLAN on network basis. MPR supports TDM2TDM services with proprietary encapsulation, i.e. not MEF-8. For this reason a TDM2TDM service profile must be terminated at the edge of the MPR network. Therefore, in case of unterminated CES, the TDM2ETH service profile must be used and the MAC DA of the Ethernet frame outgoing from one GE interface must manually configured by operator. Details
The main service characteristic is the VLAN ID (in the range 2..4080): it is selected by operator or it can be automatically selected by the system. VLAN ID must be unique per service in all MPR network, otherwise loss of E1 signal could occur. In case of TDM2TDM service profile, the PW label (aka ECID) is automatically computed by MPR and is 1:1 with the service VLAN. In case of TDM2ETH service profile, the ECID can be selected by operator for each service direction. The following CES attributes can always be modified upon operator request: • • •
userlabel service group comment1/comment2/comment3
• •
text1/text2/text3 signal mode to framed/unframed
The following CES attributes can be modified only when the CES is defined: • •
ECID A->Z ECID Z->A
•
Destination MAC address
.................................................................................................................................................................................................................................... 1350 OMS 25-33 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
MEF8 CES terminated service
....................................................................................................................................................................................................................................
All MEF8 CES terminations of all PDH ports belonging to the same card must be configured with the same TDM clock source type. The service creation fails if another service already exists that terminates on the same E1 card and has a different type. Two ports belong to the same card if their slot number “x” is the same; the card slot number is represented in the port’s ifIndex: “60 ‘x’ ‘nn’”. The NE MAC address is used as source address in case of TDM2ETH service profile and is configured by the management system as destination address of the remote NE. In case of TDM2TDM NE MAC address is never used. MPR does not support one MAC address per Ethernet interface. The TDM clock source has to be configured in the NE at XC creation time. The ECID Tx identifies uniquely the PDH destination port in the scope of the card. In fact, the core unit switches packets based on VLAN, while the PDH card switches packets based on ECID Tx. Each CES has an associated Packet-Radio tunnel, representing the Ethernet infrastructure for circuit emulation. In case of MPR NE, the association between CES and Tunnel is 1:1. PKT is requested to apply admission control checks at allocation time. The bandwidth reserved on a given port depends on port technology and also on service characteristics. A new MIB object has been introduced representing the allocated bandwidth for one E1 service over one radio interface: cesCfgBandwidth on opticsIMCESoEthMIB. This MIB object is used to provide the E1 bandwidth occupation vs the radio interface. In general, however, the bandwidth reserved by the service on each interface depends on interface type, service profile and TDM clock source according to the following table. Table 25-4
E1 service bandwidth occupation for MPR R1.3/R1.4
Interface
Service Profile
TDM clock source
Service CIR [Mbit/sec]
Radio
TDM2TDM
Differential
22.852
Radio
TDM2ETH
Differential
22.569
Radio
TDM2ETH
Adaptive
21.844
Ethernet
TDM2ETH
Differential
25.443
Ethernet
TDM2ETH
Adaptive
24.482
The TDM2TDM encapsulation occupies more bandwidth than TDM2ETH one, since it incorporates also some protection overhead. In particular, in case of TDM2ETH service profile, E1 service bandwidth occupation depends also on RTP presence or not. RTP presence depends on TDM clock source value: • •
differential -> RTP present adaptive -> RTP not present
.................................................................................................................................................................................................................................... 1350 OMS 25-34 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
MEF8 CES terminated service
....................................................................................................................................................................................................................................
At allocation time, PKT creates one XC in each crossed NE. MEF8 CES allocation over Packet Radio on MPT radio ports
The bandwidth reserved by one E1 signal is different for ODU300 and MPT ODU. The bandwidth occupied by one E1 signal is computed from a configuration table, using as inputs the following parameters: • •
radio interface type service profile (TDM2TDM, TDM2ETH)
•
TDM clock source (differential, adaptive)
Table 25-5
E1 service bandwidth occupation since MPR R2.1
Interface type
Service Profile
TDM clock source
Service CIR [Mbit/sec]
Radio ODU300
TDM2TDM
Differential
22.852
Radio ODU300
TDM2ETH
Differential
22.569
Radio ODU300
TDM2ETH
Adaptive
21.844
Radio MPT
TDM2TDM
Differential
21.667
Radio MPT
TDM2ETH
Differential
22.579
Radio MPT
TDM2ETH
Adaptive
21.853
Ethernet
TDM2ETH
Differential
25.443
Ethernet
TDM2ETH
Adaptive
24.482
.................................................................................................................................................................................................................................... 1350 OMS 25-35 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Generic Circuit Emulation implementation
....................................................................................................................................................................................................................................
Generic Circuit Emulation implementation relationships between E1 and PW tables
The following picture shows the relationships between E1 and PW tables – depending on NE type – both in case of MEF-8 and SATOP services. Figure 25-12 SNMP MIB relationships between E1 and PW tables
Manual deimplementation of CES
PKT manages the removal of provisioned CE connectivity in the network. The CES deimplementation triggers the automatic Tunnel deimplementation. In case of MPR NE, the automatic pwCTDMCfg deletion is implemented by NE agent when PKT requests the pw deletion: if the pwCGenTDMCfgIndex value of associated pwCTDMTable entry is no longer contained in any other pwCGenTDMCfgIndex object, then the referenced pwCTDMCfgTable entry (that indexed by pwCGenTDMCfgIndex value) has to be deleted.
.................................................................................................................................................................................................................................... 1350 OMS 25-36 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Generic Circuit Emulation implementation
....................................................................................................................................................................................................................................
In case of TSS NE, it is manager (PKT, ZIC) responsibility to maintain 1:1 association between pwEntry and pwCTDMCfgEntry. Therefore PKT will be in charge of explicit pwCTDMCfgEntry deletion. If ZIC allows to reuse the same pwCTDMCfgEntry for two different pw entries, this will cause a failure when PKT tries to deimplement (i.e. delete in the NE) one those services. PKT operator workaround to overcome failure: •
run an audit: the failed service connection will be recognized as allocated (i.e. deleted in the NE)
•
retry the deimplementation of the failed service: the deimplementation will be successful the second time
.................................................................................................................................................................................................................................... 1350 OMS 25-37 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
MEF8 Circuit Emulation Service implementation
....................................................................................................................................................................................................................................
MEF8 Circuit Emulation Service implementation flows supported by 9500MPR NE
When implementing the MEF-8 service, PKT is requested to configure the following flow connections in the 9500MPR NE: • • •
PDH to Radio Radio to Radio Radio to Ethernet
•
PDH to Ethernet
MEF8 CES terminated service implementation
TDM2TDM service profile provisioning PDH To Radio Traffic Flow
The system automatically performs the following provisioning steps: • •
configuration of the PDH port signal mode to unframed/framed Tunnel Termination Segment Creation via SNMP: – creation of Ethernet ingress flow associated to PDH port (service ID = PDH port ifIndex, service type = Ethernet) and corresponding to tunnel termination –
•
creation of TC associated to the VLAN assigned by operator that has to be pushed and represented by the corresponding tunnel segment attribute – creation of CES over Ethernet profile corresponding to the service profile pointing to the ingress flow and represented by the corresponding tunnel segment attribute Tunnel Segment Creation via SNMP: –
• •
creation of Ethernet egress flow associated to Radio port (server ID = Radio port ifIndex, service type = Ethernet) and corresponding to tunnel segment creation of cross-connection between tunnel segments CES termination profile creation via SNMP: nothing to be provisioned
• •
CES termination creation via SNMP: nothing to be provisioned Tunnel Termination Segment Configuration via SNMP: nothing to be provisioned
Radio To Radio Traffic Flow
The provisioning sequence is the same as above. Radio To PDH Traffic Flow
The provisioning sequence is unchanged. Radio To Ethernet Traffic Flow
Ethernet to Radio connection is not allowed in case of TDM2TDM service profile. PDH To Ethernet Traffic Flow
Ethernet to Radio connection is not allowed in case of TDM2TDM service profile.
.................................................................................................................................................................................................................................... 1350 OMS 25-38 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
MEF8 Circuit Emulation Service implementation
....................................................................................................................................................................................................................................
Ethernet To Radio Traffic Flow
Ethernet to Radio connection is not allowed in case of TDM2TDM service profile. MEF8 CES unterminated service implementation
TDM2ETH service provisioning PDH To Radio Traffic Flow (MPR NE)
In case of MPR NE, the system automatically performs the following provisioning steps: • •
configuration of the PDH port signal mode to unframed/framed CES Termination Profile Creation via SNMP: – creation of PW TDM CFG object (fixed payload size = 256, fixed RTP header = true, TDM clock source specified by operator and represented by corresponding CES termination attribute)
•
CES Termination Creation via SNMP: – creation of a PW entry (fixed type = e1Satop(17), ifIndex of the PDH port) -> as a side effect, the NE creates automatically one PW TDM entry that PKT has to configure (TDMboundPWlabel = ECID Rx, PSNboundPWlabel = ECID Tx, PW TDM CFG reference to previously created entry) according to corresponding CES termination attributes Tunnel Termination Segment Creation via SNMP: – creation of Ethernet ingress flow associated to PDH port (service ID = PDH port ifIndex, service type = Ethernet) and corresponding to tunnel termination – creation of TC associated to the VLAN assigned by operator that has to pushed and represented by corresponding tunnel segment attribute
•
–
•
•
creation of CES over Ethernet profile corresponding to the service profile pointing to the ingress flow and to the PW entry (CESCfgPwIndex is set to point to pwIndex) and characterized by tunnel segment’s service profile attribute. Tunnel Segment Creation via SNMP: – creation of Ethernet egress flow associated to Radio port (server ID = Radio port ifIndex, service type = Ethernet) and corresponding to tunnel segment creation of cross-connection between tunnel segments
.................................................................................................................................................................................................................................... 1350 OMS 25-39 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
MEF8 Circuit Emulation Service implementation
....................................................................................................................................................................................................................................
PDH To Radio Traffic Flow (TSS NE)
In case of TSS NE, the system will perform automatically the following provisioning steps: • •
configuration of the PDH port signal mode to unframed/framed Tunnel Termination Segment Creation via SNMP: – creation of Ethernet ingress flow associated to PDH port (service ID = PDH port ifIndex, service type = Ethernet) and corresponding to tunnel termination –
•
• •
•
creation of TC associated to the VLAN assigned by operator that has to pushed and represented by corresponding tunnel segment attribute – creation of CES over Ethernet profile corresponding to the service profile pointing to the ingress flow and characterized by tunnel segment’s service profile attribute. CESCfgPwIndex is not initialized Tunnel Segment Creation via SNMP: – creation of Ethernet egress flow associated to Radio port (server ID = Radio port ifIndex, service type = Ethernet) and corresponding to tunnel segment creation of cross-connection between tunnel segments Ces Termination Profile Creation via SNMP: – creation of PW TDM CFG object (fixed payload size = 256, fixed RTP header = true, TDM clock source specified by operator and represented by corresponding CES termination attribute) CES Termination Creation via SNMP: –
•
creation of a PW entry (fixed type = E1SATOP, ifIndex of the PDH port) -> as a side effect, the NE creates automatically one PW TDM entry that PKT has to configure (TDMboundPWlabel = ECID Rx, PSNboundPWlabel = ECID Tx, PW TDM CFG reference to previously created entry) according to corresponding CES termination attributes Tunnel Termination Segment Configuration via SNMP: – CESCfgPwIndex is set to point to pwIndex
MEF8 CES terminated service implementation
TDM2TDM service profile provisioning PDH To Radio Traffic Flow
The system automatically performs the following provisioning steps: • •
configuration of the PDH port signal mode to unframed/framed Tunnel Termination Segment Creation via SNMP: – creation of Ethernet ingress flow associated to PDH port (service ID = PDH port ifIndex, service type = Ethernet) and corresponding to tunnel termination – –
creation of TC associated to the VLAN assigned by operator that has to be pushed and represented by the corresponding tunnel segment attribute creation of CES over Ethernet profile corresponding to the service profile pointing to the ingress flow and represented by the corresponding tunnel segment attribute
.................................................................................................................................................................................................................................... 1350 OMS 25-40 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
MEF8 Circuit Emulation Service implementation
....................................................................................................................................................................................................................................
•
Tunnel Segment Creation via SNMP: – creation of Ethernet egress flow associated to Radio port (server ID = Radio port ifIndex, service type = Ethernet) and corresponding to tunnel segment
• • • •
creation of cross-connection between tunnel segments CES termination profile creation via SNMP: nothing to be provisioned CES termination creation via SNMP: nothing to be provisioned Tunnel Termination Segment Configuration via SNMP: nothing to be provisioned
Radio To Radio Traffic Flow
The provisioning sequence is the same as above with the exception that ECID Tx/Rx values must not be provisioned (NE configures automatically the zero value). MPR requires the configuration of TDM clock source, payload size and RTP header also on transit nodes: these attributes are conventionally aligned in the scope of the XC object (only in case of transit node and TDM2ETH service profile). Radio To Ethernet Traffic Flow
The provisioning sequence is the same as for the PDH-Radio cross-connection with the addition of the destination MAC address provisioning in the PW table and with the exception that ECID Tx/Rx values must not be provisioned (NE configures automatically the zero value). PDH To Ethernet Traffic Flow
The provisioning sequence is the same as for the PDH-Radio cross-connection with the addition of the destination MAC address provisioning in the PW table. Ethernet To Radio Traffic Flow
MPR does not allow to configure a VLAN range at an Ethernet input port for association to one service flow, but only one single specific VLAN. Ethernet to Radio connection is allowed in case of TDM2ETH service profile. It is a MEF-8 encapsulation with VLAN tag (EtherType 0x8100). It is configured in the same way as radio to Ethernet traffic flow. Radio available bandwidth management during MEF8 CES implementation
The radioPDHTTPBidAvailableBandwith object is used to check if a cross-connection of a TDM signal to/from Radio Direction is feasible (Connection Admission Control) and it is updated automatically by the NE when the cross-connection is created or deleted. CE manager is requested to manage the available bandwidth on Radio ports since the NE also supports ATM services that contend for bandwidth with CE services. In fact, the CAC checks performed by CE manager at allocation time ensure that there is enough available bandwidth on the radio links selected by the routing algorithm, as far as only circuit emulation services are concerned.
.................................................................................................................................................................................................................................... 1350 OMS 25-41 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
MEF8 Circuit Emulation Service implementation
....................................................................................................................................................................................................................................
CE manager is therefore requested to implement the following behavior: • • • •
upload the available bandwidth of the radio port, when the radio link is notified to the Packet Radio domain automatically synchronize the available bandwidth of the radio port during audit operation support manual synchronization of available bandwidth on CE transport link with radio transport technology synchronize the available bandwidth of the radio port before starting CES implementation, for all radio ports along the CES route
The available bandwidth attribute is reported on CE transport links belonging to Packet Radio domain, together with the reserved bandwidth for CE services. MEF8 CES configuration
For a TDM2TDM CES, PKT allows the configuration of the following CES attributes: •
signal mode to framed/unframed (also at run-time)
• •
VLAN (only if the CES is defined) PM enabling/granularity (also at run-time)
Signal mode configuration to framed/unframed is not traffic impacting and it is performed in both PDH ports. VLAN ID is reconfigured in the tunnel segments. PM enabling and granularity is reconfigured in the PDH CES terminations. PM enabling and granularity is reconfigured in the PDH CES terminations. • •
ECID A->Z/ Z->A (only when the CES is defined) destination MAC address (only when the CES is defined)
•
TDM clock source (only when the CES is defined or allocated)
ECID A->Z/ Z->A and destination MAC address are reconfigured in both CES terminations. TDM clock source is reconfigured in both CES terminations. MEF8 CES termination configuration
The CES termination configuration allows to modify the following attributes. For a CES of TDM2TDM service profile, PKT allows to configure the following CES termination attributes: •
PM enabling/granularity
For a defined CES of TDM2ETH service profile, PKT allows additionally to configure the following PW termination attributes: •
destination MAC address
ECID Tx/Rx and TDM clock source are reconfigured only on CES basis. .................................................................................................................................................................................................................................... 1350 OMS 25-42 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
SATOP Circuit Emulation Service implementation
....................................................................................................................................................................................................................................
SATOP Circuit Emulation Service implementation Connections configured by PKT
When implementing the SATOP service, PKT is requested to configure only the following flow connections in the TSS-5C NE: • •
PDH TO T-MPLS T-MPLS TO PDH
SATOP CES implementation
It is assumed that the operator has already provisioned via PKT the required T-MPLS infrastructure for transporting the service across the T-MPLS domain; this implies that PKT has already performed via TL1 the PW segment creation with the following characteristics: • •
Control word set to ‘Enable’ Status set to ‘On’
The PW is requested to be verified as not already used by Ethernet over T-MPLS services. The system automatically performs the following provisioning steps: 1. PDH port configuration, consisting of below settings (without ordered sequence) consisting of below settings (without ordered sequence) • [only in case of TSS-5C] Signal mode provisioning to a value different from ‘disabled’ via SNMP • Administrative status provisioning to ‘up’ via SNMP 2. CES profile entry creation (pwCTDMCfgTable) – if not already existing - with setting of payload size, clock source and other profile parameters 3. CES termination creation consisting of below settings: • pwIndex retrieval via SNMP GET-NEXT operation • •
pwEntry entry creation via SNMP by management action, including pwType configuration to: e1Satop pwIfIndex is set equal to ifIndex of the ifEntry associated with the PW (computed from TL1 PW AID according to the well-known naming rule)
• The NE automatically creates one pwCTDMTable entry 4. CES termination configuration and activation consisting of below settings: • pwCTDMIfIndex must point to E1 ifIndex • pwCGenTDMCfgIndex must point to CES profile entry •
set of pwCTDMClassOfService and other PW parameters to the value requested by operator
.................................................................................................................................................................................................................................... 1350 OMS 25-43 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
SATOP Circuit Emulation Service implementation
....................................................................................................................................................................................................................................
• •
pwRowStatus set to ‘up’ value The NE automatically configures pwCTDMBandwidth according to payload size and underlying layer of output PW interface and performs both CAC and QoS checks between SNMP PW and TL1 PW
.................................................................................................................................................................................................................................... 1350 OMS 25-44 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Generic Circuit Emulation Service OAM and protections
....................................................................................................................................................................................................................................
Generic Circuit Emulation Service OAM and protections CES termination alarms enabling/disabling
The alarms on the PDH port are automatically: • •
enabled when setting the PDH port signal mode to framed/unframed/framedFAS/framedCRC disabled when setting the PDH port signal mode to disabled
It is not possible to suppress alarm notifications related to Ethernet ports. Correlation of PDH port alarms to supported services
PKT manages the PDH port alarms horizontal correlation to CES. In case of unterminated CES, PKT manages the Ethernet port alarm vertical correlation to CES. Correlation of CES termination alarms to service
PKT manages the horizontal correlation of CES termination’s loss of frame to CES availability status transport failure. CES fault localization
In case of faulty CE service, PKT manages the inventory of elementary alarms affecting the service. The fault localization operates in the reverse direction of the correlation process. The CES fault localization must take into account the value of the CES availability status. In case of transport failure, the root cause is a PDH port alarm or a CES termination alarm. In case of server transport failure, the root cause could be: • • •
a radio port alarm an Ethernet port alarm a T-MPLS PW alarm
LOF on CES termination is also generated as the consequence of remote fault on a radio/cable link. Since the radio link failure does not trigger the automatic AIS insertion in the PDH signal (or FDI insertion in the VLAN tunnel), then the NE that terminates the CES does not receive any signal and therefore generates the LOF alarm on CES termination. PKT must therefore be able to inform the operator that the CES failure is due to the server layer (radio/cable) fault and that it is not due to the PDH layer fault. This is achieved introducing a new fault probable cause in the availability status, i.e. the server transport failure.
.................................................................................................................................................................................................................................... 1350 OMS 25-45 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
MEF8 Circuit Emulation Service OAM and protections
....................................................................................................................................................................................................................................
MEF8 Circuit Emulation Service OAM and protections Elementary alarms on MEF8 CES termination
The following table shows the elementary alarms managed on the MEF8 CES termination. Table 25-6 SNMP table CESoETHCfgTable
MEF8 CES termination alarms
NE Probable Cause
Description
PKT object
opticsIMAlarmLossOfFrameRaise
Loss of frame
CES termination
PKT Probable Cause LOF
PKT severity (fixed ASAP) Major
PKT manages the horizontal correlation of CES termination alarms towards the impacted CES: •
LOF on CES termination -> transport failure of CES
Correlation of link over radio alarms to supported services
Correlation of link over radio alarms to supported services (vertical correlation) is ALWAYS performed. PKT has to vertically correlate the radio link failure to the impacted services (keeping into account the radio protection switch position). The vertical correlation is performed by means of vertical alarm propagation from layer to layer: • •
from radio link to VLAN tunnel from VLAN tunnel to CES
The vertical correlation is performed according to two different algorithms, depending whether the radio link is protected or unprotected. Due to the vertically correlated alarm, the CES availability status indicates that there is a server transport failure. Vertical correlation in case of unprotected radio linkThe CES is in failure if there is a radio link failure: •
Unprotected link over radio failure -> server transport failure on VLAN tunnel -> server transport failure on CES
The CES is degraded if there is a radio link degrade: •
Unprotected link over radio degrade -> server transport degrade on VLAN tunnel -> server transport degrade on CES
Vertical Correlation In Case Of Protected Radio Link
The CES is in failure only if there is a LossProt on main radio port: •
LossProt on main radio port -> server transport failure on VLAN tunnel -> server transport failure on CES
.................................................................................................................................................................................................................................... 1350 OMS 25-46 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
MEF8 Circuit Emulation Service OAM and protections
....................................................................................................................................................................................................................................
The CES is degraded only if there is NOT a LossProt on main radio port and if there is a degrade on both main and spare radio links: • •
Link over radio double degrade (or single failure + single degrade) -> server transport degrade on VLAN tunnel -> server transport degrade on CES Link over radio single failure -> no propagation to VLAN tunnel and CES
•
Link over radio single degrade -> no propagation to VLAN tunnel and CES
PKT triggers the vertical correlation from radio link transport failure to client VLAN tunnels and CES as follows: • •
Link over radio double failure -> server transport failure on VLAN tunnel -> server transport failure on CES Link over radio double degrade (or single failure + single degrade) or single failure -> server transport degrade on VLAN tunnel -> server transport degrade on CES
In the last case, the CES degrade must be interpreted as a warning for the user to perform the fault localization to check if the CES is really impacted or not, since the NE does not notify if the active link is faulty or not. LossProt alarm on protected Radio port
Since R2.1 and in case of radio link protection, MPR supports the LossProt alarm on main radio port. The LossProt alarm is not propagated to the radio link. PKT reports this alarm on the radio port and correlates it directly to the client VLAN tunnel and CES.
.................................................................................................................................................................................................................................... 1350 OMS 25-47 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
SATOP Circuit Emulation Service OAM and protections
....................................................................................................................................................................................................................................
SATOP Circuit Emulation Service OAM and protections Elementary alarms on SATOP CES termination
The following table shows the elementary alarms managed on the SATOP CES termination Table 25-7
SATOP CES termination alarms
SNMP table
NE Probable Cause
Description
pwCTDMTable (NOT SUPPORTED)
opticsIMAlarmJitterBufferOverrunRaise
Jitter buffer overrun: the number of times an over-run condition has occurred exceeded threshold.
pwCTDMTable
opticsIMAlarmJitterBufferUnderrunRaise
Jitter buffer underrun: the number of times an under-run condition has occurred exceeded threshold.
pwCTDMTable
opticsimAlarmMalformedFramesRaise
pwCTDMTable
PKT PKT object Probable Cause
PKT severity (fixed ASAP)
CES termination
JBO
Major
CES termination
JBU
Major
Malformed frames: The malformed packet counter resets every 1sec. If the threshold is not reached within the 1sec period, the alarm is not reported
CES termination
MAF
Major
opticsIMAlarmStraypacketsRaise
Stray packets: The stray packet counter resets every 1sec. If the threshold is not reached within the 1sec period, the alarm is not reported
CES termination
SPKT Major
pwCTDMTable
opticsIMAlarmExcessivepacketLossRaise
Excessive packet loss: By the end of each monitoring window, the packet loss rate is compared with threshold value. If the threshold is reached for 3 continuous window time, the alarm is reported
CES termination
ELOP Major
pwCTDMTable
opticsIMAlarmRemotepacketlossRaise
Remote packet loss: When remote packet loss happen (receive valid packets with R-bit set) for 3 continous seconds, the alarm is reported. The alarm is cleared if there is no remote packet loss for 10 seconds
CES termination
RLOP Major
pwCTDMTable
opticsIMAlarmInvalidTdmDataRaise
Invalid TDM data: L bit is set in SAToP Control Word, it indicate that TDM data carried in the payload is invalid due to an attachment circuit fault. L bit is cleared in SAToP Control Word
CES termination
INTD Major
The counter resets every 1sec. If the threshold is not reached within the 1sec period, the alarm is not reported
The counter resets every 1sec. If the threshold is not reached within the 1sec period, the alarm is not reported.
.................................................................................................................................................................................................................................... 1350 OMS 25-48 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
SATOP Circuit Emulation Service OAM and protections
....................................................................................................................................................................................................................................
PKT manages the horizontal correlation of CES termination alarms towards the impacted CES, e.g.: •
LOF on CES termination -> transport failure of CES
Circuit Emulation Service QoS management
The CE service class by default is transported by guaranteed packet traffic.
.................................................................................................................................................................................................................................... 1350 OMS 25-49 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Circuit Emulation AAR Network Operation
....................................................................................................................................................................................................................................
Circuit Emulation AAR Network Operation Audit of 9500 MPR NE
PKT compares the resource attributes in database with the NE attributes and marks the resource consistency status according to the comparison result: • •
normal not-aligned
The audit of CE resources is in charge of CE manager and it is integrated in the scope of the global AAR procedure. The audited CE resources are: • •
CE node CE port CE ports include – CE edge ports (PDH or Ethernet) – CE transport link extremities (Ethernet only)
•
Tunnel XC Tunnel XCs include: – – –
Tunnel segments Tunnel cross-connects CE service terminations
For audit purposes, all Tunnel segment and CES termination attributes are mirrored in the tunnel XC. Audit of TSS-5C NE
The audit of T-MPLS PW terminations is performed by T-MPLS manager. The audited CE resources are: • •
CE node CE ports, including: CE edge ports (PDH)
•
Tunnel XC including: CE service terminations
For audit purposes, all CES termination attributes are mirrored in the tunnel XC. Audit: ATM Xconn upload
During the audit operation, the upload involves the cross-connection with ATM2ATM or ATM2ETH service profile, that are synchronized and stored in PKT database. The retrieved ATM Xconns are visualized in the Xconn list retrievable from the containing Packet Radio node. The operator can then inspect the VLANID used by each ATM Xconn. ATM Xconns are ignored by force-align down and Takeover operations. .................................................................................................................................................................................................................................... 1350 OMS 25-50 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
Circuit Emulation AAR Network Operation
....................................................................................................................................................................................................................................
Alignment: 9500 MPR NE align down
PKT creates in the NE resources that are missing in the NE and present in the database. PKT marks the resource consistency status according to the alignment result: • •
normal failed-to-align
Alignment: 9500 MPR NE forced align down
PKT creates in the NE resources that are missing in the NE and present in the database and, in case of conflicting values related to resources present in both databases, aligns the NE value to the NMS value. PKT marks the resource consistency status according to the alignment result: • •
normal failed-to-align
Alignment: TSS-5C NE forced align down
PKT forced align down procedure apply to TSS-5C NE.
.................................................................................................................................................................................................................................... 1350 OMS 25-51 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Overview
CES Takeover description
....................................................................................................................................................................................................................................
CES Takeover description Reservation: 9500 MPR NE
PKT creates in database resources that are present in the NE and missing in NMS database. PKT marks the consistency status of the uploaded resources as “reserved”. Reservation: TSS-5C NE
Starting from CES NE, the user can retrieve all discovered XCs: the XC attributes include the SNMP PW attributes uploaded from NE. MEF8 CES Takeover
PKT is requested to upload MEF8 CES connectivity already implemented in the network and to display it to the user. The Takeover procedure works in PKT database exploiting the “reserved” resources. At the end of the procedure, those resources that have been successfully recognized as components of the recovered CES connectivity are marked as normal. The Takeover operation can be started on: •
CES port: the system discovers automatically all services crossing the port
•
CES node: the system discovers automatically all services crossing the node
The algorithm pursues on VLANID and service profile basis the discovered cross-connections in that port (or node) continuing the discovery in the adjacent node, until an edge port is reached. SATOP CES Takeover
The Takeover procedure is applied to SATOP CES, assuming that the T-MPLS PW infrastructure has been already discovered and assigned to CES Domain.
.................................................................................................................................................................................................................................... 1350 OMS 25-52 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Overview
....................................................................................................................................................................................................................................
CES Procedures Purpose
This section provides an information about the CES procedures. Contents Circuit Emulation Service graphical inventory
25-55
View the list of CES Domains (Packet Radio)
25-58
View the details of CES Domain (Packet Radio)
25-59
Inventory from CES Domain (Packet Radio)
25-60
Create CES Domain (Packet Radio)
25-61
Assign/Deassign resources to Packet Radio Domain
25-62
Assign/Deassign resources to T-MPLS Domain
25-63
View the list of CES NEs
25-64
Description of the list of CES NEs
25-65
View the details of CES NE
25-66
Details of CES NE
25-67
Inventory from CES NE
25-68
Inventory from Protection Group
25-70
View the list of CES Transport Links
25-71
Description of the list of CES Transport Links
25-72
View the details of CES Transport Link
25-73
Details of the CES Transport Link
25-74
Inventory from CES Transport Link
25-75
Inventory from CES Transport Link extremity
25-76
View the list of CES PDH Ports
25-78
Description of the list of CES PDH Ports
25-79
View the details of CES PDH Port
25-82
Details of CES PDH Port
25-83
Inventory from CES PDH Port
25-84
List CES Edge Ports
25-85
Description of the list of CES Port
25-86
View the details of CES Edge Port
25-87
Details of CES Port
25-88
Inventory from CES Edge Port
25-89
.................................................................................................................................................................................................................................... 1350 OMS 25-53 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures ....................................................................................................................................................................................................................................
View the list of CES Links Over Radio
25-90
Description of the list of CES Links Over Radio
25-91
View the details of CES Link Over Radio
25-92
Details of CES Link Over Radio
25-93
Inventory from CES Link Over Radio
25-94
Synchronization of CES Link Over Radio
25-96
View the list of CES Radio Ports
25-97
Description of the list of CES Radio Ports
25-98
View the details of CES Radio Port
25-99
Details of CES Radio Port
25-100
Inventory from CES Radio Port
25-101
View the list of CES VLAN Paths
25-102
Description of the list of CES VLAN Paths
25-103
Join CES tunnels
25-104
Stitch CES tunnels
25-105
View the list of Circuit Emulation Services
25-106
Description of the list of Circuit Emulation Services
25-107
View the list of CES Terminations
25-114
Description of the list of CES Terminations
25-115
Create Circuit Emulation Service
25-122
Inventory from CES
25-126
Configure CES
25-127
Routing display of CES
25-130
Configure CES terminations
25-131
Takeover procedure for MEF8 CES
25-132
Takeover procedure for SATOP CES
25-134
.................................................................................................................................................................................................................................... 1350 OMS 25-54 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Circuit Emulation Service graphical inventory
....................................................................................................................................................................................................................................
Circuit Emulation Service graphical inventory E2E PDH: Navigation toward SDH manager
The operator can navigate from one CES towards the associated SDH path if the following conditions are verified: • • •
the SDH path has been already manually implemented the CES termination corresponds to the local termination of one Link over PDH the SDH path termination corresponds to the remote termination of the same Link over PDH
In order to start the navigation towards SDH GUI server and open the SDH path routing display, the operator has to open the CES routing display, select the SDH network icon and right-click. The navigation command is enabled only if the above conditions are true. Show properties of Tunnel
PKT manages the display of Tunnel properties listed in: •
Table 25-8, “Generic Tunnel attributes.” (p. 25-55)
•
Table 25-9, “Packet Radio Tunnel attributes” (p. 25-56)
•
There are no specific T-MPLS Tunnel attributes.
Table 25-8 PKT attr name
Generic Tunnel attributes.
PKT attr val
Comment
Description
Userlabel
String
Automatically computed by PKT by VLAN conversion to string
Friendly name
Configuration state
{defined, allocated, implemented}
It tells whether the needed resources has been reserved or not, in database only or also in the network
Target configuration state
Availability status
{normal, server-transportfailure}
Type
{Packet-Radio, T-MPLS, Ethernet, Sdh}
Alarm status
It represents the Tunnel transport layer
Tunnel type
The following table shows the specific Packet-Radio tunnel attributes.
.................................................................................................................................................................................................................................... 1350 OMS 25-55 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Circuit Emulation Service graphical inventory
....................................................................................................................................................................................................................................
Table 25-9 PKT attr name VLAN-ID
Packet Radio Tunnel attributes PKT attr val
feb-80
Comment Operator: not modifiable after service creation.
Description Ethernet tunnel identifier
Tunnel label.
Listing of tunnels
PKT manages the list of all tunnels, filterable by domain Inventory from tunnel
PKT manages the inventory of: • •
the supported CE services the server CE transport links
The inventory is started selecting the tunnel and then right-click to open the desired target list. Show properties of tunnel segment
Tunnel segments can be retrieved from dedicated inventory (from transport link extremity or from edge port) or tunnel routing display PKT manages the display of CE termination properties listed in: •
Table 25-10, “Generic Tunnel segment attributes” (p. 25-56)
•
“MEF8 CES termination attributes” (p. 25-116)
•
There are no specific T-MPLS Tunnel segment attributes.
Table 25-10 PKT attr name
Generic Tunnel segment attributes
PKT attr val
Configuration state
{defined, allocated, implemented}
Alarm status
{normal, server-transport-failure}
Consistency status
{normal, not-aligned, failed-to-align}
Comment
Description
It tells whether the needed resources has been reserved or not, in database only or also in the network
Target configuration state Alarm status
Download disable management
MIB alignment between NMS and NE
.................................................................................................................................................................................................................................... 1350 OMS 25-56 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Circuit Emulation Service graphical inventory
....................................................................................................................................................................................................................................
Tunnel Xconn attributes Table 25-11 PKT attr name
Generic Tunnel Xconn attributes
PKT attr val
Master
SNMP table
SNMP attr name
SNMP attr val
Description
Configuration state
{defined, allocated, implemented}
PKT
Target configuration state
Consistency status
{normal, not-aligned, failed-to-align}
PKT
MIB alignment between NMS and NE
.................................................................................................................................................................................................................................... 1350 OMS 25-57 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
View the list of CES Domains (Packet Radio)
....................................................................................................................................................................................................................................
View the list of CES Domains (Packet Radio) When to use
The function lists the CES Domains. Related information
PKT manages the display of all Packet Radio domains For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The Services menu is shown. ...................................................................................................................................................................................................
2
Select Circuit Emulation > CES Domain. Result: The CES Domain list is shown.
The attributes displayed for each domain are: • User Label. • CAC tolerance. (strict, loose). Connection admission control policy. Meaningful only in case of CES over Packet Radio. • Transport type. (CesOverPacketRadio, CesOverT-MPLS). Server Transport technology. • Minimun Vlan Type • Maximum Vlan Type E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-58 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
View the details of CES Domain (Packet Radio)
....................................................................................................................................................................................................................................
View the details of CES Domain (Packet Radio) When to use
The function show the properties of a CES Domain. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > CES Domain. Result: The CES Domain list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Select Action > Circuit Emulation > Properties. Result: The CES Domain Properties window is shown.
The attributes displayed for each domain are: • User Label. • CAC tolerance. (strict, loose). Connection admission control policy. Meaningful only in case of CES over Packet Radio. • Transport type. (CesOverPacketRadio, CesOverT-MPLS). Server Transport technology. • Minimun Vlan Type • Maximum Vlan Type E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-59 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Inventory from CES Domain (Packet Radio)
....................................................................................................................................................................................................................................
Inventory from CES Domain (Packet Radio) When to use
The function lists objects related to a CES Domain . Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Inventory from Packet Radio domain
PKT manages the inventory of resources contained in one Packet Radio domain: •
CES nodes
• •
Transport links CES edge ports
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Circuit Emulation > CES Domain. Result: The CES Domain list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Select Action > CES Domain Select one of resources contained in the CES Domain: •
CES nodes
• •
Transport links CES edge ports Result: The list of resource is shown.
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-60 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Create CES Domain (Packet Radio)
....................................................................................................................................................................................................................................
Create CES Domain (Packet Radio) When to use
The function creates the CES Domain. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Action > Packet > Construction > Create Domain. Result: The Create Domain window is shown. ...................................................................................................................................................................................................
2
Insert User Label. Select Type (CE). Packet Radio Select Vlan space. (100-200, 1001, 2000-4080). Select Used Vlan space. (100-110, 1001, 2000-2005). Result: The CES Domain is created. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-61 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Assign/Deassign resources to Packet Radio Domain
....................................................................................................................................................................................................................................
Assign/Deassign resources to Packet Radio Domain When to use
The function assigns/deassign resources the CES Domain. Related information
The resources to assign/deassign: • • • •
MPR PDH Port Ethernet Port Link Over Cable Link Over Radio
For a description about the action, refer to the topic“Resource assignment to Packet Radio domain” (p. 25-12). For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
For procedure refer to “Assign resources to a Domain” (p. 13-27). E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-62 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Assign/Deassign resources to T-MPLS Domain
....................................................................................................................................................................................................................................
Assign/Deassign resources to T-MPLS Domain When to use
The function assigns/deassign resources the CES Domain. Related information
The resources to assign/deassign: • • •
TSS-5C PDH Port TSS-5C Ethernet Port Link Over T-MPLS
For a description about the action, refer to the topic“Resource assignment to T-MPLS domain” (p. 25-14). For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
For procedure refer to “Assign resources to a Domain” (p. 13-27). E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-63 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
View the list of CES NEs
....................................................................................................................................................................................................................................
View the list of CES NEs When to use
The function lists CES NE. Related information
PKT manages the list of all nodes supporting CES, filterable by domain. For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The Services menu is shown. ...................................................................................................................................................................................................
2
Select Circuit Emulation > CES NE. Result: The Circuit Emulation Services NE list is shown.
See the following topic in this document: “Description of the list of CES NEs” (p. 25-65) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-64 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of CES NEs
....................................................................................................................................................................................................................................
Description of the list of CES NEs Attributes of a CES NE
The attributes displayed for each NE are: •
User Label.
•
Network Element Type.
•
Operational State.
•
Takeover Active
•
NE CAC tolerance. (strict, loose). Connection admission control policy. Meaningful
• •
only in case of CES over Packet Radio. The CAC tolerance represents whether NE CAC checks are performed wrt minimum or maximum radio interface capacity. PKT displays this information to inform the user that the traffic implemented on this NE can be dropped in case of bandwidth degradation and in case of loose tolerance. Consistency State.(normal, not-aligned, failed-to-aligned). Alignment beetwen NMS and NE. MAC Address. L2 address.
.................................................................................................................................................................................................................................... 1350 OMS 25-65 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
View the details of CES NE
....................................................................................................................................................................................................................................
View the details of CES NE When to use
The function lists CES NE properties. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Circuit Emulation > CES NE. Result: The Circuit Emulation Services NE list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Select Action > Properties. Result: The Circuit Emulation Services NE list is shown.
See the following topic in this document: “Details of CES NE” (p. 25-67) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-66 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Details of CES NE
....................................................................................................................................................................................................................................
Details of CES NE Attributes of a CES NE
The attributes displayed for each NE are: •
User Label.
•
Network Element Type.
•
Operational State.
•
Takeover Active
•
NE CAC tolerance. (strict, loose). Connection admission control policy. Meaningful
only in case of CES over Packet Radio. Supported only by MPR NE. The CAC tolerance represents whether NE CAC checks are performed wrt minimum or maximum radio interface capacity. This information informs the user that the traffic implemented on this NE can be dropped in case of bandwidth degradation and in case of loose tolerance. Loose= CAC disabled. Value meaningful only in case of radio adaptive modulation mode • • •
Consistency State.(normal, not-aligned, failed-to-aligned). Alignment beetwen
NMS and NE. MAC Address.(00 0B 32 B6 C2 11). L2 address. Timestamp frequency. (77760kHz, 25000kHz[default], 16384kHz). Supported by
TSS NE only • •
PDH deg interval. (Range 2-10 sec; 5 sec default)
•
PDH deg clear thr. (Range 0-1000 errors; 20 default). Supported by TSS NE only
•
Physical impedance. (ohm). Not managed
PDH deg raise thr. (Range 0-1000 errors; 30 default). Supported by TSS NE only
Note that: • •
MAC address is not meaningful in case of PDH technology Signal mode is not meaningful in case of Ethernet port
.................................................................................................................................................................................................................................... 1350 OMS 25-67 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Inventory from CES NE
....................................................................................................................................................................................................................................
Inventory from CES NE When to use
The function lists objects related to CES NE. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Inventory from CES node
PKT manages the inventory of resources contained in one CES node: •
PDH ports
• • •
Ethernet ports Radio ports (radio link extremities) T-MPLS ports (T-MPLS link extremities)
• •
Protection groups Xconn
The Xconn list includes TDM2TDM, TDM2ETH, ATM2ATM and ATM2ETH connections. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Circuit Emulation > CES NE. Result: The Circuit Emulation Services NE list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Click Action > CES NE Select one of resources contained in one CES node: •
PDH ports
•
Ethernet ports
•
Radio ports (radio link extremities)
.................................................................................................................................................................................................................................... 1350 OMS 25-68 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Inventory from CES NE
....................................................................................................................................................................................................................................
• • •
T-MPLS ports (T-MPLS link extremities) Protection groups Xconn Result: The list of resources is shown, according to the selected type.
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-69 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Inventory from Protection Group
....................................................................................................................................................................................................................................
Inventory from Protection Group When to use
The function lists objects related to Protection Group. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Inventory from Protection Group
PKT manages the inventory of resources contained in one Protection Group: •
Contained Radio ports
•
Packet Radio Node container
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
List the protection groups. Refer to the procedure “Inventory from CES NE” (p. 25-68) Result: The protection group list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Click Search > Protection group Select the type of resources related to the protection group: •
Radio ports
•
Packet Radio Node Result: The list of resources is shown, according to the selected type.
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-70 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
View the list of CES Transport Links
....................................................................................................................................................................................................................................
View the list of CES Transport Links When to use
The function lists CES Transport Links. Related information
PKT manages the list of all CE transport links, filterable by domain. For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The Services menu is shown. ...................................................................................................................................................................................................
2
Select Circuit Emulation > CES Transport Links. Result: The Transport Links list is shown.
See the following topic in this document: “Description of the list of CES Transport Links” (p. 25-72) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-71 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of CES Transport Links
....................................................................................................................................................................................................................................
Description of the list of CES Transport Links Attributes of a CES Transport Link
The attributes displayed for each Transport Link are: •
User Label.
•
Domain.
•
Transport Type
• •
Transport Link Technology.
•
PseudoWire Id.
•
CIR
• •
CBS
•
PBS
•
Reserved CIR
•
Reserved CBS
•
Reserved PIR
•
Reserved PBS
VLAN Id.
PIR
.................................................................................................................................................................................................................................... 1350 OMS 25-72 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
View the details of CES Transport Link
....................................................................................................................................................................................................................................
View the details of CES Transport Link When to use
The function lists Properties of CES Transport Links. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Circuit Emulation > CES Transport Links. Result: The list is shown. ...................................................................................................................................................................................................
2
Select one item in the list Select Action > Properties. Result: The Transport Links Property List is shown.
See the following topic in this document: “Details of the CES Transport Link” (p. 25-74) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-73 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Details of the CES Transport Link
....................................................................................................................................................................................................................................
Details of the CES Transport Link Attributes of a CES Transport Link
PKT manages the display of the following CE transport link properties. Table 25-12 PKT attr name
CE transport link attributes
PKT attr val
Comment
Description
Userlabel
string
Same as Core link userlabel
Friendly name
Bandwidth
Mb/s
Same as Core link rate
Committed net bandwidth
Peak bandwidth
Mb/s
Meaningful only in case of radio underlying technology. Equal to rate otherwise
Peak net bandwidth
Available bandwidth on NE
Mb/s
In case of link over radio, it corresponds to uploaded Radio ports available bandwidth
Net available bandwidth on NE
Used CIR
Mb/s
Computed from implemented CE services
Used bandwidth for implemented CE services
Reserved CIR
Mb/s
Computed from allocated and implemented CE services
Reserved bandwidth for allocated and implemented CE services
Transport technology
{radio, cable}
It represents the underlying physical transport layer
Transport technology
Transport type
It represents the underlying {CesOverPacketRadio, transport technology CesOverTMPLS}
Transport type
The underlying technology of one CE transport link can be radio or Ethernet cable or link over T-MPLS. In case of radio link protection, there is only one CE transport link.
.................................................................................................................................................................................................................................... 1350 OMS 25-74 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Inventory from CES Transport Link
....................................................................................................................................................................................................................................
Inventory from CES Transport Link When to use
The function lists objects related to CES Transport Link. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Inventory from CES Transport Link
PKT manages the inventory of resources contained in one CES Transport Link: •
CE Transport Link extremities
The extremity underlying technology can be Ethernet physical or radio or T-MPLS port. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Circuit Emulation > CES Transport Link. Result: The CES Transport Link list is shown. ...................................................................................................................................................................................................
2
Select one edge port in the list Select Search > CES Transport Link > Select the type of resources contained in one Transport Link: •
CE Transport Link extremities Result: The resources are shown, according to the selected type.
For attributes description refer to “Description of the list of CES Port” (p. 25-86) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-75 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Inventory from CES Transport Link extremity
....................................................................................................................................................................................................................................
Inventory from CES Transport Link extremity When to use
The function lists objects related to CES Transport Link extremities. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Inventory from CES Transport Link extremities
PKT manages the inventory of resources contained in one CES Transport Link extremities: • • •
the physical port or SDH termination or T-MPLS PW termination associated to the CE transport link extremity the containing CES node the supported Tunnel segments. “Show properties of tunnel segment” (p. 25-56)
The CE transport link extremities are displayed together with the CE edge ports in a single CE port list. In case of NNI port type, only the CE transport link extremity inventories are meaningful. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
List CES Transport Link extremities. Refer to the procedure “Inventory from CES Transport Link” (p. 25-75) Result: The CES Transport Link extremity list is shown. ...................................................................................................................................................................................................
2
Select one item in the list Click Search > CES Transport Link extremity Select the type of resources related to one CES Transport Link extremity: •
SDH Terminations
•
T-MPLS PW Terminations
.................................................................................................................................................................................................................................... 1350 OMS 25-76 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Inventory from CES Transport Link extremity
....................................................................................................................................................................................................................................
•
CES nodes
•
Tunnel segments Result: The resources are shown according to the selected type.
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-77 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
View the list of CES PDH Ports
....................................................................................................................................................................................................................................
View the list of CES PDH Ports When to use
The function lists CES PDH Ports. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The Services menu is shown. ...................................................................................................................................................................................................
2
Select CES Ports. Result: The CES Port list is shown.
See the following topic in this document: “Description of the list of CES PDH Ports” (p. 25-79) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-78 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of CES PDH Ports
....................................................................................................................................................................................................................................
Description of the list of CES PDH Ports Attributes of a CES PDH Port
Depending on the used underlying infrastructure, for the attributes description, refer to Table 25-13, “9500MPR PDH port attributes” (p. 25-79) or Table 25-14, “TSS-5C PDH port attributes” (p. 25-80). Table 25-13 PKT attr name
9500MPR PDH port attributes
PKT attr val
Master
SNMP table
SNMP attr name
SNMP attr val
Description
userLabel
String
NE: uploaded by Core
see 1
ifMib::ifIndex
InterfaceIndex: INTEGER
Friendly name
technology
PDH
NE: uploaded by Core
ifTable
ifMib::ifType
ds1 (18) for MPR also in case of e1 PDH port
Characteristic technology
interfaceRate
Integer
NE: uploaded by Core & exported to CEM
ifTable
ifMib::ifSpeed
2048 Kbit/s
Net bandwidth
signal mode
{framed, unframed, disabled}
PKT. This attribute is managed by CES
E1pPITTPTable e1pPITTPSignalMode INTEGER
alarm status
TDM frame type
Computed by PKT
Alarm status Alarm severity assignment profile
ASAP profile
Pointer to fixed ASAP
Severity assigned by PKT
Network role
{UNI, E-NNI}
PKT
N.A.
N.A.
N.A.
Network role
TDM rate
{e1, ds1}
NE: uploaded by Core
ifTable
ifMib::ifType
ds1 (18) or e1(19)
TDM service rate
Consistency status
{normal, not-aligned, failed-to-align}
MIB alignment between NMS and NE
.................................................................................................................................................................................................................................... 1350 OMS 25-79 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of CES PDH Ports
....................................................................................................................................................................................................................................
Table 25-13 PKT attr name Encapsulation type
9500MPR PDH port attributes
PKT attr val
Master
(continued)
SNMP table
{cesUnstructured, NE: uploaded atmIma} by Core
SNMP attr name
SNMP attr val
Description
E1pPITTPTable e1pPITTPEncapsType
Notes:
1.
The port userLabel is computed, starting from the retrieved integer value, using the UFL library (User Friendly Label) according to the naming rule of the 9500MPR NE. Table 25-14 PKT attr name
PKT attr val
TSS-5C PDH port attributes Master
SNMP table
SNMP attr name
SNMP attr val
Description
ifMib::ifIndex
InterfaceIndex: INTEGER
Friendly name
userLabel
String
NE: uploaded by Core
technology
PDH
NE: uploaded by Core
ifTable
ifMib::ifType
e1 (19)
Characteristic technology
interfaceRate
Integer
NE: uploaded by Core & exported to CEM
ifTable
ifMib::ifSpeed
2048 Kbit/s
Net bandwidth
signal mode
{unframed, disabled (default), framedFAS, framedCRC}
PKT. This attribute is shown in the associated CES port
E1pPITTPTable e1pPITTPSignalMode INTEGER
alarm status
TDM frame type
Computed by PKT
Alarm status Alarm severity assignment profile
ASAP profile
Pointer to fixed ASAP
Severity assigned by PKT
Network role
{UNI, E-NNI}
PKT
N.A.
N.A.
N.A.
Network role
TDM rate
{e1, ds1}
NE: uploaded by Core
ifTable
ifMib::ifType
ds1 (18) or e1(19)
TDM service rate
.................................................................................................................................................................................................................................... 1350 OMS 25-80 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of CES PDH Ports
....................................................................................................................................................................................................................................
Table 25-14 PKT attr name
PKT attr val
TSS-5C PDH port attributes Master
SNMP table
(continued)
SNMP attr name
SNMP attr val
Description MIB alignment between NMS and NE
Consistency status
{normal, not-aligned, failed-toalign}
Administrative status
{up, down}
Loopback status
PKT: {disabled(default), Managed line, read-only by internal} Core (NE supports also loopback configuration).
PKT. Managed by CEM at CES implementation time
ifTable
ifAdminStatus
up(1), down(2)
E1pPITTPTable e1pPITTPLoopback disabled(0), line(1), internal(2)
Administrative status
Loopback status
.................................................................................................................................................................................................................................... 1350 OMS 25-81 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
View the details of CES PDH Port
....................................................................................................................................................................................................................................
View the details of CES PDH Port When to use
The function lists the properties of CES PDH Ports. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Circuit Emulation > CES Ports. Result: The CES Port list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Select Action > Properties. Result: The CES Port property window is shown.
See the following topic in this document: “Details of CES PDH Port” (p. 25-83) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-82 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Details of CES PDH Port
....................................................................................................................................................................................................................................
Details of CES PDH Port Attributes of a CES PDH Port
The attributes displayed for each Port are: •
User Label.
•
Interface Technology.
•
Interface Type.
•
Network Element .
•
Domain.
•
Transport Type
• •
Transport Link.
• •
Reserved Capacity.
•
Signal Mode
•
Administrative State
•
Consistency State
•
Alarm Status
•
MAC Address
•
Radio Interface Type
•
CBS
•
PIR
•
PBS
•
Reserved CBS
•
Reserved PIR
•
Reserved PBS
Maximum Capacity. Used Bandwidth
Show properties of PDH port
PKT GUI displays the PDH port properties listed in: in case of MPR NE in case of TSS-5C NE
.................................................................................................................................................................................................................................... 1350 OMS 25-83 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Inventory from CES PDH Port
....................................................................................................................................................................................................................................
Inventory from CES PDH Port When to use
The function lists objects related to CES PDH Port. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Inventory from PDH Port
Selecting one PDH port, PKT supports the inventory of the supported CES, if any. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > ... > CES PDH Port. Result: The PDH Port list is shown. ...................................................................................................................................................................................................
2
Select one item in the list Click Search > PDH Port Select the type of resources related to one Edge Port: •
Container CES Result: The resources are shown according to the selected type.
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-84 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
List CES Edge Ports
....................................................................................................................................................................................................................................
List CES Edge Ports When to use
The function lists CES Edge Port. Related information
PKT manages the list of all CES edge ports, filterable by domain. For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The Services menu is shown. ...................................................................................................................................................................................................
2
Select Circuit Emulation > CES Ports. Result: The CES Port list is shown.
See the following topic in this document: “Description of the list of CES Port” (p. 25-86) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-85 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of CES Port
....................................................................................................................................................................................................................................
Description of the list of CES Port Attributes of a CES Port
The CES port merges the attributes of CES edge port and CE transport link extremity. The CE transport link extremity properties are displayed together with the CE edge port properties. In case of NNI port type, only the CE transport link extremity properties are meaningful. Table 25-15
The CES port attributes
PKT attr name
PKT attr val
Comment
userlabel
String
Friendly name
network role
{ENNI, UNI}
Network role
technology
{PDH, radio, eth}
Underlying technology
admin status
{up, down}
Administrative status
ASAP profile
Pointer to fixed ASAP
Alarm severity assignment profile. Not yet managed
consistency status
{normal, not-aligned, failed-to-align}
MIB alignment between NMS and NE
DCN label
integer
DCN label. Meaningful only in case of ETH port
peak bandwidth
Number
Net bandwidth corresponding to the maximum capacity that can be allocated to services
.................................................................................................................................................................................................................................... 1350 OMS 25-86 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
View the details of CES Edge Port
....................................................................................................................................................................................................................................
View the details of CES Edge Port When to use
The function lists the properties of CES Edge Port. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Circuit Emulation > CES Ports. Result: The CES Port list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Select Action > Properties. Result: The CES Port property window is shown.
See the following topic in this document: “Details of CES Port” (p. 25-88) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-87 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Details of CES Port
....................................................................................................................................................................................................................................
Details of CES Port Attributes of a CES Port
The CES port merges the attributes of CES edge port and CE transport link extremity. Transport Link extremity
The extremity underlying technology can be Ethernet physical or radio or T-MPLS port. The CE transport link extremity properties are displayed together with the CE edge port properties: in case of NNI port type, only the CE transport link extremity properties are meaningful. Edge Port
The CE edge port properties are displayed together with the CE transport link extremity properties. In case of UNI port type, only the CE edge port properties are meaningful. The underlying technology can be PDH or Ethernet physical. In case of Ethernet physical underlying technology, the edge port is characterized by the additional attributes. Table 25-16
Ethernet port attributes
PKT attr name Acceptable frame type
PKT attr val {all, only-tagged}
Description Filtering based on frame tag
NOT MANAGED Port VLAN ID
0-4094
VLAN ID for untagged frames
NOT MANAGED Port priority
0-7
Priority for untagged frames
NOT MANAGED VLAN member set
VLAN range
Filtering based of frame VLAN ID
NOT MANAGED admin status
{up, down}
Administrative status
Alarm status
{critical, major, minor, warning, cleared}
Alarm status
ASAP profile
Pointer to fixed ASAP
Alarm severity assignment profile
Consistency status
{normal, not-aligned, failed-to-align}
MIB alignment between NMS and NE
.................................................................................................................................................................................................................................... 1350 OMS 25-88 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Inventory from CES Edge Port
....................................................................................................................................................................................................................................
Inventory from CES Edge Port When to use
The function lists objects related to CES Edge Port. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Inventory from CES Edge Port
PKT manages the inventory of: •
the supported CE service terminations
•
the containing CES node
From GUI perspective, the CE edge ports are displayed together with the CE transport links in a single CE port list: in case of UNI port type, only the CE edge port inventories are meaningful. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Circuit Emulation > CES Port. Result: The Edge Port list is shown. ...................................................................................................................................................................................................
2
Select one item in the list Select Search > Edge Port Select the type of resources related to Edge Port: •
CE Service terminations
•
CES Nodes Result: The resources are shown according to selected type.
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-89 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
View the list of CES Links Over Radio
....................................................................................................................................................................................................................................
View the list of CES Links Over Radio When to use
The function lists CES Link Over Radio. Related information
PKT displays the list of all links over radio, filtered by domain. For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Construction. Result: The Construction menu is shown. ...................................................................................................................................................................................................
2
Select Circuit Emulation > CES Link Over Radio. Result: The Transport Links list is shown.
See the following topic in this document: “Description of the list of CES Links Over Radio” (p. 25-91) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-90 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of CES Links Over Radio
....................................................................................................................................................................................................................................
Description of the list of CES Links Over Radio Attributes of a CES Link Over Radio Table 25-17 PKT attr name
Link over radio attributes PKT attr val
Comment
Description
Userlabel
string
Computed by NPR
Friendly name
Rate
Mb/s
Computed from radio port bandwidth
Committed net bandwidth
Peak rate
Mb/s
Computed from radio port peak bandwidth
Peak net bandwidth
Protection role
{none, working, protecting}
Computed from the radio port naming rule
Traffic bearing role in case of radio link protection
Protection type
{unprotected, 1+1}
Computed from the presence or not of the radio protection group
Protection type
Availability status
{normal, in-failure}
Alarm status
.................................................................................................................................................................................................................................... 1350 OMS 25-91 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
View the details of CES Link Over Radio
....................................................................................................................................................................................................................................
View the details of CES Link Over Radio When to use
The function shows the properties of CES Link Over Radio. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
List the Link Over Radio Refer to the procedure “View the list of CES Links Over Radio” (p. 25-90) Result: The Link Over Radio list is shown. ...................................................................................................................................................................................................
2
Select one item in the list Select Action > Properties. Result: The Link Over Radio property window is shown.
See the following topic in this document: “Details of CES Link Over Radio” (p. 25-93) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-92 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Details of CES Link Over Radio
....................................................................................................................................................................................................................................
Details of CES Link Over Radio Attributes of a CES Link Over Radio Table 25-18 PKT attr name
Link over radio attributes PKT attr val
Comment
Description
Userlabel
string
Computed by NPR
Friendly name
Rate
Mb/s
Computed from radio port bandwidth
Committed net bandwidth
Peak rate
Mb/s
Computed from radio port peak bandwidth
Peak net bandwidth
Protection role
{none, working, protecting}
Computed from the radio port naming rule
Traffic bearing role in case of radio link protection
Protection type
{unprotected, 1+1}
Computed from the presence or not of the radio protection group
Protection type
Availability status
{normal, in-failure}
Alarm status
.................................................................................................................................................................................................................................... 1350 OMS 25-93 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Inventory from CES Link Over Radio
....................................................................................................................................................................................................................................
Inventory from CES Link Over Radio When to use
The function lists objects related to CES Link Over Radio. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Inventory from CES Link Over Radio
PKT supports the inventory of: •
radio interface terminations
• •
supported CES peer radio link (in case of 1+1 link protection)
Tunnel inventory from link over radio
PKT supports the inventory of: •
supported Tunnels
selecting the desired link over radio and then right-click to open the supported VLAN tunnel list Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
List the Link Over Radio Refer to the procedure “View the list of CES Links Over Radio” (p. 25-90) Result: The Link Over Radio list is shown. ...................................................................................................................................................................................................
2
Select one item in the list Click Search > Link Over Radio Select the type of resources related to the Link Over Radio: •
Radio Interface Termination
•
Supported CES
.................................................................................................................................................................................................................................... 1350 OMS 25-94 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Inventory from CES Link Over Radio
....................................................................................................................................................................................................................................
• •
Peer Radio Link (in case of 1+1 protection) Supported Tunnel Result: The resource list is shown according to the selected type.
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-95 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Synchronization of CES Link Over Radio
....................................................................................................................................................................................................................................
Synchronization of CES Link Over Radio When to use
The function manually upload CES Link Over Radio. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
List the Link Over Radio Refer to the procedure “View the list of CES Links Over Radio” (p. 25-90) Result: The Link Over Radio list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Select Action > Synchronize. Result: The selected Link Over Radio is updated. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-96 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
View the list of CES Radio Ports
....................................................................................................................................................................................................................................
View the list of CES Radio Ports When to use
The function lists CES Radio Port. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Construction. Result: The Construction menu is shown. ...................................................................................................................................................................................................
2
Select .... CES Radio Port. Result: The CES Radio Port list is shown.
See the following topic in this document: “Description of the list of CES Radio Ports” (p. 25-98) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-97 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of CES Radio Ports
....................................................................................................................................................................................................................................
Description of the list of CES Radio Ports Attributes of a CES Radio Port Table 25-19
radio port properties
PKT attr name
PKT attr val
Description
userLabel
String
Friendly name
technology
RADIO
Characteristic technology
Modulation mode
{preset, adaptive}
Modulation operation mode
Modulation
{4QAM, 16QAM, 32QAM, 64QAM, 128QAM, 256QAM}
Modulation type
Channel spacing
{7Mhz, 14Mhz, 28MHz, 56Mhz}
Channel spacing
Capacity
130.56Mb/s
Committed gross bandwidth
Maximum capacity
130.56Mb/s
Peak gross bandwidth
Bandwidth
129158Kbit/s
Committed net bandwidth
Peak bandwidth
Kbit/s
Peak net bandwidth
Tx Frequency
10.8GHz
Transmit frequency
Rx Frequency
11.33GHz
Receive frequency
Shifter
530.0MHz
Delta between transmit and receive frequencies
Alarm status
Alarm status
ASAP profile
Alarm severity assignment profile
Available bandwidth on NE
Mb/s
Net available bandwidth
Consistency status
{normal, failed, notAligned}
Alignment between NE and NMS MIB
Radio interface type
{ODU300, MPT}
.................................................................................................................................................................................................................................... 1350 OMS 25-98 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
View the details of CES Radio Port
....................................................................................................................................................................................................................................
View the details of CES Radio Port When to use
The function shows properties of CES Radio Port. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
List the CES Radio Port Refer to the procedure “View the list of CES Radio Ports” (p. 25-97) Result: The CES Radio Port list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Result: The CES Radio Port property window is shown.
See the following topic in this document: “Details of CES Radio Port” (p. 25-100) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-99 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Details of CES Radio Port
....................................................................................................................................................................................................................................
Details of CES Radio Port Attributes of a CES Radio Port Table 25-20
radio port properties
PKT attr name
PKT attr val
Description
userLabel
String
Friendly name
technology
RADIO
Characteristic technology
Modulation mode
{preset, adaptive}
Modulation operation mode
Modulation
{4QAM, 16QAM, 32QAM, 64QAM, 128QAM, 256QAM}
Modulation type
Channel spacing
{7Mhz, 14Mhz, 28MHz, 56Mhz}
Channel spacing
Capacity
130.56Mb/s
Committed gross bandwidth
Maximum capacity
130.56Mb/s
Peak gross bandwidth
Bandwidth
129158Kbit/s
Committed net bandwidth
Peak bandwidth
Kbit/s
Peak net bandwidth
Tx Frequency
10.8GHz
Transmit frequency
Rx Frequency
11.33GHz
Receive frequency
Shifter
530.0MHz
Delta between transmit and receive frequencies
Alarm status
Alarm status
ASAP profile
Alarm severity assignment profile
Available bandwidth on NE
Mb/s
Net available bandwidth
Consistency status
{normal, failed, notAligned}
Alignment between NE and NMS MIB
Radio interface type
{ODU300, MPT}
.................................................................................................................................................................................................................................... 1350 OMS 25-100 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Inventory from CES Radio Port
....................................................................................................................................................................................................................................
Inventory from CES Radio Port When to use
The function lists objects related to CES Radio Port. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Inventory from CES Radio Port
PKT manages the inventory of resources related to a Radio Port: •
Radio Link
•
Protection group (1+1 protection)
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
List the CES Radio Port Refer to the procedure “View the list of CES Radio Ports” (p. 25-97) Result: The CES Radio Port list is shown. ...................................................................................................................................................................................................
2
Select one item in the list Click Search > Radio Port Select the type of resources related to the Radio Port: •
Radio Link
•
Protection group (1+1 protection) Result: The resource list is shown according to the selected type.
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-101 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
View the list of CES VLAN Paths
....................................................................................................................................................................................................................................
View the list of CES VLAN Paths When to use
The function lists CES VLAN Path. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The Services menu is shown. ...................................................................................................................................................................................................
2
Select Circuit Emulation > CES VLAN Path. Result: The CES VLAN Path list is shown.
See the following topic in this document: “Description of the list of CES VLAN Paths” (p. 25-103) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-102 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of CES VLAN Paths
....................................................................................................................................................................................................................................
Description of the list of CES VLAN Paths Attributes of a CES VLAN Path
The attributes displayed for each VLAN Path are: •
User Label.
•
Tunnel Type
• •
Working State.
•
Service State.
•
Availability Status
Configuration State.
.................................................................................................................................................................................................................................... 1350 OMS 25-103 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Join CES tunnels
....................................................................................................................................................................................................................................
Join CES tunnels When to use
The function adds a tunnel to a Circuit Emulation Service. Related information
Refer to the description “Manual join a tunnel to a CES” (p. 25-27) For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Circuit Emulation > Circuit Emulation Services. Result: The Circuit Emulation Services list is shown ...................................................................................................................................................................................................
2
Select one item in the list. Select Action > Circuit Emulation Services > Join. Select Tunnel to join. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-104 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Stitch CES tunnels
....................................................................................................................................................................................................................................
Stitch CES tunnels When to use
The function lists Circuit Emulation Services. Related information
Refer to the description “Manual join a tunnel to a CES” (p. 25-27) For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The Circuit Emulation Services list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Select Action > Circuit Emulation Services > Stitch. Select Tunnel to stitch. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-105 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
View the list of Circuit Emulation Services
....................................................................................................................................................................................................................................
View the list of Circuit Emulation Services When to use
The function lists Circuit Emulation Services. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). The service CIR is automatically computed by PKT: • •
based on interface type, service profile and clock source in case of MEF-8 based on payload size in case of SATOP, CBS is not managed in case of MEF-8.
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services. Result: The Services menu is shown. ...................................................................................................................................................................................................
2
Select Circuit Emulation > Circuit Emulation Services. Result: The Circuit Emulation Services list is shown.
See the following topic in this document: “Description of the list of Circuit Emulation Services” (p. 25-107) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-106 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of Circuit Emulation Services
....................................................................................................................................................................................................................................
Description of the list of Circuit Emulation Services Attributes of a CES Services
The CES PW list is the same as the CES list. The attributes displayed for each Services are: •
User Label.
•
Service Group
• •
Domain.
•
NAD Value.
•
Service State.
• •
Working State
•
Service Profile
•
Availability State
•
Ecid A-Z
•
Ecid Z-A
•
MAC Address AZ
•
Service Group Id
•
Encapsulation Type
•
Transport Type
•
CIR
•
CBS
•
PIR
•
PBS
• •
Class Of Service
•
Packet Replace policy
•
Packet Filter Pattern
•
Payload Suppression
•
Average Packet Loss Time Window
• •
Excessive Packet Loss Threshold
•
Alarm Clearing Threshold
•
Stray Packet Detection
•
Stray Packet Threshold
•
Malformed Packet Threshold
•
Buffer Overrun Threshold
Signal Type.
Configuration State
Jitter buffer deppth
Alarm Raising Threshold
.................................................................................................................................................................................................................................... 1350 OMS 25-107 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of Circuit Emulation Services
....................................................................................................................................................................................................................................
•
Buffer Underrun Threshold
• •
Remote Packet Loss Threshold
•
Egress RTP synchro source
•
Expected Ingress RTP Payload Type
•
Engress RTP Payload Type
Packet Loss Threshold
Attributes are described in the following: •
“Generic CES attributes” (p. 25-108)
•
“MEF8 attributes” (p. 25-109)
•
“SATOP CES attributes” (p. 25-110)
Generic CES attributes Table 25-21 PKT attr name
Generic CES attributes
PKT attr val
Master
Description
Service group
string
Operator: always modifiable
Friendly name for service group
Userlabel
string
Operator: always modifiable
Friendly name
Comment1, Comment2, Comment3
string
Operator: always modifiable
User comment
Text1, Text2, Text3
string
Operator: always modifiable
User text
Availability status
{normal, degraded, transport-failure, server-transport-failure, server-transport-degrade}
Computed automatically by PKT. It tells whether the service has been affected by failure of any used resource
Alarm status
Service rate
e1 (2048 Kb/s)
Operator: no more modifiable after service definition
Service rate
CoS
{G, G2, R1, R, R3, R4, BE, BK}
Operator: modifiable at any time.
Class Of Service
CoS=G is fixed in case of CesOverPacketRadio Transport type
{CesOverPacketRadio, CesOverT-MPLS}
Automatically computed by PKT based on domain type
Transport type
Encapsulation type
{MEF8, SATOP}
Automatically computed by PKT based on domain type
Encapsulation type
.................................................................................................................................................................................................................................... 1350 OMS 25-108 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of Circuit Emulation Services
....................................................................................................................................................................................................................................
Table 25-21
Generic CES attributes
(continued)
PKT attr name
PKT attr val
Master
Description
Configuration state
{defined, allocated, implemented}
Automatically computed by PKT. It tells whether the needed resources has been reserved or not, in database only or also in the network
Target configuration state
PM enabling
{false, true}
Operator: modifiable at any time. It indicates if PM should be automatically enabled at service implementation time on PDH terminations. The only supported value is false.
Performance monitoring enabling
PM granularity
{15min, 24h}
Operator: modifiable at any time. It indicates the granularity of the PM counters. Both directions are monitored. Meaningful only if PM enabling is true.
PM counter granularity
CIR
Kb/s
It is automatically computed by PKT
Service committed rate
CBS
Bytes
It is automatically computed by PKT. It is not managed in case of MEF-8
Service burst size
MEF8 attributes
The following table shows the specific MEF8 CES attributes. Table 25-22
MEF8 CES attributes
PKT attr name
PKT attr val
Comment
Signal mode
{framed, unframed}
Service profile
{TDM2TDM, Operator: no more modifiable after service definition. TDM2ETH} The service compression type
Frame encapsulation type
Payload size
121, 256
Size of TDM payload in bytes
Operator: always modifiable to framed/unframed. This attribute is mirrored to the PDH ports
Operator: modifiable only when CES is in defined state. Configurable by operator only in case of MEF8 TDM2ETH service profile. It is fixed and equal to 121 bytes in case of TDM2TDM or equal to 256 bytes in case of TDM2ETH. In case of TDM2ETH it could be configured but the configuration is not yet supported.
Description TDM frame type
.................................................................................................................................................................................................................................... 1350 OMS 25-109 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of Circuit Emulation Services
....................................................................................................................................................................................................................................
Table 25-22 PKT attr name
MEF8 CES attributes
PKT attr val
TDM clock source
{adaptive, differential}
(continued) Comment
Description
Configurable only when the service is in defined or allocated state.
TDM clock source
Configurable only in case of TDM2ETH service profile. In case of TDM2TDM profile, it is fixed to differential. In the same card, it is not possible to use both differential and adaptive clock source. ECID A->Z
feb-80
Operator: modifiable only when the CES is defined. In case of MPR, it is to be configurable only in case of TDM2ETH service profile (in case of TDM2TDM it is equal to VLAN). In case of TSS5 it has to be configured in both cases
ECID Z->A
feb-80
Operator: modifiable only when the CES is defined. In case of MPR, it is to be configurable only in case of TDM2ETH service profile (in case of TDM2TDM it is equal to VLAN). In case of TSS5 it has to be configured in both cases
Destination MAC address
00 22 fa bd a3 b6
Operator: modifiable only when the CES is defined.
VLAN-ID
feb-80
Operator: not modifiable after service creation.
Configurable only in case of TDM2ETH service profile. It is the MAC address of the Ethernet remote peer
Emulated circuit (PW) identifier in the A->Z direction
Emulated circuit (PW) identifier in the Z->A direction
MAC address of CE remote peer
Ethernet tunnel identifier
Tunnel label.
Note that: • •
MAC address is not meaningful in case of PDH technology Signal mode is not meaningful in case of Ethernet port
SATOP CES attributes
The following table shows the list of SATOP CES attributes. Table 25-23 PKT attr name Signal mode
SATOP CES attributes
PKT attr val {unframed, framedFAS, framedCRC}
Master Operator. This attribute is mirrored to the PDH ports. The NE supports also the value disabled when there is no supported service.
When modifiable not modifiable
Description TDM frame type
.................................................................................................................................................................................................................................... 1350 OMS 25-110 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of Circuit Emulation Services
....................................................................................................................................................................................................................................
Table 25-23 PKT attr name Payload size
SATOP CES attributes
PKT attr val Bytes: 128, 256(default)
(continued)
Master Operator. SATOP standard allows the following payload sizes, depending on service rate:
When modifiable
Description
modifiable only when CES is in defined state
Size of TDM payload in bytes
modifiable also at run-time when the service is implemented
TDM clock source
e1: 32, 64, 128, 256(default), 384, 512, 640 480
ds1: 96, 192(default), 288, 384,
TDM clock source
{adaptive, differential, tdmLine, system(default)}
Operator.
RTP header used
TRUE
NE
Not configurable
Usage of RTP header
Jitter buffer depth
Microseconds: range from 1000 us (default) to 16000 us in step of 125 us
Operator
configurable only when the service is in defined or allocated state
Size buffer (in microseconds)used to accommodate to the PSNspecific packet delay variation
Packet replace policy
{allOnes(default), Operator implementationSpecific}
modifiable also at run-time when the service is implemented
Packet replace policy
Packet filler pattern (NOT SUPPORTED)
(0..255):
modifiable also at run-time when the service is implemented
Packet filler pattern
255 (default)
RTP header is always inserted all cases. In case "adaptive", although the receiving Node does not care the RTP header in received CES PW, but the transmitting Node will always send RTP header.
Operator. It is modifiable only when: packet replace policy = filler.
.................................................................................................................................................................................................................................... 1350 OMS 25-111 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of Circuit Emulation Services
....................................................................................................................................................................................................................................
Table 25-23 PKT attr name
SATOP CES attributes
PKT attr val
(continued)
Master
When modifiable
Description
Payload suppression
{enable, disable(default)}
Operator
modifiable also at run-time when the service is implemented
Payload suppression
Average packet loss time window
Milliseconds: integer 1000(default)
Operator
modifiable also at run-time when the service is implemented
Average packet loss time window
Excessive packet loss threshold
[0..100]: 10 (default)
Operator
modifiable also at run-time when the service is implemented
Excessive packet loss threshold
Alarm raising threshold
Milliseconds: unsigned32
NE
modifiable also at run-time when the service is implemented
Time of defect detection for alarm reporting
NE
modifiable also at run-time when the service is implemented
Time of defect undetection for alarm clearing
3000(default) Alarm clearing threshold
Milliseconds: unsigned32 10000(default)
Stray packets detection
{false(default), true}
Operator
modifiable also at run-time when the service is implemented
Stray packets detection
Stray packets threshold
[1..300]:
Operator.
modifiable also at run-time when the service is implemented
Stray packets threshold
Operator.
modifiable also at run-time when the service is implemented
Malformed packets threshold
Operator.
modifiable also at run-time when the service is implemented
Buffer overrun threshold
300 (default) Malformed packets threshold
[1..300]:
Buffer overrun threshold
[1..300]:
300 (default)
300 (default)
.................................................................................................................................................................................................................................... 1350 OMS 25-112 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of Circuit Emulation Services
....................................................................................................................................................................................................................................
Table 25-23 PKT attr name
SATOP CES attributes
PKT attr val
Buffer underrun threshold
[1..300]:
Remote packet loss threshold
[1..300]:
Master
Description
modifiable also at run-time when the service is implemented
Buffer underrun threshold
Operator.
modifiable also at run-time when the service is implemented
Remote packet loss threshold
Operator.
modifiable also at run-time when the service is implemented
Packet loss threshold
300 (default) [1..300]:
When modifiable
Operator.
300 (default)
Packet loss threshold
(continued)
1 (default) Timestamp frequency (NOT SUPPORTED)
{0[default], 77760kHz, 25000kHz, 16384kHz}
Operator.
configurable only when the service is in defined or allocated state
Timestamp frequency per session
Expected ingress RTP payload type
[0..127]:
Operator.
modifiable also at run-time when the service is implemented
Expected RTP payload type of incoming packets
Operator.
modifiable also at run-time when the service is implemented
RTP payload type of outgoing packets
101(default)
Egress RTP payload type
[0..127]:
101(default)
There are no specific T-MPLS Tunnel attributes. All T-MPLS transport attributes are managed via TL1 and reported in the properties of the T-MPLS PW corresponding to the Link over T-MPLS. There are no specific T-MPLS Tunnel segment attributes. All T-MPLS transport segment attributes are managed via TL1 and reported in the properties of the T-MPLS PW termination corresponding to the Link over T-MPLS termination.
.................................................................................................................................................................................................................................... 1350 OMS 25-113 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
View the list of CES Terminations
....................................................................................................................................................................................................................................
View the list of CES Terminations When to use
The function lists Circuit Emulation Services Terminations. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4).CES PW terminations are the same as CES terminations. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Circuit Emulation > Circuit Emulation Services. Result: The CES list is shown. ...................................................................................................................................................................................................
2
Select one item in the list Select Search > Circuit Emulation > CES Terminations. Result: The CES Termination list is shown.
See the following topic in this document: “Description of the list of CES Terminations” (p. 25-115) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-114 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of CES Terminations
....................................................................................................................................................................................................................................
Description of the list of CES Terminations Attributes of a CES termination
CE service terminations can be retrieved via dedicated inventory (from CES or from edge port) or via CES routing display. Attributes are described in the following: •
“Generic CES termination attributes” (p. 25-115)
•
“MEF8 CES termination attributes” (p. 25-115)
•
“SATOP CES termination attributes” (p. 25-116)
The following table shows the specific MEF8 service termination attributes. Generic CES termination attributes
The following table shows the Generic attributes. Table 25-24 PKT attr name
Generic CES termination attributes PKT attr val
Comment
Description
Userlabel
String
It is the port userlabel
Port ifIndex
TDM rate
e1 (2Mb/s)
It corresponds to service rate and PDH port TDM rate
TDM rate
Transport type
{CesOverPacketRadio, Automatically computed by PKT CesOverT-MPLS} based on domain type
Transport type
Encapsulation type
{MEF8, SATOP}
Automatically computed by PKT based on domain type
Encapsulation type
PM enabling
{false, true}
Meaningful only in case of PDH termination. The only supported value is false.
Performance monitoring enabling
PM granularity
{15min, 24h}
Always both directions are monitored. Meaningful only if PM enabling is true.
PM counter granularity
Consistency status
{normal, not-aligned, failed-to-align}
Download disable management
MIB alignment between NMS and NE
MEF8 CES termination attributes
The following table shows the specific MEF8 service termination attributes.
.................................................................................................................................................................................................................................... 1350 OMS 25-115 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of CES Terminations
....................................................................................................................................................................................................................................
Table 25-25 PKT attr name
MEF8 CES termination attributes
PKT attr val
Comment
Description
Service profile
{TDM2TDM, The service compression type TDM2ETH}
Frame encapsulation type
ECID Tx
feb-80
PW egress label. It is equal to ECID Z->A on node A (and to ECID A->Z on node Z)
Emulated circuit (PW) identifier in the egress direction
ECID Rx
feb-80
PW ingress label. It is equal to ECID A->Z on node A (and to ECID Z->A on node Z). It must be checked that no two ports receive the same ingress label
Emulated circuit (PW) identifier in the ingress direction
Destination MAC address
00 22 fa bd a3 b6
In case of MPR NE it has to be provisioned only on ETH termination
MAC address of CE remote peer
TDM clock source
{adaptive, differential}
Meaningful only in case of PDH termination
TDM clock source
Payload size
121, 256
It is fixed and equal to 121 bytes in case of TDM2TDM or equal to 256 bytes in case of TDM2ETH. In case of TDM2ETH it could be configured but the configuration is not yet supported.
Size of TDM payload
RTP header used
{false, true}
Meaningful only in case of PDH termination:
Usage of RTP header
-
false in case of adaptive clock source
-
true in case of differential clock source
Note that: • •
MAC address is not meaningful in case of PDH technology Signal mode is not meaningful in case of Ethernet port
The following table shows the specific Packet-Radio tunnel segment attributes. PKT attr name VLAN
PKT attr val feb-80
Comment VLAN tunnel identifier
Description VLAN tunnel identifier
SATOP CES termination attributes
The following table shows the specific SATOP CES termination attributes.
.................................................................................................................................................................................................................................... 1350 OMS 25-116 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of CES Terminations
....................................................................................................................................................................................................................................
Table 25-26 PKT attr name
PKT attr val
SATOP CES termination attributes Comment
SNMP MIB
Description
Payload size
128, 256(default)
The value of this object indicates the Payload Size (in bytes) to be defined during the SNMP PW setUp.
pwCTDMCfgPayloadSize
Size of TDM payload in bytes
TDM clock source
{adaptive, differential, tdmLine, system(default)}
The clock used to play out the data at the PSN-bound IWF.
pwCTDMCfgClockSource
TDM clock source
RTP header used
TRUE
If set to false, an RTP header is not pre-pended to the TDM packet. Meaningful only in case of PDH termination: in case of SATOP it is always true.
pwCTDMCfgRtpHdrUsed
Usage of RTP header
Jitter buffer depth
[1000-16000]
The value shall be in units of microsecond. The value ranges from 1000 us (microseconds) = 1ms to 16000 us = 16ms in step of 125 us.
pwCTDMCfgJtrBfrDepth
Size buffer used to accommodate to the PSNspecific packet delay variation
(1000 us default)
Packet replace policy
{allOnes(default), This parameter determines the value to be played when CE bound packets implementaover/underflow the jitter buffer, or are tionSpecific} missing for any reason. This byte pattern is sent (played) on the TDM line. Selecting implementationSpecific implies an agent-specific algorithm. Selecting filler requires the setting of pwTDMCfgPktFiller. The default value is allones, i.e. play AIS.
pwCTDMCfgPktReplacePolicy
Packet replace policy
Packet filler pattern (NOT SUPPORTED)
[0..255]
Filler byte pattern played out on the TDM interface. The default value is 255,i.e. play all ones, equal to AIS indications.
pwCTDMCfgPktFiller
Packet filler pattern
Payload suppression
{enable, disable(default)}
Selecting enable means that payload suppression is allowed. Payload may be omitted in order to conserve bandwidth. Selecting disable means no suppression under any condition. Object MAY be changed at any time
pwCTDMCfgPayloadSuppression
Payload suppression
255 (default)
.................................................................................................................................................................................................................................... 1350 OMS 25-117 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of CES Terminations
....................................................................................................................................................................................................................................
Table 25-26 PKT attr name
PKT attr val
SATOP CES termination attributes
(continued)
Comment
SNMP MIB
Description
Average packet loss time window
Integer: 1000(default)
The length of time over which the average packet loss rate should be computed to detect excessive packet loss rate. The value shall be in units of millisecond. The default value is 1000 millisecond (1 s)
pwCTDMCfgAvePktLossTimeWindow
Average packet loss time window
Excessive packet loss threshold
[0..100]:
Excessive packet loss is detected by computing the average number of lost packetloss over a pwTDMCfgAvePktLossTimeWindow amount of time and comparing it with this threshold value. The rate is expressed in number of packets.
pwCTDMCfgExcessivePktLossThreshold
Excessive packet loss threshold
Alarms are only reported when the defect state persists for the length of time specified by this object. Object MAY be changed only when the related PW is defined as not active. The value shall be in units of milisec.
pwCTDMCfgAlarmThreshold
Time of defect detection for alarm reporting
Alarm MUST be cleared after the corresponding defect is undetected for the amount of time specified by this object. Object MAY be changed only when the related PW is defined as not active. The value shall be in units of milisec.
pwCTDMCfgClearAlarmThreshold
Time of defect undetection for alarm clearing
10 (default)
Alarm raising threshold
Milliseconds: unsigned32 3000(default)
Alarm clearing threshold
Milliseconds: unsigned32
10000(default)
Stray packets detection
{true, false(default)}
Enable or Disable the Stray packet detection mechanism for the Pseudowire.
pwCTDMCfgStrayPacketDetect
Stray packets detection
Stray packets threshold
[1..300]:
The number of stray packets in the Pseudowire within 1 second must be met in order to declare an alarm, if pwCTDMCfgStrayPacketDetect was set to True. Stray packet: If the SSRC field of incoming Pseudowire packets do not match the configured value of inssrc, the packet is discarded and stray packet count is incremented.
pwCTDMCfgStraypacketsThreshold
Stray packets threshold
300 (default)
.................................................................................................................................................................................................................................... 1350 OMS 25-118 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of CES Terminations
....................................................................................................................................................................................................................................
Table 25-26 PKT attr name Malformed packets threshold
PKT attr val [1..300]
300 (default)
SATOP CES termination attributes
(continued)
Comment
SNMP MIB
Description
The number of Malformed packets in the Pseudowire within 1 second must be met in order to declare an alarm. Malformed packets: are detected by mismatch between the expected packet size (taking the value of the L bit into account) and the actual packet size inferred from the PSN and PW demultiplexing layers. When RTP is used, lack of correspondence between the PT value and that allocated for this direction of the PW is used for this purpose as well.
pwCTDMCfgMalformedPacketsThreshold
Malformed packets threshold
The number of times a newly-arriving packet dropped due to Buffer overrun in the Pseudowire within 1 second must be met in order to declare an alarm.
pwCTDMCfgBufferOverrunThreshold
Buffer overrun threshold
The number of times a packet needed to be played out and the jitter buffer was empty in the Pseudowire within 1 second must be met in order to declare an alarm.
pwCTDMCfgBufferUnderrunThreshold
Buffer underrun threshold
The number of received packets with their R bit set in the Pseudowire within 1 second must be met in order to declare an alarm.
pwCTDMCfgRemotePacketLossThreshold
Remote packet loss threshold
Buffer overrun threshold
[1..300]:
Buffer underrun threshold
[1..300]:
Remote packet loss threshold
[1..300]:
Packet loss threshold
[1..300]: 1(default)
The number of lost packets in the Pseudowire within 1 second must be met in order to declare an alarm. This threshold is used to report opticsIMAlarmLossOfCESoETHFrameRaise (aka LOPS) on opticsIME1PathITTPTable
Packet loss pwCTDMthreshold CfgCESoETHFrameLossThreshold
Timestamp frequency (NOT SUPPORTED)
{0[default], 77760kHz, 25000kHz, 16384kHz}
This value is differential timestamp frequency of the system (in units of KHz). The default (0) means that global setting is inherited from opticsIMCESoEthDifferentialTimestampFrequency
pwCTDMDifferentialTimestampFrequency
300 (default)
300 (default)
300 (default)
Timestamp frequency per session
.................................................................................................................................................................................................................................... 1350 OMS 25-119 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of CES Terminations
....................................................................................................................................................................................................................................
Table 25-26 PKT attr name Expected ingress RTP synchro source
Actual ingress RTP synchro source
PKT attr val
SATOP CES termination attributes
(continued)
Comment
SNMP MIB
Description
integer:
The expected value of Synchronization Source (SSRC) field of the RTP header of the incoming pseudowire packets.
pwCTDMRTPHdrSsrcIn
2* PW ingress label (default)
Supported by NE as read-only: therefore reported only on CES termination.
Expected RTP synchronization source label of incoming packets
integer
The actual value of Synchronization Source (SSRC) field of the RTP header of the incoming pseudowire packets.
pwCTDMRTPHdrSsrcInActual
Expected RTP synchronization source label of incoming packets
pwCTDMRTPHdrSsrcOut
RTP synchronization source label of outgoing packets
Supported by NE as read-only: therefore reported only on CES termination. integer:
The value of Synchronization Source (SSRC) field of the RTP header of the outgoing pseudowire packets.
2* PW egress label (default)
Supported by NE as read-only: therefore reported only on CES termination.
Expected ingress RTP payload type
[0..127]: 101(default)
The expected value of the Payload Type field of the RTP header on the incoming Pseudowire packets.
pwCTDMRTPPayloadTypeIn
Expected RTP payload type of incoming packets
Actual ingress RTP payload type
[0..127]
The actual value of the Payload Type field of the RTP header on the incoming Pseudowire packets.
pwCTDMRTPPayloadTypeInActual
Actual RTP payload type of incoming packets
Egress RTP synchro source
Supported by NE as read-only: therefore reported only on CES termination. Egress RTP payload type
[0..127]: 101(default)
The value of the Payload Type field of the RTP header on the outgoing Pseudowire packets.
pwCTDMRTPPayloadTypeOut
RTP payload type of outgoing packets
NE CIR
INTEGER
This value indicates the total amount of bandwidth necessary to carry the TDM Service required.
pwCTDMBandwidth
Committed information rate computed by NE
It is a read-only value of the CES termination
.................................................................................................................................................................................................................................... 1350 OMS 25-120 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Description of the list of CES Terminations
....................................................................................................................................................................................................................................
Table 25-26 PKT attr name CoS
SATOP CES termination attributes
(continued)
PKT attr val
Comment
SNMP MIB
{G(default), G2, R1, R, R3, R4, BE, BK}
This value indicates the Class of Service the TDM service is expected to be carried in the PW
pwCTDMClassOfService
Description Class of Service
.................................................................................................................................................................................................................................... 1350 OMS 25-121 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Create Circuit Emulation Service
....................................................................................................................................................................................................................................
Create Circuit Emulation Service When to use
The function creates a Circuit Emulation Service. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Dedicated wizard for CES creation
In case of SATOP CES, the operator can select if the CES will be created in bottom-up or top-down mode, by toggling the top-down flag: • •
in bottom-up mode, the operator must select the single link transporting the service in top-down mode, no transport link can be selected and the system automatically picks up one unused link or it creates a new one on the fly
In case of MEF8 CES, the system automatically applies a routing algorithm to identify the transport links crossed by the service. Wizard for SATOP CES creation
Some CES attributes are present both for MEF8 and SATOP services, but with different range of values, as described in Table 25-22, “MEF8 CES attributes” (p. 25-109) section and Table 25-23, “SATOP CES attributes” (p. 25-110). Depending on domain type selection, the system automatically computes the corresponding encapsulation type (MEF8, SATOP) and the wizard should present the appropriate range of values for that encapsulation type. Therefore, the operator can configure the following tabs: •
in case of MEF8: Generic, Info, MEF8 and QoS
•
in case of SATOP: Generic, Info, RTP, QoS and OAM
The RTP, QoS and OAM tabs are disabled in case of MEF8, since the corresponding attributes are not supported by MPR. The management of SATOP requires also to introduce new CES attributes. CES automatic allocation and routing
The CE service can be optionally allocated in cascade right after creation time. The CES allocation triggers the automatic Tunnel allocation. PKT supports the automatic routing of CE services. It automatically identifies the needed radio/cable/T-MPLS links for transporting the service and reserves the needed bandwidth on these links. The automatic routing is applied to the Tunnel layer.
.................................................................................................................................................................................................................................... 1350 OMS 25-122 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Create Circuit Emulation Service
....................................................................................................................................................................................................................................
For a description about Manual deallocation and deletion of CES, refer to the topic “Manual deallocation and deletion of CES ” (p. 25-32). Unterminated.PKT supports the creation and allocation of CE services with one Ethernet termination. The CES service profile must be TDM2ETH. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Action > Packet > Services > Circuit Emulation > Create CES. Result: The Create Circuit Emulation Service window is shown.
The step Create CES is highlighted. ...................................................................................................................................................................................................
2
In the step Create CES, click Generic tab. In the Generic tab, insert the following information: •
Insert User Label
• •
Select CES Domain from list Select Transport Type from list
•
Select Encapsulation Type from list
•
Select Service Profile from list (for MEF8 only)
•
Select Clock Source from list
•
Select Service Rate from list
•
Select Payload size from list
•
Select Signal Type from list
•
Insert External Mark
• •
Select NAD from list Select Service Group from list
...................................................................................................................................................................................................
3
In the step Create CES, click Info tab. In the Info tab, insert the following optional information: •
Comment 1
•
Comment 2
.................................................................................................................................................................................................................................... 1350 OMS 25-123 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Create Circuit Emulation Service
....................................................................................................................................................................................................................................
•
Comment 3
• •
Text 1
•
Text 3
Text 2
...................................................................................................................................................................................................
4
In the step Create CES, click MEF8 tab. In the MEF8 tab, insert the following information: •
Insert R_APS VLAN Id (for MEF8 only)
•
Insert Ecid A-Z (for MEF8 only)
•
Insert Ecid Z-A (for MEF8 only)
•
Insert Destination MAC Address. Meaningful only if TDM2ETH CES. (in hex characters). (for MEF8 only)
...................................................................................................................................................................................................
5
In the step Create CES, click QOS tab. In the QOS tab, insert the following information: •
Select Class Of Service from list
•
Insert Jitter buffer depth (for SATOP only)
•
Select Payload Suppression (Enable, Disable) (for SATOP only)
...................................................................................................................................................................................................
6
In the step Create CES, click OAM tab. In the OAM tab, insert the following information: •
Select Packet Replace Policy from list (for SATOP only)
•
Insert Packet Filter Pattern (for SATOP only)
•
Insert Average Packet Loss Time Window (for SATOP only)
• •
Insert Excessive Packet Loss Threshold (for SATOP only) Insert Alarm Raising Threshold (for SATOP only)
•
Insert Alarm Clearing Threshold (for SATOP only)
•
Insert Stray Packet Detection. (True, False). (for SATOP only)
•
Insert Stray Packet Threshold (for SATOP only)
•
Insert Malformed Packet Threshold (for SATOP only)
•
Insert Buffer Overrun Threshold (for SATOP only)
•
Insert Buffer Underrun Threshold (for SATOP only)
•
Insert Remote Packet Loss Threshold (for SATOP only)
•
Insert Packet Loss Threshold (for SATOP only)
•
PM enabling
•
PM granularity
.................................................................................................................................................................................................................................... 1350 OMS 25-124 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Create Circuit Emulation Service
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
7
In the step Create CES, click RTP tab. In the RTP tab, insert the following information: • • •
Insert RTP header used (for SATOP only. When RTP header is NOT used, all remaining following attributes in tab are greyed) Select Expected Ingress RTP Payload Type from list (for SATOP only) Select Egress RTP Payload Type from list (for SATOP only)
...................................................................................................................................................................................................
8
Click Next. Result: The step CES Terminations is highlighted. ...................................................................................................................................................................................................
9
In the step CES Terminations, select termination A and termination Z. ...................................................................................................................................................................................................
10
Click Next. Result: The step Available actions is highlighted. ...................................................................................................................................................................................................
11
In the step Available actions, select one or more available actions. ...................................................................................................................................................................................................
12
Click OK. Result: The step Circuit Emulation Service is created. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-125 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Inventory from CES
....................................................................................................................................................................................................................................
Inventory from CES When to use
The function lists objects related to Circuit Emulation Services. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Inventory from CES
PKT manages the inventory of: •
CE service terminations
•
Server Tunnels. “Show properties of Tunnel” (p. 25-55)
The inventory from PW is the same as the inventory from CES. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Circuit Emulation > Circuit Emulation Services. Result: The CES list is shown. ...................................................................................................................................................................................................
2
Select one item in the list Click Search > CES Select the type of resources related to the CES: •
CE Service terminations
•
Server Tunnels Result: The resource list is shown according to the selected type.
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-126 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Configure CES
....................................................................................................................................................................................................................................
Configure CES When to use
The function configures Circuit Emulation Services. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Allocated SATOP CES configuration
When the CES is in allocated state, PKT allows the configuration of the following attributes: • • •
Signal mode PM enabling/granularity TDM clock source
• • • •
Jitter buffer depth Packet replace policy Packet filler pattern Payload suppression
• • •
Average packet loss time window Excessive packet loss threshold Alarm raising threshold
• • •
Alarm clearing threshold Stray packets detection Stray packets threshold
• • • •
Malformed packets threshold Buffer overrun threshold Buffer underrun threshold Remote packet loss threshold
• •
Packet loss threshold Expected ingress RTP payload type
• •
Egress RTP payload type CoS
The attributes are automatically reconfigured in both CES terminations. Implemented SATOP CES configuration
When the CES is in implemented state, PKT allows the configuration of the following attributes: • •
Signal mode PM enabling/granularity
.................................................................................................................................................................................................................................... 1350 OMS 25-127 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Configure CES
....................................................................................................................................................................................................................................
• •
TDM clock source Packet replace policy
• • • • •
Packet filler pattern Payload suppression Average packet loss time window Excessive packet loss threshold Alarm raising threshold
• • •
Alarm clearing threshold Stray packets detection Stray packets threshold
• • • •
Malformed packets threshold Buffer overrun threshold Buffer underrun threshold Remote packet loss threshold
• • • •
Packet loss threshold Expected ingress RTP payload type Egress RTP payload type CoS
The attributes are automatically reconfigured in both CES terminations. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Circuit Emulation > Circuit Emulation Services. Result: The CES list is shown. ...................................................................................................................................................................................................
2
Select one item in the list Select Search > Circuit Emulation > CES Configuration. Result: The CES Configuration window is shown. ...................................................................................................................................................................................................
3
Modify attributes and click OK
.................................................................................................................................................................................................................................... 1350 OMS 25-128 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Configure CES
....................................................................................................................................................................................................................................
Result: The CES is re-Configured. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-129 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Routing display of CES
....................................................................................................................................................................................................................................
Routing display of CES When to use
The function creates a Circuit Emulation Service. Related information
For a description about Circuit Emulation Services, refer to the topic “Routing display of CES” (p. 25-30). For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Services > Circuit Emulation > CES. Result: The Create Circuit Emulation Service list is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Select Search > CES > Routing Display. Result: The graphical routing display is open. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-130 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Configure CES terminations
....................................................................................................................................................................................................................................
Configure CES terminations When to use
The function configures Circuit Emulation Services terminations. Related information
For a description about Circuit Emulation Services, refer to the topic “Circuit Emulation Services definition” (p. 25-4). SATOP CES termination configuration
The CES termination configuration allows to modify the following attributes: •
PM enabling/granularity
The other CES attributes are reconfigured only on CES basis. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From MS-GUI main window: ...................................................................................................................................................................................................
1
List CES terminations. Refer to the procedure “View the list of CES Terminations” (p. 25-114) Result: The CES ermination tlist is shown. ...................................................................................................................................................................................................
2
Select one item in the list. Select Action > CES termination > Configuration. Result: The CES Configuration window is shown. ...................................................................................................................................................................................................
3
Modify attributes and click OK Result: The CES is re-Configured. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-131 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Takeover procedure for MEF8 CES
....................................................................................................................................................................................................................................
Takeover procedure for MEF8 CES When to use
The procedure permit to take in charge Network Elements and Connectivity when the PKT is deployed in a network where (network wide) such connectivity is already in place. Related information
CES Takeover operations start from: •
CES Ports
•
CES NEs
For more information refer to: “CES Takeover description” (p. 25-52) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. Conditions
The topology of the network must be already defined. Ports and Transport link must be assigned to Packet radio domain (MEF8) or T-MPLS (SATOP) domain. Task for MEF8 CES
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select the object to start the CES Takeover using one of the following command: •
Search > Packet > Services > Circuit Emulation > CES Port.
•
Search > Packet > Services > Circuit Emulation > CES NE. Result: The list of the selected objects is shown.
...................................................................................................................................................................................................
2
Select one item in the list Select Action > Takeover Result: NE Cross Connections are uploaded.
PKT recursively discovers all the Cross Connections composing a CES. If the Cross Connections form a complete CES, The CES is automatically created on PKT DB. Port used bandwidth is updated. The CES Provisioning Status is set to Implemented .................................................................................................................................................................................................................................... 1350 OMS 25-132 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Takeover procedure for MEF8 CES
....................................................................................................................................................................................................................................
Note: If Cross Connections are present on NE and do not belong to any CES, they are loaded on DB with reserved consistency state. The user can delete unused Cross Connections. Note: If a Node is not reachable, CES discovery algorithm cannot be completed. The uploaded Cross Connections are not correlated to any CES. Therefore they are loaded on DB with reserved consistency state. When the node is reachable again, the user restart the action to complete the Takeover. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-133 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Takeover procedure for SATOP CES
....................................................................................................................................................................................................................................
Takeover procedure for SATOP CES When to use
The procedure permit to take in charge Network Elements and Connectivity when the PKT is deployed in a network where (network wide) such connectivity is already in place. Related information
For more information refer to: “CES Takeover description” (p. 25-52) For more information refer to: “T-MPLS Takeover description” (p. 18-130) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. Conditions
The topology of the network must be already defined. Ports and Transport link must be assigned to Packet radio domain (MEF8) or T-MPLS (SATOP) domain. Task for SATOP CES
From MS-GUI main window: ...................................................................................................................................................................................................
1
Select Search > Packet > Construction > Link Over Cable. Assign Links Over Cable to T-MPLS domain. For details refer to the procedure “Assign a Link Over Cable to a Domain” (p. 14-60). Result: The selected Links Over Cable are assigned to T-MPLS domain ...................................................................................................................................................................................................
2
Execute the T-MPLS PW Takeover: Select Search > Packet > T-MPLS > T-MPLS domain.. Select the T-MPLS domain. Select Action > T-MPLS > Takeover All Note: In a large network the Takeover from the domain requires a long time to execute. The user can start the Takeover only from involved nodes.
.................................................................................................................................................................................................................................... 1350 OMS 25-134 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management CES Procedures
Takeover procedure for SATOP CES
....................................................................................................................................................................................................................................
Result: T-MPLS Tunnels and PseudoWires are discovered and created in the PKT
DB. ...................................................................................................................................................................................................
3
Assign PWs to CES Domain. For details refer to the procedure “Assign resources to a Domain” (p. 13-27). ...................................................................................................................................................................................................
4
Start the CES Takeover from a CES port or from a CES NE. Refer to “Task for MEF8 CES” (p. 25-132) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 25-135 8DG42227DAAA 9.6 Issue 3 December 2012
Circuit Emulation Service Management
Takeover procedure for SATOP CES
....................................................................................................................................................................................................................................
.................................................................................................................................................................................................................................... 1350 OMS 25-136 8DG42227DAAA 9.6 Issue 3 December 2012
Part IV: Advanced Functions
Overview Purpose
This document part provides conceptual information and procedures to accomplish typical network management tasks. Contents Chapter 26, TSS-320 versus TSS-40 with packet ring
26-1
Chapter 27, Performance Monitoring
27-1
Chapter 28, Enhanced Procedures
28-1
................................................................................................................................................................................................................................... 1350 OMS IV-1 8DG42227DAAA 9.6 Issue 3 December 2012
Advanced Functions
Overview
....................................................................................................................................................................................................................................
.................................................................................................................................................................................................................................... 1350 OMS IV-2 8DG42227DAAA 9.6 Issue 3 December 2012
26
26 TSS-320 versus TSS-40 with packet ring
Overview Purpose
This chapter provides the conceptual information and the associated tasks for managing Ethernet Virtual Connection over the T-MPLS tunnel with packet ring facility. Contents Create T-MPLS Tunnel and PW (SNI)
26-2
Create T-MPLS tunnel 320-40 (SNI)
26-2
Create T-MPLS PW 320-40 (SNI) Create T-MPLS Tunnel and PW (DNI)
26-14 26-21
Create T-MPLS tunnel 320-40 (DNI)
26-21
Create T-MPLS PW 320-40 (DNI)
26-33
Create EVC over T-MPLS 320-40
26-40
Create EVC over T-MPLS 320-40
26-40
Verify creation of EVC over T-MPLS 320-40
26-58
................................................................................................................................................................................................................................... 1350 OMS 26-1 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (SNI)
Create T-MPLS tunnel 320-40 (SNI)
....................................................................................................................................................................................................................................
Create T-MPLS Tunnel and PW (SNI) Create T-MPLS tunnel 320-40 (SNI) When to use
The scope of this procedure is to create the T-MPLS tunnel between TSS-40 and TSS-160/320. Related Information
The reference network is shown below. Figure 26-1 Reference Network
.................................................................................................................................................................................................................................... 1350 OMS 26-2 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (SNI)
Create T-MPLS tunnel 320-40 (SNI)
....................................................................................................................................................................................................................................
Before you begin
All needed conditions are detailed along the procedure. Task ...................................................................................................................................................................................................
1
From the main menu bar select Actions > Packet > T-MPLS > Create T-MPLS tunnel. Figure 26-2 Actions>Packet>T-MPLS>Create T-MPLS tunnel
...................................................................................................................................................................................................
2
In the Create T-MPLS tunnel box: •
enter User Label name
•
Topology = Point to Point
.................................................................................................................................................................................................................................... 1350 OMS 26-3 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (SNI)
Create T-MPLS tunnel 320-40 (SNI)
....................................................................................................................................................................................................................................
•
Protection Level = Packet Ring Bidir
•
Flow = bidirectional
Figure 26-3 Create T-MPLS tunnel
...................................................................................................................................................................................................
3
Select folder Quality of Service. Enter CIR, PIR, CBS, PBS and select T-MPLS PHB Profile. ...................................................................................................................................................................................................
4
Select folder OAM
.................................................................................................................................................................................................................................... 1350 OMS 26-4 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (SNI)
Create T-MPLS tunnel 320-40 (SNI)
....................................................................................................................................................................................................................................
Set fields Alarm Enable, CV (Connectivity Verification) Enable, CV Period, PM granularity. Click on Next. ...................................................................................................................................................................................................
5
In step2 you will select: •
the first extremity working
•
the first extremity protection
•
the second extremity
Select the node relevant to the first extremity working and to the first extremity protection (Node 122 in this case). Figure 26-4 Point to point Packet Ring bidir protected T-MPLS tunnel
.................................................................................................................................................................................................................................... 1350 OMS 26-5 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (SNI)
Create T-MPLS tunnel 320-40 (SNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
6
Select the port for the first extremity working. It is the SDH port used by the SDH path connecting Node 41 to Node 122. Figure 26-5 Selection of the port
...................................................................................................................................................................................................
7
Analogously select the first extremity protection port on the same node.
.................................................................................................................................................................................................................................... 1350 OMS 26-6 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (SNI)
Create T-MPLS tunnel 320-40 (SNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
8
Select the second extremity, in our case node TSS-40_41 Figure 26-6 Select the second extremity (node)
...................................................................................................................................................................................................
9
Select the port working and protecting, according to the physical connections previously created.
.................................................................................................................................................................................................................................... 1350 OMS 26-7 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (SNI)
Create T-MPLS tunnel 320-40 (SNI)
....................................................................................................................................................................................................................................
Figure which follows shows all selected extremities. Figure 26-7 P2P bid prot T-MPLS tunnel: selected extremities
.................................................................................................................................................................................................................................... 1350 OMS 26-8 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (SNI)
Create T-MPLS tunnel 320-40 (SNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
10
Select the constraint. It is the one relevant to the main tunnel. Figure 26-8 P2P: constraint
.................................................................................................................................................................................................................................... 1350 OMS 26-9 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (SNI)
Create T-MPLS tunnel 320-40 (SNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
11
Extremities and constraint have been selected. Click on Apply to confirm. Figure 26-9 P2P bid prot T-MPLS tunnel: selected extremities and constraint
.................................................................................................................................................................................................................................... 1350 OMS 26-10 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (SNI)
Create T-MPLS tunnel 320-40 (SNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
12
The tunnel has been created. To verify the creation issue Search > Packet > T-MPLS > T-MPLS Tunnels. Figure 26-10 Search>Packet>T-MPLS>T-MPLS Tunnels
.................................................................................................................................................................................................................................... 1350 OMS 26-11 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (SNI)
Create T-MPLS tunnel 320-40 (SNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
13
The tunnel is created with status defined. Select the created tunnel in the list and issue, using the right mouse button, Actions > Allocate. Figure 26-11 Tunnel list
...................................................................................................................................................................................................
14
Implement the tunnel. Figure 26-12 Actions>Implement T-MPLS Tunnel
.................................................................................................................................................................................................................................... 1350 OMS 26-12 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (SNI)
Create T-MPLS tunnel 320-40 (SNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
15
The tunnel is now implemented. Figure 26-13 The tunnel is implemented
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 26-13 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (SNI)
Create T-MPLS PW 320-40 (SNI)
....................................................................................................................................................................................................................................
Create T-MPLS PW 320-40 (SNI) When to use
The scope of this procedure is to create a pseudo wire within a T-MPLS tunnel. Related Information
All needed conditions are detailed along the procedure. Before you begin
All needed conditions are detailed along the procedure. Task ...................................................................................................................................................................................................
1
From the main bar select Actions > Packet > T-MPLS > Create T-MPLS Pseudo Wire. Figure 26-14 Actions>Packet>T-MPLS>Create T-MPLS Pseudo Wire
.................................................................................................................................................................................................................................... 1350 OMS 26-14 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (SNI)
Create T-MPLS PW 320-40 (SNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
2
In the Create T-MPLS Pseudo Wire box select: •
User Label
•
Topology = Point to Point
•
Flow = Bidirectional
Figure 26-15 Create T-MPLS Pseudo Wire
...................................................................................................................................................................................................
3
Select folder Quality of Service
.................................................................................................................................................................................................................................... 1350 OMS 26-15 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (SNI)
Create T-MPLS PW 320-40 (SNI)
....................................................................................................................................................................................................................................
Enter CIR, PIR, CBS, PBS and select T-MPLS PHB Profile. Note: These values must be consistent with those specified for the relevant tunnel ...................................................................................................................................................................................................
4
Select OAM values. Click on Next. ...................................................................................................................................................................................................
5
Select the extremities. The modality of selection is the same as described for the above procedure of tunnel create.
.................................................................................................................................................................................................................................... 1350 OMS 26-16 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (SNI)
Create T-MPLS PW 320-40 (SNI)
....................................................................................................................................................................................................................................
The constraint is the above mentioned tunnel. Figure 26-16 Point to Point Bidirectional T-MPLS PW
.................................................................................................................................................................................................................................... 1350 OMS 26-17 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (SNI)
Create T-MPLS PW 320-40 (SNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
6
Select Search > Packe t> T-MPLS > T-MPLS Pseudo Wire. Figure 26-17 Search>Packet>T-MPLS>T-MPLS Pseudo Wire
...................................................................................................................................................................................................
7
The list of the T-MPLS pseudo wires is shown below. The PW just created is Allocated. Figure 26-18 T-MPLS Pseudo Wires
.................................................................................................................................................................................................................................... 1350 OMS 26-18 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (SNI)
Create T-MPLS PW 320-40 (SNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
8
Select the relevant Pseudo Wire and issue Actions > Implement T-MPLS Pseudo wire. Figure 26-19 PW Implementation
...................................................................................................................................................................................................
9
The T-MPLS Pseudo wire is now implemented. Figure 26-20 T-MPLS Pseudo wire implemented
...................................................................................................................................................................................................
10
The Pseudo Wire is seen as a T-MPLS Transport Link in the area of the Services. From the main menu bar issue Search > Packet > Services > T-MPLS > T-MPLS Transport Links to list the Transport Links.
.................................................................................................................................................................................................................................... 1350 OMS 26-19 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (SNI)
Create T-MPLS PW 320-40 (SNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
11
The list of the T-MPLS Transport Links is displayed. It includes the Pseudo Wire just created. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 26-20 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (DNI)
Create T-MPLS tunnel 320-40 (DNI)
....................................................................................................................................................................................................................................
Create T-MPLS Tunnel and PW (DNI) Create T-MPLS tunnel 320-40 (DNI) When to use
The scope of this procedure is to create the T-MPLS tunnel between TSS-40 and TSS-160/320. Related Information
The reference network is shown below. Figure 26-21 Reference Network
.................................................................................................................................................................................................................................... 1350 OMS 26-21 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (DNI)
Create T-MPLS tunnel 320-40 (DNI)
....................................................................................................................................................................................................................................
Before you begin
All needed conditions are detailed along the procedure. Task ...................................................................................................................................................................................................
1
From the main menu bar select Actions > Packet > T-MPLS > Create T-MPLS tunnel. Figure 26-22 Actions>Packet>T-MPLS>Create T-MPLS tunnel
...................................................................................................................................................................................................
2
In the Create T-MPLS tunnel box enter: •
the User Label
the Topology = Point to Point the Protection Level = Packet Ring Bidir Open .................................................................................................................................................................................................................................... 1350 OMS 26-22 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (DNI)
Create T-MPLS tunnel 320-40 (DNI)
....................................................................................................................................................................................................................................
the Flow = bidirectional Figure 26-23 Create T-MPLS tunnel
...................................................................................................................................................................................................
3
Select folder Quality of Service. Enter CIR, PIR, CBS, PBS and select T-MPLS PHB Profile. ...................................................................................................................................................................................................
4
Select folder OAM
.................................................................................................................................................................................................................................... 1350 OMS 26-23 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (DNI)
Create T-MPLS tunnel 320-40 (DNI)
....................................................................................................................................................................................................................................
Set fields Alarm Enable, CV (Connectivity Verification) Enable, CV Period, PM granularity. Click on Next. ...................................................................................................................................................................................................
5
In step2 you will select: •
the first extremity working
•
the first extremity protection
•
the second extremity
Select the node relevant to the first extremity working (Node 122 in this case). Figure 26-24 Point to point Packet Ring bidir protected T-MPLS tunnel open sink
.................................................................................................................................................................................................................................... 1350 OMS 26-24 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (DNI)
Create T-MPLS tunnel 320-40 (DNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
6
Select the port. It is the SDH port used by the SDH path connecting Node 41 to Node 122. Figure 26-25 Selection of the port
...................................................................................................................................................................................................
7
Analogously select the first extremity protection
.................................................................................................................................................................................................................................... 1350 OMS 26-25 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (DNI)
Create T-MPLS tunnel 320-40 (DNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
8
Select the second extremity, in our case node TSS-40_41 Figure 26-26 Select the second extremity (node)
...................................................................................................................................................................................................
9
Select the port working and protecting, according to the physical connections previously created.
.................................................................................................................................................................................................................................... 1350 OMS 26-26 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (DNI)
Create T-MPLS tunnel 320-40 (DNI)
....................................................................................................................................................................................................................................
Figure which follows shows all selected extremities. Figure 26-27 P2P bid prot T-MPLS tunnel open sink: selected extremities
.................................................................................................................................................................................................................................... 1350 OMS 26-27 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (DNI)
Create T-MPLS tunnel 320-40 (DNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
10
Select the constraint. It is the one relevant to the main tunnel. Figure 26-28 P2P open sink: constraint
.................................................................................................................................................................................................................................... 1350 OMS 26-28 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (DNI)
Create T-MPLS tunnel 320-40 (DNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
11
Extremities and constraint have been selected. Click on Apply to confirm. Figure 26-29 P2P bid prot T-MPLS tunnel open sink: selected extremities and constraint
.................................................................................................................................................................................................................................... 1350 OMS 26-29 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (DNI)
Create T-MPLS tunnel 320-40 (DNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
12
The tunnel has been created. To verify the creation issue Search > Packet > T-MPLS > T-MPLS Tunnels. Figure 26-30 Search>Packet>T-MPLS>T-MPLS Tunnels
.................................................................................................................................................................................................................................... 1350 OMS 26-30 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (DNI)
Create T-MPLS tunnel 320-40 (DNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
13
The tunnel is created with status defined. Select the created tunnel in the list and issue, using the right mouse button, Actions > Allocate. Figure 26-31 Tunnel list
...................................................................................................................................................................................................
14
Implement the tunnel. Figure 26-32 Actions>Implement T-MPLS Tunnel
.................................................................................................................................................................................................................................... 1350 OMS 26-31 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (DNI)
Create T-MPLS tunnel 320-40 (DNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
15
The tunnel is now implemented. Figure 26-33 The tunnel is implemented
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 26-32 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (DNI)
Create T-MPLS PW 320-40 (DNI)
....................................................................................................................................................................................................................................
Create T-MPLS PW 320-40 (DNI) When to use
The scope of this procedure is to create a pseudo wire within a T-MPLS tunnel. Related Information
All needed conditions are detailed along the procedure. Before you begin
All needed conditions are detailed along the procedure. Task ...................................................................................................................................................................................................
1
From the main bar select Actions > Packet > T-MPLS > Create T-MPLS Pseudo Wire. Figure 26-34 Actions>Packet>T-MPLS>Create T-MPLS Pseudo Wire
.................................................................................................................................................................................................................................... 1350 OMS 26-33 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (DNI)
Create T-MPLS PW 320-40 (DNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
2
In the Create T-MPLS Pseudo Wire box select: •
User Label
•
Topology = Dual Point to Point
•
Flow = Bidirectional
Figure 26-35 Create T-MPLS Pseudo Wire
...................................................................................................................................................................................................
3
Select folder Quality of Service
.................................................................................................................................................................................................................................... 1350 OMS 26-34 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (DNI)
Create T-MPLS PW 320-40 (DNI)
....................................................................................................................................................................................................................................
Enter CIR, PIR, CBS, PBS and select T-MPLS PHB Profile. Note: these values must be consistent with those specified for the relevant tunnel ...................................................................................................................................................................................................
4
Select OAM values. Click on Next. ...................................................................................................................................................................................................
5
Select the extremities. The modality of selection is the same as described for the above procedure of tunnel create.
.................................................................................................................................................................................................................................... 1350 OMS 26-35 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (DNI)
Create T-MPLS PW 320-40 (DNI)
....................................................................................................................................................................................................................................
The constraint is the above mentioned tunnel. Figure 26-36 Dual Point to Point Bidirectional T-MPLS PW
.................................................................................................................................................................................................................................... 1350 OMS 26-36 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (DNI)
Create T-MPLS PW 320-40 (DNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
6
Select Search > Packet > T-MPLS > T-MPLS Pseudo Wire Figure 26-37 Search>Packet>T-MPLS>T-MPLS Pseudo Wire
...................................................................................................................................................................................................
7
The list of the T-MPLS pseudo wires is shown below. The PW just created is Allocated. Figure 26-38 T-MPLS Pseudo Wires
.................................................................................................................................................................................................................................... 1350 OMS 26-37 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (DNI)
Create T-MPLS PW 320-40 (DNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
8
Select the relevant Pseudo Wire and issue Actions > Implement T-MPLS Pseudo wire. Figure 26-39 PW Implementation
...................................................................................................................................................................................................
9
The T-MPLS Pseudo wire is now implemented. Figure 26-40 T-MPLS Pseudo wire implemented
...................................................................................................................................................................................................
10
The Pseudo Wire is seen as a T-MPLS Transport Link in the area of the Services. From the main menu bar issue Search > Packet > Services > T-MPLS > T-MPLS Transport Links to list the Transport Links.
.................................................................................................................................................................................................................................... 1350 OMS 26-38 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create T-MPLS Tunnel and PW (DNI)
Create T-MPLS PW 320-40 (DNI)
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
11
The list of the T-MPLS Transport Links is displayed. It includes the Pseudo Wire just created. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 26-39 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create EVC over T-MPLS 320-40
Overview
....................................................................................................................................................................................................................................
Create EVC over T-MPLS 320-40 Create EVC over T-MPLS 320-40 When to use
The scope of this procedure is to create an EVC over T-MPLS. Related Information
All needed conditions are detailed along the procedure Before you begin
All needed conditions are detailed along the procedure Task ...................................................................................................................................................................................................
1
From the main menu bar select Actions > Packet > Services > T-MPLS > Create T-MPLS EVC Figure 26-41 Actions>Packet>Services>T-MPLS>Create T-MPLS EVC
...................................................................................................................................................................................................
2
Folder Specific is already selected.
.................................................................................................................................................................................................................................... 1350 OMS 26-40 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create EVC over T-MPLS 320-40
Create EVC over T-MPLS 320-40
....................................................................................................................................................................................................................................
Select the following attributes: •
User Label
• • •
Select Service type, e.g. Service type=EVPLAN Ethernet service and type are not meaningful Select domain=T-MPLS
.................................................................................................................................................................................................................................... 1350 OMS 26-41 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create EVC over T-MPLS 320-40
Create EVC over T-MPLS 320-40
....................................................................................................................................................................................................................................
• •
Select traffic type=unicast. For service type=BTV, traffic type=multicast Select resource sharing=Full. It describes the resource reservation (UNI and link).
Figure 26-42 Create T-MPLS EVC: Specific
...................................................................................................................................................................................................
3
Select folder Detail.
.................................................................................................................................................................................................................................... 1350 OMS 26-42 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create EVC over T-MPLS 320-40
Create EVC over T-MPLS 320-40
....................................................................................................................................................................................................................................
Default values are OK. ...................................................................................................................................................................................................
4
Select folder Info. This folder houses only textual comments. ...................................................................................................................................................................................................
5
Select folder PM Execute the suitable selections. ...................................................................................................................................................................................................
6
Select folder Miscellaneous. Execute the suitable selections. Click Next. ...................................................................................................................................................................................................
7
Select the node. Select the port. Figure 26-43 Create T-MPLS EVC: Terminations Selection
.................................................................................................................................................................................................................................... 1350 OMS 26-43 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create EVC over T-MPLS 320-40
Create EVC over T-MPLS 320-40
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
8
Select the second node and the port. Figure 26-44 Terminations Selection
...................................................................................................................................................................................................
9
Termination Setting. It is the definition of the traffic flows.
.................................................................................................................................................................................................................................... 1350 OMS 26-44 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create EVC over T-MPLS 320-40
Create EVC over T-MPLS 320-40
....................................................................................................................................................................................................................................
Click Traffic Descriptor button. Select the traffic descriptor from the selection box and Click V-sign to confirm. Note: Traffic Descriptor values (CIR, PIR,....) must be contained in the corresponding values of the PW being associated.
.................................................................................................................................................................................................................................... 1350 OMS 26-45 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create EVC over T-MPLS 320-40
Create EVC over T-MPLS 320-40
....................................................................................................................................................................................................................................
See TransportLlink selection phase of the EVC over T-MPLS tunnel create (this procedure) Figure 26-45 Termination Settings
...................................................................................................................................................................................................
10
Select policy mode. If you select color aware, you will select color profile
.................................................................................................................................................................................................................................... 1350 OMS 26-46 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create EVC over T-MPLS 320-40
Create EVC over T-MPLS 320-40
....................................................................................................................................................................................................................................
Select classification priority-code0-7 / DSCP code 0-63 Select VLAN POP disabled ...................................................................................................................................................................................................
11
Folder Traffic Classifier deals on VLAN id Folder Leaf Term deals on HSI Folder Reuse Flows allows to copy and reuse flow characteristics.
.................................................................................................................................................................................................................................... 1350 OMS 26-47 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create EVC over T-MPLS 320-40
Create EVC over T-MPLS 320-40
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
12
Click Create. Figure 26-46 Ingress flow create
.................................................................................................................................................................................................................................... 1350 OMS 26-48 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create EVC over T-MPLS 320-40
Create EVC over T-MPLS 320-40
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
13
You can monitor that the Ingress flow has been created: after create the relevant traffic descriptor is displayed in the bottom of the window Figure 26-47 Ingress Flow: create monitoring
.................................................................................................................................................................................................................................... 1350 OMS 26-49 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create EVC over T-MPLS 320-40
Create EVC over T-MPLS 320-40
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
14
Select button Egress Flow, folder Push Select: •
Class of service (guaranteed/best effort/regulated)
•
If you select Clear all fields, subsequent fields can be ignored.
.................................................................................................................................................................................................................................... 1350 OMS 26-50 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create EVC over T-MPLS 320-40
Create EVC over T-MPLS 320-40
....................................................................................................................................................................................................................................
• •
VLAN ID. It is an additional ID added to the stack. Priority Mode. If set to Color Aware fields Green Priority and Yellow Priority are
active. Figure 26-48 Egress Flow: Push
.................................................................................................................................................................................................................................... 1350 OMS 26-51 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create EVC over T-MPLS 320-40
Create EVC over T-MPLS 320-40
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
15
Click Create Egress You can monitor that the Egress flow has been created: after create the relevant traffic descriptor is displayed in the bottom of the window Figure 26-49 Create Egress monitoring
.................................................................................................................................................................................................................................... 1350 OMS 26-52 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create EVC over T-MPLS 320-40
Create EVC over T-MPLS 320-40
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
16
Select folder Spoke Transport Link selection Figure 26-50 Spoke Transport Link selection
...................................................................................................................................................................................................
17
Select the other port (on TSS-146)
.................................................................................................................................................................................................................................... 1350 OMS 26-53 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create EVC over T-MPLS 320-40
Create EVC over T-MPLS 320-40
....................................................................................................................................................................................................................................
All fields are already set with the selections made for the first port. Select Create Ingress. Figure 26-51 Create Ingress node A
.................................................................................................................................................................................................................................... 1350 OMS 26-54 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create EVC over T-MPLS 320-40
Create EVC over T-MPLS 320-40
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
18
Select Create Egress. Click Next button. Figure 26-52 Create Egress node A
.................................................................................................................................................................................................................................... 1350 OMS 26-55 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create EVC over T-MPLS 320-40
Create EVC over T-MPLS 320-40
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
19
Select the Pseudo Wire just created . Figure 26-53 Select the transport link
...................................................................................................................................................................................................
20
Select EVC state (implemented).
.................................................................................................................................................................................................................................... 1350 OMS 26-56 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create EVC over T-MPLS 320-40
Create EVC over T-MPLS 320-40
....................................................................................................................................................................................................................................
Click OK to confirm EVC creation. Figure 26-54 T-MPLS EVC Allocate and Implement
E................................................................................................................................................................................................... N D O F S T E P S .................................................................................................................................................................................................................................... 1350 OMS 26-57 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create EVC over T-MPLS 320-40
Verify creation of EVC over T-MPLS 320-40
....................................................................................................................................................................................................................................
Verify creation of EVC over T-MPLS 320-40 When to use
The scope of this procedure is to verify the creation of EVC over T-MPLS. Related Information
This task does not have any related information. Before you begin
This task does not have any preconditions. Task ...................................................................................................................................................................................................
1
From the main menu bar select Search > Packet > Services > T-MPLS > T-MPLS EVCs. Figure 26-55 Search>Packet>Services>T-MPLS>T-MPLS EVCs
.................................................................................................................................................................................................................................... 1350 OMS 26-58 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring Create EVC over T-MPLS 320-40
Verify creation of EVC over T-MPLS 320-40
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
2
The list of the T-MPLS EVCs is displayed. Figure 26-56 T-MPLS EVCs
...................................................................................................................................................................................................
3
Allocate the EVC Figure 26-57 Allocate the EVC
...................................................................................................................................................................................................
4
Implement the EVC Figure 26-58 EVC implemented
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 26-59 8DG42227DAAA 9.6 Issue 3 December 2012
TSS-320 versus TSS-40 with packet ring
Verify creation of EVC over T-MPLS 320-40
....................................................................................................................................................................................................................................
.................................................................................................................................................................................................................................... 1350 OMS 26-60 8DG42227DAAA 9.6 Issue 3 December 2012
27
Performance Monitoring 27
Overview Purpose
This chapter provides the conceptual information and the associated tasks for the Performance Monitoring management of the1350 OMS PKT application. Contents PM in EVC create
27-2
PM in EVC create
27-2
Performance Monitoring activate
27-7
PM activate
27-7
PM consistency PM consistency PM Reports create PM Reports create PM report generate PM report generate
27-12 27-12 27-15 27-15 27-19 27-19
................................................................................................................................................................................................................................... 1350 OMS 27-1 8DG42227DAAA 9.6 Issue 3 December 2012
Performance Monitoring PM in EVC create
PM in EVC create
....................................................................................................................................................................................................................................
PM in EVC create PM in EVC create When to use
The scope of this procedure is to set PM characteristics in the phase of EVC create. Related Information
This task does not have any related information. Before you begin
This task does not have any preconditions.
.................................................................................................................................................................................................................................... 1350 OMS 27-2 8DG42227DAAA 9.6 Issue 3 December 2012
Performance Monitoring PM in EVC create
PM in EVC create
....................................................................................................................................................................................................................................
Task ...................................................................................................................................................................................................
1
During the EVC creation phase select PM folder on the creation window. Figure 27-1 EVC definition: PM folder
...................................................................................................................................................................................................
2
You have to set:
.................................................................................................................................................................................................................................... 1350 OMS 27-3 8DG42227DAAA 9.6 Issue 3 December 2012
Performance Monitoring PM in EVC create
PM in EVC create
....................................................................................................................................................................................................................................
• PM active or not • granularity (15 ', 24 h) • CSV reporting (typically 2 h) • policy, which deals on maintaining PM data (keep/Purge on stop/Purge on Delete/Not meaningful) Figure 27-2 EVC definition: PM policy
.................................................................................................................................................................................................................................... 1350 OMS 27-4 8DG42227DAAA 9.6 Issue 3 December 2012
Performance Monitoring PM in EVC create
PM in EVC create
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
3
When creating a measure, via Actions > Create Measure Figure 27-3 Create Measure
.................................................................................................................................................................................................................................... 1350 OMS 27-5 8DG42227DAAA 9.6 Issue 3 December 2012
Performance Monitoring PM in EVC create
PM in EVC create
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
Enter the following attributes: • •
measure name (userlabel) . The measure name can be modified only if the measure status is PLANNED. start/end time. If you do not specify start/end time, you can subsequently activate manually the measure by means of the command Measure Start, otherwise the Measure will be started at the Start Time and stopped at the Stop time.
•
granularity. The granularity is the monitoring frequency, i.e. the frequency of historical data counters grouping. You can select: – 24 hours . Data are grouped per day. – 15 minutes. Data are grouped per quarter of hour.
• • • •
flow (aggregate/flow/aggregate flow) Automatic Purge of the Measure (TRUE/FALSE) Purge State of the Measure (when stopped/when terminated) Automatic deletion Hystorical Data (TRUE/FALSE)
...................................................................................................................................................................................................
5
Click on button OK to confirm the creation. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 27-6 8DG42227DAAA 9.6 Issue 3 December 2012
Performance Monitoring Performance Monitoring activate
PM activate
....................................................................................................................................................................................................................................
Performance Monitoring activate PM activate When to use
The scope of this procedure is to activate PM. Related Information
This task does not have any related information. Before you begin
This task does not have any preconditions. Task ...................................................................................................................................................................................................
1
From the measure list issue Actions menu. Figure 27-4 Measure: Actions menu options
.................................................................................................................................................................................................................................... 1350 OMS 27-7 8DG42227DAAA 9.6 Issue 3 December 2012
Performance Monitoring Performance Monitoring activate
PM activate
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
2
From the main menu bar the user can issue Search > PM > PM domains on NML. Figure 27-5 Search>PM>PM domains
...................................................................................................................................................................................................
3
The list of the PM domains on NML is displayed. Select Ethernet domain and issue the Search menu. Figure 27-6 Ethernet domain: Search menu
.................................................................................................................................................................................................................................... 1350 OMS 27-8 8DG42227DAAA 9.6 Issue 3 December 2012
Performance Monitoring Performance Monitoring activate
PM activate
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
The corresponding Actions menu is shown below. Figure 27-7 Ethernet domain: Actions menu
...................................................................................................................................................................................................
5
You may select a PM transport and subsequently the Actions menu. Figure 27-8 PM transport: Actions menu
.................................................................................................................................................................................................................................... 1350 OMS 27-9 8DG42227DAAA 9.6 Issue 3 December 2012
Performance Monitoring Performance Monitoring activate
PM activate
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
6
From the PM transport you can find the PM TP list. Figure 27-9 PM TP list
...................................................................................................................................................................................................
7
Select a PMTP and issue Actions>Start TP Figure 27-10 Start TP dialog box
.................................................................................................................................................................................................................................... 1350 OMS 27-10 8DG42227DAAA 9.6 Issue 3 December 2012
Performance Monitoring Performance Monitoring activate
PM activate
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
8
Select a PMTP and issue Actions>Stop TP Figure 27-11 Stop TP dialog box
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 27-11 8DG42227DAAA 9.6 Issue 3 December 2012
Performance Monitoring PM consistency
PM consistency
....................................................................................................................................................................................................................................
PM consistency PM consistency When to use
The scope of this procedure is to execute consistency checks on PM data. Related Information
This task does not have any related information. Before you begin
This task does not have any preconditions.
.................................................................................................................................................................................................................................... 1350 OMS 27-12 8DG42227DAAA 9.6 Issue 3 December 2012
Performance Monitoring PM consistency
PM consistency
....................................................................................................................................................................................................................................
Task ...................................................................................................................................................................................................
1
From the measure list select the measure and issue Actions>Measure consistency Figure 27-12 Measure consistency
...................................................................................................................................................................................................
2
From the PM NE select Actions>Generate Audit Figure 27-13 NE: Actions>Generate Audit
.................................................................................................................................................................................................................................... 1350 OMS 27-13 8DG42227DAAA 9.6 Issue 3 December 2012
Performance Monitoring PM consistency
PM consistency
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
3
The Generate Audit box allows to launch the operation. Figure 27-14 Generate Audit
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 27-14 8DG42227DAAA 9.6 Issue 3 December 2012
Performance Monitoring PM Reports create
PM Reports create
....................................................................................................................................................................................................................................
PM Reports create PM Reports create When to use
The scope of this procedure is to create PM Reports. Related Information
This task does not have any related information. Before you begin
This task does not have any preconditions.
.................................................................................................................................................................................................................................... 1350 OMS 27-15 8DG42227DAAA 9.6 Issue 3 December 2012
Performance Monitoring PM Reports create
PM Reports create
....................................................................................................................................................................................................................................
Task ...................................................................................................................................................................................................
1
From the measure issue Actions>Create Report Profile. Figure 27-15 Create Report Profile
.................................................................................................................................................................................................................................... 1350 OMS 27-16 8DG42227DAAA 9.6 Issue 3 December 2012
Performance Monitoring PM Reports create
PM Reports create
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
2
You can issue the correlation of the Measure with Report Profile. Figure 27-16 Correlation Measure with Report Profile
.................................................................................................................................................................................................................................... 1350 OMS 27-17 8DG42227DAAA 9.6 Issue 3 December 2012
Performance Monitoring PM Reports create
PM Reports create
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
3
You can issue the uncorrelation of the Measure from Report Profile. Figure 27-17 Uncorrelation Measure with Report Profile
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 27-18 8DG42227DAAA 9.6 Issue 3 December 2012
Performance Monitoring PM report generate
Overview
....................................................................................................................................................................................................................................
PM report generate PM report generate When to use
The scope of this procedure is to generate PM Reports. Related Information
This task does not have any related information. Before you begin
This task does not have any preconditions. Task ...................................................................................................................................................................................................
1
From PM TP Actions menu you can select the generate of the suitable report. Figure 27-18 PM TP Actions menu
.................................................................................................................................................................................................................................... 1350 OMS 27-19 8DG42227DAAA 9.6 Issue 3 December 2012
Performance Monitoring PM report generate
PM report generate
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
2
It is required to export TPs to CSV file. Figure 27-19 Export TPs to CSV file
.................................................................................................................................................................................................................................... 1350 OMS 27-20 8DG42227DAAA 9.6 Issue 3 December 2012
Performance Monitoring PM report generate
PM report generate
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
3
You can generate Measure PM Report to CSV file. Figure 27-20 Generate Measure PM Report to CSV file
.................................................................................................................................................................................................................................... 1350 OMS 27-21 8DG42227DAAA 9.6 Issue 3 December 2012
Performance Monitoring PM report generate
PM report generate
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
4
Or generate PM tabular report. Figure 27-21 Generate PM tabular report
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 27-22 8DG42227DAAA 9.6 Issue 3 December 2012
28
Enhanced Procedures 28
Overview Purpose
This chapter provides collect procedures dedicated to specific purpose. Contents TSS 5 In Band Management
28-3
Overview
28-3
T-MPLS Subnetwork topology
28-4
In-band configuration
28-8
Resources reservation for In fiber Inband Ethernet Linear Protection
28-11 28-16
Link Over EVC
28-18
Link over EVC: unlock EVC
28-20
Link over EVC creation
28-22
Link over EVC deletion
28-24
Link over EVC: Alarms
28-25
Link over EVC: OAM
28-26
Link over EVC: assign and deassign
28-27
Link over EVC: Transport Link configuration
28-28
Link over EVC: activation and deactivation
28-29
Link over EVC: Usage within an EVC
28-30
Link over EVC: AAR
28-31
Link over EVC: Routing Display
28-32
Link over EVC: Inventory
28-33
Ethernet Linear Protection (ELP)
28-34
Add protection to PB EVC
28-39
................................................................................................................................................................................................................................... 1350 OMS 28-1 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures
Overview
....................................................................................................................................................................................................................................
Remove protection from EVC
28-41
Configure protection
28-42
ELP Protection properties
28-43
Description of the properties
28-44
Send APS command to protection group
28-45
Manual alignment of protection group
28-47
Implement a protected EVC
28-48
Deimplement a protected EVC
28-49
Disabled operations
28-50
Alarm propagation for protected EVCs
28-51
OAM on protected EVC
28-52
Inventory of Transport Link from protected EVC
28-54
Inventory of MA from protected EVC
28-55
Routing Display of protected EVC
28-56
.................................................................................................................................................................................................................................... 1350 OMS 28-2 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures TSS 5 In Band Management
Overview
....................................................................................................................................................................................................................................
TSS 5 In Band Management Overview About the in-band management
The equipment of the family TSS 320, 100 etc. are able to take in charge and manage other devices (TSS-3, TSS-5 etc.) usually on the customer side. The local management is made by DCN, in the case of remote devices the management is implemented by reserving a channel on the fiber link. On the cable PKT realizes user services that are added to the service reserved to the control. Management systems such as PKT must take into account the resources already allocated in the managing equipment during both the allocation of new resources for the user, but especially during the reserve release. In case of release of all the resources you should not put down the ports when the channel management must remain active. The ZIC configures the "IN BAND MANAGEMENT". The cable port is configured with an IP address reserved for the equipment to manage (add route) and a VLAN = 4094 reserved for the management of the NE (VLAN-DCN). In the case of TSS-5, T-MPLS management requires a structuring of the cable tunnel and the pseudowire. The PKT, to learn about the resources allocated by the ZIC should do a Takeover that is not working with TSS-5/T-MPLS. Therefore needs to be rebuilt in PKT "hand" made the management structure and take it up with the ZIC Allocated in order to reserve resources at PKT. These resources must be recognizable not be erased by the operator.
.................................................................................................................................................................................................................................... 1350 OMS 28-3 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures TSS 5 In Band Management
T-MPLS Subnetwork topology
....................................................................................................................................................................................................................................
T-MPLS Subnetwork topology Single T-MPLS sub-network
OMS uses the Router as a gateway (next hop) to manage the TSS nodes. A VSI is configured on TSS-320 to transport the management traffic received from OMS (via Router). The VSI consists of an incoming port from the Router, PWs connecting to the remote TSS-5s, and a local interface to TSS-320. Initially, when the OMS sends traffic towards TSS-5, the Router sends ARP request towards TSS-320. The VSI on TSS-320 broadcasts this request over all ports/PWs of the VSI. When the ARP response is received from TSS-5 the VSI learns the MAC address over the PW and forwards it to the Router. The Router resolves the IP to MAC address of TSS-5. All further traffic from the OMS (via Router) is sent with MAC address of TSS-5. The VSI on TSS-320 forwards this traffic on a specific PW based on the destination MAC address of the packet. In this topology all IP addresses are on the same IP subnet.
.................................................................................................................................................................................................................................... 1350 OMS 28-4 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures TSS 5 In Band Management
T-MPLS Subnetwork topology
....................................................................................................................................................................................................................................
Multiple T-MPLS subnetworks with separate physical connection
Each T-MPLS network has nodes in different IP subnetworks. For e.g. TSS-5 – {a, b, and c} are in a different subnetwork compared to TSS-5-{x, y, and z}. A separate physical connection is provided from the Router to the TSS-320 for each subnetwork. The VSIs forward traffic similar to the single T-MPLS subnetwork topology.
.................................................................................................................................................................................................................................... 1350 OMS 28-5 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures TSS 5 In Band Management
T-MPLS Subnetwork topology
....................................................................................................................................................................................................................................
Multiple T-MPLS subnetworks with single physical connection
Each T-MPLS network has nodes in different IP subnetworks. For e.g. TSS-5 – {a, b, and c} are in a different subnetwork compared to TSS-5- {x, y, and z}. A single physical connection is provided from the Router the TSS-320 for each subnetwork. Outgoing traffic from the Router is tagged with a different VLAN for each IP subnetwork. On the TSS-320, each VLAN’s traffic is associated with a different VSI. The VSIs forward traffic similar to the single T-MPLS subnetwork topology.
.................................................................................................................................................................................................................................... 1350 OMS 28-6 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures TSS 5 In Band Management
T-MPLS Subnetwork topology
....................................................................................................................................................................................................................................
Protection
In the protected solutions, the PW and the Tunnel may take an alternate path for protection.
.................................................................................................................................................................................................................................... 1350 OMS 28-7 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures TSS 5 In Band Management
In-band configuration
....................................................................................................................................................................................................................................
In-band configuration Configuration Notes Figure 28-1 TSS-5 interworking with TSS160/320
Configuration requirements •
VLAN tag The TSS5 requires a VLAN tag on management traffic. The router sends untagged traffic. The TSS160/320 is not able to push a VLAN tag onto incoming traffic. As a result there are 2 options: 1. Reconfigure router to insert a VLAN tag onto the port interfacing with the Gateway TSS 160/320. 2. Insert another TSS5 between the router and the gateway. The VLNC4x will push a VLAN on the incoming management traffic.
•
One T-MPLS tunnel required per TSS5 shelf. In addition, if protection is required, 1 protection tunnel per TSS5 is required. For inband management of the TSS5s, the network (internal) IP address on the TSS5s must be in the same subnet as the router. The serviceport (external) IP address must be in a different subnet.
•
.................................................................................................................................................................................................................................... 1350 OMS 28-8 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures TSS 5 In Band Management
In-band configuration
....................................................................................................................................................................................................................................
•
•
Inband management of both the VLNC4x and the VLNC6x requires only 1 tunnel. However, 1 pseudo-wire (PW) is required for the VLNC4x and one PW for the VLNC6x. A transit T-MPLS tunnel is required on a node that is not terminating the given tunnel. For instance, tunnel #3 is terminated on TSS5 #3. So TSS5 #1 and TSS5 #2 must have a transit tunnel provisioned to forward the management traffic to TSS5 #3.
Tunnel and Pseudo-Wire Configuration
TSS5 T-MPLS Tunnel and Pseudo-Wire Configuration for Inband Management •
The management tunnel depicted above is a terminated T-MPLS tunnel. The traffic descriptor associated with the management tunnel, should have a CIR=PIR. This value can be increased if necessary. The value for CBS and PBS can be any value.
•
The two tunnels depicted above are for management of both the VLNC4x and the VLNC6x. PW #1 above is the PW for inband management of the VLNC4x. PW #2 above is the PW for inband management of the VLNC6x. Port a-100 is an internal port on the VLNC4x. It is dedicated to inband management. It is used as the UNI port for the PW #1. Port a-100 is used in R7.0.1 and above. In release R7.0.0, the UNI port will be port a-60. Port d2-4 is the backplane port to the VLNC6x. It is the UNI port for the PW #2.
•
Configuration details
Configuration via ZIC •
A management VLAN must be chosen. This management VLAN must be provisioned on each VLNC4x and on each VLNC6x, in every TSS5 shelf: – System -> Configuration -> Service Network –
•
Set Host-id and management VLAN.
For inband management to function for each VLNC4x: – create TUNNEL with the decided label. – create PW with decided label.
.................................................................................................................................................................................................................................... 1350 OMS 28-9 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures TSS 5 In Band Management
In-band configuration
....................................................................................................................................................................................................................................
– –
Apply TD with CIR= 10, PIR= 20, CBS= 15, PBS= 25 to tunnel e PW. Create a null GUA Traffic Descriptor for ETS service.
– •
Create VPWS, set name, set port a-100, associate PW and traffic descriptor created before.(policing mode disable). For inband management to function for each VLNC6x: – Set a VPWS service similar to the prior VPWS changing the port: d2-4.
.................................................................................................................................................................................................................................... 1350 OMS 28-10 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures TSS 5 In Band Management
Resources reservation for In fiber Inband
....................................................................................................................................................................................................................................
Resources reservation for In fiber Inband When to use
The procedure allocate in the PKT all the resources allocated in the NEs for the In fiber InBand management. Related information
For a description of in-band management, refer to “Overview” (p. 28-3). For a network classification of in-band management, refer to“T-MPLS Subnetwork topology” (p. 28-4). For configuration requirements, refer to“Configuration Notes” (p. 28-8). For Tunnel and Pseudo-wire settings, refer to“Tunnel and Pseudo-Wire Configuration” (p. 28-9). For a description of configuration steps, refer to“Configuration details” (p. 28-9). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. Procedure
Following steps should be done to execute correctly the Takeover with online command: From MS-GUI main window: ...................................................................................................................................................................................................
1
Search the physical connections setting characteristics. Select Search > physical > physical connections. Select the TSS-320 ->TSS-5 physical connection. Result: Physical connection setting characteristics are shown ...................................................................................................................................................................................................
2
Search the TSS-5 setting characteristics. Select Search > EML > NE. Select the TSS5. Select Search > NE > Show equipment. In the ZIC window of the selected device: Select System > Configuration > Network Connectivity to see VLAN ID, IP address, Management Priority.
.................................................................................................................................................................................................................................... 1350 OMS 28-11 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures TSS 5 In Band Management
Resources reservation for In fiber Inband
....................................................................................................................................................................................................................................
Select System > T-MPLS > Port summary to see information on T-MPLS Ports. Select System > T-MPLS > Tunnel Management > Tunnel summary to view transit/termination tunnel, in/out Labels, L2 Encapsulation profile, PHB profile. Select System > T-MPLS > Quality Of Service to see Traffic Descriptor (CIR, PIR, PBS, CBS). Select System > Quality Of Service > ETS Flow > TD to see Traffic Descriptor of ETS Flow Services. Result: TSS-5 setting characteristics are shown. ...................................................................................................................................................................................................
3
Search the TSS-320 setting characteristics. Select Search > EML > NE. Select the TSS320. Select Search > NE > Show equipment. In the ZIC window of the selected device: Select T-MPLS > Tunnel management, (filtered by), search. In the list, select the Tunnel to see Traffic Descriptor, Label Identifiers. Select T-MPLS > PW management, (filtered by), search. In the list, select the Pseudo Wire to see Traffic Descriptor, Label Identifiers. Select Communication > InFiber In Band Management, (Select Board), search, (Select Port), Details to see VLAN ID label. Result: TSS-320 setting characteristics are shown. ...................................................................................................................................................................................................
4
If not created, Create one or more domains that corresponds to the scenario already acting in field : from the Construction application Select Action > Packet > Costruction > Create Domain.
.................................................................................................................................................................................................................................... 1350 OMS 28-12 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures TSS 5 In Band Management
Resources reservation for In fiber Inband
....................................................................................................................................................................................................................................
Insert the User Label, Domain Type, Bridge Type and STP Type compliant with the attributes already present. Figure 28-2 Create Domain
Result: The list Domain window is shown with new Domain. ...................................................................................................................................................................................................
5
If not created, Define the Network Elements to the PKT environment : from the Construction application. Select Action > Packet > Costruction > Define NE.
.................................................................................................................................................................................................................................... 1350 OMS 28-13 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures TSS 5 In Band Management
Resources reservation for In fiber Inband
....................................................................................................................................................................................................................................
Insert the User Label, Working Mode and STP Type compliant with the attributes already present. Figure 28-3 Define NE
...................................................................................................................................................................................................
6
If not created, Select the Network Elements to be added from the list, click the confirm button. The Defined Network Element List updated. When the NEs are added, assign the resources already present or create them. Select Action > Packet > Costruction > Assign Resources to Domain. Result: The list Network Element window is shown with new NE. ...................................................................................................................................................................................................
7
If the Customer is not created, Select Action > Packet > Services > Create Customer. Insert the informations compliant with the attributes already present.
.................................................................................................................................................................................................................................... 1350 OMS 28-14 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures TSS 5 In Band Management
Resources reservation for In fiber Inband
....................................................................................................................................................................................................................................
Result: The Customer list is shown with new elements. ...................................................................................................................................................................................................
8
Create Traffic Descriptor that corresponds to the scenario already acting in field : Select Action > Packet > Services > Create Traffic Descriptor. ...................................................................................................................................................................................................
9
Create Traffic Classifier that corresponds to the scenario already acting in field : Select Action > Packet > Services > Create Traffic Classifier. ...................................................................................................................................................................................................
10
Create the Tunnel that corresponds to the scenario already acting in field : Select Action > Packet > T-MPLS > Create T-MPLS Tunnel. Insert the parameters compliant with the attributes already present. Note: For the general settings, refer to “T-MPLS tunnel create” (p. 17-14). Result: The tunnel list window is shown with new object. ...................................................................................................................................................................................................
11
Create the PseudoWire that corresponds to the scenario already acting in field : Select Action > Packet > T-MPLS > Create T-MPLS Pseudo Wire. Insert the parameters compliant with the attributes already present. Note: For the general settings, refer to “ T-MPLS-Create PW” (p. 17-21). Result: The PW list window is shown with new object. ...................................................................................................................................................................................................
12
Create one or more EVC (with the Service in automatic mode) that corresponds to the scenario already acting in field : Select Action > Packet > Services > T-MPLS > Create T-MPLS EVC. Insert the parameters compliant with the attributes already present. Insert VLAN ID reserved for the management of the NE (Standard value is 4094). Insert Service Type EVPLAN. Note: For the general settings, refer to “Create EVC over T-MPLS EVPLAN” (p. 17-72). Result: The list EVC window is shown with new EVC. ...................................................................................................................................................................................................
13
Allocate the object related to the in band management. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 28-15 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures
Abbreviations
....................................................................................................................................................................................................................................
Ethernet Linear Protection Overview Purpose
ELP is a VLAN-based Ethernet Linear Protection based on ITU-T G.8031/Y.1342 (Ethernet Protection Switching). Contents Link Over EVC
28-18
Link over EVC: unlock EVC
28-20
Link over EVC creation
28-22
Link over EVC deletion
28-24
Link over EVC: Alarms
28-25
Link over EVC: OAM
28-26
Link over EVC: assign and deassign
28-27
Link over EVC: Transport Link configuration
28-28
Link over EVC: activation and deactivation
28-29
Link over EVC: Usage within an EVC
28-30
Link over EVC: AAR
28-31
Link over EVC: Routing Display
28-32
Link over EVC: Inventory
28-33
Ethernet Linear Protection (ELP)
28-34
Add protection to PB EVC
28-39
Remove protection from EVC
28-41
Configure protection
28-42
ELP Protection properties
28-43
Description of the properties
28-44
Send APS command to protection group
28-45
Manual alignment of protection group
28-47
Implement a protected EVC
28-48
Deimplement a protected EVC
28-49
Disabled operations
28-50
Alarm propagation for protected EVCs
28-51
OAM on protected EVC
28-52
.................................................................................................................................................................................................................................... 1350 OMS 28-16 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Overview
....................................................................................................................................................................................................................................
Inventory of Transport Link from protected EVC
28-54
Inventory of MA from protected EVC
28-55
Routing Display of protected EVC
28-56
.................................................................................................................................................................................................................................... 1350 OMS 28-17 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Link Over EVC
....................................................................................................................................................................................................................................
Link Over EVC Description
Link over EVC is lets a higher layer to use an EVC as an infrastructure. In case of a single domain, Link over EVC is permit to manage scenarios otherwise handled through E2E. One EVC plus two Transport Links makes a Link over EVC Since more than one EVC can coexist over the same Edge Port, the same Transport Link can be used to form multiple Link over EVCs. Edge Port is the extremity of one of the interworking links added to the EVC to obtain the Link over EVC. Only the case of Link over EVC built over T-MPLS EVCs and assigned to Provider Bridge domain is considered here. Once an EVC has been used to form a Link over EVC, it is locked and can't be modified. It is marked “for infrastructure” The created Link over EVC is visible in its own list in construction and can be used, for the most part, as a normal link and assigned to a Domain in which it will be used to build EVCs. Involved objects
A Link over EVC is composed by an EVC and two interworking links are required. The system checks that: • • • • • •
the EVC is not used to form another Link over EVC there exist two Transport Links that are connected to the two extremities of the EVC the two Transport Links have the same Technology. The technology can be either SDH, Cable, VCG LAG or LAG in case of Transport Links with SDH or VCG LAG Technology, both links have the same Protocol Type (either GFP, LAPS or HDLC); both links are bi-directional (no unidirectional links allowed) the extremities of the two links that are not UNI for the EVC (the extremities are not extremities of the Link over EVC): the extremities: – they are not assigned to any domain – they are not both belonging to ENEs (at most one extremity of the Link over EVC may belong to an ENE)
Bandwidth usage
The bandwidth used on the lower layer EVCs is allocated on the ports where they have their termination, i.e. the internal ports of the interworking links. .................................................................................................................................................................................................................................... 1350 OMS 28-18 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Link Over EVC
....................................................................................................................................................................................................................................
On the external ports of the interworking links, only the bandwidth of the created Links over EVC is allocated (in the above figure you can see that of the 3 Mb/s allocated on the internal ports, only 2 Mb/s are allocated on the external ports, because one of the EVCs has not been used to form a Link over EVC). The Link over EVC has its own bandwidth and, on it, it is allocated the bandwidth used by higher layer EVCs that use that Link over EVC. A check of the available bandwidth is performed on the two Transport Links that have been identified during previous checks. Since those Transport Links will be, together with the specified EVC, the infrastructure of the Link over EVC to be created, the bandwidth of the Link over EVC will consume the bandwidth of the Transport Links and, hence, both Transport Links must have enough free bandwidth to host the Link over EVC. Both Transport Links must have a capacity of at least the PIR of the EVC and they must have an available bandwidth of at least the CIR of the EVC. for each Transport Link: •
Egress Shaping Rate of external port >= PIR of EVC
•
Available Bandwidth of external port >= CIR of EVC Note: “external port” is the port of the Transport Link that is not a UNI for the EVC Available Bandwidth = Egress Shaping Rate - sum of CIR .
“sum of CIR” is the sum of the CIR of all the Links over EVC terminated by that port.
.................................................................................................................................................................................................................................... 1350 OMS 28-19 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Link over EVC: unlock EVC
....................................................................................................................................................................................................................................
Link over EVC: unlock EVC When to use
The operator un-marks an EVC as an infrastructure thus preventing it to be used to form a Link over EVC. Related Information
For more information, refer to “Link Over EVC” (p. 28-18). Unlock EVC operation is only provided to work-around rare emergency situations where there exists an EVC that is marked to be used for infrastructure (locked) but it's not used for a Link over EVC and the operator does not want to use it to form a Link over EVC. Lock EVC is not a user operation. It is accomplished when an EVC is used to form a Link over EVC. Lock EVC prevents the following operation on the locked EVC. • •
provisioning state changes (de-implementation) topology changes (add/remove termination, add/remove flow)
• • •
modification (modify EVC, modify Termination, modify Flow) configuration (configure EVC, configure Termination, configure Flow) modification/configuration of any object used by the EVC (configuration of Edge Ports, configuration of Transport Links)
•
join of a E2E EVC
Any operation that does not modify the EVC can be performed on it (list, properties, navigations from/to other objects, etc.). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select a locked EVC. ...................................................................................................................................................................................................
2
Select Action > Un-Lock.
.................................................................................................................................................................................................................................... 1350 OMS 28-20 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Link over EVC: unlock EVC
....................................................................................................................................................................................................................................
Result: The system checks that the EVC is not used to form any Link over EVC and un-marks (unlocks) the EVC.
If the EVC is used in aLink over EVC, the operation is rejected. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 28-21 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Link over EVC creation
....................................................................................................................................................................................................................................
Link over EVC creation When to use
The function creates a Link over EVC. Related Information
For more information, refer to “Link Over EVC” (p. 28-18). To create a Link over EVC, an EVC and two interworking links are required. See “Involved objects” (p. 28-18) A check of the available bandwidth is performed on the two involved Transport Links. Both Transport Links must have a capacity of at least the PIR of the EVC and they must have an available bandwidth of at least the CIR of the EVC. See “Bandwidth usage” (p. 28-18) Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Action > Packet > Construction > Create Link Over EVC. ...................................................................................................................................................................................................
2
The operator specifies: •
EVC
•
userlabel
•
comment (optional) Result: The system locks the EVC as exported for infrastructure.
The system locks the two involved interworking Links. Link over EVC has the following characteristics: • the userlabel provided by the operator •
the commentprovided by the operator
•
the CIR of the specified EVC
.................................................................................................................................................................................................................................... 1350 OMS 28-22 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Link over EVC creation
....................................................................................................................................................................................................................................
• •
the PIR of the specified EVC the extremities of the two interworking Transport Links that are not connected to the two extremities of the EVC
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 28-23 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Link over EVC deletion
....................................................................................................................................................................................................................................
Link over EVC deletion When to use
The function deletes a Link over EVC. Related Information
For more information, refer to “Link Over EVC” (p. 28-18). If not assigned to any Domain, a Link over EVC can be deleted. Link over EVC is not assigned when: • •
if this was the last/only Link over EVC the two interworking Transport Links were part of, the latter are no more locked and can be freely operated the operation of un-export is invoked for the EVC
As result of a deletion, the Link over EVC is decomposed to an EVC and two interworking Links. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select Search > Packet > Construction > Link Over EVC. ...................................................................................................................................................................................................
2
Select a Link over EVC and select Action > Delete. Result: The system un-locks the EVC.
The system un-locks the two involved interworking Links. If the un-export of the EVC fails, the Link over EVC is anyway deleted and an error is reported to the operator, warning him/her that the involved EVC is yet marked and that the should be manually invoked to unmark it. See “Link over EVC: unlock EVC” (p. 28-20) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 28-24 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Link over EVC: Alarms
....................................................................................................................................................................................................................................
Link over EVC: Alarms Alarms on the interworking Transport Links
Alarms on the interworking Transport Links or on the EVC are propagated to the Link over EVC. Alarms on the Link over EVC are propagated normally. The Link over EVC introduces a couple correlation kinds: • •
whenever the EVC is alarmed the Link over EVC is alarmed too whenever one interworking Transport Link is alarmed the Link over EVC is alarmed too
In addition, since the Link over EVC is a link, alarms on it must be propagated to other kinds of link
.................................................................................................................................................................................................................................... 1350 OMS 28-25 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Link over EVC: OAM
....................................................................................................................................................................................................................................
Link over EVC: OAM OAM over link and OAM over EVC
OAM over link has limitations if applied to the Link over EVC. OAM is not allowed OAM on the Link over EVC OAM over EVC is handled normally if applied to an EVC that uses the Link over EVC. On the higher level EVC(s) that use the Link over EVC, no MIPs are create within the Link over EVC (only at its extremity). .The Link over EVC must be considered a link from all points of view.
.................................................................................................................................................................................................................................... 1350 OMS 28-26 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Link over EVC: assign and deassign
....................................................................................................................................................................................................................................
Link over EVC: assign and deassign Assign Link over EVC to Domain
Being the Link over EVC a link from most points of view, it must be possible to assign it to a Domain. The only kind of Domain allowed to accept such a link is Provider Bridge. As for any other link kind, whenever a Link over EVC is assigned to a Domain, the system must check that the extremities of the link reside on two NEs that have a Working Mode compatible with the chosen Domain. The main difference in respect to another link kind is that the first Link over EVC to be assigned to a Domain causes all the other Links over EVC that are made with one or both of its interworking links, to be assigned to the same Domain (this is in order to prevent that the same real port is assigned to two different domains). If, for a mistake of the operator, a Link over EVC "LEVC1" is made by an interworking Transport Link "Link1", that is part of another Link over EVC assigned to Domain "PB1", and by an interworking Transport Link "Link2", that is part of another Link over EVC assigned to Domain "PB2", this means that "LEVC1" can't be assigned to any domain at all. Once a Link over EVC is assigned to a Domain, the usual mechanics of the used bandwidth management apply to its (virtual not real) extremities. Refer to the general function to assign a resource to a domain. Deassign Link over EVC from Domain
If not already used by an EVC, a Link over EVC assigned to a (Provider Bridge) Domain can be de-assigned from it by the operator (as for other kinds of link). To move a Link over EVC from a Domain to another, all the Links over EVC that share with the former at least one interworking Transport Link, needs not to be assigned to any Domain (i.e. any of those Links over EVC must be de-assigned from the Domain it belongs to). The procedure to move a Link over EVC from a Domain to another is: 1. De-assign the Link over EVC (LOE1) from its Domain (DOM1) 2. De-assign from DOM1 any Link over EVC sharing at least one interworking Transport Link with LOE1. Any Link over EVC that shares an interworking TL with LOE1 either is assigned to DOM1 or not assigned to any Domain. 3. Assign LOE1 to the new Domain (DOM2) Refer to the general function to deassign a resource from a domain.
.................................................................................................................................................................................................................................... 1350 OMS 28-27 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Link over EVC: Transport Link configuration
....................................................................................................................................................................................................................................
Link over EVC: Transport Link configuration Limitations
The configuration of the extremities of the Link over EVC, from a bridge perspective, is subject to limitations in its applicability. The Link over EVC extremities are not real interfaces in the NE, rather they are virtual ports internally created by PKT. This means, among other things, that when the operator requests the configuration of a Link over EVC, he is warned by the system that the configuration will affect all the Links over EVC that shares the same interworking Transport Links. In addition, the system will prevent the operator to configure a Link over EVC if it shares only one interworking Transport Link with another Link over EVC (because this would cause the other Link over EVC to have its extremities misaligned). From a bridge perspective, it is possible to configure only the extremities of a Link over EVC, also because the interworking links which make part of it do not belong to any bridge Domain (hence they could not be configured in a bridge perspective) and, in addition, have two extremities that have different Client Types. As for other bridge Transport Links the configurable attributes are: • • •
Acceptable Frame Type P-VID Ingress Filtering
• • • •
VLAN Type Default User Priority Priority Bit Mapping PCP
Refer to the general function to configure a transport link.
.................................................................................................................................................................................................................................... 1350 OMS 28-28 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Link over EVC: activation and deactivation
....................................................................................................................................................................................................................................
Link over EVC: activation and deactivation The activation of the extremities
The activation of the extremities of the Link over EVC is subject to limitations in its applicability. The Link over EVC extremities are not real interfaces in the NE, rather they are virtual ports internally created by PKT. This means that when the operator requests the activation of a Link over EVC, he is warned by the system that the activation will affect all the Links over EVC that shares the same interworking Transport Links. If the activation is in the scope of the implementation of an EVC that uses the Link over EVC, the operator is not warned. The deactivation of the extremities
The deactivation of the extremities of the Link over EVC is subject to limitations in its applicability. The Link over EVC extremities are not real interfaces in the NE, rather they are virtual ports internally created by PKT. This means, among other things, that when the operator requests the deactivation of a Link over EVC, he is warned by the system that the deactivation will affect all the Links over EVC that shares the same interworking Transport Links. If the deactivation is in the scope of the de-implementation of an EVC that uses the Link over EVC, the operation is not performed at all if there's another Link over EVC with the same interworking Transport Links and that is used by an EVC that is at least partially implemented.
.................................................................................................................................................................................................................................... 1350 OMS 28-29 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Link over EVC: Usage within an EVC
....................................................................................................................................................................................................................................
Link over EVC: Usage within an EVC Work around
There are limitations to be worked around in order to make correctly interact the Link over EVC with STP. The capability of the Link over EVC to correctly interact with (i.e. let pass through) the BPDU of the xSTP protocol used by the higher level EVC, depends on how the underlying EVC is made. • •
capability of the inner EVC to encapsulate the BPDU and transport them; frames allowed to transit into the inner EVC.
A T-MPLS EVC complies with 1), but the compliancy with 2) depends on the TCs present in the EVC Terminations of the inner EVC. This means, for example, that an EVC with a set of TCs that makes only pass frames with VIDs in the range 10-100, will never be able to make STP/RSTP BPDUs to pass (they are untagged...). In this case the operator can approach this problem in different ways: • •
use the Link over EVC only in domains with STP Type = None/Disabled; configure the extremities of the Link over EVC to have Forced Port State = Forwarding;
• •
have the Link over EVC accept any kind of frame (Default TC = Don't Care); create a second Link over EVC used only for BPDU to pass.
.................................................................................................................................................................................................................................... 1350 OMS 28-30 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Link over EVC: AAR
....................................................................................................................................................................................................................................
Link over EVC: AAR AAR
The Link over EVC extremities are not real interfaces in the NE, rather they are virtual ports internally created by PKT. For this reason, in the scope of AAR, they are not considered at all. This means that AAR will be performed, instead, on the real ports that support the virtual extremities.
.................................................................................................................................................................................................................................... 1350 OMS 28-31 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Link over EVC: Routing Display
....................................................................................................................................................................................................................................
Link over EVC: Routing Display Routing Display
The routing display of the Link over EVC shows its components (interworking TLs + EVC) The routing display of the Link over EVC shows its three components, i.e. the two interworking Transport Links and the EVC. It is possible to navigate from the EVC to the routing display of the EVC itself.
.................................................................................................................................................................................................................................... 1350 OMS 28-32 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Link over EVC: Inventory
....................................................................................................................................................................................................................................
Link over EVC: Inventory EVC to Link over EVC
Starting from an EVC marked "for infrastructure" navigates to the Link over EVC built on it. Link over EVC to EVC
Starting from a Link over EVC navigates to the EVC marked "for infrastructure" that makes part of it. Link over EVC to Transport Link
Starting from a Link over EVC shows the list of Transport Links that support it. The list shows two Transport Links. Transport Link to Link over EVC
Starting from a Transport Link shows the list of Links over EVC that are supported by it.
.................................................................................................................................................................................................................................... 1350 OMS 28-33 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Ethernet Linear Protection (ELP)
....................................................................................................................................................................................................................................
Ethernet Linear Protection (ELP) Description
TSS-3 R2.2 introduces a VLAN-based Ethernet Linear Protection based on ITU-T G.8031/Y.1342 (Ethernet Protection Switching). Albeit the ITU standard foresees a number of different protection schemes, PKT is going to support only bidirectional 1:1 linear protection (the only one supported by TSS-3). Ethernet Linear Protection (ELP) applies to Virtual Bridge and Provider Bridge EVCs. This specification is going to focus on the Provider Bridge case (even if most of what is said is applicable to the Virtual Bridge case too). The protection is “linear” and, hence, only applies to “linear” connectivity, i.e. EVCs with a linear route. In short, ELP aims to provide an alternative route to the traffic of an EVC, so that, if there's a failure on the main route, the traffic is switched on the other route quickly and with minimal impacts. In order to achieve this, the following elements are needed: • • •
a linear connectivity to protect (i.e. a Virtual or Provider Bridge EVC); an alternate route; one MA running on the route to protect (using Down MEPs, of course);
• •
one MA running on the alternate route (using Down MEPs, of course); a Protection Group that associates the main and the alternate route and that manages the protection switch.
Whenever on the main route there's a failure that prevents traffic, the failure is detected by OAM CC and the Protection Group performs the switch on the alternate route. Independently from the protection, the EVC as a whole can be monitored by an OAM CC through a MA. ITU-T G.8031/Y.1342 is a VLAN based protection, this means that what is protected is the VLAN used as a transport for the frames (i.e. the S-VID in the Provider Bridge case). The EVC to protect has it's S-VID distributed over its data plane, in addition, the alternate route must have the protecting S-VID distributed all over the ports that belongs to it. The protecting S-VID can be the same S-VID of the EVC or a different one depending on what supported by the involved NEs (e.g. TSS-3 R2.2 only supports different VIDs). Since STP and EPL conflicts, when EPL is used no STI must be running on the involved ports. This means either that STP is disabled on the involved NEs (STP Type = None/Disabled) or that STP Force Port State is "Forwarding" for the involved ports. As a consequence, the routes of the involved EVC must be fully linear, with no cycles, nor branches inside (otherwise, without STP, traffic would multiply until fully fill the transport links capacity). .................................................................................................................................................................................................................................... 1350 OMS 28-34 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Ethernet Linear Protection (ELP)
....................................................................................................................................................................................................................................
This specification has been developed with in mind the T-MPLS protection (tunnel protection). Since the differences of the two cases (the EVC is an object conceptually very different than the Tunnel), it has not always been possible to stick to the same approach. Even if it could already be obvious (or it will be obvious in the following), it's worth to specify now that ELP only applies to EVCs with VLAN Distribution = Not Full Meshed. The T-MPLS approach: why we can't follow it completely
In the T-MPLS approach, when we have a Tunnel to protect, we are able to create another Tunnel and associate the two under a Protection Group, so that the first Tunnel is the working one and the second Tunnel is the protecting one. As a first try, an identical approach based on having a working EVC and a protecting EVC was firstly analyzed and, after some reasoning, discarded because, in reality, the "protecting EVC" is not an EVC at all (it has no EVC Terminations), but simply an alternate route, a protecting data plane. We discovered that modeling the alternate route as an EVC (which isn't) brings a lot of conceptual and practical problems that made us discard it. The proper way to model a protected EVC is to have one EVC and two data planes: We found a couple of approaches to achieve this kind of model. Link over EVC and Protecting Data Plane
The approach hereby described consists in having the direct creation of the data plane (that in the case of EVC Fragment is not a big issue) while removing the need for E2E (so that we can safely ignore the E2E issues we would have with this approach). We need two things: • •
1. direct creation of protecting data plane within the Add Protection operation; 2. link over EVC.
Direct creation of protecting data plane
A new operation "Add Protection" is available to the operator that, through it, is able to add a "Protecting Data Plane" to an existing EVC. The Protecting Data Plane is specified in Add Protection by passing a number of Transport Links and, optionally, one or two E-NNI port(s). Even if the Protection Group must be provisioned to the involved NEs, it's not needed to make it a distinct object at PKT level: it could just be a set of properties that are visible/enabled when the EVC is under protection. Link over EVC over T-MPLS
This feature is already described by its own set of RATS.
.................................................................................................................................................................................................................................... 1350 OMS 28-35 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Ethernet Linear Protection (ELP)
....................................................................................................................................................................................................................................
Pros and cons
Pros: •
there exist only a single EVC with two data planes;
•
there is clear distinction between the working route, the protecting route and the protected EVC; alarm correlation works on a single EVC (it could be feasible to allow alarm correlation only if the EVC is under OAM CC); only one domain in most cases -> no E2E
• • •
in case of single link EVC, an even simpler procedure (and with minimal development effort) could be used
Cons: •
• • •
a new entity is introduced (even if it's only a "sub object" of the EVC) and operations are needed to manage it, alternatively, if few operations are provided to the operator to manage it, it will be difficult for him to handle this kind of object; effort to realize Link over EVC impacts caused by Link over EVC this approach was designed to avoid E2E, if E2E is needed despite the link over EVC, creating a Protecting Data Plane for an E2E EVC can be not trivial for the operator and difficult to understand/manage (it seems also a problem from the development point of view)
EVC attributes to support ELP
New attributes are added to the EVC in order to support ELP. These new attributes are meaningful only for protected EVCs. Notice that, while Protection is always meaningful, when Protection is no all the other attributes are not meaningful. Table 28-1
EVC attributes for ELP
Attribute name
Attribute type
Default
Master
Protection
{yes, no}
no
PKT
NE object name (SNMP)
Whether the EVC is protected or not Revertive
{yes, no}
yes
PKT
opticsIMEthLinearPGType
Whether traffic switches back after recovery of working resource
.................................................................................................................................................................................................................................... 1350 OMS 28-36 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Ethernet Linear Protection (ELP)
....................................................................................................................................................................................................................................
Table 28-1
EVC attributes for ELP
(continued)
Attribute name
Attribute type
Default
Master
NE object name (SNMP)
Revert time
0, ..., 12 min
5 min
PKT
opticsIMEthLinearPGWTR
Time before switching back (meaningful only in case of revertive protection) Holdoff time
0, 100, 200 … 10000 ms
0 ms
PKT
opticsIMEthLinearPGHoldoff
working
NE
opticsIMEthLinearPGProtectingActive
Hold off time before switching Active
{working, protecting}
Current switch position (i.e. which data plane is carrying traffic) Current request
{No Request (Working Active), No Request (Protection Active), Lockout, Forced Switch, Signal Fail - W, Signal Fail - P, Manual Switch (Protection/Active), Wait-to-Restore, Do-not-Revert, FOP, Manual Switch (Working Active), Exercise (Working Active), Exercise (Protection Active), Reverse Request (Working Active), Reverse Request (Protection Active)}
No Request (Working Active)
NE
opticsIMEthLinearPGProtectionstatus
Last APS command executed for the protection group Pending request
{none, Pending Signal Fail}
none
NE
opticsIMEthLinearPGPendingRequest
The pending APS command that will executed when current request clears (i.e. it tells whether there's a lower priority automatic switch request blocked by a higher priority manual request) APS Priority
0, ..., 7
7
PKT
opticsIMEthLinearPGAPSPriority
Priority of ethernet frames with ETH-APS information (default value (7) is the highest priority)
.................................................................................................................................................................................................................................... 1350 OMS 28-37 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Ethernet Linear Protection (ELP)
....................................................................................................................................................................................................................................
Protect an EVC
Protection is applied to an EVC under the following conditions: •
the EVC has VLAN Distribution = Not Full Meshed;
• • •
the EVC is not already protected; the values specified for the attributes of the protection are valid; the S-VID for the Protecting Data Plane is different than the S-VID of the EVC;
•
the EVC is “linear”. the EVC is “linear” when (the following conditions imply that the EVC is at least allocated): –
•
• •
it has its EVC Terminations in exactly two NEs (i.e. it has at least two EVC Terminations in two different NEs, but there can be more than two EVC Terminations as long as the involved NEs are no more than two); – it has a data plane (which is going to become the Working Data Plane) that is “linear”, i.e. it's and end-to-end chain of Transport Links from an extremity NE (i.e. a NE where an EVC Termination is) to the other; the specified Protecting Data Plane is “linear” and has the same extremities of the Working Data Plane, i.e. it's and end-to-end chain of Transport Links from an extremity NE (i.e. a NE where an EVC Termination is) to the other; the involved Domain has STP Type = None/Disabled or all the involved ports have Forced Port State = Forwarding; the NEs at the extremities support Ethernet Linear Protection.
Unprotect an EVC
The system does the following: •
if the EVC is Implemented or Partially Implemented, un-provisions the protection from the involved NEs: – – – –
•
un-provisions the Protection Group; un-provisions the two involved MAs; un-provisions the Protecting Data Plane; any failure during this phase ends the procedure leaving the EVC with Provisioning State = Partially Implemented and Protection = Yes
if the un-provisioning has been successful or if the EVC is Allocated: – removes the Protection Group; – removes the two involved MAs; – –
removes the Protecting Data Plane; any failure during this phase causes a rollback and exits with the EVC in the same state it was before this phase.
.................................................................................................................................................................................................................................... 1350 OMS 28-38 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Add protection to PB EVC
....................................................................................................................................................................................................................................
Add protection to PB EVC When to use
The operator is able to turn an unprotected EVC into a protected one. Related Information
The operator is able to turn an existing unprotected EVC into a protected one, by specifying the S-VLAN to be used for the protection and the route of the protection. The "Add protection" command is only enabled/visible for those EVCs with Protection = no. For more information, refer to “Ethernet Linear Protection (ELP)” (p. 28-34). For more information, refer to “Protect an EVC” (p. 28-38). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select a S-VID for the Protecting Data Plane. ...................................................................................................................................................................................................
2
Select the route of the Protecting Data Plane as a list of Transport Links. ...................................................................................................................................................................................................
3
(see “EVC attributes to support ELP” (p. 28-36) for ELP attributes of the EVC, for the meaning of each attribute, the allowed values and the default values) Select the attributes of the protection •
Revertive
• • •
Revert time (meaningful only if Revertive is "yes") Hold-off time APS priority
.................................................................................................................................................................................................................................... 1350 OMS 28-39 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Add protection to PB EVC
....................................................................................................................................................................................................................................
Result: Once all the checks are passed: the protection is added to the EVC only in the PKT DB.
• •
the Protecting Data Plane is added to the EVC; two MAs are created, one for each data plane, with each MA having two Down MEPs (one Down MEP for each extremity of the associated data plane);
• –
a Protection Group is created with two Protection Units: the one with Working Role associated to the Working Data Plane and to the Working MA; the one with Protecting Role associated to the Protecting Data Plane and to the Protecting MA;
– • •
the EVC's Protection attribute is set to "yes"; if anything goes wrong during this phase, a rollback is done and the state of the EVC remains unchanged;
if the EVC is Implemented the protection is provisioned to the involved NEs: • the Protecting Data Plane is provisioned; • • •
the two MAs are provisioned and OAM CC is enabled on them; the Protectiong Group is provisioned; if at any step there's a failure the EVC becomes Partially Implemented and the procedure ends.
if the STP Type of the Domain is not None/Disabled, all the ports in the data planes of the EVC have their Forced Port State locked on Forwarding (i.e. that attribute can't be configured for those ports). In the above procedure, any failure during the provisioning of any element needed for the protection (Protecting Data Plane, OAM objects, Protection Group) causes the EVC to become Partially Implemented and stops the procedure but always exits with a protected EVC (although not fully implemented in some cases) . ,whenever a failure occurs during the provisioning phase, at the end the EVC is Partially Implemented and has Protection = yes. ...................................................................................................................................................................................................
4
If, after an Add Protection, an EVC that initially was Implemented becomes Partially Implemented, the operator can recover the situation in one of these three ways: • •
•
de-implement the EVC and obtain an allocated protected EVC (then it's possible to continue by re-trying the implementation of the EVC or removing the protection); remove the protection from the EVC, thus obtaining (in case of success) an implemented unprotected EVC (if successful the EVC could yet remain in Partially Implemented state and it could be necessary to implement it to update its Provisioning State); implement the EVC, thus obtaining (in case of success) an implemented protected EVC.
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 28-40 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Remove protection from EVC
....................................................................................................................................................................................................................................
Remove protection from EVC When to use
The operator is able to turn a protected EVC into an unprotected one. Related Information
The operator specifies the protected EVC from which the protection must be removed. The "Removed protection" command is only enabled/visible for those EVCs with Protection = yes. For more information, refer to “Ethernet Linear Protection (ELP)” (p. 28-34). For more information, refer to “Unprotect an EVC” (p. 28-38). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
List the EVC ...................................................................................................................................................................................................
2
Select the protected EVC, select Remove protection E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 28-41 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Configure protection
....................................................................................................................................................................................................................................
Configure protection When to use
This function configures the attributes of the Protection Group. Related Information
For more information, refer to “Ethernet Linear Protection (ELP)” (p. 28-34). For more information, refer to “EVC attributes to support ELP” (p. 28-36). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select a Protected EVC. ...................................................................................................................................................................................................
2
(see “EVC attributes to support ELP” (p. 28-36) for ELP attributes of the EVC, for the meaning of each attribute, the allowed values and the default values) Modify the attributes of the protection: • • •
Revertive Revert time (meaningful only if Revertive is "yes") Hold-off time
•
APS priority Result: Attributes are modified.
E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 28-42 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
ELP Protection properties
....................................................................................................................................................................................................................................
ELP Protection properties When to use
The protection-specific attributes of the EVC are shown in a dedicate tab of the properties window. Related Information
For more information, refer to “Ethernet Linear Protection (ELP)” (p. 28-34). For more information, refer to “EVC attributes to support ELP” (p. 28-36). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select a Protected EVC. ...................................................................................................................................................................................................
2
Select one item in the list. Select Search > Properties. Result: The Property window is displayed.
See the following topic in this document: “Description of the properties” (p. 28-44) E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 28-43 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Description of the properties
....................................................................................................................................................................................................................................
Description of the properties Attributes specific for ELP
The attributes displayed are: •
Protection (no, yes).Whether the EVC is protected or not
•
Revertive (yes, no).Whether traffic switches back after recovery of working resource.
•
Revert time (from 0 to 12 min; default: 5).Time before switching back (meaningful
• • •
• •
only in case of revertive protection) Hold-off time (0, 100, 200 … 10000 ms; default: 0). Hold off time before switching Active (working, protecting).Current switch position (i.e. which data plane is carrying traffic) Current request (No Request (Working Active), No Request (Protection Active), Lockout, Forced Switch, Signal Fail - W, Signal Fail - P, Manual Switch (Protection/Active), Wait-to-Restore, Do-not-Revert, FOP, Manual Switch (Working Active), Exercise (Working Active), Exercise (Protection Active), Reverse Request (Working Active), Reverse Request (Protection Active)). Last APS command executed for the protection group Pending request (none, Pending, Signal Fail). APS Priority (from 0 to 7; default: 7). Priority of ethernet frames with ETH-APS
information.
.................................................................................................................................................................................................................................... 1350 OMS 28-44 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Send APS command to protection group
....................................................................................................................................................................................................................................
Send APS command to protection group When to use
The operator is able to send APS commands to the NE. Related Information
The operator is able to send APS commands to the NE, so to affect the selection of the active data plane. For more information, refer to “Ethernet Linear Protection (ELP)” (p. 28-34). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select a Protected and Implemented EVC. ...................................................................................................................................................................................................
2
Select the send APS command. Chose one of the following commands: •
Clear (default value); to clear any initiated command
•
Lockout of Protection (LO); to fix the selector position to the working connection
•
Forced Switch (FS); for working connection: switches the selector from the working
•
•
•
connection to the protection connection (unless a higher priority switch request (i.e., LO) is in effect) Manual Switch (MS); for working connection: switches the selector from the working connection to the protection connection (unless an equal or higher priority switch request (i.e., LO, FS, SF or MS) is in effect) Manual Switch (MS-W); for protection connection: switches the selector from the protection connection to the working connection (unless an equal or higher priority switch request (i.e., LO, FS, SF, MS, MS-W) is in effect); Exercise (EXER); tests if the APS communication is operating correctly, and does not modify the selector Note: Freeze, Clear Freeze, Lockout and Clear Lockout have been excluded because not supported by our NEs.
.................................................................................................................................................................................................................................... 1350 OMS 28-45 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Send APS command to protection group
....................................................................................................................................................................................................................................
Result: The system checks that the specified EVC is protected and implemented and then sends the command to one of the two NEs at the extremities of the EVC. If one of the two NEs is an ENE, the provisioning is mandatory in the other NE. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 28-46 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Manual alignment of protection group
....................................................................................................................................................................................................................................
Manual alignment of protection group When to use
The operator is able to manually align the NE mastered attributed of the Protection Group/Protection Units. Related Information
An alignment operation is available to the operator to manually align the NE mastered attributed of the Protection Group/Protection Units. Manual alignment is useful in case automatic alignment fails for various reasons (NE isolation, crash of EoT BB or Adaptation BB, etc.). For more information, refer to “Ethernet Linear Protection (ELP)” (p. 28-34). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select a Protected and Implemented EVC. ...................................................................................................................................................................................................
2
Select the Switch command synchronization command. Result: The system uploads the PG/PUs attributes from one of the involved NEs and
refreshes the GUI. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 28-47 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Implement a protected EVC
....................................................................................................................................................................................................................................
Implement a protected EVC When to use
The operator is able to implement a protected EVC. Related Information
The implementation of a protected EVC, in addition to what is done for un-protected EVCs, involves the provisioning of the protecting Data Plane, the two MAs for the working and protecting Data Planes and the provisioning of the Protection Group. For more information, refer to “Ethernet Linear Protection (ELP)” (p. 28-34). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select a Protected EVC. ...................................................................................................................................................................................................
2
Select the Implement command. Result: The EVC is in implemented state. E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 28-48 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Deimplement a protected EVC
....................................................................................................................................................................................................................................
Deimplement a protected EVC When to use
The operator is able to deimplement a protected EVC. Related Information
The de-implementation of a protected EVC, in addition to what is done for un-protected EVCs, involves the un-provisioning of the Protection Group, of the two MAs for the working and protecting Data Planes and of the protecting Data Plane. For more information, refer to “Ethernet Linear Protection (ELP)” (p. 28-34). Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select a Protected and Implemented EVC. ...................................................................................................................................................................................................
2
Select the Deimplement command. Result: The EVC is in allocated state . E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 28-49 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Disabled operations
....................................................................................................................................................................................................................................
Disabled operations Deallocation is disabled
A Provider Bridge EVC can be protected only when at least allocated, hence de-allocation is disabled. To enable de-allocation is necessary to remove the protection from the EVC. Change topology is disabled
A protected Provider Bridge EVC has its topology locked so any operation that changes the topology is disabled. The following operations are not allowed for a protected EVC: • •
add termination remove termination
• • • •
add transport link remove transport link add flow remove flow
NNIs is Locked
The NNIs that are referred by a Protection Group (i.e. the extremities of the working and protecting data planes) can't be configured or they could have different configuration and that's not allowed. For each protected EVC there exist four NNIs that are the extremities of its two Data Planes (two NNIs for the working Data Plane and two NNIs for the protecting Data Plane), in order for the protection to work properly the working NNI and the protecting NNI that are in the same NE must have the same configuration. This means, among other things, that when an EVC is protected the NNIs at the extremities of its Data Planes can't be configured anymore by the operator (they are locked). any explicit configuration operation on those ports is refused by the system.
.................................................................................................................................................................................................................................... 1350 OMS 28-50 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Alarm propagation for protected EVCs
....................................................................................................................................................................................................................................
Alarm propagation for protected EVCs Propagation from Transport Link to EVC
At the moment, in the scope of bridge EVCs, there's no propagation at all of alarms from Transport Link to EVC. This is due to the fact that a failure on a single Transport Link in a connectionless scenario does not mean, in general, any failure for the supported EVC(s). The case of the protected EVC is different: there are two linear routes and this means that if two links on the two routes stop working, the EVC is alarmed. This kind of correlation/propagation could be done by PFM BB basing on the currently active route. Anyway, in order to simplify the management of alarms it has been decided to not implement this kind of correlation and, instead, leave this task to the OAM on the EVC. In other words, if the operator wants to know whether the EVC is working or not, he will have to activate the OAM CC on it and watch OAM alarms.
.................................................................................................................................................................................................................................... 1350 OMS 28-51 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
OAM on protected EVC
....................................................................................................................................................................................................................................
OAM on protected EVC OAM for data planes
In order for ELP to work, there's the need of a MA for each Data Plane. This means that a new kind of MA is introduced: after the MA for EVC, the MA for Edge Port and the MA for Transport Link we have the MA for Data Plane. OAM on protected EVC
The EVC has two VIDs : the VID of the protected route/data plane (i.e. the original S-VID) and the VID of the protection. If the protection route is active the NEs at the extremity of the EVC take care to "convert" the OAM packets, that originally were created for the S-VID, so to work with the protection VID. The internal NEs of the protection route are not even aware of the protection and, in order to make OAM work, must have a MA with protection S-VID. The operator must be aware of the protection when operating the OAM over the protected EVC. For example, when the operator requests an OAM LB specifying the MAC address of a MIP, he/she must be aware of the currently active route and know that if a MIP on the other route will be chosen, the loopback will fail for sure. Analogously, in the case of OAM LT, the operator must be aware of the protection in order to correctly interpret the results of the link trace. Performance Monitoring
PM on protected EVC has no impacts at all for what concerns ELP Audit
The new items with protected EVCs are: • •
protected Data Plane Data Plane MAs
•
Protection Group
First two items must be handled by PKT at high level (toward the operator and internally within the DB) but the related NE elementary objects (VLAN member sets, MDs, MAs, MEPs) are already managed by PKT. This means that no new management is needed for these objects on the AAR side In the audit results we will only see the Protection Group entity that, will encompass attributes of both the Protection Group and the Protection Unit.
.................................................................................................................................................................................................................................... 1350 OMS 28-52 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
OAM on protected EVC
....................................................................................................................................................................................................................................
Force align down
The Protection Group, introduced for ELP, needs to be part of all the AAR procedures. The provisioning sequence for the ELP is: 1. VLAN Member set on Data Plane 2. Data Plane MAs and MEPs 3. Protection Group + Protection Units This order is fixed both for provisioning and for un-provisioning . Reservation and take-over
The Protection Group and Protection Unit information are saved during reservation to be used during the take-over. For the operator, operations are identical to the ones done in the un-protected case.
.................................................................................................................................................................................................................................... 1350 OMS 28-53 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Inventory of Transport Link from protected EVC
....................................................................................................................................................................................................................................
Inventory of Transport Link from protected EVC When to use
This command shows the list of Transport Links of the Working Data Plane or of the Protecting Data Plane. Related Information
For a protected PB EVC the Search > Transport Links contextual menu is replaced by two menu items: • •
Working Data Plane Transport Links Protecting Data Plane Transport Links
Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select a Protected EVC. ...................................................................................................................................................................................................
2
Select the Search command. Result: The following sub menu are shown:
•
Working Data Plane Transport Links
•
Protecting Data Plane Transport Links
...................................................................................................................................................................................................
3
Select the desired data plane. Result: The list shows the Transport Links belonging to the selected Data Plane E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 28-54 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Inventory of MA from protected EVC
....................................................................................................................................................................................................................................
Inventory of MA from protected EVC When to use
This command shows the list of MA of the Working Data Plane or of the Protecting Data Plane. Related Information
From a protected EVC the operator can navigate to the MA associated to its Working Data Plane or its Protecting Data Plane. Before you begin
The system is running. The system is properly configured. The system is connected by MS-GUI. The MS-GUI is set to map mode. Task
From the MS-GUI Main menu: ...................................................................................................................................................................................................
1
Select a Protected EVC. ...................................................................................................................................................................................................
2
Select the Search command. Result: The following sub menu are shown:
•
Working Data Plane MA
•
Protecting Data Plane MA
...................................................................................................................................................................................................
3
Select the desired data plane. Result: The list shows the MA belonging to the selected Data Plane E................................................................................................................................................................................................... N D O F S T E P S
.................................................................................................................................................................................................................................... 1350 OMS 28-55 8DG42227DAAA 9.6 Issue 3 December 2012
Enhanced Procedures Ethernet Linear Protection
Routing Display of protected EVC
....................................................................................................................................................................................................................................
Routing Display of protected EVC Routing Display request
The Routing Display command shows both the route of the Working Data Plane and of the Protecting Data Plane. The operator is able to understand which is the working Data Plane and which is the protecting Data Plane. Any additional action from the operator is required.
.................................................................................................................................................................................................................................... 1350 OMS 28-56 8DG42227DAAA 9.6 Issue 3 December 2012
Appendix A: Use script changeNeShOperatorLabel.sh
Use the script changeNeShOperatorLabel.sh to change NEShOperator When to use
The script changeNeShOperatorLabel.sh allows to change the NEShOperator label in PKT Related Information
This task does not have any related information. Before you begin
This task does not have any preconditions. Task ...................................................................................................................................................................................................
1
Login as bmml user into the system. ...................................................................................................................................................................................................
2
Set to the correct directory: cd /usr/Systems/PKT__/databases/dbbmml/admin/create ...................................................................................................................................................................................................
3
Run the script: $ ./changeNeShOperatorLabel.sh ...................................................................................................................................................................................................
4
Verify that the migration of the data has been correctly executed checking the file changeNeShOperatorLabel.lst.
................................................................................................................................................................................................................................... 1350 OMS A-1 8DG42227DAAA 9.6 Issue 3 December 2012
Use script changeNeShOperatorLabel.sh
Use the script changeNeShOperatorLabel.sh to change NEShOperator
.................................................................................................................................................................................................................................... ...................................................................................................................................................................................................
5
Remove the files: changeNeShOperatorLabel.lst and changeNeShOperatorLabel.sql E................................................................................................................................................................................................... N D O F S T E P S
Where Variable
Description
BM Id
is the 1354BMETH instance identification number
BM version
is the 1354BMETH version
old_shOperatorLabel
userlabel to be modified
new_shOperatorLabel
new value of the userlabel
.................................................................................................................................................................................................................................... 1350 OMS A-2 8DG42227DAAA 9.6 Issue 3 December 2012
Appendix B: Application Limits
Limits Overview
This appendix provides a reminder of every limits and constraints that are managed by the 1350 OMS PKT application. Table B-1
Limits for Subnetworks
Maximum number of subnetworks
500
Maximum number of subnetwork levels
4
Maximum number of NEs or ENEs in one subnetwork
60
Maximum number of subnetworks in one subnetwork
250
Table B-2
Limits for Service Nodes
Maximum number of service nodes
Table B-3
See the NE limitation Table B-4, “Limits for NEs” (p. B-1)
Limits for Domains
Maximum number of domains managed by 1350 OMS PKT Table B-4
500
Limits for NEs
Maximum number of NEs managed by 1350 OMS PKT
2500
................................................................................................................................................................................................................................... 1350 OMS B-1 8DG42227DAAA 9.6 Issue 3 December 2012
Application Limits
Limits
....................................................................................................................................................................................................................................
Table B-5
Limits for ENEs
Maximum number of ENEs managed by 1350 OMS PKT Table B-6
20000
Limits for ETPs in an ENE
Maximum number of ETPs per ENE
100
Maximum number of ETPs at ENE creation
10
Maximum number of Edge ETPs at ENE creation
5
Table B-7
Limits for LSPs
Maximum number of LSPs Table B-8
Limits for Customers
Maximum number of Customers Table B-9
250000
Limits for Ethernet Services
Maximum number of Ethernet Services Table B-10
108000
250000
Limits for Ethernet Virtual Connections
Maximum number of Ethernet virtual connections (EVC)
250000
Maximum number of EVC terminations
500000
Table B-11
Limits for Ethernet Transport Links
Maximum number of Ethernet Transport Links (ETS)
500000
Maximum number of Ethernet Transport Link terminations
1000000
Maximum number of Ethernet Transport Links (ETB)
100000
.................................................................................................................................................................................................................................... 1350 OMS B-2 8DG42227DAAA 9.6 Issue 3 December 2012
Application Limits
Limits
....................................................................................................................................................................................................................................
Table B-12
Limits for Ethernet Segments
Maximum number of Ethernet Segments Table B-13
Limits for Ethernet edge physical ports
Maximum number of Ethernet edge physical ports Table B-14
600000
25000
Limits for Ethernet Traffic Descriptors
Maximum number of Ethernet Traffic Descriptors
2000
Maximum number of Ethernet Traffic Descriptors per NE
Table B-22, “Limits for each board” (p. B-4)
Table B-15
Limits for Ethernet Traffic Classifiers
Maximum number of Ethernet Traffic Classifiers
5000
Maximum number of Ethernet Traffic Classifiers per NE
Table B-22, “Limits for each board” (p. B-4)
Table B-16
Limits for Ethernet Color Profiles
Maximum number of Ethernet Color Profiles
2000
Maximum number of Ethernet Color Profiles per NE
Table B-22, “Limits for each board” (p. B-4)
Table B-17
Limits for Ethernet switches
Maximum number of Ethernet Switches
2000000
.................................................................................................................................................................................................................................... 1350 OMS B-3 8DG42227DAAA 9.6 Issue 3 December 2012
Application Limits
Limits
....................................................................................................................................................................................................................................
Table B-18
Limits for VLAN Types
Maximum number of VLAN Types
128
Maximum number of VLAN Types constraints
200000
Table B-19
Limits for MPLS Transport Links
Maximum number of Best Effort VC-LSPs & LSP tunnels per Transport Link (FW & BW) Table B-20
200
Limits for MPLS Traffic Descriptors
Maximum number of MPLS Traffic Descriptors
200
Maximum number of MPLS Traffic Descriptors per NE
200
Table B-21
Limits for MPLS VC-LSPs
Maximum number of VC-LSPs
504000
Depending of NE type are defined different limits for each object that 1350 OMS PKT provisions on the boards. The table these limits: Table B-22
Limits for each board
Board Type
ES1 3FE
ES1 8FE
ES1 8FX
Board Version
Traffic Descriptor Limit
Color Profile Limit
Cross Connection limit
Traffic Classifier Limit
1.0
1
Not supported
16
16
1.1 / 1.1B
8
Not supported
1512
512
1.0
1
Not supported
16
16
1.1 / 1.1B
8
Not supported
1512
512
1.1 / 1.1B / 1.2
8
Not supported
1512
512
.................................................................................................................................................................................................................................... 1350 OMS B-4 8DG42227DAAA 9.6 Issue 3 December 2012
Application Limits
Limits
....................................................................................................................................................................................................................................
Table B-22
Limits for each board
Board Type
Board Version
(continued)
Traffic Descriptor Limit
Color Profile Limit
Cross Connection limit
Traffic Classifier Limit
ES4 8FE
1.1 / 1.1B / 1.2
8
Not supported
1512
512
ISA PR EA S1P
1.0
200
Not supported
2000
2000
1.1 / 1.2
200
256
2000
5000
1.0
200
Not supported
2000
5000
1.1 / 1.2
200
256
2000
5000
1.0
200
Not supported
2000
5000
1.1 / 1.2
200
256
2000
5000
ES16- No Access Module
2.0
200
256
20000
20000
ES16 - Access Module: 14FE
2.0
200
256
20000
20000
ES16 - Access Module: 4GE
2.0
200
256
20000
20000
ES16 - No Access Module
2.1
200
256
20000
20000
ISA PR EA 4ETH
ISA PR EA 1GEP
.................................................................................................................................................................................................................................... 1350 OMS B-5 8DG42227DAAA 9.6 Issue 3 December 2012
Application Limits
Limits
....................................................................................................................................................................................................................................
.................................................................................................................................................................................................................................... 1350 OMS B-6 8DG42227DAAA 9.6 Issue 3 December 2012
Appendix C: List of Abbreviations
Abbreviations List Abbreviation
Meaning
100Base-T
100 Mb/s IEEE standard Physical Ethernet interface.
10Base-TX
10 Mb/s IEEE standard Physical Ethernet interface.
1355VPN
Virtual Private Network manager (Alcatel-Lucent product).
14FE
Board type.
1678MCC
Alcatel-Lucent equipment.
1GEP
Board type.
3FE
Board type.
4ETH
Board type.
4GE
Board type.
802.1ad
IEEE standard (Provider Edge Bridging).
802.1D
IEEE standard (MAC Bridge).
802.1p
IEEE standard (Priority Queuing).
802.1Q
IEEE standard (Virtual Bridge).
802.1X
IEEE standard. Port Based Network Access Control.
8FE
Board type.
8FX
Board type.
AAR
Audit/Align/Reserve (as a single function).
ACL
Access Control List.
ADM
Add and Drop Multiplexer.
AF
Assured Forwarding.
AIS
Alarm Indication Signal.
ALMAP
Alcatel-Lucent MAnagement Platform.
ANSI
American National Standards Institute.
................................................................................................................................................................................................................................... 1350 OMS C-1 8DG42227DAAA 9.6 Issue 3 December 2012
List of Abbreviations
Abbreviations
....................................................................................................................................................................................................................................
Abbreviation
Meaning
AS
Alarm Surveillance; Alarm Surveillance interface.
ASAP
Alarm Severity Assignment Profile.
ATM
Asynchronous Transfer Mode.
BA
Broadband Access.
BE
Best Effort.
BM
Broadband Management, Broadband Manager.
BPDU
Bridge Protocol Data Units.
BSR
Broadband Service Router.
BTV
Broadcast Tele Vision.
BW
BandWidth.
CAC
Check Admission Control.
CBS
Committed Burst Size.
CCITT
Telegraph and Telephone International Consultative Committee.
CD-ROM
Compact Disk Read Only Memory.
CE
Customer Edge.
CES
Circuit Emulation Service.
CE-VLAN
Customer Edge VLAN.
CIR
Committed Information Rate.
CIST
Common and Internal Spanning Tree.
CM
Connect Manager.
CNA
CMISE Element Network Adapter.
CORBA
Common Object Requesting Broker Architecture.
CoS
Class of Service.
CP
Connection Profile; Connectivity Problem.
CPE
Customer Premise Equipment.
CSF
Client Signal Failure.
CTP
Connection Termination Point.
C-VLAN
Customer VLAN.
DB
Database.
DEG
Degraded Signal.
DSCP
Differentiated Services Code Point.
DSLAM
Digital Subscriber Line Access Multiplexer.
DWDM
Dense Wavelength Division Multiplexing.
DXC
Cross-Connect.
.................................................................................................................................................................................................................................... 1350 OMS C-2 8DG42227DAAA 9.6 Issue 3 December 2012
List of Abbreviations
Abbreviations
....................................................................................................................................................................................................................................
Abbreviation
Meaning
E/FE
Ethernet and Fast Ethernet board.
E/FE/GE
Ethernet/Fast Ethernet/Gigabit Ethernet.
E2E
End to End.
EBS
Excess Burst Size.
EF
Expedited Forwarding.
EIR
Excess information Rate.
E-LAN
Ethernet LAN.
E-LINE
Ethernet Line.
ELR
Effective Line Rate.
E-LSP
EXP inferred LSP.
EML
Element Management Layer.
ENE
External Network Element.
eOMS
Element Management System.
EOT
Ethernet Over Transport; end-of-task.
EPL
Ethernet Private Line.
EPLAN
Ethernet Private LAN.
EPLANE
Ethernet Private Local Area Network Emulation.
EPLINE
Ethernet Private Line.
EPTL
Ethernet Private Transparent Line.
EPTLINE
Ethernet Private Line.
ES
Ethernet Switching equipment.
ES1
ISA Ethernet Switch equipment.
ES1/4
ISA Ethernet Switch equipment.
ES16
ISA Ethernet Switch equipment.
ES4
ISA Ethernet Switch equipment.
ETB
Ethernet Transport Bridging.
ETH
Ethernet.
ETP
External Termination Point.
E-TREE
Ethernet tree service type.
ETS
Ethernet Transport Service.
ETSI
European Telecommunications Standards Institute.
EVC
Ethernet Virtual Connection.
EVP
Ethernet Virtual Private.
EVPL
Ethernet Virtual Private Line.
.................................................................................................................................................................................................................................... 1350 OMS C-3 8DG42227DAAA 9.6 Issue 3 December 2012
List of Abbreviations
Abbreviations
....................................................................................................................................................................................................................................
Abbreviation
Meaning
EVPLAN
Ethernet virtual private LAN.
EVPLINE
Ethernet Virtual Private Line.
FAD
Function Access Domain.
FE
Fast Ethernet.
FM
Fault Management.
FR
Fault Report.
FW
Farward.
GARP
Generic Attribute Registration Protocol.
Gbit
Giga bits.
Gbit/s
Gigabits per Second.
Gbps
Gigabits per Second.
GE
Gigabit Ethernet.
GENOS
generic OS-to-OS.
GFP
Generic Frame Protocol.
GMPLS
Generalized Multi Protocol Label Switching.
GMRP
GARP Multiple Registration Protocol.
GTM
GFP Type Mismatch Alarm.
GUI
Graphical User Interface.
GVRP
GARP VLAN Registration Protocol.
HA
High Availability.
HDLC
High Level Data Link Control.
HSI
High Speed Internet.
HTML
HyperText Markup Language.
I/O
input/output.
Id
identify, identifier; identification.
IEEE
Institute of Electrical and Electronics Engineers.
IETF
Internet Engineering Task Force.
IGMP
Internet Group Management Protocol.
IM
Information Manager.
IP
Internet Protocol.
ISA
Industry Standard Architecture.
ISA E/FE
ISA Ethernet Switch equipment.
ISA E/FE/GE
ISA 10/100 Eth /ISA Gb Eth.
ISA ES
ISA Ethernet Switch.
.................................................................................................................................................................................................................................... 1350 OMS C-4 8DG42227DAAA 9.6 Issue 3 December 2012
List of Abbreviations
Abbreviations
....................................................................................................................................................................................................................................
Abbreviation
Meaning
ISA ES1
ISA Ethernet Switch equipment.
ISA ES1/4
ISA Ethernet Switch equipment.
ISA ES16
ISA Ethernet Switch equipment.
ISA ES4
ISA Ethernet Switch equipment.
ISA PR
Integrated Service Adapter Packet Ring.
ISA PR EA
Integrated Service Adapter Packet Ring Edge Aggregator.
ISA PR ES16
ISA Ethernet Switch equipment.
ISP
Internet Service Provider.
IWI
Interworking Interface.
Kb/s
Kilo bits per second.
Kbit
Kilo bits.
Kbit/s
Kilo bits per second.
L2CP
Layer 2 Control Protocol.
LAC
Local Access Control.
LACP
Link Aggregation Control Protocol.
LAG
Link Aggregation Group.
LAN
Local Area Network.
LAPS
Link Access Procedure for SDH.
LER
Label Edge Router.
LO
Low Order.
LOF
Loss-of-Frame.
LOS
Loss-of-Signal.
LSP
Label Switched Path.
LSR
Label Switched Router.
MAC
Media Access Control.
MAN
Metropolitan Area Network.
MAU
Medium Attachment Unit.
max
maximum.
Mb/s
Mega bits per second.
Mbps
Megabits per second.
MEF
Metro Ethernet Forum.
MEN
Metro Ethernet Network.
MEP
Maintenance End Point.
MIB
Management Information Base.
.................................................................................................................................................................................................................................... 1350 OMS C-5 8DG42227DAAA 9.6 Issue 3 December 2012
List of Abbreviations
Abbreviations
....................................................................................................................................................................................................................................
Abbreviation
Meaning
min
minimum.
MISTP
Multiple Instance Spanning Tree Protocol.
MPLS
Multiple Protocol Label Switching.
MPtoMP
Multi Point to Multi Point.
MS-GUI
Multi Service - Graphical User Interface.
MSTI
Multiple Spanning Tree Instance.
MSTP
Multiple Spanning Tree Protocol (also called MISTP).
MW
Middleware equipment.
MW-INT
Middleware Interface.
NA
Network Adapter.
NAD
Network Access Domain.
NAP
Network Access Point.
NBI
Northbound Interface.
NE
Network Element.
NML
Network Management Layer.
NMS
Network Management System.
NNI
Network-to-Network Interface.
NV
Native View.
OAM
Operations, Administration, and Maintenance.
OMSN
Optical Multi-Services Node.
OS
Operating System, as in UNIX; Operations System; Optical Section.
OSK
Operation System Kernel.
OTH
Optical Transport Hierarchy.
PAE
Port Access Entity.
PBS
Peak Burst Size.
PC
personal computer.
PCP
Priority Code Point.
PDF
Portable Document Format.
PE
Provider Edge or Edge node.
PHB
Per Hop Behaviour.
PIR
Peak Information Rate.
PKT
Packet.
PLM
Payload Label Mismatch.
PLS
Physical Layer Signalling.
.................................................................................................................................................................................................................................... 1350 OMS C-6 8DG42227DAAA 9.6 Issue 3 December 2012
List of Abbreviations
Abbreviations
....................................................................................................................................................................................................................................
Abbreviation
Meaning
PM
Performance Monitoring.
PMC
Process Monitoring Control.
POP
Point Of Presence.
PPT
Ethernet Physical Port.
PR EA
Packet Ring Edge Aggregator (ISA Ethernet Switch equipment).
P-tagged
Proprietary tagged frame.
PtoMP
Point to Multi Point.
PtoP
Point to Point.
PTP
Physical Termination Point.
P-VLAN
Provider VLAN.
PVSTP
Per-VLAN Spanning Tree Protocol.
PW
Pseudo Wire.
Q3
CMISE-based OSI Inteface.
QoS
Quality of Service.
Q-TAG
Standard VLAN tag.
Q-tagged
Standard VLAN tagged frame.
RM
Regional Manager. Ring Manager.
RMP
routed multipoint.
RPR
Risilient Packet Ring.
RSTP
Rapid Spanning Tree Protocol.
S1P
Board type.
SC
Service Connect.
SDH
Synchronous Digital Hierarchy.
SLA
Service Level Agreement.
SMF
System Management Functions.
SML
Service Management Layer.
SNMP
Simple Network Management Protocol.
SNMP NE
Either an ISA board or a 4G NE.
SONET
Synchronous Optical Network.
STI
Spanning Tree Instance.
STP
Spanning Tree Protocol.
SUBM
Alcatel-Lucent SUBMarine equipments.
S-VLAN
Service VLAN.
TCI
Tag Control Information.
.................................................................................................................................................................................................................................... 1350 OMS C-7 8DG42227DAAA 9.6 Issue 3 December 2012
List of Abbreviations
Abbreviations
....................................................................................................................................................................................................................................
Abbreviation
Meaning
TDM
Time Division Multiplexing.
TL
Transport Link.
TL1
Transaction Language 1.
T-MPLS
Transport Multiple Protocol Label Switching.
TNA
TL1 Network Adapter.
TOS
Type Of Service.
TSF
Trail Signal Failure.
TSS
Transport Service Switch.
TU
Transport Unit.
UI
User Interface.
UNI
User Network Interface.
URU
Underlying Resource Unavailable.
VC
Virtual Container; Virtual Connection.
VC12
Virtual Container 1/2 Mbit/s.
VC-LSP
Virtual Connection - Label Switched Path.
VID
VLAN Identifier.
VLAN
Virtual Local Area Network.
VPAS
Virtual Private Access Services.
VPHS
Virtual Private Hub Services.
VPLAN
Virtual private LAN.
VPLS
Virtual Private LAN Services.
VPN
Virtual Private Network.
VPWS
Virtual Private Wire Services.
VT
Virtual Terminal
WDM
Wavelength Division Multiplexing.
XC
Cross-Connect.
XML
Extensible Markup Language.
XoS
XML-over-socket.
.................................................................................................................................................................................................................................... 1350 OMS C-8 8DG42227DAAA 9.6 Issue 3 December 2012
Index
Symbols
EmlAdapter process, 4-3
.data log file suffix, 6-2 .dataflow log file suffix, 6-2
NmlAdapter process, 4-3 Added value modules
.log log file suffix, 6-2
1350 OMS HA, 1-5
*_dbi.log, 6-2
1350 OMS OI, 1-5
*Gui.log, 6-3 ............................................................. Numerics
1350 OMS applications, 1-2
Administration functions, 11-43 Administrator, 11-71 Also see: System management AF See: Assured Forwarding See: Assured Forwarding (AF)
Alignment, 23-4, 23-26 Also see: Utilities Also see: Utilities after deletion and recreation of SDH Path, 12-61 offline procedure AlignDBSDHPathID, 12-61 All to One Bundling attribute See: User Network Interface (UNI) allTracesModify.log, 6-3 Any to Any See: Service classification
definition, 1-2
Alarm management See: Fault Management
supported NEs, 1-4
Alarm synchronization, 22-15
Backup and restore, 2-2
Alarms
instances, 2-1
1350 OMS PKT application General information, 11-3
AlmAdapter process, 4-3
Applications
Process Monitoring, 2-1
1354BM.log, 6-2
AS_Current_IM process, 4-3
ascurusm.log, 6-3
1678MCC NE
AS_Historic_IM process, 4-3
Assured Forwarding (AF), 11-66, 15-5
Add port, 13-141 Overview, 13-140 Remove port, 13-143 ............................................................. A AAR
See: Utilities Access control default operator profiles, 5-2 Access Control Data Base, 11-71 Adapters
Align Up See: Utilities AlignDBSDHPathID See: Alignment AlignDBSDHPathID Tool definition, 10-2 operating principals, 10-2
Audience intended for this document, lxix, lxx Audit See: Utilities Audit results, 23-8, 23-24 Also see: Utilities Also see: Utilities
Run AlignDBSDHPathID Tool task, 10-3
for Construction domain, 23-8
tool location and execution, 10-2
for MPLS domain, 23-10
for Ethernet domain, 23-8
for T-MPLS domain, 23-11
AlmAdapter process, 4-3 .................................................................................................................................................................................................................................... 1350 OMS IN-1 8DG42227DAAA 9.6 Issue 3 December 2012
Index ....................................................................................................................................................................................................................................
Auditable NEs See: Utilities Audited NEs See: Utilities Autonegotiation, 11-52 Also see: Network Topology Construction
Configure Edge Port, 19-83 Create, 19-49
Add NE to a Domain, 19-91
Delete, 19-56
Configure a NE, 19-98
Delete Termination, 19-81
Create a Customer, 19-104
Details, 19-58
Create an Ethernet Service, 19-107
.............................................................
Inventory Transport Link, 19-64
B BA
List, 19-47 See: Broadband Access (BA)
Modify, 19-53
Back hauling, 11-31
Overview, 19-6
Backups
Remove Transport Link, 19-63
Application backups, 2-2
Routing Display, 18-75
Full system backups, 2-2
Show PM, 18-74
Bandwidth Profile, 19-17
Bridge Workflow, 19-88
Show STI, 19-119
Create and configure EVC, 19-111 Create Domain, 19-90 Domain configuration, 19-88 Domain Configuration, 19-94 Domain definition, 19-88 Domain Modification, 19-96 Ethernet Physical Port configuration, 19-102
Default operations, 19-19
Start PM, 18-71
EVC provisioning, 19-20
Stop PM, 18-72
Link Over TDM configuration, 19-100
Manual operations, 19-19
Synchronize PM, 18-73
NE configuration, 19-89
per CoS, 19-18
Terminations, 19-72
Overwiew, 19-88
per EVC, 19-18
View Provider Bridge Flows, 19-26
Traffic Descriptor Definition, 19-109
per UNI, 19-18, 19-18 QoS, 19-19
Bridge NE, 19-22
Broadband Access (BA), 11-8
See: Best Effort (BE)
Bridge Network See: Ethernet Transport Bridging (ETB)
Broadcast Containment See: Broadcast Domain Containment
BmAdaptationModifyTrace.log, 6-3
Bridge Traffic management See: Ethernet Transport Bridging (ETB)
Broadcast Domain Containment
BmMplsModifyTrace.log, 6-3, 6-3
Bridge Transport Link
BE Best Effort (BE), 11-66
Bridge Edge Port
Activate, 19-41
Activate, 19-45
Add to EVC, 19-62
Configure, 19-83
Configure, 19-30
Deactivate, 19-46
deactivate, 19-42
List, 19-43
Details, 19-38
Description, 20-76 Disable, 20-78 Enable, 20-77 Broadcast Service Type See: Service Type Broadcast Tele Vision See: Broadcast TV (BTV) Broadcast TV (BTV), 11-24 Also see: Service Type
Bridge ENE, 19-24
Get extremities, 19-34
Bridge EVC
Inventory, 19-64
Bridge Based Service, 21-40
Add Termination, 19-74
List, 19-27
Bridge Services, 21-41
Add Transport Link, 19-62
Remove from EVC, 19-63
Configure, 19-61
Construction workflow, 21-24 Create, 21-8
.................................................................................................................................................................................................................................... 1350 OMS IN-2 8DG42227DAAA 9.6 Issue 3 December 2012
Index ....................................................................................................................................................................................................................................
Create Customer, 21-34 Create element, 21-26 Create ETP, 21-20 Create EVC, 21-37 Create Link, 21-29 Create path, 21-25
CES See: Circuit Emulation Services CES procedures, 25-53 Assign resources to Radio Domain, 25-62
Create Service, 21-35
Assign resources to T-MPLS Domain, 25-63
Delete, 21-14
CES attributes, 25-107
Details, 21-16 EVC management, 21-44
CES configuration, 25-127 CES creation, 25-122
IGMP Snooping management, 21-42
CES inventory, 25-126
IGMP Snooping state, 21-44 List, 21-6
CES Nodes See: CES NE
List ETP, 21-18
CES Routing display, 25-130
Modify, 21-11 Overview, 21-3 Service workflow, 21-33 BTV See: Broadcast TV (BTV) Bundling See: User Network Interface (UNI) B-VID See: PBB B-VID ............................................................. C CBS
See: Committed Burst Size (CBS) CC Continuity Check (CC) See: Operations, Administration, and Maintenance (OAM) CDN See: CORBA-based interface (CDN) CE See: Customer Edge (CE)
CES list, 25-106
CES termination attributes, 25-115 CES termination configuration, 25-131 CES termination list, 25-114 Deassign resources from Radio Domain, 25-62
Link Over Radio list, 25-90 Link Over Radio properties, 25-92 Link Over Radio property attributes, 25-93 Link Over Radio synchronization, 25-96 NE attributes, 25-65 NE inventory, 25-68 NE List, 25-64 NE properties, 25-66 NE property attributes, 25-67 PDH Port attributes, 25-79 PDH Port inventory, 25-84 PDH Port properties, 25-82 PDH Port property attributes, 25-83 PDH ports, 25-78 Protection Group inventory, 25-70 Radio Port attributes, 25-98 Radio Port inventory, 25-101
Deassign resources from T-MPLS Domain, 25-63
Radio Port list, 25-97
Domain creation, 25-61 Domain inventory, 25-60
Radio Port property attributes, 25-100
Domain List, 25-58
Stitch tunnels, 25-105
Domain properties, 25-59
Takeover for MEF8, 25-132
Edge Port attributes, 25-86
Takeover for SATOP, 25-134
Edge Port inventory, 25-89
Transport Link attributes, 25-72
Edge Port list, 25-85 Edge Port properties, 25-87 Edge Port property attributes, 25-88 Join tunnels, 25-104 Link Over Radio attributes, 25-91 Link Over Radio inventory, 25-94
Radio Port properties, 25-99
Transport Link extremity inventory, 25-76 Transport Link inventory, 25-75 Transport Link List, 25-71 Transport Link properties, 25-73 Transport Link properties attributes, 25-74
.................................................................................................................................................................................................................................... 1350 OMS IN-3 8DG42227DAAA 9.6 Issue 3 December 2012
Index ....................................................................................................................................................................................................................................
VLAN Paths attributes, 25-103 VLAN Paths list, 25-102 CE-VLAN, 11-12 CIR See: Committed Information Rate (CIR) Circuit Emulation Services AAR Network Operation, 25-50
Implementation, 25-36, 25-38, 25-38, 25-39, 25-40, 25-43, 25-43 inband management, 25-13
Reservation, 25-52, 25-52, 25-52
Interworking, 25-25, 25-25, 25-26, 25-26
Reservation of Link over T-MPLS, 25-14
join, 25-27
Resource assignment, 25-12
layering, 25-4
Resource assignment to T-MPLS domain, 25-14
Loopback management, 25-21, 25-21
Alarm management, 25-17, 25-18, 25-18, 25-18
Manual deimplementation, 25-36
Align, 25-51, 25-51, 25-51
Manual synchronization of PDH links, 25-25
Audit, 25-50, 25-50, 25-50 Bandwidth, 25-41 CAC tolerance, 25-11 Configuration, 25-42, 25-42, 25-43 Control word, 25-15 CoS, 25-29 CoS/PHB Profile compatibility, 25-29
MEF 8, 25-7 modulation mode, 25-11 Navigation, 25-55 network role on PDH port, 25-25 OAM and protections, 25-45, 25-46, 25-48 OAM and protections on PACKET radio, 25-17
creation, 25-33
OAM and protections on T-MPLS, 25-22
creation and allocation, 25-27
Overview, 25-4
deallocation, 25-32
PDH degrade thresholds (TSS-5C), 25-23
definitions, 25-4 deletion, 25-32 E1, 25-36
QoS management, 25-24
infrastructures, 25-5
Alarm correlation, 25-22, 25-23, 25-23, 25-23
allocation, 25-33, 25-35
Protection setup (Workaround), 25-9
Performance Monitoring, 25-19, 25-19, 25-19, 25-19
E1 signal, 25-34, 25-35
Port assignment, 25-12, 25-14, 25-14, 25-22
Encapsulation, 25-7, 25-7, 25-29
Port deassignment, 25-12, 25-14
External Interfaces, 25-7
Port segregation, 25-27
External Products, 25-6 Fault localization, 25-45
Protection Group, 25-20, 25-20, 25-20
IETF, 25-7
Protection schemes, 25-9 Protection setup, 25-9
Routing display, 25-30 SAToP, 25-7 scenarios, 25-4 security, 25-27 stitch, 25-27 Supported flow, 25-38 Switch synchronization, 25-21 synchronization between CES terminations, 25-8 synchronization of Transport Link, 25-13 Takeover, 25-52 Takeover description, 25-52 TDM traffic, 25-7 terminated, 25-33 timestamp frequency, 25-16 Traffic Flow, Ethernet To Radio, 25-39, 25-41 Traffic Flow, PDH To Ethernet, 25-38, 25-41 Traffic Flow, PDH To Radio, 25-38, 25-39, 25-40, 25-40 Traffic Flow, Radio To Ethernet, 25-38, 25-41 Traffic Flow, Radio To Radio, 25-38, 25-38, 25-41 Transport link assignment, 25-12 Transport link deassignment, 25-12
.................................................................................................................................................................................................................................... 1350 OMS IN-4 8DG42227DAAA 9.6 Issue 3 December 2012
Index ....................................................................................................................................................................................................................................
tunnel type management, 25-30
Allocation, 18-54
unterminated, 25-4
Commission, 18-58
Unterminated, 25-39
Configure, 19-61
CORBA-based interface (CDN), 11-42 See: Software interfaces Also see: Software interfaces
Create, 18-44
Core
Class of Service (CoS) CoS Preservation, 18-41 Color Profile
Deallocation, 18-55
c_AuditAlignRecovery, 4-3
Decommission, 18-59
c_DataManagement process, 4-3
Create, 18-135
Deimplement, 18-57
Delete, 18-139
Delete, 18-49
c_EquipmentTopology, 4-3
Details, 18-140
Delete Termination, 18-62
c_FaultManagement process, 4-3
List, 18-134
Details, 18-51
Modify, 18-136
Fault Localization, 18-68
Overview, 18-133
Get terminations, 18-60
Color Profile Management macro functions and default user profiles, 5-12 Command Log, 2-3 administration, 2-3 Committed Burst Size (CBS), 11-64 Committed Information Rate (CIR), 11-64 Compressed transmission, 11-30, 11-31 Configuration Access the System Configuration Window and Configure a 1350 OMS Application task, 3-3 Integrate the 1350 OMS PKT Master Workstation with the Client Workstation task, 3-9 Integrate the 1350 OMS PKT with Other NMSs task, 3-8 Configure the application, 11-43 Confirm the action, 11-40 Connection Less Networks See: Ethernet Transport Bridging (ETB) Connection Oriented EVC Add termination, 18-66
Implement, 18-56
c_Scheduler, 4-3 c_TopologyManagementprocess, 4-3
List, 18-42
CoS See: Class of Service (CoS)
Modify, 18-47
CoS Preservation, 18-44
Overview, 18-37
CPE See: Customer Premise Equipment
Properties, 18-63 Routing Display, 18-75
Start PM, 18-71
Cross Connection, 18-197, 15-63 See: T-MPLS Pseudo Wire See: T-MPLS tunnel Also see: LSP Tunnel
Stop PM, 18-72
Customer
Show PM, 18-74
Synchronize PM, 18-73 Constraint of Ethernet Segment, 18-213 of LSP Tunnel, 15-53, 15-56, 15-58, 15-60
Create, 18-11 Customer Edge (CE), 11-49 Also see: Network Topology Construction Delete, 18-14
of T-MPLS Pseudo Wire, 16-60, 16-62, 16-76, 16-78
Details, 18-15
of T-MPLS Tunnel, 16-109, 16-111
List, 18-9
Constructor, 11-71 Also see: System management Continuity Check (CC) See: Operations, Administration, and Maintenance (OAM)
inventory Services, 18-36
Modify, 18-12 Overview, 18-8 Single-Customer, 12-69 VLAN Mapping, 11-59 Also see: Ethernet Frame Hierarchy VLAN tunneling, 11-61 Also see: Ethernet Frame Hierarchy
.................................................................................................................................................................................................................................... 1350 OMS IN-5 8DG42227DAAA 9.6 Issue 3 December 2012
Index ....................................................................................................................................................................................................................................
Customer management macro functions and default user profiles, 5-9
Configure OAM ETH DM Tool, 24-50
Deactivate DM Tool, 24-46
C-VLAN
List, 24-38
C-VLAN Preservation, 18-41, 18-44
Inventory, 24-48
Documentation related documents, lxxiii Domain Assign resource, 13-27 Create, 13-20
D Data Plane
create Topological View, 13-34
Databases PM Administration, 2-2 databases/dbbmml/data directory, 6-4 DB_SIZE parameter, 7-6 DEI bit, 20-81 Directories
Delete, 13-24 Details, 13-25 eOMS, 13-15 ETB Domain, 13-15 ETS Domain, 13-15 Indirect, 13-15 inventory of NE, 13-31
databases/dbbmml/data, 6-4
inventory of Transport Links, 13-32
ORACLE/databases/dbnml/ admin/bdump, 6-3
inventory of VT Queue Profiles, 13-33
ORACLE/databases/dbnml/ admin/create, 6-3
List, 13-17
ORACLE/databases/dbnml/ admin/logbook, 6-3 ORACLE/databases/network, 6-4 SMF/tools/log/data, 6-3 TAO/maintenance/trace, 6-4 DM (Packet) Delay Measurement See: DM Tool DM Tool, 24-33 Activate DM Tool, 24-46 Configure Maintenance End Points, 24-36
See: End-to-End E_Bridge
Description, 24-34
.............................................................
See: EVC
E E2E
Create ETH DM Tool, 24-42
Customer Premise Equipment (CPE), 11-48 Also see: Network Topology Construction
Customer VLAN, 11-59 Also see: Ethernet Frame Hierarchy
.............................................................
Modify, 13-22 Overview, 13-15 Domain management, 11-47 Also see: Network Topology Construction macro functions and default user profiles, 5-3 Domain Wide VID distribution See: PBB B-VID Duplex mode
E_Bridge process, 4-4 Edge Port See: Ethernet Edge Port EF See: Expedited Forwarding (EF) Egress (-ing), 11-35 Element Management Layer (EML), 11-5 ELP See: Ethernet Linear Protection (ELP) EML See: Element Management Layer EML Proxy, 11-43 EML-IM, 11-43 EMLStart.log, 6-2 Encapsulation Layer-2 See: T-MPLS Pseudo Wire See: T-MPLS tunnel Martini See: Martini encapsulation End-to-End, 18-76 Also see: End-to-End EVC Also see: End-to-End Service End-to-End EVC Create, 18-80 Create full EVC, 18-84 Create raw EVC, 18-86 Full E2E EVC, 18-76 Join, 18-89
full mode, 11-52
List, 18-78
half mode, 11-52
Modify full EVC, 18-87 Overview, 18-76 Prevented Actions, 18-77
.................................................................................................................................................................................................................................... 1350 OMS IN-6 8DG42227DAAA 9.6 Issue 3 December 2012
Index ....................................................................................................................................................................................................................................
Raw E2E EVC, 18-76 End-to-End Service, 11-11 ENE See: External Network Element (ENE) ENE management macro functions and default user profiles, 5-4 EOT e_AuditAlignRecovery process, 4-4
ERP Instance See: Ethernet Ring Protocol (ERP) ETB See: Ethernet Transport Bridging (ETB) Ether Type Frame Classification, 18-6 Ethernet connectivity See: Functional domain Ethernet Edge Physical Port Configure, 18-172
e_DataManagement process, 4-4
Details, 18-175
e_Facility process, 4-4
List, 18-169
e_FaultManagement process, 4-4
List traffic parameters, 18-177
e_ProfileManagement process, 4-4 e_ServiceManagement process, 4-4 e_TrafficManagement process, 4-4 EotModifyTrace.log, 6-3 EPL See: Ethernet Private Line See: Ethernet Private Line (EPL) EPTL See: Ethernet Private Transparent Line Equipment Inner equipment, 11-48 Also see: Network Topology Construction Provider equipment, 11-48 Also see: Network Topology Construction view, 13-70 ERP See: Ethernet Ring Protection See: Ethernet Ring Protocol
VLAN Tag, 11-54 VLAN Tag Protocol Type, 11-54 Ethernet Linear Protection (ELP), 28-16 Add protection, 28-39 Alarms, 28-51 Audit, 28-52 Condition for protecting, 28-38 Condition for unprotecting, 28-38 Configure protection, 28-42 de-implementation, 28-49 Description, 28-34
macro functions and default user profiles, 5-10
Disabled operations, 28-50
Modify, 18-170
EVC specific Attributes, 28-36
Overview, 18-168 Show equipment, 18-180 Ethernet Edge Port
Force align, 28-53 Implementation, 28-48 Inventory, 28-33
Show External Termination Point, 18-183
Inventory of MA, 28-55
Show PM, 18-182
Inventory of Transport Link, 28-54
Ethernet Edge Port management, 11-51 Also see: Network Topology Construction Ethernet Frame Hierarchy Customer VLAN mapping, 11-54 Customer VLAN tunneling, 11-54 Overview, 11-54 Also see: Traffic Management Overview Provider VLAN mapping, 11-54
Linear, 28-38 Manual alignment, 28-47 OAM, 28-52 PM, 28-52 Properties, 28-43 Remove protection, 28-41 Reservation, 28-53 Routing Display, 28-56 Send APS command, 28-45 Take-Over, 28-53 Ethernet Macro functions
Provider VLAN tunneling, 11-54
Color Profile management, 5-12
VLAN management, 11-55
Customer management, 5-9
.................................................................................................................................................................................................................................... 1350 OMS IN-7 8DG42227DAAA 9.6 Issue 3 December 2012
Index ....................................................................................................................................................................................................................................
Ethernet Edge Physical Port management, 5-10
Ethernet Ring Protection (ERP), 20-107
Ethernet Segment management, 5-11
Ethernet Ring Protocol (ERP)
Ethernet Traffic Classifier management, 5-10 Ethernet Traffic Descriptor management, 5-10 Ethernet Transport Segment management, 5-11 EVC management, 5-9 Provider Network management, 5-13 Service management, 5-9 Transport Link management, 5-12 VLAN Type management, 5-13 Ethernet Operations, Administration, and Maintenance (OAM), 24-1 See: Operations, Administration, and Maintenance (OAM) Ethernet Physical Port, 13-96 assign to Domain, 13-35 Assign to domain, 13-106 Configure, 13-99 deassign from Domain, 13-36 Details, 13-108 List, 13-96 Modify, 13-104 Navigation to equipment, 13-111 Ethernet physical port management macro functions and default user profiles, 5-5
Add/remove Node, 20-116 Add/remove ring in a bundle, 20-118 Add/remove Transport Link, 20-115 associate to OAM, 20-126 Create/delete, 20-110
Details, 18-240 Details of constraint, 18-219 Disassociate a Traffic Classifier, 18-211 Get extremities, 18-235 Get Route, 18-242 Implement, 18-229 List, 18-199 List constraint, 18-216
Create/delete bundle, 20-117
macro functions and default user profiles, 5-11
Create/delete ERP instance, 20-123
Modify, 18-205
Fault Localization, 20-134 Graphical view, 20-127 Implement/deimplement, 20-112, 20-125 Instance List, 20-121 List, 20-108 Modify Defined ERP instance, 20-129 Modify implemented ERP instance, 20-131 Navigation to AS, 20-134 Overview, 20-10 Switch Command, 20-113, 20-114 Ethernet Segment, 11-6
Modify constraint, 18-222 Overview, 18-197 Ethernet Service, 11-6, 11-15 All to One Bundling attribute See: User Network Interface (UNI) Bundling Service attribute See: User Network Interface (UNI) Create, 18-22 Delete, 18-32 Details, 18-33 List, 18-20 management, 11-53 Also see: Traffic Management
Add constraint, 18-213
Modify, 18-30
Allocate, 18-226
Overview, 18-17
Associate a Traffic Classifier, 18-209
Service Multiplexing attribute See: User Network Interface (UNI)
Configure, 18-233 connectivity view, 18-244 Create, 18-202
Ethernet Private Line (EPL), 11-8, 11-18
Deallocate, 18-227
Ethernet Private Transparent Line (EPTL), 11-17
Delete, 18-208
Deimplement, 18-231
Delete constraint, 18-218
Setup, 18-24 Ethernet Switch, 18-197 Ethernet Termination Point (ETP) Create, 21-20 Delete, 21-22 List, 21-18
.................................................................................................................................................................................................................................... 1350 OMS IN-8 8DG42227DAAA 9.6 Issue 3 December 2012
Index ....................................................................................................................................................................................................................................
Ethernet Traffic Classifier management macro functions and default user profiles, 5-10 Ethernet Traffic Descriptor management macro functions and default user profiles, 5-10 Ethernet Transport Bridging (ETB), 19-4 Also see: Bridge Overview, 19-4 Ethernet Transport Link Bandwidth load, 18-196 Configure, 18-188
Ethernet Virtual Private Line (EVPL), 11-8, 11-16
Extended Ethernet Virtual Private Line (Extended EVPL), 11-20
ETP See: Ethernet Termination Point
Extended EVPL See: Extended Ethernet Virtual Private Line
ETS See: Ethernet Transport Service (ETS)
Extended EVPLAN See: Extended Ethernet Virtual Private LAN
ETS NNI Interface
External Network Element (ENE), 13-78, 11-48 Also see: Network Topology Construction
VLAN Push/Pop See: VLAN Management EVC See: Ethernet Virtual Connection (EVC) EVC Bandwidth
Create, 13-82 Delete, 13-87 Details, 13-88
Dynamic change, 19-112
List, 13-80
EVC Terminations, 19-116
Modify, 13-85
Implemented Object applicability, 19-113
Overview, 13-78
List, 18-186 Overview, 18-184
Object applicability, 19-112
Details, 18-193 Get extremities, 18-190
Ethernet Transport Segment macro functions and default user profiles, 5-11 Ethernet Transport Service (ETS), 11-6 Also see: Traffic Management Also see: Connection Oriented Ethernet Virtual Connection (EVC), 11-6 Also see: Bridge EVC Also see: End-to-End EVC Data Plane, 19-11 Fault Localization, 19-65, 19-70 Life cycle See: Spanning tree instance Start OAM, 24-28 Ethernet Virtual Private hub (EVP Hub), 11-8 Ethernet Virtual Private LAN (EVPLAN) See: LAN
Object status applicability, 19-113 EVC management, 11-53 Also see: Traffic Management macro functions and default user profiles, 5-9 EVP Hub See: Ethernet Private Line hub (EVP hub) EVPL See: Ethernet Virtual Private Line See: Ethernet Virtual Private Line (EVPL) EVPLAN See: Ethernet Virtual Private LAN Expedited Forwarding (EF), 11-66 Extended Ethernet Virtual Connection See: End-to-End EVC Extended Ethernet Virtual Private LAN (Extended EVPLAN), 11-21
External termination management macro functions and default user profiles, 5-5 External Termination Point Create, 13-92 Delete, 13-94 List, 13-90 ............................................................ F FAD
See: Functional Access Domain Failure management log file location, 6-5 log file suffixes, 6-5 Fault Localization, 11-69 List, 22-12 Navigation to equipment, 19-65 Navigation to manager, 19-70 Fault Management (FM), 22-12, 22-12 Also see: Fault Localization Alarm probable cause, 22-2
.................................................................................................................................................................................................................................... 1350 OMS IN-9 8DG42227DAAA 9.6 Issue 3 December 2012
Index ....................................................................................................................................................................................................................................
Alarm synchronization, 22-15
Graphical User Interface (GUI), 11-39
Client Signal Fail, 22-16
Grooming feature, 11-31
from ISA E/FE/GE board, 22-3
GUI See: Graphical User Interface
from ISA ES1 board, 22-4 from ISA ES16 board, 22-6
.............................................................
from ISA ES4 board, 22-4 H Half mode
on SDH paths, 22-8
See: Duplex mode
Overview, 22-2
Hash key, 13-118
Flow control
High Speed Internet (HSI), 11-22
Asymmetric, 11-52 Symmetric, 11-52 FM See: Fault Management (FM) Frame delivery, 18-41, 18-44 Frame distribution See: Hash key
Instances, 2-1 Interworking Interface (IWI), 11-48 IP address See: TCP/IP address IP DSCP/TOS
Hub & Spoke Topology, 11-31 Also see: Network Topology Description
ISA BCE Ethernet Board
In Band
free pool, 11-71, 11-72
Address Configuration, 20-157
Full E2E EVC See: End-to-End EVC
LAG port creation, 20-165
Full meshed Topology, 11-33 Also see: Network Topology Description
Inner Provider, 11-48 Also see: Network Topology Construction
HSI See: High Speed Internet
............................................................. I
Inner equipment, 11-48 Also see: Network Topology Construction
Management, 20-156 NMS Start Supervision, 20-183 In band management, 28-3
Frame Classification, 18-6
Configuration, 13-146 ISA board MIB realignment for, 9-2 Realign an ISA Board MIB task, 9-4 IWI See: Interworking Interface ............................................................. J JacORB.log, 6-2
Full mode See: Duplex mode
Configuration requirements, 28-8
Join See: CES procedures
Functional Access Domain (FAD), 11-71
Manual resource reservation, 28-11
Jumbo Frames, 13-135
Functional domain
Overview, 28-3
Ethernet connectivity, 11-45
Pseudowire configuration, 28-9
Maintenance management, 11-46
Subnetwork topology, 28-4
Configure, 13-137 Overview, 13-135 .............................................................
MPLS management, 11-46 Network Topology Construction, 11-45 Overview, 11-45 T-MPLS management, 11-46 Traffic management, 11-45 Utilities, 11-46 ............................................................. G Glossary, lxxiii
Tunnel configuration, 28-9 In fiber management See: In band management
L Label Edge Router (LER), 11-10,
11-10 Label Switched Router (LSR), 11-10
inband management, 25-13 Also see: Circuit Emulation Services
LAC state, 13-40 See: Network Element (NE)
Ingress (-ing), 11-35
LAG See: Link Aggregation
Initiator, 11-71, 11-72 Inner ENE, 11-48 Also see: Network Topology Construction
LAG Link Over Cable, 14-62 Create from extremities, 14-63 Create from Links, 14-66
.................................................................................................................................................................................................................................... 1350 OMS IN-10 8DG42227DAAA 9.6 Issue 3 December 2012
Index ....................................................................................................................................................................................................................................
Create VCG from extremities, 14-69 Create VCG from Links, 14-72 Delete, 14-77 Details, 14-80 Get extremities, 14-79 List, 14-62 Modify, 14-75 LAG Port Assign NAD, 13-125 Create, 13-118
deassign from Domain, 14-61
Get extremities, 14-90
Delete, 14-46
List, 14-89
Details, 14-50
Link over MPLS
Fault Localization, 14-59 Get extremities, 14-48 Join, 14-52 List, 14-41 Link over cable macro functions and default user profiles, 5-6 Link Over Cable
Details, 13-126
Modify, 14-44
Inventory of physical port, 13-128
Overview, 14-38
List, 13-116 Modify, 13-120 LAN See: Local Area Network Layer-2 Control Protocol Processing, 19-16 Encapsulation See: T-MPLS Pseudo Wire See: T-MPLS tunnel LER See: Label Edge Router Link Aggregation (LAG), 13-113, 13-113 Also see: LAG Port Group of Ports, 13-113 Overview, 13-113 Supporting NE, 13-114 Link Over Cable, 14-38 Assign NAD, 14-58 assign to Domain, 14-60
Split, 14-52 Upload, 13-74 Link over EVC AAR, 28-31 Activation, 28-29 Alarms, 28-25 Assign to Domain, 28-27 Bandwidth usage, 28-18 Creation, 28-22 Deactivation, 28-29 Deassign from Domain, 28-27 Deletion, 28-24 Description, 28-18 Inventory, 28-33 Involved objects, 28-18 Lock and unlock, 28-20 OAM, 28-26 Routing Display, 28-32 STP impacts, 28-30
Configure, 14-57
Transport Link configuration, 28-28
Configure Join, 14-54
Usage within an EVC, 28-30
Configure Split, 14-54 Create, 14-42
Link Over MPLS Details, 14-91
macro functions and default user profiles, 5-6 Link Over MPLS Overview, 14-88 Link Over Radio List, 14-93 Link over SDH macro functions and default user profiles, 5-5 Link Over TDM Assign NAD, 14-32 assign to Domain, 14-30 Configure, 14-25 Create, 14-21 deassign from Domain, 14-31 Delete, 14-24 Details, 14-34 Fault Localization, 14-36 Get extremities, 14-27 List, 14-17 remove inconsistent paths, 14-29 Upload, 13-59 Link Over T-MPLS Details, 14-97 Get extremities, 14-96 infrastructure, 14-99 List, 14-95 Overview, 14-94 Link Over WDM Details, 14-86 Get extremities, 14-84 List, 14-83 Overview, 14-82
.................................................................................................................................................................................................................................... 1350 OMS IN-11 8DG42227DAAA 9.6 Issue 3 December 2012
Index ....................................................................................................................................................................................................................................
Linktrace See: Operations, Administration, and Maintenance (OAM) Local port, 11-47, 11-47 Also see: Ethernet physical port
trace management log file locations, 6-6
LSR See: Label Switched Router
trace management log file suffixes, 6-6
.............................................................
log out, 11-38
Loopback See: Operations, Administration, and Maintenance (OAM)
login, 11-38
LSP PHB profile
Logs
Create, 16-8
1354BM.log, 6-2
Delete, 16-11
allTracesModify.logg, 6-3
Details, 16-13
ascurusm.log, 6-3
List, 16-6
BmAdaptationModifyTrace.log, 6-3
Modify, 16-9
BmMplsModifyTrace.log, 6-3, 6-3 Command logs, 2-3 .data log file suffixes, 6-2 .dataflow log file suffixes, 6-2 *_dbi.log, 6-2 EMLStart.log, 6-2 EotModifyTrace.log, 6-3 failure management log file location, 6-5 failure management log file suffixes, 6-5 *Gui.log, 6-3 JacORB.log, 6-2 list of maintenance/log files, 6-2
Overview, 16-5 LSP Tunnel, 15-39 Add constraint, 15-56
MAC Bridge Configure edge switching port, 12-73 Configure internal switching port, 12-72 Configure switching port, 12-71 Configure UNI, IWI, or NNI switching ports, 12-72 Distributed MAC Bridge, 12-67
Bandwidth load, 15-74
Network Configuration, 12-77
Create, 15-43
Provisioning procedure, 12-70
Deallocate, 15-51
MAC Bridging, 11-8
Delete, 15-47
MAC flushing
Delete constraint, 15-58, 15-60
Creation, 16-158
Details, 15-70
Force, 16-164
Get extremities, 15-67
Interconnection Schemes, 16-162
Implement, 15-65 List, 15-18, 15-36, 15-41, 16-28 List constraint, 15-53
log file locations, 6-2 .log log file suffixes, 6-2
List of Transport Links, 15-79
NMLStart.log, 6-2
List of VC-LSP, 15-72
pmc2.log, 6-2
Modify, 15-45
PMCStart.log , 6-2
Overview, 15-40
Security logs, 2-3
Route, 15-77
System logs, 2-3
Maintenance Association (MA) See: Operations, Administration, and Maintenance (OAM)
Allocate, 15-48
List of cross connections, 15-63
smf.log, 6-2
M MA
LSP Tunnel management macro functions and default user profiles, 5-7
List, 16-160 MAC flushing protection Description, 16-157 MAC Flushing Protection, 16-156 Also see: T-MPLS Tunnel Redundancy Macro functions Domain management, 5-3 ENE management, 5-4 Ethernet physical port, 5-5 External termination management, 5-5 Link over cable, 5-6
.................................................................................................................................................................................................................................... 1350 OMS IN-12 8DG42227DAAA 9.6 Issue 3 December 2012
Index ....................................................................................................................................................................................................................................
Link over MPLS, 5-6
EVPLAN, 11-27
Link over SDH, 5-5
Extended EVPL, 11-27
NE management, 5-4
Extended EVPLAN, 11-27
SDH termination management, 5-4
HSI, 11-27
Service node management, 5-3 TMPLS management, 5-3 Utilities management, 5-6 Maintenance Activation, 24-28 Maintenance Association (MA) See: Operations, Administration, and Maintenance (OAM) Maintenance management, 11-69, 11-46 Also see: Fault Localization Also see: Functional domain overview Alarms, 11-69 Inventory, 11-70 Overview, 11-69 Management Layers
Service Definition, 11-27 MIB categories of misalignment, 9-3 definition, 9-2 MIB parameter, 7-6 operating principals, 9-2 Realign an ISA Board MIB task, 9-4 realignment for a new ISA board, 9-2 MPLS LSP Tunnel management macros, 5-7 m_AuditAlignRecovery process, 4-3 m_DataManagement process, 4-3
Element Management Layer (EML), 11-5
m_FaultManagement process, 4-3
Network Management Layer (NML), 11-5
m_NetworkManagement process, 4-3
Physical Layer, 11-5
m_TrafficProfileManagement process, 4-3
Service Management Layer (SML), 11-5 Manager control, 13-90 Also see: External Termination Point Martini encapsulation, 11-33 MEF See: Metro Ethernet Forum Metro Ethernet Forum (MEF) Broadcast, 11-27 BTV, 11-27 EPL, 11-27 EPTL, 11-27
Traffic descriptor management macros, 5-7 Transport Link management macros, 5-7 VC LSP management macros, 5-8 MPLS layer T-MPLS comparison, 11-9 MPLS management, 11-46 Also see: Functional domain overview LSP Tunnel, 11-65, 11-66 MPLS Transport Link, 11-65
T-MPLS Transport Link, 11-65, 11-65 Traffic Descriptor, 11-65, 11-66 Transport Link, 11-65 VC-LSP, 11-65, 11-67 MS-GUI See: Multi-Service GUI Multi-Manager management, 11-44 Multi-Manager Management definition, 8-2 identifying Ethernet-defined entities, 8-3 operational guidelines, 8-3 scenarios, 8-2 Multiplexing attribute See: User Network Interface (UNI) Multipoint to Multipoint See: Service classification Multi-Service GUI (MS-GUI), 11-39 Multi-service node T-MPLS PseudoWire, 11-10 MW-INT functionality, 2-1 instances and, 2-1 Process Monitoring, 2-1 ............................................................ N NAD
See: Network Access Domain Create, 13-132 Delete, 13-134 List, 13-130 Modify, 13-133 Native Network, 11-35 NBI NbiManagement process, 4-4
EVPL, 11-27 .................................................................................................................................................................................................................................... 1350 OMS IN-13 8DG42227DAAA 9.6 Issue 3 December 2012
Index ....................................................................................................................................................................................................................................
NE See: Network Element (NE) NE management macro functions and default user profiles, 5-4 NEs those supported for this release, 1-4
Network Topology Construction, 11-45 Also see: Functional domain overview Auto-negotiation, 11-48 Customer Edge (CE), 11-49 Domain management, 11-47 ENE management, 11-48
Network Access Domain (NAD), 11-71, 11-72, 11-72, 13-130
Ethernet Edge Port management, 11-51
Network architecture, 11-7
Inner equipment, 11-48
Network Element (NE), 13-40, 11-47 Also see: discovery
NE management, 11-47
Add to Subnetwork, 13-46 assign to Domain, 13-29 available NE, 13-53 Boards, 11-48 create Topological View, 13-77
Overview, 11-47
............................................................. O OAM
See: Operations, Administration, and Maintenance (OAM) Operations, Administration, and Maintenance (OAM), 11-9 Configure Maintenance Association, 24-23 Configure OAM Domain, 24-13 Continuity Check (CC), 24-3 Create OAM Domain, 24-7
Provider equipment, 11-48
Deimplement Maintenance Association, 24-25
Subnetwork management, 11-47
Deimplement OAM Domain, 24-14
Transport Link management, 11-50
Disable Continuity Check, 24-24
Network Topology Description
create VT Queue Profile, 13-76
Full meshed Topology, 11-33
Enable Continuity Check, 24-24
deassign from Domain, 13-30
Hub & spoke Topology, 11-31
Inventory item of MA, 24-26
Define, 13-43
Overview, 11-30
Defined NE, 13-42
Point to Point Topology, 11-30
Inventory objects of MA, 24-27
Details, 13-52
Ring Topology, 11-35
inventory of VT Queue Profiles, 13-73
Network-to-Network Interface (NNI), 11-10, 11-48, 18-225
LAC state Acknowledge, 13-68
NML See: Network Management Layer
Management, 11-47 Also see: Network Topology Construction
NML Proxy, 11-43
Modify, 13-49
NML-IM, 11-43
Overview, 13-40
NMLStart.log, 6-2
Resources, 11-47 Also see: Network Topology Construction
NNI See: Network-to-Network Interface
Network Management Layer (NML), 11-5 Network topologies, 11-8 Also see: Service classification
north interface, 11-71 Also see: System management
Inventory of monitored objects, 24-16 Inventory of OAM Domain, 24-15 Linktrace, 24-3 Linktrace activation, 24-31 List Maintenance Association, 24-18 List OAM Domains, 24-8 Loopback, 11-69, 24-3 Loopback activation, 24-29 Maintenance Association, 24-17 Maintenance Association (MA), 24-3 Maintenance Domain (MD), 24-3 Model, 24-4
.................................................................................................................................................................................................................................... 1350 OMS IN-14 8DG42227DAAA 9.6 Issue 3 December 2012
Index ....................................................................................................................................................................................................................................
Modify Maintenance Association, 24-22 Modify OAM Domain, 24-12 Monitored Objects, 24-6 Overviw, 24-3 Properties of MA, 24-20 Properties of OAM Domain, 24-10 Start on EVC, 24-28 Terminology, ITU vs IEEE, 24-3 Operator, 11-71 Also see: System management Oracle ORACLE/databases/dbnml/ admin/bdump directory, 6-3 ORACLE/databases/dbnml/ admin/create directory, 6-3 ORACLE/databases/dbnml/ admin/logbook file, 6-3 ORACLE/databases/network directory, 6-4 oracle_monitor_process, 4-3 ............................................................. P Packet concatenation, 11-31, 11-33
Packet Radio See: Circuit Emulation Services Parameters DB_SIZE parameter, 7-6 MIB parameter, 7-6 PRINTER parameter, 7-4 SYS_START_WAIT_VAL parameter, 7-5 SYSTEM_TUNING_VAL parameter, 7-5 TMP_ALM_PADDINGRATE parameter, 7-9 TMP_ALM_TEMPOASYNC parameter, 7-9
TMP_A:LM_ TEMPOPOLLING parameter, 7-9
TMP_WAIT_MPLS_ SYNCHRO_STARTUP parameter, 7-12
TMP_ALM_TEMPOTIMER parameter, 7-9
UI_LANGUAGE parameter, 7-4
TMP_ CDNDATABLOCKSIZE parameter, 7-9
PBB See: Provider Backbone Bridge (PBB)
TMP_EML_ TEMPOPOLLING parameter, 7-10
PBB B-VID
TMP_FORBIDDEN_ COMMENT_CHAR parameter, 7-10 TMP_FORBIDDEN_LABEL_ CHAR parameter, 7-10 TMP_LINK_OVER_SDH_ SYNCHRONIZATION_AT_ STARTUP parameter, 7-10
Allocate, 20-87 Create, 20-84 Deallocate, 20-88 Deimplement, 20-91 Delete, 20-86 Domain Wide distribution, 20-93 Implement, 20-89
TMP_LOG_BASED_ SYNCHRONIZATION_AT_ STARTUP parameter, 7-10
Inventory of ERP instances, 20-101
TMP_NE_UNDER_ _ MANAGEMENT parameter, 7-11
List ERP instances, 20-101
TMP_NML_ TEMPOPOLLING parameter, 7-11
Ring Association, 20-95
TMP_ REMOTENAMINGEMLFILE parameter, 7-11
Transport Link association, 20-102
TMP_SDH_TERM_ SYNCHRONIZATION_AT_ STARTUP parameter, 7-11 TMP_SE_ACCESSCTL parameter, 7-11 TMP_TRACELEVEL parameter, 7-12
List, 20-83
Management, 20-82 modify ERP, 20-99
Ring Dissociation, 20-97
Transport Link dissociation, 20-104 PBB EVC, 20-77, 20-78 Also see: Broadcast Domain Containment Also see: Broadcast Domain Containment Add Termination, 20-56
TMP_ TRACEMAXLINECOUNT parameter, 7-12
Add Termination on implemented EVC, 20-71
TMP_WAIT_EOT_ SYNCHRO_STARTUP parameter, 7-12
Bridge Flows, 20-74
Allocation, 20-65
Configure, 20-73 Create, 20-63, 20-144
.................................................................................................................................................................................................................................... 1350 OMS IN-15 8DG42227DAAA 9.6 Issue 3 December 2012
Index ....................................................................................................................................................................................................................................
Deallocation, 20-67
Per Hop Behaviour (PHB), 19-18
deimplement, 20-70
profile See: LSP PHB profile See: T-MPLS Pseudo Wire
Fault Localization, 20-134 Fault Management, 20-133 Implement, 20-68
Performance Monitoring (PM), 11-69
List, 20-61
Selective collection, 11-69
Management, 20-60
ShowPM, 18-74, 18-182
Navigation to AS, 20-134
Start, 18-71
Remove Termination, 20-59
Stop, 18-72
Remove Termination on implemented EVC, 20-72
Synchronize, 18-73
PBB EVC Termination Automatic association to default VT, 20-79 Manual association to default VT, 20-80 PBB Workflow, 20-135 Add NE to a Domain, 20-138 Add Transport Link to a Domain, 20-139 B-VID configuration, 20-143 Create PBB Domain, 20-137 Domain overview, 20-135 ERP provisioning, 20-141 EVC Allocation and Implementation, 20-155
VPWS procedure, 12-62 per-STI See: Spanning Tree Instance PHB See: Per Hop Behaviour (PHB) Physical Layer, 11-5, 11-5 Physical Port Inventory from LAG port, 13-128 Upload, 13-54 PIR See: Peak Information Rate (PIR) PM See: Performance Monitoring (PM) PM Administration, 2-2
EVC traffic classification, 20-153
pmc2.log, 6-2
Overwiew, 20-135
PMCStart.log, 6-2
Traffic Descriptor Definition, 20-154
Point to Multipoint See: Service classification
Transport Link overwiew, 20-135
Point to Point See: Service classification
PBS See: Peak Burst Size (PBS) Peak Burst Size (PBS), 11-64 Peak Information Rate (PIR), 11-64
Topology, 11-30 Also see: Network Topology Description Policy Control, 11-64 Also see: Traffic Management PRINTER parameter, 7-4
Priority Id, 11-56 Also see: VLAN Management Process Monitoring, 2-1 Protection, 28-16 Also see: Ethernet Linear Protection (ELP) Provider Equipment, 11-48 Also see: Network Topology Construction Provider network, 12-67 VLAN mapping, 11-60 Also see: Ethernet Frame Hierarchy VLAN tunneling, 11-61 Also see: Ethernet Frame Hierarchy Provider Backbone Bridge (PBB), 20-5 Also see: PBB Overview, 20-5 Provider Bridging, 11-8 Provider Network Management macro functions and default user profiles, 5-13 Proxies Proxy_E_EML_NAME process, 4-4 Proxy_E_SNA_NAME process, 4-4 Proxy_N_NML_NAME process, 4-4 Proxy, 11-43 Pseudo Wire See: T-MPLS Pseudo Wire P-VLAN, 11-60 Also see: Provider VLAN ............................................................. Q Q3, 11-47, 11-48
QoS See: Quality of Service
.................................................................................................................................................................................................................................... 1350 OMS IN-16 8DG42227DAAA 9.6 Issue 3 December 2012
Index ....................................................................................................................................................................................................................................
Q-tag, 11-56, 11-58 Also see: VLAN Management Quality of Service, 11-69 ............................................................. R Radio Ports
Upload, 13-75 Raw E2E EVC See: End-to-End EVC Remote port, 11-47, 11-47 Also see: TDM terminations Replacement See: Utilities Reroute operation, 16-109, 16-111 Reservation See: Utilities Reserved Spanning Tree Protocol, 12-69 Restore procedure, 23-33 Resynchronization See: Synchronization Ring Topology, 11-35 Also see: Network Topology Description Routed Multipoint See: Service classification Routing Display, 18-75
SEC User Authentication, 2-2 Service classification, 11-15 Any to Any, 11-15 Multipoint to Multipoint, 11-15 Point to Multipoint, 11-15 Point to Point, 11-15 Routed Multipoint, 11-15 Service Delimiting, 19-117 Operation and expected behavior, 19-117 Vlan Push/Pop on UNI/IWI, 19-117 Service management macro functions and default user profiles, 5-9 Service Management Layer (SML), 11-5 Service Node inventory of NE, 13-38 List, 13-39 Overview, 13-37 Service node management macro functions and default user profiles, 5-3 Service Type
RSTP See: Reserved Spanning Tree Protocol
BTV, 11-24
.............................................................
EPL, 11-18
S Safety information, lxix
EPTL, 11-17
SDH termination management macro functions and default user profiles, 5-4
Broadcast, 11-26
EVPL, 11-16 EVPLAN, 11-19 Extended EVPL, 11-20
SEC User Administration, 2-2
Extended EVPLAN, 11-21
SEC User Authentication, 2-2
HSI, 11-22
Section See: T-MPLS Section Security SEC User Administration, 2-2
Sessions SessionManagement process, 4-4
SLM (Packet) Loss Measurement See: SLM Tool SLM Tool, 24-33 Activate SLM Tool, 24-47 Configure Maintenance End Points, 24-36 Configure OAM ETH SLM Tool, 24-52 Create ETH SLM Tool, 24-44 Deactivate SLM Tool, 24-47 Description, 24-35 Inventory, 24-49 List, 24-40 SMF smf.log, 6-2 SMF/tools/log/data file directory, 6-3 SML See: Service Management Layer SNMP, 11-47, 11-48 Software interfaces, 11-42 Spanning Tree Instance (STI) active STI, 19-8 configuration, 19-121 Control plane, 19-9 Deimplementation, 19-124 EVC life cycle, 19-13 Implementation, 19-123 inventory, 19-119 List, 19-120 Overview, 19-8 per-STI, 19-8 Port configuration, 19-8 Static tree topology, 19-9 ST-link, 19-8 Tree topology, 19-8, 19-8
.................................................................................................................................................................................................................................... 1350 OMS IN-17 8DG42227DAAA 9.6 Issue 3 December 2012
Index ....................................................................................................................................................................................................................................
Start AAR procedure See: Utilities STI See: Spanning Tree Instance Stitch See: CES procedures
............................................................. T Takeover
CES See: CES Procedures Description for TMPLS, 18-130
TMP_ALM_PADDINGRATE parameter, 7-9 TMP_ALM_TEMPOASYNC parameter, 7-9 TMP_ALM_TEMPOPOLLING parameter, 7-9
ST-link See: Spanning Tree Instance
Full EVC Overview, 18-121
TMP_ALM_TEMPOTIMER parameter, 7-9
Stop AAR procedure See: Utilities
Key features for T-MPLS, 18-130
TMP_CDNDATABLOCKSIZE parameter, 7-9
Subnetwork
Main procedure steps for T-MPLS, 18-130
TMP_EML_TEMPOPOLLING parameter, 7-10
Procedure for full EVC, 18-122
TMP_FORBIDDEN_ COMMENT_CHAR parameter, 7-10
Create, 13-8 Delete, 13-13 Details, 13-14 List, 13-7 Modify, 13-10 Overview, 13-5 Subnetwork management, 11-47 Also see: Network Topology Construction Synchronization, 12-60 synchronization CES Link Over Radio See: CES procedures SYS_START_WAIT_VAL parameter, 7-5 System management, 11-46 Also see: Functional domain overview
Procedure for TMPLS, 18-131 TAO/maintenance/trace file, 6-4 Tasks Access the System Configuration Window and Configure a 1350 OMS Application, 3-3 Integrate the 1350 OMS PKT Master Workstation with the Client Workstation, 3-9 Integrate the 1350 OMS PKT with Other NMSs, 3-8 Realign an ISA Board MIB task, 9-4 Run AlignDBSDHPathID Tool task, 10-3 View Application Release Information, 2-4
Access Control Data Base, 11-71
TCP/IP address, 11-38, 13-40
FAD, 11-71
TDM termination
free pool, 11-71, 11-72
Audit, 13-62
Initiator, 11-71, 11-72
Details, 13-67
NAD, 11-71, 11-72
List, 13-66
Overview, 11-71
Synchronize, 13-64
User Profile management, 11-71, 11-71
Upload, 13-57
SYSTEM_TUNING_VAL parameter, 7-5
Termination Point See: Ethernet Termination Point
TMP_FORBIDDEN_LABEL_ CHAR parameter, 7-10 TMP_LINK_OVER_SDH_ SYNCHRONIZATION_AT_ STARTUP parameter, 7-10 TMP_LOG_BASED_ SYNCHRONIZATION_AT_ STARTUPP parameter, 7-10 T-MPLS EVC Force MAC flushing, 16-164 List, 17-32 MAC flushing List, 16-160 T-MPLS layer MPLS comparison, 11-9 TMPLS management macro functions and default user profiles, 5-3 T-MPLS networking layers, 11-10 LSP Tunnel, 11-10 PseudoWire, 11-10 Section, 11-10 T-MPLS Pseudo Wire Add constraint, 16-60 Add/Remove PHB profile, 16-64 Allocate, 16-67
.................................................................................................................................................................................................................................... 1350 OMS IN-18 8DG42227DAAA 9.6 Issue 3 December 2012
Index ....................................................................................................................................................................................................................................
Bandwidth load, 16-86
Dellocate, 16-120
Configure, 16-60, 16-62, 16-64
Details, 16-107
Create, 16-53
Get extremities, 16-132
Deallocate, 16-70
Get route, 16-137
Deimplement, 16-74
Implement, 16-122
Delete, 16-57
Inventory, 16-134
Delete constraint, 16-62
Inventory of Pseudo Wires, 16-138
Details, 16-58 Details of constraints, 16-78 Get extremities, 16-82 Get route, 16-87 Implement, 16-72 Layer-2 encapsulation, 16-66 List, 16-51 List constraints, 16-76 List cross connections, 16-80 List crossing Pseudo Wires, 16-88
Layer-2 encapsulation, 16-115 List, 16-99 List constraints, 16-126 List cross connections, 16-130 Modify, 16-104 Overview, 16-97 Remove PHB Profile, 16-113 T-MPLS Tunnel Redundancy, 16-165 Also see: MAC Flushing Protection
List sections, 16-84
Black Hole prevention, 16-167
Modify, 16-55
Create Dual-point-topointProtection, 16-175
Overview, 16-50 T-MPLS Section Details, 14-102
Create MAC Flushing Protection Schema, 16-177
TMP_NML_TEMPOPOLLING parameter, 7-11 TMP_ REMOTENAMINGEMLFILE parameter, 7-11 TMP_SDH_TERM_ SYNCHRONIZATION_AT_ STARTUP parameter, 7-11 TMP_SE_ACCESSCT parameter, 7-11 TMP_TRACELEVEL parameter, 7-12 TMP_ TRACEMAXLINECOUNT parameter, 7-12 TMP_WAIT_EOT_SYNCHRO_ STARTUP parameter, 7-12 TMP_WAIT_MPLS_ SYNCHRO_STARTUP parameter, 7-12 Tool See: Utilities Trace management log file location, 6-6 log file suffixes, 6-6 Traffic Classifier
Get extremities, 14-101
Create one-to-one-open protection, 16-173
Associate to an Ethernet Segment, 18-209
Inventory from tunnel, 16-134
Description, 16-166
Create, 18-160
List, 14-100
EVC setup, 16-178
Delete, 18-164
Overview, 14-99
Interconnection types, 16-167
T-MPLS LSP Tunnel, 11-10
Disassociate from an Ethernet Segment, 18-211
PW dual-point-to-point, 16-167
T-MPLS Tunnel
List, 18-158
Add constraint, 16-109
Redundancy creation types, 16-166
Modify, 18-162
Add PHB Profile, 16-113
Reference network, 16-166
Overview, 18-156
Allocate, 16-117
Reference scenarios, 16-168
Properties, 18-165
Bandwidth load, 16-136
Tunnel one-to-one-open, 16-166
Create, 16-101 Deimplement, 16-124 Delete, 16-106 Delete constraint, 16-111
TMP_NE_UNDER_ _MANAGEMENT parameter, 7-11
Traffic Descriptor Create, 18-146 Delete, 18-152 Details, 18-153 for MPLS, 15-5
.................................................................................................................................................................................................................................... 1350 OMS IN-19 8DG42227DAAA 9.6 Issue 3 December 2012
Index ....................................................................................................................................................................................................................................
List, 18-144
Transport Link for MPLS
Modify, 18-149
Bandwidth load, 15-33
Overview, 18-142
Define, 15-25
Traffic Descriptor for MPLS
Details, 15-31
Create, 15-8
Get extremities, 15-28
Delete, 15-15
Inventory, 15-36
Details, 15-16
List, 15-23
Inventory, 15-18
List from LSP Tunnel, 15-79
List, 15-6
Overview, 15-21
Modify, 15-12 Traffic descriptor management macro functions and default user profiles, 5-7 Traffic management, 11-45 See: Ethernet Transport Bridging (ETB) Also see: Functional domain overview EVC management, 11-53 Overview, 11-53 Policy Control, 11-64 VLAN management, 11-54 Also see: Ethernet Frame Hierarchy
Transport Link for T-MPLS Bandwidth load, 16-25 Define, 16-18 Details, 16-23 Get extremities, 16-20 Inventory, 16-28 List, 16-16 Overview, 16-14 Transport Link management Link Over Cable, 11-50 Link Over MPLS, 11-51 Link Over RPR, 11-51 Link Over TDM, 11-50
Traffic parameter See: Ethernet Edge Physical Port
Link Over T-MPLS, 11-51
Transparent transmission, 11-30, 11-31
macro functions and default user profiles, 5-7
Transport layer, 11-8 RPR ring, 11-11 SDH layer, 11-9 T-MPLS layer, 11-9 Transport Link, 18-184 Also see: Ethernet Transport Link Classification, 14-5 Concatenated VC, 14-11 List by domain, 14-104 Overview, 14-4
Link Over WDM, 11-51, 11-51
Transport Link Management macro functions and default user profiles, 5-12 Transport Link management, 11-50 Also see: Network Topology Construction TSS 5 See: In band management Tunnel Redundancy See: T-MPLS Tunnel Redundancy
............................................................. U UI_LANGUAGE parameter, 7-4
UNI See: User Network Interface (UNI) User Network Interface (UNI), 19-18 Also see: Bandwidth Profile All to One Bundling attribute, 11-12 Bundling Service attribute, 11-12 Service Multiplexing attribute, 11-13 User profiles (default) Color Profile management, 5-12 Customer management, 5-9 domain management, 5-3 ENE management, 5-4 Ethernet Edge Physical Port management, 5-10 Ethernet physical port, 5-5 Ethernet Segment management, 5-11 Ethernet Traffic Classifier management, 5-10 Ethernet Traffic Descriptor management, 5-10 Ethernet Transport Segment management, 5-11 EVC management, 5-9 External termination management, 5-5 Link over cable, 5-6 Link over MPLS, 5-6 Link over SDH, 5-5 LSP Tunnel management, 5-7 NE management, 5-4 Provider Network management, 5-13
.................................................................................................................................................................................................................................... 1350 OMS IN-20 8DG42227DAAA 9.6 Issue 3 December 2012
Index ....................................................................................................................................................................................................................................
SDH termination management, 5-4 Service management, 5-9 Service node management, 5-3 TMPLS management, 5-3 Traffic descriptor management, 5-7
............................................................. V VC LS management
macro functions and default user profiles, 5-8 VC-LSP, 15-81, 15-72 Also see: LSP Tunnel, List of VC-LSP
Transport Link management, 5-7, 5-12
Commission, 15-96
Utilities management, 5-6
Decommission, 15-98
VC LS management, 5-8
Deimplement, 15-94
VLAN Typemanagement, 5-13
Delete, 15-91
Users
Create, 15-85
Details, 15-102
VLAN configuration scenario, 12-75 VLAN Tag, 11-57 Also see: Ethernet Frame Hierarchy VLAN Tag Protocol Type, 11-62 Also see: Ethernet Frame Hierarchy Also see: VLAN Type Virtual Private Hub Service (VPHS), 11-8 Virtual Private Wire Service (VPWS), 12-62 PM management, 12-62
SEC User Administration, 2-2
Get extremities, 15-99
SEC User Authentication, 2-2
Implement, 15-92
Configure, 16-42
List, 15-18, 15-36, 15-83, 16-28
Create, 16-35
Utilities, 11-46 Also see: Functional domain overview AAR procedure, 23-3 Align Up, 23-15, 23-28
Modify, 15-89 Overview, 15-82
Alignment, 23-4, 23-26
Viewer, 11-71 Also see: System management
Audit, 23-3
Virtual Bridging, 11-8
audit on a NE, 23-20
Virtual concatenation, 11-31
Audit results, 23-8, 23-24
Virtual Local Area Network (VLAN)
Audit tool, 23-6 Force Alignment, 23-4 List of auditable NEs, 23-18 List of Audited NEs, 23-22 Overview, 23-3 Recovery, 23-5 Replacement, 23-30 Reservation, 23-4, 23-32 Start AAR procedure, 23-16 Stop AAR procedure, 23-17 Utilities management macro functions and default user profiles, 5-6
Virtual Transport
Deimplement, 16-46 Delete, 16-39 Details, 16-40 Get extremities, 16-48 Implement, 16-44 List, 16-33 Modify, 16-37 Overview, 16-31
Management, 11-54, 11-62 Also see: Ethernet Frame Hierarchy
VLAN See: Virtual Local Area Network
Mapping, 11-59 Also see: Ethernet Frame Hierarchy
Vlan and Priority based
Overview, 19-10
VLAN Id, 11-56 Also see: VLAN Management
pop, 11-57, 11-58 push, 11-57, 11-58 Push/Pop at ETS NNI Interface, 18-225
Frame Classification, 18-6 Also see: VLAN
VLAN Tag, 11-56 Also see: VLAN Management VLAN type
swap, 11-57, 11-58
Create, 18-248
Tunneling, 11-61 Also see: Ethernet Frame Hierarchy
Delete, 18-253 List, 18-247 Modify, 18-251
.................................................................................................................................................................................................................................... 1350 OMS IN-21 8DG42227DAAA 9.6 Issue 3 December 2012
Index ....................................................................................................................................................................................................................................
Overview, 18-246 VLAN Type Management macro functions and default user profiles, 5-13 VPHS, 11-33 See: Virtual Private Hub Service (VPHS) VPWS See: Virtual Private Wire Service VT association to fixed VT, 20-80 default VT, 20-79 VT Queue Profile create, 13-76 ............................................................. W Web Desktop, 11-38
Web Portal, 1-3, 2-2
.................................................................................................................................................................................................................................... 1350 OMS IN-22 8DG42227DAAA 9.6 Issue 3 December 2012
