ISA-ES1 - 4ENH 3.0 OPER - HDBK - Ed01 PDF

Alcatel-Lucent ISA Board
ETHERNET SWITCHING SYSTEM (ES1 & ES4) | RELEASE 3.0

CT OPERATOR’S GUIDE
P/N 8DG15785AAAA
JANUARY 2011
ISSUE 01
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 © 2011 Alcatel-Lucent. All Rights Reserved.
Notice
Every effort was made to ensure that this information product was complete and accurate at the time of printing. However, information is subject to change.
Trademarks
All trademarks and service marks specified herein are owned by their respective companies.
Conformance statement
Interference Information: Part 15 of FCC Rules

NOTE: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are
designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment
generates, uses, and can radiate radio frequency energy. If the equipment is not installed and used in accordance with the guidelines in this document, the
equipment may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference,
in which case the user will be required to correct the interference at the expense of the user.
Security Statement
In rare instances, unauthorized individuals make connections to the telecommunications network through the use of remote access features. In such an event,
applicable tariffs require that the customer pay all network charges for traffic. Alcatel-Lucent cannot be responsible for such charges and will not make any
allowance or give any credit for charges that result from unauthorized access.
Limited Warranty
For terms and conditions of sale, contact your Alcatel-Lucent Account Team.
Contents
About this document

Purpose ......................................................................................................................................................xxv
Reason for reissue .....................................................................................................................................xxv
Intended audience ......................................................................................................................................xxv
How to use this document .........................................................................................................................xxv
Safety information ................................................................................................................................... xxvi
Admonishments ............................................................................................................................. 1-xxvi
Conventions used ..................................................................................................................................... xxvi
Related documentation .......................................................................................................................... xxviii
Training ................................................................................................................................................. xxviii
Document support ................................................................................................................................. xxviii
Technical support .................................................................................................................................... xxix
How to order ............................................................................................................................................ xxix
How to comment ..................................................................................................................................... xxix
Packaging collection and recovery requirements .................................................................................... xxix
Recycling/take-back/disposal of product ................................................................................................ xxix
1 System generalities
ISA-ES1/4 System ..................................................................................................................................... 1-3
Ethernet Technique .................................................................................................................................. 1-18
MEF (Metro Ethernet Forum) Applications ............................................................................................ 1-19
Ethernet Private Line (EPL), end to end implementation example ......................................................... 1-21
E-Lan/E-VLan, end to end implementation example .............................................................................. 1-23
E-VPL, end to end implementation example .......................................................................................... 1-27
Protocols .................................................................................................................................................. 1-31
Data frames ....................................................................................................................................... 1-31
Protocol list ....................................................................................................................................... 1-38
STP functionality (Spanning Tree Protocol) ........................................................................................... 1-43
Virtual Concatenation and LCAS ............................................................................................................ 1-52
Internal Loop-Back management ............................................................................................................ 1-53
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA iii
Issue 01 January 2011
ISA ES1/4 Release 3.0
Contents
............................................................................................................................................................................................................................................................
System alarm management ..................................................................................................................... 1-54

CSF alarm management ................................................................................................................... 1-54
VC-AIS alarm management ............................................................................................................. 1-55
Auto-Negotiation management ............................................................................................................... 1-58
Flow-Control management ..................................................................................................................... 1-59
Port Mirroring management .................................................................................................................... 1-62
Resource Management Indication ........................................................................................................... 1-64
Bridging Data Plane ................................................................................................................................ 1-66
IGMP Snooping management .......................................................................................................... 1-66
IGMP Snooping Statistics ................................................................................................................ 1-67
Link Aggregation management ............................................................................................................... 1-68
Link Aggregation, implementation example .................................................................................... 1-72
Control Protocols management in a Transport Network ......................................................................... 1-74
Selective Tunnelling ......................................................................................................................... 1-74
Dual-homing ..................................................................................................................................... 1-75
Redundancy features ............................................................................................................................... 1-77
Dual-homing (via selective BPDU tunnelling) ................................................................................ 1-77
Network protections ................................................................................................................................ 1-79
Ethernet Ring Protection (ERP) ....................................................................................................... 1-79
Ethernet OAM ......................................................................................................................................... 1-86
Connectivity Fault Management ...................................................................................................... 1-86
Management software ............................................................................................................................. 1-88
Ethernet over SDH Management ...................................................................................................... 1-90
ES-CT main management menus ..................................................................................................... 1-94
2 Software Product and Licence
Software product and licenses description ................................................................................................ 2-2
Software products, licenses and part numbers .......................................................................................... 2-3
3 ES Software Installation
Software Version ....................................................................................................................................... 3-2
Start-up of the Personal Computer ............................................................................................................ 3-3
Host Computer Configuration ................................................................................................................... 3-4
Verification of IP address assignment for the host computer ............................................................. 3-5
Summary procedure for ES software installation ..................................................................................... 3-6
ES-CT Installation procedure .................................................................................................................... 3-8
NE-ES package installation procedure ................................................................................................... 3-28
............................................................................................................................................................................................................................................................
iv P/N 8DG15785AAAA
Contents
............................................................................................................................................................................................................................................................
Software Uninstallation procedure .......................................................................................................... 3-33

ES-CT Uninstallation ........................................................................................................................ 3-33
NE-ES software downloading ................................................................................................................. 3-36
Start-Up of the ES Craft Terminal management software ...................................................................... 3-40
4 Craft Terminal for ES1-ES4 Management

ES-CT summary ........................................................................................................................................ 4-2
Summary procedure for ES Management ................................................................................................. 4-4
Main view .................................................................................................................................................. 4-5
Resources TREE area (A1) ................................................................................................................. 4-7
List of the menus options ........................................................................................................................ 4-12
Views menu introduction .................................................................................................................. 4-13
Configuration menu introduction ..................................................................................................... 4-14
Diagnosis menu introduction ............................................................................................................ 4-14
Supervision menu introduction ......................................................................................................... 4-15
Mib-Management menu introduction ............................................................................................... 4-15
OAM Domain menu introduction ..................................................................................................... 4-15
Transmission menu introduction ...................................................................................................... 4-16
Connection menu introduction ......................................................................................................... 4-20
Performance menu introduction ....................................................................................................... 4-21
Help menu introduction .................................................................................................................... 4-23
Supervision management ........................................................................................................................ 4-24
Access state (allow or inhibit ES-Craft access) ................................................................................ 4-24
Set Manager list ................................................................................................................................ 4-25
Restart ISA (Not operative) .............................................................................................................. 4-25
Generic and common functions ............................................................................................................... 4-26
Options of Configuration menu ........................................................................................................ 4-26
Search in Views menu ....................................................................................................................... 4-28
Print in Views menu .......................................................................................................................... 4-32
Diagnosis and Alarms Configuration ...................................................................................................... 4-33
Alarms Severity (ASAP management) in Configuration menu ........................................................ 4-33
Set Alarms Severities ........................................................................................................................ 4-37
Loop Back Management in Configuration menu ............................................................................. 4-40
Allow/Inhibit Alarms Notifications .................................................................................................. 4-41
Alarms re-synchronization ................................................................................................................ 4-41
Alarms Surveillance (Diagnosis - Alarms option) ............................................................................ 4-41
Event Log Browser (Diagnosis - Log Retrieval) .............................................................................. 4-43
Navigation to EML-USM in Diagnosis menu .................................................................................. 4-46
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA v
Contents
............................................................................................................................................................................................................................................................
MIB Management ................................................................................................................................... 4-47

Backup/Restore DB .......................................................................................................................... 4-47
Compare two Backup Files .............................................................................................................. 4-48
Transmission ........................................................................................................................................... 4-49
Ethernet Ports denomination and numbering ................................................................................... 4-49
ETS Traffic Descriptor configuration ............................................................................................... 4-51
Traffic Descriptor, Forwarding Priority and Class of Service .......................................................... 4-54
GMII - MII Remote Interface Selection (ES4 board only) .............................................................. 4-60
Configure ISA .................................................................................................................................. 4-62
ISA Properties .................................................................................................................................. 4-64
ISA application table in the Transmission context ........................................................................... 4-65
Configure (local) Ethernet Port ........................................................................................................ 4-67
Ethernet Port (local) Properties ........................................................................................................ 4-78
Configure (remote) Ethernet Port ..................................................................................................... 4-80
Ethernet Port (remote) Properties ..................................................................................................... 4-91
Substitute Server Layer for an Ethernet Port .................................................................................... 4-92
Characterization Service of an Ethernet Port ................................................................................... 4-93
Traffic Management of an Ethernet Port .......................................................................................... 4-93
Traffic Management of an Aggregator ............................................................................................. 4-94
Configure ACL for an Ethernet Port ................................................................................................ 4-94
Properties ACL of an Ethernet Port .................................................................................................. 4-99
Disassociate ACL for an Ethernet Port ............................................................................................. 4-99
Create ETS InFlow for an Ethernet Port ........................................................................................ 4-100
Create ETS OutFlow for an Ethernet Port ...................................................................................... 4-103
Create ETS OutFlow / VLANManagement (not available) ........................................................... 4-104
Modify ETS InFlow ....................................................................................................................... 4-106
ETS InFlow Properties ................................................................................................................... 4-106
Modify ETS OutFlow ..................................................................................................................... 4-106
ETS OutFlow Properties ................................................................................................................. 4-106
Delete ETS InFlow ......................................................................................................................... 4-107
Delete ETS OutFlow ...................................................................................................................... 4-107
Create Eth2ETS Classifier .............................................................................................................. 4-107
Modify Classifier ............................................................................................................................ 4-110
Classifier Properties ........................................................................................................................ 4-111
Delete Classifier ............................................................................................................................. 4-111
Create Provider InFlow for an Ethernet Port .................................................................................. 4-112
Create Provider InFlow / S-VID Management ............................................................................... 4-114
Create Provider OutFlow for an Ethernet Port ............................................................................... 4-115
Substitute Client Layer for an Ethernet Port or an Aggregator ...................................................... 4-116
............................................................................................................................................................................................................................................................
vi P/N 8DG15785AAAA
Contents
............................................................................................................................................................................................................................................................
VLAN Registration ......................................................................................................................... 4-118

Resources Availability .................................................................................................................... 4-122
Configure Bridge Port (Provider) ................................................................................................... 4-125
Configure Bridge Port (Virtual) ...................................................................................................... 4-130
Configure Bridge Port (MAC) ........................................................................................................ 4-133
Regenerated User Priority for the BridgePort ................................................................................ 4-134
Default User Priority List of the Bridge Port .................................................................................. 4-136
Modify PVID (Port Vlan Identifier) of the Bridge Port ................................................................. 4-137
STP-Per Bridge Management by the ControlPlane of the Bridge Port .......................................... 4-137
STP-PerPort Management by the ControlPlane of the Bridge Port ............................................... 4-140
MST Region Management by CIST of the Bridge Port ................................................................. 4-144
MSTID Management by the MSTI of the Bridge Port ................................................................... 4-145
Bridge Port Properties of the Ethernet Port .................................................................................... 4-148
Show VLAN Info of the Ethernet Bridge Port ............................................................................... 4-149
Configure Queue for the Ethernet Port ........................................................................................... 4-150
Properties Queue for the Ethernet Port ........................................................................................... 4-152
Configure IGMP ............................................................................................................................. 4-155
IGMP Properties ............................................................................................................................ 4-158
Configure IGMP for the Ethernet Port ........................................................................................... 4-158
IGMP Properties for the Ethernet Port ........................................................................................... 4-159
Configure IGMP for the Aggregator .............................................................................................. 4-162
IGMP Properties of the Aggregator ................................................................................................ 4-162
Ethernet Ring Protection ................................................................................................................. 4-163
Configure Physical ERP (Topologies) ............................................................................................ 4-164
Configure Logical ERP (Instances) ................................................................................................ 4-173
Create Aggregator ........................................................................................................................... 4-193
Configure Aggregator ..................................................................................................................... 4-196
Aggregator Properties ..................................................................................................................... 4-201
Delete Aggregator ........................................................................................................................... 4-201
Configure an Aggregation Port ....................................................................................................... 4-202
Properties an Aggregation Port ....................................................................................................... 4-205
In Fiber In Band management for an Ethernet Port ........................................................................ 4-206
EFM Management for the Ethernet Port ........................................................................................ 4-210
OAM ...................................................................................................................................................... 4-217
Summary procedure for OAM configuration ................................................................................. 4-217
Configure Resources ....................................................................................................................... 4-218
Properties Resources ....................................................................................................................... 4-230
Configure ........................................................................................................................................ 4-230
Properties ........................................................................................................................................ 4-231
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA vii
Contents
............................................................................................................................................................................................................................................................
Configure LoopBack ...................................................................................................................... 4-232

Loop Back Properties ..................................................................................................................... 4-234
Connection ............................................................................................................................................ 4-235
Filtering Data Base for the Bridge .................................................................................................. 4-235
Create Ets XC One Step (MAC & Virtual) for the Ethernet Port ................................................... 4-242
Create Ets XC One Step (Provider) for the Ethernet Port .............................................................. 4-246
Delete Ets XC One Step (MAC & Virtual) for the Ethernet Port ................................................... 4-256
Delete ETS XC One Step (Provider) for the Ethernet Port ............................................................ 4-257
Create ETS XC for the ETS InFlow (not operative) ...................................................................... 4-260
Modify ETS XC for the ETS InFlow ............................................................................................. 4-260
ETS XC Properties for the ETS InFlow ......................................................................................... 4-261
Delete ETS XC for the ETS InFlow (not operative) ...................................................................... 4-261
Create ETS XC for the ETS OutFlow (not operative) .................................................................... 4-262
Modify ETS XC for the ETS OutFlow (not operative) .................................................................. 4-262
ETS XC Properties for the ETS OutFlow ...................................................................................... 4-262
Delete Ets XC for the ETS OutFlow .............................................................................................. 4-262
Performance .......................................................................................................................................... 4-263
Granularity 15Minutes/1Hour for the MPLS Switch ..................................................................... 4-263
Configure Eth. Aggr. for an Ethernet Port ...................................................................................... 4-264
Eth Aggr. Properties of an Ethernet Port ........................................................................................ 4-265
Configure InFlow for an ETS InFlow ............................................................................................ 4-267
InFlow Properties of an ETS InFlow .............................................................................................. 4-268
Configure OutFlow for an ETS OutFlow ....................................................................................... 4-270
OutFlow Properties of an ETS OutFlow ........................................................................................ 4-270
IGMP snooping statistics ............................................................................................................... 4-273
PM Data Results (HISTORY and MAINTENANCE) ................................................................... 4-289
5 Maintenance
General trouble-shooting flow-chart for ISA-ES boards .......................................................................... 5-2
Alarms, states and commands on ISA-ES board front cover .................................................................... 5-3
Troubleshooting by means of the ES Craft Terminal ................................................................................ 5-4
Alarms/states organization in the main view ...................................................................................... 5-5
Alarms synthesis indications .............................................................................................................. 5-6
Alarms indications in the Resources TREE area (A1) ....................................................................... 5-9
Alarms indications in the resource properties .................................................................................. 5-10
Alarms relevant to ES-Boards observable on SDH-CT ................................................................... 5-13
Alarms Surveillance (AS) ................................................................................................................. 5-14
ISA-ES Units replacement ...................................................................................................................... 5-18
Software Upgrading/Downgrading ......................................................................................................... 5-19
............................................................................................................................................................................................................................................................
viii P/N 8DG15785AAAA
Contents
............................................................................................................................................................................................................................................................
A Technical support
Purpose .............................................................................................................................................. A-1
Contents ............................................................................................................................................. A-1
Technical assistance ................................................................................................................................. A-2
Overview ............................................................................................................................................ A-2
Technical support ............................................................................................................................... A-3
On-line customer support .................................................................................................................. A-3
Accessing and navigating the On-Line Customer Support (OLCS) web site .......................................... A-7
Description ......................................................................................................................................... A-7
Accessing the OLCS web site ............................................................................................................ A-7
Obtaining a login for OLCS .............................................................................................................. A-7
View an OLCS website ...................................................................................................................... A-8
Other technical support services ............................................................................................................ A-12
The technical support services expert workshop series ................................................................... A-12
GL Glossary
Acronyms and Abbreviations .................................................................................................................GL-1
Terms and Definitions ..........................................................................................................................GL-17
IN Index
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA ix
Contents
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
x P/N 8DG15785AAAA
List of figures
1-1 ISA-ES subsystem, protocol stacking .......................................................................................... 1-7
1-2 Bridge representation example and relevant FDB table ............................................................... 1-8
1-3 System into SDH network, example ............................................................................................ 1-9
1-4 VLAN Bridge representation example and relevant FDB table ................................................. 1-10
1-5 Frames acceptance criteria ......................................................................................................... 1-11
1-6 MAC Bridge distribution domain (example) ............................................................................. 1-12
1-7 Virtual Bridge distribution domain (example) ........................................................................... 1-12
1-8 Provider Bridge distribution domain (example) ......................................................................... 1-13
1-9 Generic VLAN Classification-Identification-Aggregation (example) ....................................... 1-14
1-10 Stacked VLAN management (example) .................................................................................... 1-15
1-11 Transparent Mac/Virtual Port-to-Port XC “OneStep" (Example) .............................................. 1-15
1-12 End-to-End ETS link Example ................................................................................................... 1-17
1-13 MEF-Network application for OMSN+ISA-ES System ............................................................ 1-20
1-14 EPL application example ........................................................................................................... 1-22
1-15 Example of E-Lan/E-VLan implementation (1: centralized LAN) ............................................ 1-25
1-16 Example of E-Lan/E-VLan implementation (2: distributed LAN) ............................................ 1-26
1-17 EVPL implementation example ................................................................................................. 1-29
1-18 Ethernet Packet format ............................................................................................................... 1-31
1-19 Ethernet packet and MAC frame format .................................................................................... 1-31
1-20 Ethernet “Q-Tagged" MAC 802.3 frame format ........................................................................ 1-32
1-21 TCI Field format (802.1Q VLAN Tag) ...................................................................................... 1-32
1-22 Ethernet “Stacked VLAN" frame format ................................................................................... 1-33
1-23 Ethernet “Stacked VLAN" frame format ................................................................................... 1-34
1-24 Ethernet encapsulation into GFP frame (from G.7041/Y.1303) ................................................ 1-35
1-25 Ethernet/LAPS encapsulation (ITU-T X.86) ............................................................................. 1-35
1-26 Ethernet Framing (on Local Ethernet Port) ................................................................................ 1-36
1-27 Ethernet over SDH Framing (Remote Ethernet Port) ................................................................ 1-37
1-28 Spanning Tree example .............................................................................................................. 1-43
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA xi
List of figures
............................................................................................................................................................................................................................................................
1-29 Some examples of Bridges and Ports roles in xSTP network .................................................... 1-44
1-30 PER-VLAN Spanning Tree example ......................................................................................... 1-45
1-31 PER-VLAN Spanning Tree (example of active topology for a single VLAN) ......................... 1-46
1-32 MSTP BPDU Frame format ....................................................................................................... 1-47
1-33 MSTP Network topology example ............................................................................................ 1-48
1-34 MSTP “collapsed” topology example ........................................................................................ 1-50
1-35 MSTP, VLAN differentiated routing example ........................................................................... 1-51
1-36 Virtual Concatenation (example) ............................................................................................... 1-52
1-37 Internal Loop Back scheme ....................................................................................................... 1-53
1-38 CSF alarm management ............................................................................................................. 1-54
1-39 VC-AIS alarm management ....................................................................................................... 1-55
1-40 Configure (remote) EthernetPort: GFP: VC-AIS setting ........................................................... 1-57
1-41 Configure (local) EthernetPort: MAU: FlowControl and ShutDown disabling ......................... 1-57
1-42 Flow Control scheme ................................................................................................................. 1-60
1-43 Configure (local) EthernetPort: MAU: FlowControl setting ..................................................... 1-61
1-44 Port Mirroring example .............................................................................................................. 1-63
1-45 IGMP application example ........................................................................................................ 1-67
1-46 LACPDU Frame format ............................................................................................................. 1-71
1-47 Link Aggregation example ......................................................................................................... 1-72
1-48 Customer BPDU Selective Tunnelling capability ...................................................................... 1-75
1-49 Dual-homing BPDU STP - dual (PE) node ............................................................................... 1-77
1-50 Dual-homing BPDU (network) STP tunnel ............................................................................... 1-78
1-51 Dual-homing BPDU (local) STP tunnel .................................................................................... 1-78
1-52 ERP reference scheme in normal/idle state ............................................................................... 1-81
1-53 ERP reference scheme in failure state ....................................................................................... 1-81
1-54 Connectivity Fault Management ................................................................................................ 1-86
1-55 Protocol stack for ATM/MPLS/Ethernet over SDH management ............................................. 1-90
1-56 Example of management of an SDH network with SDH and ES traffic ................................... 1-91
1-57 OSI and IP addressing example ................................................................................................. 1-93

2-1 Management Software, generic structure .................................................................................... 2-2
3-1 Craft Terminal components versions ........................................................................................... 3-2
............................................................................................................................................................................................................................................................
xii P/N 8DG15785AAAA
List of figures
............................................................................................................................................................................................................................................................
3-2 Initial presentation intermediate screen ...................................................................................... 3-9

3-3 Selecting installation procedure (1st step) ................................................................................... 3-9
3-4 Craft Terminal master setup, list of detected Components on the media ................................... 3-10
3-5 Selecting Craft Terminal components (1st step) ........................................................................ 3-11
3-6 Software License agreement ...................................................................................................... 3-12
3-7 Existing previous ES-CT version uninstall ................................................................................ 3-13
3-8 Uninstall confirmation ............................................................................................................... 3-14
3-9 Uninstall previous ES-CT version successfully completed ....................................................... 3-14
3-10 Choose destination folder for ES-CT installation ...................................................................... 3-15
3-11 Setup type ................................................................................................................................... 3-16
3-12 Program Folder denomination .................................................................................................... 3-16
3-13 Start copying files and current settings summary ...................................................................... 3-17
3-14 Setup in progress, temporary windows sequence presentation .................................................. 3-18
3-15 Successive installation, temporary windows presentation ......................................................... 3-19
3-16 Installation procedure menu window (2nd step) ........................................................................ 3-20
3-17 Craft Terminal master setup, list of detected Components on the media ................................... 3-20
3-18 Selecting SNMPCT component ................................................................................................. 3-21
3-19 Existing different SNMPCT release to be uninstalled ............................................................... 3-22
3-20 Existing previous similar release to be maintained: REPAIRE ................................................. 3-23
3-21 SNMP CT Add On setup ............................................................................................................ 3-24
3-22 SNMPCT setup in progress temporary window ........................................................................ 3-25
3-23 Maintenance Finished ................................................................................................................ 3-26
3-24 SNMPCT installation completed ............................................................................................... 3-26
3-25 Selecting installation procedure (end step) ................................................................................ 3-27
3-26 Descriptor files administration ................................................................................................... 3-28
3-27 Software Package Administration-ES service specific .............................................................. 3-29
3-28 File-Browser for Software Package installation ......................................................................... 3-30
3-29 Software Package Administration - create Enhanced OMSN .................................................... 3-30
3-30 Software Package Administration - add ES service ................................................................... 3-31
3-31 Add/Remove Programs icon selection ....................................................................................... 3-33
3-32 Add/Remove Programs view ...................................................................................................... 3-34
3-33 Delete confirmation (example) ................................................................................................... 3-34
3-34 Delete completed (example) ...................................................................................................... 3-35
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA xiii
List of figures
............................................................................................................................................................................................................................................................
3-35 Download Initiate (example) ..................................................................................................... 3-36

3-36 Download confirmation box ...................................................................................................... 3-37
3-37 Download progress .................................................................................................................... 3-37
3-38 NE Software package activation (example) ............................................................................... 3-38
3-39 Activate SW package confirmation ........................................................................................... 3-38
3-40 SW package details .................................................................................................................... 3-39
3-41 1320CT software start-up .......................................................................................................... 3-40
3-42 NES view example ..................................................................................................................... 3-41
3-43 ES view example ........................................................................................................................ 3-42
3-44 Login dialog box ........................................................................................................................ 3-42
3-45 ISA USM starting ...................................................................................................................... 3-43
4-1 Logon view .................................................................................................................................. 4-3
4-2 Main view .................................................................................................................................... 4-7
4-3 TREE area example ..................................................................................................................... 4-8
4-4 Spontaneous information message example .............................................................................. 4-11
4-5 Set Manager list ......................................................................................................................... 4-25
4-6 Options of Configuration menu ................................................................................................. 4-27
4-7 Configuration -> Options - Program (“Full Window Mode" example) ..................................... 4-28
4-8 Configuration -> Options - Program (“Tabbed Window Mode" example) ................................ 4-28
4-9 Views -> Search ETS InFlow ..................................................................................................... 4-30
4-10 Views -> Search ETS OutFlow .................................................................................................. 4-30
4-11 Views -> Search Ethernet Port ................................................................................................... 4-31
4-12 Views -> Search Agg. Group ..................................................................................................... 4-31
4-13 Views -> Print ............................................................................................................................ 4-32
4-14 ASAP Management dialogue box. ............................................................................................ 4-34
4-15 ASAP - Severities profile example ............................................................................................ 4-35
4-16 ASAP: Set Alarm Severities (example) ..................................................................................... 4-39
4-17 Loop Back Management dialogue box ...................................................................................... 4-40
4-18 Alarms Surveillance (“ISA Alarms" example) .......................................................................... 4-42
4-19 Log Retrieval -> Event (Filter example) .................................................................................... 4-44
4-20 Log Retrieval -> Event (Report example) .................................................................................. 4-44
4-21 Log Retrieval -> Alarm (Filter example) ................................................................................... 4-45
............................................................................................................................................................................................................................................................
xiv P/N 8DG15785AAAA
List of figures
............................................................................................................................................................................................................................................................
4-22 Log Retrieval -> Alarm (Report example) ................................................................................. 4-45

4-23 MIBmanagement Ë Backup/Restore DB ................................................................................... 4-47
4-24 Backup info boxes ...................................................................................................................... 4-48
4-25 Backup/restore selection ........................................................................................................... 4-48
4-26 Configuration -> ETS Traffic Descriptor (example) .................................................................. 4-51
4-27 Create an ETS Traffic Descriptor (example) .............................................................................. 4-52
4-28 ETB Virtual/MAC Bridge Scheduling Mode ............................................................................. 4-57
4-29 5P3D Scheduling Mode (ETB ports) ......................................................................................... 4-58
4-30 8P0D Scheduling Mode (ETB ports) ......................................................................................... 4-59
4-31 MII or GMII interface selection ................................................................................................. 4-61
4-32 Configure ISA - System Info ..................................................................................................... 4-62
4-33 Configure ISA - Bridge Management ........................................................................................ 4-63
4-34 Configure ISA - MIB Default Value .......................................................................................... 4-64
4-35 Configure ISA - MTU/MRU ...................................................................................................... 4-64
4-36 ISA Properties ............................................................................................................................ 4-65
4-37 ISA-ES node: transmission application table ............................................................................. 4-66
4-38 Configure (local) Ethernet Port - Configuration ........................................................................ 4-70
4-39 Configure (local) Ethernet Port - MAU ..................................................................................... 4-73
4-40 Configure (local) Ethernet Port - L2 Control Frame .................................................................. 4-74
4-41 Configure (local) Ethernet Port - Port Mirroring ....................................................................... 4-75
4-42 Configure (local) Ethernet Port - Alarms ................................................................................... 4-76
4-43 List of Protocol Profile ............................................................................................................... 4-77
4-44 Create Protocol Profile ............................................................................................................... 4-78
4-45 (Local) Ethernet Port Properties ................................................................................................. 4-79
4-46 Configure (remote) Ethernet Port - Configuration ..................................................................... 4-83
4-47 Configure (remote) Ethernet Port - GFP .................................................................................... 4-85
4-48 Configure (remote) Ethernet Port - L2 Control Frame .............................................................. 4-86
4-49 Configure (remote) Ethernet Port - Alarms ................................................................................ 4-86
4-50 Configure (remote) Ethernet Port (LAPS) ................................................................................. 4-87
4-51 Rate Limiting Combination example (VC4 case) ...................................................................... 4-89
4-52 Virtual Concatenation Granularity example (MII, VC12 case) ................................................. 4-90
4-53 Inconsistency error on Port Configuration ................................................................................. 4-90
4-54 (Remote) Ethernet Port Properties ............................................................................................. 4-91
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA xv
List of figures
............................................................................................................................................................................................................................................................
4-55 Substitute Server Layer (from GFP to LAPS) ........................................................................... 4-92

4-56 Substitute Server Layer (from LAPS to GFP) ........................................................................... 4-92
4-57 Configure ACL ........................................................................................................................... 4-94
4-58 ACL list setting .......................................................................................................................... 4-96
4-59 ACL/ACE setting ....................................................................................................................... 4-99
4-60 Port: ACL Properties .................................................................................................................. 4-99
4-61 Port: Disassociate ACL ............................................................................................................ 4-100
4-62 Create ETS InFlow ................................................................................................................... 4-102
4-63 Create ETS OutFlow ................................................................................................................ 4-104
4-64 Create VLAN Management ..................................................................................................... 4-105
4-65 Delete ETS InFlow ................................................................................................................... 4-107
4-66 Create Eth2ETS Classifier ....................................................................................................... 4-110
4-67 Create Provider InFlow ............................................................................................................ 4-113
4-68 Provider Inflow: S-VID Filter .................................................................................................. 4-114
4-69 Create Provider OutFlow ......................................................................................................... 4-116
4-70 Substitute Port Type (from ETS to ETB) ................................................................................. 4-117
4-71 Substitute Port Type (from ETB to ETS) ................................................................................. 4-117
4-72 Substitute Client Type (from ETS to Link Aggregator) .......................................................... 4-117
4-73 VLAN Registration .................................................................................................................. 4-119
4-74 Static VLAN Registration Management (Provider case) ......................................................... 4-121
4-75 Resource Availability pop-up menu ......................................................................................... 4-122
4-76 Resource Availability Group 1 and Group 2 ............................................................................ 4-123
4-77 Configure Provider Bridge Port (“PERVLANSTP" case) ....................................................... 4-129
4-78 Configure Bridge Port (Provider case/MSTP) ......................................................................... 4-129
4-79 Configure Bridge Port (Virtual case/PERVLANSTP) ............................................................. 4-132
4-80 Configure MAC Bridge Port .................................................................................................... 4-134
4-81 Bridge Port: Regenerated Priority List .................................................................................... 4-135
4-82 Bridge Port: Default User Priority ........................................................................................... 4-136
4-83 BridgePort: Modify Port VLAN Identifier (PVID) ................................................................. 4-137
4-84 BridgePort: STP-PerBridge Management ................................................................................ 4-140
4-85 BridgePort: STP-PerBridge Management (MSTI case) .......................................................... 4-140
4-86 BridgePort: STP-PerPort Management .................................................................................... 4-143
4-87 BridgePort: STP-PerPort Management (MSTI case) ............................................................... 4-143
............................................................................................................................................................................................................................................................
xvi P/N 8DG15785AAAA
List of figures
............................................................................................................................................................................................................................................................
4-88 Bridge Port: CIST: MST Region Management ........................................................................ 4-145

4-89 Bridge Port: CIST: MST Region List ....................................................................................... 4-145
4-90 Bridge Port: MSTI: MSTI Management .................................................................................. 4-147
4-91 Bridge Port: MSTI: MSTID/VLAN Assignment ..................................................................... 4-147
4-92 Bridge Port: MSTI: MSTID/VLAN List .................................................................................. 4-147
4-93 Bridge Port Properties (Provider/MSTP case) ......................................................................... 4-148
4-94 Show VLAN Info ..................................................................................................................... 4-149
4-95 Queue (QoS) Management ....................................................................................................... 4-152
4-96 QoS Management: Forwarding Class Number ........................................................................ 4-152
4-97 QoS Management: Queue Number .......................................................................................... 4-152
4-98 Queue (QoS) Properties ........................................................................................................... 4-154
4-99 QoS Properties: Forwarding Class Mapping ............................................................................ 4-154
4-100 QoS Properties: Queue Number List ........................................................................................ 4-154
4-101 ISA: IGMP Snooping Management List .................................................................................. 4-156
4-102 ISA: IGMP Snooping, VLAN association ............................................................................... 4-157
4-103 Port: IGMP Services Management ........................................................................................... 4-159
4-104 Port: IGMP Services Properties List ........................................................................................ 4-161
4-105 Port: IGMP Request Membership Group ................................................................................. 4-161
4-106 Pop-up menu ERP Management .............................................................................................. 4-163
4-107 Configure ERP - Topologies .................................................................................................... 4-164
4-108 Create Ethernet Ring Protection Topology, LAG and Ethernet Interfaces .............................. 4-166
4-109 Create ERP Topology, Ethernet Interfaces ............................................................................... 4-167
4-110 Create ERP Topology, LAG Interfaces - Interconnection Node as true ................................... 4-168
4-111 Search LAG or Ethernet Interfaces .......................................................................................... 4-169
4-112 Modify ERP Topology, Ethernet Interfaces ............................................................................. 4-170
4-113 Modify ERP Topology, Ethernet Interface - Interconnection Node as True ............................ 4-171
4-114 Modify EERP Topology, LAG Interface - Interconnection Node as True ............................... 4-172
4-115 Delete EERP Topology - Confirmation Message ..................................................................... 4-173
4-116 Configure ERP - Instances ....................................................................................................... 4-173
4-117 Create ERP Instance - Configuration Tab ................................................................................ 4-175
4-118 Search ERP Topology .............................................................................................................. 4-177
4-119 Search ERP Topology - No selection ....................................................................................... 4-178
4-120 Create ERP Instance - Defects tab ........................................................................................... 4-179
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA xvii
List of figures
............................................................................................................................................................................................................................................................
4-121 Modify ERP Instance - Configuration tab .............................................................................. 4-180

4-122 Modify ERP Instance - Defects tab ......................................................................................... 4-182
4-123 Modify ERP Instance - Interfaces tab (Major Ring) ................................................................ 4-183
4-124 Modify ERP Instance - Interfaces Tab (sub Ring) ................................................................... 4-184
4-125 Search Mep with direction down ............................................................................................. 4-185
4-126 Modify ERP Instance - Alarms tab .......................................................................................... 4-186
4-127 Remove ERP Instance - Message ........................................................................................... 4-186
4-128 Properties ERP Instance - Configuration tab .......................................................................... 4-187
4-129 Properties ERP Instance - Defects tab ..................................................................................... 4-187
4-130 Properties ERP Instance - Interfaces tab .................................................................................. 4-188
4-131 Properties ERP Instance - Alarms tab ...................................................................................... 4-188
4-132 Modify ERP Instance - Configuration Tab - Scope as perVLAN ............................................ 4-189
4-133 Management Traffic VLAN ..................................................................................................... 4-189
4-134 Create Traffic VLAN ............................................................................................................... 4-191
4-135 Modify Traffic VLAN .............................................................................................................. 4-191
4-136 Delete Traffic VLAN ............................................................................................................... 4-192
4-137 Aggregator: Creation ............................................................................................................... 4-195
4-138 Aggregator: Set Protocol List .................................................................................................. 4-195
4-139 Aggregator: Configure Aggregator/Configuration ................................................................... 4-199
4-140 Aggregator: Configure Aggregator/Information ...................................................................... 4-200
4-141 Aggregator: Configure Aggregator/Alarm ............................................................................... 4-200
4-142 Aggregator Properties .............................................................................................................. 4-201
4-143 Delete Aggregator .................................................................................................................... 4-202
4-144 Aggregation Port: Configure .................................................................................................... 4-205
4-145 Aggregation Port: Set Actor Admin Key ................................................................................. 4-205
4-146 Aggregation Port: Properties .................................................................................................... 4-206
4-147 Create the In Fiber In Band ..................................................................................................... 4-207
4-148 Modify the In Fiber In Band ................................................................................................... 4-208
4-149 Delete In Fiber In Band ............................................................................................................ 4-209
4-150 Properties of the In Fiber In Band ........................................................................................... 4-210
4-151 Configuration of the EFM ....................................................................................................... 4-211
4-152 Statistics of the EFM ............................................................................................................... 4-214
4-153 Alarms of the EFM ................................................................................................................. 4-215
............................................................................................................................................................................................................................................................
xviii P/N 8DG15785AAAA
List of figures
............................................................................................................................................................................................................................................................
4-154 EFM Properties ....................................................................................................................... 4-216

4-155 OAM: Configure Resources ..................................................................................................... 4-218
4-156 OAM: Configure Resources: Create MD ................................................................................. 4-218
4-157 OAM: Configure Resources: Delete MD ................................................................................. 4-219
4-158 OAM: Configure Resources: MA Navigation .......................................................................... 4-220
4-159 OAM: Configure: MA Navig.: Create MA .............................................................................. 4-220
4-160 OAM: Configure: MA Navig.: Create: Vid ............................................................................. 4-221
4-161 OAM: Configure: MA Navig.: MEP Navigation .................................................................... 4-222
4-162 OAM: Configure: MA Navig.: MEP Navigation: Create MEP ............................................... 4-223
4-163 OAM: Configure: MA Navig.: MEP Navigation: Loop Back ................................................ 4-224
4-164 OAM: Configure: MA Navig.: MEP Navigation: Link Trace ................................................ 4-225
4-165 OAM: Configure: MA Navig.: MEP Navigation: Details ....................................................... 4-226
4-166 OAM: Configure: MA Navig.: Show All MEP ....................................................................... 4-227
4-167 OAM: Configure: MA Navig.: MA-MEP List ID .................................................................. 4-228
4-168 OAM: Configure: MA Navig.: Modify ................................................................................... 4-228
4-169 OAM: Configure: MA Navig.: Modify: Show ........................................................................ 4-229
4-170 OAM: Configure: MA Navig.: Details .................................................................................... 4-229
4-171 OAM: Configure: MA Navig.: Delete .................................................................................... 4-230
4-172 OAM: Properties Resources ..................................................................................................... 4-230
4-173 OAM: Configure ...................................................................................................................... 4-231
4-174 OAM: Properties ...................................................................................................................... 4-232
4-175 OAM: Configure LoopBack ..................................................................................................... 4-232
4-176 OAM: Configure Loop Back: Test List ................................................................................... 4-233
4-177 OAM: Configure Loop Back: Test List: Modify ...................................................................... 4-234
4-178 OAM: Loop Back Properties .................................................................................................... 4-234
4-179 Filtering Data Base/Dynamic Filtering Database (Virtual Bridge case) .................................. 4-237
4-180 Filtering Data Base/Static Unicast Filtering (Virtual Bridge case) .......................................... 4-239
4-181 Filtering Data Base/Static Multicast Filtering (Virtual Bridge case) ....................................... 4-240
4-182 Filtering Data Base/Dynamic Multicast Filtering (Virtual Bridge case) ................................. 4-241
4-183 Filtering Data Base/Learned Mac Address Details .................................................................. 4-241
4-184 Ethernet Port: Connection application table ............................................................................ 4-242
4-185 Create Ets XC “OneStep" ........................................................................................................ 4-245
4-186 Error message on “Create Ets XC OneStep" ........................................................................... 4-245
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA xix
List of figures
............................................................................................................................................................................................................................................................
4-187 Topology for “Create Ets XC OneStep" (Provider) ................................................................. 4-247

4-188 Create Ets XC “OneStep" (Provider, UNI-NNI) ..................................................................... 4-252
4-189 Topology Classification Properties .......................................................................................... 4-252
4-190 SVID Filter ............................................................................................................................... 4-253
4-191 Protocol List ............................................................................................................................. 4-253
4-192 Create Ets XC “OneStep" (Provider, NNI-UNI) ..................................................................... 4-253
4-193 List of Color Profile ................................................................................................................. 4-254
4-194 Create Color Profile ................................................................................................................. 4-255
4-195 Delete Ets XC “OneStep" (MAC & Virtual) ........................................................................... 4-257
4-196 Topology for Delete Ets XC “OneStep" (Provider) ................................................................. 4-258
4-197 Delete Ets XC “OneStep" (Provider, UNI-NNI) ..................................................................... 4-259
4-198 Delete Ets XC “OneStep" (Provider, NNI-UNI) ..................................................................... 4-260
4-199 Ets XC Properties ..................................................................................................................... 4-261
4-200 Ethernet Port Configure Monitoring (example) ....................................................................... 4-265
4-201 Ethernet Port Monitoring Properties (example) ....................................................................... 4-266
4-202 InFlow Configure Monitoring (example) ................................................................................. 4-268
4-203 InFlow Monitoring Properties (example) ................................................................................ 4-269
4-204 OutFlow Configure Monitoring (example) .............................................................................. 4-270
4-205 OutFlow Monitoring Properties (example) .............................................................................. 4-272
4-206 IGMP snooping statistics (Node resource) .............................................................................. 4-273
4-207 IGMP <VLAN> creation (Node resource) .............................................................................. 4-274
4-208 IGMP <VLAN> searching (Node resource) ............................................................................ 4-274
4-209 IGMP <VLAN> modification (Node resource) ....................................................................... 4-275
4-210 IGMP <VLAN> properties (Node resource) ........................................................................... 4-276
4-211 IGMP <VLAN>15 minutes properties (Node resource) ......................................................... 4-276
4-212 IGMP <VLAN> 24 hours properties (Node resource) ............................................................ 4-277
4-213 IGMP snooping statistics (Port resource) ................................................................................ 4-278
4-214 IGMP <VLAN> creation (Port resource) ................................................................................ 4-279
4-215 IGMP <VLAN> searching (Port resource) .............................................................................. 4-280
4-216 IGMP <VLAN> modification (Port resource) ......................................................................... 4-281
4-217 IGMP <VLAN> properties (Port resource) ............................................................................. 4-282
4-218 IGMP <VLAN>15 minutes properties (Port resource) ........................................................... 4-282
4-219 IGMP <VLAN> 24 hours properties (Port resource) .............................................................. 4-283
............................................................................................................................................................................................................................................................
xx P/N 8DG15785AAAA
List of figures
............................................................................................................................................................................................................................................................
4-220 IGMP <VLAN, Multicast> creation (Node resource) ............................................................. 4-284

4-221 IGMP <VLAN, Multicast> searching (Node resource) ........................................................... 4-285
4-222 IGMP <VLAN, Multicast> modification (Node resource) ...................................................... 4-286
4-223 IGMP <VLAN, Multicast> properties (Node resource) .......................................................... 4-287
4-224 IGMP <VLAN, Multicast>15 minutes properties (Node resource) ........................................ 4-288
4-225 IGMP <VLAN, Multicast> 24 hours properties (Node resource) ........................................... 4-288
4-226 PM data results (Port example) ................................................................................................ 4-291
4-227 PM data results (InFlow example) ........................................................................................... 4-291
5 Maintenance
5-1 General Flow-chart for ISA-ES board troubleshooting ............................................................... 5-2
5-2 Alarms/statuses organization in the main-view ........................................................................... 5-5
5-3 TREE area example ...................................................................................................................... 5-9
5-4 Example of Ethernet Port Properties alarms .............................................................................. 5-11
5-5 Example of alarms reported in the “resource information area A3" .......................................... 5-12
5-6 AlarmsSurveill.-“Counter Summary" window (“ISA Alarms" example) .................................. 5-14
5-7 AlarmsSurveill.-“Alarm Sublist" window (“ISA Alarms" example) ......................................... 5-15
A Technical support
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA xxi
List of figures
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
xxii P/N 8DG15785AAAA
List of tables
About this document

1 Alcatel-Lucent ISA ES1/4 Documentation Set ........................................................................ xxviii
1-1 Ethernet layer stack over SDH ..................................................................................................... 1-3
1-2 Allowed board .............................................................................................................................. 1-7
1-3 L2 Control Protocols .................................................................................................................. 1-38
1-4 IEEE 802.3 Slow Protocols ........................................................................................................ 1-39
2-1 Software product part number ...................................................................................................... 2-3
2-2 Software licenses part numbers ................................................................................................... 2-3

4-1 Alarms & Severities association in predefined ASAPs.............................................................. 4-37
4-2 Typical association between TD, UP and P-CoS (ETB ports MAC/Virtual Bridge .................. 4-57
4-3 Provider Bridge - Traffic Scheduling in 5P3D mode (ETB ports) ............................................. 4-58
4-4 Provider Bridge - Traffic Scheduling in 8P0D mode (ETB ports) ............................................. 4-59
4-5 Traffic Descriptor, Policing Mode and Color Profile for INFLOW resource: ......................... 4-255
5 Maintenance
5-1 Alarms colors and Severity association ....................................................................................... 5-7
5-2 Colors of the Management States when in “abnormal" condition (alarmed) .............................. 5-7
5-3 Severity Alarms Synthesis indications ......................................................................................... 5-7
5-4 Domain Alarm Synthesis indication ............................................................................................ 5-8
5-5 Management States Control Panel ............................................................................................... 5-8
5-6 Alarms Surveillance information general description ................................................................ 5-16
5-7 “Probable Cause" of alarms and relevant maintenance actions ................................................. 5-17
5-8 DIP-SWITCHES operations ...................................................................................................... 5-18
A Technical support
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA xxiii
List of tables
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
xxiv P/N 8DG15785AAAA
About this document
Purpose
This document provides general information and operational procedures common to all
Alcatel-Lucent ISA Board ES1 & ES4 (Alcatel-Lucent ISA ES1/4).
Reason for reissue

This document is the first issue of Release 3.0.
History
Issue Date Reason

01 January 2011 First validated issue of this guide
Intended audience
This Operator Handbook is intended primarily for telecommunications technicians and
communications network providers.
It is a common handbook for several equipment of different product–releases using ISA
ES1 or ISA ES4 product. The use of this handbook is indicated in the list of the Technical
Handbook of the Network Element, as listed in Table 1, (pg. 1-xxviii). This handbook is
not applied to a specific Network Element product–release; being the document dedicated
to a set of equipment, screens are inserted as "example" and can be extracted from any of
the referred equipment. Handbooks relevant to software applications (typically the
Operator's Handbooks) are not modified unless the new software "version" distributed to
Customers implies man-machine interface changes or in case of slight modifications not
affecting the understanding of the explained procedures.
How to use this document

This manual is divided into several chapters and it is useful to the trained operator or
system administrator.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA xxv
ISA ES1/4 Release 3.0 About this document
............................................................................................................................................................................................................................................................
Safety information
This information contains hazard statements for your safety. Hazard statements are given
at points where risks of damage to personnel, equipment, and operation may exist. Failure
to follow the directions in a hazard statement may result in serious consequences.
Safety precautions
Adhere to the following safety precautions:
• Electrostatic discharge (ESD)
You must be properly grounded when making contact with the Alcatel-Lucent ISA Board
ES1 & ES4 frame and handling circuit packs, disk drives, and tapes. Wrist strap ground
cords should be routinely tested for the minimum 1-megohm resistance.
• Plug-in storage
Circuit packs should be stored in static-safe packaging or in a grounded cabinet.
Admonishments
To avoid hazardous conditions, observe the following admonishments:
DANGER
Possibility of personal injury.
CAUTION
Possibility of service interruption.
WARNING
Possibility of equipment damage.
Conventions used
The following typographical conventions are used in this guide:
Appearance Description
italicized text • File and directory names
• Emphasized information
• Titles of publications
• A value that the user supplies
italicized bold text • Emphasized information
• A value that the user supplies
............................................................................................................................................................................................................................................................
xxvi P/N 8DG15785AAAA
About this document ISA ES1/4 Release 3.0
............................................................................................................................................................................................................................................................
Appearance Description
GUI reference or key name • Text that is displayed in a graphical user
interface or in a hardware label
• The name of a key on the keyboard
input text Command names and text that the user types or
selects as input to a system
output text Text that a system displays or prints
Î Next selection in pull down menu
For the remainder of this document, “Alcatel-Lucent ISA ES1/4” is used in place of
Alcatel-Lucent ISA Board ES1 & ES4 in most cases.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA xxvii
............................................................................................................................................................................................................................................................
Related documentation
This Handbook is always supplied with Technical Handbook and CT Operator's
Handbook dedicated to the specific Network Element. Each manual has its own Part
number.
Example of Equipment 1660SM Rel. 5.5.
The following table provide additional information about the Alcatel-Lucent ISA Board:
Table 1 Alcatel-Lucent ISA ES1/4 Documentation Set
Document Number Document Title

3AL 79551 AAAA 1320CT-Basic Operator Handbook (Version 3.x
3AL 88876 AAAA AS Operator's Handbook
3AL 88877 AAAA ELB Operator's Handbook
OMSN - Operator Handbooks
Alcatel-Lucent 1640FOX Operator Handbook
In the suitable
Alcatel-Lucent 1650SMC Operator Handbook
release
Alcatel-Lucent 1660SM Operator Handbook
OMSN-Technical Handbooks
Alcatel-Lucent 1640FOX Technical Handbooks
In the suitable
Alcatel-Lucent 1650SMC Technical Handbooks
release
Alcatel-Lucent 1660SM Technical Handbooks
Training
Alcatel-Lucent University provides courses for system planning, engineering, and
ordering, as well as courses to train telecommunications technicians in installation,
operations, and maintenance. Suitcasing of these courses is also available. Contact
Alcatel-Lucent University at 1 (888) 582-3688 to enroll in training classes. To arrange
suitcase sessions, call the Product Training Manager at 1 (800) 432-6317 (within USA) or
+1 (614) 764-5542 (worldwide). For a list of available courses, see the Alcatel-Lucent
University web site at https://training.alcatel-lucent.com.
Document support
Alcatel-Lucent provides a referral telephone number for document support. Use this
number to report errors or to ask questions about the document. This is a non-technical
number. The referral number is 1 (888) 727-3615 (continental United States) or +1 (630)
713-5000 (for all countries).
............................................................................................................................................................................................................................................................
xxviii P/N 8DG15785AAAA
About this document ISA ES1/4 Release 3.0
............................................................................................................................................................................................................................................................
Technical support
For technical support, contact your local Alcatel-Lucent customer support team. See the
Alcatel-Lucent Support web site (http://alcatel-lucent.com/support) for contact
information. For more information, refer to Refer to Appendix A, “Technical support” for
more information.
How to order
To order Alcatel-Lucent documents, contact your local sales representative or use Online
Customer Support (OLCS) (https://support.alcatel-lucent.com).
How to comment
To comment on this information product, go to the Online Comment Form
(http://infodoc.alcatel-lucent.com/comments/enus/) or email your comments to the
Comments Hotline (comments@alcatel-lucent.com).
Packaging collection and recovery requirements

Countries, states, localities, or other jurisdictions may require that systems be established
for the return and/or collection of packaging waste from the consumer, or other end user,
or from the waste stream. Additionally, reuse, recovery, and/or recycling targets for the
return and/or collection of the packaging waste may be established.
For more information regarding collection and recovery of packaging and packaging
waste within specific jurisdictions, please contact the Alcatel-Lucent Field
Services/Installation - Environmental Health and Safety organization.
For installations not performed by Alcatel-Lucent, please contact the Alcatel-Lucent
Customer Support Center at:
Technical Support Services, Alcatel-Lucent
• Within the United States: 1 (866) 582-3688, prompt 1
• From all other countries: +1 (630) 224 4672, prompt 2
Recycling/take-back/disposal of product
Electronic products bearing or referencing the symbol shown below, when put on the
market within the European Union, shall be collected and treated at the end of their useful
life in compliance with applicable European Union and local legislation. They shall not be
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA xxix
............................................................................................................................................................................................................................................................
disposed of as part of unsorted municipal waste. Due to materials that may be contained in
the product, such as heavy metals or batteries, the environment and human health may be
negatively impacted as a result of inappropriate disposal.
Note: In the European Union, a solid bar under the crossed-out

wheeled bin indicates that the product was put on the market after
13 August 2005.
Moreover, in compliance with legal requirements and contractual agreements, where
applicable, Alcatel-Lucent will offer to provide for the collection and treatment of Alcatel-
Lucent products at the end of their useful life. Alcatel-Lucent will also offer to provide for
the collection and treatment of existing products displaced by Alcatel-Lucent equipment.
For information regarding take-back of equipment by Alcatel-Lucent, or for more
information regarding the requirements for recycling/disposal of product, please contact
your Alcatel-Lucent Account Manager or Alcatel-Lucent Take-Back Support at
takeback@alcatel-lucent.com.
............................................................................................................................................................................................................................................................
xxx P/N 8DG15785AAAA
Overview
This chapter describes the main features of the graphical interface for the Alcatel-Lucent
ISA Board ES1 & ES4 Operator and provides a general overview of the system
architecture.
All the manuals describe menus, but not necessarily all the options of these menus. When
a menu option is not detailed in a manual, the information is given in another manual.
This chapter provides information on the following topics:
• “ISA-ES1/4 System” (p. 1-3)
• “Example of end-to-end ETS link creation” (p. 1-16)
• “Ethernet Technique” (p. 1-18)
• “Ethernet Technique” (p. 1-18)
• “Ethernet Private Line (EPL), end to end implementation example” (p. 1-21)
• “E-Lan/E-VLan, end to end implementation example” (p. 1-23)
• “E-VPL, end to end implementation example” (p. 1-27)
• “Protocols” (p. 1-31)
• “Data frames” (p. 1-31)
• “Customer BPDU” (p. 1-39)
• “Slow Protocols” (p. 1-39)
• “802_1X” (p. 1-40)
• “Bridge management” (p. 1-40)
• “Provider GVRP” (p. 1-41)
• “Customer GMRP” (p. 1-41)
• “Customer GARP” (p. 1-42)
• “STP functionality (Spanning Tree Protocol)” (p. 1-43)
• “Virtual Concatenation and LCAS” (p. 1-52)
• “Internal Loop-Back management” (p. 1-53)
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-1
ISA ES1/4 Release 3.0 System generalities
CT Operator’s Guide Overview
............................................................................................................................................................................................................................................................
• “System alarm management” (p. 1-54)

• “CSF alarm management” (p. 1-54)
• “VC-AIS alarm management” (p. 1-55)
• “Auto-Negotiation management” (p. 1-58)
• “Flow-Control management” (p. 1-59)
• “Port Mirroring management” (p. 1-62)
• “Resource Management Indication” (p. 1-64)
• “Bridging Data Plane” (p. 1-66)
• “IGMP Snooping management” (p. 1-66)
• “IGMP Snooping Statistics” (p. 1-67)
• “Link Aggregation management” (p. 1-68)
• “Link Aggregation, implementation example” (p. 1-72)
• “Control Protocols management in a Transport Network” (p. 1-74)
• “Selective Tunnelling” (p. 1-74)
• “Dual-homing” (p. 1-75)
• “Redundancy features” (p. 1-77)
• “Dual-homing (via selective BPDU tunnelling)” (p. 1-77)
• “Network protections” (p. 1-79)
• “Ethernet Ring Protection (ERP)” (p. 1-79)
• “Ethernet OAM” (p. 1-86)
• “Connectivity Fault Management” (p. 1-86)
• “Management software” (p. 1-88)
• “Ethernet over SDH Management” (p. 1-90)
• “ES-CT main management menus” (p. 1-94)
............................................................................................................................................................................................................................................................
1-2 P/N 8DG15785AAAA
System generalities ISA ES1/4 Release 3.0
ISA-ES1/4 System CT Operator’s Guide
............................................................................................................................................................................................................................................................
ISA-ES1/4 System
Alcatel-Lucent ISA-ES (Integrated Services Adapter - Ethernet Switching) is a system
operating at layer 2 by means of the MAC protocol. It acts as an Ethernet Switch (or
bridge), used to connect different LAN's between them. The LAN's may be local or
remote, where remote LAN's are linked using the existing SDH physical backbone, by
means of the EOS (Ethernet Over SDH/SONET) procedure.
For more information about Ethernet/MAC refer to IEEE 802.3 standard.
Table 1-1 Ethernet layer stack over SDH
3 NETWORK any network “packetized" data service

2 DATA LINK ETHERNET
1 PHYSICAL SDH
The Alcatel-Lucent ES system can manage packets data streams transported over “local"
Ethernet FE or GbE (Fast Ethernet, Gigabit Ethernet) and “remotized" ethernet over
GFP/SDH or LAPS/SDH; the GbE port is available only on ES4 boards.
Two types of ES boards are foreseen:
• ISA-ES1 (with an SDH equivalent capacity of 1 VC4, 8 Fast Ethernet Local ports and
8 Remote ports),
• ISA-ES4 (with an SDH equivalent capacity of 4 VC4, 8 Fast Ethernet Local ports, 1
Giga Ethernet Local port, and 16 Remote MIII ports or 2 Remote GMII ports).
The two boards are differentiated also by other features that will be explained, in this
handbook, as they come across in the configurations of the single features.
The bridge function may be carried out by means of the MAC autolearning procedure
(802.1D Rec.) or by means of manual “engineered" point-to-point connections.
The Ethernet Bridge representation is schematically illustrated in Figure 1-2, (pg. 1-8)
and also Figure 1-6, (pg. 1-12). The insertion of the ES Bridge into the SDH network is
illustrated in Figure 1-3, (pg. 1-9).
ES system can act also as a Virtual Bridge (802.1Q Rec.) or as a Provider Bridge
(802.1ad/D1.3 Rec.) managing the VLAN (user tag) and S-VLAN (provider tag) fields of
the MAC frame (also called “VLAN-tagged MAC frames"); in this way it can further
support the SLA with differentiated CoS.
The use of VLAN permits the aggregation of many users over a single virtual circuit, also
if they are not physically tied on the same physical segment, and can communicate each
other as if they were on the same LAN. In this way, users may also move from a segment
to another without changing their physical address.
............................................................................................................................................................................................................................................................
CT Operator’s Guide ISA-ES1/4 System
............................................................................................................................................................................................................................................................
The Virtual Bridge representation is schematically illustrated in Figure 1-6, (pg. 1-12)
See also Figure 1-7, (pg. 1-12).
A Provider Bridge application is illustrated in Figure 1-8, (pg. 1-13).
Some generic examples about VLAN and S-VLAN utilization (in engineered mode) are
reported in Figure 1-9, (pg. 1-14). and Figure 1-10, (pg. 1-15).
For more details about VLAN/LLC refer to IEEE 802.1Q standard.
Furthermore it accomplishes the functions requested by the Spanning Tree Protocol (STP,
RSTP, PerVLAN-STP, MSTP). This procedure “breaks" all the loops of the network,
permitting only one path from a Bridge to any other Bridge, in order to prevent “infinite
loops" (i.e. infinite replaying of the frames) due to redundantly connected bridges
networks.
Moreover, the (X)STP procedures accomplish the resilience of the network against STP
failures. It provides, if the bridged network is redundantly protected, to recover the
network connectivity (with respect to the STP topology). For instance by electing a new
Root Bridge (that is the root of the tree), if the actual one has failed; or by deactivating a
failed link and activating a backup one, if existing. STP functions are compliant to 802.1d,
802.1w, 802.1s Rec.
Some STP examples are illustrated in “Data frames” (p. 1-31).
Furthermore, ES1 and ES4 systems support the following functions:
• IGMP (Internet Group Multicast Protocol), see “IGMP Snooping management”
(p. 1-66).
• Link Aggregation , see “Link Aggregation management” (p. 1-68).
• Ethernet Protection Ring, see “Ethernet Ring Protection (ERP)” (p. 1-79).
• OAM (Operation, Administration, Maintenance), see “Ethernet OAM” (p. 1-86).
• Port Mirroring, see “Port Mirroring management” (p. 1-62).
• ACL (Access Control List), see “Configure ACL for an Ethernet Port” (p. 4-94).
The framing procedures and the various Ethernet frames formats are illustrated in “E-
VPL, end to end implementation example” (p. 1-27). The other frames formats are
reported in the related OMSN (1640FOX/1650SMC/1660SM) Technical Handbooks,
listed in Table 1, (pg. 1-xxviii), and in the standard recommendations.
The ISA-ES system and protocol stacking is illustrated in the figure below
(Figure 1-1, (pg. 1-7)).
An example of Port-to-Port cross-connected Ethernet link is illustrated in
Figure 1-11, (pg. 1-15).
An example of generic Point-to-Point (P2P) link creation, showing the use of the main
resources involved, is reported in “ISA-ES1/4 System” (p. 1-3).
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Other examples and applications are reported in “Example of end-to-end ETS link
creation” (p. 1-16) up to “E-VPL, end to end implementation example” (p. 1-27).
The ISA-ES1 family (with an SDH equivalent capacity of 1 VC4) available units are:
Unit Acronym (code) Local ports Remote ports

ISA ES1-3FE (3AL 97194 AC--)
1 FX and 2 FE 2 MII
ISA ES1-3FEN (3AL 97194 BA--)
ISA ES1-8FE (3AL 98128 AB--/AC--)
8FE 8 MII
ISA ES1-8FEN (3AL 97165 BA--)
ISA ES1-8FX (3AL 98150 AB--/AC--) 8FX 8 MII
ISA ES1-8FEB (3AL 98128 BA--) 8FE 6 MII and 2 GMII
ISA ES1-8FXB (3AL 98150 BA--) 8FX 6 MII and 2 GMII
Legenda:
• FE = Fast Ethernet (10/100 Base T)
• FX = Fast Ethernet (100 Base FX Optical)
• MII = Media Independent Interface
• GMII = Gigabit Media Independent Interface
Local ports Remote ports Local ports Remote ports

9 1
10 2
1FX 3 11 3
+ ISA ES1 1 2 (MII)
8FE 12
ISA ES1 4 8 (MII)
4 2 SDH 13 5 SDH
2FE
5
3FE 14
8FE 6
15 7
16 8
Local ports Remote ports

9 1
10 2
11 3
8FX 12 ISA ES1 4 8 (MII)
SDH
13
14
8FX 5
6
15 7
16 8

9 1 9 1
10 2 10 2
11 ... 6 (MII) 11 ... 6 (MII)
8FE 12
ISA ES1 5 8FX 12 ISA ES1 5
13 8FEB 6 13 8FXB 6
14 + 14 +
15 7 2 (GMII) 15 7 2 (GMII)
16 8 16 8
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
The ISA-ES4 family (with an SDH equivalent capacity of 4 VC4) available units are:
Unit Acronym (code) Local ports Remote ports

ISA ES4-8FE (3AL 81879 AA--/AB--) 8 FE and 1 GE 16 MII and 2 GMII
ISA ES4-E (3AL 97352 AA--) 8FE and 2 GE 8 MII and 2 GMII
ISA ES4-GE (3AL 97380 AA--) 4FE and 2 GE 8 MII and 2 GMII
ISA ES4-8FEB (3AL 81879 BA--) 8FE and 1 GE 15 MII and 2 GMII
Legenda:
• FE = Fast Ethernet (10/100 Base T)
• GE = Gigabit Ethernet
• MII = Media Independent Interface
• GMII = Gigabit Media Independent Interface

1 GE 19 1 11 1
+ 2 2 GE 12 2
20 ... 16 (MII) + ... 8 (MII)
21 ISA ES4 15 13 ISA ES4 7
... 16 14
8 FE ...
8FE + 8 FE ...
E 8
+
26 17 19 9 2 (GMII)
2 (GMII)
27 18 20 10

11 1 1 GE 19 1
2 GE
12 2 + 2
+ ... 8 (MII) 20 ... 15 (MII)
13
ISA ES4 7 21 ISA ES4 14
...
4 FE 14 GE 8
+
8 FE
...
8FEB 15
+
15
9 2 (GMII) 26 16 or 18
16 2 (GMII)
10 27 17
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Table 1-2 Allowed board
ISA-ES NE ES1-3FEN
ES4-GE ES1-8FXB ES1-8FEB ES4-8FEB
Equipment ES1-8FEN
1642EM 2 1 N.A. N.A. N.A.
1642EMC 1 N.A. N.A. N.A. N.A.
1662SMC N.A. N.A. 8 8 8
1660SM N.A. N.A. 16 16 16
1650SMC N.A. N.A. 3 3 3
Throughput on back-
155 622 155 155 622
panel (Mb/s)
MAC Addresses “on 8

26 19 19 29
per NE basis” 19
Figure 1-1 ISA-ES subsystem, protocol stacking
3 any 3 any 3 any
S-VLAN S-VLAN MAC

3 any
2
2 VLAN 2 VLAN GFP or LAPS
2 MAC
MAC MAC 1 SDH/SONET
1 FE or GE
VLAN and/or S-VLAN

processing
Ethernet GFP Ethernet

Local or SDH / over
FE, GE CIA Switch/
Ethernet LAPS SONET SDH/SONET
Bridge
(remote Ethernet)
Local: SONET/SDH equivalent capacity: Remote:

- ES1: 8 FE ports - ES1: # 1 VC4 - ES1: 8 ports
- ES4: 8 FE + 1GE ports - ES4:# 4 VC4 - ES4: 16 ports SMII or 2 ports GMII
CIA = Classification, Identification, Aggregation.

CIA function can be enabled/disabled by the operator.
Note:
• For MII and GMII ports definition see “GMII - MII Remote Interface Selection (ES4 board only)”
(p. 4-60).
• The MAC layer may optionally includes VLAN or S-VLAN sub-layers.
• The Ethernet over SDH/SONET function is implemented in an optional sub-module (PIM-MS).
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Figure 1-2 Bridge representation example and relevant FDB table

C10 C28
C23 C26
L1 1 4 L4
L2 2 B1 5 L5
L3 3 6 L6
BRIDGE
C15 C24 C21
(OMSN+ES)
FDB table
NOTES: (Filtering Data Base table)
- 1, 2, 3, 4, 5, 6 : ports of the bridge Computer Address Port
MAC-C10 1
- L1, L2, L3, L4, L5, L6: LANs
MAC-C15 3
Cn : Computer with its own MAC address MAC-C23 5
MAC-C24 6
MAC-C26 5
Cn : new inserted computer MAC-C28 4
Bridge operations examples:

- C15 to C26 --> FORWARD to port5
- C26 to C23 --> DISCARD
- C10 to C21 --> LEARNING
- C21 to C28 --> LEARNING (adding C21 on FDB)
Note:
• A “MAC Bridge" takes into account the MAC addresses.
• A “Virtual Bridge" takes into account the MAC addresses and the VLAN identifiers (user tag), see
next figure.
• A “Provider Bridge" takes into account the MAC addresses and the S-VLAN identifiers (provider
tag), see next figure.
• The “Provider Bridge" can work in mixed mode, taking into account the VLAN and the S-VLAN
identifiers.
• In any of the above configurations, the Bridge ports work in “promiscuous" mode.
Auto-Learning mechanism:
Unknown incoming frames are flooded on all ports of the bridge, except the port
where they arrived. When a far station responds back on a port, the bridge “learns" that
frames having this received MAC-Address (and, if existing, the associated VLAN-ID)
have to be forwarded to that port. This connection is written on the FDB table, used to
forward next incoming frames.
Note: one VLAN will be learned and forwarded, on a given port, only if registered on
that port, otherwise it will be discarded.
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Figure 1-3 System into SDH network, example
Remote Ports OMSN

Ethernet over SONET/SDH B4 +
(POS) ISA-ES
OMSN
+
ISA-ES
OMSN
B2
+
ISA-ES
Local SDH SONET NETWORK

Ethernet B1
Ports
B3 OMSN
+
ISA-ES
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Figure 1-4 VLAN Bridge representation example and relevant FDB table
VLAN-C VLAN-A VLAN-A
VLAN-B VLAN-A
C31 C10 C28
C23 C26
A, C A
L1 1 4 L4
B A, B
L2 2 B1 5 L5
B, A A
L3 3 6 L6
BRIDGE
VLAN-A C15 C15 (OMSN+ES) C24 C21 VLAN-A
VLAN-B VLAN-A
C21 moved
FDB table
NOTES: (Filtering Data Base table)
- 1, 2, 3, 4, 5, 6 : ports of the bridge Computer Address Port VLAN
MAC-C10 1 A
- L1, L2, L3, L4, L5, L6: LANs
MAC-C15 3 B
- A, B, C: VLANs MAC-C23 5 B
MAC-C24 6 A
Cn : Computer with its own MAC address
MAC-C26 5 A
MAC-C28 4 A
MAC-C31 1 C
Cn : new inserted (or moved) Computer
Note:
• The Bridge (ISA-ES) is configured in Virtual or Provider mode.
• The afferent VLAN's have to be registered on the relevant ports, otherwise they are discarded.
• In this way, incoming frames having a given VLAN-ID are distributed only to those ports registered
on that VLAN (distribution domain “Member Set").
• Bundling examples are shown on ports 1, 3, 5 (more VLAN's are registered over one single port).
............................................................................................................................................................................................................................................................
1 - 10 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 1-5 Frames acceptance criteria

Frames Ingress Acceptance criteria on Bridge ports
The ISA-ES system permits to set the Frames Filtering criteria on ingress of Virtual or
Provider Bridge ports (ETB), by means of the menu option Transmission Î Bridge Port
Management Î Configure Bridge Port. The related parameters are the following:
Acceptable Frames: possible values: AdmitAll / AdmitOnlyVlanTagged
if “AdmitAll": all types of MAC frames are accepted by the port
if “AdmitOnlyVlanTagged": only VLAN tagged frames are accepted by the port
Ingress Filtering: possible values: True/False
if True: only registered VLAN's are accepted by the port
if False: all VLAN’s are accepted by the port (not supported in current release).
In case that untagged (or only-priority-tagged) frames are provisioned to be accepted,
then they will be forwarded by attaching to them the PVID, i.e. the Port Vlan Id. assigned
by means of the menu option Transmission Î Bridge Port Î Modify Virtual/Provider
Port PVID.
For details about the specific configurations here recalled, see their relevant paragraphs.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-11
............................................................................................................................................................................................................................................................
Figure 1-6 MAC Bridge distribution domain (example)
LAN or LAN or LAN or LAN or

SDH/ SDH/ SDH/ SDH/
SONET SONET SONET SONET
ETB ETB ETB ETB

port port port port
(rate) (rate) (rate) (rate)
MAC Bridge
(MAC distribution Domain)
The frames are distributed to all the active ETB ports
Note:
• ETB ports can be either Remote or Local
• The incoming frames are distributed to all the active ETB ports in MAC-learning modality (in case
of VLAN Bridge, the frames are distributed only to the ports registered on the same VLAN)
• No XC is necessary, as the frames distribution is based upon the FDB table. The “Static
Unicast/Multicast Filtering" option of the FDB table can be used to create a “permanent" cross-
connection
• This configuration is used for “Point-to-Multipoint", “Multipoint-to-Multipoint", or so called “E-
Lan" applications.
Figure 1-7 Virtual Bridge distribution domain (example)
LAN or LAN or LAN or LAN or

SDH/ SDH/ SDH/ SDH/
SONET SONET SONET SONET
ETB ETB ETB ETB

port port port port
(rate)
(RP) (RP) (RP) (RP)
VLAN VLAN VLAN VLAN
Reg Reg Reg Reg
MAC Bridge
(MAC distribution Domain)
The frames are distributed only to the ports registered on the same VLAN.
Examples of VLAN registration:
VLAN-a = port1, port4, port5, port6 (Member-Set of VLAN-a)
VLAN-b = port2, port3, port5 (Member-Set of VLAN-b)
RP= Regenerated Priority option
Note:
• E-VLAN type (see notes of previous figure)
............................................................................................................................................................................................................................................................
1 - 12 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 1-8 Provider Bridge distribution domain (example)

SVID
LAN Registr.
ETS
or Classifier UNI to NNI PUSH SVID
port SVID
SONET (VLAN, Pri) Registr.
LAN
ETS ETB
Provider or
InFlow XC OutFlow
port
SONET
(TD, Polic.) (RP, PT)
Provider
Bridge
SVID
Registr.
SVID
LAN ETS distrib.
or UNI to NNI POP SVID
port SVID Domain
SONET Registr.
LAN
Provider ETB
ETS or
OutFlow
XC InFlow port
SONET
(TD0) (RP, PT)
RP= Regenerated Priority option
PT= Protocol Type option
TD0= Traffic Descriptor "null"
Note:
• ETS ports, as well as ETB ones, can be Remote or Local.
• The two XC's can also be created over the same ETS port.
Note that the “Uni-Nni XC OneStep” procedure, described in “Create Ets XC One Step (MAC &
Virtual) for the Ethernet Port” (p. 4-242), provides to create a bidirectional Uni-Nni connection
over the same Ets Port.
• More data flows can be defined over one port (for Multiplexed and Differentiated Services).
• The incoming frames are distributed only to the ports registered over the relevant S-VLAN, i.e.
parts of the “member set" distribution domain of that S-VLAN (SVID registration). In this way,
ports registered on the same SVID can exchange ethernet frames.
• The Provider to edge connection is accomplished by means of “One-Step" procedure.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-13
............................................................................................................................................................................................................................................................
Figure 1-9 Generic VLAN Classification-Identification-Aggregation (example)

Classifier
Pri3
VLAN#25
C
ETS InFlow
ETS OutFlow
(TD,Pol.)
L-ETH C
VLAN#150
LAN1 Port Pri7
(E-Rate)
R-ETH EOS
Port
ETS InFlow (VCG-Rate)
C ETS OutFlow
VLAN#200 (TD,Pol.)
Pri5
ETS InFlow
LAN2 L-ETH C ETS OutFlow
(TD,Pol.) SDH
Port
VLAN#500-700 SONET
(E-Rate) Pri3 - 6 ETS XC
R-ETH
EOS
ETS OutFlow Port
(VCG-Rate)
L-ETH R-ETH
ETS InFlow
LAN3 Port C ETS OutFlow Port
(TD,Pol.)
(E-Rate) (VCG-Rate)
VLAN#1000-2000
Pri3 - 6
R-ETH
ETS OutFlow Port
(VCG-Rate)
Note:
• L-ETH = local ethernet; R-ETH = remote ethernet; EOS= Ethernet Over Sdh
VCG= Virtual Concatenation Group; TD = Traffic Descriptor; Pol= Policing
C = classifier; PRI = priority; XC = Cross-Connection
E-Rate = rate of the ethernet port; VCG-rate= rate of the Sdh Port
• The involved ports can be either Remote or Local
• Classifiers, InFlows and OutFlows are internal resources
• A frame with VLAN tag that is not defined on Classifiers is discarded
• More VLAN's and more Priorities can be defined by one classifier (Bundling)
• More InFlows/OutFlows resources can be created over one Port (Multiplexing)
• The VLAN usage is possible in “none" or Virtual or Provider Bridge configuration
• The VLAN identifiers on LAN1 and LAN2 must be not-overlapping
• Classification of more VLAN's and Service Multiplexing with differentiated CoS are possible only
in “none" or Provider bridge Configuration
• The E-Rate, sum of TD rates and VCG-Rate must be congruent
• The VLAN's on LAN1 and LAN2 are aggregated on the same SDH resource
• LAN3 shows an example of multicast connection (Point-to-Multipoint).
............................................................................................................................................................................................................................................................
1 - 14 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 1-10 Stacked VLAN management (example)
SVLAN PUSH POP

Registr. SVLAN SVLAN
ETS ETS ETS(Prov) ETS(Prov)
LAN1 port InFlow OutFlow InFlow
SVLAN SVLAN
SVLAN PUSH Registr. Registr. POP
ETS ETS ETS(Prov) ETH ETH ETS(Prov)
network
LAN2 port InFlow OutFlow port port InFlow
XC XC
SVLAN PUSH POP
ETS ETS ETS(Prov) ETS(Prov)
LAN3 port InFlow OutFlow InFlow
UNI to NNI XC Provider Provider NNI to UNI XC

or "none" or "none"
Bridge Bridge
S-VLAN management example
Note:
• Creation and Cross connections of S-VLAN resources are possible in Provider and “none" Bridge
Configurations and are managed by means of “Create-XC OneStep" procedures.
• PB= Provider Bridge domain.
• Classification and Identification of the single data flows is possible, as seen in Figure 1-9, (pg.
1-14).
• The involved ports must be registered on the relevant S-VLAN's (in case of “Provider" config.).
• SVLAN registration is not needed, in case of “none" Bridge config.
• VLAN's classification, Traffic Description, Policing and Color Profile are also possible.
Figure 1-11 Transparent Mac/Virtual Port-to-Port XC “OneStep" (Example)
SDH Network
SDH XC SDH XC
Ethernet Ethernet
Data Data
L-ETH Port R-ETH Port R-ETH Port L-ETH Port
(Rate) (Rate) (Rate) (Rate)
InFlow OutFlow InFlow OutFlow

XC XC
OutFlow InFlow OutFlow InFlow

XC XC
Transparent Port-to-Port (p2p) XC example bidirectional)
Note:
• The ports are devoted to only one data flow, in transparent mode, without traffic classification nor
policing.
• The two involved Ethernet ports may be either local or remote.
• The operations to create this structure are reported in “Ethernet Technique” (p. 1-18).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-15
............................................................................................................................................................................................................................................................
Example of end-to-end ETS link creation

Figure 1-12, (pg. 1-17) shows an application example of unidirectional, end-to-end ETS
link.
Note: This is only a generic example, in order to show the main
resources involved in a link.
A bidirectional link can be accomplished, by creating, under the same port, the relative
InFlow and OutFlow resources.
More Inflows/OutFlows can be created under the same port.
The Bridge Type is configured as none.
For details about the specific configurations here recalled, see their relative paragraphs.
• on the first end (OMSN+ES A):
1. In Transmission context, configuration of the Bridge (in “none" mode):
Transmission Î Node Management Î ConfigureNode
set the BridgeType= none and the ProtocolType
2. Creation of the required ETS Traffic Descriptors (TD), with the appropriate CIR/PIR
and CBS/PBS values for both sides:
(Configuration Î Traffic Descriptor Î ETS Traffic Descriptor)
3. In Transmission context, configuration of GFP or LAPS framing on the involved
Remote Ethernet Ports:
Transmission Î Ethernet Port Management Î Substitute Server Layer
4. In Transmission context, activation of all the involved ETS ports:
Transmission Î Ethernet Port Management Î Configure Ethernet Port
set Promiscuous Mode = enabled; Admin Status= up
For the involved Remote Ethernet Ports, set the Sdh VCG rate in the “TP/GFP (or
LAPS) SDH Configuration" Sector
5. Cross-Connections creation, by means of the option:
Connection Î Ethernet Port Î Create Ets XC One-Step
This operation is described in “Create Ets XC One Step (MAC & Virtual) for the
Ethernet Port” (p. 4-242) and “Create Ets XC One Step (Provider) for the Ethernet
Port” (p. 4-246); it permits to create all the necessary resources (InFlows/OutFlows,
Classifiers, VLAN Management, etc.)
6. In Connection context, creation of eventual Static Unicast Filtering entries:
Connection Î Bridge Management Î Filtering Data Base
then follow the procedure described in the relevant paragraph Connection Î Bridge
Management Î Filtering Data Base, selecting “Static Unicast Filtering“ folder.
............................................................................................................................................................................................................................................................
1 - 16 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
7. Connection into the transport SDH network

The involved ETS Ports must be associated to suitable Sdh-VC's (VC12 or VC3 or
VC4 or VCn-xv) and then cross-connected in the SDH network.
These operations are done on SDH-CT (see SDH Operator's Handbook for details).
Example (VC12 case):
– Remote Ethernet Port association to a VC12 or to a group of VC12 (VC12-xv), in
case of VCG link
– LCAS configuration, if used
– cross-connection of VC12 to TU12
– association of TU12 to VC4, and VC4 connection as indicated in the figure.
• on the other involved OMSN+ES equipment:
Similar operations as in the first equipment
Figure 1-12 End-to-End ETS link Example
Originating Transport Terminating

Point Network Point
SDH Network
SDH XC SDH XC
OMSN+ES (A) OMSN+ES (B)
Ethernet (Rate) (Rate) (Rate) (Rate) Ethernet
Data Data
POP POP POP POP

S-VLAN S-VLAN S-VLAN S-VLAN
(ColorProf.) (ColorStack) (ColorProf.) (ColorStack)
InFlow InFlow OutFlow

OutFlow (TD, polic.)
(TD, polic.)
VLAN VLAN
Classifier Classifier
(Priority) (Priority)
(VLAN) ETS XC (VLAN) ETS XC
Note:
• Cross-Connections Creations are managed by means of “Create-XC OneStep" procedure.
Note: A BIDIRECTIONAL link can be accomplished by creating, under the
same port, an InFlow and an OutFlow associated to the related data flow, and so
on.
• VLAN, S-VLAN and TD are possible only in Provider configuration (and also in "none" bridge)
• More InFlows/OutFlows over a port are possible, in Provider config. (and also in "none" bridge")
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-17
CT Operator’s Guide Ethernet Technique
............................................................................................................................................................................................................................................................
Ethernet Technique
The Ethernet technique (also called MAC 802.3), operating at level 2 of the ISO-OSI
protocol stack, is used to transport data packets originated by the network layer (level 3). It
is based over the concept of “Multi Access Channel"; i.e. a single channel is shared
among many users that are connected on the same communication medium. The MAC
(Medium Access Control) functions provide to manage the access to the physical channel
and the related possible access conflicts that can arise. The channel used to connect many
users is called LAN (Local Area Network).
The data packets are encapsulated into the MAC frame (illustrated in Figure 1-18, (pg.
1-31). and Figure 1-19, (pg. 1-31)), and then are sent into the Ethernet physical layer
(level 1), after conversion using the Manchester encoding procedure.
............................................................................................................................................................................................................................................................
1 - 18 P/N 8DG15785AAAA
MEF (Metro Ethernet Forum) Applications CT Operator’s Guide
............................................................................................................................................................................................................................................................
MEF (Metro Ethernet Forum) Applications

The MEF (Metro Ethernet Forum) specifies, in MEF-10-2004 and MEF-6-2004
recommendations, the basic models, services and applications for ethernet users.
This paragraph illustrates some examples implementing MEF structures, by using ISA-ES
Data Systems.
Network connections types (MEF terminology):
• EVC (Ethernet Virtual Connection) can be:
1. Point-to-Point (P2P), or E-Line. It can be:
a. Ethernet Private Line (EPL)
b. Ethernet Virtual Private Line (EVPL)
2. MultiPoint-to-MultiPoint (MP2MP), or E-LAN
MEF-Network connections accomplishment on ISA-ES Data system:
• The EPL can be achieved, on ISA-ES Data system, using the transparent Port-to-Port
connection. See Figure 1-14, (pg. 1-22).
• The E-LAN can be achieved by means of the FDB function, either in MAC Bridge, or
Virtual Bridge (also called E-VLAN), or Provider Bridge modality. See
Figure 1-15, (pg. 1-25) (centralized LAN) and Figure 1-16, (pg. 1-26) (distributed
LAN).
• An example of EVPL with Services Multiplexing and differentiated CoS is shown in
Figure 1-17, (pg. 1-29).
• The Bundling service can be achieved in Provider and Virtual Bridge configuration, by
registering more VLAN's over one EthernetPort. Either it can be achieved, in Provider
bridge mode, by defining a range of customer VLAN's for a single Classifier
associated to a data flow.
• The Service Multiplexing can be achieved in Provider Bridge configuration, by
creating more and different user data flows over one EthernetPort. See EVPL,
Figure 1-17, (pg. 1-29).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-19
CT Operator’s Guide MEF (Metro Ethernet Forum) Applications
............................................................................................................................................................................................................................................................
Figure 1-13 MEF-Network application for OMSN+ISA-ES System
Remote Ports (EOS) or

B4 OMSN+ES
Local Ports
Ethernet Bridge
OMSN+ES
MEN B2
EVC1
Local/
Remote B1
Ethernet EVC2
Ports
OMSN+ES
B3 OMSN+ES
Note:
• EVC (Ethernet Virtual Connection) is a connection between two or more Ethernet enabled Network
Elements (such as OMSN+ES System).
• MEN = Metro Ethernet Network
............................................................................................................................................................................................................................................................
1 - 20 P/N 8DG15785AAAA
Ethernet Private Line (EPL), end to end implementation CT Operator’s Guide
............................................................................................................................................................................................................................................................
Ethernet Private Line (EPL), end to end implementation

example
Refer to Figure 1-14, (pg. 1-22).
For details about the specific configurations here recalled, see their relevant paragraphs.
All involved ports are in ETS mode, concerning the client layer: see “Substitute Client
Layer for an Ethernet Port or an Aggregator” (p. 4-116) .
1. In Transmission context, activation of the desired Local EthernetPort (L-ETH):
set Promiscuous Mode = enabled; AdminStatus = up
2. In Transmission context, configuration of GFP or LAPS framing on the desired
Remote EthernetPort (R-ETH):
3. In Transmission context, activation of the desired Remote EthernetPort (R-ETH):
set Promiscuous Mode = enabled; Admin Status = up
set the Sdh VCG rate in the “TP/GFP (or LAPS) SDH Configuration" sector
4. In Connection context, creation and connection of a bidirectional ETS flow:
select one of the above activated Local or Remote Ethernet Port
Connection Î Ethernet Port Î Create Ets Xc One-Step
(In case of Provider Bridge, first select Transmission Î Ethernet Port Management
Î Characterization Service, choosing the Port to Port option, as described
in“Characterization Service of an Ethernet Port” (p. 4-93), then follow the procedure
described in the relevant paragraph “Create Ets XC One Step (Provider) for the
Ethernet Port” (p. 4-246), selecting Connection Type = Bidirectional.
The created Ethernet flow passes through the sdh network; the involved Remote Port
must be associated to suitable Sdh-VC's (VC12 or VC3 or VC4) and then cross-
connected.
These operations are to be done on SDH-CT (see SDH Operator's Handbook for
details about SDH configuration and connection). Example (VC12 case):
– Remote Ethernet Port association to a VC12 or to a group of VC12, in case of
VCG link
– bidirectional cross-connection of VC12 to TU12
– association of TU12 to AU4
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-21
CT Operator’s Guide Ethernet Private Line (EPL), end to end implementation
............................................................................................................................................................................................................................................................
– Optical fibers connection

• on the second end (OMSN+ES B):
the same operations as in the first end
Figure 1-14 EPL application example
SONET/SDH
Network
STM link
SXC SXC
Ethernet OMSN+ES (A) OMSN+ES (B) Ethernet
Data Data
(E-Rate) (VCG-Rate) (VCG-Rate) (E-Rate)
InFlow OutFlow InFlow OutFlow

XC XC
OutFlow InFlow OutFlow InFlow

XC XC
Port-to-Port or EPL example
Note:
• E-Rate= rate of the Ethernet LAN link (10/100/1000/10000 Mbps)
• VCG-Rate= rate of the Ethernet over SDH link, that can also be concatenated over more SDH paths
• VCG= Virtual Concatenation Group
• The E-Rate and VCG-Rate must be congruent
• The STM link is bidirectional and LCAS option can be used
• Local (L-ETH) and Remote (R-ETH) Ethernet ports are ETS type
• The ports are devoted to only one flow, in transparent mode, without traffic classification nor
policing.
• The two involved Ethernet ports may be either local or remote.
• The connection is done by means of the “OneStep Port-to-Port" procedure (see “Connection”:
“Create Ets XC One Step”.
• This link is EPL (Ethernet Private Line) type (also called point-to-point)
............................................................................................................................................................................................................................................................
1 - 22 P/N 8DG15785AAAA
E-Lan/E-VLan, end to end implementation example CT Operator’s Guide
............................................................................................................................................................................................................................................................
E-Lan/E-VLan, end to end implementation example

Refer to Figure 1-15, (pg. 1-25) (centralized LAN) or Figure 1-16, (pg. 1-26) (distributed
LAN).
All involved ports are in ETB mode (except if the Bridge is Provider). In case of Provider
Bridge, see next paragraphs for more information.
1. In Transmission context, configuration of the Bridge (MAC or Virtual or Provider):
Transmission Î Node Management Î Configure Node
set the BridgeType and the ProtocolType
2. In Transmission context, substitution of the involved ports from ETS to ETB mode:
Transmission Î Ethernet Port Management Î Substitute Client Layer
set ETS Î ETB Layer
4. In Transmission context, configuration of Regenerated Priority mapping on the
involved Ports:
Transmission Î Etherne tPort Management Î Configure Ethernet Port
select the Regeneration User Priority item
5. In Transmission context, activation of all the involved ETB ports:
set Promiscuous Mode = enabled; AdminS tatus = up
For the involved Remote Ethernet Ports, set the Sdh VCG rate in the TP/GFP (or LAPS)
SDH Configuration sector
6. In Transmission context, configuration of Bridge Ports:
Transmission Î Bridge Port Management Î Configure Bridge Port
set the Ingress Filtering Criteria and the STP parameters
7. In Transmission context, registration of the involved VLAN's on the relative ETB
ports:
Transmission Î Bridge Management Î Vlan Registration
then follow the procedure described in the relevant paragraph “Filtering Data Base for
the Bridge” (p. 4-235), selecting Static Unicast Filtering folder.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-23
CT Operator’s Guide E-Lan/E-VLan, end to end implementation example
............................................................................................................................................................................................................................................................

The involved ETB Remote Port must be associated to suitable Sdh-VC's (VC12 or
VC3 or VC4 or VCn-xv) and then cross-connected.
case of VCG link
– association of TU12 to VC4, and VC4 connections as indicated in the figure.
............................................................................................................................................................................................................................................................
1 - 24 P/N 8DG15785AAAA
E-Lan/E-VLan, end to end implementation example CT Operator’s Guide
............................................................................................................................................................................................................................................................
Figure 1-15 Example of E-Lan/E-VLan implementation (1: centralized LAN)

OMSN+ES (B)
OMSN+ES (A) SONET/SDH Vid 1,2 Vid 1,2
NETWORK LAN or
SXC Port ETB Br. Port ETB SONET/SDH
Vid 1 Vid 1,2
LAN or
SONET/SDH Port ETB Port ETB SXC
OMSN+ES (C)
Vid 2 Vid 3 Vid 3 Vid 3
LAN or LAN or
Br. Br. SONET/SDH
SONET/SDH Port ETB Port ETB SXC SXC Port ETB Port ETB
Vid 3 Vid 1
LAN or OMSN+ES (D)
SONET/SDH Port ETB Port ETB SXC Vid 1 Vid 1
LAN or
SXC Port ETB Br. Port ETB SONET/SDH
SXC = SDH/SONET XC
Vid X = VLAN ID X Registration
Br = Bridge
Note:
• The Bridges can be Mac or Virtual or Provider
• In case of MAC Bridge no registration is needed and the MAC frames are forwarded on all active
ETB ports of the bridge (E-Lan implementation)
• In case of Virtual or Provider Bridge, the incoming frames are distributed only to the ports
registered over the same VLAN, i.e. to those ports that are parts of the “member set" distribution
domain (DD) of that VLAN
• More VLAN's can be registered on one port
• More ports can be part of the “member set" distribution domain (DD) of one VLAN
• The indicated links are bidirectional
• The frames distribution is based upon the FDB table
• ETB ports can be Remote (for SDH) or Local (for LAN).
• Where ETB ports are Remote, they need SDH XC (SXC) and eventual VCG association
• The LCAS feature can be used on the SDH-VCG links, in order to improve the band utilization
• The “Static Unicast Filtering" option of the FDB table can be used, in order to avoid the initial
flooding of unknown frames destinations
• The E-VP Lan structure can be implemented by using Provider bridge, for Differentiated and
Multiplexed Services applications (see next example for some details about Provider Bridge
configuration)
• This application is called “MultiPoint-to-MultiPoint" or “E-Lan/E-VLan"
• The Regenerated Priority option can be used, on the ETB ports
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-25
CT Operator’s Guide E-Lan/E-VLan, end to end implementation example
............................................................................................................................................................................................................................................................
Figure 1-16 Example of E-Lan/E-VLan implementation (2: distributed LAN)
LAN or LAN or LAN or

SONET SONET SONET
/SDH /SDH /SDH
OMSN+ES
OMSN+ES
OMSN+ES
OMSN+ES
V2 V3 V1 V2 V3 V1
ETB ETB ETB ETB
Br. Br. Br. Br.
ETB ETB ETB ETB ETB ETB ETB ETB

V1 V2 V3 V1 V2 V3 V1 V2 V3 V1 V2 V3 V1 V2 V3 V1 V2 V3 V1 V2 V3 V1 V2 V3
SXC SXC SXC SXC SXC SXC SXC SXC

SONET/SDH link SONET/SDH link SONET/SDH link
Note:
• SXC = SONET/SDH XC
• Vx = VLAN x Registration
• Br = Bridge
• The indicated links are bidirectional
• The SDH network emulates an E-VLAN for VLAN's ID 1,2,3
............................................................................................................................................................................................................................................................
1 - 26 P/N 8DG15785AAAA
E-VPL, end to end implementation example CT Operator’s Guide
............................................................................................................................................................................................................................................................
E-VPL, end to end implementation example

Refer to Figure 1-17, (pg. 1-29) illustrating an EVPL example with Service Multiplexing
and Differentiated Class of Services.
1. In Transmission context, configuration of the Bridge (Provider):
Transmission Î Node Management Î Configure Node
set the BridgeType and the ProtocolType
2. In Transmission context, substitution of relevant ports from ETS to ETB mode:
Transmission Î Ethernet Port Management Î Substitute Client Layer
set ETS Î ETB Layer
4. In Transmission context, configuration of Regenerated Priority (if used) on the
involved Ports:
select the Regeneration User Priority item
5. In Transmission context, activation of all the involved ETB ports:
set Promiscuous Mode = enabled; Admin Status = up
For the involved Remote Ethernet Ports, set the Sdh VCG rate in the TP/GFP (or LAPS)
SDH Configuration sector
6. In Transmission context, configuration of Bridge Ports:
Transmission Î Bridge Port Management Î Configure Bridge Port
set the Ingress Filtering Criteria and the STP parameters
7. In Transmission context, VLAN's registration on the involved ETS and ETB ports:
Transmission Î Bridge Management Î Vlan Registration
then follow the procedure described in the relevant paragraph “Filtering Data Base for
the Bridge” (p. 4-235), selecting Static Unicast Filtering folder.
9. In Connection context, creation of ETS-Cross Connections and related resources:
Connection Î Ethernet Port Management Î Create Ets Xc One-Step-Provider
follow the “OneStep" procedure described in the relevant paragraph “Create Ets XC
One Step (Provider) for the Ethernet Port” (p. 4-246).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-27
CT Operator’s Guide E-VPL, end to end implementation example
............................................................................................................................................................................................................................................................

The involved ETB Remote Port must be associated to suitable Sdh-VC's (VC12 or
VC3 or VC4 or VCn-xv) and then cross-connected.
The indicated STM links are bidirectional.
case of VCG link
– association of TU12 to VC4, and VC4 connection as indicated in the figure.
............................................................................................................................................................................................................................................................
1 - 28 P/N 8DG15785AAAA
P/N 8DG15785AAAA
System generalities

SONET/SDH OMSN+ES (C)
Network RSVid1
ETS
port
OMSN+ES (A) Provider -SVid1 NNI to UNI
LAN Bridge P-IF
RSVid1 XC E-OF
RSVid1,2,3 (TD0)
or Pr.
SONET ETS ETB port Classifier
Classifier SXC Br. UNI to NNI (VLAN5, Pri 3..6)
port (RP, PT) +SVid1
/SDH UNI to NNI dd1
E-VPL, end to end implementation example
(VLAN1.5, Pri 3..6) E-IF

+SVid1 P-OF XC
E-IF (TDa,
(TDa, XC P-OF RSVid1 Pol. a)
Pol. a) SVID 1 STM
(a) distrib. ETB port SXC
NNI to UNI -SVid1 (RP, PT) OC
Domain link
E-OF XC P-IF
(TD0) (d) OMSN+ES (C) RSVid2
ETS
Classifier port
(VLAN6, Pri 3) UNI to NNI
+SVid2 -SVid2 NNI to UNI
E-IF P-IF
(TDb, XC P-OF RSVid2 RSVid2 XC E-OF
(TD0)
Pol. b) SVID 2 Pr.
ETB port SXC ETB port Classifier
(b) distrib. (RP, PT)
SXC Br. UNI to NNI (VLAN6, Pri 3)
NNI to UNI -SVid2 (RP, PT) +SVid2
Domain STM dd2 E-IF
E-OF XC P-IF P-OF XC (TDb,
(TD0) (e) OC
Pol. b)
link
Figure 1-17 EVPL implementation example
Classifier
(VLAN7, Pri 6)
UNI to NNI
+SVid3
E-IF
(TDc, XC P-OF RSVid3 OMSN+ES (D)
Pol. c) RSVid3
SVID 3 ETS
ETB port SXC STM
(c) distrib. (RP, PT)
NNI to UNI -SVid3 OC port
Domain NNI to UNI
P-IF link -SVid3
E-OF XC
(TD0) (f) P-IF
RSVid3 XC E-OF
(TD0)
Pr.
ETB port Classifier
SXC Br. UNI to NNI (VLAN7, Pri 6)
(RP, PT) +SVid3
dd3 E-IF
P-OF XC (TDc,
Pol. c)
RSVid = S-Vlan Registration E-IF = ETS InFlow Pol = Policing

Pr.Br = Provider Bridge E-OF = ETS OutFlow RP = Regenerated Priority option
dd = Distribution Domain P-OF = Provider OutFlow PT = Protocol Type option
TD0 = Traffic Descriptor "null" P-IF = Provider InFlow SXC = SONET/SDH XC
EVPLapplication example with Services Multiplexing and differentiated CoS

............................................................................................................................................................................................................................................................
1-29
............................................................................................................................................................................................................................................................
CT Operator’s Guide
CT Operator’s Guide E-VPL, end to end implementation example
............................................................................................................................................................................................................................................................
Note: about Figure 1-17, (pg. 1-29):

• The links a to d, b to e, c to f are parts of three different EVC's, afferent to one single ETS port.
• (a), (b), (c): bidirectional links for different users; VLAN id, Priority (Pri), Traffic Descriptors (TD)
and Policing (Pol) on these connections can be different.
• VLAN 1...5 means that VLAN's on range 1 to 5 are transported over this data flow (bundling).
• The priority (Pri) for a group of VLAN's can also be defined as a range, e.g. from Pri3 to Pri5.
• RSVID 1,2,3 means that S-VLAN 1,2 and 3 are registered on this port.
• (d), (e), (f): these ETB ports are used as Bridge Network Interfaces respectively for the data flows a,
b, c.
• ETS ports, as well as ETB ones, can be Remote (for SDH) or Local (for LAN).
• Where ports are Remote, they need SDH XC and VCG association
• The frames are distributed only to the ports registered over the relevant S-VLAN, i.e. parts of the
“member set" distribution domain of that S-VLAN (SVID registration).
• More data flows can be created under one ETS port.
• More S-VLAN Id can be registered on a single port.
• More ports can be headed to one S-VLAN.
• More (or a range of) customer VLAN's can be defined on one Classifier (user VLAN Bundling).
• The CoS of one traffic (Priority) may be changed at the ingress of the provider bridge network, in
ETB port, RP option.
• The Protocol Type of one traffic (Protocol Type) may be changed at the ingress of the provider
bridge network, in ETB port, PT option.
• The Provider UNI/NNI or NNI/UNI connections are accomplished by means of “One-Step"
procedure (see “Delete Ets XC One Step (MAC & Virtual) for the Ethernet Port” (p. 4-256)).
............................................................................................................................................................................................................................................................
1 - 30 P/N 8DG15785AAAA
Protocols CT Operator’s Guide
............................................................................................................................................................................................................................................................
Protocols
Data frames
Figure 1-18 Ethernet Packet format
IPG
SFD
IPG Preamble Ethernet Frame
.... (7 Bytes) (64 to "maxFrame" Bytes) ....
(1)
• IPG= Inter Packets Gap

• Preamble= fixed pattern, used to lock the synchronization circuitry with the received frame's
timing
• SFD= Start of Frame Delimiter; it is fixed to 10101011
• Frame Size:
Minimum frame size: 64 bytes
Maximum frame size (MTU= Maximum Transmit Unit, or MRU= Maximum Receive Unit):
– MTU/MRU = 2026 bytes if the frame is “untagged"
– MTU/MRU = 2000 bytes for NNI interface
– MTU/MRU = 2026 bytes for UNI interface
Jumbo Frame (JF): frames with length greater than 2000 (UNI) or 2026 (NNI):
– JF-MTU/MRU = 2008 bytes
– JF-MTU/MRU = 2026 bytes
Figure 1-19 Ethernet packet and MAC frame format
Preamble DA SA Data + Pad FCS

L/T
FS
(7) (6) (6) (46 to n) (4)

(1) (2)
Frame
• Pre = Preamble
• FS = Frame Start, also called SFD: start of frame delimiter
• DA: Destination Address
• SA: Source Address
• n: max number of bytes contained in the data field, depending from the MTU value (see
Figure 1-18, (pg. 1-31)) in this case n= MTU-18
• L/T = Length (of-data-field) / Type; it indicates the Length or Type of the frame:
– If its value is less than 1536 decimal, then L/T field indicates the number of MAC client data
octets contained in the subsequent “Data" field of the frame.
– If its value is greater than or equal to 1536 decimal, then L/T field indicates the nature of the
MAC client protocol.
• PAD = optional field, containing fixed stuff, to be added in case that the “Data" field is less or
equal than 46 bytes, in order that the frame length (from DA to FCS) is at least 64 bytes.
• FCS = Frame Check Sequence: it contains a cyclic redundancy check (CRC), computed over all
fields except Preamble, SFD, FCS
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-31
CT Operator’s Guide Protocols
............................................................................................................................................................................................................................................................
Figure 1-20 Ethernet “Q-Tagged" MAC 802.3 frame format
Q-TAG
Preamble DA SA Data Pad FCS
1Q
TCI
L/T
FS
(7) (6) (6) (0 to n) (42 to 0) (4)
(1) (2) (2) (2)
• PRE: Preamble; FS: Frame Start; DA: Destination Addr.; SA: Source Addr.
• 1Q: “ProtocolType" 802.1Q field (a constant fixed value= hex“0x8100")
• TCI: Tag Control Information = (3bits: user priority 802.1p)+(1bit: CFI)+(12bits: VLAN identifier
802.1q); [CFI: Canonical Field Id.]
• L/T: MAC client Length/Type
Note: The PAD is an optional field, containing fixed stuff, to be added in case that the
data field is less or equal than 42 bytes, in order that the frame length (from DA to FCS) is
at least 64 bytes.
Figure 1-19, (pg. 1-31))
Figure 1-21 TCI Field format (802.1Q VLAN Tag)

0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
UP C VID
• UP: User Priority (3 bits)

• C: CFI, Canonical Field Identifier (1 bit)
• VID: VLAN Identifier (12 bits)
............................................................................................................................................................................................................................................................
1 - 32 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 1-22 Ethernet “Stacked VLAN" frame format
S-TAG Q-TAG
TCIP
1QP
Preamble DA SA Data Pad FCS
1Q
TCI
L/T
FS
(7) (6) (6) (0 to n) (38 to 0) (4)
(1) (2) (2) (2) (2) (2)
• PRE: Preamble; FS: Frame Start; DA: Destination Addr.; SA: Source Addr.
• 1Q: “ProtocolType" (PT) 802.1Q field (a constant fixed value= hex“0x8100")
• TCI: “Tag Control Information" = (3bits: user priority 802.1p)+(1bit: CFI)+(12bits: VLAN
identifier 802.1q); [CFI: Canonical Field Id.]
• L/T: MAC client Length/Type
• 1QP: 2 bytes “provider-ProtocolType" , similar to the 1Q identifier, settable by the Service Provider
• TCIP: 2 bytes “provider-Tag Control Information" , similar to the TCI bytes
– (3 bits: provider-priority) + (1bit: CFI) + (12bits: provider-VLAN id.),
– settable by the Service Provider
Note: Q-TAG is also called C-TAG (Customer Tag, or User Tag); S-TAG is also called
P-TAG
Note: the PAD is an optional field, containing fixed stuff, to be added in case that the
data field is less or equal than 38 bytes, in order that the frame length (from DA to FCS) is
at least 64 bytes.
Figure 1-19, (pg. 1-31))
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-33
............................................................................................................................................................................................................................................................
Figure 1-23 Ethernet “Stacked VLAN" frame format
1
2 GFP Core Header 4
3
4
octect -
transmission -
order -
GFP Payload Area 4 to 65535 octets
n
octet 1 2 3 4 5 6 7 8
bit bit transmission order
GFP Frame size and transmission order
16-bit Payload 2 bytes

length indicator
cHEC 2 bytes
GFP
(CRC-16)
Core
Header
Payload headers X = 4 to 64 bytes

(4-64 bytes)
GFP
Payload
Area Client
payload
information
field
N= 0 to 65535-X bytes
(Ethernet frame)
Optional
4 bytes
payload FCS
(CRC-32)
Fields constituting a GFP client frame
............................................................................................................................................................................................................................................................
1 - 34 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 1-24 Ethernet encapsulation into GFP frame (from G.7041/Y.1303)

Ethernet MAC Frame GFP Frame
Octets
2 PLI
2 cHEC
2 Type
7 Preamble 2 tHEC
1 Start of frame delimiter 0-60 GFP Extension Header
6 Destination Address (DA)
6 Source Address (SA)
2 Length Type GFP
MAC client data Payload
PAD
4 Frame Check Sequence (FCS)
Octets 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
Bits
Figure 1-25 Ethernet/LAPS encapsulation (ITU-T X.86)

nr. of bytes
LAPS Frame
nr. of bytes Flag (0x7E) 1
Ethernet Frame Address (0x04 1
Control (0x03) 1
7 Preamble 1st byte of SAPI (0xFE) 1
1 Start of Frame Delimiter 0-60 2nd byte of SAPI (0x01) 1
6 Destination Address (DA) Destination Address (DA)
6 Source Address (SA) Source Address (SA) Ethernet
2 Length/Type Length/Type frame
Client data Client data
46 to 1500
PAD PAD
4 FCS FCS
FCS of LAPS 4
Flag (0x7E) 1
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-35
............................................................................................................................................................................................................................................................
Figure 1-26 Ethernet Framing (on Local Ethernet Port)

DA SA L/T Ethernet payload FCS
P-VLAN C-VLAN
S-VLAN management
DA SA S-VLAN L/T Ethernet payload FCS
opportunity
Ethernet frame
Ethernet MAU
PRE FS Ethernet frame
(E, FE, GbE)
Ethernet Packet
Note:
• P-VLAN = Provider VLAN
• C-VLAN = Customer VLAN
............................................................................................................................................................................................................................................................
1 - 36 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 1-27 Ethernet over SDH Framing (Remote Ethernet Port)
Ethernet MAU PRE FS DA SA L/T Ethernet Payload FCS
DA SA L/T Ethernet Payload FCS
Ethernet Packet
Label Label Ethernet Packet

MPLS 1 2
Labelled Packet (MPLS)
PPP PPP Header MPLS packet PPP

PAD
HDLC Flag Addr Control PPP frame FCS
HDLC frame
SDH
VC4 or VC3 or VC12 frame
POH SDH payload
Notes:
P-VLAN = Provider VLAN
C-VLAN = Customer VLAN
Note:
• The FCS on GFP or LAPS is optionally included
• P-VLAN = Provider VLAN
• C-VLAN = Customer VLAN
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-37
............................................................................................................................................................................................................................................................
Protocol list
Either BPDU or VRRP Selective Tunnelling requires below configuration operations to
Management Operator:
• Definition of proper ETS Classifier Criteria’s;
• Provisioning of Layer 2 control Frames “on per port basis” and “on per flow basis”.
Table 1-3 L2 Control Protocols
MAC Address Protocol Description

01-80-C2-00-00-00 Customer BPDU (STP, RSTP, MSTP) (see “Customer BPDU” (p. 1-39))
01-80-C2-00-00-01 802.3 Pause Frames (see Note: )
01-80-C2-00-00-02 Slow Protocols (see “Slow Protocols” (p. 1-39))
01-80-C2-00-00-03 802.1X PAE (see “802_1X” (p. 1-40))
01-80-C2-00-00-04
Reserved for future MAC applications
01-80-C2-00-00-05
01-80-C2-00-00-06
Reserved for future Bridge operations
01-80-C2-00-00-07
01-80-C2-00-00-08 Provider BPDU (STP, RSTP, MSTP)
01-80-C2-00-00-09
Reserved for future Bridge operations
01-80-C2-00-00-0A
01-80-C2-00-00-0B
Reserved for future Provider Bridge operations
01-80-C2-00-00-0C
01-80-C2-00-00-0D Reserved for Provider GVRP (see “Provider GVRP” (p. 1-41))
01-80-C2-00-00-0E
Reserved for future Customer Bridge operations
01-80-C2-00-00-0F
01-80-C2-00-00-10 Bridge Management “Bridge management” (p. 1-40)
01-80-C2-00-00-20 Customer GMRP (see “Customer GMRP” (p. 1-41))
01-80-C2-00-00-21 Customer GVRP
01-80-C2-00-00-22
Reserved for future GARP applications (see “Customer GARP”
.....
(p. 1-42))
01-80-C2-00-00-2F
MAC Destination Address for VRRP packets (not available in current
01-00-5e-00-00-12
release)
Note: Pause frames on native local Ethernet interfaces are either

processed or dropped by the EFC functional block according to the
Flow Control configuration. For security reasons, any frame
received by the EFC with the Pause MAC Destination Address is
always dropped (there is no configuration option for this
behaviour).
............................................................................................................................................................................................................................................................
1 - 38 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Customer BPDU
The bridges have to determine the root bridge and compute the port roles (root,
designated, or blocked) with only the information that they have. To ensure that each
bridge has enough information, the bridges use special data frames called Bridge Protocol
Data Units (BPDUs) to exchange information about bridge IDs and root path costs.
A bridge sends a BPDU frame using the unique MAC address of the port itself as a source
address, and a destination address of the STP multicast address 01:80:C2:00:00:00.
BPDUs are exchanged regularly (every 2 seconds by default) and enable switches to keep
track of network changes and to start and stop forwarding at ports as required.
When a device is first attached to a switch port, it will not immediately start to forward
data. It will instead go through a number of states while it processes BPDUs and
determines the topology of the network. When a host is attached such as a computer,
printer or server the port will always go into the forwarding state, albeit after a delay of
about 30 seconds while it goes through the listening and learning states (see below). The
time spent in the listening and learning states is determined by a value known as the
forward delay (default 15 seconds and set by the root bridge). However, if instead another
switch is connected, the port may remain in blocking mode if it is determined that it would
cause a loop in the network.
Slow Protocols
Slow protocols frames, when supported on the UNI/ETH-IWI (for Aggregated Ports
belonging to a LAG), are processed before they are received by the ETS classifier. In this
case, it is possible to define a different behaviour for each slow protocol as defined in
Table 1-4. Slow protocol frames not processed at the UNI/ETH-IWI port level [example:
no supported Link OAM PDU Peering (due to disabled Ethernet Link OAM)] are
processed by the ETS classifier in the same way according to the MAC Destination
Address field (i.e. untagged Link OAM PDU are managed according to ETS Classifier
criteria for Untagged frames.)
Table 1-4 IEEE 802.3 Slow Protocols
MAC Address EtherType Sub-type Protocol Description

0x01
01-80-C2-00-00-02 0x8809 802.3 LACP and LAMP
0x02
01-80-C2-00-00-02 0x8809 0x03 802.3 EFM OAM
0x04
01-80-C2-00-00-02 0x8809 … Reserved for future 802.3 Slow Protocols
0x0A
01-80-C2-00-00-02 0x8809 Other Illegal values (see Note: )
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-39
............................................................................................................................................................................................................................................................
Note: When one slow protocol is supported, the slow protocol

frames received with an illegal sub-type are dropped by the slow
protocol processes.
802_1X
The 802.1X standard is designed to enhance the security of wireless local area networks
(WLANs) that follow the IEEE 802.11 standard. 802.1X provides an authentication
framework for wireless LANs, allowing a user to be authenticated by a central authority.
The actual algorithm that is used to determine whether a user is authentic is left open and
multiple algorithms are possible.
802.1X uses an existing protocol, the Extensible Authentication Protocol (EAP, RFC
2284), that works on Ethernet, Token Ring, or wireless LANs, for message exchange
during the authentication process.
In a wireless LAN with 802.1X, a user (known as the supplicant) requests access to an
access point (known as the authenticator). The access point forces the user (actually, the
user's client software) into an unauthorized state that allows the client to send only an EAP
start message. The access point returns an EAP message requesting the user's identity. The
client returns the identity, which is then forwarded by the access point to the
authentication server, which uses an algorithm to authenticate the user and then returns an
accept or reject message back to the access point. Assuming an accept was received, the
access point changes the client's state to authorized and normal traffic can now take place.
Bridge management
Bridges are data communications devices that operate principally at Layer 2 of the OSI
reference model. As such, they are widely referred to as data link layer devices. Bridges
allow connected and enabled packet forwarding between homogeneous networks. More
recently, bridging between different networks has also been defined and standardized.
Several kinds of bridging have proven important as internetworking devices. Transparent
bridging is found primarily in Ethernet environments, while source-route bridging occurs
primarily in Token Ring environments. Translational bridging provides translation
between the formats and transit principles of different media types (usually Ethernet and
Token Ring). Finally, source-route transparent bridging combines the algorithms of
transparent bridging and source-route bridging to enable communication in mixed
Ethernet/Token Ring environments.
Bridge controls data flow, handles transmission errors, provides physical (as opposed to
logical) addressing, and manages access to the physical medium by using various link
layer protocols that dictate specific flow control, error handling, addressing, and media-
access algorithms. Examples of popular link layer protocols include Ethernet, Token Ring,
and FDDI.
............................................................................................................................................................................................................................................................
1 - 40 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Bridges are capable of filtering frames based on any Layer 2 fields. For example, a bridge
can be programmed to reject (not forward) all frames sourced from a particular network.
Because link layer information often includes a reference to an upper-layer protocol,
bridges usually can filter on this parameter. Furthermore, filters can be helpful in dealing
with unnecessary broadcast and multicast packets.
Bridges can be grouped into categories based on various product characteristics. Using
one popular classification scheme, bridges are either local or remote. Local bridges
provide a direct connection between multiple LAN segments in the same area. Remote
bridges connect multiple LAN segments in different areas, usually over
telecommunications lines. Remote bridging presents several unique internetworking
challenges, one of which is the difference between LAN and WAN speeds. Although
several fast WAN technologies now are establishing a presence in geographically
dispersed internetworks, LAN speeds are often much faster than WAN speeds. Vast
differences in LAN and WAN speeds can prevent users from running delay-sensitive LAN
applications over the WAN.
Provider GVRP
It s a protocol that facilitates control of virtual local area networks (VLANs) within a
larger network. GVRP conforms to the IEEE 802.1Q specification, which defines a
method of tagging frames with VLAN configuration data. This allows network devices to
dynamically exchange VLAN configuration information with other devices.
GVRP is based on GARP (Generic Attribute Registration Protocol), a protocol that
defines procedures by which end stations and switches in a local area network (LAN) can
register and de-register attributes, such as identifiers or addresses, with each other. Every
end station and switch thus has a current record of all the other end stations and switches
that can be reached. GVRP, like GARP, eliminates unnecessary network traffic by
preventing attempts to transmit information to unregistered users. In addition, it is
necessary to manually configure only one switch and all the other switches will be
configured accordingly.
Customer GMRP
It provides a mechanism that allows bridges and end stations to dynamically register group
membership information with the MAC bridges attached to the same LAN segment and
for that information to be disseminated across all bridges in the Bridged LAN that
supports extended filtering services. The operation of GMRP relies upon the services
provided by the GARP.
The format of the GMRP packet is that of the GARP. However, the attribute type is
specific to GMRP: it can be as follows:
• Group Attribute Type.
• Service Requirement Attribute Type.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-41
............................................................................................................................................................................................................................................................
Customer GARP
It is a local area network (LAN) protocol that defines procedures by which end stations
and switches can register and de-register attributes, such as network identifiers or
addresses, with each other. Every end station and switch thus has a record, or list, of all the
other end stations and switches that can be reached at any given time.
When an attribute for an end station or switch is registered or de-registered according to
GARP, the set of reachable end stations and switches, called participants, is modified
according to specific rules. The defined set of participants at any given time, along with
their attributes, is a subset of the network topology called the reachability tree. Data
frames are propagated only to registered end stations. This prevents attempts to send data
to end stations that are not reachable.
GARP was previously called Group Address Registration Protocol.
............................................................................................................................................................................................................................................................
1 - 42 P/N 8DG15785AAAA
STP functionality (Spanning Tree Protocol) CT Operator’s Guide
............................................................................................................................................................................................................................................................
STP functionality (Spanning Tree Protocol)

Figure 1-28 Spanning Tree example
C
E
D H
F
G
PHYSICAL TOPOLOGY (example)
Active (forwarding) Port

A Active link
Active (forwarding) Port

B Active link
Root Bridge
C Blocking (discarding) Port
E
D H
F
G
ACTIVE SPANNING TREE TOPOLOGY (example)
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-43
CT Operator’s Guide STP functionality (Spanning Tree Protocol)
............................................................................................................................................................................................................................................................
Figure 1-29 Some examples of Bridges and Ports roles in xSTP network
DesignatedBridge for L6
RootPort for Bridge A DesignatedPort for LAN L6
A
L6 RootPort for Bridge B
AlternatePort
L1 for Bridge A B
L4
Root Bridge
L13
L9
DesignatedPort DesignatedPort
C for L4 for path H - I
L2 L15
L7 E L10
I
D H L16
DesignatedBridge
L3 for L4, L5, L7 BackupPort
L5 L11 for path H - I
L14
F L8
G
: Blocking (discarding) Port (Alternate or Backup role)
BRIDGE and PORT ROLES (example)
Note:
• A, B,...: bridges
• L1, L2, ...: LAN's
• The active STP topology is dynamic, therefore it will change on occurrence of certain
events/failures
• The Root Bridge (i.e. the root of the tree) is the bridge having the highest priority, or, at priority
equality, the identifier with lowest numerical value
• The STP procedure is managed by means of control frames BPDU (Bridge Protocol Data Unit)
• The “blocking" (or discarding) Ports can be configured to accept control BPDU frames
• Each Bridge and each Port has its own cost parameter and priority parameter
• The “Root Path Cost" for a given bridge is the sum of the costs of all the Root Port encountered
along the path to reach the Root Bridge. If this value is zero, the selected bridge is the Root Bridge.
• The best path from a bridge to the root is calculated taking into account the cost and, at costs
equality, the priority parameters of ports and bridges along the path
• The parameters indicated will be detailed hereinafter in this handbook, where they will be used (see
“ConfigureBridgePort” “Create Provider OutFlow for an Ethernet Port” (p. 4-115) and
subsequents. See also, for instance: “STP-Per Bridge Management by the ControlPlane of the
Bridge Port” (p. 4-137), “STP-PerPort Management by the ControlPlane of the Bridge Port”
(p. 4-140), etc.).
............................................................................................................................................................................................................................................................
1 - 44 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 1-30 PER-VLAN Spanning Tree example
A
Registered VLAN's 7,8
3,5,7 B
5,3
7,8 8,9
C
4,5
5,7 E
D 9 H
6,7 7,9
6
9
F 7,9
G
PHYSICAL TOPOLOGY and Registered VLAN's
Blocking port towards VLAN 7

b7
A
7,8
b5
3,5,7 B
5,3
Root Bridge
7,8 8,9
for VLAN 5
C
4,5
5,7 E
D 9 H
b9
6,7 7,9
6
9
F 7,9 Root Bridge

b7 G for VLAN 7
: Blocking Port with respect to the indicated VLAN
PER-VLAN ACTIVE SPANNING TREE TOPOLOGY (example)
Note: In this case, the STP procedure is applied, independently, to

each afferent VLAN, as if there were as many independent networks
as the VLAN's are (see example in next figure).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-45
............................................................................................................................................................................................................................................................
Figure 1-31 PER-VLAN Spanning Tree (example of active topology for a single
VLAN)
Blocking port towards VLAN 7

b7
A
7,8
3,5,7 B
7,8
C
5,7 E
6,7 7,9
F 7,9 Root Bridge

b7 G for VLAN 7
: Blocking Port with respect to the indicated VLAN
PER-VLAN ACTIVE SPANNING TREE TOPOLOGY

(example for VLAN 7)
RSTP
The RSTP (Rapid Spanning Tree Protocol) differs from STP in some parameters:
the convergence time is reduced to 5 sec (instead it is 30 s in STP) and in the possible
States of the Ports: Data Frame Discarding, Learning, Forwarding (STP Port States are
5, including “Disabled” and “Listening”). The descriptions of these parameters are
given in Configure Bridge Port.
The BPDU (Bridge Protocol Data Unit) Frame for MSTP networks (from IEEE Std.
802.1Q-2003):
“MSTP (Multiple STP) provides simple and full connectivity for frames assigned to
any given VLAN throughout a Bridged LAN comprising arbitrarily interconnected
Bridges, each operating MSTP, STP or RSTP. MSTP allows frames assigned to
different VLAN’s to follow separate paths, each based on an independent Multiple
Spanning Tree Instance (MSTI), within Multiple Spanning Tree (MST) Regions
............................................................................................................................................................................................................................................................
1 - 46 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
composed of LAN’s and or MST Bridges. These Regions and the other Bridges and
LAN’s are connected into a single Common Spanning Tree (CST)...” (from IEEE Std.
802.1Q-2003).
The MSTP-BPDU frame (see figure below) is compatible with the STP/RSTP BPDU,
with the addition of fields conveying MST topology information and Regional
Instances. Each MST Instance is represented by an additional field attached to the
MSTP-BPDU, called MSTI Configuration Message. Up to a max of 64 “MSTI
Configuration Messages” are allowed in a network.
Figure 1-32 MSTP BPDU Frame format

Octet
Protocol Identifier 1-2
Protocol Version Identifier 3
BPDU Type 4
CIST Flags 5
CIST Root Identifier 6-13
CIST External Path Cost 14-17
CIST Regional Root Identifier 18-25
CIST Port dentifier 26-27
Message Age 28-29
Max Age 30-31
Hello Time 32-33
Forward Delay 34-35
Version 1 Length = 0 36
Version 3 Length 37-38
MST Configuration Identifier 39-89
CIST Internal Root Path Cost 90-93
CIST Bridge Identifier 94-101
CIST Remaining Hops 102
MSTI Configuration Messages 103-39 +
Version 3
(may be absent) Length
MSTI BPDU parameters and format

Octet
MSTI Flags 1
MSTI Regional Root Identifier 2-9
MSTI Internal Root Path Cost 10-13
MSTI Bridge Priority 14
MSTI Port Priority 15
MSTI Remaining Hops 16
MSTI Configuration Message parameters and format
In particular, the octets in the field “MST Configuration Identifier” of the frame contain
the meaningful parameters defining a Region, i.e.:
• Configuration Identifier Format Selector (fixed by the standard to value 0)
• Configuration Name
• Revision Level
• Configuration Digest
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-47
............................................................................................................................................................................................................................................................
Thus, by definition, Bridges having the same value of “MST Configuration Identifier” are
considered to be part of the same Region, if they are connected between them by a LAN
contained in the same Region, i.e. if the CIST designated Bridge for that LAN is in the
same Region. (CIST = Common and Internal Spanning Tree).
In a same region, frames assigned to different VLAN’s can follow separate paths, each
based on an independent nMultiple Spanning Tree Instance (MSTI); in other words, the
VLANs associated to an Instance of the Region are routed independently, as if there were
as many independent networks as the VLAN-Instances are.
The parameters of one Port of an MSTP Bridge can be set in differentiated mode, for
different MSTP Instances.
Furthermore, a Region of an MSTP network can be seen as a single Bridge whose Ports
are those Ports that are connecting the Region with the other Region of the network.
An example of MSTP Bridge network and MSTID use is shown in Figure 1-35, (pg.
1-51).
The setting of the MSTP parameters is done by means of the option Configure Bridge
Port, described in “Configure Bridge Port (Provider)” (p. 4-125), and subsequent ones.
Figure 1-33 MSTP Network topology example
Region 1
D
A C
E H
Region 2
X Y
F
G
Region 4 Region 5
Region 3
MSTP TOPOLOGY Example
One Bridge in all the network is chosen as the CIST Root Bridge: that one having the
lowest numerical Bridge Identifier of all the Bridges in the network.
One Bridge in each Region is chosen as the CIST Regional Root Bridge: that one having
the lowest External Root Path Cost through a boundary Port.
............................................................................................................................................................................................................................................................
1 - 48 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Bridges A, C and D are in the same MST Region (Region 1) because they have the same
“MST Configuration Identifier”.
Bridges B, E and H belong to Region 2 because they have the same “MST Configuration
Identifier”, but different from those contained in Region 1.
Bridge G is in Region 3 because its “MST Configuration Identifier” is different from the
Bridges contained in Region 1 and Region 2.
Bridge F is outside of any region, because it is not an MSTP Bridge (can be STP or
RSTP).
Bridges X and Y are in different Regions, even though they had the same “MST
Configuration Identifier”, because the LAN that connects them, e.g. by means of an hub,
is in a different Region.
Region 1 and Region 2 can be seen, from the MSTP point of view, as “collapsed” single
bridges, as illustrated in Figure 1-34, (pg. 1-50).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-49
............................................................................................................................................................................................................................................................
Figure 1-34 MSTP “collapsed” topology example
Region 1
RB1
RB2
Region 2
X Y
Region 4 Region 5 F
G
Region 3
MSTP "collapsed" TOPOLOGY
............................................................................................................................................................................................................................................................
1 - 50 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 1-35 MSTP, VLAN differentiated routing example

Region 1
5,7,10,11 A Registered VLANs
5,7,10,11
Notes:
5,7,10,11 5,7,10,11 all the VLANs involved in a Region
should be registred at all the port of the Region
5,7,10,11 (recommended)
C D
5,10 5,7,10,11
7,11
5,10 7,11
X Y
Equivalent MSTP for different VLANs

Supposing that:
VLAN 5 and 10 are associated to MSTID = 1
VLAN 7 and 11 are associated to MSTID = 2
Region 1
CIST RootBridge
A
F 5,10 F 5,10
F 7,11 F 7,11 Instance 1
Instance 2
F 5,10 b 5,10
F 7,11 The path A-D for VLANs 7 and 11 may be chosen by
F 7,11
F 5,10 MSTP if, for example, the PathCost are the relevant
F 7,11 ports, for MSTID 2, has benn set at lower value than
C D that on path A-C
The same pratice can be followed to route VLANs
F5,10
5,10 on path A-C
F7,11
If a failure occurs, for example on path A-D, then the
MSTIP procedure will re-route VLANs 7 and 11 on path A-
C-D-Y
F5 F7
F 10 F 11 Notes:
X Y F7: VLAN 7 is forwarded, at the relevant Port
b7: VLAN 7 is blocked, at the relevant Port
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-51
CT Operator’s Guide Virtual Concatenation and LCAS
............................................................................................................................................................................................................................................................
Virtual Concatenation and LCAS

The ISA-ES system supports (at the SDH side) Virtual Concatenation and LCAS features.
The Virtual Concatenation consists in the fact that frames not fitting into a single SDH-
container are transported over more individual containers, indicated with the symbol VCn-
Xv (e.g. VC12-3v indicates the virtual concatenation of 3 VC12).
The original frame is paralleled Time Slot-by-Time Slot and loaded over different
payloads.
The individual containers can follow different paths in the network, with different delays,
and they need to be reassembled at the end points, taking into account the different path
delays.
This feature is compliant to ITU-T G.707 rec.
A schematic example is illustrated in the figure below (example with concatenation
granularity = 3).
The LCAS feature (Link Capacity Adjustment Scheme) permits the operator to “hitless"
modify the bandwidth capacity of a virtual concatenated link, in order to meet the
bandwidth needs of the service (by adding or removing virtual containers in all the
involved nodes of the network). It can also temporarily remove failed links of the group, in
automatic and hitless mode. In case of failure or addition of links, the traffic is
automatically redistributed over the working links. Reference: ITU-T G.7042 rec.
Figure 1-36 Virtual Concatenation (example)

Byte "big" Ethernet frame
a1 a2 a3 a4 a5 a6 a7 a8 a9 a10 a11 a12 Originating

b1 b2 b3 b4 b5 b6 b7 b8 b9 b10 b11 b12 Point
time slot 1 2 3 4 5 6 7 8 9 10 11 12
SONET / SDH network
VCG
VC number 1, path delay 1 VC number 2, path delay 2 VC number 3, path delay 3
a1 a4 a7 a10 a2 a5 a8 a11 a3 a6 a9 a12 SONET/SDH

Network
b1 b4 b7 b10 b2 b5 b8 b11 b3 b6 b9 b12
a1 a2 a3 a4 a5 a6 a7 a8 a9 a10 a11 a12

Terminating
b1 b2 b3 b4 b5 b6 b7 b8 b9 b10 b11 b12 Point
............................................................................................................................................................................................................................................................
1 - 52 P/N 8DG15785AAAA
Internal Loop-Back management CT Operator’s Guide
............................................................................................................................................................................................................................................................
Internal Loop-Back management

The ISA-ES system supports the Internal Loop-Back feature, in order to check the
network link integrity.
The loop-back configuration is done by means of “Configure (local) Ethernet Port”
(p. 4-67).
The loop-back scheme is illustrated in the Figure 1-37, (pg. 1-53).
Figure 1-37 Internal Loop Back scheme
Local Remote Remote Local

Port Port Port Port
IF XC OF OF XC IF
SONET
DTE DTE
SDH
OF XC IF IF XC OF
Shutdown Internal
in case of LB LB
Note:
• The internal LB is possible only in case of Port-to-Port connection (P2P)
• LB = Loopback
• IF = InFlow
• OF = OutFlow
• XC = Cross-connection
• DTE = Data Terminal Equipment
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-53
CT Operator’s Guide System alarm management
............................................................................................................................................................................................................................................................
System alarm management

CSF alarm management
The ISA-ES system supports the CSF alarm management (Client Signal Fail), in order to
indicate signal failure occurrences on Ethernet line or on network link. The CSF alarm is
coded inside the GFP frame, in the Type bytes of the header.
The Shut-Down triggering (on local-port) can be enabled or disabled by means of
Configure (LOCAL) Ethernet Port Î MAU: Configure Remote Client = shutdown, see
“Configure (local) Ethernet Port” (p. 4-67).
The CSF is managed by means of Transmit Capability, see “Configure (remote) Ethernet
Port” (p. 4-80).
The CSF can be managed using the old G.7041 standard (unidir and bidir) or the new
G.7041 standard (unidir UPI-LOF and bidir UPI-LOF). The two functionalities are the
same, but changing only the coding of UPI byte inserted into the GFP frame. UPI= User
Payload Identifier. The CSF is inserted towards SDH network, if TransmitCapability is
enabled, in case of LOS (unidir) or in case of LOS, LOF, TSF, PLM (bidir). The
ShutDown on TX Local Port is carried out if Conf. Remote Client = shutdown, on the
same local Port.
The CSF mechanism scheme is illustrated in Figure 1-38, (pg. 1-54).
Figure 1-38 CSF alarm management

CSF insertion (bidir)
LOF, TSF, PLM detection

(P2P)
IF XC OF IF XC O F
Local Remote SONET Remote Local
DTE DTE
Port Port SDH Port Port
OF XC IF IF XC O F X
(P2P)
Shutdown in CSF detection CSF insertion LOS detection
case of CSF
detection (if Conf.RemoteClient= Shutdown) (if GFP - Transmit Capability is enabled)
CSF insertion modality:

(if GFP-TransmitCapability is enabled)
– UNIDIR (or Unidir UPI-LOF): CSF is inserted after LOS detection on connected Local Port
– BIDIR (or Bidir UPI-LOF): CSF is inserted after LOS or LOF or TSF or PLM detection
LocalPort TxShutDown: triggered by CSF detection, if Conf.RemoteClient = Shutdown
Note:
• The management of CSF alarm is possible only in case of GFP port type
• The shut-down mechanism is possible only in case of Port-to-Port connection (P2P)
• IF = InFlow
• OF = OutFlow
• XC = Cross-connection
............................................................................................................................................................................................................................................................
1 - 54 P/N 8DG15785AAAA
System alarm management CT Operator’s Guide
............................................................................................................................................................................................................................................................
VC-AIS alarm management

The ISA-ES Data system supports the VC-AIS alarm management (Virtual Container -
Alarm Indication Signal), in order to propagate Ethernet signal failure indications to the
SDH systems. This option is possible only in case of GFP framing on server layer, in Port-
to-Port connection. The VC-AIS insertion is unidirectional.
The VC-AIS alarm is coded inside the SDH frame header. The VC-AIS function is
supported on 10/100 Mbps ports (also on 1000 Mbps port, in ES4 board).
The VC-AIS is managed by means of Transmit Capability item (see Figure 1-36, (pg.
1-52). and “Configure (remote) Ethernet Port” (p. 4-80)).
The Transmit Capability possible options are: unidir/ bidir / Unidir VC-AIS/ disabled.
For this issue, the Transmit Capability parameter has to be set to Unidir VC-AIS.
The AIS alarm will be inserted on the SDH transport containers, as a consequent action
after local Ethernet Port failure (Ethernet LOS detection).
The other Transmit Capability options (unidir/ bidir/ ... etc.) are relative to CSF alarm
management (Client Signal Failure), described in “CSF alarm management” (p. 1-54).
The VC-AIS mechanism scheme is illustrated in Figure 1-39, (pg. 1-55).
Figure 1-39 VC-AIS alarm management

LOS detection
VC-AIS insertion
IF XC OF
Local Remote SONET
DTE
Port Port SDH
The VC-AIS alarm is inserted on the SONET/SDH containers upon Ethernet LOS
detection.
The VC-AIS alarm insertion is uni-directional
The ShutDown on local port must be disabled
The Flow Control function on local port must be disabled
Note:
• The management of VC-AIS alarm is possible only in case of GFP server layer
• The management of VC-AIS alarm is possible only in case of Port-to-Port connection (P2P)
• IF = InFlow
• OF = OutFlow
• XC = Cross Connection
This option is obtained, after selecting a REMOTE EthernetPort, by means of the
contextual pop-up menu, or by selecting in the menu-bar:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-55
CT Operator’s Guide System alarm management
............................................................................................................................................................................................................................................................
Transmission Î Ethernet Port Management Î Configure Ethernet Port.

An example of the window displayed (GFP sector) is reported in figure below.
For a correct working, please follow the instructions noted below.
Important! The switch between GFP and LAPS framing type is
done by means of Transmission: Ethernet Port Management Î
Substitute Server Layer menu option (when the REMOTE port is
in down state).
Important! The Flow Control function must be disabled on
LOCAL port (see “Port Mirroring management” (p. 1-62)). This is
done by means of Transmission Î Ethernet Port Management Î
Configure Ethernet Port Î MAU: DefaultPause = disabled,
AutoNegotiation- AdminStatus = enabled , AutoNegotiation-
LocalCapabilityOptions (current)" = b10baseTFD (in case of
10Mbps) / b100baseTXFD (in case of 100Mbps) / b1000baseXFD
(in case of 1000Mbps). See Figure 1-41, (pg. 1-57) for 10/100 Mbps
case.
Important! The ShutDown function must be disabled on LOCAL
port. This is done by means of Transmission Î Ethernet Port
Management Î Configure Ethernet Port: Conf.RemoteClient =
disabled ; see Figure 1-41, (pg. 1-57) and “Configure (local)
Ethernet Port” (p. 4-67).
Important! The TSF alarm visualization must be disabled on
REMOTE port. This is done by means of the following steps:
– Create a specific ASAP with TSF alarm cleared, by means of
Configuration Î Alarms Severity Î Create; then selecting
the TSF alarm and associate to it the Severity = cleared; then
giving a name in the field ASAP Identifier (e.g. TSF_cleared).
– Associate this created ASAP to the remote port by means of
Transmission Î Ethernet Port Management Î Configure
Ethernet Port Î AsapName = TSF_cleared.
............................................................................................................................................................................................................................................................
1 - 56 P/N 8DG15785AAAA
System alarm management CT Operator’s Guide
............................................................................................................................................................................................................................................................
Figure 1-40 Configure (remote) EthernetPort: GFP: VC-AIS setting
Figure 1-41 Configure (local) EthernetPort: MAU: FlowControl and ShutDown

disabling
FlowControl
Pause
ShutDown
disabling
FlowControl
disabling
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-57
CT Operator’s Guide Auto-Negotiation management
............................................................................................................................................................................................................................................................
Auto-Negotiation management
The ES1/4 system supports the start up of a communication link by means of the Auto-
Negotiation function. Possible only in Point-To-Point links.
AutoNegotiation is supported on electrical 10 Mbps and 100 Mbps (FE), and on optical
1Gbps interfaces (only on ES4N-enhanced board). It is not supported on optical 10/100-
FE interface.
This function provides the capability, for an ethernet local interface, to advertise the
interface connected at the far end about its transmission facilities (rate, Half Duplex or
Full Duplex technology, etc.), and to detect the same information sent from the far end
device.
In this way the two connected devices can communicate their transmission capabilities in
order to determine if they are compatible. They can then establish the data transmission at
the best conditions offered by their common technology.
For example:
– one interface can work at 10Mbps, 100Mbps-HD. (HD= Half Duplex)
– the other interface can operate at 100Mbps-HD, 100Mbps-FD. (FD= Full Duplex)
then the Auto-Negotiation algorithm will select the best capability common to the two
connected devices, that is 100Mbps-HD.
WARNING
Half Duplex (HD) transmission mode is used in an area where several ethernet
interfaces are interconnected and share the same LAN medium. Multiple and
simultaneous attempts to access the same medium can occur, causing
transmission interferences. The arising conflicts are managed by means of the
CSMA/CD protocol.
Full Duplex (FD) transmission mode is used in a point to point connection,
where only two ethernet interfaces are connected by means of a link segment,
and they can transmit and receive simultaneously without transmission
interferences.
The setting of the Auto-Negotiation function is done by means of the Configure Local
Ethernet Port option, described in “Configure (local) Ethernet Port” (p. 4-67). See also
next Figure 1-42, (pg. 1-60).
............................................................................................................................................................................................................................................................
1 - 58 P/N 8DG15785AAAA
Flow-Control management CT Operator’s Guide
............................................................................................................................................................................................................................................................
Flow-Control management
The ISA-ES Data system supports the Flow Control feature (FC). Only in Full Duplex
transmission modality, and only in Port-To-Port links (P2P).
This function provides the capability, for an ethernet system, to advertise the system
connected at the far end about its state of congestion. The receiving system, when starts to
be congested, sends a special Pause MAC control frame (PF), in order to inform the far-
end connected system to stop sending new frames for a given period of time. After this
pause period the data transmission is continued.
The FC is initiated when the data rate of an ingress port exceeds the max bandwidth on the
corresponding egress port.
FC can be Symmetric or Asymmetric:
• Asymmetric FC: the local system can generate PF towards peer ethernet system, but
cannot support incoming PF: input PF are silently discarded.
• Symmetric FC: the local system can generate PF towards peer ethernet system. It
supports also incoming PF: input PF are used to slow down the rate on the opposite
direction of the link towards peer ethernet system.
For instance, FC starts when the rate on a local port exceeds the capacity of the
corresponding Sdh-VC on the connected Remote Port.
In case of 1Gb Port (ES4 board), the FC is started also if the received rate exceeds the
value set on Fractional Rate (not available in current release).
WARNING
In occurrence of FlowControl enabled, the traffic Policing should be disabled.
The setting of the Flow Control function is done by means of the “Configure (local)
The LocalPort-MAU Configuration dialog window is also reported in next
Figure 1-43, (pg. 1-61).
1. In case of AutoNegotiation disabled (i.e. with AutoNegotiation Î Admin.Status =
disabled), the FlowControl is configured as follows:
– enabling: select, in Default Pause item: asymmetric or symmetric options
– disabling: select, in Default Pause item: disabled
2. In the case of AutoNegotiation enabled (i.e. with AutoNegotiation Î Admin.Status =
enabled). In this case the above said Default Pause item is not considered and the
FlowControl is configured as follows:
– FlowControl enabling:
for 100Mbps case, Asymmetric FC:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-59
CT Operator’s Guide Flow-Control management
............................................................................................................................................................................................................................................................
– select, in Local Capability Options, in the available field, the following 3

items: b100baseTXFD, bFdxAPause and bFdxPause.
for 100Mbps case, Symmetric FC:
– select, in Local Capability Options, in the available field, the following 3
items: b100baseTXFD, bFdxSPause and bFdxPause.
– select: b10baseTFD, bFdxAPause and bFdxPause.
– select: b10baseTFD, bFdxSPause and bFdxPause.
– select: b1000baseXFD, bFdxAPause and bFdxPause.
– select: b1000baseXFD, bFdxSPause and bFdxPause.
FlowControl disabling:
select, in Local Capability Options, in the available field, only the following one
item: b100baseTXFD (100Mbps case). In case of 10Mbps: b10baseTFD. In case
of 1000Mbps: b1000baseXFD.
Figure 1-42 Flow Control scheme

ETH Rx SDH Tx
BW BW
(P2P)
PF-R IF XC OF
Eth Local Remote SONET
DTE Port Port /SDH
PF-T OF XC IF
ETH Tx SDH Rx
BW BW
Asymmetric FC:
• EthRx-BW > SdhTx-BW => PF-T are generated to slow down Eth-DTE rate
• EthRx-BW > SdhTx-BW => PF-R are silently discarded by LocalPort
Symmetric FC:
• EthRx-BW > SdhTx-BW => PF-T are generated to slow down Eth-DTE rate
• EthRx-BW > SdhTx-BW => PF-R are accepted by LocalPort and the Tx-rate towards
Eth-DTE is slowed down
Note:
• The FlowControl is supported only in case of Port-to-Port Connection (P2P)
• IF = InFlow, OF = OutFlow, BW = Bandwidth
............................................................................................................................................................................................................................................................
1 - 60 P/N 8DG15785AAAA
Flow-Control management CT Operator’s Guide
............................................................................................................................................................................................................................................................
• PF-R = Pause Frame received

• PF-T = Pause Frame transmitted
• XC = Cross Connection
Figure 1-43 Configure (local) EthernetPort: MAU: FlowControl setting

MAU - 10/100 FE Port
FlowControl1
AutoNegotiation
enabling/disabling
FlowControl2
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-61
CT Operator’s Guide Port Mirroring management
............................................................................................................................................................................................................................................................
Port Mirroring management

This function is activated in Transmission context, in the “Configure (local) Ethernet Port”
(p. 4-67).
WARNING
It is not supported on Remote Ports, and on Link Aggregations, and LAG-Ports.
It is not supported on GE Port (ES4 board).
It is not supported on ES1-3FE board.
The function of this option is to create a copy of the traffic over a port in service. The copy
of this traffic is sent to another port, without affecting the services alive on the original
port.
The adding or removing of mirroring ports does not affect the in-service traffic.
LAG ports can not be mirrored.
This feature can be used for testing or analysis of the traffic on a port.
Mirroring can be done either on received or on transmitted traffic, but only one direction
of only one port at a time can be mirrored. The traffic direction on the “copy” mirror-port
is always outgoing.
An illustrative example is reported in Figure 1-44, (pg. 1-63).
The ES1/4 system provides some pre-defined ports (mirror-port) dedicated for mirroring
the other ports, in the following combinations:
ES1-8FE and ES1-8FX:
input or output Local Ports 9 to 15 ==> mirrorable on mirror-port 16
WARNING
Only one single direction of one single port at a time can be mirrored over a
mirror-port.
ES4-8FE:
input or output Local FE Ports 20 to 26 ==> mirrorable on mirror-port 27 (GE Local
Port 19 can not be mirrored)
WARNING
Only one single direction of one single port at a time can be mirrored over a
mirror-port.
............................................................................................................................................................................................................................................................
1 - 62 P/N 8DG15785AAAA
Port Mirroring management CT Operator’s Guide
............................................................................................................................................................................................................................................................
Figure 1-44 Port Mirroring example

Rx1-mir Rx1-mir
p3
p3
Rx1 Tx2
p1 XC p2
Tx1 Rx2
p3 p3
Tx1-mir Rx1-mir
Traffic Rx1 on port p1 is mirrored on port p3, or

Traffic Tx1 on port p1 is mirrored on port p3, or
Traffic Tx2 on port p2 is mirrored on port p3, or
Traffic Rx2 on port p2 is mirrored on port p3
Note: Port p3 is the unique mirror-port, this example illustrates
that p3 can be used for mirroring different ports and different
directions, but in mutually exclusive mode.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-63
CT Operator’s Guide Resource Management Indication
............................................................................................................................................................................................................................................................
Resource Management Indication

The System is able to:
• monitor and count the amount of dynamic NE resources, where dynamic NE resources
(e.g. ETS Classifier, ETS Inflow, ETS Outflow....) are mapped inside NE internal
resources through complex NE internal algorithms;
• report the “used amount of entries” and the “available amount of entries” (associated
to each dynamic NE resource) to a Management operator, informing Management
Operator when available resources are exhausted.
Above both combined capabilities allow to verify the “feasibility” of a network
configuration to be applied to multiple NEs, via checking of both bandwidth resources and
System local resources (for each NE), anticipating errors in case of resources exhausted on
a single NE.
Resource Management Indication feature is supported via Resource Management Pools
defined “on per NE basis”, and providing <Nominal values, Used entries, Available entries
> 3-ple for each System resource up to granularity (refer to below) of:
• ETS Layer Transmission/Connection dynamic resources (Ethernet Classifiers, ETS In-
Flows, ETS Out-Flows and ETS Cross-connections);
• Ethernet Bridge dynamic resources [Ethernet OAM MEPs, ACLs..];
• Number of “per VLAN basis” Rapid Spanning Tree Instances and Bridge Control
Plane load.
Resource Management Pools

Packet processor CAM Applied via Flow Set
ETS (Ethernet) Classifier Applied
ETS In-Flows Applied to BOTH Ethernet and Provider Bridge ETS Inflows
ETS Out-Flows Applied to BOTH Ethernet and Provider Bridge ETS Outflows
ETS Cross-Connections Applied
“per VLAN Basis” Rapid Applied
Spanning Tree Instances
Sustained Control Plane Load Applied
(#supported packets every sec)
Ethernet OAM MEPs Applied
VLAN Port Association (VPA) Applied
ACL’s Applied
............................................................................................................................................................................................................................................................
1 - 64 P/N 8DG15785AAAA
Resource Management Indication CT Operator’s Guide
............................................................................................................................................................................................................................................................
The System is able:

• to update Resource Management Pools (Nominal, Used and Available) 3-ple values,
where the nominal values are not currently profiled, depending from both “on per NE
basis” dynamically allocated internal resources and performance reasons;
• to keep aligned the values inside Management Pools with Packet processor CAM
tightly coupled with NE hardware resources.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-65
CT Operator’s Guide Bridging Data Plane
............................................................................................................................................................................................................................................................
Bridging Data Plane

IGMP Snooping management
The ISA-ES system supports the IGMP function (Internet Group Multicast Protocol), as
specified in international standard rec. IETF-RFC 1112, 2236, 3376.
It is configurable by means of the Transmission menu, ISA Î Configure IGMP and
EthernetPort Î Configure IGMP options (see “Configure IGMP” (p. 4-155) and
subsequent paragrahs). It is not allowed in case of MAC Bridge.
The function of this option is to configure the OMSN+ES equipment as a “Proxy”
equipment, in order to intercept and inspect IP packets of level 3 transporting IGMP
information. In this way the ISA-ES (that is a level 2 Switch) can check prospective
requests of multicast traffic (using IGMP packets) between users and IP-Multicast Routers
inserted into the network (i.e. IGMP Snooping activity). According to requests of
“Multicast Join” or “Multicast Leave” received from users, the OMSN+ES system
manages the forwarding or the shutting down of Multicast traffic on Ports towards the
connected users, in order to save band resources.
The Multicast packets are sent only to ports that are part of the IGMP group.
Further the IGMP system can provide to reduce the traffic of periodic packets between the
Router and the users, by summarizing the individual Reports (JoinReports and
LeaveReports) from users (called also hosts) in one single collective Proxy Report towards
the Router.
The Leave and Join reports are dynamic events traced on the FDB table, as well as the
Query messages periodically sent by the Router to discover its IGMP members.
An application example is reported in figure below.
............................................................................................................................................................................................................................................................
1 - 66 P/N 8DG15785AAAA
Bridging Data Plane CT Operator’s Guide
............................................................................................................................................................................................................................................................
Figure 1-45 IGMP application example
IP-MR
g1....g6
g1....g6
NE-ES1
IGMP Ring
NE-ES2 NE-ES4
NE-ES3
g2
g1
g5 g3 V1,V2,V3 V4,V5,V6
g4
g1-g3 g4-g6
DSLAM1 DSLAM2
g1 g2 g3 g6 g4 g5
U1 U2 U3 U4 U5 U6
g1,g2,...., g6 are Multicast Group packets flows

V1,V2,...,V6 are VLAN identifiers registered on given ports
u1 to u6 are users interested in Multicast trafic accessed by means of appropriate DSLAm equipments
IP-MR= IP Multicast Router equipment

NE-ES = OMSN equipped with ISA-ES Boards
IGMP Snooping Statistics

The System, as Provider Bridge, supports History Performance Monitoring counters for
IGMP Snooping (DSL Forum TR-101 document).
IGMP Snooping counters are explicitly activated from Management Operator (with 15
minutes [up to 16 stored “15 min basis” PM data] and/or 24 h [1 stored “24 h basis” PM
data] Granularity periods) and with below different granularities:
• “on per <VLAN> basis” IGMP Snooping counters;
• “on per <VLAN, port> basis” IGMP Snooping counters;
• “on per <VLAN, Multicast IP Address> basis” IGMP Snooping counters.
The System supports a maximum number of 128 IGMP Monitoring Points (i.e. with either
15 minutes or 24 h granularity periods) selected shared among activated instances.
The operative function is described in “IGMP snooping statistics” (p. 4-273).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-67
CT Operator’s Guide Link Aggregation management
............................................................................................................................................................................................................................................................
Link Aggregation management

The ES1 and ES4 systems support the Link Aggregation at the Ethernet side, as specified
in IEEE Std. 802.3ad-2000; it is a technique to aggregate many data streams into a single
logical link. The resulting aggregate link will be treated by the system (with regard to
instances about STP, IGMP, network protections, etc.), as a single link. It permits to
overcome the bandwidth limitation of the single ethernet interfaces, or to protect the
traffic.
Permitted port rates to be aggregated are FE (100Mbps), FX ports aggregation is
supported only on ES1 board, GbE port aggregation on ES4 board is not supported. Ports
to be aggregated on the same group must be homogeneous, i.e. the same type.
The max number of ports (LAG-size) to be aggregated is 4; (LAG stands for Link
Aggregation Group).
Links may be anytime added or removed to/from the bundle.
Its management in the network is based upon the communication, between the aggregate
partner equipment, of LACP messages (Link Aggregation Control Protocol). The LACP
packets transport information about set-up, aggregation capability, links failures,
automatic reconfiguration after failure, etc.
The Link Aggregation control messaging is managed by means of special control frames
LACPDU (Link Aggregation Control Protocol Data Unit), periodically sent, in band, by
the nodes using the Link Aggregation function. The LACPDU frame format is illustrated
in Figure 1-46, (pg. 1-71).
The packets distribution over the constituting links is based upon classification of MAC
SA and DA (Source Addresses and Destination Addresses), all packets belonging to the
same conversation (i.e. same MAC-DA/SA) are transported over the same link.
The packets can not be fragmented, i.e. a packet is transmitted entirely on the same link.
More conversations (i.e. different MAC SA/DA) can be transported on the same link.
A fair load-balancing is not guaranteed, since conversations and packets can not be
fragmented.
A priority value is associated to each port of the bundle, embedded in the Port Identifier.
The Priority is coded on 16 bits (of which only 8 are used), lower values meaning higher
priority.
A port of the aggregate is classified, by the system, in Active or Stand-by state, depending
from the port-priority values and from the LAG-size. E.g.: if port-rate =100Mbps, LAG-
size =5, number of ports =7, then 2 ports (those ones having lower priorities) are classified
as “stand-by” by the system.
............................................................................................................................................................................................................................................................
1 - 68 P/N 8DG15785AAAA
Link Aggregation management CT Operator’s Guide
............................................................................................................................................................................................................................................................
In case that the port-priorities between the two connected equipment do not match
properly, then the Master system can change the port-priorities of the peer system; (Master
system is the one having the lower System-Identifier value. System-Identifier is composed
of 2 octets of System-Priority value and 6 octets of the System-MAC-Address).
The Port-priority is then used to manage the re-distribution of failed links, when Stand-By
ports are configured for traffic protection.
In case of a protected traffic, if a link failure occurs, the traffic of the failed link will be
switched to the Stand-By port having a priority value just lower than the failed one.
Both Actor (local) and Partner (far) systems must switch accordingly. The messages for
link switch between connected aggregate systems are transported by means of slow-
protocol packets called LAMP (Link Aggregation Marker Protocol).
If the traffic is not protected, i.e. no stand-by ports are configured, then the traffic of the
failed link will be redistributed to all ports, if bandwidth is available. In this case frames
discarding may occur.
The redistribution of the traffic after failures impacts all the involved links, therefore the
transport is not hitless for all the conversations in operation.
The reconfiguration is triggered by the LOS on aggregate ports.
The reconfiguration is accomplished within 1 second.
In case that one or more links failed, the alarm LAG-DEG is arisen by the system.
In case that all links of the bundle fail, the alarm LAG-LOS is arisen by the system.
One “Primary” port is elected among the ports constituting the aggregate, for carrying
special traffic (network control packets with multicast/broadcast address, such as xSTP-
BPDU, IGMP, etc., and also packets with unknown address). Primary port is the one that
was first created in the group.
In case that the Primary port fails, the control protocol packets will be switched over the
port created immediately after the first one, and so on. The flooding rate of unknown
addressed packets can be limited, by the administrator.
Primary port selection is independent from the Priority values, depending only from the
port creation date.
The benefits of Link Aggregation feature are:
• Bandwidth limitation overcoming.
• Load balancing (the traffic is distributed over the constituting links).
• Reliability increasing (in case that a link of the aggregate fails, its traffic will be
automatically distributed over the other links of the aggregate).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-69
............................................................................................................................................................................................................................................................
The conditions for Link Aggregation option are the followings:

• All involved ports must work at the same rate.
• All involved ports must have the same configurations, regarding AutoNegotiation and
FlowControl.
• All aggregated links must be point-to-point (Multicast is not allowed).
• All involved interfaces must work in full-duplex modality.
• All involved ports must be Local (Remote ports are not allowed).
• Actor and Partner ports (local and far sides) must be of the same type.
An example of Link Aggregation is illustrated in Figure 1-47, (pg. 1-72); the
implementation procedure is described in “Link Aggregation, implementation example”
(p. 1-72).
............................................................................................................................................................................................................................................................
1 - 70 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 1-46 LACPDU Frame format
LACPDU frame (from IEEE Std. 802.3ad-2000)

Octets
Destination Address 5
Source Address 5
Length/Type 2
Subtype = LACP 1
Version Number 1
TLV_type = Actor Information 1
Actor_Information_Length = 20 1
Actor_System_Priority 2
Actor_System 5
Actor _Key 2
Actor_Port_Priority 2
Actor_Port 2 OCTETS
Actor_State 1 WITHIN
Reserved 3 FRAME
TRANSMITTED
TLV_type = Partner Information 1 TOP-TO-
Partner_Information_Length = 20 1 BOTTOM
Partner_System_Priority 2
Partner_System 6
Partner _Key 2
Partner_Port_Priority 2
Partner_Port 2
Partner_State 1
Reserved 3
TLV_type = Collector Information 1
Collector_Information_Length = 15 1
CollectorMaxDelay 2
Reserved 12
TLV_type = Terminator 1
Terminal_Length = 0 1
Reserved 50
FCS 4
LSB MSB
b0 b7
BITS WITHIN FRAME
TRANSMITTED
LEFT-TO-RIGHT
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-71
............................................................................................................................................................................................................................................................
Figure 1-47 Link Aggregation example

1Gbps link
using only 500
Mbps of bandwidth
(Actor System) (Partner System)

Active links
100 Mb 100 Mb
1 Gb
p1 (LagSize=5) p1
500 Mbps Aggregate Link
X 100 Mb 100 Mb X
p5 p5
Stand-By
100 Mb 100 Mb
links
p6 p6
100 Mb 100 Mb
p7
p7
OMSN & ES-A OMSN & ES-A

Each port (p1 to p7) is associated by the operator to a priority, in which lower value means higher priority.
Example of Port-Priority association:
p1: prior 6
p2: prior 5 (highest priority)
p3: prior 12
p4: prior 87
p5: prior 21
p6: prior 252 (lowestpriority)
p7: prior 251
With these values of priorities, having a LagSize=5 and PortRate=100Mbps, the ports p6 and p7 are
set, by the system, to "StandBy" state.
In case of failure on a port, the traffic will be switched to port p7, that has priority higher than p6.
In case the priorities between the two connected equiments do not match properly, then the Master
system can change the priorities of the peer system.
In this example, a 500 Mbps packets stream, is transported on an incoming segment over a 1Gbps link,
and the outgoing segment is implemented by means of the Link Aggregation feature, using 7 Ports at
100 Mbps, of which 2 are used for protection (Stand-By links).
In case of failure, the traffic of failed link is switched to the stand-by port having higher priority.
Link Aggregation, implementation example

Refer to Figure 1-47, (pg. 1-72), illustrating a Link Aggregation example with active and
stand-by links.
For details about the specific configurations here recalled, see their relative paragraphs in
this handbook.
............................................................................................................................................................................................................................................................
1 - 72 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
1. on the first node (OMSN+ES-A):

a. In Transmission context, creation of the Aggregator (select the symbol
AggGroupManagement):
Transmission Î Aggregator Management Î Create Aggregator
set the Name (e.g. #1), the ActorAdmin Key (e.g. = 1), the Actor System Priority
(e.g. = 10), the Size (e.g. = 5). Other parameters can be default values.
b. In Transmission context, activation of the created Aggregator (select the symbol
LAG#1):
Transmission Î Aggregator Î Configure Aggregator
set AdminState = enable
c. In Transmission context, transformation of one selected Local Ethernet Ports
Client Layer in “LinkAggLayer”:
Transmission Î Ethernet Port Management Î Substitute Client Layer Î
LinkAgg Layer
WARNING
The Port must have been already equipped in SDH side, before using it.
d. In Transmission context, configuration of the created Aggregate Port:
Transmission Î Ethernet Port Management Î Aggregation Port Î Configure
click on [...] key of the Actor Admin Key item: on the opened dialog select the
LAG#1 item, then set the Actor Port Priority (e.g. = 6), the Admin State = up
e. In Transmission context, creation and configuration of all the involved Aggregate
Ports, repeating the steps (c) and (d) for the seven used ports, setting to them the
ActorPortPriority parameter as indicated in Figure 1-47, (pg. 1-72).
f. In Connection context, creation of eventual Cross-Connections for the data-flows
afferent to the involved Aggregate Ports.
2. on the other involved equipment (OMSN+ES-B):
Repeat similar operations as done in the first equipment A, creating a LAG with Size =
5 and Actor System Priority (e.g. = 20: in this case the Master system will be the
Node-A), then creating 7 Aggregate Ports with Actor Port Priority parameters equal
to what set in Node-A (otherwise the master will change their priorities to match with
the peer system).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-73
CT Operator’s Guide Control Protocols management in a Transport Network
............................................................................................................................................................................................................................................................
Control Protocols management in a Transport Network

The service offered to specific Customer Layer 2 protocols (e.g. STP, RSTP, MSTP etc…),
transported through an ETS Server Layer, may appear in one of below capabilities:
• Tunnelling to the operation of the protocol between customer. Customer Layer 2
protocol frames are not filtered but conveyed with opportune encapsulation into
Service Provider Network: they are managed as Data Frames. This is the default
behaviour;
• Discarding: discarding Customer Layer 2 protocol frames;
• Peering, with a local protocol entity at the point of provider network ingress and
egress, participating and terminating the operation of the protocol;
– The peering option is automatically configured by enabling the processing of the
specific control protocol on the ETS interface (e.g. by supporting Link
Aggregation, LACP and LAMP frames are handled in the peering mode);
– When the peering option is in-force, the associated control frames will never be
processed by the ETS classifier and therefore the handling configured in the ETS
layer is meaningless (for security reason the dropping action is recommended to be
configured but no checks are performed by the NE);
• Selective Tunnelling (see “Selective Tunnelling” (p. 1-74)).
Note: Tunnelling, Discarding or Selective Tunnelling capabilities
over Layer 2 Control frames are enabled from Manager operator
both “on per flow basis” (over ETS InFlows with Ethernet as
Service Type) and “on per port basis”, and are made operational
as result of AND of both “on per flow basis” and “on per port
basis” configurations.
The ETS layer is responsible to define (via management Operator configuration):
• “on per flow basis” tunnelling, discarding and selective tunnelling capabilities over
Layer 2 Control Frames;
• “on per flow basis” tunnelling and discarding capabilities over User data frames.
Selective Tunnelling
NE, as Provider Bridge, supports (ONLY for 'CE Dual Homing' interconnection):
• BPDU Selective Tunnelling capability [irrespective of underlying either (local or
remote) Ethernet Interface or Link Aggregation Interface] including:
• Customer-BPDU Selective Tunnelling at Provider Bridge UNI Interface;
• Provider-BPDU Selective Tunnelling at Provider Bridge ETH-IWI Interface;
• VRRP PDU Selective Tunnelling capability at both Provider Bridge UNI and ETH-
IWI Interfaces.
............................................................................................................................................................................................................................................................
1 - 74 P/N 8DG15785AAAA
Control Protocols management in a Transport Network CT Operator’s Guide
............................................................................................................................................................................................................................................................
'Customer Edge Dual Homing' interconnection is a redundant interconnection (see

Figure 1-48, (pg. 1-75)) between customer and Service Provider equipment (Provider
Bridge) with both Primary and Secondary Links, where the selection of the active Primary
link is up to the customer bridging protocol (STP/RSTP/PerVLAN/MSTP).
Figure 1-48 Customer BPDU Selective Tunnelling capability
C-BPDU(/P-BPDU or VRRP) Selective Tunnelling is defined to consist of below 2

ordered operations, both performed at ETS Layer:
a. Detection (on MAC DA basis) of:
– Both Customer BPDU frames generated by x-STP customer instances (frames
for any customer bridging protocol - STP/RSTP/PerVLAN/MSTP) and P-
BPDU, both sharing the same MAC Address, as referred in Table 1-3, “L2
Control Protocols” (p. 1-38).
and
– VRRP frames generated from VRRP protocol, as referred in Table 1-3, “L2
Control Protocols” (p. 1-38).
b. Tunnelling of either BPDU or VRRP across the network.
Dual-homing
In Ethernet LANs, dual-homing is a network topology that adds reliability by allowing a
device to be connected to the network by two way of two independent connection points
(points of attachment). One access pont is the operating connection, and the other is a
standby or back-up connecton that s activated in the event of a failure of the operating
connection.
A dual-homng architecture wth two attachments into the network, offers two independent
media paths and two upsteam switch connections. Loss of the Link signal on the operating
port connected upstream indicates a fault in that path, and traffic is quickly moved to the
standby connection to accomplish a fault recovery.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-75
CT Operator’s Guide Control Protocols management in a Transport Network
............................................................................................................................................................................................................................................................
Dual-homing protection (consisting of redundant interfaces) through proper configuration

of Ethernet Service, performed at UNI Interface and based on Layer 2 Control Protocol
capabilities.
“on per flow basis” provisioned Selective Tunnelling capability, constrained ONLY to
frames whose destination address matches ”Bridge Group Address” for CE Dual Homing
interconnection.
............................................................................................................................................................................................................................................................
1 - 76 P/N 8DG15785AAAA
Redundancy features CT Operator’s Guide
............................................................................................................................................................................................................................................................
Redundancy features
Dual-homing (via selective BPDU tunnelling)
The ISA-ES1and ISA-ES4 support the Customer Edge (CE) “dual-homing” connection on
dual node topology.
The following network scenario are supported:
Figure 1-49 Dual-homing BPDU STP - dual (PE) node
A Customer Edge (CE) is connected to the network by way of two independent access
points PE (Provider Edge). One access point is the “primary” connection, and the other is
a “standby” connection, activated by STP process in the event of a failure of the primary
connection.
Specifically, “primary” and “secondary” connections are linked on two different systems
(ISA-ES1/4 boards) and from the PE (Provider Edge) Ethernet point of view this
configuration it is considered as dual node.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-77
CT Operator’s Guide Redundancy features
............................................................................................................................................................................................................................................................
Figure 1-50 Dual-homing BPDU (network) STP tunnel
Figure 1-51 Dual-homing BPDU (local) STP tunnel
Important! In ISA-ES1/4, the BPDU Tunnelling between two UNI

in the same ISA-ES1/4 board (PE single node dual attachment is
admitted) is not supported.
............................................................................................................................................................................................................................................................
1 - 78 P/N 8DG15785AAAA
Network protections CT Operator’s Guide
............................................................................................................................................................................................................................................................
Network protections
In the following are described the ISA-ES1 and ISA-ES4 network protection.
Ethernet Ring Protection (ERP)

The ISA-ES1 and ISA-ES4 (from Rel. 3.0 onward and ONLY configured as either Virtual
or either Provider Bridge), supports ERP mechanism as Ethernet Layer Protection
Protocol, in accordance with ITU-T G.8032 / Y.1344 v.2.
The ISA-ES1 and ISA-ES4 support with a 50 ms of timing switchover for an ERP
protection instance (this period includes FDB Flush time) for a ring well planned of the
whole bandwidth.
ERP protocol, configured “on per ERP instance basis”, will be based on the following
mutually exclusive assignments:
• Per Port ;
• Per VLAN (Group) , i.e. on per VLAN basis.
ISA-ES4 supports also multiple physical rings topology.
ISA-ES1 and ISA-ES4 don’t support sub-ring physical rings topology, and provisioning of
Interconnection Node.
Each ERP Ring defines an ERP Topology instance, from which an ERP instance are
configured.
ISA-ES1 and ISA-ES4 accepts remote Ethernet Port, to be assigned as Ring Ports to a
ERP Topology instance.
ERP Ring ports have to be excluded from flat (per-port) RSTP/MSTP bridging protocols
according to below behavior:
• per-port bridging protocols are allowed ONLY over those ports outside ERP
Topology;
• “Per VLAN basis” ERP and “per VLAN basis” proprietary RSTP are admitted ONLY
over different VLANs (different VLANs are allowed over the same bridge port): the
same VLAN is denied to be concurrently managed (over the same ring and over the
same port) via both ERP instance and per VLAN proprietary RSTP instance.
ERP terms definition

For better understanding the ERP operation, refer to “Terms and Definitions” (p. GL-17)
where is given a description of the ERP entities, as per ITU-T G.8032 / Y.1344 v.2 and
particularl for:
• Ethernet Ring
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-79
CT Operator’s Guide Network protections
............................................................................................................................................................................................................................................................
• Ethernet Ring Link

• Ethernet Ring Node
• Ring Protection Link (RPL)
• RPL Owner Node
• RPL Node
• Ring MEL
ERP operation
Each ring node is connected to adjacent nodes participating in the same ring, using two
independent links. A ring link is bounded by two adjacent nodes and a port for a ring link
is called a ring port. The minimum number of nodes on a ring is two.
The ERP switching architecture is mainly based on:
• loop avoidance
• learning, forwarding, and address table mechanisms defined in the Ethernet flow
forwarding function (ETH_FF).
The loop avoidance in the ring is achieved by guaranteeing that, at any time, traffic may
flow on all but one of the ring links. This particular link is called the Ring Protection Link
(RPL), and under normal conditions this link is blocked, i.e., not used for traffic.
One designated node, the RPL Owner, is responsible to block traffic over the RPL. Under
a ring failure condition, the RPL Owner is responsible to unblock the RPL, allowing the
RPL to be used for traffic. The other node adjacent to the RPL may also participate in
blocking or unblocking its end of the RPL.
The event of a ring failure results in protection switching of the traffic, under control of
ETH_FF on all ring nodes. An APS protocol is used to coordinate the protection actions
over the ring, triggering a flush action on MAC learned addresses. The R-APS protocol
uses specific channel to carry ETH OAM R-APS PDU packets, with a dedicated VLAN
ID in ETH OAM frame. The R-APS channel is blocked for those ports also in blocked
state for data traffic.
The two next figures show the reference model for ERP ring in “normal” and “failure”
state.
............................................................................................................................................................................................................................................................
1 - 80 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 1-52 ERP reference scheme in normal/idle state
Figure 1-53 ERP reference scheme in failure state
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-81
............................................................................................................................................................................................................................................................
ERP configuration
The ISA-ES1 and ISA-ES4 can be configured with ERP protocol (according to ITU-T
G.8032 v. 2) on ERP instance basis over a physical ring topology, where ERP instance
inherits the Ring Port(s) from the “ERP Topology instance” with which it is associated.
The user select the option to bind an Ethernet OAM Down MEP to a Ring Port, supporting
Continuity check time period (up to 3.3.msec), so supporting both:
• ERP Ring port Link monitoring
– Continuity Check packets are terminated on each Ring Port, supporting the
reporting of Ethernet OAM CCM defects.
• ERP switch trigger.
– The ERP protection mechanism can be triggered to switch on defects (refer to
“Protocol behavior control” (p. 1-82)) that are detected by a MEP that is assigned
to a Ring Port. In this case the defects detected by the MEP processes are “added”
to the defects that are directly detected on the physical port level. To enable this
additional monitoring, one MEP can be selected on each Ring Port to supply the
additional defects.
The selected Down MEP may have any MEG Level and any (Primary) VID, including
Ring APS VID and using tagged or untagged CFM PDUs.
The MEP can either be of the type that monitors all traffic on the port, i.e. the one using
CFM PDUs that are untagged or of the type that monitors selectively the path that is
associated to a (group of) VLAN(s) i.e. the one using VLAN-tagged CFM PDUs.
In all cases it may be a potential alternative to use a MEP that monitors the same VLAN
that carries the R-APS PDUs. Note that in this case the [7]MEL (Ethernet OAM
Maintenance Level) to be assigned to the MEP needs to be lower than the MEL assigned
to the ERP instance, otherwise the R-APS messages (which are a special kind of CFM
PDUs) will be blocked by the MEP.
Protocol behavior control

The user shall have the option to read or provision:
• Wait-to-Restore Time (WTR) of an ERP instance can be provisioned in the set (0, 1,
2, ..... 12 minutes, infinite), with default value at 5 minutes. A value “infinite” stands
for “non revertive“ switching behaviour (not supported).
The switching behaviour of an ERP instance, can be provisioned (Revertive, Non
Revertive). Default value is Revertive.
• Guard Timer of an ERP instance can be provisioned in the range (10 - 2000 msec)
with 10 msec steps. Default value is 500 msec.
• Hold-off Timer of an ERP instance can be provisioned in the range (0 - 10 sec), with
0.1 sec. steps. Default value is 0 sec.
............................................................................................................................................................................................................................................................
1 - 82 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• contribution of Signal Degrade defects (dDEG) to the switching criteria of an ERP

instance.
• contribution of Ethernet OAM CCM defects to the switching criteria of an ERP
instance. CCM defects are all either enabled or disabled.
The user can deny to provision:
• the switching behavior of an ERP instance. Fixed value is “Revertive”;
• any operator administrative commands (Forced Switch, Manual Switch, Clear) during
maintenance or upgrade operations in the network. In order to force or clear ERP
switching conditions.
ERP basic instance configuration

The selection of the VLAN identifier for the R-APS protocol channel must be done
carefully, where VLAN-ID in the R-APS PDU frames is S-VLAN for that ERP instance,
accordingly to Provider Bridge configuration.
To avoid messages to “spill-over” from one ERP instance to another, each ERP instance
that is active in a ISA-ES1 and ISA-ES4 is requested to use a different Ring APS VID,
provided this VID is not otherwise used, including any VID that is designated to carry
management information.
The ISA-ES1 and ISA-ES4 shall automatically add the Ring Ports that are assigned to the
ERP instance in the “port member set” of the provisioned Ring APS VID, irrespective of
the order in which Ring APS VID and Ring Ports are provisioned. uses the VLAN
filtering mechanism to control the blocking / unblocking of Ring Ports.
An ERP instance can operate in two different ways:
• “Per Port”: the ERP instance will block all untagged traffic intending to ingress or
egress a blocked port, when the attached link is selected by the protocol to be blocked.
All VLANs that have registered on this port are (temporarily) removed from their
“Active Port Member Set” until the port is unblocked again. Note that this does not
prevent the local node to receive or transmit R-APS PDUs over a blocked port.
• “Per VLAN (group)”: the ERP instance will only block the traffic of the VLANs in the
group, including the Ring APS VID, by temporarily removing this port from their
“Active Port Member Set” (untagged traffic shall not be affected by an ERP block) .
Note that this does not prevent the local node to receive or transmit R-APS PDUs over
a blocked port
In case simultaneously an ERP per Port and one or more ERP per VLAN instances are
configured on a certain Major Ring or Sub-Ring, the ERP per Port instance protects only
those VLANs that are not protected by any of the ERP per VLAN instances.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-83
............................................................................................................................................................................................................................................................
The assignment of a VLAN to an ERP instance when operating in “Per VLAN” mode,
shall always be accepted, on condition that the VLAN is not already assigned to another
“Per VLAN” instance. It shall be allowed to assign a VLAN to a “Per VLAN” instance if
it was up to that moment protected by a “Per Port” instance.
The removal of a VLAN from an ERP instance when operating in “Per VLAN” mode is
always accepted.
The ISA-ES1 and ISA-ES4 shall unblock any Ring Ports, which may have been blocked
by the ERP instance that protected the VLAN at the moment of the removal. In case a “Per
Port” instance is active on the same Ring Port, the traffic that belongs to the removed
VLAN shall be protected by this ERP instance after removal from the “Per VLAN”
instance. The provisioned port member set of the VLAN is not changed during this
operation.
The ISA-ES1 and ISA-ES4 is able to support up to 20 nodes per ring with 1 sec. of timing
switchover for an ERP protection instance. ERP switchover s applicable for any single
Signal Fail event (however in this case the time to detect the failure and the Hold-Off Time
is not included in the switch completion time).
Operator Administrative commands

The Administrative commands are external commands allowing the operator to control the
ERP protocol. This is useful during maintenance or upgrade operations in the network.
The following controls are provided:
• Forced Switch. Purpose of the forced switch is to force a certain port to be blocked,
irrespective of the failed state of that port. Multiple simultaneous forced switches are
allowed per ERP ring and per ERP node. The user can issue a “Forced Switch” (FS)
command to a Ring Port of an active ERP instance. Such a command overrules and
clear any active “Manual Switch” (MS) commands in the system at that time. The
system allows FS commands to be active on both Ring Ports simultaneously
• Manual Switch. Purpose of the manual switch is to force a certain port to be blocked,
provided no ports in the ring are in failed or forced switch state. Only a single Manual
Switch command is allowed per ERP ring. As soon as a signal fail or forced switch
occurs in the ring, the Manual Switch is automatically cleared. The user can issue a
“Manual Switch” (MS) command to a Ring Port of an active ERP instance. Such a
command is rejected in case a Forced Switch or Signal Fail condition is active
anywhere in the ERP ring. The system allows only a single Manual Switch command
to be applied at any particular time
• Clear. It clears any active Manual or Forced switch command on a certain node. In
case multiple Forced Switch commands are active on different ERP Ring Nodes, a
Clear command must be issued on each such Ring Node to restore the normal
situation. In addition, the Clear command stops a running WTR Timer in the RPL
............................................................................................................................................................................................................................................................
1 - 84 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Owner to abort the WTR period. The user can issue a “Clear” (CLR) command to an
active ERP instance. Such a command clears all locally issued and still active FS and
MS commands. In case the “Clear” command is issued on the RPL Owner and there
are no MS or FS commands locally active, the command stops the WtR Timer and
generates the “WTRxp” (WtR Timer Expired) event.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-85
CT Operator’s Guide Ethernet OAM
............................................................................................................................................................................................................................................................
Ethernet OAM
In Provider Bridge mode configuration only, Ethernet OAM (OperationAdministration
and Maintenance) refes to the tools to monitor and troubleshoot Ethernet network and
quickly detect failures.
Ethernet OAM is broad topics where different standards have been developed known as
Service OAM (Connectivity Fault Management), Link OAM (OAM) and other different
standards.
Connectivity Fault Management

CFM provides “service” fault management. This means that it defines proactive and
diagnostic fault localization procedures for point to point and multipoint EVCs that spans
in one or more links, as shown in Figure 1-54. So the CFM enables the service provider to
know if an EVC is affected by fault and provides the tools to rapidely isolate the failure.
Figure 1-54 Connectivity Fault Management
............................................................................................................................................................................................................................................................
1 - 86 P/N 8DG15785AAAA
Ethernet OAM CT Operator’s Guide
............................................................................................................................................................................................................................................................
ME - Maintenance Entity
Maintenance Entity (ME) is in general, an entity of the Ethernet layer network that
requires maintenance; specifically, it represents a point-to point relationship between two
MEP (Maintenance End Point) at a particular ME level.
ME level represents the information to be used to distinguish between OAM signals
belonging to different nested MEs, at any point in a network. Eight ME levels are available
to accomodate different network deployment scenario.
a. Customers are assigned 3 ME levels: 0, 1, and 2.
b. Providers are assigned 2 ME levels: 3, and 4.
c. Operators are assigned 3 ME levels: 5, 6, and 7.
MEG - Maintenance Entity Group

Maintenance Entity Group (MEG) includes different MEs (Maintenance Entities).
One or more ME Groups, all at the same ME level, may be grouped into a “Maintenance
Domain”.
MEP - MEG End Point

MEG End Point (MEP) is an expanded ETH flow point that is capable to initiate and
terminate proactive OAM signals.
MIP - MEG Intermediate Point

MEG Intermediate Point (MIP) is an expanded ETH flow point that is capable to react to
diagnostic and do not to initiate diagnostic OAM signals.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-87
CT Operator’s Guide Management software
............................................................................................................................................................................................................................................................
Management software
The transportation of Ethernet frames is achieved by integrating the necessary hardware
and software functions into the SDH Network Elements.
The software related to the Ethernet Switch (ES) management provides a human interface
permitting the Operator to manage the relevant functions. The human interface can be
integrated on a Personal Computer representing the ES Craft Terminal (ES-CT), or on a
Work Station representing the ES Operations System (ES-OS).
ES-CT is installed on a Common Platform CT, and ES-OS is installed on a Common
Platform OS.
The Alcatel-Lucent-NE's management is based on a software platform, common to all the
transport equipment, resulting on the NES operator interface (Network Elements
Synthesis); the description of the NES interface and some generic procedures, common to
all the Alcatel-Lucent-NE's, are reported on 1320CT Operator Handbook, listed in
Table 1, (pg. 1-xxviii); the hardware configuration, features and functionalities of Alcatel-
Lucent Network Elements supporting ES services are described in the relevant Technical
Handbooks, listed in Table 1, (pg. 1-xxviii); the SDH traffic management by means of the
SDH-CT is described in the relevant OMSN-CT Operator Handbooks, listed in
Table 1, (pg. 1-xxviii).
The ES management by means of the OS is described in the relevant TMN Operations
System Operator's Handbooks.
The aim of this handbook is to illustrate the operational procedures to access and to handle
the Ethernet traffic by means of the ES-Craft Terminal (ES-CT).
The ES-CT permits to manage the functions and the parameters relevant to the ES service,
such as:
• signals rate, bandwidth, interface type, traffic contract, cross-connections, manual and
automatic switching, alarms, performance monitorings, etc.
The ES traffic and network management signalling inside the existing SDH network is
accomplished by means of a dedicated communication protocol, as indicated in “Ethernet
over SDH Management” (p. 1-90).
The provided CT software needs a WINDOWS computer operating environment. The
operator's interface is organized in a WINDOWS system. A skill on these tools is required
on behalf of the user.
The CT Common Platform (i.e. 1320CT) software package has to be already installed,
before installing the ES-CT.
The software product is distributed by Alcatel-Lucent in a CD-ROM.
This CD-ROM contains:
............................................................................................................................................................................................................................................................
1 - 88 P/N 8DG15785AAAA
Management software CT Operator’s Guide
............................................................................................................................................................................................................................................................
• Software products for management by means of the craft terminal

• Software product for updating the NE (download)
The software products used for management permits the dialogue between the Craft
terminal and the NE, to realize the functions of the applications as configuration, alarms
management, etc.
The software product used for updating the NE must be installed on the PC and then
downloaded on the NE, thus following product evolution. The download of the NE is done
in the SDH-CT environment, therefore the relevant download operations are reported in
the specific OMSN-Operator Handbook
The list with the part numbers of the software product relevant to ES service is reported in
“Software product and licenses description” (p. 2-2).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-89
............................................................................................................................................................................................................................................................
Ethernet over SDH Management

The management of SDH equipment is organized as required by the 7-layers ISO/OSI
protocol stack, while the Ethernet, MPLS and ATM equipment (ISA) are usually managed
by means of SNMP (Simple Network Management Protocol), that is an application of the
5-layers TCP/IP reference model.
By carrying the Ethernet traffic over the SDH network structures there is the need to
manage together and contemporarily SDH and Ethernet equipment; this function is
accomplished by means of the encapsulation of SNMP messages inside the OSI layers (IP
over OSI tunneling). In this way the Ethernet management information is transported
over the existing SDH networks.
The various protocols relations are illustrated in Figure 1-55, (pg. 1-90).
An example of Ethernet/MPLS/SDH network management is shown in Figure 1-56, (pg.
1-91).
In this example, the OS enters the network management messaging over an Ethernet link
(IEEE-802.3 protocol) of a Gateway NE (GNE); here the messages are transported over
the optical Qecc links by means of the LAPD protocol; at the remote managed nodes, the
messages are acknowledged as belonging to:
OSI reference model, for SDH management
TCP/IP (SNMP) reference model, for Ethernet, ATM and MPLS management.
Figure 1-55 Protocol stack for ATM/MPLS/Ethernet over SDH management
Application Lay 7
Presentation Lay 6
SNMP Session Lay 5

Transport
UDP Lay 4
(TP4)
IP Network
(CLNP) Lay 3
4 3
2 1
802.3 LAPD Lay 2
Q3 Qecc/F Lay 1
1. OSI stack for SDH management (F/Qecc Interface)

2. IP over CLNP tunneling for iSA management (F/Qecc Interface)
3. OSI stack for SDH management (QB3/Qecc Interface)
4. IP over CLNP tunneling for iSA management (GNE entry from OS, IEEE-802.3)
............................................................................................................................................................................................................................................................
1 - 90 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 1-56 Example of management of an SDH network with SDH and ES traffic
OS SONET/SDH (OSI) &
SONET/SDH-OS ES (SNMP)
&
TMN
ES-OS
Q3
802.3
QECC LAPD
QECC
F Gateway NE
CT
OSI (GNE)
LAPD SONET/SDH
SONET/SDH-CT
SNMP + ES NE F
& SONET/SDH
LAPD OSI
ES-CT NE
QECC QECC
SONET/SDH
CT LAPD OSI SONET/SDH + ES NE OSI
F
NE LAPD
SONET/SDH-CT
SNMP
QECC
LAPD
QECC
F
OSI SNMP
SONET/SDH + ES NE
Protocol stack at different interfaces:

Q3 F QECC
SONET/SDH SONET/SDH SONET/SDH

Data (OSI) Data (OSI) Data (OSI)
(SNMP) Appl. (SNMP) Appl. (SNMP) Appl.
SNMP Pres. SNMP Pres. SNMP Pres.
UDP Sess. UDP Sess. UDP Sess.
TP4 TP4 TP4
IP CLNP IP CLNP IP CLNP
MAC MAC MAC
Eth-Q3 Eth-Q3 Eth-Q3
Tunnel Tunnel Tunnel
Note:
– The tunnel IP over CLNP is initiated inside the Manager (CT or OS) and terminated at the
destination NE, in order to carry SNMP management messages into the SDH network.
– The SNMP messages are tunneled in the NE's where the message is not to be opened
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-91
............................................................................................................................................................................................................................................................
Important! In order to transfer the management information, the

involved entities need an OSI address (for the ISO/OSI information
messages) and an IP address (for the SNMP information
messages). In particular:
– the CT (personal computer, local manager or craft terminal)
needs to be associated to an OSI address and to an IP address.
The OSI address is assigned by means of the Alcatel-Lucent
Lower Layers Manager (ALL) application; the IP address
assignment is done in the WINDOWS environment by means of
the Network application of the Control Panel. Refer to the
1320CT Basic Handbook listed in Table 1, (pg. 1-xxviii) for
these operations.
– the EC (Equipment Controller board of the NE) needs to be
associated to an OSI address and to an IP address. The OSI
address and IP address are assigned by means of the SDH-CT
application (Configuration Î Comm/Routing:... options).
Refer to the OMSN Operator's Handbook listed in Table 1, (pg.
1-xxviii) for these operations.
– the ISA board needs to be associated to an IP address. The IP
address is assigned by means of the SDH-CT application
(Configuration Î Comm/Routing:... options). Refer to the
OMSN Operator's Handbook listed in Table 1, (pg. 1-xxviii) for
these operations.
An illustrative example is reported in Figure 1-57, (pg. 1-93).
............................................................................................................................................................................................................................................................
1 - 92 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 1-57 OSI and IP addressing example

OSI Address
+ (Operations System)
OS
IP Address
IP Over OSI Tunnel Managed NE (adjacent)
NE + ISA ES
(Local manager)
Q3 Ethernet Config OSI Address
OSI Address CT
+ IP Address
F EC
IP Address IP over OSI
IP Router/CLNP Tunnel
SDH port
SDH
SONET
LAPD = Network
LAPD Config
Qecc SDH port
SDH
SONET
LAPD = User
LAPD
DATA port DATA#1

VLAN
for In Fiber In Band

management DATA#n
SNMP
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 1-93
............................................................................................................................................................................................................................................................
ES-CT main management menus

The main menus presented by the ES Craft Terminal are the following:
1. Supervision
It permits to manage the access to the ES functions from the various levels of
management.
2. Configuration
It permits to manage the configuration of the following functions:
– Alarms Severities Assignment Profiles (ASAP)
– Threshold data table setting for Performance monitoring
– Traffic contract descriptor setting.
3. Diagnosis
It permits to open the Alarms Surveillance (AS) application.
4. MIB Management
It permits to save/load the MIB (data base) of the ES functionality configurations.
5. Transmission
It permits to manage the functions related to the Transmission domain:
– creation, configuration, modification and deletion of the ES resources (ES-Node,
Ethernet-Ports, in/outFlows, Classifiers, etc.).
6. Connection
It permits to manage the functions related to the Connection domain:
– creation, configuration, modification and deletion of the links, cross-connections
on ISA-ES.
7. Performance Monitoring
It permits to manage the functions related to the Performance domain:
– configuration, modification and deletion of data collections related to the
Performance Monitoring (PM) on the ES resources.
............................................................................................................................................................................................................................................................
1 - 94 P/N 8DG15785AAAA
2 Software Product and
Licence
Overview
This chapter describes the software packages list, the software licenses list, and their
relevant part-numbers.
• “Software product and licenses description” (p. 2-2)
• “Software products, licenses and part numbers” (p. 2-3)
............................................................................................................................................................................................................................................................
ISA ES1/4 Release 3.0 Software Product and Licence
CT Operator’s Guide Software product and licenses description
............................................................................................................................................................................................................................................................
Software product and licenses description

The software products are distributed by Alcatel-Lucent in a CD-ROM.
This CD-ROM contains:
• Software packages for ES management by means of the craft terminal
• Software packages to be downloaded into the NE (by means of the download
function).
The software package used for management permits the dialogue between the ES-CT and
the NE, to configure all the ES functions. The overall generic structure of the Alcatel-
Lucent Management Software is illustrated in Figure 2-1 below.
The software package used for updating the NE must be installed on the PC and then
downloaded on the NE, thus following product evolution. The download on the NE is
done in the SDH-CT environment, therefore the relevant download operations are reported
in the specific-NE Operator Handbook.
Alcatel-Lucent, typically, offers several software licenses for the software product;
they are referred both to the Network Element software features and to the Craft Terminal
software features.
Figure 2-1 Management Software, generic structure
AddOn Applications SDH-CT ES-CT SNMP ...
Common Platform CT-K JRE
Communication ALL
Lower Layer
JRE: Java Running Environment

CT-K: Craft Terminal Kernel
ALL: Alcatel-Lucent Lower Layer
............................................................................................................................................................................................................................................................
Software Product and Licence ISA ES1/4 Release 3.0
Software products, licenses and part numbers CT Operator’s Guide
............................................................................................................................................................................................................................................................
Software products, licenses and part numbers

The software product is identified by a denomination and one or more part numbers, as
listed on the following table.
Table 2-1 Software product part number
Denomination Factory Part Number Note

SW package ES1B R.3.0 (CD-ROM) 3AL98419AA**
for 1660SM, 1650SMC and 1662
SW package ES4B R.3.0 (CD-ROM) 3AL98420AA**
SW package ES1N R.3.0 (CD-ROM) 3AL97395AA** for 1642EM, 1642EMC
SW package ES4N R.3.0 (CD-ROM) 3AL97399AA** for 1642EM
In order to use the above software product, one or more software licenses may be
requested.
Every software license is identified by a denomination and a part number, listed in the
following table.
Table 2-2 Software licenses part numbers
Name Factory Part Number Note

SW Licence OMNSN METRO Vers. “A” ETH LP 8DG15540AB** a
SW Licence ENH ETH (ES1 R3.0) :
8DG15540BA** b
ERPC2, 9KJ, BC/MCSCTRL, MACACL, ETHPHYLOOP
SW Licence ENH ETH (ES4 R3.0) :
8DG15540BB** c
ERPV2, 9KJ, BC/MCSCTRL, MACACL, ETHPHYLOOP
Note:
a. To be used for OMSN and ES funcionalities. The Licence Points Access are the
following:
– #2 for each ISA ES1 in the network
– #4 for each ISA ES4 in the network
b. To be used for each ISA ES1 housed in 1660SM, 1650SMC, 1662, 1642EM and
1642EMC.
c. To be used for each ISA ES4 housed in 1660SM, 1650SMC, 1662 and1642EM.
Note: This product includes software developed by the Apache
Software Foundation (http://www.apache.org).
............................................................................................................................................................................................................................................................
ISA ES1/4 Release 3.0 Software Product and Licence
CT Operator’s Guide Software products, licenses and part numbers
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Overview
This procedure describes how to install the software required by the ES-Craft Terminal
and how to de-install it, if necessary.
WARNING
The figures included in this chapter are only examples, in order to explain the
installation procedures. In the real installation, some version/edition/release
numbers inside the windows may be different, but the procedure is the same.
• “Software Version” (p. 3-2)
• “Start-up of the Personal Computer” (p. 3-3)
• “Host Computer Configuration” (p. 3-4)
• “Summary procedure for ES software installation” (p. 3-6)
• “ES-CT Installation procedure” (p. 3-8)
• “NE-ES package installation procedure” (p. 3-28)
• “Software Uninstallation procedure” (p. 3-33)
• “NE-ES software downloading” (p. 3-36)
• “Start-Up of the ES Craft Terminal management software” (p. 3-40)
............................................................................................................................................................................................................................................................
ISA ES1/4 Release 3.0 ES Software Installation
CT Operator’s Guide Software Version
............................................................................................................................................................................................................................................................
Software Version
The edition of this Handbook refers to the features of ISA-ES product developed in
• MPLS ES1/ES4 FASTETH 3.0.xx (CT_ES1-sw)
that are the released versions for ISA-ES1 and ISA-ES4 Rel. 3.0 (see next figure) and
where “x” is the file maintenance descriptor (for updating version only).
WARNING
In some subsequent figures of this document, software version numbers may be
different, since they can have been derived by previous releases of this
handbook, but they are to be considered as mere illustrative examples.
Figure 3-1 Craft Terminal components versions
............................................................................................................................................................................................................................................................
ES Software Installation ISA ES1/4 Release 3.0
Start-up of the Personal Computer CT Operator’s Guide
............................................................................................................................................................................................................................................................
Start-up of the Personal Computer

The PC is started by means of the relevant switch.
WARNING
Administrator privileges for WINDOWS environment are needed, to install and
de-install the ES-CT software package.
WARNING
The Alcatel-Lucent Craft Terminal Common Platform (i.e. 1320CT) software
package already installed is needed, before starting the installation of the ES-
CT software package.
At this point the Windows application starts automatically and the operator will see the
Windows desktop.
............................................................................................................................................................................................................................................................
CT Operator’s Guide Host Computer Configuration
............................................................................................................................................................................................................................................................
Host Computer Configuration

The configuration of the Personal Computer hosting the ES Craft Terminal is the same as
the configuration for Alcatel-Lucent Craft Terminal Common Platform (i.e. 1320CT). See
the 1320CT Basic Handbook (listed in Table 1, (pg. 1-xxviii)) for details about this issue.
WARNING
The IP address assignment to the host computer (PC) is necessary, before using
the ES-CT; the procedure to assign this IP address is reported into the 1320CT-
Basic Handbook (listed in Table 1, (pg. 1-xxviii)); the steps to verify that the IP
address to the PC has been assigned are recalled in the following paragraph.
WARNING
If, for any reason, the IP address is changed, the following customization
WINDOWS command is necessary: Start Î Programs Î ALCATEL Î
SNMPCT-K-ADDON Î SNMP-AddOn Customization.
WARNING
If a previous ES-CT version is installed, then the following system Backup from
WINDOWS environment is suggested: Start Î Programs Î ALCATEL Î
1320CT Backup&RestoreTools Î SystemBackup (see 1320CT Operator
Handbook listed in Table 1, (pg. 1-xxviii) for details).
............................................................................................................................................................................................................................................................
Host Computer Configuration CT Operator’s Guide
............................................................................................................................................................................................................................................................
Verification of IP address assignment for the host computer

Important! The following procedure is here described only for
WINDOWS-NT environment, but for WINDOWS-XP or others it is
similar; please refer to 1320CT Basic Handbook listed in
Table 1, (pg. 1-xxviii) for details.
1. Verify that the LLman Lower Layers adapter is installed:
a. In WINDOWS environment: Start Î Setting Î ControlPanel;
b. in the Control Panel view, start the Network application
c. in the Network view, open the Adapters folder
d. in the Adapters folder, verify that the item LLman NIC LowerLayerAdapter is
listed
2. Verify that the IP address to the PC is assigned:
a. In WINDOWS environment: Start Î Setting Î ControlPanel;
b. in the Control Panel view, start the Network application
c. in the Network view, open the Protocols folder
d. in the Protocols folder, select the item TCP/IP Protocol and then click on the key
Properties
e. in the opened Properties window, in the Adapters pull-down menu, select the
item LLman NIC LowerLayerAdapter
f. in the IP address fields, verify if the IP-address and related mask are already
assigned
If any of the above features is not verified, refer to 1320CT Basic Handbook (listed in
Table 1, (pg. 1-xxviii)) for the Alcatel-LucentLowerLayer manager installation and for the
IP address assignment.
............................................................................................................................................................................................................................................................
CT Operator’s Guide Summary procedure for ES software installation
............................................................................................................................................................................................................................................................
Summary procedure for ES software installation

WARNING
Before starting the SW installation, verify that the USM-CT SW (on PC) and the
NE-SW (on the equipment) are aligned, else provide to align them by installing,
on the PC, the appropriate CT-SW that can handle that NE release (see 1320CT
Basic Handbook listed in Table 1, (pg. 1-xxviii) for details)..
The following steps have to be done, mainly, for ES software installation:
1. Installation of 1320CT and SDH-CT packages, see 1320CT Basic Handbook listed in
Table 1, (pg. 1-xxviii) (see also note below).
2. Installation of SDH-NE software package into the PC, see 1320CT Basic Handbook
listed in Table 1, (pg. 1-xxviii).
3. Download of SDH-NE software into the NE, see the specific OMSN Operator's
Handbook listed in Table 1, (pg. 1-xxviii).
4. Installation of ES-CT, see “ES-CT Installation procedure” (p. 3-8).
5. Installation of ES-NE software package into the PC, see “NE-ES package installation
procedure” (p. 3-28).
6. Download of ES-NE software into the NE, see “NE-ES software downloading”
(p. 3-36).
7. Activation of the ES-NE software into the NE, see “Start-Up of the ES Craft Terminal
management software” (p. 3-40).
WARNING
In case of OMSN migration from a release to another one (for instance from
Rel. 4.3 to 4.4), the presence of the previous release of SDH-USM software
package (see 1320CT Operator Handbook) is necessary, in order to download
the new software release, otherwise the equipment-SW and the CT-SW are not
aligned and the equipment cannot be supervised anymore. Hence the operator
is recommended to keep the previous release of the SDH-USM, until the actual
SW-package will be downloaded into the equipment.
WARNING
In case of OMSN migration to a new (never used before) release containing a
new “ADD-ON" (Service Specific packet such as the ES-swp), from an old
release containing another service packet (for instance an ATM-swp), the
download of the software into the NE must be done in two steps:
• first step downloading the new SDH packet associated with the known
service packets (e.g.: enhanced OMSN with ATM, see also “NE-ES package
installation procedure” (p. 3-28))
• second step downloading the new SDH packet associated with the new
service packet (e.g.: enhanced OMSN with ES).
............................................................................................................................................................................................................................................................
Summary procedure for ES software installation CT Operator’s Guide
............................................................................................................................................................................................................................................................
WARNING
In case of OMSN UPGRADE from an OLD release to a NEW release that is
not consecutive, the download of the software into the NE must be done in two
steps:
• first step: the release of the software into the NE and the release of the CT
must be aligned (i.e., if the CT is in current release, it must be downgraded,
thus installing the CT aligned to the NE software resident into the NE); in
these conditions the new SW_package can be downloaded and activated,
using the old CT.
• second step: instal the new CT release and access the NE. If the Data Service
board (ES) was not present in the old release, then download the new SDH
packet associated with the new service packet (e.g.: enhanced OMSN with
ES).
CAUTION
All installations must be done on the same disk partition of the host Personal
Computer.
............................................................................................................................................................................................................................................................
CT Operator’s Guide ES-CT Installation procedure
............................................................................................................................................................................................................................................................
ES-CT Installation procedure

The software of the ES Craft Terminal is contained in a Compact Disk (CD-ROM),
supplied by Alcatel-Lucent.
The part number of this product is reported in “Software products, licenses and part
numbers” (p. 2-3).
As an alternative it can be received from an Internet distribution Alcatel-Lucent Service
site, managed by Alcatel-Lucent; in this latter case the installation can be slightly different
from this following procedure.
WARNING
Every Craft Terminal application (NES, ES-CT, EML-USM, etc.) must be
closed, before starting the installation.
CAUTION
In order to guarantee the correct operations, all the Craft Terminal (SDH and
ES) software packages must be installed in the same PC disk partition.
Important! This product includes software developed by the
Apache Software Foundation (http://www.apache.org)
The sequence of the installation procedure will be different, according to software and
selection conditions:
• first installation, without ES-CT software previously installed in the PC
• installation with ES-CT software of previous or same version already installed in the
PC.
This differences will be explained hereinafter.
To install the ES-CT software execute the following operations:
1. Insert the CD-ROM disk into the CD-ROM drive (example E:).
2. The installation program automatically starts and after an intermediate screen shown
in Figure 3-2, (pg. 3-9), the window of Figure 3-3, (pg. 3-9) will appear.
The Back button permits to go back to the previous window; the Cancel button permits to
abort the present window: these functions are the same in all the screens where they are
present.
............................................................................................................................................................................................................................................................
ES-CT Installation procedure CT Operator’s Guide
............................................................................................................................................................................................................................................................
Figure 3-2 Initial presentation intermediate screen
Figure 3-3 Selecting installation procedure (1st step)
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
3. Refer to Figure 3-3, (pg. 3-9). The above view permits to select the following options:
– Installation of the ES-CT software product: CT Products installation.
– The CT Products de-installation option is not operative.
The uninstallation of the application has to be done in the Windows environment,
see instructions at “Software Uninstallation procedure” (p. 3-33).
– Quit, to exit the installation procedure.
In this phase select the first option (CT Products installation).
Then click on Next button, to access the next dialog box shown in Figure 3-4, (pg.
3-10).
Figure 3-4 Craft Terminal master setup, list of detected Components on the media
4. Refer to Figure 3-5, (pg. 3-11). The screen lists the installed Software Components
detected.
Click Yes to have the next dialog box:
............................................................................................................................................................................................................................................................
3 - 10 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 3-5 Selecting Craft Terminal components (1st step)
5. Refer to Figure 3-5, (pg. 3-11). This view permits to select the software components to
be installed. They are:
– JRE ... (Java Runtime Environment, to support java software procedures)
– Alcatel-Lower-Layer V... (to manage the interfaces communication between the
computer and the Network Element)
– COMMON ADM FASTETH ... (supporting ES management functionality)
– CT-K rel... (to support the 1320CT Craft Terminal Common Platform)
– SNMPCT-K-ADD-ON v... (Add-on software to manage the SNMP
communication)
Important! The procedures to install the components JRE,
Alcatel-Lower-Layer and CT-K are the same as described in the
1320CT Basic Handbook (listed in Table 1, (pg. 1-xxviii)), therefore
they are not described in this manual; please refer to the 1320CT
Basic Handbook (listed in Table 1, (pg. 1-xxviii)).
Important! As regards the CT-K component, the most recent
version is recommended to be installed, after comparing the
installed version and the one contained in current package.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 3-11
............................................................................................................................................................................................................................................................
Important! In case of CT-K upgrading, the system Backup from

WINDOWS environment is recommended: Start Î Programs Î
ALCATEL Î 1320CT Backup & RestoreTools Î System Backup
(see 1320CT Operator Handbook listed in Table 1, (pg. 1-xxviii) for
details).
Important! The installation can be done by selecting more than
one or all the components together, in this window, or selecting only
one of them at a time; in general, the installation of one component
at a time is advisable.
Important! The procedure can be slightly different, if all the
components are selected, since some windows will be skipped, in
this latter case.
The overall generic structure of the Alcatel-Lucent Management Software is
illustrated in Figure 2-1, (pg. 2-2).
Click on Clear All button, then click on the square correspondent to
COMMON_FASTETH component to mark it with a check, and then click on Next to
have the following window:
Figure 3-6 Software License agreement
............................................................................................................................................................................................................................................................
3 - 12 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
6. Refer to Figure 3-6, (pg. 3-12). This view presents the terms of the license for the
usage of the ES-CT.
Press the Yes button for acceptance, then the procedure can continue toward two
directions:
– if another ES-CT component is already existing in the host computer, then the
procedure will ask if it has to be uninstalled; in this case the following
Figure 3-7, (pg. 3-13) will be displayed
– otherwise the Figure 3-10, (pg. 3-15) will be shown.
If an already existing ES-CT software has been detected, then the following figure
will be displayed:
Figure 3-7 Existing previous ES-CT version uninstall
7. Refer to Figure 3-7, (pg. 3-13). Click on Install this Delivery version and De-install
the previous one option, to mark it.
Then click on Next button to continue on the following:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 3-13
............................................................................................................................................................................................................................................................
Figure 3-8 Uninstall confirmation
8. Refer to Figure 3-8, (pg. 3-14). Click on Yes button to continue:
Figure 3-9 Uninstall previous ES-CT version successfully completed
9. Refer to Figure 3-9, (pg. 3-14). This window informs that the de-installation of the
previous ES-CT software has been successfully completed.
Clicking on Ok button, the procedure will return the following Figure 3-10, (pg. 3-15).
............................................................................................................................................................................................................................................................
3 - 14 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 3-10 Choose destination folder for ES-CT installation
10. Refer to Figure 3-10, (pg. 3-15). The procedure proposes the default directory (C:\...)
for the installation.
CAUTION
All the applications for the ES-Craft Terminal must be installed under the same
disk partition of the host Personal Computer.
The Browse button can be used to change directory: in this case a file manager box
will be opened to choose a new folder.
When finished, select Next button.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 3-15
............................................................................................................................................................................................................................................................
Figure 3-11 Setup type
11. Refer to Figure 3-11, (pg. 3-16). It proposes the setup type, that is only the Typical
one. Click on Next button.
Figure 3-12 Program Folder denomination
12. Refer to Figure 3-12, (pg. 3-16). It suggests the default program-icon name and
permits to change it, if necessary.Click on Next button.
............................................................................................................................................................................................................................................................
3 - 16 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 3-13 Start copying files and current settings summary
13. Refer to Figure 3-13, (pg. 3-17). It displays the current settings for the installation.
If any displayed setting is not correct, click on Back option for a review, otherwise:
click on Next button to start the files copying.
Then, a series of automatic windows presentation will be displayed, showing the setup
in progress; see an example in next figure:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 3-17
............................................................................................................................................................................................................................................................
Figure 3-14 Setup in progress, temporary windows sequence presentation
14. Refer to Figure 3-14, (pg. 3-18). The ES-CT installation procedure starts and, after
intermediate automatic screens, it will continue toward two directions:
– If more than one component installation at a time has been chosen in
Figure 3-5, (pg. 3-11), then the following Figure 3-15, (pg. 3-19) will be
displayed.
– otherwise, if only one component installation at a time has been chosen in
Figure 3-5, (pg. 3-11), then the Figure 3-16, (pg. 3-20) will be displayed.
............................................................................................................................................................................................................................................................
3 - 18 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 3-15 Successive installation, temporary windows presentation
15. Refer to Figure 3-15, (pg. 3-19). The sequence of successive components installation
procedure continues and, after intermediate automatic screens, the procedure will
continue as detailed in the point Step 19.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 3-19
............................................................................................................................................................................................................................................................
Figure 3-16 Installation procedure menu window (2nd step)
16. Refer to Figure 3-16, (pg. 3-20). To install the SNMPCT-K-ADD-ON component
click on CT products installation and then on Next to access the following view
shown in Figure 3-17, (pg. 3-20). .
Figure 3-17 Craft Terminal master setup, list of detected Components on the
media
17. Refer to Figure 3-17, (pg. 3-20). The screen lists the installed Software Components
detected.
Click on OK to present next dialog box:
............................................................................................................................................................................................................................................................
3 - 20 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 3-18 Selecting SNMPCT component
18. Refer to Figure 3-18, (pg. 3-21). This view permits to select the software components
to be installed.
To install the SNMPCT Manager: click on Clear All button, then click on the square
correspondent to SNMPCT-K-ADD-ON component to mark it with a check, and then
click on Next.
19. At this point the procedure can continue toward the following directions:
• If no previous SNMPCT-K-ADD-ON component is installed in the host
computer, then the procedure will continue presenting the following figures:
Figure 3-21, (pg. 3-24), then Figure 3-22, (pg. 3-25), then Figure 3-24, (pg. 3-26),
and then Figure 3-25, (pg. 3-27).
• If another SNMPCT-K-ADD-ON component is already existing in the host
computer, then two cases will be possible:
– Different release: in this case the procedure will ask if it has to be uninstalled,
displaying Figure 3-19, (pg. 3-22), then Figure 3-21, (pg. 3-24), and so on,
skipping Figure 3-23, (pg. 3-26).
– Equal or similar release: in this case (maintenance) the procedure will continue
displaying Figure 3-20, (pg. 3-23), then Figure 3-21, (pg. 3-24), and so on.
If another different release of SNMPCT software has been detected, then the
following figure will be displayed:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 3-21
............................................................................................................................................................................................................................................................
Figure 3-19 Existing different SNMPCT release to be uninstalled
20. Refer to Figure 3-19, (pg. 3-22). This view permits to uninstall the different software
components.
To uninstall the SNMPCT component: select the Remove it... item, and then click on
Next.
The procedure will continue on Figure 3-21, (pg. 3-24).
If another equal or similar release of SNMPCT software has been detected, then the
following figure will be displayed:
............................................................................................................................................................................................................................................................
3 - 22 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 3-20 Existing previous similar release to be maintained: REPAIRE
21. Refer to Figure 3-20, (pg. 3-23). Select the Repair item, to maintain the software
release.
Then click on Next button to continue to the following:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 3-23
............................................................................................................................................................................................................................................................
Figure 3-21 SNMP CT Add On setup
22. Refer to Figure 3-21, (pg. 3-24). This window permits to choose between CT-K (new
CT version) or the Q3CT-P (old CT version) where the SNMP-AddOn packets are to
be inserted.
Click on CT-K... to select the new CT version.
Then, clicking on Next button, the procedure will display the following
Figure 3-22, (pg. 3-25).
............................................................................................................................................................................................................................................................
3 - 24 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 3-22 SNMPCT setup in progress temporary window
23. Refer to Figure 3-22, (pg. 3-25). This is a temporary window showing the setup
progress.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 3-25
............................................................................................................................................................................................................................................................
Maintenance case (skipped in case of first installation):
Figure 3-23 Maintenance Finished
24. Refer to Figure 3-23, (pg. 3-26). This window informs that maintenance is completed.
Click on Finish to continue.
Figure 3-24 SNMPCT installation completed
25. Refer to Figure 3-24, (pg. 3-26). This window informs that the installation of the
SNMPCT software has been completed.
Press the OK button, then the following figure will be shown:
............................................................................................................................................................................................................................................................
3 - 26 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 3-25 Selecting installation procedure (end step)
26. Refer to Figure 3-25, (pg. 3-27). The above view permits to select the installation
procedures options.
In this final phase select the last option (QUIT), then click on Next button to end and to
leave the installation application.
WARNING
After finished the installation, a Restart of the personal computer is necessary
(Start Î ShutDown Î Restart the computer).
WARNING
After the restart of the personal computer, the following window operation is
necessary: Start Î Programs Î ALCATEL Î SNMPCT-K-ADDON Î SNMP-
AddOn Customization.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 3-27
CT Operator’s Guide NE-ES package installation procedure
............................................................................................................................................................................................................................................................
NE-ES package installation procedure

After the installation of the craft-terminal packages, the installation of the NE-ES package
(i.e. the file descriptor for the ES part, to be downloaded inside the NE in a subsequent
step) is needed. Execute the following operations:
Start the NES (Network Element Synthesis) view as described in “Start-Up of the ES Craft
Terminal management software” (p. 3-40), then the following window will be displayed:
Figure 3-26 Descriptor files administration
1. Refer to Figure 3-26, (pg. 3-28). In this window, select the menu options:
Supervision Î Files Administration Î SWP Administrator.
The Software Package Administration window will be opened:
............................................................................................................................................................................................................................................................
3 - 28 P/N 8DG15785AAAA
NE-ES package installation procedure CT Operator’s Guide
............................................................................................................................................................................................................................................................
Figure 3-27 Software Package Administration-ES service specific
2. Refer to Figure 3-27, (pg. 3-29). This window contains three folders: SDH,
SERV.SPEC. and OMSN;
select the SERV.SPEC. (Service Specific) folder, then click on Install.. button.
A file-manager box will be opened, as shown in Figure 3-28, (pg. 3-30).
In this file-browser box, select the CD-ROM driver (e.g. E:\, see note below) and the
filename path: Ect\Swdw\ESx\(version)\ESx.dsc (i.e. the ES descriptor file); then
click on Open button; at this point the installation will start.
WARNING
If not already in, insert the ES software CD-ROM into the PC driver, the
installation setup is started automatically; stop the setup clicking on Cancel
button and then confirm with Exit Setup.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 3-29
............................................................................................................................................................................................................................................................
Figure 3-28 File-Browser for Software Package installation
Figure 3-29 Software Package Administration - create Enhanced OMSN
3. Refer to Figure 3-30, (pg. 3-31). In this window click on the SDH/WDM folder, then
select the specific equipment with the desired version to be associated with the ES
part.
............................................................................................................................................................................................................................................................
3 - 30 P/N 8DG15785AAAA
NE-ES package installation procedure CT Operator’s Guide
............................................................................................................................................................................................................................................................
WARNING
If the appropriate SDH/WDM Package is not already installed, it must be done
in the same way as described for the ES “Service-Specific“ package, in the
previous Step 2; (for more details see 1320CT Handbook listed in Table 1, (pg.
1-xxviii)).
Click on Create OMSN button, to create a new software package: SDH+ES, whose
name will be the same of the equipment, with the “E" suffix (Enhanced).
WARNING
If the Create OMSN button is “greyed" (i.e. not available), it means that the
relevant OMSN is already existing: in this case go to the next step.
Figure 3-30 Software Package Administration - add ES service
4. Refer to Figure 3-27, (pg. 3-29). In this window click on the “OMSN" folder. In the
Created OMSN Packages field, select the specific “Enhanced" OMSN, as created in
the previous point.
Select the ES version (in the Compatible Add-Ons field) and click on Add button.
WARNING
If the Add button is “greyed" (i.e. not available), it means that the relevant add-
on service is already installed
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 3-31
............................................................................................................................................................................................................................................................
WARNING
In case of migration to a new release containing a new “ADD-ON" (Service
Specific packet such as the ES-swp), from an old release containing another
service packet (for instance an ATM-swp), the download of the software into the
NE must be done in two steps:
a. first step downloading the new SDH packet associated with the known
service packet (e.g.: enhanced OMSN with ATM)
b. second step downloading the new SDH packet associated with the new
After the aforesaid operations, the software package SDH+ES is installed in the host
computer and can be downloaded into the NE, in a subsequent step, from the EML-
USM environment, as described in “NE-ES software downloading” (p. 3-36).
5. Refer to Figure 3-27, (pg. 3-29). At the end of the operation, exit this application by
means of the Close button.
............................................................................................................................................................................................................................................................
3 - 32 P/N 8DG15785AAAA
Software Uninstallation procedure CT Operator’s Guide
............................................................................................................................................................................................................................................................
Software Uninstallation procedure

ES-CT Uninstallation
To de-install the software in WINDOWS environment, execute the following operations:
1. Open the Windows-Control Panel (Start Î Settings Î ControlPanel) and select the
Add/Remove Programs icon, as for the following figure.
Figure 3-31 Add/Remove Programs icon selection
2. Refer to Figure 3-31, (pg. 3-33). Click twice on the Add/Remove Programs icon to
open it; then the next window will appear:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 3-33
CT Operator’s Guide Software Uninstallation procedure
............................................................................................................................................................................................................................................................
Figure 3-32 Add/Remove Programs view
3. Refer to Figure 3-32, (pg. 3-34). Select, in the Current installed programs. list of this
window, the application FASTETHUSM x.x.x (or other CT components) and click on
the Change/Remove button.
A confirmation message is presented:
Figure 3-33 Delete confirmation (example)
4. Refer to Figure 3-33, (pg. 3-34). After confirmation with Yes button, next figure
(example) appears, indicating the deleting process:
............................................................................................................................................................................................................................................................
3 - 34 P/N 8DG15785AAAA
Software Uninstallation procedure CT Operator’s Guide
............................................................................................................................................................................................................................................................
Figure 3-34 Delete completed (example)
Refer to Figure 3-34, (pg. 3-35). At the end of the deleting process click OK.
The uninstallation of the SNMPCT component can be done in a similar way, by
selecting the Alcatel-Lucent CT Kernel (SNMP Add-On v...) row. The de-
installation procedure for other Craft Terminal components is the same too.
Then it is possible to de-install other Alcatel-Lucent Craft Terminal software
components or close the Control Panel window, exiting the procedure.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 3-35
CT Operator’s Guide NE-ES software downloading
............................................................................................................................................................................................................................................................
NE-ES software downloading

The download is the operation that permits to transfer a software package from the
computer (server) to the specific equipment (client). The download generalities and details
are reported in the operator handbook relevant to the specific equipment. The download is
to be done in the EML-USM context (i.e. SDH-CT); to start the sdh-ct select (in the NES
view) the OMSN hosting the ES board and then the option Supervision Î Show
Equipment (see also “Start-Up of the ES Craft Terminal management software”
(p. 3-40)).
To download the ES-NE software, execute the following operations:
1. In the EML-USM view, select the menu options: Download Î Init Download... to
activate the following window:
Figure 3-35 Download Initiate (example)
............................................................................................................................................................................................................................................................
3 - 36 P/N 8DG15785AAAA
NE-ES software downloading CT Operator’s Guide
............................................................................................................................................................................................................................................................
2. Refer to Figure 3-35, (pg. 3-36). In this box, select the software package containing
the ES service, i.e. that one with the “E" suffix (in this example 1650SME).
3. Press the Ok button to start, a confirmation box ask for a confirmation.
Figure 3-36 Download confirmation box
4. Press the OK button to start, a box showing the progress of the downloading process
will be then displayed.
Figure 3-37 Download progress
When the download will finish with the message “Software download completed",
click on Close button of this box.
5. Refer to Figure 3-35, (pg. 3-36). Click on Cancel to close this box, after download
completed.
6. In the EML-USM view, select the menu options: Download Î Units Info... to have
the following window:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 3-37
CT Operator’s Guide NE-ES software downloading
............................................................................................................................................................................................................................................................
Figure 3-38 NE Software package activation (example)
7. Refer to Figure 3-38, (pg. 3-38). Select the appropriate equipment-version tab of this
window. Select the Activate option of the “CurrentState\Action" pull-down field, and
then the Ok button, to activate the selected Software package.
8. Press the Ok button on the displayed confirmation box.
Figure 3-39 Activate SW package confirmation
Refer to Figure 3-38, (pg. 3-38). The SW Units Det. button opens another box giving some
information about the selected downloaded package.
............................................................................................................................................................................................................................................................
3 - 38 P/N 8DG15785AAAA
NE-ES software downloading CT Operator’s Guide
............................................................................................................................................................................................................................................................
Figure 3-40 SW package details
Refer to Figure 3-38, (pg. 3-38). Click on Cancel button to close this box.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 3-39
CT Operator’s Guide Start-Up of the ES Craft Terminal management software
............................................................................................................................................................................................................................................................
Start-Up of the ES Craft Terminal management software

In order to activate the Alcatel-Lucent product , perform the following sequence:
1. Start Î 1320CT
as shown in next figure:
Figure 3-41 1320CT software start-up
2. Then, the NES (Network Elements Synthesis) window will be displayed (see next
figure).
............................................................................................................................................................................................................................................................
3 - 40 P/N 8DG15785AAAA
Start-Up of the ES Craft Terminal management software CT Operator’s Guide
............................................................................................................................................................................................................................................................
Figure 3-42 NES view example
3. In the NES window, select the specific host equipment in the map folder, and:
• select the following menu options: Supervision Î Start Supervision
or
• click on the mouse right button and select Start Supervision,
the red question mark is replaced with a magnifier
4. When the supervision is ended;
• select the following menu options: NE Directory Î Realign ISA board
population
or
select the equipment and click on the mouse right button and select Realign ISA
•
board population,
5. When the realignment phase is finished (see Figure 3-43, (pg. 3-42) where ADM,
1660SM #r01sr1sl24(ES4-8FE3.0) means type of equipment [1660SM], rack number
[#r01], subrack number [#sr01], slot number [#sl24] and type of ISA board and
release [ES4-8FE3.0] ), select the ES equipment and:
• select the following menu options: Supervision Î Start Supervision
or
• click on the mouse right button and select Start Supervision,
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 3-41
............................................................................................................................................................................................................................................................
Figure 3-43 ES view example
6. Then:
• select the following menu options: Supervision Î Show Equipment
or
• click on the mouse right button and select Show Equipment,
7. The Login dialog box will be displayed.
Figure 3-44 Login dialog box
8. Digit the Login and Password and the ISA USM starts.
............................................................................................................................................................................................................................................................
3 - 42 P/N 8DG15785AAAA
Start-Up of the ES Craft Terminal management software CT Operator’s Guide
............................................................................................................................................................................................................................................................
Figure 3-45 ISA USM starting
The ES-CT application can be also activated from the SDH-CT view, by selecting the ES
board and then the following menu option: Equipment Î ISA Navigate (anyway this is
possible only after the “realignment" and the “start supervision" operations from NES
view).
WARNING
Before using the ES-CT, the downloading of the ES software into the NE, and
the assignment of the IP addresses to the host computer, to the Controller board
and to the ES Board (from sdh-ct: Configuration Î Comm/Routing Î
IPConfiguration Î ISABoardIPAddress) are necessary. See “NE-ES software
downloading” (p. 3-36) for details about download procedure, the OMSN-
Operator Handbook for the board IP address setting, and the 1320CT Basic
Handbook listed in Table 1, (pg. 1-xxviii) for the PC IP address setting.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 3-43
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
3 - 44 P/N 8DG15785AAAA
4 Craft Terminal for ES1-
ES4 Management
Overview
This chapter describes all the views presented by the ES-Craft Terminal, including all the
information needed to set the various Alcatel-Lucent ISA ES1/4 parameters and
configurations.
• “Summary procedure for ES Management” (p. 4-4)
• “Main view” (p. 4-5)
• “List of the menus options” (p. 4-12)
• “Supervision management” (p. 4-24)
• “Generic and common functions” (p. 4-26)
• “Diagnosis and Alarms Configuration” (p. 4-33)
• “MIB Management” (p. 4-47)
• “Transmission” (p. 4-49)
• “OAM” (p. 4-217)
• “Connection” (p. 4-235)
• “Performance” (p. 4-263)
............................................................................................................................................................................................................................................................
ISA ES1/4 Release 3.0 Craft Terminal for ES1-ES4 Management
CT Operator’s Guide ES-CT summary
............................................................................................................................................................................................................................................................
ES-CT summary
This application (here named “ES-CT") permits to manage the ES boards provisioned for
the OMSN equipment.
WARNING
Before using the ES-CT, the assignment of some IP addresses is necessary:
a. to the CT (personal computer). See the 1320CT-Basic Operator
Handbook listed in Table 1, (pg. 1-xxviii) for details about IP address
setting for the host computer.
b. to the EC (controller) board (from sdh-ct: Configuration Î Comm/Routing
Î IP Configuration Î IP Address Of Point To Point Interface). See the
OMSN-Operator Handbook listed in Table 1, (pg. 1-xxviii) for details
about IP address setting for EC board.
c. to the ES board (from sdh-ct: Configuration Î Comm/Routing Î IP
Configuration Î ISA Board IP Address). See the OMSN-Operator
Handbook listed in Table 1, (pg. 1-xxviii) for details about IP address
setting for ES board.
WARNING
f, for any reason, the IP address is changed, the following customization
WINDOWS command is necessary: Start Î Programs Î ALCATEL Î SNMPCT-K-
ADDON Î SNMP-AddOn Customization.
It has to be used in conjunction with the 1320CT platform, because it is an option of this
latter; the activation of “ES-CT" starts from the Network Element Synthesis view, by doing
the following operations:
• select the NE hosting the ES board; then, with the pop-up menu: Realign ISA Board
Population; then select the displayed ES-NE and with the pop-up menu: Start
Supervision.
After having done these latter operations, the entering into ES-CT can be done:
a. from the NES view, by selecting the ES object and then the pop-up menu option
Show Equipment
b. from the SDH-CT view, by selecting the ES board and then the menu option
Equipment Î ISA Navigate.
After the activation, the following temporary screen is displayed.
............................................................................................................................................................................................................................................................
Craft Terminal for ES1-ES4 Management ISA ES1/4 Release 3.0
ES-CT summary CT Operator’s Guide
............................................................................................................................................................................................................................................................
Figure 4-1 Logon view
............................................................................................................................................................................................................................................................
CT Operator’s Guide Summary procedure for ES Management
............................................................................................................................................................................................................................................................
Summary procedure for ES Management

The following actions have to be done, mainly, for ES traffic management (the order of
sequence is mandatory, for a correct working):
a. IP address assignment for the Craft Terminal, the EC board and the ES board
b. definition of SDH virtual ports and containers to be used for ES signals and
relevant Remote Ethernet Ports associations (via the menu Configuration Î ISA
Port Configuration, on SDH-CT)
c. cross-connection of virtual SDH containers transporting Ethernet (on SDH-CT)
d. Bridge configuration (on ES-CT)
e. Ethernet or Bridge Ports definition: ETS or ETB (on ES-CT)
f. Local and Remote Ethernet ports configuration and GFP or LAPS interface
definition (on ES-CT)
g. Bridge Ports configuration (on ES-CT)
h. traffic contract definition (on ES-CT)
i. V-LAN Registration, in case of Virtual or Provider Bridge (on ES-CT)
j. InFlow/OutFlows creation: see Note: below (on ES-CT)
k. Classifiers definition: see Note: below (on ES-CT)
l. Cross-Connection between InFlows and OutFlows: see Note: below (on ES-CT)
m. Configuration of Performance Monitoring points (on ES-CT).
Note: The points ( j), ( k), ( l) must be done in one single step by
means of the Connection wizard. See “Create Ets XC One Step
(MAC & Virtual) for the Ethernet Port” (p. 4-242) and “Create Ets
XC One Step (Provider) for the Ethernet Port” (p. 4-246).
............................................................................................................................................................................................................................................................
Main view CT Operator’s Guide
............................................................................................................................................................................................................................................................
Main view
After the temporary logon view, the shown screen is similar to the following
Figure 4-2, (pg. 4-7), where a generic view is reported in order to explain the meaning of
its main components.
The following fields and areas are generally displayed:
• title: window frame containing name of Craft Terminal and release and equipment
labels.
• menu bar: bar containing the applications pull-down menus: Views, Configuration,
Diagnosis, Supervision, Mib_Management, OAM Domain, Transmission / Connection /
Performance (alternative: the desired menu application can be activated either from the
Views options, or from the application tabs), Help (see “List of the menus options”
(p. 4-12)).
• tool bar: providing some fast buttons (from left to right): go to the previous view; go to
the next view; refresh tree, properties of selected resource; delete the selected resource;
print the selected resource; help about the clicked item.
Note: In the Performance and Connection applications, some
further buttons are displayed (fast keys), in order to switch among
different modalities of the function).
• curr.Appl.: current selected application.
• Appl.tabs (Application tabs): containing the tabs to enter the main ES applications:
Transmission, Connection, Performance. By clicking on these tabs, the corresponding
alternative menu is displayed in the menu-bar, and the displayed areas are changed,
according to the selected application.
• message row: it displays an help/information message about the current action or the
object on which the mouse is transiting over.
• Severity Alarms Synthesis: a series of boxes reporting the alarms and their current
counting, subdivided according to the assigned severity: CRItical, MAJor, MINor,
WarNinG, INDeterminate; the detailed description is reported in Chapter 5,
“Maintenance”.
• Domain Alarms Synthesis: a box reporting the alarms counting relevant to the
Transmission Domain; the detailed description is reported in the Chapter 5,
“Maintenance”.
• Management States Control Panel: a series of boxes displaying the states of the
management control: SUPervised, local access (key), COM (CT-communication port
connected), OS (1353SH presence), Manager (upper level NM-manager presence); the
detailed description is reported in Chapter 5, “Maintenance”, see also “Supervision
management” (p. 4-24).
............................................................................................................................................................................................................................................................
CT Operator’s Guide Main view
............................................................................................................................................................................................................................................................
• A1 (Resources Tree Area): this area displays the available resources by means of a tree
structure; when an item is indicated by a “+" sign it means that the resource contains
more lower resources and can be expanded, if indicated by “-" it means the resource is
already expanded, if no sign is present it means that the resource is a leaf. An item of
the tree can be selected by clicking on the left mouse button; a pop-up menu,
containing the actions that can be done on the selected item, is generated by clicking
on the right mouse button. See details in “Resources TREE area (A1)” (p. 4-7).
• A2 (Application Table Area): this area lists, in tabular form, the object contained in the
selected resource (selected in the tree). A row of the table can be selected by clicking
on the left mouse button; a pop-up menu, containing the actions that can be done on
the selected item, is generated by clicking on the right mouse button.
• A3 (Resource Information Area): this area displays, only for information purpose, the
details about the selected resource, after selecting it in the above area A2; the
displayed information depends on the application that is being used.
• Pop-up menus: some menus pop up in the areas A1 or A2, after selecting a resource
and clicking on the right button of the mouse; the pop-up menus yield directly the
possible options, for that particular selected resource, that are related to the current
selected application.
The pop-up menus appearing in the tree-area (A1) are also called contextual pop-up
menu. The items contained in the contextual pop-up menus are the same as those
contained in the specific menus of the menu-bar. The pop-up menu can also be
activated after selecting a resource in the application-table-area A2.
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Figure 4-2 Main view
title
menu bar
tool bar
Severity Alarms Domain Alarms

Synthesis Synthesis
curr.Appl.
Appl. tabs
A1
A2
Manag. States
Control Panel
Contextual
pop-up
menu
A3
message
row
The whole window and also the “A1", “A2" and “A3" areas can be stretched, by means of
the mouse arrow.
Further, a self-explaining message appears under the mouse cursor, when it is passed over
an active field; this message reports the status-information, when the mouse is passed over
the resources listed in the Tree area (see “Spontaneous Informations about Resources in
the Tree Area” (p. 4-11)).
Resources TREE area (A1)

The Tree is composed of: a “root" (the ISA ES Node), “branches" and “leaves". A branch
contains one or more leaves and is expandable, to see the leaves. It is preceded by a little
square containing a “+" sign or a “-" sign; the “+" means that the branch is contracted and
can be expanded, the “-" means that the branch is already expanded and can be contracted.
A leaf is not preceded by any sign and means that cannot be expanded.
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Figure 4-3 TREE area example
ISA-Switch
expanded branch
leaf
Usable Ethernet port
not expanded branch
Not usable Ethernet port
All the ports are visualized automatically by the system in the tree; if not yet defined, they
are greyed.
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Resources Visualization in the Tree Area

• ES Node (with active alarms):
The colored circle before the switch is a visual indication of the alarms synthesis, see below
for details.
• ETHERNET port
– configurable, not in service (down):
– Local (or Remote), in-service (up), with active alarms:
– in not usable state, not configurable:
The colored ball before the port is a visual indication of the alarms synthesis, see below for
details.
• IN-FLOW Point:
• OUT-FLOW Point:
The presence of a little upper cross (“X") means that the point is connected.
• CLASSIFIER Point:
• ETB Port: orange colored (also called “(R)STPBridgePort")
• AggGroup-Root: named AggGroup-Management, it

collects all created LAGs
• LAG, i.e., “Link Aggregation Group”

Note:
– ES Node: representing the ISA-ES virtual node
– LOCAL ETHERNET PORT: representing the local ethernet access
– REMOTE ETHERNET PORT: representing the remote ethernet access, i.e.
the interface towards the network, mapping the ethernet frames over SDH
– IN-FLOW: internal resource used into a “Local" or “Remote" ethernet port, in
order to define and characterize an incoming ethernet data flow
– OUT-FLOW: internal resource used into a “Local" or “Remote" ethernet port,
in order to define and characterize an outgoing ethernet data flow
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
– Eth2ETS CLASSIFIER: representing the Classifier Point (identification), to

classify the ethernet data flow; it defines the priority and the Vlan number of
the flow; it can define also a range of Vlan links into an ethernet flow, if they
are directed towards the same way
– ETB Port (also called “(R)STPBridgePort"): representing the Ethernet Ports
that have been configured to work in “autolearning" modality. The colour is
changed to orange, after their swapping
– AggregateGroupManagement: representing the logical point to organize all
the “LinkAggregated" resources
– LAG: representing the logical resource grouping the links to be aggregated.
Visualization of Resources Conditions in the Tree Area

Colors of the displayed resource:
• colored (yellow, or blue, green, etc.) = available and in-service (active)
• light grey = available but not-in-service
• dark grey = out-of-context (not manageable in current application)
A little upper cross (above the resource symbol) means that the resource is a connection
point.
A little lower black point (under the resource symbol) means that the resource contains
active PM (Performance Monitoring) points.
Note: The black point is displayed only in the Performance
domain.
Alarms Visualization in the Tree Area

Alarms summary: (at level of ES Node)
The Alarms summary is visualized only at the ES Node level, reporting the colors of the
maximum alarm severities, detected in the current ES Node (inner circle) and in the
contained resources (outer rings). If the inner circle is not colored, it means that the alarms
are in the contained resources and not in the parent one.
Alarms synthesis (only at the ports level):
The Alarms synthesis is visualized at all the ports, reporting all the alarm severity colors
(in form of concentric rings), detected in the current resource (inner circle) and in the
contained resources (outer rings). If the inner circle is not colored, it means that the alarms
are in the contained resources and not in the parent one.
The colors of the alarms are detailed in Chapter 5, “Maintenance”.
............................................................................................................................................................................................................................................................
4 - 10 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Spontaneous Informations about Resources in the Tree Area

A self-explaining message appears under the mouse cursor, when it is passed over an
active field; this message reports the status-information, when the mouse is passed over
the resources listed in the Tree area (see Figure 4-4, (pg. 4-11)); more information is given
by pressing the F12 key on the keyboard.
This spot gives information about: Traffic Label, Traffic Contract, Connection Type,
Alarms, etc.
Figure 4-4 Spontaneous information message example
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-11
CT Operator’s Guide List of the menus options
............................................................................................................................................................................................................................................................
List of the menus options

The menu bar contains all the options for the configuration and supervision of the ISA-ES
Elements.
These paragraphs list all the menus options. Their usages and functions are described in
other paragraphs that are referenced; here a brief description is given for someone of them.
WARNING
Some option of the menus can be sometime deactivated (greyed), if its function
is not congruent with the currently selected item or application, or when it is
not yet operative.
The menu bar contains “permanent menus" (always displayed) and other “specific menus",
alternative between them, displayed only when a particular application is selected in the
Application tabs, or when they are selected in the Views items. Starting from left, the menus
are:
• Permanent Menus
– Views (first column). See options in “Views menu introduction” (p. 4-13).
– Configuration(second column). See options in “Configuration menu introduction”
(p. 4-14).
– Diagnosis (third column). See options in “Diagnosis menu introduction” (p. 4-14).
– Supervision (fourth column). See options in “Supervision menu introduction”
(p. 4-15).
– MIB-Management (fifth column). See options in “Mib-Management menu
introduction” (p. 4-15).
– OAM Domain (sixth column). See options in “OAM Domain menu introduction”
(p. 4-15).
– Help (last column: it activates the help system). See options in “Help menu
• Specific alternative Menus
– Transmission(seventh column) See options in “Transmission menu introduction”
(p. 4-16).
– Connection (seventh column). See options in “Connection menu introduction”
(p. 4-20).
– Performance(seventh column). See options in “Performance menu introduction”
(p. 4-21).
............................................................................................................................................................................................................................................................
4 - 12 P/N 8DG15785AAAA
List of the menus options CT Operator’s Guide
............................................................................................................................................................................................................................................................
• Pop-up Menus
The menu items contained in the contextual pop-up menus are the same as those
contained in the specific menus of the menu-bar; e.g.: the contextual pop-up item
Configure Ethernet Port of the Transmission application can be also activated by
selecting, in succession: Transmission in the applications tabs, then a Local (or Remote)
Ethernet port in the Tree area, then, in the menu-bar, Transmission Î Ethernet Port
Management Î Configure Ethernet Port; therefore for their details please refer to the
description given for the equivalent menu-bar options.
Views menu introduction

It contains the following entries:
• Backward: To go to the backward view.
• Forward: To go to the forward view.
• Transmission: to enter the Transmission application. See options in “Transmission
menu introduction” (p. 4-16).
It yields the Transmission menu in the seventh column of the menu bar.
• Connection: to enter the Connection application. See options in “Connection menu
It yields the Connection menu in the seventh column of the menu bar.
• Performance: to enter the Performance application. See options in “Performance menu
It yields the Performance menu in the seventh column of the menu bar.
• Arrange Windows: not yet operative
• Refresh: It refreshes the graphical views.
It contains the following sub-options:
– Refresh Tree: It refreshes the resources TREE.
• Open Object: not yet operative
• Open In Window...: not yet operative
• Search...: It activates a general search window from which a specific (or a group of)
resource can be searched. (See “Search in Views menu” (p. 4-28)).
• Filter...: not yet operative
• Print: It causes the printing of details for the selected resource list shown in the
Application Table area. (See “Print in Views menu” (p. 4-32)).
• Close...: not yet operative
• Exit: To close the ES-CT session.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-13
............................................................................................................................................................................................................................................................
Configuration menu introduction

• Alarms Severities: To manage the Alarms Severity Assignment Profile (ASAP). See
“Alarms Severity (ASAP management) in Configuration menu” (p. 4-33).
• Set Alarms Severities: To associate an ASAP to a resource. See “Set Alarms Severities”
(p. 4-37).
• List CEPST Instances: not yet operative
• Loop-Back Management: See “Loop Back Management in Configuration menu”
(p. 4-40).
• Set ACD level: not yet operative
• Traffic Descriptor: To manage the parameters defining the traffic.
– ETS Traffic Descriptor: to manage the Ethernet traffic parameters. See “ETS Traffic
Descriptor configuration” (p. 4-51) .
• Link Creation Wizard: (not yet operative).
To start a wizard program for helping during the Links configurations. This procedure
recalls, in the right order, the necessary dialogue windows to configure the links
parameters.
• Connection Wizard: (not yet operative). To start a wizard program for helping during
the Connections configurations. This procedure recalls, in the right order, the
necessary dialogue windows to configure the cross-connections.
• Options: To set some options relevant to the CT graphic interface and to the
applications (default values, measurement units, etc.). See “Options of Configuration
menu” (p. 4-26).
Diagnosis menu introduction

• Alarms: To enter the Alarms Surveillance (AS) application. See “Alarms Surveillance
(Diagnosis - Alarms option)” (p. 4-41). It contains the following sub-options:
– ISA Alarms: for the Surveillance of alarms relevant to the ES board.
– Object Alarms: for the Surveillance of alarms relevant to the selected object.
– Transmission Alarms: for the Surveillance of alarms relevant to the Transmission
domain.
• Log Retrieval: To manage the Event Log Browser (ELB).
See “Event Log Browser (Diagnosis - Log Retrieval)” (p. 4-43). It contains the
following sub-options:
– Event: to “browse" the logs relevant to the ES events.
............................................................................................................................................................................................................................................................
4 - 14 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
– Alarm: to “browse" the logs relevant to the ES alarms.

• Navigation: It contains the following sub-options:
– EMLUSM: To navigate to the parent EML-USM layer (OMSN equipment). See
“Navigation to EML-USM in Diagnosis menu” (p. 4-46).
Supervision menu introduction

• Access State: To manage the supervision access states. See “Access state (allow or
inhibit ES-Craft access)” (p. 4-24).
– OS: to switch the access from CT to the OS
– Requested: to request the access for the local CT
• Alarms: To manage the alarms relevant to the supervision state.
– Re-synchronize: See “Alarms re-synchronization” (p. 4-41) .
– Allow Notification: See “Allow/Inhibit Alarms Notifications” (p. 4-41).
– Inhibit Notification: See “Allow/Inhibit Alarms Notifications” (p. 4-41).
• Set Manager List: To manage the accesses to the local node from the various types of
managers that are available. See “Set Manager list” (p. 4-25).
• Restart ISA: To restart the equipment software. See “Restart ISA (Not operative)”
(p. 4-25). Not operative in current release.
Mib-Management menu introduction

• Backup/Restore DB: To manage the backup and restore of the MIB (configuration data-
base). See “Backup/Restore DB” (p. 4-47).
• Compare two Backup Files: Not operative in current release.
OAM Domain menu introduction

• Configure Resources (OAM): To manage the resources of OAM Domain. See
“Configure Resources” (p. 4-218).
• Properties Resources (OAM): To show properties for resources of OAM Domain. See
“Properties Resources” (p. 4-230).
• Configure (OAM): To manage the Global parameters for OAM. See “Configure”
(p. 4-230).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-15
............................................................................................................................................................................................................................................................
• Properties (OAM): To show the Global parameters for OAM. See “Properties”
(p. 4-231).
• Configure LoopBack (OAM): To manage the parameters for Alcatel-Lucent-Proprietary
LoopBack. See “Configure LoopBack” (p. 4-232).
• LoopBack Properties (OAM): To show the parameters for Alcatel-Lucent-Proprietary
LoopBack. See “Loop Back Properties” (p. 4-234).
Transmission menu introduction

• ISA Management: To manage the transmission parameters for the ISA-ES unit.
– Configure ISA: See “Configure ISA” (p. 4-62) .
– VLAN Registration: See “VLAN Registration” (p. 4-118).
– Private VLAN Registration: Not operative in current release.
– Resources Availability: See “Resources Availability” (p. 4-122)
– IGMP Management:
– Configure IGMP: See “Configure IGMP” (p. 4-155).
– IGMP Properties: See “IGMP Properties” (p. 4-158).
– ERP Management:
– Configure Physical ERP: See “Configure Physical ERP (Topologies)” (p. 4-164).
– Configure Logical ERP: See “Configure Logical ERP (Instances)” (p. 4-173).
– ISA Properties: See “ISA Properties” (p. 4-64).
• Ppp Port Management: Not operative in current release.
• Ethernet Port Management: To manage the transmission parameters for an Ethernet
port (Local or Remote). It contains the following sub-options:
– Substitute EthernetÎ Ppp: Not operative in current release.
– Substitute Server Layer: See “Substitute Server Layer for an Ethernet Port”
(p. 4-92).
– ETH on GFP
– ETH on LAPS
– Substitute Client Layer: See “Substitute Client Layer for an Ethernet Port or an
Aggregator” (p. 4-116).
– Ethernet(ETS) Î Bridge(ETB)
– Bridge(ETB) Î Ethernet(ETS)
– Queue (QoS) Management:
............................................................................................................................................................................................................................................................
4 - 16 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
– Configure Queue: see “Configure Queue for the Ethernet Port” (p. 4-150).
– Properties Queue: see “Properties Queue for the Ethernet Port” (p. 4-152).
– GFP Client Layer Management: Not operative in current release.
– Bridge Port Management: To manage transmission parameters for an ETB Port. It
contains the following sub-options:
– Configure Bridge Port (Virtual): See “Configure Bridge Port (Virtual)” (p. 4-130)
– Configure Bridge Port (Provider): See “Configure Bridge Port (Provider)”
(p. 4-125)
– Configure Bridge Port (MAC): See , “Configure Bridge Port (MAC)” (p. 4-133)
– Bridge Port Properties: See “Bridge Port Properties of the Ethernet Port”
(p. 4-148)
– Show VLAN info: See “Show VLAN Info of the Ethernet Bridge Port”
(p. 4-149).
– CEPST Management: Not operative in current release.
– Aggregation Port:
– Configure: See “Configure an Aggregation Port” (p. 4-202).
– Properties: See “Properties an Aggregation Port” (p. 4-205).
– Create Flow Group: Not operative in current release.
– Create ETS InFlow: See “Create ETS InFlow for an Ethernet Port” (p. 4-100).
– Create ETS OutFlow: See “Create ETS OutFlow for an Ethernet Port” (p. 4-103).
– Create Provider InFlow: See “Create Provider InFlow for an Ethernet Port”
(p. 4-112).
– Create Provider OutFlow: See “Create Provider OutFlow for an Ethernet Port”
(p. 4-115).
– Configure Ethernet Port:
– Local port: See “Configure (local) Ethernet Port” (p. 4-67).
– Remote port: See “Configure (remote) Ethernet Port” (p. 4-80)
– Characterization Service:
– Other: See “Characterization Service of an Ethernet Port” (p. 4-93).
– Ets Virtual Switch (Service): Not supported in current release
– Port To Port (Service): See “Characterization Service of an Ethernet Port”
(p. 4-93).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-17
............................................................................................................................................................................................................................................................
– Traffic Management:
– Traffic Enabled: See “Traffic Management of an Ethernet Port” (p. 4-93).
– Traffic Disabled: See “Traffic Management of an Ethernet Port” (p. 4-93).
– ACL Management:
– Configure ACL: See “Configure ACL for an Ethernet Port” (p. 4-94).
– Properties ACL: See “Properties ACL of an Ethernet Port” (p. 4-99).
– Disassociate ACL: See “Disassociate ACL for an Ethernet Port” (p. 4-99).
– In Fiber In Band Management:
– Create In Fiber In Band: See “Create the In Fiber In Band” (p. 4-207)
– Modify In Fiber In Band: See “Modify the In Fiber In Band” (p. 4-208)
– Delete In Fiber In Band: See “Delete the In Fiber In Band” (p. 4-209)
– Properties In Fiber In Band: See “Properties of the In Fiber In Band” (p. 4-209)
– EFM Management:
– Configure EFM: See “Configuration of the EFM” (p. 4-211)
– EFM Properties: See “Properties of the EFM” (p. 4-215)
– Ethernet Port Properties:
– Local port: See “Configure (local) Ethernet Port” (p. 4-67).
– Remote port: See “Configure (remote) Ethernet Port” (p. 4-80).
• Aggregator Management:
– Create Aggregator: See “Create Aggregator” (p. 4-193).
• Aggregator: (for LAG resource).
To manage the transmission parameters for a Link Aggregation Group.
– Substitute Client Layer: See “Substitute Client Layer for an Ethernet Port or an
Aggregator” (p. 4-116)
– ETB Layer
– ETS Layer
– Bridge Port Management:
– Configure Bridge Port (Provider): See “Configure Bridge Port (Provider)”
(p. 4-125)
– Configure Bridge Port (Virtual): See “Configure Bridge Port (Virtual)” (p. 4-130)
– Configure Bridge Port (MAC): See “Configure Bridge Port (MAC)” (p. 4-133)
– Bridge Port Properties: See “Bridge Port Properties of the Ethernet Port”
(p. 4-148).
............................................................................................................................................................................................................................................................
4 - 18 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
– Show VLAN Info: See “Show VLAN Info of the Ethernet Bridge Port”
(p. 4-149).
– CEPST Management: Not operative in current release.
– Create Flow Group: Not operative in current release.
– Create ETS InFlow: See “Create ETS InFlow for an Ethernet Port” (p. 4-100).
– Create ETS OutFlow: See “Create ETS OutFlow for an Ethernet Port” (p. 4-103).
– Create Provider InFlow: See “Create Provider InFlow for an Ethernet Port”
(p. 4-112).
– Create Provider OutFlow: See “Create Provider OutFlow for an Ethernet Port”
(p. 4-115).
– Configure Aggregator: See “Configure Aggregator” (p. 4-196).
– Delete Aggregator: See “Delete Aggregator” (p. 4-201).
– Characterization Service:
– Other (Service): See “Characterization Service of an Ethernet Port” (p. 4-93).
– Ets Virtual Switch (Service): Not supported in current release
– Port To Port (Service): See “Characterization Service of an Ethernet Port”
(p. 4-93).
– Traffic Management: See “Traffic Management of an Aggregator” (p. 4-94)
– Traffic Enable
– Traffic Disable
– Aggregator Properties: See “Aggregator Properties” (p. 4-201).
• MPLS Port Management: Not operative in current release.
• Group Flow Management: Not operative in current release.
• MPLS InSegment Management: Not operative in current release.
• MPLS OutSegment Management: Not operative in current release.
• ETS In Flow Management: To manage the transmission parameters for an InFlow point.
– Create Eth2ETS Classifier: See “Create Eth2ETS Classifier” (p. 4-107).
– Modify ETS InFlow: See “Modify ETS InFlow” (p. 4-106).
– Delete ETS InFlow: See “Delete ETS InFlow” (p. 4-107).
– ETS InFlow Properties: See “ETS InFlow Properties” (p. 4-106).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-19
............................................................................................................................................................................................................................................................
• ETS OutFlow Management: To manage the transmission parameters for an OutFlow

point.
– Modify ETS OutFlow: See “Modify ETS OutFlow” (p. 4-106).
– Delete ETS OutFlow: See “Delete ETS OutFlow” (p. 4-107).
– ETS OutFlow Properties: See “ETS OutFlow Properties” (p. 4-106).
• Classifier Management: To manage the transmission parameters for an ETS-Classifier
point.
– Modify Classifier: See “Modify Classifier” (p. 4-110).
– Delete Classifier: See “Delete Classifier” (p. 4-111).
– Classifier Properties: See “Classifier Properties” (p. 4-111).
Connection menu introduction

• Bridge Management: To manage the connection parameters for the Bridge.
– Filtering Data Base: See “Filtering Data Base for the Bridge” (p. 4-235).
– Segregated Port management: Not operative in current release.
• Ethernet Port Management: To manage the connection parameters for an Ethernet port.
– Segregated Port Set: Not operative in current release.
– Create Ets XC One Step (MAC/Virtual): See “Create Ets XC One Step (MAC &
Virtual) for the Ethernet Port” (p. 4-242).
– Delete Ets XC One Step (MAC/Virtual): See “Delete Ets XC One Step (MAC &
– Create Ets XC One Step (Provider): See “Create Ets XC One Step (Provider) for the
– Delete Ets XC One Step (Provider): See “Delete ETS XC One Step (Provider) for the
• Link AggregatorGroup Management: To manage the connection parameters for a LAG.
Note: These options are the same as the above Ethernet Port
Management.
– Segregated Port Set: Not operative in current release.
............................................................................................................................................................................................................................................................
4 - 20 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
– Create Ets XC One Step (MAC/Virtual): See “Create Ets XC One Step (MAC &
– Delete Ets XC One Step (MAC/Virtual): See “Delete Ets XC One Step (MAC &
– Create Ets XC One Step (Provider): See “Create Ets XC One Step (Provider) for the
– Delete Ets XC One Step (Provider): See “Delete ETS XC One Step (Provider) for the
• ETS InFlow Management: To manage the connection parameters for an InFlow point.
– Create Ets XC: Not operative in current release.
– Modify Ets XC: See “Modify ETS XC for the ETS InFlow” (p. 4-260)
– Ets XC Properties: See “ETS XC Properties for the ETS InFlow” (p. 4-261)
• ETS OutFlow Management: To manage the connection parameters for an OutFlow
point.
– Create Ets XC: Not operative in current release.
– Modify Ets XC: See “Modify ETS XC for the ETS OutFlow (not operative)”
(p. 4-262);
– Delete Ets XC: See “Delete Ets XC for the ETS OutFlow” (p. 4-262)
– Ets XC Properties: See “ETS XC Properties for the ETS OutFlow” (p. 4-262)
Performance menu introduction

• MPLS Switch Management:
To manage the Performance Monitoring (PM) Granularity for the Bridge. It contains
the following sub-options:
– Granularity 15 Minutes: See “Granularity 15Minutes/1Hour for the MPLS Switch”
(p. 4-263)
– Granularity 1 Hour: See “Granularity 15Minutes/1Hour for the MPLS Switch”
(p. 4-263).
• MPLS Port Management: Not operative in current release.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-21
............................................................................................................................................................................................................................................................
• Ethernet Port Management:

To manage the Performance Monitoring (PM) parameters for an Ethernet port. It
contains the following sub-options:
– Configure Eth Aggr: See “Configure Eth. Aggr. for an Ethernet Port” (p. 4-264)
– Eth Aggr Properties: See “Eth Aggr. Properties of an Ethernet Port” (p. 4-265).
• Flow Group Management: Not operative in current release.
• ETS InFlow Management: To manage the Performance Monitoring (PM) parameters for
an InFlow point. It contains the following sub-options:
– Configure InFlow: See “Configure InFlow for an ETS InFlow” (p. 4-267)
– InFlow Properties: See “InFlow Properties of an ETS InFlow” (p. 4-268).
• ETS OutFlow Management: To manage Performance Monitoring (PM) parameters for an
OutFlow point. It contains the following sub-options:
– Configure OutFlow: (not operative). See “Configure OutFlow for an ETS OutFlow”
(p. 4-270)
– OutFlow Properties: (not operative). See “OutFlow Properties of an ETS OutFlow”
(p. 4-270).
• IGMP <VLAN>: To manage IGMP statistic History Data counters for Node resource
(MPLS switch) and for the Ethernet port. It contains the following sub-options:
– Create IGMP<VLAN>. For the Node resource (MPLS switch) , see “Create IGMP
<VLAN> for Node resource” (p. 4-273). For the Ethernet port, see “Create IGMP
<VLAN> for Ethernet port” (p. 4-278).
– Modify IGMP<VLAN>. For the Node resource (MPLS switch) , see “Modify IGMP
<VLAN> for Node resource” (p. 4-275). For the Ethernet port, see “Modify IGMP
<VLAN> for Ethernet port” (p. 4-281).
– Properties IGMP<VLAN>. For the Node resource (MPLS switch) , see “Properties
IGMP <VLAN> for Node resource” (p. 4-275). For the Ethernet port, see
“Properties IGMP <VLAN> for Ethernet port” (p. 4-281).
• IGMP <VLAN, Multicast>: To manage IGMP statistic History Data counters for the
Node resource (MPLS switch). It contains the following sub-options:
– Create IGMP<VLAN, Multicast>. See “Create IGMP <VLAN, Multicast> for
Node resource” (p. 4-284)
– Modify IGMP<VLAN, Multicast>. See “Modify IGMP <VLAN, Multicast> for
Node resource” (p. 4-286)
– Properties IGMP<VLAN, Multicast>. See “Properties IGMP <VLAN, Multicast>
for Node resource” (p. 4-287)
............................................................................................................................................................................................................................................................
4 - 22 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Help menu introduction

• On Context: To activate a contextual help.
• Glossary: To display the glossary of the terms used.
• About: To display information about the ES-CT software.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-23
CT Operator’s Guide Supervision management
............................................................................................................................................................................................................................................................
Supervision management
In this paragraph and relevant sub-paragraphs general configuration referred to the
equipment supervision are described (ES-Craft Terminal access, local and upper
management list, etc.).
Access state (allow or inhibit ES-Craft access)

The ES-NE can be managed by the OS (Operations System) or by the ES-CT. To control
the competition of the OS and the CT, a Local Access Control (LAC) is available.
a. If the LAC is “granted" that means the CT is allowed to manage the NE. The icon
with a key symbol has a rectangular shape and its border is green.
b. If the NE is “isolated“ the icon with a key symbol has a rectangular shape and its
border is blue.
c. If the LAC is "access denied" that means the OS manages the NE and the CT is not
allowed to modify NE configuration (it can only “read"). The icon with a key
symbol has a circular shape.
If the LAC is "requested" that means the CT has requested permission from the OS
and is waiting for a replay.
However the OS does continue to provide a certain number of services. These services
include: Reception and processing of alarms, Performance processing, Switching back
to the OS access state.
The access state of an NE can be modified as follows:
1. Switching from the OS to the ES Craft Terminal access state
Select the Supervision pull down menu. Then select the Requested option from the
Access State cascading menu.
From the confirmation dialogue box that opens, you can confirm or cancel the "Craft
access" operation using the Yes or No push buttons. the request is up to the OS, which
accepts or refuses it.
If the OS doesn't answer in a predefined time it is assumed that the NE is in the Craft
access state and can be managed from an ES-CT.
............................................................................................................................................................................................................................................................
4 - 24 P/N 8DG15785AAAA
Supervision management CT Operator’s Guide
............................................................................................................................................................................................................................................................
2. Switching from the ES-CT access state back to the OS access state
Select the Supervision pull down menu. Then select the OS option from the Supervision
Î Access State cascading menu.
From the confirmation dialogue box that opens you can confirm or cancel the "OS
access" operation.
The NE is now managed by the OS.
Important! The key symbol icon on the management states of the NE
view indicates whether the NE is managed by a craft terminal or by the OS.
Important! Local Craft Terminal access is denied on recovery phases
after a loss of communication of the NE. When communication is lost with
the NE, the OS automatically recovers the communication and puts the
state that was set before the loss of communication (therefore the Craft
Terminal access can be denied or granted).
Set Manager list

This option allows the user to set the Manager list, i.e. to define the list and the priorities
of the entities that the ES-CT can access and manage.
Select the Set Manager list option from the Supervision pull down menu.
The dialog-box contains the following field:
• Current Value: to define the current Operator as BM (Bandwidth Manager) or EML
(Element Management Layer) .
According to the user profile, the list can be read or read/write. If the user is not
allowed, the Current Value cannot be edited.
OK button is used to validate the selection.
Cancel button closes the dialog without changes of the data.
Help button provides some useful information about the dialog.
Figure 4-5 Set Manager list
Restart ISA (Not operative)

The restart operation is a software restart.
Select the Restart ISA option from the Supervision cascading menu.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-25
CT Operator’s Guide Generic and common functions
............................................................................................................................................................................................................................................................
Generic and common functions

This paragraph and relevant sub-paragraphs describe the generic menu items, common to
all the applications:
• Configuration Î Options
• Views Î Search
• Views Î Print
Options of Configuration menu

This function is accessible by selecting, in the menu bar: Configuration Î Options
An example of the displayed dialog window is reported in Figure 4-7, (pg. 4-28).
These options permit to set some general parameters relevant to the initial default
settlement, graphic interface, etc. A set of tabbed windows is displayed, where each of
them is shown by clicking on the relevant tab (Default Values, Format, Program,
Measurement Units):
• Default Values, i.e. the initial values that the system will automatically assign to some
parameters:
– Traffic Descriptor Name: default TD name
– Protocol Profile: default Protocol Profile name (see Transmission Î EthernetPort
Configuration for details)
– ASAP Name: default ASAP name
• Format, i.e. the format for some parameters:
– Decimal: Dot Separator (“.") or Comma Separator (“,") numerical notation
– Date/Time: Long or Short
• Program, i.e. some parameters relevant to the graphical interface:
– Language: the options are: English (UK), or English (US), or Italian
– Tabular/Graphical Area: it is relevant to the Application Area; the options are:
TabularMode, or GraphicalMode; the GraphicalMode (not operative) is applicable
only in Performance Monitoring (PM)
– Secondary Window Layout: it is relevant to the displayed dialog windows; possible
options: Full window Mode (the dialogs are presented on only one window) or
Tabbed Window Mode (the dialogs are presented on more windows, accessible by
relative tabs), see “Windows Presentation: “FullWindow" and “TabbedWindow"”
(p. 4-28).
– Views Layout: the only option is Tabbed Mode
• Measurement Units:
– Time: possible options: MicroSec or MilliSec
............................................................................................................................................................................................................................................................
4 - 26 P/N 8DG15785AAAA
Generic and common functions CT Operator’s Guide
............................................................................................................................................................................................................................................................
– Size: possible options: Octet

– BitRate: possible options: kbps or Mbps
Figure 4-6 Options of Configuration menu
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-27
............................................................................................................................................................................................................................................................
Windows Presentation: “FullWindow" and “TabbedWindow"

This function is accessible by selecting, in the menu bar: Configuration Î Options and then
clicking on Program tab, SecondaryWindowLayout field.
It is relevant to the displayed dialog windows; possible options: Full window Mode (the
dialogs are presented on only one window) or Tabbed Window Mode (the dialogs are
presented on more windows, accessible by relative tabs). They report the same fields, but
represented in two different manners; see examples on Figure 4-7 and Figure 4-8.
Important! This option is not effective for all the windows.
Figure 4-7 Configuration -> Options - Program (“Full Window Mode" example)
Figure 4-8 Configuration -> Options - Program (“Tabbed Window Mode" example)
Note: All the dialogue windows described in this handbook are

both in FullWindow and in TabbedWindow mode, the information
fields reported in both modes are the same.
Search in Views menu

This function is accessible by selecting, in the menu bar: Views Î Search.
This same dialog is also always recalled by the other applications, when a specific
resource has to be searched and associated to the calling application.
............................................................................................................................................................................................................................................................
4 - 28 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
This function permits to search a resource (or a group of). A set of tabbed windows is
displayed, where each of them is shown by clicking on the relevant tab:
ETS InFlow, ETS OutFlow, Ethernet Port.
The searching can be extended over all the existing resources of that type or restricted to
some particular conditions of that resource (e.g. connected/not connected, in a range, etc.)
by entering other parameters relevant to the resource to be searched; i.e. the searching can
be done also without defining any specific parameter, in this case it will find all the
resources related to the tab window.
The possible parameters for the searching criteria are listed below:
• ETS InFlow as shown in Figure 4-9, (pg. 4-30)
– Status: up / down
– XC Status: Cross Connected / Not Cross Connected
– Service Type: Ethernet
• ETS OutFlow as shown in Figure 4-10, (pg. 4-30)
– XC Status: Cross Connected / Not Cross Connected
– Server Type: Ethernet
• Ethernet Port as shown in Figure 4-11, (pg. 4-31)
– XCEth Port Type: Local / Remote
– Client Type: ets / etb
• Agg Group as shown in Figure 4-12, (pg. 4-31)
– Client Type: ets / etb
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-29
............................................................................................................................................................................................................................................................
Figure 4-9 Views -> Search ETS InFlow
Figure 4-10 Views -> Search ETS OutFlow
............................................................................................................................................................................................................................................................
4 - 30 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-11 Views -> Search Ethernet Port
Figure 4-12 Views -> Search Agg. Group
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-31
............................................................................................................................................................................................................................................................
At the bottom of the window there are the following buttons:

• Create: to create a new search criterion.
• Delete: to delete the selected search criteria.
• Search: to start the searching: at the end of the operation, the search results are tabled
in the window.
• Apply: this key is used when the search has been called by an application, to browse a
resource; by pressing this key the selected resource will be passed to the relevant
application.
• Close: to close the Search window.
• Print: to print the results of the searching. It shows the dialog described in “Print in
Views menu” (p. 4-32).
• Help: to get helps about this function.
Print in Views menu

This function is accessible by selecting, in the menu bar: Views Î Print
An example of the displayed dialog window is reported in Figure 4-13.
This function permits to print the details concerning the list of resources shown in the
Application area of the main view.
The printing can be addressed to a Printer or to a File.
In case of File, the user can browse the desired file by clicking on the key Choose File; the
Output Format of the file can be chosen among Pdf, Html, Postscript, CSV or Ascii types.
This same dialog is also always recalled by the other applications, when the properties
details associated to a resource have to be printed.
Press on Ok to print, on Preview to preview, or on Cancel to leave the dialog without printing.
Figure 4-13 Views -> Print
............................................................................................................................................................................................................................................................
4 - 32 P/N 8DG15785AAAA
Diagnosis and Alarms Configuration CT Operator’s Guide
............................................................................................................................................................................................................................................................
Diagnosis and Alarms Configuration

Alarms indications are always present on the operator's workspace. The different types of
alarms, their number and their severity level are represented in the various views and areas
of the ES-CT (Severity and Domain Alarms Synthesis, Tree-Area, Information-Area,
Alarms Surveillance application, etc. ). The alarms are represented by symbols, or icons,
or texts (depending on the context ), which change color when the relevant alarm is active.
Thus, at any time, the user can know the number of alarms and their severity.
This paragraph and relevant sub-paragraphs describe some operations mainly related to
the associations of the alarms with an appropriate severity for faults diagnosis, and the
activation of Alarms Surveillance. The faults and alarms details and description as well as
their relevant maintenance are reported in the Chapter 5, “Maintenance”.
The following functions are related:
• Alarms Severity Assignment Profile (ASAP) management,
• Alarms re-synchronize,
• Allow/Inhibit alarms notification,
• Restart ISA,
• Alarms Surveillance: ISA alarms
• Alarms Surveillance: Object alarms
• Alarms Surveillance: Transmission alarms
Alarms Severity (ASAP management) in Configuration menu

Managed entities yield alarms when they have some malfunctions. This paragraph deals
with the configuration of ASAPs. An ASAP is a list of Alarm probable causes to which
Severities Profiles are assigned, predefined or settable by the operator.
This option permits to configure (create, modify, etc.) the ASAPs.
This same dialog is also always recalled by the other applications, when the association of
an ASAP to a selected alarm or resource is needed.
Select the Alarms Severities option from the Configuration pull down menu.
The ASAP Management dialogue box is displayed, as follows:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-33
CT Operator’s Guide Diagnosis and Alarms Configuration
............................................................................................................................................................................................................................................................
Figure 4-14 ASAP Management dialogue box.
The default presented profiles are:

• no alarm: all the alarms are disabled (cleared), i.e. they are not displayed by the ES-
CT.
• path alarms: all the alarms are enabled and set to major severity.
• all alarms: all the alarms are enabled and set to minor severity.
The predefined profiles of these default ASAPs are listed in Table 4-1, (pg. 4-37).
By clicking on any of the keys: Details or Create or Modify, a window as that of
Figure 4-15, (pg. 4-35) is displayed (example).
At the bottom of the window shown in Figure 4-14, (pg. 4-34) there are the following
other buttons:
• Delete: to delete the selected ASAP.
• Cancel: to close the window.
• Print: to print the list of ASAPs.
• Ok: this button is not active, because it can be used only to set the Alarm Severity to a
resource, when this dialog is recalled by the relevant resource configuration.
............................................................................................................................................................................................................................................................
4 - 34 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-15 ASAP - Severities profile example
Creating an ASAP
As soon as the previous window shown in Figure 4-14, (pg. 4-34) is presented, only the
Create button is available, therefore, by clicking on this key the window of
Figure 4-15, (pg. 4-35) is displayed and the user can create a new ASAP.
For this purpose follow the following steps:
• ASAP Identifier: fill this field with a name
• Probable Causes Families: the category of alarms can be chosen among:
– Communication or Error Processing or Equipment or Quality Of Service the
choosing of these families is not operative, in current release.
• Probable Cause Name: a list of alarms names belonging to the above selected family,
the meaning of these alarms severities is listed in Table 4-1, (pg. 4-37).;
the relevant severity associated to a selected alarm of the list is shown in the
adjacent field Severity; the other two fields indicate if it is No Service Affecting or
Service Independent (these latter two fields are not operative).
– Severity: this field contains a pull-down list of the possible severities to be
associated to the selected alarm, they are: cleared, major, warning, minor, critical,
indeterminate.
At the bottom of the window there are the following buttons:
• Ok: to confirm the creation of this new asap.
• Cancel: to close the window without doing any operation.
• Print: to print a detail list of this ASAP.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-35
............................................................................................................................................................................................................................................................
Getting details on ASAPs

After selecting a profile in the window of Figure 4-14, (pg. 4-34) and clicking on the
Details key, details about it are given on the displayed ASAP Severity window, the same as
Figure 4-15, (pg. 4-35).
In this case the user can just check the associated severities, by clicking on the alarms
name in the list Probable Cause Name and reading the associated severity in the Severity
field; at the end click on Cancel button to leave the dialogue.
Modifying an ASAP
After selecting a profile in the window of Figure 4-14, (pg. 4-34) and clicking on the
Modify key, the user can modify it, on the displayed ASAP Severity window shown in
Figure 4-15, (pg. 4-35).
In this case the user can change the associated severities, by clicking on the alarms name
in the list Probable Cause Name and then choosing the appropriate severity in the pull-
down list of the Severity field; at the end click on the Ok button to confirm the
modifications.
Setting an ASAP to a resource

The ASAP association to a resource is carried out from the option Configuration... (a
resource), in the Transmission context; e.g.: for an Ethernet-port, select the Transmission
application, then select the relevant Ethernet-port, then, in the pop-up menu, select the
Configure Ethernet Port option; in the presented window, in the Configuration sector there is
the field ASAP Name, where the desired ASAP can be configured: clicking on the [...]
button, the window of Figure 4-14, (pg. 4-34) will be recalled, then select the desired
ASAP and click on Ok button.
............................................................................................................................................................................................................................................................
4 - 36 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Table 4-1 Alarms & Severities association in predefined ASAPs
ASAP_ID: ASAP_ID: ASAP_ID:

ALARM name “no alarm" “path alarms" “all alarms"
LOS (Loss Of Signal) cleared major major
LOF (Loss Of Frame) cleared major major
TSF (Trail Signal Fail) cleared major major
PLM (PayLoad Mismatch) cleared major major
GTM (GFP Type Mismatch) cleared major minor
DEG (SDH Concat. Degrade) cleared minor minor
CSF (Client Signal Failure) cleared major major
LAGD (Lag Degrade) cleared minor minor
LAGL (Lag Loss) cleared major major
TD (Traffic Disabled) cleared major major
Note: “cleared" means that the alarm is not displayed by the ES-
CT. The meaning of the other alarms severities is described in
Chapter 5, “Maintenance”.
Set Alarms Severities

This option permits to send (i.e. to provision) a chosen ASAP to a selected EthernetPort,
or to all the Ethernet Ports of the ES node.
Select the Set Alarm Severities option from the Configuration pull down menu.
The ASAP Enhanced dialogue box is displayed, as for the window shown in
Figure 4-16, (pg. 4-39).
The ASAP currently operative on the selected object (only if EthernetPort) is highlighted,
permitting to check the currently used ASAP.
To set an ASAP, fill fields and areas as follows:
• Select Object: reporting the selected resource
• List of ASAPs sector:
the list reports all the existing ASAP's. One of them can be highlighted, if an
EthernetPort has been selected.
Select one of the listed ASAP's to be provisioned
Detail: it gives details about the selected ASAP, with the same procedure as seen in
“Alarms Severity (ASAP management) in Configuration menu” (p. 4-33).
• Apply to sector:
(active only if an ASAP has been selected in the List of Asap's)
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-37
............................................................................................................................................................................................................................................................
– Choose Scope items:

Selected Object Only: it is active only if an EthernetPort has been selected. If
marked it means that the selected ASAP will be sent only to the selected
object.
ISA Switch: if marked it means that the selected ASAP will be sent to all the
objects of that class (in this case Ethernet Ports) of the node.
Selected Object and Subordin...: not operative.
– Choose Class(es) items:
All Classes: if marked it means that the selected ASAP will be sent to all the
objects and all the classes of the node
Specific Class(es): if marked, it means that the selected ASAP will be set on all
the objects classes listed in the field below (Ethernet Ports).
Choose Current Asap: it applies a filter to provision only the objects that are
associated with the ASAP here indicated (path alarms/all alarms/ignore).
• Execution Monitoring sector:
(it reports the progress counting of the resources as they are provisioned)
Object Processed counter: total number of objects processed
Object Ok counter: number of objects successfully processed
Object Nok counter: number of objects where the Asap could not be changed.
At the bottom of the window there are the following other buttons:
• Ok: to provision the selected ASAP and close the window
• Apply: to provision the selected ASAP without closing the window
• Cancel: to close the window without doing any operation
Note: The ASAP association to a resource can be carried
individually out also from the option Configure (a resource), in the
Transmission context; e.g.: for an Ethernet-port, select the
Transmission application, then select the relevant Ethernet-port,
then, in the pop-up menu, select the Configure Ethernet Port option;
in the presented window, in the Configuration sector there is the field
ASAP Name, where the desired ASAP can be configured (e.g. see
“Configure (local) Ethernet Port” (p. 4-67)).
............................................................................................................................................................................................................................................................
4 - 38 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-16 ASAP: Set Alarm Severities (example)
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-39
............................................................................................................................................................................................................................................................
Loop Back Management in Configuration menu

The Local Ethernet ports support the Internal Loopback function, as described in “Internal
Loop-Back management” (p. 1-53).
This option is recalled from the Configuration pull down menu, selecting the Loop-Back
Management item.
The Loopback Management dialogue box is displayed in Figure 4-17, (pg. 4-40). It
reports the list of all the local ports of the ES node, and, correspondingly, the state of the
Internal LoopBack, that can be enabled (i.e. activated) or disabled. The loopback is
possible only on active ETS local ports containing a Port-to-Port connection. Its enabling
is managed in the option described in “Configure (local) Ethernet Port” (p. 4-67).
Note: The Line Loopback is not supported.
Figure 4-17 Loop Back Management dialogue box
............................................................................................................................................................................................................................................................
4 - 40 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Allow/Inhibit Alarms Notifications

The system provides the possibility to allow/inhibit the spontaneous incoming alarms
notifications on the ES-CT.
a. To inhibit alarm notification,
Select the Supervision pull down menu and then select the Inhibit Notification
option from the Alarms cascading menu.
From the confirmation dialogue box that opens you can confirm or cancel the
operation using the Ok or Cancel push buttons respectively.
To inform the operator that alarms have been inhibited, the labels of the alarm
panel are greyed out, as shown below:
Note: Inhibiting the alarms notification means that they are not
forwarded to the ES-CT, but alarms are still generated by the NE.
b. To allow alarm notification
Select the Supervision pull down menu and then select the Allow Notification option
from the Alarms cascading menu;
Note: This option will be available only after the above described
Inhibit Notification.
From the confirmation dialogue box that opens you can confirm or cancel the
operation using the Ok or Cancel push buttons respectively; after this operation, the
alarms will be displayed and notified again by the ES-CT.
Alarms re-synchronization
The system provides the possibility to recover alarms present on the ES-NE and to update
the current problem list (Alarms Surveillance) of the NE. After this operation, the ES-NE
and the ES-CT current alarms list (Alarms Surveillance) will be consistent.
To re-synchronize the alarms, select the Supervision pull down menu and then select the
Resynchronize option from the Alarms cascading menu.
Alarms Surveillance (Diagnosis - Alarms option)

This paragraph illustrates the access to the Alarms Surveillance application of the ES-CT.
Note: Detailed information about the significance of alarms and
statuses is given in Chapter 5, “Maintenance” of this handbook.
Select the Diagnosis pull down menu and then the Alarms cascading menu; the following
options are offered:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-41
............................................................................................................................................................................................................................................................
• ISA Alarms all the ES alarms are listed in the Alarms Surveillance report which is
activated.
• Object Alarms only the alarms relevant to the selected object are listed in the Alarms
Surveillance report
• Transmission Alarms only the alarms relevant to the Transmission context are listed in
the Alarms Surveillance report.
Selecting one of the above options, the Alarms Surveillance (AS) report is displayed as for
the example of the following figure (this example is relative to ISA Alarms option).
This view shows first a synthesis of the ES-NE alarms (Counter Summary window) with
the sum of all alarms, then a detailed list of alarms of the selected filter (Alarms Sublist).
Figure 4-18 Alarms Surveillance (“ISA Alarms" example)
Detailed information for each alarm is supplied in the Alarm Sublist window.
For example: the resource where the alarm is detected, the status, the type, the probable
cause of the relevant alarm, etc.
The listing of all the Alarms or the filtering of a class of them is also possible.
............................................................................................................................................................................................................................................................
4 - 42 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
The information supplied helps the operator, typically during troubleshooting operation,
presented in next section of this handbook (Chapter 5, “Maintenance” ), where more
details about alarms are given).
Detailed description about this application is given in the AS Operator's Handbook,
listed in Table 1, (pg. 1-xxviii).
Event Log Browser (Diagnosis - Log Retrieval)

This paragraph illustrates the access to the Event Log Browser (ELB) application of the ES-
CT.
Note: More information about the significance of alarms and
statuses is given in Chapter 5, “Maintenance” of this handbook.
Note: Detailed description about the Log application is given in
the ELB Operator's Handbook, listed in Table 1, (pg. 1-xxviii).
Select the Diagnosis pull down menu and then the Log Retrieval cascading menu; the
following options are offered:
• Event all the events related to the selected ES Unit are listed in the log report that will
be activated.
• Alarm all the alarms related to the selected ES Unit are listed in the log report that will
be activated.
Selecting one of the previously seen options, the Event Log Browser (ELB) starts. First of
all it displays a Filter dialog windows, where the user can choose the object and the time
period to be applied to the log report. After completing the filter dialog, the ELB displays
the desired report, where detailed information for each Event or Alarm is supplied.
This information helps the operator typically during troubleshooting operation, presented
in next section of this handbook (Chapter 5, “Maintenance”), where more details about
alarms are given.
• Event: in this case the filter dialog presents an Event Type and an Event Time panels, in
order to choose the filter parameters, as shown in Figure 4-19, (pg. 4-44).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-43
............................................................................................................................................................................................................................................................
Figure 4-19 Log Retrieval -> Event (Filter example)
Click on Filter key and the Event report is then displayed as for Figure 4-20, (pg. 4-44).
Figure 4-20 Log Retrieval -> Event (Report example)
• Alarm: in this case the filter dialog presents an Event Type, an Event Time, a Perceived
Severity and a Probable Cause panels, in order to choose the filter parameters, as
shown in Figure 4-21, (pg. 4-45).
............................................................................................................................................................................................................................................................
4 - 44 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-21 Log Retrieval -> Alarm (Filter example)
• Click on Filter key and the Event report is then displayed as for Figure 4-22, (pg.
4-45).
Figure 4-22 Log Retrieval -> Alarm (Report example)
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-45
............................................................................................................................................................................................................................................................
Navigation to EML-USM in Diagnosis menu

This function allows to navigate to the SDH context of the NE, i.e. to the SDH-Craft
Terminal.
Select, in the menu-bar, the Diagnosis item and then the Navigation Î EMLUSM option.
............................................................................................................................................................................................................................................................
4 - 46 P/N 8DG15785AAAA
MIB Management CT Operator’s Guide
............................................................................................................................................................................................................................................................
MIB Management
This paragraph and relevant sub-paragraphs describe some operations related to the MIB
management; MIB (Management Information Base), i.e. it is the data-base of the ES-NE
configuration.
Backup/Restore DB
This function is accessible by selecting, in the menu bar:
MIB-Management Î Backup/Restore DB.
This function permits to save (backup) the ES-NE configuration and/or to restore it.
The backup (save) can be done writing a name for the current configuration in the field
Backup name (e.g. VIM1) and then clicking on the BackUp key in order to start the backup
that is highlighted by means the info boxes shown in Figure 4-24, (pg. 4-48). After the
backup the list is filled with the relevant name in the Available Backup Files field.
The restore can be done selecting a name in the Available Backup Files field and then
clicking on the Restore key as shown in Figure 4-25, (pg. 4-48).
The restoration function will take some time to finish and during this interval the ES-NE
will not respond to the ES-CT.
Figure 4-23 MIBmanagement Î Backup/Restore DB
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-47
CT Operator’s Guide MIB Management
............................................................................................................................................................................................................................................................
Figure 4-24 Backup info boxes
Figure 4-25 Backup/restore selection
At the bottom of the window there are the following other buttons:
• Delete: to delete the selected backup file.
• Close: to close the window without doing any operation.
Compare two Backup Files

Not operative in current release.
............................................................................................................................................................................................................................................................
4 - 48 P/N 8DG15785AAAA
Transmission CT Operator’s Guide
............................................................................................................................................................................................................................................................
Transmission
The transmission application permits to manage all the parameters related to the
transmission context.
It can be entered by selecting, in the menu-bar: Views Î Transmission, or by clicking on its
relevant tab of the main view.
WARNING
All the dialogue windows described in this handbook are reported in
“FullWindow" mode, the information fields reported in the “TabbedWindow"
mode are the same as described in “Windows Presentation: “FullWindow" and
“TabbedWindow"” (p. 4-28).
Ethernet Ports denomination and numbering

WARNING
The Remote Ethernet Ports are to be configured at the SONET/SDH side, before
their usage, associating them with SONET/SDH containers; the choice of the
SONET/SDH containers should be done according to the rate of the total
forecast data traffic; (SDH-CT option: Configuration Î ISA Port Configuration);
see OMSN Operator's Handbook listed in Table 1, (pg. 1-xxviii) for details
about SDH configuration and connection.
The correspondence of Ports denomination between ES side and SDH side is the
following:
ES-CT context SDH CT context

Local Ethernet Ports: ETHLocPort#n Port Number=n
Remote Ethernet Ports: ETHRemPort#10n Port Number=n
Note: 10n stands for 1000+n

ISA-ES1 board can manage:
• Remote interfaces: 8 RemEthPorts numbered 1001 to 1008 on ES-CT corresponding
to 1 to 8 on SDH-CT;
• Local interfaces: 8 Fast Ethernet LocalEthPorts numbered 9 to 16 on ES-CT (the same
on SDH-CT), they are directly accessible at the 8 apposite connectors on the front
panel of the board (numbered from 1 to 8), the numbering order is from the top to the
down side of the board.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-49
CT Operator’s Guide Transmission
............................................................................................................................................................................................................................................................
ISA-ES4 board can manage:

• Remote interfaces:
– 16 MII RemEthPorts numbered 1001...1016 on ESCT corresponding to 1...16 on
SDH-CT,
or:
– 2 GMII RemEthPorts numbered 1017, 1018 on ESCT corresponding to 17, 18 on
SDH-CT;
WARNING
MII and GMII are mutually exclusive. The choice between them is described in
“GMII - MII Remote Interface Selection (ES4 board only)” (p. 4-60). (For
changing between them, all ports/resources of the board must be in down state).
• Local interfaces:
– 8 Fast Ethernet LocalEthPorts numbered 20 to 27 on ES-CT (the same on SDH-
CT), they are directly accessible at the 8 apposite connectors on the front panel of
the board; the numbering order, 1 to 8, is from the top to the down side of the
board.
– 1 Gigabit Ethernet LocalEthPort numbered 19 on ES-CT (the same on SDH-CT),
accessed directly at the apposite connector on the front panel of the board.
............................................................................................................................................................................................................................................................
4 - 50 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
ETS Traffic Descriptor configuration

This option is obtained by selecting, in the menu-bar:
Configuration Î Traffic Descriptor Î ETS Traffic Descriptor.
The function of this option is to show the existing traffic descriptions related to the ETS
traffic, or to create a new one, to display (or print) the details about a selected one, and also
to delete one of them.
This same dialog is also always recalled by the other Transmission applications, when the
association of a Traffic Descriptor (TD) to the relevant resource is needed.
Figure 4-26 Configuration -> ETS Traffic Descriptor (example)
The parameters listed in Figure 4-26, (pg. 4-51) are:

• Traffic Descriptor Name: name of the traffic descriptor;
• Traffic Type: Traffic codification, according to international standard conventions
(details are given in next “Creating a new ETS Traffic Descriptor” (p. 4-52)).
• CIR: Committed Information Rate;
• PIR: Peak Information Rate;
• CBS: Committed Burst Size;
• PBS: Peak Burst Size.
These latter parameters are explained in “Creating a new ETS Traffic Descriptor”
(p. 4-52).
The keys presented at the bottom of Figure 4-26, (pg. 4-51) are:
• Create (see “Creating a new ETS Traffic Descriptor” (p. 4-52)), Details (see “Getting
details about ETS Traffic Descriptor” (p. 4-54)), Modify (see “Modifying an ETS
Traffic Descriptor” (p. 4-54)): to create a new Traffic Descriptor, or to get details about
or to modify a Traffic Descriptor
• Delete: to delete the selected Traffic Descriptor
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-51
............................................................................................................................................................................................................................................................
• Close: to close the window

• Print: to print details about the selected Traffic Descriptor
WARNING
When this dialog is recalled by a resource configuration, it displays the
additional keys Apply (to associate the selected Traffic Descriptor to the
resource), and Cancel (to exit without TD association).
Creating a new ETS Traffic Descriptor

After clicking on Create key in the panel of Figure 4-26, (pg. 4-51), the following dialogue
is popped-up (example):
Figure 4-27 Create an ETS Traffic Descriptor (example)
Referring to Figure 4-27, (pg. 4-52), fill fields and areas as follows:
• Traffic descriptor Name: insert a traffic descriptor name;
• Traffic Type: identification of the traffic, in terms of international standard
codifications; possible options:
– Best Effort Service
– Guaranteed Service
– Regulated Service
– Regulated Service1 - available only in Bridge Type = bridge 802.1S-AD (Provider)
............................................................................................................................................................................................................................................................
4 - 52 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
– Guaranteed Service2 - available only in Bridge Type = bridge 802.1S-AD

(Provider)
– Back Ground Service - available only in Bridge Type = bridge 802.1S-AD
(Provider)
According to the Traffic Type, the following QoS parameters will be displayed in the
dialog of Figure 4-27, (pg. 4-52):
• CIR: Committed Information Rate; range= 0 to PIR (expressed in kb/sec). It is the
normal medium rate of the data flow (Effective Bandwidth). It is settable only if the
traffic (c) has been selected; in case (a) it is set to 0 by the system; in case (b) it is set
equal to PIR value.
• PIR: Peak Information Rate; range= 64 to physical-line-rate of the relative Port
(expressed in kb/sec). It is the maximum rate up to which the source can transmit for a
short time period.
• CBS: Committed Burst Size (committed number of bytes for which the source may
transmit the PIR); range= 0 to 128 kbytes is settable only if the traffic (c) has been
selected; in case (a) it is set to 0 by the system; in case (b) it is set equal to PBS value.
• PBS: Peak Burst Size (maximum number of bytes for which the source may transmit
the PIR); range= 1 to 128 kbytes. A value greater than the MTU is advisable.
for details about above parameters, see also WARNINGS below.
To confirm the inserted values click on Ok button.
WARNING
In case of Bridge Type = bridge 802.1S-AD (Provider), the RegulatedService (1,
3, and 4) traffic types are scheduled to different priority queues, depending on
the type of PCP decoding mode; see “Traffic Scheduling and Forwarding (ETB
ports, MAC & Virtual Bridge)” (p. 4-57).
WARNING
In case of Provider Bridge, the GuaranteedService and GuaranteedService2
traffic types are scheduled to different priority queues, depending on the type of
PCP decoding mode; see “Traffic Scheduling in Provider Bridge case (ETB
ports)” (p. 4-58).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-53
............................................................................................................................................................................................................................................................
WARNING
In general, the incoming packets are forwarded by the Policer/Scheduler
functions, towards egress ports, marking their dropping precedence in the
following way:
• packets rated below CIR are marked GREEN (high priority)
• packets rated between CIR and PIR are marked YELLOW (medium priority)
• packets rated above PIR are marked RED (red packets are to be discarded)
For more details see also “Traffic Descriptor, Forwarding Priority and Class of
Service” (p. 4-54).
Getting details about ETS Traffic Descriptor

After selecting a Traffic Descriptor and clicking on Details key as for Figure 4-26, (pg.
4-51), a dialogue window similar to Figure 4-27, (pg. 4-52) is popped-up.
The displayed dialog is read-only and gives the actual values of the parameters for the
selected Traffic Descriptor. The meaning of the displayed parameters is described in the
previous “Creating a new ETS Traffic Descriptor” (p. 4-52).
Modifying an ETS Traffic Descriptor

After selecting a Traffic Descriptor and clicking on Modify key as for Figure 4-26, (pg.
4-51), a dialogue as that in Figure 4-27, (pg. 4-52) is popped-up.
The displayed dialog permits to change only the name, in the field Traffic Descriptor
Name.
Associating an ETS Traffic Descriptor to a resource

The Traffic Descriptor association to a resource is carried out from the options Configure
or Modify... (a resource), in the Transmission context; e.g.: for an InFlow Point, select the
Transmission application, then select the relevant InFlow Point, then, in the pop-up menu,
select the Modify InFlow option; in the presented window there is the field Traffic
Descriptor, where the desired TD can be configured: clicking on the [...] button, the
window of Figure 4-26, (pg. 4-51) will be recalled, then select the desired TD and click on
Apply button.
Traffic Descriptor, Forwarding Priority and Class of Service

The prioritization of an Ethernet data flow can be indicated on the 3 “VLAN-user-priority"
bits (802.1p) of the Tagged-Ethernet frame and also on the 3 “stacked-priority" bits of the
Stacked-Vlan frame; (see frames formats in “Ethernet Technique” (p. 1-18)).
8 levels of User-priority can be defined: pri0 ... to pri7, where pri0 is the minimum and
pri7 the maximum. The relayed frames towards a generic Provider-Network (only using
ETB port types) can be “prioritized" using the DefaultUserPriority (i.e. incoming
............................................................................................................................................................................................................................................................
4 - 54 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
frames, “untagged”, without priority information are forwarded with a unique priority
value) or RegeneratedUserPriority (i.e. on “tagged” frames, incoming priority values are
mapped versus outgoing priorities by using a configurable priority table), as described in
“Regenerated User Priority for the BridgePort” (p. 4-134) and “” (p. 4-135) (in case
Bridge Type = bridge 802.1D (MAC), the Default User Priority is possible only).
The Priority bits, on the S-VLAN frames (available only in Bridge Type = bridge 802.1S-
AD (Provider)), are called PCP (Priority Code Point). The use of the PCP field is
described in “Traffic Scheduling in Provider Bridge case (ETB ports)” (p. 4-58).
In Provider Bridge case, the Prioritization and Classification modes on ETS ports are
managed by means of the options Create ETS Inflow ( “Create ETS InFlow for an Ethernet
Port” (p. 4-100)) and Create ETS Outflow ( “Create ETS OutFlow for an Ethernet Port”
(p. 4-103)) (see also “Create Provider InFlow for an Ethernet Port” (p. 4-112) and “Create
Provider OutFlow for an Ethernet Port” (p. 4-115)). In these resources, the frames can
have 8 levels of priority, and each priority can be colored (by means of the Color Profile)
in “green” or “yellow” or “red”, by means of which the scheduler, in case of traffic
congestion, can choose the packets to be discarded, checking their prioritization and
coloration. In case of congestion, first lower priorities and (in ascending order) red, yellow
or green packets are dropped away.
Note: This priority is coded on VLAN (802.1p) field.
The policing is a mechanism to check that the data flow is respecting the traffic contract,
providing to “cut" or to forward the incoming traffic.
– Disabled means that no policing is carried out.
– Color-Blind means that the policing is based upon the Traffic Descriptor (TD),
without taking into account the Priority or CoS (Class of Service).
– Color-Aware means that the policing takes into account the Traffic Descriptor
(TD), and the User Priority or CoS, that is mapped into three colors (“Color
Profile”); this option is possible only with Traffic Descriptor = Regulated (see
Table , (pg. 4-255)).
According to the traffic contract, to the policing mode, to the Color Profile and to the
available bandwidth, the forwarding of the frames into the Provider-network is decided by
the traffic scheduler of the system.
In case that the policing is in “color-aware" mode, the Provider-prioritization granularity
is made deeper, taking into account the single VLAN-priorities, that can have assigned to
any of them a green or yellow or red color. “green" colour is used for frames to be passed
in any case, “yellow" colour is used for frames to be passed if the band is available, “red"
colour is used for frames to be discarded (in cases that no more band is available); the
color mapping is done by means of the Color Profile in the EtsInFlows resources.
The scheduling is a mechanism to manage the traffic congestions. It uses the shaping and
the queueing functions.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-55
............................................................................................................................................................................................................................................................
The queueing configuration modification is allowed only for Bridge Type = bridge
802.1S-AD (Provider), on ETB ports (see “Traffic Scheduling in Provider Bridge case
(ETB ports)” (p. 4-58)). In case of Bridge Type = bridge 802.1D (MAC) or bridge 802.1Q
(Virtual ), the Queueing is fixed by default, into three queues, as indicated in “Traffic
Scheduling and Forwarding (ETB ports, MAC & Virtual Bridge)” (p. 4-57).
• The shaping provides to adapt the incoming traffic to the available output bandwidth,
by smoothing prospective peaks. It is configured by means of two parameters:
– mean shaping rate: output rate (in kb/s) at which the incoming traffic can be
moulded.
– burst shaping rate: amount of burst incoming traffic (in bytes) that can be
moulded.
Note: The egress shaping is allowed also on ETS ports.
• The queueing provides to identify the CoS (Priority bits) of the incoming frames and
to line them into different queues that can be served with higher or lower priority by
the scheduler.
Several queues are provided, each queue devoted to one or more types of traffic. The
packets queued can then be forwarded towards the output in different modes,
depending on their Class of Service:
– Strict Priority (SP): The highest priority queue is forwarded firstly; once it is
emptied, the forwarding action passes to the lower queue, and so on.
– WDRR Bandwidth: (Weighted Deficit Round Robin); each queue is associated to a
deficit counter (DC), whose value is proportional to a settable weight. The queues
are served in rotational mode, starting from the higher value of the DC counter; the
DC is then decremented by the size of the forwarded frame; when the frame size
becomes bigger than the DC value, the forwarding action passes to the queue with
higher DC, and so on. At the end of the round, the DC counters are restored to their
values. This mode can be:
– WorkConserving: empty queues are skipped
– NonWorkConserving: (not available in current release); empty queues are
served too.
the Weight of a queue is settable by means of the option Configure Queue, see
“Configure Queue for the Ethernet Port” (p. 4-150).
Only for Bridge Type = bridge 802.1S-AD (Provider), the PCP scheduling mode can be
set in two different modes: 5P3D or 8P0D, by using the option Configure ISA, “Configure
ISA” (p. 4-62). The various PCP scheduling modes are illustrated in “Traffic Scheduling
and Forwarding (ETB ports, MAC & Virtual Bridge)” (p. 4-57) and “Traffic Scheduling in
Provider Bridge case (ETB ports)” (p. 4-58).
............................................................................................................................................................................................................................................................
4 - 56 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Traffic Scheduling and Forwarding (ETB ports, MAC & Virtual Bridge)
Figure 4-28 ETB Virtual/MAC Bridge Scheduling Mode
IN SCHEDULER OUT
BPDU (pr. BPDU)

Queue 3
Regen. Guar.
Ingress Prior. Queue 2 Shaping Egress
or (pr. 7,6) (pr.7, 6) SP ETBPort
ETBPort Decod
frames Default
Prior. Regul. Queue 1
(pr. 5,4) (pr. 5,4)
BestEffort
Queue 0 (pr. 3,2,1,0)
(pr. 3,2,1,0)
DROP
Note:
Regenerated Priority is used only in VirtualBridge and on “Priority Tagged” frames
BPDU frames are always forwarded, also in case of threshold exceeded
Network Control frames are sent into the same Queue of BPDU
The “drop” (discarding) of packets is done in case of congestion; lower priority packets are dropped first
“Queue2” is called “High Priority”, “Queue1” is called “Medium Priority”, “Queue0” is called “Low Priority”
SP: Strict Priority, highest priority queue is emptied first
In MAC bridge, the scheduling can be regulated by using the Default Priority
On EtsPorts, the scheduling is not performed, since only Port-to-Port connections are permitted, in transparent mode
“Silver Service" traffic is relayed, by the traffic scheduler and policer of the system, if the
band on the link is available.
“Gold Service" traffic is relayed, as regarding the CIR, but the exceeding traffic (PIR) can
be discarded.
All the “Network Service" traffic is relayed, as regarding either CIR and PIR values.
The User Priority can be configured in Local and Remote ETB ports (Configure Bridge
Port option), as described in “Regenerated User Priority for the BridgePort” (p. 4-134)
and “” (p. 4-135).
The Table 4-2, (pg. 4-57). shows the typical association between TD, User Priority (UP)
and Provider Class of Service (P-CoS), for ETB ports in MAC and Virtual Bridges.
Table 4-2 Typical association between TD, UP and P-CoS (ETB ports MAC/Virtual
Bridge
ETS Traffic Descriptor User Priority (802.1p) Provider-Class of Service

BEST EFFORT 0, 1, 2, 3 Silver Service
REGULATED 4, 5 Gold Service
GUARANTEED 6, 7 Network Service
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-57
............................................................................................................................................................................................................................................................
Traffic Scheduling in Provider Bridge case (ETB ports)
Table 4-3 Provider Bridge - Traffic Scheduling in 5P3D mode (ETB ports)
In-Pri Traffic Type DP Queue Queue-Type Out-Pri

7 Guar. BPDU Green Q3 SP 7
6 Guar. 2 Green Q2 SP 6
5 Regul. Green Q1 WDRR 5
4 Regul. Yellow Q1 WDRR 5
3 Regul. 4 Green Q1 WDRR 5
2 Regul. 4 Yellow Q1 WDRR 5
1 BestEffort Green Q0 WDRR 0
0 BestEffort Yellow Q0 WDRR 0
Note: DP (Discarding Priority) column indicates the colour

attributed by the scheduler to the frames, meaning that green
frames must be forwarded, and that yellow frames can be
forwarded or discarded, depending on the bandwidth resources.
Figure 4-29 5P3D Scheduling Mode (ETB ports)

IN SCHEDULER OUT
Guar. (pr. 7)
(pr. 7) Queue 3
(pr. 6) SP
Guar.2
Queue 2
(pr. 6)
Regul. (pr. 5)
Queue 1
(pr. 5,4,3,2)
BestEffort WDRR
Queue 0
(pr. 1,0) (pr. 0)
Shaping + EtbPorts
EtbPorts + Default/RegenPrio
Notes:
Regenerated Priority is used on “Priority Tagged” frames
On EtsPorts, the scheduling is carried out using this same schema, if Statically or Dynamically connected by means of FDB feature
On EtsPorts, the scheduling is driven by the TD and 8 priorities and 3 colors for each priority of the inner “VLAN-Tag”
as set in EtsInflow and in EtsClassifier (when connected by means of UNI-UNI,UNI-NNI, etc. Connections).
The shaping is possible on EtsPorts too.
............................................................................................................................................................................................................................................................
4 - 58 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Table 4-4 Provider Bridge - Traffic Scheduling in 8P0D mode (ETB ports)
In-Pri Traffic Type DP Queue Queue Type Out-Pri

7 Guar. BPDU Q3 SP 7
6 Guar. 2 Q2 SP 6
5 Regul. 1 Q1 WDRR 4
4 Regul. Q1 WDRR 4
Green
1 BackGround Q0 WDRR 0
0 BestEffort Q0 WDRR 0
Figure 4-30 8P0D Scheduling Mode (ETB ports)
IN SCHEDULER OUT
Guar. (pr. 7)
(pr. 7) Queue 3
(pr. 6) SP
Guar.2
Queue 2
(pr. 6)
Regul. (pr. 4)
Queue 1
(pr. 5,4,3,2)
BE - BG WDRR
Queue 0
(pr. 1,0) (pr. 0)
Shaping + EtbPorts
EtbPorts + Default/RegenPrio
Notes:
Regenerated Priority is used on “Priority Tagged” frames
On EtsPorts, the scheduling is carried out using this same schema, if Statically or Dynamically connected by means of FDB feature
On EtsPorts, the scheduling is driven by the TD and 8 priorities and 3 colors for each priority of the inner “VLAN-Tag”
as set in EtsInflow and in EtsClassifier (when connected by means of UNI-UNI, UNI-NNI, etc. Connections).
The shaping is possible on EtsPorts too.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-59
............................................................................................................................................................................................................................................................
GMII - MII Remote Interface Selection (ES4 board only)

Only for ES4 board. This option is automatically displayed, on insertion of an ISA-ES4
board into the equipment (only if the board is new or un-configured).
WARNING
This selection must be congruent with the board setting performed on SDH-CT.
WARNING
For changing between MII/GMII options, all ports/resources of the board must
be in down state.
If the board has been already used for one option and it must be changed, it can
be done in various modes:
1. by doing a MIB-reset of the flash-card on board (see “ISA-ES Units
replacement” (p. 5-18)), and then re-equipping the board on SDH side and
ES side.
2. by storing a MIB after MIB-reset and then restoring this MIB-reset when a
MII/GMII is necessary (see “MIB Management” (p. 4-47) options).
3. by setting all ports/resources of the board to down state.
In all cases, the configuration on SDH side must be congruent.
The function of this option is to select, on ES4 board, the type of remote interfaces used
towards SDH network.
• MII case (Media Independent Interface):
16 remote ports are available, numbered 1001 to 1016, with the following limitations,
in Virtual Concatenation mode:
– VC12 case: max 50 VC12 concatenated containers
– VC4 case: not applicable
• GMII case (Gigabit Media Independent Interface):
2 remote ports are available, numbered 1017 and 1018, with the following limitations,
in Virtual Concatenation mode:
............................................................................................................................................................................................................................................................
4 - 60 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
To configure the remote interface click on MII or GMII box and then on Ok.
WARNING
The interface type must be congruent with that one equipped in SdhCT side (by
means of the Equipment Î Set... menu option).
After this configuration, the usable or not-usable state of the ports will be displayed in the
Resource-Tree by the following symbols:
• ETHERNET port (configurable):
• ETHERNET port (in not usable state, not configurable):
Figure 4-31 MII or GMII interface selection
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-61
............................................................................................................................................................................................................................................................
Configure ISA
This option is obtained, after selecting the ISA-ES ( ), by means of the contextual
pop-up menu, or by selecting in the menu-bar:
Transmission Î ISA Management Î Configure ISA.
An example of the displayed dialog windows are reported from Figure 4-32, (pg. 4-62) to
Figure 4-35, (pg. 4-64)
WARNING
The de-activation of every underlying resource (Ethernet Ports, InFlows,
OutFlows, etc.) is necessary, before swapping from one Bridge Type to another.
The function of this option is to manage the transmission parameters of the selected ISA-
ES node.
To configure the ISA-ES node, fill fields and areas as follows:
• System Info sector:
• System Location: indicating where the ISA-ES is placed (read only field)
• Up Time: incremental time since the node was started up (read only field)
• Mgmt IP Address: indicating the assigned IP address (read only field)
• Software Version: it is relevant to the SW downloaded into the NE (read only field).
The meaning of the V0300xy field is the following;
– V0300: 3.0 SW version
– xy: maintenance edition relevant to 3.0 SW version
Figure 4-32 Configure ISA - System Info
• Bridge Management sector:

• Bridge Type: (see WARNING below); possible pull-down options:
– bridge 802.1d: for MAC bridge functions
– bridge 802.1Q: for Virtual bridge functions
– bridge 802.1S-AD: for Provider bridge functions
............................................................................................................................................................................................................................................................
4 - 62 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
WARNING
The de-activation of every underlying resource (Ethernet Ports, InFlows,
OutFlows, etc.) is necessary, before swapping from one Bridge Type to another.
• Protocol Type: possible pull-down options:
– STP: for simple Spanning Tree Protocol functions
– RSTP: for Rapid Spanning Tree Protocol functions
– RSTP+: for enhanced RSTP functions (not operative)
– PERVLANSTP: for “per-VLAN" Spanning Tree Protocol functions; this option
is not available in “MAC-Bridge" case.
– MSTP: for “Multiple" Spanning Tree Protocol functions; this option is not
available in “MAC-Bridge" case.
– manualDisable: to disable the Spanning Tree Protocol functions.
• PB Profile: (displayed only in case of Provider Bridge); to define the traffic
scheduling modality, encoded into the PCP bits (Priority Code Point) of the S-
VLAN; possible pull-down options:
– 8P0D: see details in “Traffic Descriptor, Forwarding Priority and Class of
Service” (p. 4-54),
– 5P3D: see details in “Traffic Descriptor, Forwarding Priority and Class of
Service” (p. 4-54). See also “Configure Queue for the Ethernet Port”
(p. 4-150).
Figure 4-33 Configure ISA - Bridge Management
• MIB Default Value sector:

• Asap Severity: this field associates, among those reported in the pull-down menu, a
severity to the alarm on violating the default values.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-63
............................................................................................................................................................................................................................................................
Figure 4-34 Configure ISA - MIB Default Value
• MTU/MRU sector:
The MTU/MRU field establishes the “maximum transmit unit” and the “maximum
receive unit” (MTU/MRU), i.e. the maximum size of ethernet packets that can be
received/transmitted by the board. This value will be applied to all ports of the board.
Its value must be in the range from 1518 to 2026.
WARNING
MTU/MRU values will be applied only on the Remote Ports of the board. Local
Ports will not filter frames with Mtu/Mru sizes different than this one (larger or
smaller).
Figure 4-35 Configure ISA - MTU/MRU
ISA Properties
This option is obtained, after selecting the ISA-ES node ( ), by means of the
Transmission Î ISA Management Î ISA Properties.
An example of the window displayed is reported in Figure 4-36, (pg. 4-65).
The function of this option is to show the transmission parameters set for the selected ISA-
ES node.
All the reported information fields are read-only, and are the same as those explained ones
for “Configure ISA” (p. 4-62).
............................................................................................................................................................................................................................................................
4 - 64 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-36 ISA Properties
ISA application table in the Transmission context

An example of Application Table associated to the ISA-ES node is illustrated in
Figure 4-37, (pg. 4-66). It is displayed in the area A2, after selecting the ISA-ES node in
the resource-tree. It reports, in tabular form, the resources of the selected ISA-ES node.
The table contains two folders: “Local Ethernet Ports", “Remote Ethernet Ports" .
• Local Ethernet Ports lists the main parameters related to this topic:
“Alarms Synthesis", “Name", “Total Bandwidth (indicated by the supporting pipe)",
“Oper. Status", “Administration Status".
• Remote Ethernet Ports lists the main parameters related to this topic:
“Alarms Synthesis", “Name", “Total Bandwidth (indicated by the supporting pipe)",
“Oper. Status", “Physical Type", “Administration Status".
The properties of a resource of the table are displayed in the information area (A3), after
selecting a row of the table.
A pop-up menu, related to the selected resource, can be activated, after selecting an item
of the table and pressing the right button of the mouse.
The listed parameters, the displayed properties and the options of the pop-up menu are
described in the successive paragraphs.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-65
............................................................................................................................................................................................................................................................
Figure 4-37 ISA-ES node: transmission application table
............................................................................................................................................................................................................................................................
4 - 66 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Configure (local) Ethernet Port

This option is obtained, after selecting a LOCAL EthernetPort ( ), by means of the
An example of the window displayed (in TabbedWindow mode) is reported in
Figure 4-38, (pg. 4-70) to Figure 4-42, (pg. 4-76).
The function of this option is to manage the transmission parameters of the selected local
EthernetPort.
The board ISA-ES1 supports:
• 8 Fast Ethernet LocalEthPorts, numbered 9 to 16 on ES-CT (the same on SDH-CT),
they are directly accessible at the 8 apposite connectors on the front panel of the board;
the numbering order (1 to 8) is from the top to the down side of the board.
• 8 Fast Ethernet LocalEthPorts numbered 20 to 27 on ES-CT (the same on SDH-
CT), they are directly accessible at the 8 apposite connectors on the front panel of the
board; the numbering order (1 to 8) is from the top to the down side of the board.
• 1 Gigabit Ethernet LocalEthPort numbered 19 on ES-CT (the same on SDH-CT),
accessed directly at the apposite connector on the front panel of the board.
To configure a local Ethernet Port, fill fields and areas as follows:
• Configuration sector:
Ref. to Figure 4-38, (pg. 4-70).
• Name: indicating the name assigned by the system to the Port (read only field)
• Type: indicating the type of port (read only field, fixed to ethernetCsmacd)
• Underlying Layer: associated layer (read only field, in this case fixed to mau)
• Last Change: the value of System Time when the port entered its current operational
state
• MTU: Maximum Transmit Unit; size of the largest packet which can be
sent/received on the interface, specified in octets (read only field, fixed by means
of “Configure ISA” (p. 4-62)).
• Connector: (true/false) indicating if the interface has a physical connector (read
only field)
• MAC Address: address of the selected ethernet port (logical address set by the
system)
• Discard Errored Frames: indicating whether errored frames are to be discarded (read
only field, set by the system= true)
• Client Type: (read only field, set by means of “Substitute Client Layer for an
Ethernet Port or an Aggregator” (p. 4-116)), indicating the transported layer:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-67
............................................................................................................................................................................................................................................................
– ets: for Ethernet Transparent System

– etb: for Ethernet Bridge System
– LinkAgg: for Link Aggregation utilization
• Ets Service Type: (read only field, settable by means of “Characterization Service of
an Ethernet Port” (p. 4-93), indicating the Ethernet Service configuration for an
Ethernet Port with Ets as Client Type:
– other: (default value) in this case supports a generic ETS-flow based Ethernet
service with any InFlow Service Type value and any OutFlow Server Type
value
– portToPort: in this case supports a Port-to-Port Service with Ethernet as
Service Type of unique admitted InFlow and Ethernet as Server Type of unique
admitted OutFlow
– EtsVirtSw: (not supprted in current release) in this case supports a 2-Ports ETS
Virtual Switch service with Ethernet as unique admitted InFlow Service Type
and unique admitted OutFlow Server Type.
• Ets Egress Port (Peer): (read only field), set after that a “port-to-port” XC has been
created (in Connection context):
– none: in this case the port is not connected, or used for UNI-Bridged
connections
– ETH...port#...: indicating the name of Peer port connected in PortToPort.
• Traffic Enabled: (read only field, settable by means of “Traffic Management of an
Ethernet Port” (p. 4-93)), indicating if the traffic afferent to this port is Up or
Down.
• Limited Dcn Traffic: the value of this attribute can be expressed in bit/second or
kbit/second, according to product type. When it is equal to Effective Line Rate (i.e.
ELR) of the Ethernet Port, it means that the limitation for Dcn traffic is disabled.
Important! This parameter is available for Bridge Type = bridge
802.1S-AD (Provider) and bridge 802.1Q (Virtual) (ref. to
“Configure ISA” (p. 4-62)).
• Admin. Status: Administration status, possible pull-down options:
– up: to set the port in-service
– down: to set the port out-of-service
• Oper. Status: operational status, (read only field, set by the system) possible
options:
– up: the port is available
– down: the port is unavailable
• Bandwidth: max band capacity offered by the associated underlying physical
channel (read only field, set by the system); possible pull-down options:
............................................................................................................................................................................................................................................................
4 - 68 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
– 10BaseT: 10 Mb/s (for E, 10M Ethernet I/F)

– 100BaseT: 100 Mb/s (for FE, 100M Ethernet I/F)
– 1000Base: 1Gb/s (for 1GE, 1GigaEthernet I/F)
• Alias: friendly name for the interface that can be specified by the user
• Link Up Down Trap: indicating whether linkUp / linkDown traps (notification upon
the changing of the node operational state from up to down and vice versa) should
be generated for this interface; possible options: enabled / disabled .
• Promiscuous Mode: indicating whether this interface has to inspect the MAC
addresses; possible options:
– enabled: the MAC frames are accepted regardless of their MAC addresses
– disabled (not available): the MAC frames addresses are inspected before their
acceptance, in order that only frames addressed to this port can be seen
• Encaps. Method: method of MAC packets encapsulation inside the underlying
physical layer; possible options:
– ethernetV2: default mode, set by the system
– IEEE8023: not yet operative
• Asap Name: name of alarms profile to be associated to the current Port:
the key permits to choose and associate an asap to this resource, recalling the
dialogue described in “Alarms Severity (ASAP management) in Configuration
menu” (p. 4-33)
the key gives the asap properties currently associated to this resource
• Protocol Profile: name of the 2-bytes provider VLAN-protocol-tag (PT) to be
“pushed" into the ethernet frame of data flows afferent to the current Port.
Important! It is settable only if the port is in down state, and
Bridge Type = bridge 802.1S-AD (Provider).
the key permits to choose and associate a provider protocol-tag (PT) to this
resource, recalling the dialogue described in “Create Protocol Profile” (p. 4-76)
the key gives the Prot.-tag properties currently associated to this resource.
• Access Control List: (read only field, settable by means “Configure ACL for an
Ethernet Port” (p. 4-94)), indicating the ACL profile associated to this Port;
reporting the rules for the acceptance of incoming MAC ethernet frames.
• Broadcast Traffic: allows to select the broadcast traffic transmit capability of an
egress interface as a result of explicit management action. Possible values:
– true (default value) indicates the interface is enabled to transmit broadcast
traffic,
– false value indicates the interface is denied to transmit broadcast traffic.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-69
............................................................................................................................................................................................................................................................
• Unknown Traffic: allows to select the unknown traffic transmit capability of an

egress interface as a result of explicit management action. Possible values:
– true (default value) indicates the interface is enabled to transmit unknown
traffic,
– false value indicates the interface is denied to transmit unknown traffic.
• Flooding Rate: it permits the insert a possible bandwidth rate to keep under control
the broadcast and multicast traffic; when this feature is disabled the value of the
flooding rate is equal to value of if-speed and it is default value too.
Figure 4-38 Configure (local) Ethernet Port - Configuration
• MAU sector (ref. to Figure 4-39, (pg. 4-73):

• MAU Identifier: assigned by the system (read only field, fixed to “1")
• Front Panel Port: assigned by the system; identifier of the MAU connector, located
in front of the board, that is associated to this port; possible values are: (1 to 8 for
ES1), (for ES4: 1 to 9, 1 is used for GE i/f, 2 to 9 for FE i/f)
• Type: symbolic name of the mau interface
............................................................................................................................................................................................................................................................
4 - 70 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• Status: mau current status (read only field), possible pull-down options:
operational / shutdown (state of the Transmit i/f)
• Media Available: (read only field); medium availability; options: available or not
available or other.
• Default Pause: pause signal that is inserted in the Flow Control signalling. It applies
only in the case that the AutoNegotiation-AdminStatus is in disabled state (see
below).
– disabled: to disable the Flow Control function
– asymmetric: to enable the Flow Control function, Asymmetric mode: i.e. Pause
Frames are transmitted but not received.
– symmetric: to enable the Flow Control function, Symmetric mode: i.e. Pause
Frames are transmitted and received.
Note: Some details about AutoNegotiation and Flow Control are
reported in “Auto-Negotiation management” (p. 1-58) and “Flow-
Control management” (p. 1-59).
• Jack Type List: (read only field) list of available connectors types. Possible values
are: RJ45 for FE port, FiberLC for GbE port.
• Conf. Remote Client: possible options: disabled/shutdown; if shutdown is selected,
then the Tx i/f (towards the Ethernet line) of this Local Port will be set in
“ShutDown" state, in case of CSF alarm detection on the remote port connected to
this port. The shut-down mechanism is illustrated in “Internal Loop-Back
management” (p. 1-53) and “CSF alarm management” (p. 1-54).
Note: The shut-down mechanism is supported only in Port2Port
Connection.
• Jabber State: (read only field); state of the jabber process (checking about
abnormal data transmissions longer than the max permissible packet length
(MTU/MRU))
• Default Type: possible pull-down options:
– 10BaseTFD: 10Mbps i/f (10-FE)
– 100BaseTXFD: 100Mbps i/f (100-FE)
– 1000BaseXFD: 1000Mbps i/f (GE)
– 1000BaseSXFD: 1000Mbps i/f (GE)
• Type List: list of available interfaces types
• Auto Neg. Support: read-only, indicating (true/false) if the auto-negotiation is
supported; possible values: true / false.
• Loop-Back sub-sector:
• Internal Loop-Back: possible pull-down options:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-71
............................................................................................................................................................................................................................................................
Note: The loopback is possible only if a P2P (Port-to-Port)

Connection is already existing, on this port;
– enabled: the internal LB (from Remote Port-Rx to Remote Port-Tx) is enabled
(for more details see “Internal Loop-Back management” (p. 1-53))
– disabled: Loopback disabling
• Auto Negotiation sub-sector:
Note: Some details about AutoNegotiation and Flow Control are
reported in “Auto-Negotiation management” (p. 1-58) and “Flow-
Control management” (p. 1-59).
Note: AutoNeg. on optical 1Gbps interfaces is available only on
ES4N-enhanced board).
– enabled: auto-neg. enabling
– disabled: auto-neg. disabling
• Remote Signalling: notification about the detection of auto-neg. remote signalling
• Process Status: current status of the auto-negotiation process
• Restart: possible buttons:
– Autonegotiation Restart: to restart the procedure of link re-negotiation
– Refresh: to refresh the actual values of the link negotiation
– Apply All: to apply the last configured parameters of the link auto-negotiation
• Local Capability Options: used for Flow Control enabling, when the
AutoNegotiation is active. If the AutoNeg is disabled, then the above parameter
DefaultPause is instead considered. It contains two fields: Available and Current,
set of capabilities advertised by the local auto-negotiation for Flow Control
signalling (FC):
Flow Control enabling:
– for 100Mbps case, Asymmetric FC:
select, in Local Capability Options, in the available field, the following 3
items: b100baseTXFD, bFdxAPause and bFdxPause.
– for 100Mbps case, Symmetric FC:
select, in Local Capability Options, in the available field, the following 3
items: b100baseTXFD, bFdxSPause and bFdxPause.
select: b10baseTFD, bFdxAPause and bFdxPause.
select: b10baseTFD, bFdxSPause and bFdxPause.
............................................................................................................................................................................................................................................................
4 - 72 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................

select: b1000baseXFD, bFdxAPause and bFdxPause.
select: b1000baseXFD, bFdxSPause and bFdxPause.
Note: In occurrence of Flow Control enabled, the traffic Policing
should be disabled. Flow Control disabling: select, in Local
Capability Options, in the available field, only the following one
item: b100baseTXFD (100Mbps case). In case of 10Mbps:
b10baseTFD. In case of 1000Mbps: b1000baseXFD.
• Autonegotiation Result: reporting the AN results (read only field).
• Remote Capability Options: containing the field: Available; set of capabilities
received from the remote auto-negotiation entity (read only field).
Figure 4-39 Configure (local) Ethernet Port - MAU
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-73
............................................................................................................................................................................................................................................................
• L2 Control Frame sector ( ref. to Figure 4-40, (pg. 4-74)): (not displayed in case of ETB
port) it permits to enable or disable the Protocol Frames that can accede to this port:
• Protocol List: it reports all the available Protocol frames (Bit Name), and,
correspondingly, its Status. The Status can be changed by means of the apposite
pull-down menu that is activated by clicking on it; possible values:
– enabled means that the relative frame protocol is accepted by the Port.
– disabled means that the relative frame protocol is rejected by the Port.
For detailed description of items in the Bit name column, refer to “Protocols” (p. 1-31).
Figure 4-40 Configure (local) Ethernet Port - L2 Control Frame
............................................................................................................................................................................................................................................................
4 - 74 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• Port Mirroring sector:

Ref. to Figure 4-41, (pg. 4-75). It permits to create a copy of the traffic afferent over an
active, in service port, sending the copy of that traffic to this selected port.
WARNING
Before to change the Mirroring type setting, it is mandatory to set the Admin.
Status: option in “down” state in the “Configuration sector:” (p. 4-67).
Some details about this feature are reported in “Port Mirroring management” (p. 1-62).
By means of the following parameters:
• Mirroring Type: possible values:
– No Mirroring: to disable the mirroring
– Mirroring Port Output: to choose the mirroring of the Transmit traffic on
relevant port
– Mirroring Port Input: to choose the mirroring of the Receive traffic on relevant
port
• Selected Port: to choose the Port to be mirrored. It opens a search window as
described in “Search in Views menu” (p. 4-28). Ports to be mirrored must be active
and in service.
Figure 4-41 Configure (local) Ethernet Port - Port Mirroring
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-75
............................................................................................................................................................................................................................................................
• Alarms sector (ref. to Figure 4-42, (pg. 4-76)):

This group reports the alarms relevant to the EthernetPort; their color is green if not-
alarmed, if alarmed their color will be congruent with the severity assigned in the
associated ASAP; the alarms colors are described in Chapter 5, “Maintenance”.
Figure 4-42 Configure (local) Ethernet Port - Alarms
After setting all the desired parameters, click on the Ok key to send the chosen parameters
to the EthernetPort. The window will be closed without doing any operation by clicking on
Cancel key.
The Help key gives helps about this function.
Create Protocol Profile

This option is obtained, in the Configure Ethernet Port window shown in Figure 4-38, (pg.
4-70), after clicking on the key of the ProtocolProfile item.
............................................................................................................................................................................................................................................................
4 - 76 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
The function of this option is to manage the Protocol Profiles to be associated to the
Ethernet Ports resources. The ProtocolProfile defines the protocol-type (PT) contained
into the 2-bytes field of the customer VLAN shim header (802.1Q field, default value=
hex“0x8100"), see frame format in Figure 1-22, (pg. 1-33).
It reports the list of the existing Protocol Profiles, with relevant value in hex code.
Furthermore it contains:
• the Create button, permitting to create a new ProtocolProfile as explained below;
• the Details button, permitting to see the properties of an existing ProtocolProfile;
• the Modify button, permitting to change the name of an existing ProtocolProfile;
• the Delete button, permitting to delete an existing ProtocolProfile;
• the Apply button, permitting “to bind" the selected ProtocolProfile to the related port;
• the Cancel button, permitting to close the window without associating a
ProtocolProfile;
• the Print button, permitting to print the properties of a selected ProtocolProfile;
• the Help button, permitting to have information about this current function.
Figure 4-43 List of Protocol Profile
To create a ProtocolProfile, click on Create key as shown in Figure 4-43, (pg. 4-77) and
then the dialog box indicated in Figure 4-44, (pg. 4-78) will be displayed; fill fields and
areas as follows:
• Protocol Profile Name: type a mnemonic name
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-77
............................................................................................................................................................................................................................................................
• Value (HEX): type an hexadecimal value for the provider protocol-type (PT) that is
inserted into the 2-bytes field of the VLAN shim header (802.1Q field); the value
identifies the customer and has to be 2-bytes long in hexadecimal notation; the third
non-included byte is forced by default to “0x".
The PT is used to recognize the type of afferent Vlan frames, i.e. if they are “S-Vlan-
tagged” or others; by default, an hex value of 88A8 is interpreted as S-Vlan tagged.
Frames with PT value different than this will be treated as non-SVlan-tagged.
An hex value of 8100 is interpreted as Q-Vlan tagged.
Other values of PT will be interpreted as generic Stacked-Vlan frames, used to
interwork among different network providers.
Incoming frames with PT values different from the one associated to a port will be
discarded.
– click on the Ok button, to close and save the new ProtocolProfile;
– click on the Cancel button, to close the dialog without saving the new
ProtocolProfile;
– click on the Help button, to get information about this window.
Figure 4-44 Create Protocol Profile
Ethernet Port (local) Properties

This option is obtained, after selecting a Local EthernetPort ( or ), by means of
the contextual pop-up menu, or by selecting in the menu-bar:
Transmission Î EthernetPort Management Î EthernePort Properties.
The function of this option is to show the transmission parameters set for the selected local
Ethernet port.
for “Configure (local) Ethernet Port” (p. 4-67),except for the following extra field,
displayed in the Configuration sector:
............................................................................................................................................................................................................................................................
4 - 78 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• Eth.Avail.Bandwidth: remaining bandwidth that is not yet occupied by “children"

resources (in kb/s)
Figure 4-45 (Local) Ethernet Port Properties
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-79
............................................................................................................................................................................................................................................................
Configure (remote) Ethernet Port

This option is obtained, after selecting a REMOTE EthernetPort t ( ), by means of the
An example of the window displayeds are reported from Figure 4-46, (pg. 4-83) to
Figure 4-50, (pg. 4-87).
Note: The switch between GFP and LAPS framing type is done by
means of “Substitute Server Layer", see “Substitute Server Layer
for an Ethernet Port” (p. 4-92).
The function of this option is to manage the transmission parameters of the selected
remote Ethernet Port.
• 8 Remote EthPorts numbered 1001 to 1008 on ES-CT and 1 to 8 on SDH-CT;
• 16 MII Remote EthPorts numbered 1001...1016 on ES-CT corresponding to 1...16 on
SDH-CT,
or:
• 2 GMII Remote EthPorts numbered 1017,1018 on ES-CT corresponding to 17, 18 on
SDH-CT;
Note: MII and GMII are mutually exclusive: for changing them
all resources of the board must be in down state (see also “GMII -
MII Remote Interface Selection (ES4 board only)” (p. 4-60)).
WARNING
This operation requires that, on SDH-CT application, the configuration of this
same port, defining its SDH specific container, will be done (also later). See
also the note in “Inconsistency error on Port configuration” (p. 4-90).
WARNING
In case of ES4 board, the interface type must be congruent with that one
equipped in SDH-CT side (by means of the Equipment Î Set... menu option).
To configure a remote EthernetPort, fill fields and areas as follows:
• Configuration sector (ref. to Figure 4-46, (pg. 4-83)):
• Name: indicating the name assigned by the system to the Port (read only field)
• Type: indicating the type of port (read only field, fixed to ethernetCsmacd)
• Last Change: the value of System Time when the port entered its current operational
state
............................................................................................................................................................................................................................................................
4 - 80 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• MTU: Maximum Transmit Unit; size of the largest packet which can be
sent/received on the interface, specified in octets (read only field), fixed by means
of “Configure ISA” (p. 4-62).
• Connector: (true/false) indicating if the interface has a physical connector (read
only field)
• MAC Address: address of the selected ethernet port (logical address set by the
system)
• Alias: friendly name for the interface, it can be specified by the user
• Discard Errored Frames: indicating whether errored frames are to be discarded ---
(read only field), set by the system= true
• Client Type: (read only field), set by means of SubstituteClientLayer), indicating
the transported layer:
• Ets Service Type: (read only field, settable by means of “Characterization Service of
an Ethernet Port” (p. 4-93)), indicating the Service for which this Port is dedicated:
– portToPort: in this case it supports only PortToPort connections
– other: in this case it is ETB port, or supports UNI-Bridged connections
– EtsVirtSw: (not supported in current release) in this case it is used for Ets
Virtual Switch connections.
• Ets Egress Port (Peer): (read only field), set after that a port-to-port XC has been
created, (in Connection context):
– none: in this case the port is not connected, or used for UNI-Bridged
connections
– ETH...port#...: indicating the name of Peer port connected in PortToPort.
– up: to set the port in-service
– down: to set the port out-of-service
• Oper. Status: operational status, (read only field, set by the system) possible
options:
– up: the port is available
– down: the port is unavailable
• Link Up Down Trap: indicating whether linkUp / linkDown traps (notification upon
the changing of the node operational state from up to down and vice versa) should
be generated for this interface. Possible options: enabled / disabled .
• Promiscuous Mode: indicating whether this interface has to inspect the MAC
addresses; possible options:
– enabled: the MAC frames are accepted regardless of their MAC addresses
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-81
............................................................................................................................................................................................................................................................
– disabled (not available): the MAC frames addresses are inspected before their
acceptance, in order that only frames addressed to this port can be seen
physical layer; possible options:
– ethernetV2: default mode, set by the system
– IEEE8023: not yet operative
menu” (p. 4-33)
• Protocol Profile: name of the 2-bytes provider VLAN-protocol-tag (PT) to be
“pushed" into the ethernet frame of data flows afferent to the current Port.
Important! It is settable only if the port is in down state, and the
Bridge Type = bridge 802.1S-AD (Provider)).
the key permits to choose and associate a provider protocol-tag (PT) to this
resource, recalling the dialogue described in “Create Protocol Profile” (p. 4-76)
the key gives the Prot.-tag properties currently associated to this resource.
• Access Control List: (read only field, settable by means of “Configure ACL for an
Ethernet Port” (p. 4-94)), indicating the ACL profile associated to this Port;
reporting the rules for the acceptance of incoming MAC ethernet frames.
• Broadcast Traffic: specifies the broadcast traffic transmit capability of an egress
interface as a result of explicit management action. Possible values:
traffic,
• Unknown Traffic: specifies the unknown traffic transmit capability of an egress
traffic,
the broadcast and multicast traffic; when this feature is disabled the value of the
flooding rate is equal to value of if-speed and it is default value too.
............................................................................................................................................................................................................................................................
4 - 82 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• TP/GFP SDH Configuration sub-sector:

This group permits to configure the matching between the SDH container and the
ethernet bandwidth used by the current port, performing, if activated, a rate limiting
control by means of the CAC (Connection Admission Control); see also “Bandwidth
matching” (p. 4-87).
• Concatenation Type Set: available only if UnderlyingLayer = vconc; if marked it
permits to choose, in the “Bandwidth" field, the possible bandwidths that can be
used in virtual-concatenation mode
• Rate Limiting Set: available only if UnderlyingLayer = sdh; if marked it permits to
choose, in the Bandwidth field, the possible bandwidths that can be used in Rate-
Limiting mode
• Underlying Layer: possible pull-down options:
– vconc: (virtual concatenation); to permit the setting of the virtual
concatenation granularity mode
– sdh: to permit the setting of the Rate-Limiting mode
• Bandwidth [bps]: available bandwidth (band-limit) that can be used by the data
flows afferent to the current Port:
– the key permits to choose and associate a band-limit value to this
resource, recalling the dialogue described in “Bandwidth matching” (p. 4-87).
– the key gives the band-limit properties currently associated to this
resource
• Current SDH Speed: actual configured sdh rate
• Vc Type: actual configured sdh VC type.
Figure 4-46 Configure (remote) Ethernet Port - Configuration
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-83
............................................................................................................................................................................................................................................................
• GFP sector:
Figure 4-47, (pg. 4-85) shows only the GFP type port, settable by means of the option
SubstituteServerLayer:
• Enable FCS: (not operative); insertion or removal of GFP-FCS (Frame Check
Sequence) field into the optional field pFCS of the GFP frame.
• Send Control: assignment of Signal Label code (SL inserted into GFP frame);
possible pull-down options: automatic (the tx SL shall be automatically
calculated) or forced (the tx SL will be always forced to the “equipped-non-
specific" code).
• TxSL / RxSL / ExpSL: Signal Label management (Tx = transmitted, Rx = received,
Exp = expected).
• Transmit Capability: management of CSF alarm (Client Signal Fail); possible
options:
– disabled: alarms management is not managed
– unidir: CSF is inserted, towards the SDH network, into the GFP frame, in case
of LOS detection on the local ethernet port connected to this port (Rec. G.7041
2001).
– bidir: CSF is inserted, towards the SDH network, into the GFP frame, in case
of LOS detection on the local ethernet port connected to this port, or in case of
one or more of the following alarms received by this port: LOF, TSF, PLM
(rec. G.7041 2001).
– unidir UPI-LOF: management of CSF as in the above unidir case, but with the
UPI coding as specified in G.7041 2005.
– bidir UPI-LOF: management of CSF as in the above bidir case, but with the
UPI coding as specified in G.7041 2005. The CSF management is illustrated in
“CSF alarm management” (p. 1-54).
– unidir VC-AIS: for propagation of Ethernet LOS alarm to SDH. The VC-AIS
alarm is inserted, towards the SDH network, into the sdh VC container, in case
of LOS detection on the local ethernet port connected to this port. The VC-AIS
management is illustrated in “VC-AIS alarm management” (p. 1-55).
– Backward (and Backward UPI-LOF): not supported in current release.
............................................................................................................................................................................................................................................................
4 - 84 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-47 Configure (remote) Ethernet Port - GFP
• L2 Control Frame sector: see Figure 4-48, (pg. 4-86) (not displayed in case of ETB
port) it permits to enable or disable the Protocol Frames that can accede to this port:
• Protocol List: it reports all the available Protocol frames (Bit Name), and,
correspondingly, its Status. The Status can be changed by means of the apposite
pull-down menu that is activated by clicking on it; possible values:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-85
............................................................................................................................................................................................................................................................
Figure 4-48 Configure (remote) Ethernet Port - L2 Control Frame
• Alarms sector see Figure 4-49, (pg. 4-86):

This group reports the alarms relevant to the EthernetPort; their color is green if not-
associated ASAP; the alarms colors are described in Chapter 5, “Maintenance”.
Figure 4-49 Configure (remote) Ethernet Port - Alarms
• LAPS sector,
Figure 4-50, (pg. 4-87) shows only the LAPS type port, settable by means of the
option SubstituteServerLayer:
• Flag Ins.: insertion of Flag byte in the LAPS frame; possible pull-down options:
single (means consecutive frames) or two (means non-consecutive frames).
............................................................................................................................................................................................................................................................
4 - 86 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• Send Control: assignment of Signal Label code (SL inserted into LAPS frame);
possible pull-down options: automatic (the tx SL shall be automatically
calculated) or forced (the tx SL will be always forced to the “equipped-non-
specific" code).
• TxSL / RxSL / ExpSL: Signal Label management (Tx = transmitted, Rx = received,
Exp = expected).
Figure 4-50 Configure (remote) Ethernet Port (LAPS)
After setting all the desired parameters, click on the Ok key to send the chosen parameters
to the EthernetPort.
The window will be closed without doing any operation by clicking on Cancel key.
Bandwidth matching
This option is obtained, in the Configure (remote) Ethernet Port window, shown in
Figure 4-46, (pg. 4-83), after clicking on the key of the Bandwidth item.
WARNING
Before doing this operation, the user should have done, on SdhCT application
(with IsaPortConfiguration option), the configuration of this same port,
defining its SDH specific container. See also the note in “Inconsistency error on
Port configuration” (p. 4-90).
The user is recommended to configure the Ethernet-bandwidth and the SDH-
containers in a congruent mode.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-87
............................................................................................................................................................................................................................................................
The total traffic rate into Remote Ethernet Ports is limited. In fact it can be fixed to 10 or
100 Mb/s, depending on the type of ethernet interface used at the end points. Usually, the
SDH available container capacity can be greater or smaller than the band of standard
ethernet interfaces.
Thus, the rate-limiting function avoids the configuration of a total committed traffic
greater than the physical transport rates.
In case of VirtualConcatenation mode, the function permits to transport a data rate greater
than one single SDH-VCx; in fact it sets the usable bandwidth to a multiple of the number
of sdh-VC's that are used.
The setting of the rate limiting function should take into account the sum of the CIR
parameters of all the data flows afferent to a port, or, in the cases where the CIR is not
defined (BestEffort traffic), a single afferent flow's PIR must not exceed that limit.
The window displayed is different, depending on the parameter UnderlyingLayer.
– If UnderlyingLayer = sdh (RateLimiting): a window as Figure 4-51, (pg. 4-89) will
be displayed.
– If UnderlyingLayer = vconc (VirtualConc): a window as Figure 4-52, (pg. 4-90)
will be displayed.
1. Rate Limiting case (Figure 4-51, (pg. 4-89)).
The function of this option is to manage the Rate Limiting to be associated to the
current remote Ethernet Port. It is used to avoid the traffic congestion in cases when
two ports at different rates are interworking.
E.g. if a 100Mbps port is connected to a remote 100Mbps port by means of one VC4
sdh link: in this case the SDH-“fractional rate” of 100 Mbps can be used.
Note: In case that a fractional rate (not available in current
release) has been used at the connected local port as well, the two
fractional rates must be consistent.
It lists the possible sdh-VC rates that can be used, depending on the VC type that has
been configured at the SDH side (by means of the SdhCT), for the current port. It is
available only if the chosen sdh-VC is not concatenated. It reports the list of the
possible rates, with relevant payload capacity:
– if SdhVC = VC4, the possibilities are: 149,760,000; 100,000,000
– if SdhVC = VC3, the possibilities are: 48,384,000; 10,000,000
– if SdhVC = VC12, the possibilities are: 2,176,000
• the Ok button, permitting “to bind" the selected RateLimiting to the related port;
• the Cancel button, permitting to close the window without associating a
RateLimiting;
............................................................................................................................................................................................................................................................
4 - 88 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-51 Rate Limiting Combination example (VC4 case)
2. Virtual Concatenation Granularity case (Figure 4-52, (pg. 4-90)).

The function of this option is to manage the VirtualConcatenation Granularity to be
associated to the current remote Ethernet Port. It permits to set and to limit the
bandwidth equivalent to a multiple of the number of VC's that are configured at the
sdh side. The congruency between SDH side (container) and ISA-ES side (bandwidth)
is recommended.
It contains the following areas and fields (see also “GMII - MII Remote Interface
Selection (ES4 board only)” (p. 4-60)):
a. MII interface case:
– Vconc Granularity: permitting to set the number (n) of concatenated
containers, depending on the type of concatenated VC chosen at the SDH side:
SdhVC = VC4: not applicable
if SdhVC = VC3, then n_max=2
– VCi: Total Vconc Bandwidth: (VCi = VC12 or VC3); indicating the total
concatenated bandwidth
– SDH Bandwidth: indicating the actual, configured and active SDH bandwidth.
b. GMII interface case:
– Vconc Granularity: permitting to set the number (n) of concatenated
containers, depending on the type of concatenated VC chosen at the SDH side:
– VCi: Total Vconc Bandwidth: (VCi = VC12 or VC3 or VC4); indicating the
total concatenated bandwidth
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-89
............................................................................................................................................................................................................................................................
– SDH Bandwidth: indicating the actual, configured and active SDH bandwidth.
• the Ok button, permitting “to bind" the selected Vconc to the related port;
• the Cancel button, permitting to close the window without associating a Vconc;
Figure 4-52 Virtual Concatenation Granularity example (MII, VC12 case)
Inconsistency error on Port configuration
WARNING
In case that the selected port has not been configured on SdhCT side, or if the
Port actual parameters are not congruent with the Sdh side, the ISA ES-CT will
return a window informing that there is an inconsistency between SONET/SDH
and port configurations; see figure below:
Figure 4-53 Inconsistency error on Port Configuration
............................................................................................................................................................................................................................................................
4 - 90 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Ethernet Port (remote) Properties

This option is obtained, after selecting a Remote EthernetPort ( or ), by means
of the contextual pop-up menu, or by selecting in the menu-bar:
Transmission Î EthernetPort Management Î EthernePort Properties.
The function of this option is to show the transmission parameters of the selected remote
Ethernet port.
for “Configure EthernetPort", “Configure (remote) Ethernet Port” (p. 4-80), except for the
following extra field, displayed in the Configuration sector:
• Eth.Avail.Bandwidth: remaining bandwidth that is not yet occupied by “children"
resources (in kb/s)
Figure 4-54 (Remote) Ethernet Port Properties
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-91
............................................................................................................................................................................................................................................................
Substitute Server Layer for an Ethernet Port

This option is obtained, after selecting a remote Ethernet Port ( with AdminStatus =
down), by means of the contextual pop-up menu, or by selecting in the menu-bar:
Transmission Î Ethernet Port Management Î Substitute Server Layer.
It contains two sub-options:
• ETH on GFP: active only if the current framing type is LAPS over SDH, to change from
LAPS to GFP
• ETH on LAPS: active only if the current framing type is GFP over SDH, to change from
GFP to LAPS.
An example of the window displayed is reported in Figure 4-55 and Figure 4-56.
This option permits to switch the server layer where the ethernet frames are encapsulated,
between GFP over SDH and LAPS over SDH.
Figure 4-55 Substitute Server Layer (from GFP to LAPS)
Figure 4-56 Substitute Server Layer (from LAPS to GFP)
............................................................................................................................................................................................................................................................
4 - 92 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Characterization Service of an Ethernet Port

This option is obtained, after selecting a Local or Remote Ethernet Port ( with
AdminStatus = down), by means of the contextual pop-up menu, or by selecting in the
Transmission Î Ethernet Port Management Î Characterization Service
It contains three sub-options:
• Other (Service): active only if the port is currently configured for ETB, Bridge
functions, to change from Port-to-Port to Other service.
• Port To Port (Service): active only if the port is currently configured for transparent
Port-to-Port connection, to change from Other to Port-to-Port service.
• Ets Virtual Switch (Service): not supported in current release. It permits to create a set of
differentiated flows afferent to the same input port and output port (all inflows of the
same input port must be connected to outflows belonging to the same output port). In
this way the data flows between two ports can be treated in different modes, depending
on their different CoS (TD, Priority, VLAN).
This option permits to switch the service to which this port has to be deputed.
Traffic Management of an Ethernet Port

This option is obtained, after selecting a Local Port ( with Admin Status = up) or a
LAG ( with Admin Status = up), by means of the contextual pop-up menu, or by
selecting in the menu-bar:
Transmission Î Ethernet Port Management Î Traffic Management
This description applies also in case of Aggr Port (when an ETB-Aggr Port has been
selected):
Transmission Î Aggregator Î Traffic Management.
It contains two sub-options:
• Traffic Enabled: active only if the traffic on this port is currently configured as disabled,
to change from disabled to enabled traffic.
• Traffic Disabled: active only if the traffic on this port is currently configured as enabled,
to change from enabled to disabled traffic.
This option permits to interrupt the traffic afferent to this port and to restore it, thus
maintaining the already created resources and configuration existing over the port.
After disabling the traffic, alarms detection is inhibited on the port.
In traffic disabled, the VLAN registrations are preserved, and the following parameters
can be changed:
• Autonegotiation parameters, MTU/MRU, Protocol Type (i.e. “protocol-profile”).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-93
............................................................................................................................................................................................................................................................
Traffic Management of an Aggregator

This option is obtained, after selecting a Local Port ( with Admin Status = up) or a
LAG ( with Admin Status = up) , by means of the contextual pop-up menu, or by
selecting in the menu-bar:
Transmission Î Aggregator Î Traffic management.
Its function is the same of the previous above option for “Traffic Management of an
Configure ACL for an Ethernet Port

This option is obtained, after selecting a Local or Remote Ethernet Port ( with Admin
Status = up), by means of the contextual pop-up menu, or by selecting in the menu-bar:
Transmission Î Ethernet Port Management Î ACL ManagementÎ Configure ACL.
WARNING
The option is available only if the selected ethernet port is ETS type (not ETB).
The function of this option is to configure and associate an ACL profile to the selected
ETS ethernet Port. ACL (Access Control List) permits to create and associate a list of
rules for the acceptance of incoming MAC ethernet frames, according to some parameters
such as: MAC addresses, VLAN id, etc.
To configure ACL, fill fields and areas as follows:
• ACL Index: index of ACL associated to the selected resource (read only)
Note: Index “0” means that no ACL is associated actually
the corresponding key permits to choose, create or associate an ACL, opening
the dialog described in “Configure ACL/ACL setting for an Ethernet Port” (p. 4-95).
Figure 4-57 Configure ACL
After selected the ACL, click on Ok button, to associate it to the port;

the Cancel button permits to close the window without associating ACL;
the Help button, permits to have information about this function.
............................................................................................................................................................................................................................................................
4 - 94 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Configure ACL/ACL setting for an Ethernet Port

This option is obtained, in the previous Configure ACL window, after clicking on
the key of the ACL Index item.
This dialog reports the list of existing ACL, with the following fields:
Name: it is the prefix name given to the selected ACL
Apply Changes: possible values: true it can be associated to the port or false, the ACL
can be associated but it is not effective.
Status: it is always set to active
• ACL Management sub-sector:
it is related to the item selected on the list:
• Prefix Name: the user can type the prefix, that will be inserted on the above field
Name, after clicking on Modify key.
• Apply Change: the user can change the effectiveness (true/false) of selected ACL,
that will be inserted on the above field Apply Change, after clicking on Confirm
Change key.
Note: If “True” its parameters can not be changed by means of
dialog window presented in next paragraph. To modify the
parameters, swap this value to “false”.
The Create button permits to create a new ACL row in the above list.
The Configure button permits to create a new ACL Profile, opening a new window as
explained in “Ethernet Port -> Configure ACL/ACE management” (p. 4-96).
Furthermore it contains the following keys:
– the Details button, permitting to see the properties of the selected ACL, opening a
similar window as for Configure, in only-read mode;
– the Modify button, permitting to modify the “Prefix-name” as explained above;
– the Delete button, permitting to delete the selected ACL;
– the Apply button, permitting to associate the selected ACL to the related Port;
– the Cancel button, permitting to close the window without associating ACL;
– the Help button, permitting to have information about this current function.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-95
............................................................................................................................................................................................................................................................
Figure 4-58 ACL list setting
Ethernet Port -> Configure ACL/ACE management

This option is obtained, in the previous ACL management window, after clicking on the
Configure key.
This dialog permits to create or modify the ACL - ACE (Access Control Element);
WARNING
The parameters presented in this window can not be modified, if the Apply
Change in Figure 4-58, (pg. 4-96) is True.
To modify these parameters, swap Appalachian to false.
The ACE window reports the list of existing ACL/ACE, with the following fields:
• ACL/ACE Name: it is the name given to the selected ACL/ACE
• Action: possible values: permit or deny (as set in below configuration):
– permit: it means that the relevant rule is designed to permit the entrance of
incoming frames satisfying this specification.
Note: permit means also that all other frames not included in this
relevant rule will be discarded as well, if not specified in another
rule.
............................................................................................................................................................................................................................................................
4 - 96 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
– deny: it means that the relevant rule is designed to refuse the entrance of incoming
frames satisfying this specification.
Note: deny means that also all other frames not included in this
relevant rule will be discarded as well, if not specified in another
rule.
• ACE Order: it reports the order for which the system will take into account the
different ACL/ACE rules listed.
Note: If a “deny” rule is the first one, then other frames to be
accepted (if any) must be specified in other “permit” rules.
• Status: possible values: up or down (as set in below configuration)
– up: it means that the relevant rule is active and taken into account.
– down: it means that the relevant rule is inactive and not taken into account.
ACE Configuration sub-sector:
it is relative to an ACE item selected in the list, in order to create or change its
specification parameters.
• Action: possible values: permit or deny; (their meaning has been explained above).
• Status: possible values: up or down; (their meaning has been explained above).
• MAC Source: source address of incoming frames for this rule.
• MAC Source Bitmask: bitmask for source address. Each bit of source address is
matched with this mask:
– if a given bit of the mask is “0”, it means “don’t care” (i.e. the incoming address
bit can be either 0 or 1).
– if a given bit of the mask is “1”, it means “exact matching” (i.e. the incoming
address bit must be equal to what specified in this rule).
Example: if the MAC Source specified in the rule is “00:21:33:aa:bb:2c”, and
bitmask = “ff:ff:ff:ff:ff:ff”, then only frames having that exact source address
(00:21:33:aa:bb:2c) will be accepted. If, instead, its bitmask is 00:00:00:00:00:00,
then all source addresses are accepted.
• MAC Dest.: destination address of incoming frames for this rule.
• MAC Dest. Bitmask: bitmask for destination address. Each bit of destination address is
matched with this mask. Its meaning is as specified above, for source address.
• ETHer. Type: MAC client type, i.e. type of transported packet, contained in the 2 bytes
L/T field of the frame (the frame format is illustrated in “Data frames” (p. 1-31)).
• ACE VID: VLAN identifier of incoming frames specified for this rule. Possible values:
0 to 4095, “4097” means any VLAN-id (“don’t care”), “4096” means VLAN-
untagged.
• ETHer. Type Range: not supported.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-97
............................................................................................................................................................................................................................................................
• Vid Range: not supported.

• Swap Values: this fields are provided to swap the orders of two listed ACL/ACE rules;
the 2 items to be swapped must be selected in the list by means of mouse and <Ctrl>
button on keyboard, and then written, in the fields First ACE Order and Second ACE
Order, then they are swapped, by clicking on Swap ACE Order key, if Swap Values is
checked.
• Create button permits to create a new ACL/ACE item in the list;
• Modify button permits to change the parameters of a created or existing ACL/ACE
item;
Important! In order to modify the ACE parameters, it is suggested to act the
following steps:
a. select one item in the list.
b. set the Status field in down condition.
c. click on the Modify key.
d. change parameters such as Action, SourceAddr, etc., by typing in the ACE
configuration fields.
e. set the Status field in up condition.
f. click on the Modify key.
Furthermore the window contains:
• Delete button, permitting to delete the selected ACE
Important! In order to delete the ACE rule, it is suggested to set the relevant Status
field in down condition.
• Close button, permitting to return back to previous window
• Print button, permitting to print the properties of a selected item;
• Help button, permitting to have information about this current function.
............................................................................................................................................................................................................................................................
4 - 98 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-59 ACL/ACE setting
Properties ACL of an Ethernet Port

This option is obtained, after selecting an ETS Local or Remote Ethernet Port ( with
Admin Status = up), by means of the contextual pop-up menu, or by selecting in the menu-
bar:
Transmission Î Ethernet Port Management Î ACL ManagementÎ Properties ACL.
The function of this option is to show the ACL parameters set for the selected Port. All the
reported information fields are read-only, and are the same as those explained in
“Configure ACL for an Ethernet Port” (p. 4-94).
Figure 4-60 Port: ACL Properties
Disassociate ACL for an Ethernet Port

This option is obtained, after selecting an ETSLocal or Remote Ethernet Port ( Admin
Status = up), by means of the contextual pop-up menu, or by selecting in the menu-bar:
Transmission Î Ethernet Port Management Î ACL ManagementÎ Disassociate ACL.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4-99
............................................................................................................................................................................................................................................................
Note: This option is available only if an ACL profile has been

associated to the selected port.
An example of the window displayed is reported in Figure 4-61, (pg. 4-100) The function
of this option is to disassociate the ACL profile that has been set for the selected Port.
Figure 4-61 Port: Disassociate ACL
Create ETS InFlow for an Ethernet Port

This option is obtained, after selecting a Remote or Local ETS Ethernet Port ( with
Admin Status = up) or a LAG ( with Admin Status = up), by means of the contextual
Transmission Î Ethernet Port Management Î Create ETS InFlow.
This description applies also in case of LAG (when an ETB-LAG has been selected):
Transmission Î Aggregator Î Create ETS InFlow.
WARNING
The option is available only if the selected ethernet port is ETS type (and not
ETB), with AdminStatus = up.
WARNING
His creation must be done in one single step by means of the Connection
wizard. See “Create Ets XC One Step (MAC & Virtual) for the Ethernet Port”
(p. 4-242) and “Create Ets XC One Step (Provider) for the Ethernet Port”
(p. 4-246). The scope of this paragraph is to describe the settings and meanings
of the resource parameters.
The function of this option is to create an InFlow resource into the selected ETS ethernet
Port.
To create an InFlow object, fill fields and areas as follows:
• ETS InFlow: indexed name assigned by the system to the resource (read only)
............................................................................................................................................................................................................................................................
4 - 10 0 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Note: The index is incremental over all the existing inflows of all
the ports
• User Label: optional name assigned by the user to describe this resource
• Service Type: upper layer service type (read only field): Ethernet
• Traffic Descriptor indicating the name of the associated traffic descriptor (TD):
the key permits to choose and associate a traffic descriptor to the data flow,
recalling the dialogue described in “ETS Traffic Descriptor configuration” (p. 4-51).
the key gives the properties of the traffic descriptor currently associated.
WARNING
The bandwidth associated to this resource must be congruent with the CIR/PIR
values indicated in the contract, with the band indicated in the mother-port, and
also with the sdh rate capability of the logical port associated by means of the
SDH-Craft Terminal application (see “ETS Traffic Descriptor configuration”
(p. 4-51)).
• Classification Mode: to choose the Priority of this InFlow; possible pull-down options:
– priority: to use the 802.1p priority mode (prio0 to prio7)
– dscp: to use the Ip-ToS (Type-of-Service) mode
• Status: notification about the actual status of the resource; possible pull-down options
(read only):
– up: the resource is in-service;
– down: the resource is out-of-service
• Policing Mode: to set the policing on the ETS traffic; possible pull-down options:
– disabled: the policing is not performed (i.e. all rates are forwarded, if the band is
available)
– color-blind: the policing is based on the associated TD, without taking into
account the user CoS
– color-aware: (not yet available/not operative) the policing is based on the
associated TD and on the priority colors of the associated ColorProfile explained
below
• Flow Type: possible options:
– unicastNoAutolearning: for unicast link
– multicastOptionA: (not available in current release) for multicast link
• Service Id: (set by the system); indicating the suffix number of the mother-port
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 0 1
............................................................................................................................................................................................................................................................
• Protocol List sub-sector

It permits to enable or disable the Protocol Frames that can pass through this inflow.
It reports all the available Protocol frames (Bit Name), and, correspondingly, its
Status. The Status can be changed by means of the apposite pull-down menu that is
activated by clicking on it. Possible values:
Important! More information about the traffic description,
Policing, ColorProfile is reported in “Traffic Descriptor,
Forwarding Priority and Class of Service” (p. 4-54).
WARNING
Under the same mother ETH Port, all the inflows in color-aware mode must
have the same ColorProfile; i.e. only one ColorProfile per ETH Port is
supported..
After setting all the desired parameters, click on the Ok key to create this new InFlow
point, that will be shown in the tree-area, attached to the selected ethernet port. The
window will be closed without doing any operation by clicking on Cancel key. The Help
key gives helps about this function.
Figure 4-62 Create ETS InFlow
............................................................................................................................................................................................................................................................
4 - 10 2 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Create ETS OutFlow for an Ethernet Port

Transmission Î Ethernet Port Management Î Create ETS OutFlow.
Transmission Î Aggregator Î Create ETS OutFlow.
WARNING
ETB), with AdminStatus = up.
WARNING
This creation must be done in one single step by means of the Connection
The function of this option is to create an OutFlow resource into the selected ETS
EthernetPort.
To create an OutFlow object, fill fields and areas as follows:
• ETS OutFlow: indexed name assigned by the system to the resource (read only field)
Note: The index is incremental over all the existing outflows of all
the ports
• Server Type: server layer type (read only): Ethernet
• Server Id: (set by the system); indicating the suffix number of the mother-port
• Status: notification about the actual status of the resource; possible pull-down options:
– up: the resource is in-service
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 0 3
............................................................................................................................................................................................................................................................
• VLAN Management: (not yet available) automatic incremental index identifying the
StackedVLAN-management profile; value “0" means that the SVLAN-management is
disabled (“Unbound"): in this case the StackedVLAN shim header is not “pushed" into
the ethernet frame
the key permits to choose and associate a VLAN-management profile, recalling
the dialogue described in “Create ETS OutFlow / VLANManagement (not available)”
(p. 4-104),
the key gives the properties of the VLAN-management profile currently
associated
the Unbind key permits to untie the data flow from the VLAN-management profile.
Note: More information about the traffic description, Policing,
ColorProfile is reported in “Traffic Descriptor, Forwarding Priority
and Class of Service” (p. 4-54).
WARNING
In case of Multicast (not yet available), all the multi-casted outflows must have
the same VLAN-Management parameters..
After setting all the desired parameters, click on the Ok key to create this new OutFlow
point, that will be shown in the tree-area, attached to the selected ethernet port.
Figure 4-63 Create ETS OutFlow
Create ETS OutFlow / VLANManagement (not available)

This option is obtained, in the Create ETS Outflow window depicted in Figure 4-63, (pg.
4-104), after clicking on the key of the VLAN Management item.
The function of this option is to manage the Stacked-VLAN parameters to be associated
to the outflow resources. It pushes, if activated, the Stacked-Vlan (provider-ShimHeader)
to the ethernet frame.
............................................................................................................................................................................................................................................................
4 - 10 4 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
To create a VLAN-Management profile, fill fields and areas as follows:

• VLAN index: indexed value assigned by the system to this profile (read only)
• VLAN value: Stacked-Vlan identifier to which associate these parameters
• Priority Mode: (see details in “Traffic Descriptor, Forwarding Priority and Class of
Service” (p. 4-54)); provider's prioritization mode; possible options:
– colorBlind: the frames are forwarded without provider's coloring
– colorAware: the frames are forwarded associating a provider's coloring
information as follows:
– the “green" Provider's colour is identified by attaching, to the ethernet frames,
the priority value selected into the Stack Priority field
– the “yellow" Provider's colour is identified by attaching, to the ethernet frames,
the priority value selected into the Stack Priority Yellow field
• Stack Priority: priority value to be assigned to the “green" provider-colour; possible
options:
– pri000 to pri111 (min. priority= “pri000", max = pri111)
• Stack Priority Yellow: priority value to be assigned to the “yellow" provider-colour
• Stack Status: possible options:
– up: to activate this Stacked VLAN management profile
– down: to deactivate this Stacked VLAN management profile
Important! More information about the traffic description is
reported in “Traffic Descriptor, Forwarding Priority and Class of
After setting the desired parameters, click on the Ok key to create this new VLAN-
Management profile.
Figure 4-64 Create VLAN Management
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 0 5
............................................................................................................................................................................................................................................................
Modify ETS InFlow

This option is obtained, after selecting an InFlow object ( ), by means of the
contextual pop-up menu, or by selecting in the menu-bar: Transmission Î ETS InFlow
Management Î Modify ETS InFlow.
The function of this option is to modify the transmission parameters set for the selected
InFlow point.
All the reported information fields are the same as those explained ones for “Create ETS
InFlow for an Ethernet Port” (p. 4-100). It contains, further, in the Protocol List, the extra
field Actual Status.
ETS InFlow Properties

contextual pop-up menu, or by selecting in the menu-bar: Transmission Î ETS InFlow
Management Î ETS InFlow Properties.
The function of this option is to show the transmission parameters set for the selected
InFlow point.
All the reported information fields are read-only, and the same as those explained ones for
“Create ETS InFlow for an Ethernet Port” (p. 4-100).It contains, further, in the Protocol
List, the extra field Actual Status.
Modify ETS OutFlow

This option is obtained, after selecting an OutFlow object ( ), by means of the
contextual pop-up menu, or by selecting in the menu-bar: Transmission Î ETS OutFlow
Management Î Modify ETS OutFlow.
OutFlow point.
All the reported information fields are the same as those explained ones for “Create ETS
OutFlow for an Ethernet Port” (p. 4-103).
ETS OutFlow Properties

contextual pop-up menu, or by selecting in the menu-bar: Transmission Î ETS OutFlow
Management Î ETS OutFlow Properties.
OutFlow point.
All the reported information fields are read-only, and the same as those explained ones for
“Create ETS OutFlow for an Ethernet Port” (p. 4-103).
............................................................................................................................................................................................................................................................
4 - 10 6 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Delete ETS InFlow

Transmission Î ETS InFlow Management Î Delete ETS InFlow.
WARNING
The resource will not be deleted if containing any inner resource (Classifier), or
if it is cross-connected, or also if it contains PM points.
This option permits to delete the selected InFlow point.
Figure 4-65 Delete ETS InFlow
Delete ETS OutFlow

Transmission Î ETS OutFlow Management Î Delete ETS OutFlow.
WARNING
The resource will not be deleted if containing any inner resource, or if it is
cross-connected, or also if it contains PM points.
The window displayed is similar to that reported in Figure 4-65, (pg. 4-107).
This option permits to delete the selected OutFlow point.
Create Eth2ETS Classifier

This option is obtained, after selecting an ETS InFlow object ( ), by means of the
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 0 7
............................................................................................................................................................................................................................................................
Transmission Î ETS InFlow Management Î Create Eth2ETS Classifier.
WARNING
The Classifier cannot be created over a PB (Provider) InFlow.
WARNING
The function of this option is to create a Classifier of the ethernet traffic into the selected
InFlow, defining the parameters of the user LAN's afferent into the related InFlow; every
InFlow resource needs one or more classifiers, in order to select the user frames to be
transported. More classifiers can be created into the same InFlow, but heading to different
VLAN ranges. It classifies the ethernet traffic to be transported over the ETS. Ethernet
frames having VLAN tags or user-priorities different from those indicated in the Classifier
will be discarded.
To create an Eth2ETS Classifier ( ), fill fields and areas as follows:
Important! Some of the following fields will be /(will not be) editable,
depending on the option selected in the field Topology Class.
• ETS InFlow: indicating the name assigned by the system to the resource (read only
field)
• Classifier Index: incremental index assigned by the system to the resource (read only
field)
• VLan: VLAN identifier number, in decimal format; range 0 to 4095 (2^12)
– VLAN=4096 is to be used in coincidence with Priority = untagged; for frames
containing neither Vlan nor Priority tags; in this case, incoming tagged frames will
be discarded
– VLAN=4097 is to be used in coincidence with Priority = don'tCare; in this case,
all ethernet frames will be forwarded, either tagged or untagged.
• Priority: to define the ETS priority level; possible pull-down options:
– pri000 , pri010 ,don'tCare , pri111 , pri110 , pri001 , pri101 , pri100 , untagged
(min. priority = pri000, max = pri111)
untagged means that the incoming frames contains neither Vlan nor Priority
values; in this case, incoming tagged frames will be discarded
don'tCare means that all frames will be forwarded, either tagged or untagged
............................................................................................................................................................................................................................................................
4 - 10 8 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Important! In cases that the related InFlow has been set with
VLAN-Pop = enabled or ColorProfile = bound, then this value must
be different from don'tCare or untagged
• Ip Dscp: (range 0 to 63); it defines the group of user IP DSCP values accepted by this
flow.
Important! This field is settable only if, in the relative InFlow, the
Classification Mode has been set to “dscp”
the special value “notIpPacket” (set by the system, if TopologyClass = No_IP) to
indicate that ethernet frames not containing IP packets are associated to this flow
the special value “dontCare” (set by the system, if ClassificationMode = priority) to
indicate that the IP-DSCP field is not considered, either if present or not present.
Note: This item is active only when the above item (Priority) is set
to dontCare and related InFlow is dscp.
• Ethernet Type: to define the transported upper Level3 protocol. Possible values:
– IP: if transporting IP packets
– ARP: if transporting ARP packets
– DRARP-RARP: if transporting DRARP/RARP packets
– SNMP: if transporting SNMP packets
– IPv6: if transporting IPv6 packets
– PPP: for PPP packets
– PPPoE-Discovery: for PPPoE-Discovery packets
– PPPoE-Session: for PPPoE-Session packets
– MPLS-multicast: for MPLS-multicast packets
– MPLS-unicast: for MPLS-unicast packets
• Classification Mode: read only, as set by the relative InFlow
• Status: possible pull-down options:
– up: to set the resource in-service
– down: to set the resource out-of-service
• Max VLan: max VLan number on which the data flow can be linked; value '0' means
only one Vlan linked (the one indicated in the VLan field); a value greater than VLan
field defines the Vlan range, in decimal format (e.g.: VLan = 33 and Max VLan = 50
defines the vlan range from 33 to 50).
• Max Priority: max priority associable to this classifier, in binary format; value '0' means only
one priority, a value greater than the value set in Priority field defines the priority range.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 0 9
............................................................................................................................................................................................................................................................
• Max Ip Dscp: max IpDscp value associable to this classifier, in decimal format; value '0'
means only one priority, a value greater than the value set in IpDscp field defines the
IpDscp range.
• Topology Class Possible options:
– VLAN+PRIO+EthType: in this case, the following parameters are editable, in the
dialog box: Vlan or MaxVlan, Prio” or MaxPrio, EthType
– VLAN+PRIO: in this case, the following parameters are editable, in the dialog
box: Vlan or MaxVlan, Prio or MaxPrio
– Untagged+EthType: in this case, the following parameters are editable, in the
dialog box: EthType, and the other parameters will be fixed to set the frame as
“untagged”
– Untagged: in this case, no parameter is editable, and the other parameters will be
fixed to set the frame as untagged.
– Default: in this case, no parameter is available, and the other parameters will be
fixed to set the frame as dontCare.
WARNING
The VLAN identifiers defined here must be different from those ones defined in other
classifiers of the same ethernet port, otherwise the classifier cannot be created.
After setting all the desired parameters, click on the Ok key to create this new Classifier
point, that will be shown in the tree-area, attached to the selected InFlow object.
Figure 4-66 Create Eth2ETS Classifier
Modify Classifier
This option is obtained, after selecting a Classifier object ( ), by means of the
............................................................................................................................................................................................................................................................
4 - 11 0 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Transmission Î Classifier Management Î Modify Classifier.

Classifier point. All the reported information fields are the same as those explained ones
for “Create Eth2ETS Classifier” (p. 4-107).
Classifier Properties
Transmission Î Classifier Management Î Classifier Properties.
Classifier point. All the reported information fields are read-only, and the same as those
explained ones for “Create Eth2ETS Classifier” (p. 4-107).
Delete Classifier
Transmission Î Classifier Management Î Delete Classifier.
The window displayed is similar to that reported in Figure 4-65, (pg. 4-107).
This option permits to delete the selected Classifier point.
Important! The resource will not be deleted if containing any
inner resource, or if it is cross-connected, or also if it contains PM
points.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 1 1
............................................................................................................................................................................................................................................................
Create Provider InFlow for an Ethernet Port

Transmission Î Ethernet Port Management Î Create Provider InFlow.
Transmission Î Aggregator Î Create Provider InFlow.
WARNING
ETB), with AdminStatus = up; further the Bridge Type = bridge 802.1S-AD
(Provider).
WARNING
The window displayed is reported in Figure 4-67, (pg. 4-113).
The function of this option is to create an InFlow resource into the selected ETS
EthernetPort, when the Bridge Type = bridge 802.1S-AD (Provider).
• ETS PB InFlow: indexed name assigned by the system to the resource (read only)
Note: The index is incremental over all the existing inflows of all
the ports
• Service Type: upper layer service type (read only field): ProviderBridge
• Traffic Descriptor indicating the name of the associated traffic descriptor (TD):
the key permits to choose and associate a traffic descriptor to the data flow,
recalling the dialogue described in “ETS Traffic Descriptor configuration” (p. 4-51).
the key gives the properties of the traffic descriptor currently associated.
Important! The bandwidth parameters (CIR/PIR, CBS/PBS)
associated to this resource must be null.
• Status: notification about the actual status of the resource. Possible pull-down options
(read only):
– up: the resource is in-service ;
• Service Id: (set by the system); indicating the suffix number of the mother-port
............................................................................................................................................................................................................................................................
4 - 11 2 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
– disabled: the policing is not performed (i.e. all rates are forwarded, if the band is
available)
– color-aware: (not operative) the policing is based on the associated TD and on the
priority colors of the associated ColorProfile.
• Flow Type: possible options:
– unicastNoAutolearning: for unicast link
– multicastOptionA: (not operative) for multicast link
• S-VID: to pop the S-VLAN field from the ethernet frame:
the key permits to choose and associate one registered VLAN, recalling the
dialogue described in “Create Provider InFlow / S-VID Management” (p. 4-114).
Figure 4-67 Create Provider InFlow
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 1 3
............................................................................................................................................................................................................................................................
Create Provider InFlow / S-VID Management

This option is obtained as described in “Create Provider InFlow for an Ethernet Port”
(p. 4-112), or “Create Provider OutFlow for an Ethernet Port” (p. 4-115), after clicking on
the key of the S-VID item.
An example of the window displayed is reported below.
The function of this option is to associate one Stacked-VLAN to the selected inflow
resources. The system will push (for OutFlow), or pop (for InFlow)) the relevant Stacked-
Vlan (provider-ShimHeader) to/from the ethernet frame.
The window reports the list of all the VLAN registered over the parent Ethernet Port.
To associate a VLAN, select the desired VLAN and click on Ok.
Figure 4-68 Provider Inflow: S-VID Filter
............................................................................................................................................................................................................................................................
4 - 11 4 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Create Provider OutFlow for an Ethernet Port

Transmission Î Ethernet Port Management Î Create Provider OutFlow.
Transmission Î Aggregator Î Create Provider OutFlow.
WARNING
ETB), with AdminStatus = up; further the Bridge Type = bridge 802.1S-AD
(Provider).
WARNING
(p. 4-246) The scope of this paragraph is to describe the settings and meanings
The window displayed is reported in Figure 4-69, (pg. 4-116).
The function of this option is to create an OutFlow resource into the selected ETS
EthernetPort, when the Bridge Type = bridge 802.1S-AD (Provider).
• ETS PB OutFlow: indexed name assigned by the system to the resource (read only)
Note: The index is incremental over all the existing outflows of all
the ports
• Server Type: upper layer service type (read only field): ProviderBridge
• Status: notification about the actual status of the resource. Possible pull-down options
(read only):
– up: the resource is in-service ;
• Server Id: (set by the system); indicating the suffix number of the mother-port
• S-VID: to push the S-VLAN field in the ethernet frame:
the key permits to choose and associate one registered VLAN, recalling the
dialogue described in “Create Provider InFlow / S-VID Management” (p. 4-114).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 1 5
............................................................................................................................................................................................................................................................
Figure 4-69 Create Provider OutFlow
Substitute Client Layer for an Ethernet Port or an Aggregator

This option is obtained, after selecting either a Local or Remote Ethernet Port ( with
Admin Status = down), or a LAG ( with Admin Status = down), by means of the
Transmission Î Ethernet Port Management Î Substitute Client Layer,
or, for LAG resource:
Transmission Î Aggregator Management Î Substitute Client Layer
It contains these sub-options:
• ETS Î ETB Layer: active only if the current port type is ETS (i.e. the afferent traffic
switching is manually engineered), to change from ETS to ETB
• ETB Î ETS Layer: active only if the current port type is ETB (i.e. the afferent traffic is
automatically switched by means of “Mac Autolearning" procedure), to change from
ETB to ETS
• LinkAggr Layer: (available only for Local Ports), to change this selected Port into Aggr
type: i.e. the afferent traffic is a part of a Link Aggregation Group.
An example of the window displayed is reported in Figure 4-70, (pg. 4-117) and
Figure 4-71, (pg. 4-117).
This option permits to switch the ethernet port resource, between “engineered" ETS and
“bridged" ETB, or Link Aggregation.
............................................................................................................................................................................................................................................................
4 - 11 6 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-70 Substitute Port Type (from ETS to ETB)
Figure 4-71 Substitute Port Type (from ETB to ETS)
Figure 4-72 Substitute Client Type (from ETS to Link Aggregator)
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 1 7
............................................................................................................................................................................................................................................................
VLAN Registration
This option is obtained, after selecting the Bridge node ( , by means of the contextual
Transmission Î ISA Management Î Vlan Registration.
WARNING
This option is not operative if Bridge Type = bridge 802.1D (MAC) as referred
in “Configure ISA” (p. 4-62)).
The function of this option is to manage the static registration of the VLAN Identifiers
over the Ports of the selected Bridge node.
Important! In case of Bridge Type = bridge 802.1S-AD
(Provider), the VLAN taken under consideration is the S-Vlan, i.e.
the provider VLan.
To register the VLAN Id., fill fields and areas as follows:
• VLAN# table: this view reports, in tabular form, the VLAN identifiers already registered
on active Ports of the bridge, and, in the same row, the relevant existing Ethernet Ports
on which a VLAN is registered; possible values:
– tagged means that the Port is part of the “MemberSet" of the corresponding VLAN
domain
– untagged means that the Port is part of the “UntaggedSet" (i.e. frames are
accepted, at the relevant port, without Priority nor VLAN information) of the
corresponding VLAN domain
– n.a. means that the Port does not belong to the corresponding VLAN domain.
A pull-down button is present on each cell of the table, in the columns of the ports, by
means of which the current value can be changed, among the possible ones: tagged /
untagged / n.a..
Important! In Bridge Type = bridge 802.1Q (Virtual) case, all the
existing (and activated) ETB ports of the board are tabled. While in
Bridge Type = bridge 802.1S-AD (Provider) case, all the existing
(and activated) ETS and ETB ports of the board are presented.
• New VLAN: this field permits the registration of a new VLAN over the selected Data
Board, by doing the following operations:
a. type the value of the new VLAN Identifier, in the range 2 to 4094
b. click on Create button, to open the window as reported in “Static VLAN
Registration Management for a Bridge” (p. 4-120).
c. then follow the instructions on this latter paragraph.
............................................................................................................................................................................................................................................................
4 - 11 8 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
d. then the new VLAN will be listed on the table.

The max number of VLAN static registration entries is 1024.
Figure 4-73 VLAN Registration
The Apply key is used when a value relative to a Port (untagged/tagged/na) has been
changed by means of the associated pull down menu. Or whenever this function is recalled
by another function.
The Delete key causes the deletion of the VLAN entry selected on the table.
The Print key is used to print this table.
After registering all the VLAN's afferent to this selected Node, click on Close key to close
the window.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 1 9
............................................................................................................................................................................................................................................................
Static VLAN Registration Management for a Bridge

This function is activated in the Vlan Registration List window , shown in Figure 4-73, (pg.
4-119), after typing the desired VlanId. on the New VLAN field and then clicking on Create
key.
The function of this option is to manage the Static VLAN Registration on the selected
Bridge; i.e. the registration of the VLAN under consideration on a group of Ports
(membership) on which this VLAN may be present (received/transmitted); this group of
ports represents the Member Set of that VLAN on this Bridge.
• VLAN Identifier: (read-only), current VLAN (as typed in the calling window) to be
associated to one or more ports
• Port Tagged Set sector: this sector is used to choose the ports belonging to the current
VLAN, i.e. where it can be present (received/transmitted).
In case of Bridge Type = bridge 802.1S-AD (Provider), the Available Network Ports
area lists all the available active ETB ports of the bridge.
In case of Bridge Type = bridge 802.1Q (Virtual) case, the Available Ports area lists all
the available active ETB ports of the bridge:
The association of a port with the VLAN is done by selecting one of the available ETB
ports and then clicking the [>>] key, after which the same port will be listed on the
Tagged Ports area.
An associated port can be removed from the TaggedPorts list by selecting it and then
clicking on the[<<] key.
• Port Untagged Set: (only for Bridge Type = bridge 802.1S-AD (Provider)); this sector
is used to choose the ports on which the frames belonging to current VLAN can be
received/transmitted, but untagged (i.e. without Priority and VLAN information).
In case of Bridge Type = bridge 802.1S-AD (Provider), the Available Customer Ports
area lists all the available active ETS ports of the bridge.
In case of Bridge Type = bridge 802.1Q (Virtual), the Available Ports area contains no
ports.
The association of a port with the VLAN is done by selecting one of the available ETS
ports and then clicking the [>>] key, after which the same port will be listed on the
Untagged Ports area.
After setting the desired parameters, click on the Ok key to confirm this VLAN
Registration instance.
............................................................................................................................................................................................................................................................
4 - 12 0 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-74 Static VLAN Registration Management (Provider case)
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 2 1
............................................................................................................................................................................................................................................................
Resources Availability
This feature gives the possibility to operator to monitor the status of the dynamic resources
present in the Network Element, in fact the scope of the such functionality is shown for
every type of resource (i.e. ETS Inflow, ETS Outflow, ETS Cross-Connections etc…) how
many resource are in total, how many are used and how many are available yet; for each
resource type has been defined a pool at the level of the agent SNMP.
This option is obtained, after selecting the resource on the root of the resource tree of the
USM as shown in the following Figure 4-75, (pg. 4-122).
Figure 4-75 Resource Availability pop-up menu
Select the Resource Availability pop-up menu option and the following Figure 4-76, (pg.
4-123) window opens.
............................................................................................................................................................................................................................................................
4 - 12 2 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-76 Resource Availability Group 1 and Group 2
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 2 3
............................................................................................................................................................................................................................................................
This windows shows nine pools, divided in Group 1 and Group 2 tabs.
• Group 1 tab contains the following six pools:
• Packet Processor CAM: It monitors the Purple Flowset used for applying protocol
filters.
• Ethernet Classifier: It monitors all the Classifiers connected to the ETS, that had
been created.
• InFlows: It is monitored irrespective of ServerType (i.e. Ethernet, Provider &
MPLS). It is dependent on SW memory as for ETS Classifier and OutFlows.
• OutFlows: It is monitored irrespective of ServerType (i.e. Ethernet, Provider &
MPLS). It is dependent on SW memory as for ETS Classifier and InFlows.
• CrossConnections: It monitors all the Cross Connection that had been created.
• Per VLAN Spanning Tree Instances: It monitors Per VLAN RSTP instances allocated
on VLAN creation. This pool is related to Sustained Control Plane Load and is
restricted by PPS rate required by RSTP protocol for supporting MAX PVRSTP
instances.
• Group 2 tab contains the following three pools:
• Sustained Control Pane Load: It monitors Tx PPS rate for all the control protocols -
STP, LACP, IGMP, Ethernet OAM, Link OAM. PPS rate is calculated using the
protocol configuration.
• Ethernet OAM MEP (Level 0): It monitors all the MEP (Maintenance entity group
End Point) in order to control the status of the network .
• Vlan Port Association (VPA): It monitors all the Virtual LANs connected to a port.
• Access Control List: It monitors all the ACL instances, that had been created.
Each pool contains these fields:
• Used: it contains the number of used resources.
• Available: it contains the number of available resources.
• Nominal: it contains the total number of the managed resources.
• Unavailable: it contains the number of the resources obtained in this way:
• #unavailable = #nominal - ( #used + #available)
............................................................................................................................................................................................................................................................
4 - 12 4 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Configure Bridge Port (Provider)

This option is obtained, after selecting an active Bridge port (i.e. with Admin
Status = up) or a LAG ( with Admin Status = up), by means of the contextual pop-up
menu, or by selecting in the menu-bar:
Transmission Î Ethernet Port Management Î Bridge Port Management Î Configure Bridge
Port.
Transmission Î Aggregator Î Bridge Port Management Î Configure Bridge Port.
WARNING
This option is available only if Bridge Type = bridge 802.1S-AD (Provider), as
referred in “Configure ISA” (p. 4-62)).
Provider Bridge port.
To configure the Provider Bridge (ETB) port, fill fields and areas as follows:
• Bridge Port Management sector:
• Bridge Port Name: settable “alias" name for this port
• Port Use DEI: (not operative in current release) to set the detection/insertion of the
Drop Eligible Indicator (Provider-priority coloration) on incoming/outgoing
frames. Possible values: true or false.
• Port PCP Decoding: (not operative in current release).
• Port VLAN Identifier:
the key permits to choose the PVID value for this resource, recalling the
dialogue described in “” (p. 4-136). Default value is 1; it is the PVID parameter,
i.e. the VID to assign to untagged or only-priority-tagged frames retransmitted by
this port. In consequence, this Port is included in the UntaggedSet of this indicated
VLAN.
• Ingress Filtering: to enable/disable the receive frame filter. Possible values:
– true: it discards all the frames having VLAN-ID that do not have this port on
their relevant “MemberSet". VLAN dependent BPDU frames (such as GMRP)
are filtered too.
Note: VLAN independent BPDU frames (such as GVRP and STP)
are not filtered.
– false: it accepts all incoming ethernet frames.
• Acceptable Frame Type. Possible values:
– admitAll: to accept either tagged and untagged ethernet frames.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 2 5
............................................................................................................................................................................................................................................................
– admitOnlyVlanTagged: to accept only VLAN tagged ethernet frames

• Bridge Port QoS sub-sector:
• Default User Priority: to set the User Priority to be assigned by default to untagged
frames.
WARNING
This option is operative only if the selected ETB Port is in down state.
the key permits to choose the Regenerated (retransmitted) Priority for this
resource, recalling the dialogue described in “Default User Priority List of the
Bridge Port” (p. 4-136).
• Regen. User Priority: to associate a Regeneration Priority to this ETB port.
resource, recalling the dialogue described in “Regenerated User Priority for the
BridgePort” (p. 4-134).
WARNING
• Control Plane Configuration sector:
WARNING
In case that the StpProtocol is set to manualDisable, this sector cannot be
used.
• (X)STP Per Bridge Management: the value reported is a Bridge Instance number; if
the StpProtocol is STP or RSTP then this value is 0, else if StpProtocol is
PERVLANSTP then this value is “4096+Vlan#"; this item encompasses the STP
parameters related to the bridge as seen from this port. In case of STP or RSTP its
parameters will be the same for all ports of the bridge
the key permits to open the STP-PerBridge dialogue described in “STP-Per
Bridge Management by the ControlPlane of the Bridge Port” (p. 4-137)
the key permits to view the STP-PerBridge properties, i.e. the same window
as described in “STP-Per Bridge Management by the ControlPlane of the Bridge
Port” (p. 4-137), but in read-only mode.
• (X)STP Per Port Management: the value reported is the Port Identifier; this item
encompasses the STP parameters related to the port
the key permits to open the STP-PerPort dialogue described in “STP-
PerPort Management by the ControlPlane of the Bridge Port” (p. 4-140)
the key permits to view the STP-PerPort properties, i.e. the same window as
described in “STP-PerPort Management by the ControlPlane of the Bridge Port”
(p. 4-140), but in read-only mode.
............................................................................................................................................................................................................................................................
4 - 12 6 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• List of VLAN: (available only in case that the relevant Bridge STP-parameter is STP-
Protocol = PERVLANSTP); this field lists the identifiers of VLAN's afferent to
this Port.
WARNING
In this case, the STP procedure is applied, independently, to each afferent
VLAN, as if they were as many independent networks as the VLAN's are. An
example of PER-VLAN bridged network and relevant roles is reported in
Figure 1-30, (pg. 1-45).
MSTP case:
WARNING
In case that the Bridge STP-Protocol is MSTP, the Control Plane sector is
displayed as reported in Figure 4-78, (pg. 4-129).
Some details about STP-RSTP-MSTP feature are reported in “STP functionality
(Spanning Tree Protocol)” (p. 1-43).
An example of MSTP Bridge network and MSTID use is shown in Figure 1-33, (pg.
1-48), and subsequent.
The management panel is subdivided in two parts: CIST and MSTI.
The CIST parameters are used to define the Common (global) features and topology of the
network (such as Region number, Digest, etc.).
The MSTI parameters are used to define the allocation of the VLAN-ID’s over the MSTID
instances (i.e. the MST Configuration Table).
• CIST Bridge Management (Common and Internal Spanning Tree). This panel is used to
define the Port Roles, in the CIST active topology; it reports:
• The Region Number for the CIST function:
the key permits to open the MST Region Management dialogue described
in “MST Region Management by CIST of the Bridge Port” (p. 4-144).
• The fields PerBridge and perPort Management, to be used as above explained for
the other windows.
• MSTI Bridge Management (Multiple Spanning Tree Instance). This panel is used to
define the Port Roles, in each MSTI active topology; it reports:
• MSTID: to define the MST Configuration Table ...:
the key permits to open the MSTID dialogue described in “MSTID
Management by the MSTI of the Bridge Port” (p. 4-145).
• PerBridge Management is used as in the other above explained STP cases, but
recalls the dialog reported in Figure 4-85, (pg. 4-140).
• PerPort Management is used as in the other above explained STP cases, but recalls
the dialog reported in Figure 4-87, (pg. 4-143).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 2 7
............................................................................................................................................................................................................................................................
Important! The PerBridge and PerPort parameters can be

differentiated for different MSTID’s. In order to change these
parameters, for example for an already created Instance 3, select
MSTID 3 in the dialog window reported in Figure 4-90, (pg.
4-147), and then press Ok; then the above field MSTID will report
the value 3, then the parameters PerBridge and PerPort can be
modified for the Instance 3.
After setting the desired parameters, click on the Ok key to confirm.
............................................................................................................................................................................................................................................................
4 - 12 8 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-77 Configure Provider Bridge Port (“PERVLANSTP" case)
Figure 4-78 Configure Bridge Port (Provider case/MSTP)
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 2 9
............................................................................................................................................................................................................................................................
Configure Bridge Port (Virtual)

Port.
WARNING
This option is available only if the Bridge Type = bridge 802.1Q (Virtual) as
referred in “Configure ISA” (p. 4-62).
Virtual Bridge port.
To configure the Virtual Bridge (ETB) port, fill fields and areas as follows:
• Port VLAN Identifier:
the key permits to choose the PVID value for this resource, recalling the
dialogue described in “” (p. 4-136). Default value is 1; it is the PVID parameter,
i.e. the VID to assign to untagged or only-priority-tagged frames retransmitted by
this port. In consequence, this Port is included in the UntaggedSet of this indicated
VLAN.
WARNING
This option is not available if the Bridge Type = bridge 802.1D (MAC) .
This option is operative only if the selected ETB Port is in down state (i.e. the
associated ETS port is in down state too).
• Ingress Filtering: to enable/disable the receive frame filter. Possible values:
– true: it discards all the frames having VLAN-ID that do not have this port on
their relevant “MemberSet". VLAN dependent BPDU frames (such as GMRP)
are filtered too.
Note: VLAN independent BPDU frames (such as GVRP and STP)
are not filtered.
– false: it accepts all incoming ethernet frames.
• Acceptable Frame Type. Possible values:
– admitAll: to accept either tagged and untagged ethernet frames.
............................................................................................................................................................................................................................................................
4 - 13 0 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
– admitOnlyVlanTagged: to accept only VLAN tagged ethernet frames

• Bridge Port QoS sub-sector:
frames
the key permits to choose the Default (retransmitted) Priority for this
resource, recalling the dialogue described in “” (p. 4-135).
WARNING
• Regen. User Priority: to associate a Regeneration Priority to this ETB port.

resource, recalling the dialogue described in “Regenerated User Priority for the
BridgePort” (p. 4-134).
WARNING
WARNING
In case that the StpProtocol is set to manualDisable, this sector cannot be
used.
• (X)STP Per Bridge Management: the value reported is a Bridge Instance number; if
the “StpProtocol" is STP or RSTP then this value is “0", else if “StpProtocol" is
PERVLANSTP then this value is “4096+Vlan#"; this item encompasses the STP
parameters related to the bridge as seen from this port. In case of STP or RSTP its
parameters will be the same for all ports of the bridge
• (X)STP Per Port Management: the value reported is the Port Identifier; this item
the key permits to open the STP-PerPort dialogue described in “STP-PerPort
Management by the ControlPlane of the Bridge Port” (p. 4-140)
(p. 4-140), but in read-only mode
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 3 1
............................................................................................................................................................................................................................................................
• List of VLAN: (available only in case that the relevant Bridge STP-parameter is STP-
Protocol = PERVLANSTP); this field lists the identifiers of VLAN's afferent to
this Port.
WARNING
In this case, the STP procedure is applied, independently, to each afferent
VLAN, as if they were as many independent networks as the VLAN's are. An
example of PER-VLAN bridged network and relevant roles is reported in
Figure 1-30, (pg. 1-45).
MSTP case:
WARNING
In case that the Bridge STP-Protocol is MSTP, the Control Plane sector is
configured as described for ProviderBridge, in “Configure Bridge Port
(Provider)” (p. 4-125).
Figure 4-79 Configure Bridge Port (Virtual case/PERVLANSTP)
............................................................................................................................................................................................................................................................
4 - 13 2 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Configure Bridge Port (MAC)

Port.
WARNING
This option is available only if the Bridge Type = bridge 802.1D (MAC), as
referred in “Configure ISA” (p. 4-62)).
The function of this option is to manage the transmission parameters of the selected MAC
Bridge port.
To configure the MAC Bridge (ETB)port, fill fields and areas as follows:
• Bridge Port State: (set by the system); current state of this port, informing about the
action this port takes on reception of a frame. Possible values:
– disabled: the port is disabled by failure or by the administrative control. A Port
in this state does not participate in frame relay or STP operations.
– dataframediscarding: data frames received in this port should be discarded,
but the control frame (such as BPDU) should be passed. The information of
data frame and control frame is not learned.
– listening: the port is waiting to be switched to Learning or to Blocking state
(not used in RSTP case).
– learning: data frames and control frames (such as BPDU) can be learned, but
can not be forwarded to other Bridge Ports.
– forwarding: data frames and control frames can be learned and forwarded.
frames. The key permits to choose the Regenerated (retransmitted) Priority
for this resource, recalling the dialogue described in “” (p. 4-135).
WARNING
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 3 3
............................................................................................................................................................................................................................................................
WARNING
These parameters are not applicable if the (STP)-Protocol Type is set in
manual Disable (see “Configure ISA” (p. 4-62)).
• (R)STP Per Bridge Management: the value reported is a Bridge Instance number; this
value is set to 0; this item encompasses the STP parameters related to the bridge as
seen from this port; its parameters will be the same for all ports of the bridge
• (R)STP Per Port Management: the value reported is the Port Identifier; this item
the key permits to open the STP-PerPort dialogue described in “STP-
PerPort Management by the ControlPlane of the Bridge Port” (p. 4-140)
(p. 4-140), but in read-only mode.
Figure 4-80 Configure MAC Bridge Port
Regenerated User Priority for the BridgePort

This function is activated in the Virtual or Provider BridgePort Management window
(Figure 4-77, (pg. 4-129), or Figure 4-78, (pg. 4-129)), after clicking on the key of
the Regen.UserPriority item.
............................................................................................................................................................................................................................................................
4 - 13 4 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................

WARNING
T
The function of this option is to show the Regenerated User Priority on the selected ETB
port; i.e. the association between received User Priority and the retransmitted one.
It permits the association of a Virtual or Provider User Priority profile to the retransmitted
frames (Priority-Tagged or Q-Tagged or S-Tagged frames), when the network manager is
requested to change this priorities profile. The appropriate use of User Priority
regeneration is specified in 802.1Q rec. (See also “Traffic Descriptor, Forwarding Priority
and Class of Service” (p. 4-54)).
The association is set by selecting one priority from the list, and then selecting the desired
value in the Reg.UserPriority (new value) pull-down list; possible values: 0 to 7; the relative
classes of services are also indicated in the window.
After finishing the priorities mapping, the window can be closed by clicking on Close key.
Figure 4-81 Bridge Port: Regenerated Priority List
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 3 5
............................................................................................................................................................................................................................................................
Default User Priority List of the Bridge Port

(Figure 4-79, (pg. 4-132), or Figure 4-77, (pg. 4-129), or Figure 4-80, (pg. 4-134)), after
clicking on the key of the DefaultUserPriority item.
WARNING
T
The function of this option is to manage the Default User Priority on the selected ETB
port; i.e. the association of a User Priority to the retransmitted frames (towards the
network), when incoming frames do not have the priority information (Untagged frames).
(See also “Traffic Descriptor, Forwarding Priority and Class of Service” (p. 4-54)).
This association is set by selecting one priority from the list, and then clicking on the Apply
key
The window will be closed without doing the association, by clicking on Cancel key.
Figure 4-82 Bridge Port: Default User Priority
............................................................................................................................................................................................................................................................
4 - 13 6 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Modify PVID (Port Vlan Identifier) of the Bridge Port

(Figure 4-79, (pg. 4-132), or Figure 4-77, (pg. 4-129), ), after clicking on the key of
the Port VLAN Identifier item.
WARNING
This option is not operative if Bridge Type = bridge 802.1D (MAC).
T
The function of this option is to manage the PVID (Port VLAN Identifier) parameter, i.e.
the VID to be assigned to untagged or only-priority-tagged frames retransmitted by this
port. As a result, this Port will be included in the “UntaggedSet" of the VLAN under
consideration.
The window reports the list of the already registered VLAN’s of the port.
To assign the PVID to the port, select one VLAN on the list, and then click on Apply.
Figure 4-83 BridgePort: Modify Port VLAN Identifier (PVID)
STP-Per Bridge Management by the ControlPlane of the Bridge Port

This function is activated in the ControlPlane Î Configure Virtual (or MAC or Provider)
BridgePort window (Figure 4-79, (pg. 4-132), or Figure 4-77, (pg. 4-129), or
Figure 4-80, (pg. 4-134)), after clicking on the key of the (X)STP PerBridge
Management item.
An example of the window displayed is reported in Figure 4-84, (pg. 4-140). In case of
Stp-Protocol= MSTP, the window will be as reported in Figure 4-85, (pg. 4-140), when
recalled by the MSTI sub-sector.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 3 7
............................................................................................................................................................................................................................................................
The function of this option is to manage the STP-PerBridge Instances to be associated to

this ETB port.
Important! The STP procedure selects as Root Bridge of the
network the bridge having the Address parameter (described
below) with lowest numerical value.
Important! The STP procedure will calculate the best path to
reach the Root Bridge, identifying the key elements on this path
(DesignatedBridges, RootPorts, DesignatedPorts), according to
Path Cost criteria. If there are two or more paths with the same
Path Cost, then the priority parameters of the involved elements
will be used to select the best path. Further, the Root Bridge will
have the RootPathCost parameter equal to zero.
An example of bridged network and relevant xSTP roles is reported in Figure 1-28 and
Figure 1-29, (pg. 1-44).
An example of “PER-VLAN" bridged network and relevant roles is reported in
Figure 1-30, (pg. 1-45).
To set the PerBridge STP instances, fill fields and areas as follows:
• Priority: priority of the Bridge (to whom this port belongs) to become the root bridge,
at start-up or in case of failure of the actual root-bridge; 16-bit decimal value, but only
the most significant 4 bits are settable. This value is used by STP procedure to
designate the Root Bridge (see below).
The possible options are 16 values, settable by means of the associated
incrementing/decrementing keys: (best priority = least numerical value).
• Address: (read only, set by the system); Bridge identifier of this selected bridge, as
specified in IEEE802.1D, composed of 8 octets, of which the first 4 bits representing a
priority parameter (as fixed in the above item), the next 12 bits are considered as local
system ID, the remaining 6 octets represent the bridge MAC address. The Root Bridge
of the network is the bridge having this parameter with lowest numerical value.
• Designated Root: (read only) representing the Bridge Identifier of the Bridge assumed
to be the Root Bridge for the current Spanning Tree instance.
• Root Path Cost: (read only) representing the cost of the path to the Root Bridge as seen
from this bridge for this spanning tree instance. When this Bridge is the Root Bridge
this parameter has the value zero. Otherwise, it is equal to the sum of the values of all
the Root Port Costs of the Bridges encountered along the path to reach the Root
Bridge.
Note: The Root Port Cost is the sum of Port Path Cost and Port
Designed Cost (defined in “STP-PerPort Management by the
ControlPlane of the Bridge Port” (p. 4-140)) of the Root Port for
this bridge
............................................................................................................................................................................................................................................................
4 - 13 8 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• Root Port: (read only) the port number of the port which offers the lowest cost path
from this bridge to the root bridge for this spanning tree instance. I.e., that Port for
which the Path Cost to reach the Root Bridge is the lowest.
• Hold Time: (read only, only for STP, fixed to one second); interval length during which
no more than one Configuration Bridge PDUs shall be transmitted by this node.
• Time Since Change: time (in hundredths of second) since the last time a topology
change was detected by this spanning tree instance.
• Topology Changes: (read only) total number of topology changes detected by this
spanning tree instance since the management entity was last restarted or initialized.
• Hello Time: (read only: actual value that this instance is currently using); amount of
time between the transmission of Configuration bridge PDUs by this instance on any
port when it is the Root Bridge of the spanning tree or trying to become so, in units of
hundredths of a second; (range = 1 to 10 sec).
• Max Age: (read only: actual value that this instance is currently using); maximum age
of Spanning Tree Protocol information learned from the network on any port before it
is discarded, in units of hundredths of a second; (range = 6 to 40 sec).
• Fwd Delay: (read only: actual value that this instance is currently using); this value,
measured in units of hundredths of a second, controls how fast a port changes its
spanning state when moving towards the Forwarding state. The value determines how
long the port stays in each of the Listening and Learning states, which precede the
Forwarding state. This value is also used, when a topology change has been detected
and is underway, to age all dynamic entries in the filtering Database. (Range = 4 to 30
sec)
• Next Best Root Cost: (only for RSTP); cost of the path to the root through the next best
root port as seen from this bridge for this spanning tree instance.
• Next Best Root Port: (only for RSTP); port number of the next port which offers the
lowest cost path from this bridge to the root bridge for this spanning tree instance. The
port here indicated will become root port if the actual root port goes down.
• TxHoldCount: (only for RSTP); used by the Port Transmit state machine to limit the
maximum transmission rate.
• Bridge Convergence Sensibility sector:
the values considered in this sector are used by all bridges (for STP convergence
sensibility) when this bridge is acting as the Root Bridge.
Hello Time / Max Age / Fwd Delay: their meaning is the same as explained above.
After setting the desired parameters, click on the Ok key to confirm these STP Instances
set.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 3 9
............................................................................................................................................................................................................................................................
Figure 4-84 BridgePort: STP-PerBridge Management
Figure 4-85 BridgePort: STP-PerBridge Management (MSTI case)
STP-PerPort Management by the ControlPlane of the Bridge Port

This function is activated in the ControlPlane Î Configure Virtual (or MAC or Provider)
BridgePort window (Figure 4-79, (pg. 4-132), or Figure 4-77, (pg. 4-129), or
Figure 4-80, (pg. 4-134)), after clicking on the key of the (X)STP PerPort Management
item.
An example of the displayed dialog window is reported in Figure 4-86, (pg. 4-143). In
case of Stp-Protocol= MSTP, the window will be as reported in Figure 4-87, (pg. 4-143),
when recalled by the MSTI sub-sector.
The function of this option is to manage the STP-PerPort Instances to be associated to
this ETB port.
............................................................................................................................................................................................................................................................
4 - 14 0 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
An example of bridged network and relevant roles is reported in Figure 1-28 and
Figure 1-29, (pg. 1-44).
An example of “PER-VLAN" bridged network and relevant roles is reported in
Figure 1-30, (pg. 1-45).
To set the PerPort STP instances, fill fields and areas as follows:
• Ethernet Port Configuration sector:
• Port Number: (read only); assigned by the system, according to the selected port
• Force Port State: (read only); indicating the forced current state; possible values:
– Dynamic: the port is managed by the Spanning Tree Protocol. It comprises the
following States:
- Listening: the port is waiting to be switched to Learning or to Blocking state
(not used in RSTP case).
- Learning: the port is not yet in forwarding state, but can learn new MAC
destinations.
– Blocked: the frames received by this port will be discarded, thus forcing it out
of the active topology, for preventing frame duplication arising through
multiple paths; STP control frames (BPDU) are not discarded.
– Forwarding: the port is participating in the frames relay, STP algorithm
computation and MAC learning procedures, thus it is included in the active
topology.
– Disabled: used to disable the port. In this state, all frames received will be
discarded, further the Port does not participate in the operations of the STP or
MAC learning processes.
Note: In RSTP configuration, only three Port-States are used:
Discarding, Learning, Forwarding.
• Port Configuration sector:
• Port State: (read only); indicating the current port state regard the STP process;
possible values are as detailed in the sector above (item ForcePortState).
• Port Priority: priority of this port to become the root port (for the Bridge to whom
this port belongs); at start-up or in case of failure, if the other cost parameters are
the same, this value will be taken into account to designate the Root Port; 8-bit
decimal value, but only the most significant 4 bits are settable. The possible
options are 16 values, settable by means of the associated
incrementing/decrementing keys. (best priority = least numerical value).
• Port Role: (read only); the following values are available (see 802.1D Recom.):
– root: the port offers the lowest cost path from this bridge to the root bridge. It is
to be part of the active topology connecting the Bridge to the Root Bridge.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 4 1
............................................................................................................................................................................................................................................................
– designated: the port is connecting a LAN, through the current Bridge, to the
Root Bridge
– alternate: Alternate Port if the Bridge is not the Designated Bridge for the
attached LAN. It offers an alternate path (after failure) in the direction of the
Root Bridge to that provided by the Bridge Root Port.
– backup: Backup Port if the Bridge is the Designated Bridge for the attached
LAN. Backup Port acts as a backup (after failure) for the path provided by a
Designated Port in the direction of the leaves of the Spanning Tree. Backup
Ports exist only where there are two or more connections from a given Bridge
to a given LAN.
– disabled: the Port has no role within the operation of Spanning Tree.
– master: the Port provides connectivity from this Region to a Root that lies into
another Region.
• Port Path Cost: contribution of this port to the path cost of paths towards the
spanning tree root that include this port. 802.1D recommends that the default value
of this parameter be in inverse proportion to the speed of the attached LAN;
(examples: 10Mbs=100, 100Mbs=19, 1Gbs=4).
• Port Designed Root: unique Bridge Identifier of the Bridge recorded as the Root
Bridge in the Configuration BPDUs transmitted by the Designated Bridge for the
segment to which the port is attached.
• Port Designed Cost: path cost of the Designated Port of the segment connected to
this port. This value is summed to the Port Path Cost.
• Port Designed Bridge: Identifier of the bridge that this port considers to be the
Designated Bridge for the LAN attached to this port.
• Port Designed Pt Number: number of the designated port, in decimal format
• Port Designed Pt Priority: priority of the designated port, in decimal format
• Forward Transition: number of times this port has switched from Learning state to
the Forwarding state.
• Port Admin Conn Type: administrative connection type of the port, from the STP
point of view, i.e. its connectivity state for BPDU frames transport, to identify the
topological situation of current port. This parameter is used to optimize the Rapid
STP (RSTP). The following values are available:
– autopointtopoint: the connection state of the port is automatically sensed, by
means of an auto-test, and notified on the parameter below:
PortOperAdminConn Type
– edgeport: the port is a “target" port, situated at the edge of the STP network, it
can be connected to other adjacent networks; this connection blocks the BPDU
frames towards the external network.
............................................................................................................................................................................................................................................................
4 - 14 2 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
– pointtopoint: the port is directly connected, in point-to-point mode, to another

bridge of the network
– nopointtopoint: the port is connected not directly to another bridge of the
network; it is connected across other shared media or devices such as: shared
LAN’s, Hubs, etc.
• Port Oper Admin Conn Type: notification about current operational connection type
of the port.
Figure 4-86 BridgePort: STP-PerPort Management
Figure 4-87 BridgePort: STP-PerPort Management (MSTI case)
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 4 3
............................................................................................................................................................................................................................................................
MST Region Management by CIST of the Bridge Port

This function is activated, when the STP-Protocol Type is MSTP, in the Configure (Virtual
or Provider) BridgePort window (see Figure 4-78, (pg. 4-129)), after clicking on
the key of the Region Number item on the CIST management area.
The function of this option is to set the Region information for the use of MSTP instances.
It contains the following fields:
• Region Number: it is the Region Number as indicated in 802.1Q-2003 std.
• Name: text string encoded within a fixed field of 32 octets. This value is settable by the
operator, but must be the same for all the bridges belonging to the same MST Region.
• Revision Level: integer number encoded within a fixed field of 2 octets (65535). This
value is settable by the operator, but must be the same for all the bridges belonging to
the same MST Region.
• Format Selector: format of the setting. Value 0 indicates the compliance to 802.1Q-
2003 std.
• Digset: it defines the Configuration Digest as indicated in 802.1Q-2003 std., it is a
code of 16 octets of type HMAC-MD5 (see IETF RFC 2104). This value is
automatically calculated by the MSTP procedure, after the setting of the MST
instances.
Important! In order to be part of the same Region, all the Bridges
of that Region must have the same values for the following
parameters: Name, Revision Level, Format Selector, Digest.
The Show List key opens the Figure 4-89, (pg. 4-145) showing the MST Region Instance
List.
Note: The Show List will be updated only after the operations
described in next “MSTID Management by the MSTI of the Bridge
Port” (p. 4-145).
............................................................................................................................................................................................................................................................
4 - 14 4 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-88 Bridge Port: CIST: MST Region Management
Figure 4-89 Bridge Port: CIST: MST Region List
MSTID Management by the MSTI of the Bridge Port

This function is activated in the Configure (Virtual or Provider) BridgePort window (see
Figure 4-78, (pg. 4-129)), after clicking on the key of the MSTID item on the MSTI
management area
The function of this option is to create an MST Instance (MSTI), and to associate one or
more VLAN’s to an active MSTID.
Important! The Instances creation are valid for the entire Bridge
node, and not only for the selected Port. I.e. the same Instances
created on a port are valid at all the other ports of the Bridge, and
any port sees the same Instances of the other Ports.
It contains a table having the following columns:
• MSTID: (MST Instance Identifier) range 0 to 63
Note: 0 is not usable because it is used for the Common, or
global, Instance (CIST).
• Status: notInService / active; this status can be changed from notInService to active
by using the Create key. Or from active to notInService by using the Delete key.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 4 5
............................................................................................................................................................................................................................................................
The Create key permits to switch the selected entry from notInService to active, thus
creating the MST Instance.
Assignment Management of VLANs to the Instances:
If the Status of the selected MSTID instance is active, then the Assign key will open the
Figure 4-91, (pg. 4-147), that lists all the possible VLANs id., from 1 to 4094. The
association of one or more VLAN’s is possible, by selecting on the list (more VLANs
selections are possible, by moving the mouse by keeping pressed its left button and
contemporary pressing the <SHIFT> key on the keyboard; or individually, by using the
mouse button and the <CTRL> key of the keyboard on the desired VLANs).
The assignment of a VLAN to an MSTID implies the cancellation of the same VLAN
association from the MSTID = 0 or from any other MSTID, if existing. I.e. one VLAN
can be associated only to one MSTID, any subsequent association of the same VLAN
to another Instance implies the transfer of this VLAN from the previous association to
the actual.
The association of a VLAN to a certain MSTI can be deleted by doing the association
of that VLAN to the MSTI = 0.
The Details key shows the list of VLAN’s associated to the selected active MSTID, see
Figure 4-92, (pg. 4-147). (The Reset key can be used to delete a selected assignment).
The Delete key permits to switch the selected MSTID entry from active to notInService.
After deleting an MSTID, all VLAN’s to it associated are automatically transferred to
MSTID = 0.
The Ok key permits to confirm this MSTID setting, returning to Figure 4-78, (pg. 4-129),
where the PerBridge and PerPort parameters related to this selected MSTID can then be
configured.
............................................................................................................................................................................................................................................................
4 - 14 6 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-90 Bridge Port: MSTI: MSTI Management
Figure 4-91 Bridge Port: MSTI: MSTID/VLAN Assignment
Figure 4-92 Bridge Port: MSTI: MSTID/VLAN List
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 4 7
............................................................................................................................................................................................................................................................
Bridge Port Properties of the Ethernet Port

This option is obtained, after selecting a MAC, or Virtual, or Provider Bridge port
(i.e. with Admin Status = up) or a LAG ( with Admin Status = up), by
means of the contextual pop-up menu, or by selecting in the menu-bar:
Transmission Î Ethernet Port Management Î Bridge Port Management Î Bridge Port
Properties (MAC or Virtual or Provider case).
Transmission Î Aggregator Î Bridge Port Management Î Bridge Port Properties.
An example of the window displayed is reported in Figure 4-93, (pg. 4-148) (Provider
Bridge case)
Bridge ETB Port.
for “Configure Bridge Port (Virtual)” (p. 4-130), “Configure Bridge Port (Provider)”
(p. 4-125), “Configure Bridge Port (MAC)” (p. 4-133).
Figure 4-93 Bridge Port Properties (Provider/MSTP case)
............................................................................................................................................................................................................................................................
4 - 14 8 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Show VLAN Info of the Ethernet Bridge Port

This option is obtained, after selecting an active Virtual (or Provider) Bridge ETB port
(i.e. with Admin Status = up) or a LAG ( with Admin Status = up), by
Transmission Î Ethernet Port Management Î Bridge Port Management Î Show VLAN Info
Transmission Î Aggregator Î Bridge Port Management Î Show VLAN Info.
WARNING
This option is operative only if the selected ETB Port is in up state (i.e. the
associated ETS port is in up state too).
This option is not operative if Bridge Type = bridge 802.1D (MAC), as referred
in “Configure ISA” (p. 4-62).
The function of this option is to show the VLAN's afferent to this selected ETB Port, and,
correspondingly, the state of the port with respect to that VLAN, with its tagged/untagged
(Format Outgoing Frames) condition.
The VLAN registered on this port are listed, and, correspondingly, the state of the port
with respect to that VLAN, with its Format-Outgoing-Frames: tagged/untagged
condition.
The state of the Port can be: dynamic, or blocked, or forwarding, or disabled (the
meanings of these states are as explained in “STP-PerPort Management by the
ControlPlane of the Bridge Port” (p. 4-140)).
Figure 4-94 Show VLAN Info
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 4 9
............................................................................................................................................................................................................................................................
Configure Queue for the Ethernet Port

This option is obtained, after selecting an Ethernet port ( or ), by means of the
Transmission Î Ethernet Port Management Î Queue (Qos) Management Î Configure Queue
For more details see explanations in “Traffic Descriptor, Forwarding Priority and Class of
The function of this option is to set the Queueing parameters for this selected Port, such as
Shaping Rate, etc.
• Queueing Handling Per-Port sector:
The shaping provides to adapt the incoming traffic to the available output bandwidth,
by smoothing the prospective peaks. It is configured by means of two parameters:
• Mean Shaping Rate: egress shaping rate (sustained rate permitted by egress traffic
shaping) in kb/s. Value 0 means that the egress shaping rate limitation is disabled:
this is the default value.
WARNING
This value must be congruent with the Rate Limiting parameter defined in
Configure remote Port (see “Bandwidth matching” (p. 4-87)).
• Burst Shaping Rate: amount of burst traffic (in bytes) that can be moulded on the
egress. Value 0 means that the egress burst shaping limitation is disabled: this is the
default value.
The following parameters are available only in case of Bridge Type = bridge 802.1S-AD
(Provider):
• Scheduling Discipline. Possible options:
– WorkConserving: (only for weighted queues), empty queues are skipped, by
the WDRR (Weighted Deficit Round Robin) algorithm of the scheduler.
– NonWorkConserving: not available in current release. Empty queues are
served too, by the WDRR.
• Forwarding Class Num...: range 0 to 7; this field (together with the following Queue
Number) permits to create a QoS Customer Profile (not operative in current
release) that overrides the value (8P0D or 5P3D) set in “Configure ISA” (p. 4-62).
the key opens the Forwarding Class Mapping dialogue as in Figure 4-96, (pg.
4-152), that permits to set:
– Egress FC Queue: it indicates the egress queue where the Forwarding Class
will be sent. The key permits to view the Forwarding Class Mapping
properties, as above described, but in read-only mode
............................................................................................................................................................................................................................................................
4 - 15 0 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• Queue Number: range 0 to 3; this field (together with the following Queue
Number) permits to create a QoS Customer Profile (not operative in current
release) . Only the QueueWeight can be set. For more details see “Traffic
Descriptor, Forwarding Priority and Class of Service” (p. 4-54).
the key opens the Management Queue dialogue as in Figure 4-97, (pg. 4-152),
that permits to set:
Queue Type: possible options:
– Weightedbandwidth: weight and priority are considered, in forwarding
operations ...
– strictPriority: only priority is considered, in forwarding operations. The
highest priority queue is forwarded firstly; once it is emptied, the forwarding
passes to the lower queue, and so on. ...
• Queue Weight: (applicable only in case of weightedbandwidth); weight to be
applied for the selected Queue, on forwarding operations. It is supposed to be
proportional to the forwarding priority of the traffic ...
the key permits to view the “Management Queue" properties, as above
described, but in read-only mode
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 5 1
............................................................................................................................................................................................................................................................
Figure 4-95 Queue (QoS) Management
Virtual/MAC Bridge case
Provider Bridge case
Figure 4-96 QoS Management: Forwarding Class Number
Figure 4-97 QoS Management: Queue Number
Properties Queue for the Ethernet Port

This option is obtained, after selecting an Ethernet port ( or ), by means of the
Transmission Î Ethernet Port Management Î Queue (Qos) Management Î Properties
Queue
............................................................................................................................................................................................................................................................
4 - 15 2 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................

The function of this option is to show the Queueing parameters for this selected Port. All
the reported information fields are in read-only mode, and their meaning is described in
“Configure Queue for the Ethernet Port” (p. 4-150).
In case of Bridge Type = bridge 802.1S-AD (Provider) only, it will open, by means of:
• List Forwarding Class button: (see Figure 4-99, (pg. 4-154)):
it reports the ForwardingClassMapping; i.e. the association between the Priority
ForwardingClass (FC) and ForwardingQueue (FQ) that has been set. For instance, in
5P3D case, the FC#0 and FC#1 are associated to the FQ# 1 etc.
In this figure the PCP= 5P3D configuration is illustrated (in 8P0D it is similar). The
PCP value is set “Configure ISA” (p. 4-62).
• List Queue button: (see Figure 4-100, (pg. 4-154)):
it reports the List of the Queues and their relevant parameters:
• Queue Number: it is the number of the ForwardingQueue (FQ)
• Queue Type: strictPriority or WeightedBandwidth
• Queue Weight: value of the weights for the queues, assigned by default or by the
operator as seen in Figure 4-97, (pg. 4-152).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 5 3
............................................................................................................................................................................................................................................................
Figure 4-98 Queue (QoS) Properties
Virtual/MAC Bridge case
Provider Bridge case
Figure 4-99 QoS Properties: Forwarding Class Mapping
Figure 4-100 QoS Properties: Queue Number List
............................................................................................................................................................................................................................................................
4 - 15 4 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Configure IGMP
This option is obtained, after selecting the ISA-ES Node ( ), by means of the
Transmission Î ISA Management Î IGMP Management Î Configure IGMP
WARNING
This option is not allowed for Bridge Type = bridge 802.1D (MAC) case.
The VLAN’s to be associated to IGMP should be already registered.
The function of this option is to set the IGMP (Internet Group Management Protocol)
parameters for the ISA node, common to all the ports. Some general details about IGMP
are described in “Resource Management Indication” (p. 1-64).
The first window presented by the option permits to select the VLAN-ID to be associated
to the IGMP group. The following parameters are displayed:
• VLAN Range... From ... To: a range of VLAN-Id to be searched can be defined; default
is 1 to 100.
Subsequently, after clicking on Search key, the VLAN’s already associated to an IGMP
instance are displayed in the table.
• VLAN Index: identifier of the VLAN’s already associated to IGMP
• Proxy Report Enabling Possible values:
– enabled means that the VLAN delegates the ES (acting as Proxy) to report to the
Router one summarized collective message, together with the other VLAN’s
involved in the same IGMP group.
– disabled means that this VLAN is not interested in the collective Proxy reporting.
• Create: this key permits to associate a new VLAN to the IGMP instance, by opening
the dialog window reported in Figure 4-102, (pg. 4-157). See next “VLAN
association” (p. 4-156).
The other keys presented at the bottom of the window are:
• Modify: it permits to modify the IGMP parameters for the selected VLAN of the above
list.
• Details: it permits to check the IGMP parameters associated to the selected VLAN of
the list.
• Delete: to de-associate from the IGMP instance the selected VLAN.
• Cancel: to close the window
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 5 5
............................................................................................................................................................................................................................................................
Figure 4-101 ISA: IGMP Snooping Management List
VLAN association
After clicking on the Create key of the window described in the previous paragraph, the
dialog box reported in Figure 4-102, (pg. 4-157) will be displayed.
It contains the following parameters:
• VLAN ID: it permits to choose the Vlan to be associated to the IGMP instance.
the key opens one VLAN Search dialog box, in order to select the desired VLAN-
Id among all the registered VLAN’s of the ES.
• IGMP Status: possible values: up / down, (read-only, set by the system); up means that
this ISA-ES node is enabled to support the IGMP function.
• Proxy Report Enabling Possible values:
– enabled means that this VLAN delegates the ES (acting as Proxy) to report to the
Router one summarized collective message, together with the other VLAN’s
involved in the same IGMP group.
– disabled means that this VLAN is not interested in the collective Proxy reporting.
In this case all the reports from the members of the IGMP group are forwarded
transparently to the router.
• Group Memb interval(s): amount of time (in sec.) after which the IP router can check if
no other member of this IGMP group is interested in the multicast transmission, if no
Report from users is sent in this interval.
............................................................................................................................................................................................................................................................
4 - 15 6 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• Router Timeout(s): time interval (in sec.) for the ES node for dynamically refreshing
the list of existing IP Multicast Routers. After this time, not alive Routers are deleted
from the list.
• Query Max Response Time (1/10s): max amount of time (in 1/10sec.) for the users
(hosts) to respond to a query from the ES-Proxy (or from the IP Router).
• Last Memb Query Count: (LMQC), number of counts of next parameter
LastMemberQueryInterval, for the IP Router, before it establishes that no other
member of this IGMP group is present and thus removing the multicast transmission.
• Last Memb Query Interval (1/10s): (LMQI), time interval, for the IP Router, between the
queries sent from the Router to the users, to check if any other member is present on
this IGMP group.
Note: The product of the two previous parameters
(LMQC*LMQI) gives the time, for the IP Router, to establish that
no other member of this IGMP group is present and thus removing
the multicast transmission.
• Snooping Proxy Version Possible values:
– V1: it supports the IGMP Query from the Router and the Reports from users.
– V2: it supports, in addition to V1 features, the fast leave of a user from the IGMP
group.
– V3: (not supported in current release) it supports also the Source Filtering features:
i.e. the possibility, for users, to select some specific sources of Multicast traffic,
among all the existing ones in the network.
The Ok key confirms the selected parameters.
The Cancel key permits to close the window without associating a VLAN. Click on Help to
get aids about this function.
Figure 4-102 ISA: IGMP Snooping, VLAN association
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 5 7
............................................................................................................................................................................................................................................................
IGMP Properties
This option is obtained, after selecting the ISA-ES Node ( ), by means of the
Transmission Î ISA Management Î IGMP Management Î IGMP Properties
WARNING
This option is not allowed for MAC Bridge case.
The function of this option is to show the IGMP parameters for the ISA-ES Node.
The displayed parameters (presented by clicking on the unique Details key) are read-only
and their meanings are as explained in “Configure IGMP” (p. 4-155).
Configure IGMP for the Ethernet Port

This option is obtained, after selecting an active Port ( ), by means of the contextual
Transmission Î Ethernet Port Management Î IGMP Management Î Configure IGMP"
WARNING
This option is not possible for Bridge Type = bridge 802.1D (MAC) case.
Allowed for up ETB Ports only, on Bridge Type = bridge 802.1Q (Virtual).
Allowed for up ETB and ETS Ports on Bridge Type = bridge 802.1S-AD
(Provider).
Some general details about IGMP are described in “Resource Management Indication”
(p. 1-64).
The function of this option is to set the IGMP parameters for this selected Port, such as
Fast Leave, StaticRouterPort, etc.
WARNING
This association is performed for one VLAN at a time; if more VLAN’s are to be
associated to IGMP by means of this port, the operation must be repeated for
each VLAN.
• Port Label: read-only field, set by the system to the selected Port.
• VLAN ID: it permits to choose the Vlan to be associated to the IGMP instance.
the key opens one VLAN Search dialog box, in order to select the desired
VLAN-Id among all the registered VLAN’s on this Port.
• Fast Leave Per Port Possible values:
............................................................................................................................................................................................................................................................
4 - 15 8 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
– enabled means that this Port permits the FastLeave, i.e. the removal of the
Multicast traffic on this Port, upon receiving a single “Leave Report” from a user
connected on this Port.
Note: This type of Leave procedure is advisable to be used when
only one single user is connected behind the selected VLAN on that
port.
– disabled means that this Port does not permit the FastLeave procedure. In this case
the Router has to send some queries in order to check if other members of the
IGMP group registered on this Port are interested in the Multicast transmission.
• Static Router Per Port Possible values:
– enabled means that this Port is statically connected to the IP Multicast Router.
– disabled means that this one is not the Port towards the IP Multicast Router.
The Cancel key permits to close the window without confirming this setting. Click on Help
to get aids about this function.
Figure 4-103 Port: IGMP Services Management
IGMP Properties for the Ethernet Port

This option is obtained, after selecting an active Port ( ), by means of the contextual
Transmission Î Ethernet Port Management Î IGMP Management Î IGMP Properties"
WARNING
Allowed for ETB Ports only, on Bridge Type = bridge 802.1Q (Virtual) .
Allowed for ETB and ETS Ports, on Bridge Type = bridge 802.1S-AD
(Provider).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 5 9
............................................................................................................................................................................................................................................................

Some general details about IGMP are described in “Resource Management Indication”
(p. 1-64).
The function of this option is to show the IGMP parameters and services set for this
selected Port.
The following parameters are displayed:
• PortID: read-only field, set by the system, index of the selected Port.
• Port Name: read-only field, set by the system, name of selected Port.
• VLAN ID ... From ... To: a range of VLAN-Id to be searched can be defined; default is 1
to 100.
Subsequently, after clicking on Search key, the VLAN’s associated to an IGMP
instance by means of this Port are displayed in the table.
• VLAN ID: identifier of the VLAN’s associated to IGMP on this Port
• Fast Leave Possible values:
– up means that the FastLeave feature is enabled on this VLAN.
– down the FastLeave feature is disabled on this VLAN.
• Static Router Port Status Possible values:
– up means that this one is the Port statically connected to the IP Multicast Router
for the related VLAN.
– down this one is not the Port towards the IP Multicast Router for the related
VLAN.
• Dynamic Router Port IP Address Actual IP Address of the IP Multicast Router for the
related VLAN (it will show the IP address only in case this port is the Router Port).
In the lower part there is the VLAN ID field which shows the possible other VLAN-Id’s
associated to the same IGMP group. To this field ia associated the Request Membership
Group key which allows to show the IGMP group parameters associated to the selected
VLAN; it opens the property window reported in Figure 4-105, (pg. 4-161), reporting the
following tabled information:
– VLAN ID: identifier of possible other VLAN-Id’s associated to the same IGMP
group
– PORT ID: identifier of the Port on which the related VLAN is associated
– Member IP Address: Multicast IP Group address to which this VLAN is associated
– V3 Source IP Address: IP source address used by ES for sending collective Proxy
Reports to the Router (meaningful only if IGMP version V3 is used).
– Version: IGMP version (V1 or V2 or V3)
............................................................................................................................................................................................................................................................
4 - 16 0 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
– V3 Group Type: meaningful only if IGMP version V3 is used, to identify the Group
type.
The other keys presented at the bottom of the windows are:
• Close: to close the window
• Help: to get aids about this window.
Figure 4-104 Port: IGMP Services Properties List
Figure 4-105 Port: IGMP Request Membership Group
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 6 1
............................................................................................................................................................................................................................................................
Configure IGMP for the Aggregator

This option is obtained, after selecting an active Aggregator (LAG ), by means of the
Transmission Î Aggregator Î IGMP Management Î Configure IGMP
WARNING
Allowed for ETB LAGs only, on Bridge Type = bridge 802.1Q (Virtual).
Allowed for ETB and ETS LAGs, on Bridge Type = bridge 802.1S-AD
(Provider).
The use of this option is the same of that used for EthernetPort described in “Configure
IGMP for the Ethernet Port” (p. 4-158).
IGMP Properties of the Aggregator

This option is obtained, after selecting an active Aggregator (LAG ), by means of the
Transmission Î Aggregator Î IGMP Management Î IGMP Properties
WARNING
Allowed for ETB LAGs only, on Bridge Type = bridge 802.1Q (Virtual).
Allowed for ETB and ETS LAGs, on Bridge Type = bridge 802.1S-AD
(Provider).
The use of this option is the same of the one used for EthernetPort described in “IGMP
Properties for the Ethernet Port” (p. 4-159).
............................................................................................................................................................................................................................................................
4 - 16 2 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Ethernet Ring Protection

This feature gives the possibility to operator to configure the protocol ERP on either per
Port or per VLAN related these ISA boards. This feature has been subdivided in two sub-
functionality: ERP Topology and ERP Instance. The first sub-functionality to permit to
create the physical part of the ERP instead the second sub-functionality to permit the
logical ERP.
This option is obtained, after selecting the Bridge node ( , by means of the contextual
Transmission Î ISA Management Î ERP Management
Figure 4-106 Pop-up menu ERP Management
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 6 3
............................................................................................................................................................................................................................................................
In the popup menu, for ERP Management option will be displayed:

1. Configure Physical ERP
When the operator wants to handle the physical ERP functionality it needs to select the
ERP Management Î Configure Physical ERP menu path. allocated on the root of the
resource tree of the USM, as referred in “Configure Physical ERP (Topologies)”
(p. 4-164).
2. Configure Logical ERP
When the operator wants to handle the logical ERP functionality it needs to select the
ERP Management Î Configure Logical ERP menu path. allocated on the root of the
resource tree of the USM , as referred in “Configure Logical ERP (Instances)”
(p. 4-173).
Configure Physical ERP (Topologies)

Following the Transmission Î ISA Management Î ERP Management Î Configure Physical
ERP menu path in Figure 4-106, (pg. 4-163), the following secondary window will be
displayed:
Figure 4-107 Configure ERP - Topologies
This secondary window is used to manage completely the following operations:

• “Retrieve ERP Topologies” (p. 4-165) already created.
• “Create ERP Topology” (p. 4-165) by means of Create button.
• “Modify ERP Topology” (p. 4-170) already presents, by means of Modify button.
• “Delete ERP” (p. 4-173) already presents, by means of Delete button.
The Close button is used to execute the closure of the secondary window, Print button is
used to print the ERP topologies and Help button is used to have more information about
this functionality.
............................................................................................................................................................................................................................................................
4 - 16 4 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Retrieve ERP Topologies

The high part of the secondary window in Figure 4-107, (pg. 4-164), when it is opened,
shows a table which contains all Ethernet Ring Protection topologies that are present on
NE. This table have different columns:
• Name: it contains an identifier of the ERP topology, it is composed from a prefix
ERPT# and a suffix representing the index of the ERP topology itself.
• Label: it contains the label associated to this ERP topology.
• Interconnection Node: it contains a flag to indicate if the ERP Topology represents a
major on sub ring. For default this flag is set to false value representing a major ring
where two interfaces are defined one as east port and other as west port, instead when
the value of this attribute is to set to true value then only an interface is defined as east
or west.
• Status: it contains the indication of status of the ERP topology, in fact the possible
values are: active and notInService.
• East Port: it contains the operator label of the interface selected as such.
• West Port: it contains the operator label of the interface selected as such.
• Primary Flag: it contains an Boolean flag valid only for Link Aggregation Group.
Create ERP Topology

The button Create of the secondary window in Figure 4-107, (pg. 4-164) is used to create
a new ERP topology, when the operator clicks on this button the following secondary
window is opened:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 6 5
............................................................................................................................................................................................................................................................
Figure 4-108 Create Ethernet Ring Protection Topology, LAG and Ethernet
Interfaces
This secondary window is subdivided in tow parts:

• Configuration
It contains all information related to the ERP topology.
– Name: it is contained name of the ERP topology.
– Label: it is permitted to insert the name of the label associated to this ERP
topology; the length of this string could max 30 characters.
– Status: it is permitted to select the possible value related to the status of this ERP
topology
– Interconnection Node: it is permitted to select the possible value of this attribute
per this ERP topology.
• Port Management
It contains all information related to the ports defined for this topology.
– Port Qualifier: it is permitted to select the qualifier of the interface.
– Port Identifier : it is contained the operator label of the interface selected.
– Primary Flag: it is permitted to select the value of this flag, it is meaning only
when the interface selected is a Link Aggregation Group in fact in this case the
correspondent graphical object is enable instead in opposite case it is disable. This
object is not supported by boards.
............................................................................................................................................................................................................................................................
4 - 16 6 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
When the value's Interconnection Node attribute is False, the second part of this
secondary window contains two sub-sections each for each single interface; in this
scenario the value of the Port Qualifier attribute cannot contain the same value.
Figure 4-109 Create ERP Topology, Ethernet Interfaces
Interconnection Node as “True”
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 6 7
............................................................................................................................................................................................................................................................
Figure 4-110 Create ERP Topology, LAG Interfaces - Interconnection Node as true
When the selecting button near the Port Identifier is pressed the secondary window
is opened:
............................................................................................................................................................................................................................................................
4 - 16 8 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-111 Search LAG or Ethernet Interfaces
This window have two tabs activated:

• Ethernet Port for retrieval of the Ethernet Port
• LAG, for retrieval of Link Aggregation Group
The retrieval is executed when the operator presses on Search button, and selecting a row
present into table the Apply button is enabled. This last button is used to set the interface
as east or west port of ERP topology.
For the board ISA ES1/4 release 3.0 only LAG or Ethernet interfaces with client ETB can
been selected. The attribute Interconnection Node cannot modify.
The Figure , (pg. 4-167) and Figure 4-110, (pg. 4-168) are present only for scope of
completeness because the only value of the Interconnection Node cannot modify in fact
the only value can be assume is the default value (i.e. False). The graphical object
Interconnection Node in Figure 4-109, (pg. 4-167) must be disabled.
The creation operation is executed when the operator presses Ok button of
Figure 4-108, (pg. 4-166) or Figure 4-109, (pg. 4-167) or Figure , (pg. 4-167) or
Figure 4-110, (pg. 4-168) window, instead if the operator does not want to execute it
more, it needs to press the Cancel button. The Help button is used to have more
information about the functionality.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 6 9
............................................................................................................................................................................................................................................................
Modify ERP Topology

The button Modify of the secondary window in Figure 4-107, (pg. 4-164) is used to
modify an existing ERP topology, it is enabled only when an ERP topology present in
above table has been selected, when the operator pressed this button the following
secondary window is opened.
Figure 4-112 Modify ERP Topology, Ethernet Interfaces
This window permits to change these fields:

• Label: it contains the label's name that could be modified; the length of this string
could max 30 characters.
• Status: it contains the information related to the status of the ERP topology that could
be modified.
• Interconnection Node: it contains the information related to this attribute, that could
be modified.
When the value's Interconnection Node is change from False (i.e. default value ) to True
we can have these possible layout:
............................................................................................................................................................................................................................................................
4 - 17 0 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-113 Modify ERP Topology, Ethernet Interface - Interconnection Node as

True
In this case it is possible to execute the following changes:

• to select a new Ethernet Interface using the selection button near the Port
Identifier.
• to select a value for the Port Qualifier.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 7 1
............................................................................................................................................................................................................................................................
Figure 4-114 Modify EERP Topology, LAG Interface - Interconnection Node as True
In this case it is possible to execute the following changes:

• to select a new LAG Interface using the selection button near the Port Identifier.
• to select a value for the Port Qualifier.
• to select a value for the Primary Flag.
The modification operation is executed when the operator presses Ok button of window in
Figure 4-112, (pg. 4-170) or Figure 4-113, (pg. 4-171) or Figure 4-114, (pg. 4-172),
instead if the operator does not want to execute it more, it needs to press the Cancel
button. The Help button is used to have more information about the functionality.
Important! The Interconnection Node attribute present in the
Figure 4-112, (pg. 4-170) must be disabled because this
modification is not permitted, because this selection is possible only
at creation time of the ERP Topology (see Figure Create ERP
Topology) in the release 3.0 of all boards only a value is admissible
that is default value, the Figure 4-113, (pg. 4-171) and
Figure 4-114, (pg. 4-172) have been built only for completeness in
case this restriction will be removed.
............................................................................................................................................................................................................................................................
4 - 17 2 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Delete ERP
When the operator wants to remove a ERP topology it will be necessary to select it into
table of the secondary window in Figure 4-107, (pg. 4-164), only in this case the Delete
button is enabled, and after he/she must press the Delete enabled button and the following
confirmation message is shown:
Figure 4-115 Delete EERP Topology - Confirmation Message
Selecting Yes the selected ERP Topology will be removed instead selecting No no
operation will be done.
Configure Logical ERP (Instances)

Following the Transmission Î ISA Management Î ERP Management Î Configure Logical
ERP menu path in Figure 4-106, (pg. 4-163), the following secondary window will be
displayed:
Figure 4-116 Configure ERP - Instances
This secondary window is used to manage completely the following operations:

............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 7 3
............................................................................................................................................................................................................................................................
• “Retrieve the ERP Instances” (p. 4-174) already created.

• “Create an ERP Instance” (p. 4-174) by means of Create button.
• “Modify ERP instance” (p. 4-179) already presents, by means of Modify button.
• “Delete ERP Instance” (p. 4-186) already presents, by means of Delete button.
The Close button is used to execute the closure of the secondary window, Print button is
used to print the ERP topologies and Help button is used to have more information about
this functionality.
Retrieve the ERP Instances

The high part of the secondary window in Figure 4-116, (pg. 4-173), when it is opened,
shows a table which contains all Ethernet Ring Protection instances that are present on
NE. This table have different columns:
• Name: it contains an identifier of the ERP instances, it is composed from a prefix
ERP# and a suffix representing the index of the ERP topology following form
character # plus index of ERP instance itself.
• Label: it contains the label associated to this ERP instance.
• Ring Id: it contains an identifier of the ring, it can assume a possible integer in the
range [1,..,239].
• MD Level: it contains maintenance level of the ERP instance, it can assume a possible
integer in the range [0,..7].
• RowStatus: it contains the information about the status of row of an ERP instance, in
fact the possible values are: active and notInService.
• Rpl Owner: it contains the information about Rpl Owner of an ERP instance.
• Scope: it contains the scope of an ERP instance, it can assume a possible value in the
set {perPort, perVLAN}
• Ring VLan Id: it contains the VID an ERP instance, it can assume a possible values in
the range [1,..,4094]
• Status: it contains the information about the status of an ERP instance, it can assume a
possible value in the set: deactivated, idle , protection , manualSwitch,
forcedSwitch, pending.
Create an ERP Instance

a new ERP instance, when the operator clicks on this button the following secondary
window is opened:
............................................................................................................................................................................................................................................................
4 - 17 4 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-117 Create ERP Instance - Configuration Tab
This secondary window is subdivided in tow tabs:

– Configuration tab contains all information related to the ERP instances, as
described in “Configuration tab” (p. 4-175).
– Defects tab contains all information related to the interested defects to this ERP
instance, as described in “Defects tab” (p. 4-179).
1. Configuration tab
It contains all information related to the ERP instances.
• Topology: it contains name of the ERP topology to which this ERP instance
belongs.
• Label: it permits to insert the name of the label associated to this ERP instance;
the length of this string could max 30 characters.
• VLan Drop Enable: it permits to insert Drop Enable bit value used in this VLAN,
this attribute is not managed for this reason this graphical object will be disabled.
• Rpl Owner: it permits to insert the information about Rpl Owner of an ERP
instance.
• Flush Control Enable: it permits to enable or disable Automatic Flush propagation
Control applied to ERP instance, this attribute is not managed for this reason this
graphical object will be disabled.
• Ring Id: it permits to insert an identifier of the ring, it can assume a possible integer
in the range [1,..,239].
• Ring VLan Id: it permits to insert the VID of an ERP instance, it can assume a
possible values in the range [1,..,4094]
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 7 5
............................................................................................................................................................................................................................................................
• MD Level: it permits to insert the maintenance level of the ERP instance, it can
assume a possible integer in the range [0,..7].
• RowStatus: it permits to insert the status of row of an ERP instance, in fact the
possible values are: active and notInService.
• Status: it contains the information about the status of an ERP instance, it can
assume a possible value in the set: deactivated, idle , protection ,
manualSwitch, forcedSwitch, pending.
• Version: it permits to select the version of the protocol ERP, this attribute is not
managed for this reason this graphical object will be disabled.
• Revertive: it permits to select the value of this attribute, but it is not managed for
this reason this graphical object will be disabled.
• VLan Priority: it permits to insert the value of this attribute, it can assume a
possible value in the range [0,..7].
• Scope: it permits to insert the value of this attribute, it can assume a possible value
in the set {perVLAN, perPort}. This change can be done only at creation time,
after the creation it cannot be modified more.
• Asap Name: it permits to insert ASAP's name to associate to this ERP instance.
The sub-section Times groups three possible time attributes:
• Guard (10ms): it permits to insert the possible value for this attribute, this value
can assume a value in the range [1,..,200], default value is 50 and the
measurement unit is 10ms.
• HoldOff (100ms): it permits to insert the possible value for this attribute, this value
can assume a value in the range [0,..,100], default value is 0 and the measurement
unit is 100ms.
• WaitToRestore (1min): it permits to insert the possible value for this attribute, this
value can assume a value in the range [0,..,12], default value is 5 and the
measurement unit is 1min.
selection button near the Topology in Figure 4-117, (pg. 4-175), is used to select
the ERP topology to associate to ERP instance, when the operator presses this
selection button the following secondary window is shown:
............................................................................................................................................................................................................................................................
4 - 17 6 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-118 Search ERP Topology
When a row into table of this window is selected then button Ok is enabled, it is used
to associate the selected ERP topology. The Search button is used to populate the table
and, the search operation can be executed indicating a possible range, this range has a
step equal to 8. For example [1,..,8],[9,..,16] etc…
The Cancel button is used to close this window without executing any selection.
The Help button is used to have more information about this feature.
When no selection has been done the layout of the this window is the following:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 7 7
............................................................................................................................................................................................................................................................
Figure 4-119 Search ERP Topology - No selection
Pressing the key near the Asap Name in Figure 4-117, (pg. 4-175), it is possible
to select the Alarm Severity Profile to associate to ERP instance, when the operator
presses this selection button can follow procedure described in “Alarms Severity
(ASAP management) in Configuration menu” (p. 4-33).
The key gives the asap properties currently associated to this resource
............................................................................................................................................................................................................................................................
4 - 17 8 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
2. Defects tab
It contains all information related to the interested defects to this ERP instance.
Figure 4-120 Create ERP Instance - Defects tab
This tab contains all information about the defects to which this ERP instance is
interested.
The validation box allow to check or not check the relevant defect, that are:
– Critical Link Event (CLE)
– Auto Negotiation Mismatch (ANM)
– Degrade (DEG)
– Partial Loss of Capacity (PLC)
– Alarm Indication Signal (AIS)
– Loss of Continuity (LOC)
– Mis Merge Condition (MMG)
– UNexpected Mep (UNM)
– UNexpected Level (UNL)
Default values are all bits set to 0, that is graphically all objects unchecked.
Modify ERP instance

modify a new ERP instance, when the operator clicks on this button the following
secondary window with different tabs is opened:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 7 9
............................................................................................................................................................................................................................................................
Figure 4-121 Modify ERP Instance - Configuration tab
1. Configuration tab
• Name: it contains the name of the ERP instance that should be modified.
• Label: it permits to change the name of the label associated to this ERP instance,
the length of this string could max 30 characters.
• VLan Drop Enable: it permits to change Drop Enable bit value used in this VLAN,
this attribute is not managed for this reason this graphical object will be disabled.
• Rpl Owner: it permits to change the information about Rpl Owner of an ERP
instance.
• Flush Control Enable: it permits to enable or disable Automatic Flush propagation
Control applied to ERP instance, this attribute is not managed for this reason this
graphical object will be disabled.
• Ring Id: it permits to change an identifier of the ring, it can assume a possible
integer in the range [1,..,239].
• Ring VLan Id: it permits to change the VID of an ERP instance, it can assume a
possible integer in the range [1,..,4094]
• MD Level: it permits to change the maintenance level of the ERP instance, it can
assume a possible integer in the range [0,..7].
• RowStatus: it permits to change the status of row of an ERP instance, in fact the
possible values are: active and notInService.
• Status: it contains the information about the status of an ERP instance, it can
assume a possible value in the set: deactivated, idle , protection ,
manualSwitch, forcedSwitch, pending.
• Version: it permits to change the version of the protocol ERP, this attribute is not
managed for this reason this graphical object will be disabled.
............................................................................................................................................................................................................................................................
4 - 18 0 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• Revertive: it permits to change the value of this attribute, but it is not managed for
this reason this graphical object will be disabled.
• Switch Command: it permits to change the value of this attribute, the possible
values are {clear, wFS, eFS}, The button Send is used to execute the switch while
the secondary window is opened yet.
• VLan Priority: it permits to change the value of this attribute, it can assume a
possible integer in the range [0,..,7].
• Scope: it permits to change the value of this attribute, it can assume a possible
value in the set {perPort or perVLAN}. This change can be done only at creation
time, after the creation it cannot be modified more, then it means that this graphical
object must be disabled in this window opened with this profile.
Important! For the “perVLan” setting, the window content
changes, as detailed in “Modify ERP instance - perVLan case”
(p. 4-189).
• Asap Name: it permits to change ASAP's name to associate to this ERP instance.
Pressing the key near the Asap Name in Figure 4-121, (pg. 4-180), it is
possible to select the Alarm Severity Profile to associate to ERP instance, when the
operator presses this selection button can follow procedure described in ““Alarms
Severity (ASAP management) in Configuration menu” (p. 4-33).
The key gives the asap properties currently associated to this resource
The Times sub-section groups three possible time attributes:
• Guard (10ms): it permits to insert the possible value for this attribute, this value
can assume a value in the range [1,..,200], default value is 50 and the
measurement unit is 10ms.
• HoldOff (100ms): it permits to insert the possible value for this attribute, this value
can assume a value in the range [0,..,100], default value is 0 and the measurement
unit is 100ms.
• WaitToRestore (1min): it permits to insert the possible value for this attribute, this
value can assume a value in the range [0,..,12], default value is 5 and the
measurement unit is 1min.
2. Defects tab
It contains all information about the defects to which this ERP instance is interested.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 8 1
............................................................................................................................................................................................................................................................
Figure 4-122 Modify ERP Instance - Defects tab
The validation box allow to check or not check the relevant defect, that are:
– Critical Link Event (CLE)
– Auto Negotiation Mismatch (ANM)
– Degrade (DEG)
– Partial Loss of Capacity (PLC)
– Alarm Indication Signal (AIS)
– Loss of Continuity (LOC)
– Mis Merge Condition (MMG)
– UNexpected Mep (UNM)
– UNexpected Level (UNL)
3. Interfaces tab - Major Ring case
This tab contains all information related to interfaces involved in the ERP instance.
This tab have two similar sub-sections because the Interconnection Node of the ERP
topology associated is set to False value, that is major ring.
............................................................................................................................................................................................................................................................
4 - 18 2 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-123 Modify ERP Instance - Interfaces tab (Major Ring)
• Port Identifier: it shows the operator label of Interfaces selected as east or west
ports of the associated ERP topology.
• Md Index: it shows the index of selected maintenance domain related to the Mep.
• Ma Index: it shows the index of selected maintenance association related to the
Mep.
• Mep Identifier: it shows the index of selected Mep.
• Rpl Flag: this permits to change the attribute value, default value is false, it is
meaning only when Rpl Owner is set to true value, besides only a port of the ring
could be selected as Ring Protection Link.
• Forwarding Status: it shows the forwarding status of the port. The change of this
value is notified to operator a run-time (i.e. SCN)
• Current Status: it shows the current status of the port.
When the Interconnection Node is set to True value this tab has this layout:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 8 3
............................................................................................................................................................................................................................................................
Figure 4-124 Modify ERP Instance - Interfaces Tab (sub Ring)
The button Reset is used to reset the values the Md Index, Ma Index and Mep
Identifier to values 0, 0, 0.
selection button near the Mep Identifier permits to associate an possible Mep
with direction down to this ERP instance. When the operator presses this selection
button this secondary window is opened:
............................................................................................................................................................................................................................................................
4 - 18 4 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-125 Search Mep with direction down
This window permits to select a Mep that could associate to this ERP instance. The
high part of this window contains:
• MD Index: it permits to insert the index of the Maintenance Domain.
• MA Index: it permits to insert the index of the Maintenance Association.
• Mep Index: it permits to insert a possible range of indexes with a step of the 50
units, e.g. [1,..50], [51,..100] etc.
Button Search is used to invoke the retrieval of the Mep according to the indexes and
the range filled above. The button Ok is enabled when a row has been selected, it is
used to confirm the selection of this Mep to ERP instance. The button Cancel is used
to reject the operation.
4. Alarms tab
This tab contains all information about the alarms associated the ERP instance.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 8 5
............................................................................................................................................................................................................................................................
Figure 4-126 Modify ERP Instance - Alarms tab
Delete ERP Instance

The button Delete of the secondary window in Figure 4-116, (pg. 4-173) is used to delete
an existing ERP Instance, when the operator presses this button the following
Figure 4-127 Remove ERP Instance - Message
To confirm the removal of this ERP instance the button Yes must be pressed instead, if this
operation must be rejected the button No will be selected.
............................................................................................................................................................................................................................................................
4 - 18 6 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Details of an ERP Instance.

The button Details of the secondary window in Figure 4-116, (pg. 4-173) is used to show
only all details of an existing ERP Instance, when the operator presses this button the
following secondary window is opened:
Figure 4-128 Properties ERP Instance - Configuration tab
Figure 4-129 Properties ERP Instance - Defects tab
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 8 7
............................................................................................................................................................................................................................................................
Figure 4-130 Properties ERP Instance - Interfaces tab
Figure 4-131 Properties ERP Instance - Alarms tab
This secondary windows contains the same tabs of the modify operation, the only
essential difference is that no changes is possible.
............................................................................................................................................................................................................................................................
4 - 18 8 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Modify ERP instance - perVLan case

The window is equal to window in Figure 4-121, (pg. 4-180) except that when the Scope
is perVLAN, as in this case, an new graphical object Traffic VLan is shown.
Figure 4-132 Modify ERP Instance - Configuration Tab - Scope as perVLAN
selection button near the Traffic VLAN permits to add the possible VLAN that this
ERP instance should be protected. When the operator presses this selection button this
secondary window is opened:
Figure 4-133 Management Traffic VLAN
This secondary window is used to manage completely the association of the traffic VLAN
to ERP instance, it permits the following operations:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 8 9
............................................................................................................................................................................................................................................................
a. “Retrieval Traffic VLAN” (p. 4-190)

b. “Create Traffic VLan” (p. 4-190)
c. “Modify Traffic VLan” (p. 4-191) (This button is not available more)
d. “Delete Traffic VLan” (p. 4-192)
The Close button is used to execute the closure of the secondary window and Help button
is used to have more information about this functionality.
Retrieval Traffic VLAN

The high part of the window in Figure 4-133, (pg. 4-189) contains a table in which Traffic
VLan associated to the ERP instance could be shown. This table is composed by two
columns:
• Operator Label: it shows the virtual name associated to the Traffic VLan, it is
composed by a prefix VLAN# following by three indexes dived by character #, the first
is ERP topology index, the second is ERP instance index and the third is the VLAN
identifier.
• Status: it shows the information about the status of the row of the specified Traffic
VLan.
In high part of the this window the first two indexes are fixed because they identify
unambiguously the ERP instance instead, the third index, that is the VLAN identifier,
must be given by operator using a step of 50 units, e.g. [1,..50] ,[51,..100] etc.
Search button is used in order to execute the retrieval of the Traffic VLan falling in the
specified range.
Create Traffic VLan

a new Traffic VLan, when the operator clicks on this button the following secondary
window is opened:
............................................................................................................................................................................................................................................................
4 - 19 0 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-134 Create Traffic VLAN
This secondary window contains these fields:

• Topology Index: it shows the index of the ERP topology.
• Instance Index: it shows the index of the ERP instance.
• VLAN Index: it permits to insert VLAN identifier
• Status: it permits to insert row-status value, it can assume a possible value in the set
{up, down}, it cannot modified because the creation is executed in one-step, the
default value is "up".
The button Ok is used to confirm the creation instead Cancel button to reject it. Button
Help is used to have more information about this functionality.
Modify Traffic VLan

modify an existing Traffic VLan, it is enabled only when a Traffic VLan has been
previously selected, when the operator presses this button the following secondary
window is opened:
Figure 4-135 Modify Traffic VLAN
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 9 1
............................................................................................................................................................................................................................................................
This secondary window contains these fields:

• Topology Index: it shows the index of the ERP topology.
• Instance Index: it shows the index of the ERP instance.
• VLAN Index: it shows the VLAN identifier
• Status: it permits to change row-status value, it can assume a possible value in the set
{up, down}
The button Ok is used to confirm the modification instead Cancel button to reject it.
Button Help is used to have more information about this functionality. This operation is
not supported more because the creation is done in one-step.
Delete Traffic VLan

The button Delete of the secondary window in Figure 4-133, (pg. 4-189) is used to delete
an existing Traffic VLan, when the operator presses this button the following
Figure 4-136 Delete Traffic VLAN
Selecting Yes the selected Traffic VLan will be removed instead selecting No no operation
will be done.
............................................................................................................................................................................................................................................................
4 - 19 2 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Create Aggregator
This option is obtained, after selecting, on the resources Tree, the
symbol : by means of the contextual pop-up menu, or
by selecting in the menu-bar:
Transmission Î Aggregator Management Î Create Aggregator
Some general details about Link Aggregation are described in “Resource Management
Indication” (p. 1-64).
The function of this option is to create a LAG, Link Aggregation Group, defining its main
parameters.
To create a Link Aggregation Group, fill fields and areas as follows:
• Name: to set the name of the LAG; the only suffix after # can be set by the user, with an
integer in the range 1 to 123
• Type: indicating the type of port (read only field, fixed by the system to
“ieee8023adLag”)
• User Label: to indicate the LAG by means of a name defined by the user
• Actor Admin Key: to set a parameter associated with each port and with each aggregator
of an Aggregation System identifying those port that can be aggregated together. Ports
ina an Aggregation System that share the same Aggregation Key value are potentially
able to aggregate together. Possible values: from 1 to 4.
dialogue described in “Alarms Severity (ASAP management) in Configuration menu”
(p. 4-33).
• Protocol Profile: (allowed only in Bridge Type = bridge 802.1S-AD (Provider) case);
name of the 2-bytes (VLAN-Protocol Type) contained into the 802.1Q field of Vlan
ethernet frames afferent to the current Port:
the key permits to choose and associate a provider protocol-tag to this resource,
recalling the dialogue described in “Create Protocol Profile” (p. 4-76).
the key gives the Protocol Type properties currently associated to this resource
• Promiscuous Mode: indicating whether this interface has to inspect the packets' MAC
addresses. Possible options:
– enabled: the MAC packets are accepted regardless of their MAC addresses
– disabled: the MAC packets addresses are inspected, then the only frames
addressed to this port can be accepted. In this case the inner MPLS-Port can be
activated, thus using the MPLS over Ethernet modality.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 9 3
............................................................................................................................................................................................................................................................
Note: It is allowed only if the above Client-Type parameter is ets.

• Protocol List:
the key permits to set the Protocol List, recalling the dialogue reported in
Figure 4-138, (pg. 4-195); the window permits to define a list of accepted Protocols,
and then to associate it by clicking on the Ok key. The meanings and management of
this item are described in “Create ETS InFlow for an Ethernet Port” (p. 4-100).
the key gives the Protocol List properties currently associated to this resource.
• Admin. State: Administration status; this item can be set only after creation, in
Configure Aggregator option, see “Configure Aggregator” (p. 4-196);possible values:
– enable: the LAG is in-service
– disable: the LAG is out-of-service
• Lacp Type: indicating if the Link Aggregation Control Protocol is ON (i.e. LACP is
active on this aggregator) or OFF (LACP inactive); read only field, fixed by the system
• Size: to set the size of the LAG, i.e. number of Aggregated Ports. Possible values: up to
2.
• EthClient Type: (read only field, settable by means of “Substitute Client Layer for an
Ethernet Port or an Aggregator” (p. 4-116)), indicating the transported layer:
• MTU: Maximum Transmit Unit (and Maximum Receive Unit); size of the largest
packet which can be sent/received on this LAG interface, specified in octets. (read only
field, fixed by means of “Configure ISA” (p. 4-62)).
• Encaps. Method: method of MAC packets encapsulation inside the underlying physical
layer; possible options:
– ethernetV2: client layer encapsulation is Ethernet-V2
– llc-snap: client layer encapsulation is LLC-SNAP.
The Cancel key permits to close the window without creating the LAG. Click on Help to
get aids about this function.
............................................................................................................................................................................................................................................................
4 - 19 4 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-137 Aggregator: Creation
Figure 4-138 Aggregator: Set Protocol List
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 9 5
............................................................................................................................................................................................................................................................
Configure Aggregator
This option is obtained, after selecting an existing LAG, i.e., on the resources Tree, the
symbol : by means of the contextual pop-up menu, or by selecting in the
menu-bar:
Transmission Î Aggregator Î Configure Aggregator
WARNING
The Aggregator (LAG) must have been already created, before using this option.

The function of this option is to configure an existing LAG, Link Aggregation Group
(already created as described in “Create Aggregator” (p. 4-193)), defining its main
parameters.
To configure a created Link Aggregation Group, fill fields and areas as follows:
• Name: (read-only), name of the LAG, as set in previous paragraph
CreateAggregator.
• Type: indicating the type of LAG (read only field, fixed by the system to
“ieee8023adLag”)
• User Label: to indicate the LAG by means of a name chosen by the user
• Actor Admin Key: to set a parameter associated with each port and with each
aggregator of an Aggregation System identifying those port that can be aggregated
together. Ports ina an Aggregation System that share the same Aggregation Key
value are potentially able to aggregate together. Possible values: from 1 to 4.
Important! Actor indicates the local LAG system.
• Actor System Id: (read only field, fixed by the system). This parameter is the System
Identifier, composed of the LAG Mac-Address and the above ActorSystemPriority.
The LAG having the lowest LAG-System Identifier value will be elected as the
Master of the LAG link, i.e. the one that will drive the actions in case of events
such as failures, switches, etc.
• Actor System Priority: to indicate the LAG Priority. This parameter, together with
the LAG Mac-Address, forms the System Identifier. The lowest System Identifier
value will be elected as the Master of the link, i.e. the one that will drive the
actions in case of events such as failures, switches, etc. Possible values are integers
in the range 0 to 65535
• Actor Operator Key: (read only field, fixed by the system) actual operational value
of LAG-key for this LAG.
............................................................................................................................................................................................................................................................
4 - 19 6 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• EthClient Type: (read only field, settable by means of “Substitute Client Layer for
an Ethernet Port or an Aggregator” (p. 4-116)), indicating the transported layer:
• Promiscuous Mode: indicating whether this interface has to inspect the packets'
MAC addresses. Possible options:
– enabled: the MAC packets are accepted regardless of their MAC addresses
– disabled: the MAC packets addresses are inspected, then the only frames
addressed to this port can be accepted. In this case the inner MPLS-Port can be
activated, thus using the MPLS over Ethernet modality.
Important! It is allowed only if the above Client-Type parameter
is ets.
physical layer. Possible options:
– ethernetV2: client layer encapsulation is Ethernet-V2
– llc-snap: client layer encapsulation is LLC-SNAP.
• Protocol List:
the key permits to set the Protocol List, recalling the dialogue reported in
Figure 4-138, (pg. 4-195); the window permits to define a list of accepted
Protocols, and then to associate it by clicking on the Ok key. The meanings and
management of this item are described in “Create ETS InFlow for an Ethernet
Port” (p. 4-100). the key gives the Protocol List properties currently
associated to this resource.
For detailed description of items in the Bit name column, refer to “Protocols”
(p. 1-31).
• Traffic Enabled: read-only value, it can be set by using the menu-option:
Enabled/Disabled, see “Traffic Management of an Aggregator” (p. 4-94).
– up: the traffic over this LAG is enabled
– down: the traffic over this LAG is shut-down
• Admin. State: Administrative status; this item can be set by the user in order to put
the LAG in-service or out-service; possible pull-down options:
– enable: the LAG is in-service
– disable: the LAG is out-of-service
• Oper State: (read-only field, set by the system), information about the actual
operational status of the LAG; possible values:
– up: the LAG is active
– down: the LAG is inactive
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 9 7
............................................................................................................................................................................................................................................................
– logicPortCreatFailed: failure on creation

– qReservationFailed: failure on reservation
• Bandwidth: indicating the actually used Bandwidth of the LAG, after that
Aggregated Ports have been associated to this LAG. It is the sum of Aggregated
Ports rates
• Available Bandwidth: indicating the remaining Bandwidth of the LAG, not yet used
by Aggregated Ports
• Lacp Type: indicating if the Link Aggregation Control Protocol is ON (i.e. LACP is
active on this aggregator) or OFF (LACP inactive); read only field, fixed by the
system
• Size: to set the size of the LAG, i.e. number of Aggregated Ports. Possible values:
up to 2.
menu” (p. 4-33).
the key gives the asap properties currently associated to this resource.
• MTU: Maximum Transmit Unit ; size of the largest packet which can be
sent/received on this LAG interface, specified in octets. (read only field, fixed by
means of “Configure ISA” (p. 4-62)).
• Protocol Profile: (allowed only in Bridge Type = bridge 802.1S-AD (Provider)
case); name of the 2-bytes (VLAN-Protocol Type, 802.1Q field) contained into the
Vlan ethernet frames afferent to the current Port:
the key permits to choose and associate a provider protocol-tag to this
resource, recalling the dialogue described in “Create Protocol Profile” (p. 4-76).
the key gives the Protocol Type properties currently associated to this
resource
the keypermits to delete the Protocol Type for this LAG
• Broadcast Traffic: specifies the broadcast traffic transmit capability of an egress
traffic,
• Unknown Traffic: specifies the unknown traffic transmit capability of an egress
traffic,
............................................................................................................................................................................................................................................................
4 - 19 8 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
the broadcast and multicast traffic.
Figure 4-139 Aggregator: Configure Aggregator/Configuration
• Information sector (Figure 4-140, (pg. 4-200)):

• Mac Address: (read only field, fixed by the system), indicating the MAC-Address
assigned to the selected LAG
• Partner System Id: (read only field, fixed by the system). This parameter is the
System Identifier of the Partner, i.e. the connected remote LAG.
• Partner Admin Key: (read only field, fixed by the system), indicating the LAG Key
of the Partner LAG as set by the user. Possible values: 1 to 4.
• Partner Operator Key: (read only field, fixed by the system) indicating the actual
operational LAG Key of the Partner LAG as set by the system
• Partner System Priority: parameter not yet available; (fixed by the system),
indicating the LAG Priority of the Partner LAG. This parameter, together with the
LAG MAC Address, forms the System Identifier. Possible values are integers in
the range 0 to 65535
• N. Selected Ports: (read only field, fixed by the system), indicating the number of
selected ports, that are potentially aggregable on this Aggregator
• N. Attached Ports: (read only field, fixed by the system), indicating the number of
attached ports, that are actually aggregated on this Aggregator
• Primary Port: (read only field, fixed by the system); indicating the PrimaryPort,
i.e. the one selected among all aggregated ports, for carrying special traffic (such
as Multicast/BroadCast, xSTP-BPDU, IGMP, unknown addressed packets
flooding, etc.). PrimaryPort is the first one created in the LAG.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 1 9 9
............................................................................................................................................................................................................................................................
• Primary Port Position: (read only field, fixed by the system); indicating the position
of the PrimaryPort on the equipment connectors
• Number: (read only field, fixed by the system); indicating the reference number of
this LAG, as set by the system.
Figure 4-140 Aggregator: Configure Aggregator/Information
• Alarm sector (Figure 4-141, (pg. 4-200)):

this area reports the alarms relevant to the selected LAG; their color is green if not-
associated ASAP. The management and reparation of alarms and their severities colors
are reported in next Chapter 5, “Maintenance”.
Figure 4-141 Aggregator: Configure Aggregator/Alarm

The Cancel key permits to close the window without confirming these parameters values.
Click on Help to get aids about this function.
............................................................................................................................................................................................................................................................
4 - 20 0 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Aggregator Properties
This option is obtained, after selecting an existing LAG( ) , by means of the contextual
Transmission Î Aggregator Î Aggregator Properties.
LAG.
All the reported information fields are read-only, and are the same as those explained in
“Configure Aggregator” (p. 4-196).
Figure 4-142 Aggregator Properties
Delete Aggregator
This option is obtained, after selecting a disabled LAG ( ), by means of the contextual
Transmission Î Aggregator Î Delete Aggregator.
WARNING
The resource will not be deleted if Aggregated Ports are associated, or if
containing cross-connections, or also if it contains PM points.
This option permits to delete the selected LAG.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 0 1
............................................................................................................................................................................................................................................................
Figure 4-143 Delete Aggregator
Configure an Aggregation Port

This option is obtained, after selecting an existing Aggregation Port ( ), on the
resources Tree, by means of the contextual pop-up menu, or by selecting in the menu-bar:
Transmission Î Ethernet Port Management Î Aggregation Port Î Configure
WARNING
The Aggregation Port must have been already created (by means of “Substitute
Client Layer for an Ethernet Port or an Aggregator” (p. 4-116)), before using
this option.
The function of this option is to configure an existing Aggregation Port, (already created
as described in SubstituteClientLayer), defining its main parameters.
To configure an Aggregation Port, fill fields and areas as follows:
• Name: indicating the name assigned by the system to the selected Port (read only
field)
• Lacp Type: indicating if the Link Aggregation Control Protocol is ON or OFF; i.e.
if the LAG is under control of LACP; (read only field, fixed by the system)
• Primary: (read only field, fixed by the system); indicating if this is the PrimaryPort
or not (yes/no/notSignificant)
• Selected Agg. Id: (read only field, fixed by the system); Identifier of the LAG that is
selected by this Port, i.e. the LAG on which this Port may be aggregated
• Attached Agg. Id: (read only field, fixed by the system); Identifier of the actual LAG
on which this Port is currently attached and aggregated
............................................................................................................................................................................................................................................................
4 - 20 2 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• Actor Admin Key: (read only field, fixed by the system); indicating the owner LAG-
Key. This Key is set by means of “Configure Aggregator” (p. 4-196);
the key permits to choose and associate a LAG-Key to this resource, recalling
the dialogue reported in Figure 4-145, (pg. 4-205). This dialog reports the list of
enabled LAG’s. To associate, select one LAG and then click on Apply.
the key gives the properties of the LAG that is currently associated to this
resource
the Unbind key permits to disassociate the LAG-Key for this Port
• Actor Port Priority: to set the Port Priority. Possible values are integers in the range
0 to 255
• Actor Oper Key: (read only field, fixed by the system) indicating the current
operational LAG-Key value associated to this Port.
• Admin Status: Administrative status, to be set by the user; possible pull-down
options:
– up: the Aggregation Port is active
– down: the Aggregation Port is inactive
• Admin State: (read-only field, set by the system), information about the actual state
of the Aggregation Port, as set by the system. Possible values:
– enable: the Aggregation Port is in-service
– disable: the Aggregation Port is out-of-service
• Oper State: (read-only field, set by the system), current operational status of the
Port, information about the actual state of the Aggregation Port regarding the
traffic. Possible values:
– up: the traffic on Aggregation Port is active
– down: the traffic on Aggregation Port is inactive
• State: (read-only field, set by the system), state of Aggregation Port, concerning
the aggregation status. Possible values: created , configurable , configured,
selected, reserved, attached.
• Link State: indicating the actual state of this link
• Partner Admin Key: (read only field, fixed by the system), to indicate the
administrative LAG- Key of the Partner LAG, as set by the user, integer in the
range 0 to 122
• Partner Admin Port Priority: (read only field, fixed by the system), to indicate the
administrative Port Priority of the Partner Port, as set by the user.
• Partner Oper Port Priority: (read only field, fixed by the system), to indicate the
current operational Port Priority of the “Partner” Port, as set by the system.
• Partner Oper Key: (read only field, fixed by the system), to indicate the current
operational LAG-Key of the Partner LAG, asset by the system.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 0 3
............................................................................................................................................................................................................................................................
• Actor State area:

This area reports the state of the Actor (local) system, its Administrative State (as set by
user) and its Operational State (currently fixed by the system), in terms of the following
parameters:
• LACP Activity: possible values: true / false; indicating if the link is under active
control of LACP (true) or passive (false)
• LACP Timeout: possible values: true / false; indicating if the time-out for this link is
short Time Out (true) or long TimeOut (false)
• Aggregation: possible values: true / false; indicating if this link is considered
compatible to be aggregated (true) or not (false): in this latter case is considered an
individual link
• Synchronization: possible values: true / false; indicating if this link is “in-synch”,
i.e. considered correctly aggregated in the right LAG (true) or not: “out-synch”
(false)
• Collecting: possible values: true / false; true means that collection of incoming
frames on this link is definitively enabled
• Distributing: possible values: true / false; true means that distribution of outgoing
frames on this link is definitely enabled
• Defaulted: possible values: true / false; true means that the Actor system is using
default parameters for the Partner system (i.e. it has not received LACPDU
information from partner)
• Expired: possible values: true / false; true means that the Actor’s receiver machine
is in the expired state
Note: These latter above listed parameters are encoded into the
LACPDU frame, in the “Actor-State” byte, as specified in IEEE-
Std.802.3ad-2000.
• Partner State area:
This area reports the state of the Partner (remote) system, its Administrative State (as
set by user) and its Operational State (currently fixed by the system). The meanings of
the listed parameters are the same of the above Actor State area.
Note: The listed parameters are encoded into the LACPDU
frame, in the “Partner-State” byte, as specified in IEEE-
Std.802.3ad-2000.
............................................................................................................................................................................................................................................................
4 - 20 4 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-144 Aggregation Port: Configure
Figure 4-145 Aggregation Port: Set Actor Admin Key
Properties an Aggregation Port

This option is obtained, after selecting an existing Aggregation Port, on the resources
Tree, by means of the contextual pop-up menu, or by selecting in the menu-bar:
Transmission Î Ethernet Port Management Î Aggregation Port Î Properties
WARNING
The Aggregation Port must have been already created (by means of “Substitute
Client Layer for an Ethernet Port or an Aggregator” (p. 4-116)), before using
this option.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 0 5
............................................................................................................................................................................................................................................................

Aggregation Port.
“Configure an Aggregation Port” (p. 4-202).
Figure 4-146 Aggregation Port: Properties
In Fiber In Band management for an Ethernet Port

The System, as Provider Bridge, supports Ethernet In-Band management plane via both:
• dedicated S-VLAN tag
and
• upper PPP and IP protocol layer.
In-fiber/in-band indicates the transport of management plane or control plane within the
same fiber used by the data plane but using a part of the bandwidth that is allocated to the
data plane.
The encapsulation of management plane in an MPLS label and the MPLS control plane
untagged traffic are good examples of this transport mode.
An In-fiber/In-Band interface (over both local/remote Ethernet interfaces) at Management
Plane applies to the same Ethernet interface managed at Data Plane (irrespective of
administrative status) according to below operations:
• Creation/Activation of In Fiber/In band Ethernet Interface;
• Configuration of dedicated S-VLAN (Default S-VLAN: 4094);
............................................................................................................................................................................................................................................................
4 - 20 6 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• Configuration of Management Interface Client layer (Default: enabled PPP).

A check is needed at NE level, for avoiding the same VLANs used for Data plane and
management plane, either on the same or on different interfaces.
WARNING
This option is allowed in Bridge Type = bridge 802.1S-AD (Provider) or
bridge 802.1Q (Virtual) as referred in “Configure ISA” (p. 4-62).
Create the In Fiber In Band

This option is obtained, after selecting an existing Ethernet Port ( ), on the resources
Transmission Î Ethernet Port Management Î In Fiber In Band Management Î Create In
Fiber In Band
WARNING
If this functionality has been already configured on the interface this item menu
is disabled.
The function of this option is allowing to user configure the port in order to support the “In
Fiber In Band”.
Figure 4-147 Create the In Fiber In Band
To create an In Fiber In Band, fill fields as follows:

• Name Port: (read only field) indicating the selected port
• VLAN ID: it is the label which tags the management plane packets, discriminating them
from the data plane ones. In case of Ethernet interface the label is the VLAN and the
default value is 4094. Possible range from 1 to 2147483647.
• PPP Status: (read only field) indicating the PPP work status. Possible values: enabled
(default), or disabled.
• Status: (read only field) indicating the CLNS work status. Possible values: enabled, or
disabled.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 0 7
............................................................................................................................................................................................................................................................
• Routing Protocol: (read only field) indicating the routing protocol used for the
Management Plane packets. Possible values: none, local, netmgmt, icmp, egp, ggp,
hello, rip, isis, esis, ciscolgrp, bbnSpflgp, ospf, bgp, ospfAndRip.
Modify the In Fiber In Band

Transmission Î Ethernet Port Management Î In Fiber In Band Management Î Modify In
Fiber In Band
WARNING
.If this functionality has not been already created on the interface this item
menu is disabled.
The function of this option is allowing the user modify some parameters related to the “In
Fiber In Band”.
All the reported information fields are the same as those explained in “Create the In Fiber
In Band” (p. 4-207) with the following differences:
• Status: CLNS work status, possible pull-down options:
– up: to set the CLNS in-service
– down: to set the CLNS out-of-service
Figure 4-148 Modify the In Fiber In Band

............................................................................................................................................................................................................................................................
4 - 20 8 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Delete the In Fiber In Band

Transmission Î Ethernet Port Management Î In Fiber In Band Management Î Delete In
Fiber In Band
This menu is used when the user wants to remove the “In Fiber In Band” related to the
interface; if this functionality has not been already configured on the interface this item
menu is disabled. When the user clicks on this item menu, the Figure 4-149, (pg. 4-209)
message box is displayed.
Figure 4-149 Delete In Fiber In Band
Click on Yes key to confirms the deletion of the In Fiber In Band.

Click on No key to leave the In Fiber In Band.
Properties of the In Fiber In Band

Transmission Î Ethernet Port Management Î In Fiber In Band Management Î Properties
In Fiber In Band
This menu is used when the user wants only to retrieve/see all parameters related to the “In
Fiber In Band” on the interface, as shown in Figure 4-150, (pg. 4-210).
“Create the In Fiber In Band” (p. 4-207)
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 0 9
............................................................................................................................................................................................................................................................
Figure 4-150 Properties of the In Fiber In Band
Click on Yes key to confirms the deletion of the In Fiber In Band.

Click on No key to leave the In Fiber In Band.
EFM Management for the Ethernet Port

EFM (Ethernet First Mile) is a OAM standard for Ethernet for monitoring Link operation,
such as remote failure indications and remote loop-back control. EFM is intended for
point-to-point Ethernet links and conveys OAM information in OAMPDU frames
containing control and status information used to monitor, test and troubleshoot OAM
enabled links: OAMPDU frames cannot propagate beyond a single hop within a Ethernet
network.
The System in Active Mode configuration (Active mode DTEs initiate OAM
communications and can issue queries and commands to a remote device) is requested to
support below EFM functions:
• Discovery: a means for detecting the presence of an OAM sub-layer at the remote peer
and establishing OAM;
• Link Monitoring for detecting link faults;
• Remote Failure indications: a mechanism for an OAM entity to convey failure
conditions to its peer via specific flags in the OAMPDU. Failure conditions include:
– Link fault - loss of signal detected by the receiver;
– Dying Gasp – an unrecoverable, vendor-specific condition (e.g. power failure);
– Critical Event.
• Remote Loopback
An OAM entity can put its remote entity into loopback mode using a loopback control
OAMPDU.
This helps you ensure the quality of links during installation or when troubleshooting.
In loopback mode, every frame received is transmitted back on that same port except
for OAMPDUs and pause frames. The periodic exchange of OAMPDUs must
continue during loopback state to maintain the OAM session;
............................................................................................................................................................................................................................................................
4 - 21 0 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• Remote MIB Variable Retrieval: EFM provides a read-only access remote MIB
variables limited to a specific MIB branch and leaf. the variable is negligible compared
to propagation and queuing delay of the request and response.
Configuration of the EFM

Transmission Î Ethernet Port Management Î EFM Management Î Configure EFM
The function of this option is to configure the primary controls and status for the OAM
capabilities of an Ethernet like interface.
Figure 4-151 Configuration of the EFM
To configure an Ethernet First Mile, fill fields as follows:

• Admin State: representing the desired state of OAM for this interface. Possible values:
disabled or enabled.
• Operational State: (read only field) current operational status of the OAM for this
interface. Possible values: disabled, linkfault, passiveWait, activeSendLocal,
sendLocalAndRemote, sendLocalAndRemoteOk, oamPeeringLocallyRejected,
oamPeeringRemotelyRejected, or operational according to the operation and failure
conditions,
• Mode: (read only field) indicating the mode of OAM operation for this Ethernet like
interface. Possible values:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 1 1
............................................................................................................................................................................................................................................................
– active mode provides additional capabilities to initiate monitoring activities with

the remote OAM peer entity
– passive mode generally waits for the peer to initiate OAM actions with it.
• PDU Size: (read only field) indicating the OAM entities exchange maximum OAMPDU
sizes and negotiate to use the smaller of the two maximum OAMPDU sizes between
the peers. This value is determined by the local implementation.
• Config Revision: (read only field) indicating if configuration changes have occured
which might require the peer OAM entity to re-evaluate whether the peering is
allowed. The configuration revision of the OAM entity as reflected in the latest
OAMPDU sent by the OAM entity.
• Functions Supported: selection box indicating the OAM functions supported on this
Ethernet like interface. OAM consists of separate functional sets beyond the basic
discovery process which is always required. These functional groups can be supported
independently by any implementation. These values are communicated to the peer via
the local configuration field of Information OAMPDUs. Possible values:
unidirectionalSupport, loopbackSupport, eventSupport, variableSupport.
• Information TX Interval: (read only field) indicating the minimum interval, in terms of
10ms, between two consecutive Information OAMPDU's. Default value is 100 (1sec).
• L2CP Aware: combo box which allows to select whether L2CP frames are to be
discarded in case the port is in DISCARD state (remote loopback is requested to the
remote DTE). Possible values: not-aware or aware.
• Loopback Command: combo box which allows to select the initialization or termination
of remote loopback with an OAM peer. Possible values: noLoopback (no remote
loopback), startRemoteLoopback (it will cause the local OAM client to send a
loopback OAMPDU to the OAM peer with the loopback enable flags set), or
stopRemoteLoopback (it will cause the local OAM client to send a loopback
OAMPDU to the OAM peer with the loopback enable flags cleared).
• Loopback Status: (read only field) indicating the loopback status of the OAM entity.
Possible values: noLoopback, initiatingLoopback, remoteLoopback,
terminatingLoopback, localLoopback, or unknown. This status is determined by a
combination of the local parser and multiplexer states, the remote parser and
multiplexer states, as well as by the actions of the local OAM client.
• Peer Status: (read only field) indicating whether the information in this row should be
considered valid.
– active, the information is valid and represents the current peer of the OAM entity.
– inactive, the information in this row is invalid.
............................................................................................................................................................................................................................................................
4 - 21 2 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• Peer MAC Address: (read only field) indicating the MAC address of the peer OAM
entity. The MAC address is derived from the most recently received OAMPDU. This
value is initialized to all zeros (0x000000000000). This value is invalid if the Peer
Status = inactive.
• Peer Vendor OUI: (read only field) indicating the OUI of the OAM peer as reflected in
the latest information OAMPDU received with a Local Information TLV. The OUI can
be used to identify the vendor of the remote OAM entity. This value is initialized to all
zeros (0x000000). This value is considered invalid if the Peer Status = inactive.
• Peer Vendor Info: (read only field) indicating the Vendor Info of the OAM peer as
reflected in the latest information OAMPDU received with a Local Information TLV.
The vendor information field is within the Local Information TLV, and can be used to
determine additional information about the peer entity. The format of the vendor
information is unspecified within the 32-bit field. This value is intialized to all zeros
(0x00000000). This value is invalid if the Peer Status = inactive.
• Peer Mode: (read only field) indicating The mode of the OAM peer as reflected in the
latest information OAMPDU received with a Local Information TLV. The mode of the
peer can be determined from the Configuration field in the Local Information TLV of
the last Information OAMPDU received from the peer. Possible values: active,
passive, or unknown. This value is initialized to unknown, and is not valid if the if the
Peer Status = inactive.
• Peer Max OAM PDU Size: (read only field) indicating the maximum size of OAMPDU
supported by the peer as reflected in the latest information OAMPDU received with a
Local Information TLV. Ethernet OAM on this interface must not use OAMPDUs that
exceed this size. The maximum OAMPDU size can be determined from the PDU
Configuration field of the Local Information TLV of the last Information OAMPDU
received from the peer. Possible values: from 64 to 1522. This value is initialized to
64, and is invalid if the Peer Status = inactive.
• Peer Config Revision: (read only field) indicating the configuration revision of the OAM
peer as reflected in the latest OAMPDU. This attribute is changed by the peer
whenever it has a local configuration change for Ethernet OAM this interface. This
value is initialized to all zeros (0x00000000), and is invalid if the if the Peer Status =
inactive.
• Peer Functions Supported: info box indicating the OAM functions supported on this
Ethernet like interface. OAM consists of separate functionality sets above the basic
discovery process. This value indicates the capabilities of the peer OAM entity with
respect to these functions. Possible values: unidirectionalSupport, loopbackSupport,
eventSupport, variableSupport. This value is initialized so all bits are clear, and is
invalid if the Peer Status = inactive.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 1 3
............................................................................................................................................................................................................................................................
Clicking on Statistics tab the window contents change as shown in the following:
Figure 4-152 Statistics of the EFM
Where the following reading only fields shown the statistics of the EFM:
• Information Tx: indicating the current count of the number of Information OAMPDUs
transmitted on this interface.
• Information Rx: indicating the current count of the number of Information OAMPDUs
received on this interface.
• Unique Event Notification Tx: (not supported in current release) indicating the current
count of the number of unique Event OAMPDUs transmitted on this interface.
• Unique Event Notification Rx: (not supported in current release) indicating the current
count of the number of unique Event OAMPDUs received on this interface.
• Duplicate Event Notification Tx: (not supported in current release) indicating the current
count of the number of duplicate Event OAMPDUs transmitted on this interface.
• Duplicate Event Notification Rx: (not supported in current release) indicating the current
count of the number of duplicate Event OAMPDUs received on this interface.
• Loopback Control Tx: indicating the current count of the number of Loopback Control
OAMPDUs transmitted on this interface.
• Loopback Control Rx: (not supported in current release) indicating the current count of
the number of Loopback Control OAMPDUs received on this interface.
The Refresh Counters button allows to update the actual count.
............................................................................................................................................................................................................................................................
4 - 21 4 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Clicking on Alarms tab the window contents change as shown in the following:
Figure 4-153 Alarms of the EFM
This window reports the alarms relevant to the selected EFM; their color is green if not-
associated ASAP. The management and reparation of alarms and their severities colors are
reported in next Chapter 5, “Maintenance”.
Properties of the EFM

This option is obtained, after selecting an existing Ethernet Port, on the resources Tree, by
Transmission Î Ethernet Port Management Î EFM Management Î EFM Properties
This selection shows the same windows of the “Configuration of the EFM” (p. 4-211), but
with the previous editable fields, in read-only format as shown in the following picture.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 1 5
............................................................................................................................................................................................................................................................
Figure 4-154 EFM Properties
............................................................................................................................................................................................................................................................
4 - 21 6 P/N 8DG15785AAAA
OAM CT Operator’s Guide
............................................................................................................................................................................................................................................................
OAM
The OAM application (Operations, Administration, Maintenance) permits to manage all
parameters related to the OAM-Domain context.
In particular, this application manages operations aimed to test the links and the
functionality of an existing bridge network such as:
• Continuity Check: a test signal is sent by an originating point in the network, in order
to detect link failures.
• LoopBack: a test signal is sent by an originating point and is reflected back at a
destination point of a bridged network.
• LinkTrace: a test signal is sent by an originating point to a destination point of a
bridged network, and every bridge crossed along the path sends back a link signal to
the originator. It is used for link fault detection and path discovery.
WARNING
The bridge network must have been already configured and connected, in order
to use these features.
WARNING
The OAM function is supported onlyin Bridge Type = bridge 802.1S-AD
(Provider) or bridge 802.1Q (Virtual) as referred in “Configure ISA” (p. 4-62)).
The involved Ports (or LAG’s) for OAM communications are ETB types.
Summary procedure for OAM configuration

In order to configure the bridged network for OAM, follow the below listed main steps:
1. Configuration of all bridge of this OAM network, as Provider or Virtual types
2. Configuration of the OAM ports/Lags as ETB types, for every bridge of the network
3. Creation of the appropriate MD (Maintenance Domain) for every bridge of the
network to be covered by the same OAM entity.
Note: All nodes of the same OAM domain must have identical
parameters regarding MD configuration
4. Creation of the appropriate MA (Maintenance Association) for every bridge of the
network to be covered by the same OAM entity.
Note: All nodes of the same MA region must have identical
parameters regarding MA configuration
5. Creation of the appropriate MEP’s (MEG End Point) in each bridge of the network.
These items represent the interfaces where the OAM messages enter and go out the
bridges.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 1 7
CT Operator’s Guide OAM
............................................................................................................................................................................................................................................................
Configure Resources
This option is obtained, by selecting in the menu-bar:
OAM Domain Î Configure Resources (OAM)
The function of this option is to configure the parameters for the OAM.
Figure 4-155 OAM: Configure Resources
The window shown in Figure 4-155 reports in tabular form the existing MD (Maintenance
Domain), created as described within next Figure 4-156, (pg. 4-218).
OAM Configure Resources (Figure 4-155) Î Create key (Figure 4-156)
Figure 4-156 OAM: Configure Resources: Create MD
The window of Figure 4-156 permits to create the MD (Maintenance Domain). MD is the
area of the network that can be managed and administered, for OAM purposes. For
instance, an MD can coincide with an MST region.
• Operator Label: read-only, set by the system
• Name: to type a name chosen by the user
............................................................................................................................................................................................................................................................
4 - 21 8 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• Level: to specify the MD Level. It is part of the MD identifier, and can also be used to
distinguish among various MD’s inside the same network. Possible values: Level0 to
Level7.
• Status: up/down; to activate or deactivate this MD.
• Format: to define the format for the name of this MD. Possible values:
– none: (without any name)
– charString:
– dnsLikeName:
– macAddressAndUint:
Note: All Bridges belonging to the same MD must have the same
format
• MHF Creation: to define the MHF (MIP Half Function), (MIP= MEG Intermediate
Point, MEG= Maintenance Entity Group) of this MD. Possible values:
– defMHFnone: no MIP can be created for this MD
– defMHFdefault: MIP’s can be created for this MD on any bridge port
– defMHFexplicit: MIP’s can be created for this MD on bridge ports only if a MEP
is created at lower MD Level.
OAM Configure Resource (see Figure 4-155): Modify key

(same content as the Create key, see Figure 4-156).
The Modify window can be used to modify some parameters of the created MD.
OAM Configure Resource (see Figure 4-155) Î Delete key (Figure 4-157)
Figure 4-157 OAM: Configure Resources: Delete MD
It will delete the MD# selected in the table.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 1 9
............................................................................................................................................................................................................................................................
OAM Configure Resource (Figure 4-155) Î MA Navig. key (Figure 4-158)
Figure 4-158 OAM: Configure Resources: MA Navigation
The window of Figure 4-158. permits to navigate and create the MA (Maintenance
Association). The MA is described below, within the Create key.
This window reports, in table form, the already created MA, and their relevant parameters:
Operator Label, Name, Vlan ID, Status.
OAM Configure Resource (Figure 4-155) Î MA Navig. key (Figure 4-158) Î Create
key(Figure 4-159)
Figure 4-159 OAM: Configure: MA Navig.: Create MA
The window in Figure 4-159 permits to create an MA (Maintenance Association). The

MA is the sub-area of the MD that can be reached by a sub-set of OAM messages. Each
MA is independent from other MA’s inside the same MD, and thus an OAM message
originated inside an MA can circulate only into the same MA.
• Maintenance Domain: a pull-down menu permits to choose the MD among those
already created.
............................................................................................................................................................................................................................................................
4 - 22 0 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• Index MA: read-only incremental index, set by the system

• CCM Interval:; time interval for repeating the CCM message (Continuity Check
Message). Possible values from 10 ms to 1 min.
• Status: up/down; to activate or deactivate this MA
• Format: to define the format of this MA. Possible values:
– charString:
– rfc2865Vpnld:
– unsignedInt16:
– primaryVid:
Important! All Bridges belonging to the same MA must have the
same format;
• MA Name: to type a name chosen by the user
• MHF Creation: to define the MHF (MIP Half Function), (MIP= MEG Intermediate
Point, MEG= Maintenance Entity Group) of this MA. Possible values
– defMHFnone: no MIP can be created for this MA
– defMHFdefault: MIP’s can be created for this MA on any bridge port
– defMHFexplicit: MIP’s can be created for this MA on bridge ports only if a MEP
is created at lower MD Level.
• Vid: to associate a Vlan to this MA, by clicking on [...] key, see Figure 4-160.
OAM Configure Resource (Figure 4-155) Î MA Navig. key (Figure 4-158) Î Create
key(Figure 4-159) Î Vid key(Figure 4-160)
Figure 4-160 OAM: Configure: MA Navig.: Create: Vid
This window permits to associate a VLAN ID to this MA. It reports the existing VLAN.
Thus the Vlan’s to be used for OAM scopes should have been already registered over the
ETB ports to be used for OAM.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 2 1
............................................................................................................................................................................................................................................................
OAM Configure Resource (Figure 4-155) Î MA Navig. key (Figure 4-158) Î MEP
Navigation key (Figure 4-161)
(Available after MA-Create, after selecting an MA in the table of Figure 4-158)
Figure 4-161 OAM: Configure: MA Navig.: MEP Navigation
The window of Figure 4-161 permits to navigate and create the MEP (Maintenance entity
group End Point). The MEP is described below, within the Create key.
• Operator Label: name of the selected MA for this item.
The existing MEP’s can be searched, in the specified range from ... to, clicking on Search
key.
This window reports, in table form, the already created MEP’s, and their relevant
parameters: Operator Label, Status, MEP IfIndex, MEP Direction, Alarm.
............................................................................................................................................................................................................................................................
4 - 22 2 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Navigation key (Figure 4-161) Î Create key (Figure 4-162)
Figure 4-162 OAM: Configure: MA Navig.: MEP Navigation: Create MEP
The window in Figure 4-162 permits to create an MEP (MEG End Point). The MEP is the
resource defined over a Bridge, capable of initiating and terminating OAM PDU frames
for fault management and performance monitoring. A MEP is headed by an ETB port or
ETB LAG.
• Operator Label: read-only incremental index, set by the system
• Identifier: integer value set by the user, different from 0
• IfIndex: to associate a Port (or LAG) of the bridge to this MEP, by clicking on [...] key,
it opens the Search window (see “Search in Views menu” (p. 4-28)), permitting to
choose the ETB Port/LAG to be used for OAM communications for this MA.
Important! The chosen port must be already registered over the
VLAN used for the relevant MA (see Figure 4-159, (pg. 4-220))
• Cci Enabled: (true / false), to enable CCI, only false; (not operative)
• Ltm Priority: to associate a priority (0 to 7) to the LinkTrace Message, inserted into
Vlan-Tag; default is 7
• Status: actual state of this MEP (up/down), i.e. in-service/out-of-service
• Direction: to indicate the direction of OAM messages for this MEP;
– up means the OAM messages must traverse the bridge (messages go out from the
bridge via other ports).
– down means OAM messages are directly sent outside the bridge (messages go out
from the bridge via this same port).
• Active: (true / false), to activate/deactivate this MEP
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 2 3
............................................................................................................................................................................................................................................................
Navigation key (Figure 4-161) Î Modify key.
This Modify key permits to change some parameters of the selected MEP, after it has been
created as seen in Figure 4-162.
Navigation key (Figure 4-161) Î LoopBack key (Figure 4-163).
(Available after MEP-Create, after selecting a MEP in the table of Figure 4-161).
Figure 4-163 OAM: Configure: MA Navig.: MEP Navigation: Loop Back
The window in Figure 4-163 permits to define and start a LoopBack message.
• Operator Label: displays the selected MEP, set by the system
• Mep MAC Address: MAC address of this selected MEP (it is given by the system, as can
be seen in MEP Property: see Figure 4-165)
• Target MAC Address: MAC address of the target MEP that has to respond to this
LoopBack message.
Note: This Address can be read in the far MEP-Properties of the
node to be reached.
• LoopBack Type: the only permitted value is Dest. MAC ADDRESS; i.e. the LB is done
in base of the only MAC Address parameter
• Target Mep Id: read-only value set by the system; not operative.
• Target Is Mep Id: (true/false) read-only value set by the system; not operative.
• LoopBack Result: reporting the result (OK/KO) of the LoopBack test, after having
clicked on the Start key.
............................................................................................................................................................................................................................................................
4 - 22 4 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Navigation key (Figure 4-161) Î LinkTrace key (Figure 4-164)
(Available after MEP-Creation, after selecting a MEP in the table of Figure 4-161)
Figure 4-164 OAM: Configure: MA Navig.: MEP Navigation: Link Trace
The window in Figure 4-164 permits to define and start a LinkTrace (LT) message.
• Operator Label: name of the selected MEP, set by the system
• Mep MAC Address: MAC address of this selected MEP, set by the system
• Target MAC Address: MAC address of the final MEP of the path towards which this LT
message has to be sent.
Note: This Address can be read in the far MEP-Properties” of the
node to be reached.
• Egress Identifier: MAC address of the egress i/f for this LT message, set by the system
• LinkTrace Type: the only permitted value is Dest. MACADDRESS; i.e. the LT is done in
base of the only MAC Address parameter
• Target Is Mep Id: (true/false) read-only value set by the system; not operative
• Target Mep Id: read-only value set by the system; not operative
• Transmit Ltm TTL: max number of bridge nodes this message can traverse before
expiring
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 2 5
............................................................................................................................................................................................................................................................
• LinkTrace Result: reporting the result (OK/KO) of the LinkTrace test, after having
clicked on the Start key. After having clicked on ShowResult key, it will report, on any
row of the table, the parameters corresponding to each bridge that responded to this
LTM.
The ShowResult key displays the detailed test results. It causes the displaying of LT
results on the above LinkTrace Result table.
Reported parameters (for each crossed bridge):
– Entry; TTL; Forwarded; Terminal Mep; LastEgressIdentifier;
NextEgressIdentifier; Relay; Ingress; IngressMac; Egress; EgresMac
Navigation key (Figure 4-161) Î Details key (Figure 4-165)
Figure 4-165 OAM: Configure: MA Navig.: MEP Navigation: Details
This window in Figure 4-165 permits to read the parameters configured for the selected
MEP.
Note: The displayed parameter Some Rdi Defect is not operative.
Note: The alarms reported in Alarm tab are not operative.
............................................................................................................................................................................................................................................................
4 - 22 6 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
OAM Configure Resource (Figure 4-155) Î MA Navig. key (Figure 4-158) Î Show
All MEP key (Figure 4-166)
Figure 4-166 OAM: Configure: MA Navig.: Show All MEP
The window in Figure 4-166 permits to search all existing MEP’s, and to get their details.
It contains the following fields:
• Filtering: filtering criteria; possible pull-down options:
– Show All: to search all MEP’s
– Specify Criteria: in this case, the user can define the MD, MA indexes, and the
MEP range
• MD index, MA index, Show from/to fields are settable only if Filtering = Specify Criteria.
• Show from/to: this field is referred to MEP indexes range
The Details key, after selecting a MEP in the table, displays the same Detail window
described in Figure 4-165, (pg. 4-226).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 2 7
............................................................................................................................................................................................................................................................
OAM Configure Resource (Figure 4-155) Î MA Navig. key (Figure 4-158) Î MA-
MEP List ID key (Figure 4-167)
Figure 4-167 OAM: Configure: MA Navig.: MA-MEP List ID
The window in Figure 4-167 permits to search all existing MEP’s.

It contains the same fields described for Figure 4-166.
OAM Configure Resource (Figure 4-155) Î MA Navig. key (Figure 4-158) Î

Modify key (Figure 4-168)
(Available after MA-Creation, after selecting a MA in the table of Figure 4-158)
Figure 4-168 OAM: Configure: MA Navig.: Modify
The window in Figure 4-168 is very similar to Figure 4-159 (Create MA). It permits to
modify an existing MA.
Further it contains the key MA MEP List Show, that opens a next window as seen in next
Figure 4-169.
............................................................................................................................................................................................................................................................
4 - 22 8 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
OAM Configure Resource Î MA Navig. key Î Modify key Î Show key
Figure 4-169 OAM: Configure: MA Navig.: Modify: Show

Details key (Figure 4-170)
Figure 4-170 OAM: Configure: MA Navig.: Details
The window in Figure 4-170 permits to get details about the selected MA. It contains the
same parameters described for Figure 4-159 (Create MA).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 2 9
............................................................................................................................................................................................................................................................

Delete key (Figure 4-171)
Figure 4-171 OAM: Configure: MA Navig.: Delete
The window in Figure 4-171 permits to delete the selected MA, and all MEP’s related to
it.
Properties Resources
OAM Domain Î Properties Resources (OAM)
The function of this option is to show the parameters configured for OAM. It reports, in
read-only mode, the same parameters described in “Configure Resources” (p. 4-218).
Figure 4-172 OAM: Properties Resources
Configure
............................................................................................................................................................................................................................................................
4 - 23 0 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
OAM Domain Î Configure (OAM)

An example of the window displayed is reported in Figure 4-173.
The function of this option is to configure the global OAM parameters for this bridge.
Important! These parameters will be used either for Standard-
OAM (see “Configure Resources” (p. 4-218)), and for Proprietary
loop-back (see “Configure LoopBack” (p. 4-232)).
Figure 4-173 OAM: Configure
The window in Figure 4-173 contains the following fields:

• OAM Bridge MAC: unique Mac Address for OAM for this bridge, set by the system
• Lbm Time Out: number of seconds after which the LoopBack message is considered
expired
• OAM ETH Type: two-bytes hex value, inserted into OAM PDU frame, after Vlan tag. Its
default value is 8902
Click on Ok key to confirm the inserted values.
Properties
OAM Domain Î Properties (OAM)
The function of this option is to show, in read-only mode, the configured parameters,
described in “Configure” (p. 4-230).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 3 1
............................................................................................................................................................................................................................................................
Figure 4-174 OAM: Properties
Configure LoopBack
OAM Domain Î Configure Loop Back (OAM)
The function of this option is to configure a Proprietary Loop Back. These parameters are
thus independent from configurations described in “Configure Resources” (p. 4-218). The
only parameters used here will be those ones set as seen in “Configure” (p. 4-230).
This proprietary LB differs from the standard LB, because this is done per NE-bridge
basis, while the standard one is performed per interface basis. Further, the present one
does not need any MD and MA and MEP definitions.
Figure 4-175 OAM: Configure LoopBack
............................................................................................................................................................................................................................................................
4 - 23 2 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
The window in Figure 4-175 contains the following fields:

• MAC Address Dest.: MAC address of remote NE to be reached.
Note: This parameter can be read in the (global) OAM
Properties of the far bridge to be reached, as seen in
Figure 4-174, (pg. 4-232).
• Vlan: Vlan to be used for this OAM PDU messages.
WARNING
This Vlan must be registered on ports to be used for OAM purposes.
• Vlan Priority: priority to be used for this OAM message

• EthFrame Type: Possible pull-down values: Ethv2 / LLC SNAP
• Maintenance Level: MD Level. Possible values: Level0 to Level7 (default is 7).
The window contains further the following keys:
• Unbind: this button can be used to disassociate the Vlan that was bound to this
LoopBack test message.
• Start: this button is used to launch this LoopBack test message.
• Add Test: this button is used to save the parameters of this LB test into the Test List.
• Test List: this button permits to get the list of the executed tests, available only if saved by
means of previous Add Test key. It opens the window reported in Figure 4-175, (pg. 4-232).
Click on Start key to initiate this LB message.
Figure 4-176 OAM: Configure Loop Back: Test List
This window in Figure 4-176 contains the list of executed LB tests, available only if saved
by using Add Test key seen in Figure 4-175, (pg. 4-232).
It contains further the following keys:
• Ok: this button permits to get the parameters of the selected LB test, transferring the
selected parameters into the previous window Figure 4-175, (pg. 4-232).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 3 3
............................................................................................................................................................................................................................................................
• Modify: it permits to change some parameters for the selected LB test. It opens the
window reported in Figure 4-177.
• Delete: this button is used to delete the selected LoopBack test.
• Close: this button is used to close this window without doing any operation.
• Help: this button is used to get help about the present function.
OAM Configure LoopBack -> Test List key -> Modify key
Figure 4-177 OAM: Configure Loop Back: Test List: Modify
This window in Figure 4-177 permits to change some parameters relevant to the LB-Test
selected in Figure 4-176, (pg. 4-233). Test parameters are described within previous
Figure 4-175, (pg. 4-232).
Loop Back Properties

OAM Domain Î Loop Back Properties (OAM)
The function of this option is to show, in read-only mode, the same parameters described
in “Configure LoopBack” (p. 4-232), in particular, Figure 4-175, (pg. 4-232).
Figure 4-178 OAM: Loop Back Properties
............................................................................................................................................................................................................................................................
4 - 23 4 P/N 8DG15785AAAA
Connection CT Operator’s Guide
............................................................................................................................................................................................................................................................
Connection
The Connection application permits to manage all the parameters related to the
Connection context.
It can be entered by selecting, in the menu-bar: Views Î Connection, or by clicking on its
Note: All the dialogue windows described in this handbook are
reported in FullWindow mode, the information fields reported in the
TabbedWindow mode are the same (see “Windows Presentation:
“FullWindow" and “TabbedWindow"” (p. 4-28)).
Important! ISA-ES1 and ISA-ES4 support (in mutually exclusive
mode) the following working modalities (see “Configure ISA”
(p. 4-62)):
General Bridge Management modalities:
– bridge 802.1d: for MAC bridge functions
– bridge 802.1Q: for Virtual bridge functions
– bridge 802.1S-AD: for Provider bridge functions
In order to swap from one Bridge Type to another, the de-activation of every
underlying resource (Ethernet Ports, InFlows, OutFlows, etc.) is necessary, before
the swapping.
Filtering Data Base for the Bridge

This option is obtained, after selecting the Switch symbol ( ), by means of the
Connection Î Bridge Management Î Filtering Data Base.
The function of this option is to manage the Filtering Data Base (FDB) Table, such as:
Dynamic Filtering, Static Unicast Filtering, Static Multicast Filtering, Dynamic
Multicast Filtering.
The FDB reports the bridge instances, i.e. the rules on how and where the afferent ethernet
frames have to be forwarded (connected). These rules can be dynamic (i.e. temporary) or
static (i.e. permanent). The forwarding rules are associations among MAC-addresses and
Ports; the VLAN-Id is used too, in case of Virtual and Provider bridge.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 3 5
CT Operator’s Guide Connection
............................................................................................................................................................................................................................................................
Dynamic Filtering: unknown incoming frames are flooded on all ports of the bridge.
When a far station responds back on a port, the bridge “learns" that frames having this
received VLANID/MAC Address couple have to be forwarded to that port. This
connection is written on the FDB table. These instances are temporary and are deleted,
after passing the ageing time.
Static Filtering: the forwarding (or connection) instances are manually entered by the
operator and are permanent.
Furthermore, the FDB instances may be Unicast (incoming frames are relayed only
towards one Port), or Multicast (incoming frames are relayed towards two or more egress
Ports).
The following parameters are listed: VLANID, Port, MAC Address, Status.
It reports the bridging instances learned by means of the auto-learning process, i.e. a
mapping between Ports and VID/MAC Addresses. Further it reports the “permanent"
(Static) bridging instances, manually set by the operator.
To manage the Filtering Data Base, fill fields and areas as follows:
• Dynamic Filtering Database sector:
• VLANID: applicable only in case of Bridge Type = bridge 802.1S-AD (Provider) or
bridge 802.1Q (Virtual) (fixed to 1 in case of MAC Bridge); it is the VLAN
identifier whose incoming frames are to be bridged to the relevant associated port .
• Port: this is the target Port for the associated VLANID and MAC-Address
• MAC Address: MAC Address whose incoming frames are to be bridged to the
relevant associated port.
• Status: it indicates the status of this entry. Possible values:
– learned - the corresponding FDB instance was learned, and is being used.
– mgmt- the corresponding FDB instance is also contained in the Static FDB
– invalid - the corresponding FDB instance is no longer valid (e.g., it was
learned, but aged-out), but has not yet been flushed from the table.
– Self - the corresponding FDB instance represents one of the bridge's addresses.
– Permanent - the corresponding FDB instance has been created in static mode.
– Other - the corresponding FDB instance does not fall into any of the above
cases.
............................................................................................................................................................................................................................................................
4 - 23 6 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• Ageing Time:
This sector permits to set the “Ageing Time" of each single item in the FDB table,
after selecting the relevant row of the displayed table. After this time, the item of
the FDB table that reached this age is removed. Measurement unit in seconds.
Range: 10 s to 1000000 s (recommended value 300s), granularity 1 s.
To set this parameter, type a value (or select it from the pull-down menu) in the
Ageing Time field and then click on the Set Ageing Time key.
• Total MAC learned:
This field shows the number of MAC addresses learned (after Search).
• Detail (MAC Status):
This key permits to get information about the status of a learned MAC selected in
the table. It displays, after a row selection, the window reported in
Figure 4-183, (pg. 4-241).
Figure 4-179 Filtering Data Base/Dynamic Filtering Database (Virtual Bridge case)
• Static Unicast Filtering sector:

The static FDB table is composed by the same parameters as the Dynamic one, but
reporting the static instances.
This sector permits to create static bridging connections (called also permanent
forwarding instances), in manual mode, after clicking on the New key. The inserted
MAC addresses must be Unicast type, otherwise the operation will be refused by the
system.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 3 7
............................................................................................................................................................................................................................................................
Note: The MAC address must be written separating each octet

with a colon, e.g.: “28: 29: 30: aa: bb: cc”.
In order to insert a new static forwarding instance:
– click on New key
– choose, on VLANID field, the desired value, by means of the pull-down menu (all
the registered VLAN’s are listed)
– type, on MAC ADDRESS field, the appropriate MAC Address of one station to be
reached by passing through a given port of the bridge. The address must be Unicast
type, otherwise it will be refused by the system.
– choose the port on which the frames having the selected VID/MAC Address
couple have to be retransmitted, by selecting it on the Available field and then
using the “>>" key for adding it on the Allowed To Go To field.
– click on Apply key. At the end the created instance will be displayed on the FDB
table.
• Available field reports all the ETB ports of the ISA Board, that are part of the
“MemberSet" associated with the selected VLANID (i.e. registered, see “VLAN
Registration” (p. 4-118)). In the MAC-Bridge case, it reports all the ETB ports.
The Data Board can be chosen by means of the associated pull-down menu.
• Allowed To Go To field reports the port (or ports) on which the frames, having a
VID/MAC couple as in the entry selected on the table, are allowed to go, after
using the “>>" key.
The properties of an entry of the FDB table can be shown: after selecting an entry
of the table, the port (or ports) where the related frames are sent is shown on
Allowed To Go To field.
............................................................................................................................................................................................................................................................
4 - 23 8 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-180 Filtering Data Base/Static Unicast Filtering (Virtual Bridge case)
• Static Multicast Filtering sector:

This sector permits to insert, manually, static multicast bridging connections. The
inserted MAC addresses must be Multicast type (i.e. with the LSB of the most-
significant-octet fixed to 1, or odd values, e.g.: “27: 29: 30: aa: bb: cc”), otherwise the
operation will be refused by the system.
The meanings and operations on this sector are similar as the previously unicast sector,
with the difference that here, the incoming relevant frames (associated to the selected
VID/MAC Address couple) can be sent to a group of stations and, correspondingly, to
a group of ports ("Egress Ports").
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 3 9
............................................................................................................................................................................................................................................................
Figure 4-181 Filtering Data Base/Static Multicast Filtering (Virtual Bridge case)
• Dynamic Multicast Filtering sector, (see Figure 4-183, (pg. 4-241)):

It reports the Dynamic-Multicast FDB instances, in particular the IGMP dynamic
instances.
• VLANID: applicable only in case of Virtual or Provider Bridge (fixed to 1 in case of
MAC Bridge); it is the VLAN identifier whose incoming frames are to be
multicast to the relevant associated ports .
• MAC Group Address Destination: Multicast MAC Address that is associated to a
group of ports involved in a Multicast transmission.
• GroupStatus: it indicates the status of this entry Group. Possible values:
– RegisterByIgmp - the corresponding FDB instance was registered for IGMP
purposes.
– Other - the corresponding FDB instance does not fall into any of the above
cases.
• Egress Ports area:
This area lists the egress Ports towards which the selected Multicast Group entry
Frames are sent.
............................................................................................................................................................................................................................................................
4 - 24 0 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-182 Filtering Data Base/Dynamic Multicast Filtering (Virtual Bridge case)
The Search key causes the searching of the existing bridge instances of the FDB.
The Delete key deletes the selected bridge instance of the table.
The Apply key is used to create the static bridge instances, as above explained.
After setting all the desired parameters, click on the Close key to close the dialog window.
Figure 4-183 Filtering Data Base/Learned Mac Address Details
Ethernet Port: application table in the Connection context

An example of Application Table associated to the EthernetPort is illustrated in
Figure 4-184. It is displayed in the area A2, after selecting the EthernetPort in the
resource-tree. It reports, in tabular form, the main parameters related to the existing
connections into the selected Port:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 4 1
............................................................................................................................................................................................................................................................
“ETS InFlow", “Status", “ETS OutFlow".

Note: The Connection view displays in the tool-bar a further fast-
key, for quick recalling the EthernetPort option Create XC One
Step.
Note: In the Connection view the Bridge resource displayed into
the TREE area is named Switch.
The properties of a connection of the table are displayed in the information area (A3), after
selecting a row of the table. A pop-up menu, related to the selected resource, can be
activated, after selecting an item of the table and pressing the right button of the mouse.
The listed parameters, the displayed properties, and the options of the pop-up menu are
described in the successive paragraphs.
Figure 4-184 Ethernet Port: Connection application table
"XC" FastKey
Create Ets XC One Step (MAC & Virtual) for the Ethernet Port
This option is obtained, after selecting an active ETS Ethernet Port ( with Admin
............................................................................................................................................................................................................................................................
4 - 24 2 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Connection Î Ethernet Port Management Î Create Ets XC One Step.

or, if a LAG resource has been selected:
Connection Î Link Aggregator Group Management Î Create Ets XC One Step.
WARNING
This option is not available if the Port is ETB type.
This option can also be quickly recalled by the further fast-key added into the
tool bar.
This description applies only in Bridge Type = bridge 802.1D (MAC) or bridge
802.1Q (Virtual) as referred in “Configure ISA” (p. 4-62)); for the Provider
bridge case see “Create Ets XC One Step (Provider) for the Ethernet Port”
(p. 4-246).
The Remote Ethernet Ports are to be configured and connected also at the sdh
side; see OMSN Operator's Handbook listed in Table 1, (pg. 1-xxviii) for details
This connection is possible only if the Characterization Service for the two
involved ports has been set as Port-To-Port: see “Characterization Service of
an Ethernet Port” (p. 4-93).
An application example of MAC or Virtual XC creation is reported in “Ethernet Private
Line (EPL), end to end implementation example” (p. 1-21).
The function of this option is to create a One-Step cross-connection, i.e. the connection
point of an ETS EthernetPort in automatic mode, starting from the parent ethernet port
(Ingress). It can be done for ports not yet containing cross-connected resources (InFlow or
OutFlow), as one port is devoted to only one ethernet flow in transparent mode, in current
release. Therefore this operation will not be possible if the selected ethernet port contains
already connected resources: in this case an error message will be displayed (see
Figure 4-186, (pg. 4-245)).
The InFlow/Classifier/OutFlow resources will be automatically created with dummy
parameters, since the afferent traffic will not be classified nor policed.
To create a OneStep connection, fill fields and areas as follows:
• Port Eth. Ingress: name of the selected EthernetPort, fixed to ingress by the system.
• Port Eth. Egress: name of the egress EthernetPort
this item is browsed by means of the key, that recalls the Search dialogue
described in “Search in Views menu” (p. 4-28).
• Connection Type: (settable only after the choice of the above egress EthernetPort)
possible pull-down options:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 4 3
............................................................................................................................................................................................................................................................
– UniDirectional: to create 1 Inflow into the Ingress Port and 1 OutFlow into the
Egress Port, unidirectionally connected
– BiDirectional: to create 1 InFlow and 1 OutFlow into the Ingress Port and the
same into the Egress Port, bidirectionally connected.
• Inflow Section:
– Name Label: to indicate the user label (optional) of the inflow to be connected;
– Name Label BiDirectional: to indicate the user label (optional) of the second
inflow to be bidirectionally connected.
Note: This item will appear only if the bidirectional connection
type has been selected.
• Outflow Section:
– Name Label: to indicate the user label (optional) of the outflow to be connected;
– Name Label BiDirectional: to indicate the user label (optional) of the second outflow
to be bidirectionally connected.
Note: This item will appear only if the bidirectional connection
type has been selected.
• History area: reporting the operations executed by the program on doing the current
connection.
After setting all the desired parameters, click on the Apply key to set up the cross
connection.
Once the program executed the requested operations, click on Finish key to close the
dialog window.
The Print key causes the printing of the operation and its history.
............................................................................................................................................................................................................................................................
4 - 24 4 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-185 Create Ets XC “OneStep"
Figure 4-186 Error message on “Create Ets XC OneStep"
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 4 5
............................................................................................................................................................................................................................................................
Create Ets XC One Step (Provider) for the Ethernet Port

Connection Î Ethernet Port Management Î Create Ets XC One Step.
Connection Î Link Aggregator Group Management Î Create Ets XC One Step.
WARNING
This option can also be quickly recalled by the further fast-key added into the
tool bar.
This description applies only in Bridge Type case set to bridge 802.1S-AD
(Provider) as referred in “Configure ISA” (p. 4-62); for the MAC or Virtual
bridge case see “Create Ets XC One Step (MAC & Virtual) for the Ethernet
Port” (p. 4-242).
The Remote Ethernet Ports are to be configured and connected also at the sdh
side; see OMSN Operator's Handbook listed in Table 1, (pg. 1-xxviii) for details
The Ethernet Ports involved in this XC must have been already declared into the
“Member Set" of the VLAN to be associated here (SVID), by means of the
“Vlan Registration" described in “VLAN Registration” (p. 4-118).
The requested null Provider Traffic Descriptors must have been already
created, with all traffic parameters equal to zero; defining only the Traffic Type
of the provider connection.
The XC's here created are unicast type.
This connection is possible only if the Characterization Service for the two
involved ports has been set as Other: see “Characterization Service of an
An example of Provider domain distribution is illustrated in Figure 1-8, (pg. 1-13), an
application example of Provider XC creation is reported in “E-VPL, end to end
implementation example” (p. 1-27).
The function of this option is to create a One-Step cross-connection, i.e. the connection
point of an ETS EthernetPort in automatic mode, starting from the parent ethernet port
(Ingress). The Ingress and Egress connection points can also be contained in the same
port. The InFlow/Classifier/OutFlow resources will be automatically created by this
option.
............................................................................................................................................................................................................................................................
4 - 24 6 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
In order that an ETS port participates to the Provider S-VLAN distribution, an XC

involving the provider's resources is necessary, such as UNI/NNI or NNI/UNI, as created
by the present procedure.
To create a OneStep connection, fill fields and areas as follows (see Figure 4-187):
• Topology: to choose the XC type; possible pull-down options:
• UNIÎNNI: to create an XC from a User-Interface to a Network-Interface, where the
NNI interface is towards the Bridge domain; in this case the procedure will
continue, after clicking on Next >> key, as explained in point 1. (p. 4-247).
WARNING
This UNIÎNNI procedure provides to create a bidirectional UNI-NNI connection
over the same Ets Port.
• NNIÎUNI: to create an XC from a Network-Interface to a User-Interface, where the
NNI interface is towards the Bridge domain; in this case the procedure will
continue, after clicking on Next >> key, as explained in point 2. (p. 4-250).
Figure 4-187 Topology for “Create Ets XC OneStep" (Provider)
1. UNIÎNNI: refer to Figure 4-188, (pg. 4-252):

• Port Ingress: name of the selected EthernetPort, fixed by the system.
• Topology XC: set by the system to the value chosen in the previous window
• Traffic section:
– Ethernet Traffic Descriptor: name of the associated User traffic descriptor (TD):
the key permits to choose and associate a User traffic descriptor to the data
flow, recalling the dialogue described in “ETS Traffic Descriptor configuration”
(p. 4-51).
• Classifier Section: parameters meanings and setting are as explained in “Create
Eth2ETS Classifier” (p. 4-107).
Important! Some of the following fields will be /(will not be)
displayed, depending on the option selected in the field Topology
Class:
• Topology Class: possible options:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 4 7
............................................................................................................................................................................................................................................................
– VLAN+PRIO+EthType: in this case, the following parameters will be

displayed, and thus editable: Vlan / MaxVlan, Prio / MaxPrio, EthType
– VLAN+PRIO: in this case, the following parameters will be displayed, and
thus editable: Vlan / MaxVlan, Prio / MaxPrio
– VLAN+IP_DSCP: in this case, the following parameters will be displayed, and
thus editable: Vlan / MaxVlan, IpDSCP / MaxIpDSCP (Dscp range is 0 to 63)
– VLAN/No_Ip+EthType: in this case, the following parameters will be
displayed, and thus editable: Vlan / MaxVlan, EthType (EthType is without IP
values)
– VLAN/No_Ip: in this case, the following parameters will be displayed, and
thus editable: Vlan / MaxVlan, (EthType is fixed without IP values)
– Untagged+EthType: in this case, the following parameters will be displayed,
and thus editable: EthType; the other parameters will be fixed to set the frame
as “untagged”
– Untagged/No_IP+EthType: in this case, the following parameters will be
displayed, and thus editable: EthType (without IP values); the other parameters
will be fixed to set the frame as “untagged”
– Untagged/No_IP: in this case, no parameters will be displayed: the parameters
will be fixed to set the frame as “untagged”, and without IP values
– Untagged+Ip_DSCP: in this case, the following parameters will be displayed,
and thus editable: IpDSCP / MaxIpDSCP; the other parameters will be fixed to
set the frame as “untagged”
– Untagged: in this case, no parameter is displayed. The parameters will be fixed
to set the frame as “untagged”
– Default: in this case, no parameter is displayed. The parameters will be fixed to
set the frame as “dontCare”
the key opens Figure 4-189, (pg. 4-252), permitting to view the Topology
Classification Properties.
............................................................................................................................................................................................................................................................
4 - 24 8 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• Bridge Management section:

• Color Profile: (see “Create ETS InFlow for an Ethernet Port” (p. 4-100). For other
details see “Traffic Descriptor, Forwarding Priority and Class of Service”
(p. 4-54)); indicating the name of the association between the VLAN user-
priorities and the Provider-VLAN traffic coloring;
Note: If a ColorProfile is associated, the TrafficDescriptor must
be Regulated, and the priority field of the relevant associated
Classifier must be different from untagged or don't care.
the key permits to choose and associate a color profile, recalling the dialogue
described in “Color Profile” (p. 4-254).
the key gives the properties of the color profile currently associated
the “X" key permits to untie the data flow from the color profile
– disabled: the policing is not performed (i.e. all rates are forwarded, if the band
is available)
• S-VID: name of the associated Stacked-VLAN-ID that will be inserted into the
Provider-Frame:
the key permits to choose and associate a VLAN-ID, recalling the dialogue as
in Figure 4-190, (pg. 4-253); that window reports the VLAN’s registered over the
involved Ports, permitting to select a VLAN#, and then to associate it by clicking
on the Ok key.
Note: The ports involved in this XC must have been already
declared into the “Member Set" of the VLAN under consideration,
by means of “VLAN Registration” (p. 4-118).
• Protocol List: the user can manage the protocol control frames that can pass
through this XC:
the key opens the box as in Figure 4-191, (pg. 4-253), that lists all the
available protocols (Bit Name) and the relevant status; the cells in List Status
contain a pull-down menu that permits to enable or disable the access of the
corresponding protocol.
the key permits to view the list of the Protocols and their states.
For detailed description of items in the Bit name column, refer to “Protocols”
(p. 1-31).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 4 9
............................................................................................................................................................................................................................................................
• User Label section:

optional name that can be assigned by the user to describe the involved resources.
• History area: reporting the operations executed by the program on doing the
current connection, after clicking on the Apply key.
This option will create the following resources:
– one ETS InFlow under the Ingress port, with its associated Classifier;
– one Provider OutFlow under the Ingress port;
– one XC between the ETS InFlow and the Provider OutFlow under the Ingress
port;
See more details about the created resources reported in the Notes about created
resources: at the end of this paragraph.
2. NNIÎUNI: refer to Figure 4-192, (pg. 4-253):
• Port Ingress: name of the selected EthernetPort, fixed by the system.
• Topology XC: set by the system to the value chosen in the previous window
• Traffic section:
• Provider Traffic Descriptor: name of the associated Provider traffic descriptor
(TD):
the key permits to choose and associate a Provider traffic descriptor to the
data flow, recalling the dialogue described in “ETS Traffic Descriptor
configuration” (p. 4-51).
Note: In this case the associated TD must be null, i.e. with all
traffic parameters equal to zero; only the Traffic Type must be
defined.
• Bridge Management section:
disabled: the policing is not performed (i.e. all rates are forwarded, if the band is
available)
• S-VID: name of the associated Stacked-VLAN-ID that will be inserted into the
Provider-Frame:
the key permits to choose and associate a VLAN-ID, recalling the dialogue as
in Figure 4-190, (pg. 4-253); that window reports the VLAN’s registered over the
involved Ports, permitting to select a VLAN#, and then to associate it by clicking
on the Ok key.
Note: The ports involved in this XC must have been already
declared into the “Member Set" of the VLAN under consideration,
by means of “VLAN Registration” (p. 4-118).
............................................................................................................................................................................................................................................................
4 - 25 0 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• User Label section:

optional name that can be assigned by the user to describe the involved resources.
• History area: reporting the operations executed by the program on doing the
current connection, after clicking on the Apply key.
This option will create the following resources:
– one ETS InFlow under the Ingress port, with its associated Classifier;
– one Provider OutFlow under the Ingress port;
– one XC between the ETS InFlow and the Provider OutFlow under the Ingress
port;
See more details about the created resources reported hereunder.
------------------------------------------------------------------------
Notes about created resources:
For the meanings and settings of parameters of the created resources see:
– Create ETS InFlow, “Create ETS InFlow for an Ethernet Port” (p. 4-100).
– Create ETS OutFlow, “Create ETS OutFlow for an Ethernet Port” (p. 4-103).
– Create Eth2ETS Classifier, “Create Eth2ETS Classifier” (p. 4-107).
– Ets XC Properties, “ETS XC Properties for the ETS InFlow” (p. 4-261).
– CreateProviderInFlow “Create Provider InFlow for an Ethernet Port”
(p. 4-112) and “Create Provider InFlow / S-VID Management” (p. 4-114) and
also
– CreateProviderOutFlow “Create Provider OutFlow for an Ethernet Port”
(p. 4-115), (for more details about “S-VID")
The properties of the created resources (In/Out-Flows, Classifier, Ets-XC, etc.) are
illustrated in their relevant paragraphs of this handbook.
------------------------------------------------------------------------
After setting all the desired parameters, click on the Apply key to set up the cross
connection.
The procedure will return to the previous window, if clicking on <<Back key.
dialog window.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 5 1
............................................................................................................................................................................................................................................................
Figure 4-188 Create Ets XC “OneStep" (Provider, UNI-NNI)
Figure 4-189 Topology Classification Properties
............................................................................................................................................................................................................................................................
4 - 25 2 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-190 SVID Filter
Figure 4-191 Protocol List
Figure 4-192 Create Ets XC “OneStep" (Provider, NNI-UNI)
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 5 3
............................................................................................................................................................................................................................................................
Color Profile
This option is obtained, in the Create XC One Step window as depicted in
Figure 4-188, (pg. 4-252), after clicking on the key of the Color Profile item.
The function of this option is to manage the VLAN-Provider traffic coloring for the
selected Inflow resources. It reports the list of the existing Color Profiles, with relevant
name and color associated to the relevant priority.
• the Create button, permitting to create a new Color Profile as explained below;
• the Details button, permitting to see the properties of an existing Color Profile;
• the Modify button, permitting to change the properties of an existing Color Profile;
• the Delete button, permitting to delete an existing Color Profile;
• the Apply button, permitting “to bind" the selected Color Profile to the related Inflow;
• the Cancel button, permitting to close the window without associating a Color Profile;
• the Print button, permitting to print the properties of a selected Color Profile;
Note: More information about the traffic description, Policing,
Color Profile is reported in “Traffic Descriptor, Policing Mode and
Color Profile for ETS InFlow” (p. 4-255).
Figure 4-193 List of Color Profile
To create a Color Profile, click on Create key (Figure 4-193, (pg. 4-254)) and then the
dialog box indicated in Figure 4-194 will be displayed; fill fields and areas as follows:
• Color Profile Name: type a mnemonic name
• Color Mode: not operative; set by the system to “priority”
............................................................................................................................................................................................................................................................
4 - 25 4 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
• Priority0 ... to Priority7: choose, by means of the pull-down menu, the desired
provider-color (green = max-prior., yellow = medium-prior., red = min-prior.) to be
associated to the corresponding user-priority value (0 = min-Prior, 7 = max-Prior).
Click on the Ok button, to close and save the new Color Profile;
Click on the Cancel button, to close the dialog without saving the new Color Profile;
Click on the Help button, to get information about this window.
Figure 4-194 Create Color Profile
Traffic Descriptor, Policing Mode and Color Profile for ETS InFlow
Table 4-5 Traffic Descriptor, Policing Mode and Color Profile for INFLOW resource:
Traffic Descriptor Policing Mode Color Profile(1) Scheduler-Color (2)
“disabled" YELLOW
BEST EFFORT only “Unbound"
“color-blind" YELLOW or RED
“disabled" GREEN
GUARANTEED only “Unbound"
“color-blind" GREEN or RED
“Unbound" GREEN
“disabled"
“Bound" (3) GREEN or YELLOW
REGULATED
“color-blind" “Unbound" GREEN or YELLOW or RED
“color-aware" “Bound" (3) as assigned by the “Color Profile"
Note: on Table 4-5.

See “Create ETS InFlow for an Ethernet Port” (p. 4-100).
Green: max Provider-priority, Red: min priority
1.“Unbound" means that “No Profile" is associated to the Color Profile field, or the “Unbind"
key has been clicked; “Bound" means that a Color Profile has been assigned
2.In cases different from “color-aware", the coloring is performed by the scheduler, depending
on the traffic condition
3.In this case the “Priority" value of the Classifier associated to this InFlow must be different
from “untagged" or “don't care"
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 5 5
............................................................................................................................................................................................................................................................
Delete Ets XC One Step (MAC & Virtual) for the Ethernet Port
Connection Î Ethernet Port Management Î Delete Ets XC One Step.
Connection Î Link Aggregator Group Management Î Delete Ets XC One Step.
WARNING
This description applies only if the Bridge Type = bridge 802.1D (MAC) or
bridge 802.1Q (Virtual) see “Configure ISA” (p. 4-62)); for the Bridge Type =
bridge 802.1S-AD (Provider) see “Create Ets XC One Step (Provider) for the
The function of this option is to delete a One-Step cross-connection, that was created with
the Create ETS XC OneStep option detailed in “Create Ets XC One Step (MAC & Virtual)
for the Ethernet Port” (p. 4-242).
To delete a OneStep connection, fill fields and areas as follows:
• Port Ethernet: name of the selected EthernetPort, fixed by the system.
• Connection Type: (settable only after the choice of the above egress EthernetPort).
Possible pull-down options:
– BiDirectional: to delete the 1 InFlow and 1 OutFlow into the Ingress Port and also
the same ones into the Egress Port, bidirectionally connected.
– UniDirectional Egress: to delete the 1 Inflow into the Egress Port and the 1
OutFlow into the Ingress Port, unidirectionally connected
– UniDirectional Ingress: to delete 1 Inflow into the Ingress Port and the 1 OutFlow
into the Egress Port, unidirectionally connected.
deletion.
After setting all the desired parameters, click on the Apply key to delete the cross
connection.
dialog window.
............................................................................................................................................................................................................................................................
4 - 25 6 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-195 Delete Ets XC “OneStep" (MAC & Virtual)
Delete ETS XC One Step (Provider) for the Ethernet Port

Connection Î Ethernet Port Management Î Delete Ets XC One Step.
Connection Î Link Aggregator Group Management Î Delete Ets XC One Step.
WARNING
This description applies only in Bridge Type = bridge 802.1S-AD (Provider) as
referred in “Configure ISA” (p. 4-62); for the Bridge Type = bridge 802.1D
(MAC) or Bridge Type = bridge 802.1Q (Virtual) cases see “Color Profile”
(p. 4-254).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 5 7
............................................................................................................................................................................................................................................................
The function of this option is to delete a One-Step cross-connection, that was created with
the Create ETS XC OneStep option detailed in “Delete Ets XC One Step (MAC & Virtual)
for the Ethernet Port” (p. 4-256) or “Create Ets XC One Step (Provider) for the Ethernet
Port” (p. 4-246).
To delete a OneStep connection, fill fields and areas as shown in Figure 4-196, (pg.
4-258):
• XC Type: to choose the XC type; possible options:
– Port to Port: to delete an XC from an Eth Port to another Eth Port; in this case the
procedure will continue, after clicking on Ok key, as explained in “Color Profile”
(p. 4-254).
– Provider: to delete an XC in case the bridge is Provider type in this case the
procedure will continue, after clicking on Ok key, towards three different windows,
depending on the choice of the parameter XC Topology:
– point a. (p. 4-258), if “XC Topology" is UNI->NNI.
– point b. (p. 4-258), if “XC Topology" is NNI->UNI.
Figure 4-196 Topology for Delete Ets XC “OneStep" (Provider)
a. “XC Topology"= UNIÎNNI: refer to Figure 4-197, (pg. 4-259):

– Ethernet Port Ingress: name of the selected EthernetPort, fixed by the system.
– XC Topology: this parameter impacts on the parameters displayed by the
window, as explained before (it can be: UNI-NNI, or NNI-UNI).
After having chosen the above parameters, click on Search key to search the UNI-
NNI cross-connections existing between the indicated ports.
The existing cross-connections will be listed into the Active Cross Connections
area.
Select the XC to be deleted and then click on Apply key to delete it.
b. “XC Topology"= NNIÎUNI: refer to Figure 4-198, (pg. 4-260):
– Ethernet Port Egress: name of the selected EthernetPort, fixed by the system.
............................................................................................................................................................................................................................................................
4 - 25 8 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
– XC Topology: this parameter impacts on the parameters displayed by the

window, as explained before (it can be: UNI-UNI, or UNI-NNI, or NNI-UNI).
After having chosen the above parameters, click on Search key to search the NNI-
UNI cross-connections existing between the indicated ports.
The existing cross-connections will be listed into the Active Cross Connections
area.
Select the XC to be deleted and then click on Apply key to delete it.
The other parts of the window are:
connection.
dialog window.
Figure 4-197 Delete Ets XC “OneStep" (Provider, UNI-NNI)
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 5 9
............................................................................................................................................................................................................................................................
Figure 4-198 Delete Ets XC “OneStep" (Provider, NNI-UNI)
Create ETS XC for the ETS InFlow (not operative)

WARNING
wizard. See “Delete Ets XC One Step (MAC & Virtual) for the Ethernet Port”
(p. 4-246). The scope of this paragraph is to describe the settings, meanings
and properties of the resource parameters.
Modify ETS XC for the ETS InFlow

This option is obtained, after selecting a connected InFlow, by means of the contextual
Connection Î ETS InFlow Management Î Modify Ets XC.
The function of this option is to modify the parameters (such as Add Leg or Del Leg) of
the selected connected InFlow point.
All the reported information fields and operations are the same as those explained in
“Create ETS XC for the ETS InFlow (not operative)” (p. 4-260).
............................................................................................................................................................................................................................................................
4 - 26 0 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
ETS XC Properties for the ETS InFlow

Connection Î ETS InFlow Management Î Ets XC Properties.
The function of this option is to show the parameters set for the selected cross-connection.
All the reported information fields are read-only, and the same as those explained in
“Create ETS XC for the ETS InFlow (not operative)” (p. 4-260). Further this properties
window reports also the location (i.e. the parent resource) of the resources involved
(InFlow, OutFlow), thus facilitating the individuation of their position.
Figure 4-199 Ets XC Properties
Delete ETS XC for the ETS InFlow (not operative)

WARNING
This deletion must be done in one single step by means of the procedure
described in “Delete Ets XC One Step (MAC & Virtual) for the Ethernet Port”
(p. 4-256) and “Delete ETS XC One Step (Provider) for the Ethernet Port”
(p. 4-257).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 6 1
............................................................................................................................................................................................................................................................
Create ETS XC for the ETS OutFlow (not operative)

WARNING
(p. 4-246)..
Modify ETS XC for the ETS OutFlow (not operative)

WARNING
This option is not operative; his modification has to be executed by means of the
procedure described in “Modify ETS XC for the ETS InFlow” (p. 4-260) and
subsequents.
ETS XC Properties for the ETS OutFlow

This option is obtained, after selecting a connected OutFlow, by means of the contextual
Connection Î ETS OutFlow Management Î Ets XC Properties.
The function of this option is to show the parameters set for the selected cross-connection.
All the reported information fields are read-only, and the same as those explained in “ETS
XC Properties for the ETS InFlow” (p. 4-261).
Delete Ets XC for the ETS OutFlow

This option is obtained, after selecting a connected OutFlow point, by means of the
Connection Î ETS OutFlow Management Î Delete Ets XC.
This option permits to delete the selected cross-connection.
The XC will be deleted, in all its connected points, after clicking on the Yes key.
............................................................................................................................................................................................................................................................
4 - 26 2 P/N 8DG15785AAAA
Performance CT Operator’s Guide
............................................................................................................................................................................................................................................................
Performance
The Performance application permits to manage all the parameters related to the
performance context.
It can be entered by selecting, in the menu-bar: Views Î Performance, or by clicking on its
WARNING
All the dialogue windows described in this handbook are reported in
“FullWindow" mode, the information fields reported in the “TabbedWindow"
mode are the same (see “Windows Presentation: “FullWindow" and
“TabbedWindow"” (p. 4-28)).
WARNING
The following paragraphs report the terms green, yellow and red. They are the
symbolic colors used by the policer/scheduler functions of the system, in order
to mark the different priorities of the frames, consequent to the traffic
conditions:
• green: color of frames to be always relayed
• yellow: color of frames to be relayed if the band resource is available
• red: color of frames to be discarded
WARNING
The following paragraphs report the terms Unicast, Multicast and Broadcast
Frames:
• Unicast Frames: frames sent to a unique MAC device, having the Mac-
Destination Address with LSB of the most-significant-octet different from 1,
or even values, e.g.: “28: 29: 30: aa: bb: cc”
• Multicast Frames: frames sent to many MAC devices, having the Mac-
Destination Address with LSB of most-significant-octet equal to 1, or odd
values, e.g.: “27: 29: 30: aa: bb: cc”
• Broadcast Frames: frames sent to all MAC devices of the network, having
the Mac-Destination Address bits equal to all-1 value, e.g.: “ff: ff: ff: ff: ff:
ff”
Granularity 15Minutes/1Hour for the MPLS Switch

This option is obtained, after selecting the ES-Switch symbol, by means of the contextual
Performance Î MPLS Switch Management Î Granularity 15 Minutes
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 6 3
CT Operator’s Guide Performance
............................................................................................................................................................................................................................................................
or:
Performance Î MPLS Switch Management Î Granularity 1 Hour .
The function of this option is to set the Granularity of the Performance Monitoring (PM)
collected data for History Data. The History Data tables are described in “PM Data
Results (HISTORY and MAINTENANCE)” (p. 4-289).
To set the granularity, click on the desired item of the displayed menu.
If the Granularity 15 Minutes has been set (in this case the relevant text of the menu is bold
black, and the other one is greyed), the PM History will report the collected data with a 15
minutes granularity (HD-15min). In this case, the history data monitoring are reported
over 16 samples; the 17th monitoring sample will be overwritten over the 1st one.
If the Granularity 1 Hour has been set (in this case the relevant text of the menu is in bold
black, and the other one is greyed), the PM History will report the collected data with a 1
hour granularity (HD-1h). In this case, the history data monitoring are reported over 4
samples; the 5th monitoring sample will be overwritten over the 1st one.
Configure Eth. Aggr. for an Ethernet Port

This option is obtained, after selecting an active Ethernet Port (local or remote), by means
of the contextual pop-up menu, or by selecting in the menu-bar:
Performance Î Ethernet Port Management Î Configure Eth Aggr.
The function of this option is to manage the Performance Monitoring (PM) parameters of
the selected EthernetPort (local or remote), activating the data collection.
To configure the PM function for an Ethernet Port, fill fields and areas as follows:
• Incoming sector (these parameters are relative to the monitoring of the port incoming
side):
– Eth Inc Name: name of the selected EthernetPort incoming side (read only field)
– Data Collection: mark this box, in order to start the monitoring. Else, clear this
box, in order to stop the monitoring, in this way removing also the PM point.
• Outgoing sector (these parameters are relative to the monitoring of the port outgoing
side):
– Eth Out Name: name of the selected EthernetPort outgoing side (read only field)
............................................................................................................................................................................................................................................................
4 - 26 4 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-200 Ethernet Port Configure Monitoring (example)
Click on Ok key to confirm the chosen values. The Cancel key aborts the dialog. The Help
key gives detailed information about this window.
Eth Aggr. Properties of an Ethernet Port

This option is obtained, after selecting a monitored Ethernet Port, by means of the
Performance Î Ethernet Port Management Î Eth Aggr Properties.
The function of this option is to show the Performance Monitoring (PM) parameters and
the currently collected values (CD) for the selected Ethernet-Port. All the reported
information fields are read-only.
It contains the following information fields:
• Incoming/Outgoing - Configuration sectors:
these parameters are the current Eth Port monitoring configuration parameters; their
meanings are described in “Configure Eth. Aggr. for an Ethernet Port” (p. 4-264).
• Incoming - Information sector:
these fields indicate the current PM collected values
– TRCF: number of Total Received Correct ethernet Frames
– TRCO: number of Total Received Correct ethernet Octets
– TRCF Unicast: number of Total Received Correct Frames, Unicast type
– TRCF Multicast: number of Total Received Correct Frames, Multicast type
– TRCF Broadcast: number of Total Received Correct Frames, Broadcast type
– TDF: number of Total Discarded ethernet Frames for congestion or policing
– TRSEF: number of Total Received Service Errored ethernet Frames
– Start Time: indicating the time when the performance monitoring was started, as
described in “Configure Eth. Aggr. for an Ethernet Port” (p. 4-264).
• Outgoing - Information sector:
these fields indicate the current PM collected values
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 6 5
............................................................................................................................................................................................................................................................
– TTF: number of Total Transmitted ethernet Frames

– TTO: number of Total Transmitted ethernet Octets
– TTF Unicast: number of Total Transmitted Frames, Unicast type
– TTF Multicast: number of Total Transmitted Frames, Multicast type
– TTF Broadcast: number of Total Transmitted Frames, Broadcast type
– Start Time: indicating the time when the performance monitoring was started as
described in “Configure Eth. Aggr. for an Ethernet Port” (p. 4-264).
The Reset key causes the resetting of the reported values (not operative).
The Refresh key causes the updating of the reported values.
The Close key closes the window. The Print key causes the printing of the reported values.
The Help key gives detailed information about this window.
Figure 4-201 Ethernet Port Monitoring Properties (example)
PM Data Results (HISTORY and Maintenance)

The history and maintenance monitoring data results are reported in the main view, in the
Application-Table-Area (A2), after having selected the EthernetPort in the tree-area (see
example reported in “PM Data Results (HISTORY and MAINTENANCE)” (p. 4-289)).
............................................................................................................................................................................................................................................................
4 - 26 6 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
The HISTORY and Maintenance PM data for the Eth Port, reported into the application
table area (A2), are detailed in “Ethernet Port PM data tables (History and Maintenance)”
(p. 4-292).
Configure InFlow for an ETS InFlow

Performance Î ETS InFlow Management Î Configure ETS InFlow
WARNING
The selected InFlow has to be already cross-connected, otherwise the PM menu
is not active.
WARNING
• This option is possible only in Bridge Type = bridge 802.1S-AD (Provider)
case.
• This option is possible only if the InFlow ServiceType parameter is Ethernet,
see “Create ETS InFlow for an Ethernet Port” (p. 4-100).
the selected InFlow resource: activating the data collection, etc.
To configure the PM function for an InFlow, fill fields and areas as follows:
• InFlow Cd - Configuration sector:
Note: Cd = Current Data
– InFlow Name: indicating the name of the selected ETS InFlow (read only field)
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 6 7
............................................................................................................................................................................................................................................................
Figure 4-202 InFlow Configure Monitoring (example)
InFlow Properties of an ETS InFlow

This option is obtained, after selecting a monitored InFlow, by means of the contextual
Performance Î ETS InFlow Management Î ETS InFlow Properties.
WARNING
The selected InFlow has to be already cross-connected, otherwise the PM menu
is not active.
WARNING
case .
• This option is possible only if the InFlow ServiceType parameter is Ethernet,
see “Create ETS InFlow for an Ethernet Port” (p. 4-100).
the currently collected values for the selected InFlow. All the reported information fields
are read-only.
• InFlow Cd - Configuration sector:
Note: Cd = Current Data
these parameters are relative to the current monitoring configuration parameters; their
meanings are described in “Configure InFlow for an ETS InFlow” (p. 4-267).
• InFlow Cd - Information sector:
these fields indicate the current PM collected values (Cd= Current Data)
............................................................................................................................................................................................................................................................
4 - 26 8 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
– TRCFg: number of Total Received Correct ethernet Frames, green colored

– TRCOg: number of Total Received Correct ethernet Octets, green colored
– TRCFy: number of Total Received Correct ethernet Frames, yellow colored
– TRCOy: number of Total Received Correct ethernet Octets, yellow colored
described in “Configure InFlow for an ETS InFlow” (p. 4-267).
Figure 4-203 InFlow Monitoring Properties (example)

Application-Table-Area (A2), after having selected the ETS InFlow in the tree-area (see
The HISTORY and Maintenance PM data for the ETS InFlow, reported into the
application table area (A2), are detailed in “ETS InFlow PM data tables - History and
Maintenance” (p. 4-295).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 6 9
............................................................................................................................................................................................................................................................
Configure OutFlow for an ETS OutFlow

This option is obtained, after selecting a connected OutFlow, by means of the contextual
Performance Î ETS OutFlow Management Î Configure ETS OutFlow.
WARNING
• The selected OutFlow has to be already cross-connected, otherwise the PM
menu is not active.
as referred in “Configure ISA” (p. 4-62).
the selected OutFlow resource: activating the data collection, etc.
To configure the PM function for an OutFlow, fill fields and areas as follows:
• OutFlow Cd - Configuration sector: (Cd = Current Data)
– OutFlow Name: indicating the name of the selected ETS OutFlow (read only
field)
Figure 4-204 OutFlow Configure Monitoring (example)
OutFlow Properties of an ETS OutFlow

This option is obtained, after selecting a monitored OutFlow, by means of the contextual
............................................................................................................................................................................................................................................................
4 - 27 0 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Performance Î ETS OutFlow Management Î ETS OutFlow Properties.
WARNING
• The selected OutFlow has to be already cross-connected, and with a
configured PM, otherwise this PM menu is not active.
• This operation on OutFlow resource is not effective.
the currently collected values for the selected OutFlow. All the reported information fields
are read-only.
• OutFlow Cd - Configuration sector: (Cd= Current Data)
these parameters are relative to the current monitoring configuration parameters; their
meanings are described in “Configure OutFlow for an ETS OutFlow” (p. 4-270).
• InFlow Cd - Information sector:
these fields indicate the current PM collected values (Cd= Current Data)
– TTFg: number of Total Transmitted ethernet Frames, green colored
– TTOg: number of Total Transmitted ethernet Octets, green colored
– TTFy: number of Total Transmitted ethernet Frames, yellow colored
– TDFg: number of Total Discarded ethernet Frames, green colored
– TDFy: number of Total Discarded ethernet Frames, yellow colored
– TTOy: number of Total Transmitted ethernet Octets, yellow colored
described in “Configure InFlow for an ETS InFlow” (p. 4-267).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 7 1
............................................................................................................................................................................................................................................................
Figure 4-205 OutFlow Monitoring Properties (example)

Application-Table-Area (A2), after having selected the ETS OutFlow in the tree-area (see
The HISTORY and Maintenance PM data for the ETS OutFlow, reported into the
application table area (A2), are detailed in “ETS OutFlow PM data tables - History and
Maintenance” (p. 4-297).
............................................................................................................................................................................................................................................................
4 - 27 2 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
IGMP snooping statistics

WARNING
This option is not available both when the board:
• is configured as MAC Bridge (i.e. Bridge Type = bridge 802.1D)
• is configured as Virtual Bridge (i.e. Bridge Type = bridge 802.1Q).
as referred in “Configure ISA” (p. 4-62).
NE as Provider Bridge (i.e. Bridge Type = bridge 802.1S-AD) is requested to support
three groups of the IGMP statistic History Data counters:
• <VLANID, Granularity Period> associated to VLANID IGMP.
• <VLANID, Multicast Group, Granularity Period> associated to VLANID and
Multicast Group IGMP.
• <VLANID, Port, Granularity Period> associated to VLANID and Port IGMP.
Create IGMP <VLAN> for Node resource

Click with right key of the mouse on the Node resource ( ), and the contextual pop-up
menu appears (see Figure 4-206, (pg. 4-273)).
Figure 4-206 IGMP snooping statistics (Node resource)
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 7 3
............................................................................................................................................................................................................................................................
Select the Create IGMP <VLAN> option, and the following window opens:
Figure 4-207 IGMP <VLAN> creation (Node resource)
This window has two tabs used to start the performance monitoring fixing a VLAN ID,
one for granularity period 15 minutes and other for granularity period 24 hours.
• VLANID: this field contains a VLAN Identifier.
Selecting the button near to VLAN ID field the following window opens:
Figure 4-208 IGMP <VLAN> searching (Node resource)
This window is used to execute the search of the VLAN-ID. When a VLAN-ID is selected
into list the Apply button is enabled.
• Search: this button is used to start the search of the VLAN-ID.
• Apply: this button is used to apply the VLAN-ID secondary window calling.
............................................................................................................................................................................................................................................................
4 - 27 4 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Modify IGMP <VLAN> for Node resource

menu appears, as shown in Figure 4-206, (pg. 4-273).
Select the Modify IGMP <VLAN> option, and the following window opens:
Figure 4-209 IGMP <VLAN> modification (Node resource)
This window allows to execute a research, fixing a range of the VLAN Identifier (VLAID
From To) of all activated points. When a row from this table is selected, the button Delete
is enabled.
• Delete: this button is used to remove performance point previously created.
• Reset: this button is used to reset the counters previously started.
Properties IGMP <VLAN> for Node resource

Select the Properties IGMP <VLAN> option, and the following window opens:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 7 5
............................................................................................................................................................................................................................................................
Figure 4-210 IGMP <VLAN> properties (Node resource)
Fixing a correct range of the VLAN-ID and clicking on Search button all performance
point, that fall in this selected range, are retrieved. When a row of this table is selected the
button Details is enabled.
• Details: this button is used to show all counters related to the selected instance.
Clicking the Details button, one out of the following windows open, according to the
granularity:
Figure 4-211 IGMP <VLAN>15 minutes properties (Node resource)
............................................................................................................................................................................................................................................................
4 - 27 6 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-212 IGMP <VLAN> 24 hours properties (Node resource)
If the granularity period is 15 minutes no more sixteen rows can be present instead if the
granularity period is 24 hours then a row can be present.
The Refresh button is used to retrieve the counters directly from NE.
The column counters meaning of the shown tables are:
• Tx Joins - Number of sent IGMP Join messages (it is significant only in case IGMP
Proxy function is enabled).
• Rx Joins - Number of received IGMP Join messages.
• OK Joins - Number of successful received IGMP join messages.
• OK Joins - Number of unsuccessful received IGMP join messages.
• Tx Leave - Number of sent IGMP Leave messages (it is significant only in case IGMP
Proxy function is enabled).
• Rx Leave - Number of received IGMP Leave messages.
• Tx General Queries - Number of sent General IGMP Queries.
• Rx General Queries - Number of received General IGMP Queries.
• Tx Group Queries - Number of sent Specific IGMP Queries.
• Rx Group Queries - Number of received Specific IGMP Queries.
• Invalid IGMP Packet - Number of invalid received IGMP messages (it is related to
VLAN only).
• Port List - The list of ports that are members of any Multicast group inside that
VLAN.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 7 7
............................................................................................................................................................................................................................................................
Create IGMP <VLAN> for Ethernet port

Click with right key of the mouse on an active local (i.e. ETHLocPort#xx) or remote (i.e.
ETHRemPort#xx) Ethernet local ( with Admin Status = up), and the contextual pop-
up menu appears (see Figure 4-213, (pg. 4-278)).
Figure 4-213 IGMP snooping statistics (Port resource)
Select the Create IGMP <VLAN> option, and the following window opens:
............................................................................................................................................................................................................................................................
4 - 27 8 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-214 IGMP <VLAN> creation (Port resource)
• VLANID: this field contains an VLAN Identifier.
• Port User Label: this field contains the Ethernet port selected.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 7 9
............................................................................................................................................................................................................................................................
Figure 4-215 IGMP <VLAN> searching (Port resource)
• Apply: this button is used to apply the VLAN-ID.
When an entry is selected in this table the button Apply is enabled if the selected interface
is registered on this VLAN-ID.
............................................................................................................................................................................................................................................................
4 - 28 0 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Modify IGMP <VLAN> for Ethernet port

Click on an active local (i.e. ETHLocPort#xx) or remote (i.e. ETHRemPort#xx) Ethernet
local ( with Admin Status = up), and the contextual pop-up menu appears (see
Figure 4-213, (pg. 4-278)).
Select the Modify IGMP <VLAN> option, and the following window opens:
Figure 4-216 IGMP <VLAN> modification (Port resource)
is enabled.
Properties IGMP <VLAN> for Ethernet port

Click on an active local (i.e. ETHLocPort#xx) or remote (i.e. ETHRemPort#xx) Ethernet
local ( with Admin Status = up), and the contextual pop-up menu appears (see
Figure 4-213, (pg. 4-278)).
Select the Properties IGMP <VLAN> option, and the following window opens:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 8 1
............................................................................................................................................................................................................................................................
Figure 4-217 IGMP <VLAN> properties (Port resource)
granularity:
Figure 4-218 IGMP <VLAN>15 minutes properties (Port resource)
............................................................................................................................................................................................................................................................
4 - 28 2 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-219 IGMP <VLAN> 24 hours properties (Port resource)
• OK Joins - Number of successful received IGMP join messages.
• OK Joins - Number of unsuccessful received IGMP join messages. Possible causes:
– When join report is received on router port (static or dynamic).
– When multicast entry is configured statically and join report is received for
configured group.
– When join report could not be processed due to system related failures (memory
allocation failure or IPC failure etc..).
• Rx Leave - Number of received IGMP Leave messages.
• Tx General Queries - Number of sent General IGMP Queries (a generated general
Query is sent to all ports of a VLAN).
• Tx Group Specific Queries - Number of sent Specific IGMP Queries (a generated
specific Query is sent only on a specific port of a VLAN).
• Invalid IGMP Packet - Number of invalid received IGMP messages (an invalid IGMP
message is any kind of received IGMP message with either wrong IGMP PDU
checksum or invalid value of any IGMP PDU field.).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 8 3
............................................................................................................................................................................................................................................................
Create IGMP <VLAN, Multicast> for Node resource

menu appears (see Figure 4-206, (pg. 4-273)).
Select the Create IGMP <VLAN, Multicast> option, and the following window opens:
Figure 4-220 IGMP <VLAN, Multicast> creation (Node resource)
• VLANID: this field contains a VLAN Identifier.
• IP Address: this field contains the IP-address of the multicast group.
• IGMP Src IP Address: this field contains the IP-address of the IGMPv3 source, in our
case it is fixed to 0.0.0.0.
............................................................................................................................................................................................................................................................
4 - 28 4 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-221 IGMP <VLAN, Multicast> searching (Node resource)
• Apply: this button is used to apply the VLAN-ID secondary window calling.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 8 5
............................................................................................................................................................................................................................................................
Modify IGMP <VLAN, Multicast> for Node resource

Select the Modify IGMP <VLAN, Multicast> option, and the following window opens:
Figure 4-222 IGMP <VLAN, Multicast> modification (Node resource)
is enabled.
............................................................................................................................................................................................................................................................
4 - 28 6 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Properties IGMP <VLAN, Multicast> for Node resource

Select the Properties IGMP <VLAN, Multicast> option, and the following window
opens:
Figure 4-223 IGMP <VLAN, Multicast> properties (Node resource)
granularity:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 8 7
............................................................................................................................................................................................................................................................
Figure 4-224 IGMP <VLAN, Multicast>15 minutes properties (Node resource)
Figure 4-225 IGMP <VLAN, Multicast> 24 hours properties (Node resource)
• Current Rx Reports - Number of currently active IGMP hosts (number of received
IGMP Membership Reports for a certain <VLAN, multicast group> according to
“user-defined” granularity period).
............................................................................................................................................................................................................................................................
4 - 28 8 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
PM Data Results (HISTORY and MAINTENANCE)

Application-Table-Area (A2), after having selected the relevant resource in the tree-area;
as examples see Figure 4-226, (pg. 4-291) and Figure 4-227, (pg. 4-291).
Important! In the Performance application, one further fast key
is displayed in the tool-bar: PM:Refresh, in order to refresh the
displayed values. When in Graphical Format (not operative), three
further fast buttons are displayed in the tool-bar: GraphicalPM:
save an image of the graph, GraphicalPM: switch between decimal
and exponential format and GraphicalPM: switch between
Histogram and Bar representation.
Important! The PM Data view will report the History Data (HD)
folders HD15m or HD1h depending if the Granularity has been set
to 15 minutes or 1 hour (see “Granularity 15Minutes/1Hour for the
MPLS Switch” (p. 4-263)).
Acronyms used in PM views:
CD = Current Data
HD = History Data
The application table area (A2) contains different types of folders:
• HD 1h/HD 15m: it means History Data for 1 hour period, (or for 15 minutes, if the
granularity was so set). It reports the PM values measured over the entire granularity
intervals. This table reports the measured parameters in the last 4 intervals.
In HD-1h case, the history data monitoring are reported over 4 samples; the 5th sample
will be overwritten over the 1st one.
In HD-15min case, the history data monitoring are reported over 16 samples; the 17th
sample will be overwritten over the 1st one.
Reported values are the difference between current and previous monitoring period;
when the mouse is passed on a value, it pops-up the corresponding absolute value
(accumulated since the starting time).
• HD 24h: it means History Data for 24 hour period, reported values are absolute values
(accumulated since the starting time). This table reports the measured parameters only
in the last interval.
• CD: it means Current Data. It reports the PM values currently measured up to now,
since the PM was started. The monitored data of this view can be updated by clicking
on the PM refresh “fast key”.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 8 9
............................................................................................................................................................................................................................................................
• Maintenance: it reports some monitoring data useful for maintenance operations, such
as (examples): total afferent correct frames, errored frames (TRSEF), discarded frames
(TDF), frames coloration, etc. Reported values are absolute values. Different
monitoring parameters are reported for different resources (see the following sub-
paragraphs).
Note about POLLING: The Maintenance and CD folders display
also, in the Resource Information Area (A3), a dialog pane in
which the user can carry out a sampling in real time of the PM data
(polling), by choosing the Polling Time and the number of samples
(N. Retries), and pressing then on the Start Polling key. After
finishing the collection of the requested number of samples, the
polling is automatically stopped, if not yet stopped by the user (by
means of the Stop Polling key.
Further the total polling time is reported in the Polling Window field.
The polling test can be printed too, by means of the Print key.
Reported values are the difference between current and previous monitoring
period; when the mouse is passed on a value, it pops-up the corresponding absolute
value.
The History Data can be displayed either in tabular and in graphical format.
The choice between tabular and graphical format is done by means of the Configuration Î
Options, Program folder, at the Tabular/GraphicalArea item, as described in “Options of
Configuration menu” (p. 4-26).
When in Graphical Format (not operative), the choice between decimal and exponential
representation or between histogram and bar representation is done by means of the
relevant “fast PM keys" presented in the tool-bar.
An image of the graph (in histogram or bar representation), not operative, can be captured
by means of the relevant “GraphicalPM: save an image of the graph" fast PM key
presented in the tool-bar.
TABULAR format (example)
The view reports (see example in next Figure 4-226, (pg. 4-291) and Figure 4-227, (pg.
4-291)), in tabular form, the same PM parameters that are described in “Ethernet Port PM
data tables (History and Maintenance)” (p. 4-292) for the EthPort ,or “ETS InFlow PM
data tables - History and Maintenance” (p. 4-295) for the InFlow, or “ETS OutFlow PM
data tables - History and Maintenance” (p. 4-297) for the OutFlow.
............................................................................................................................................................................................................................................................
4 - 29 0 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 4-226 PM data results (Port example)
PM fast key
A2
A3
Figure 4-227 PM data results (InFlow example)
PM Refresh fast key
A2
A3
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 9 1
............................................................................................................................................................................................................................................................
Ethernet Port PM data tables (History and Maintenance)
WARNING
The PM Data view will report the History Data (HD) folders HD15m or HD1h
depending if the Granularity has been set to 15 minutes or 1 hour (see
“Granularity 15Minutes/1Hour for the MPLS Switch” (p. 4-263)).
CD = Current Data
HD = History Data
The application table area (A2) contains, for EthernetPort resources, the following PM
data folders:
• HD1h(15m) Inc., HD1h(15m) Out, HD24h Inc., HD24h Out, CD Rx, CD Tx, Maintenance Inc.,
Maintenance Out; the Local ports contain also a folder relevant to the physical
interface: Interface Maintenance.
• HD 1h(15m) Inc. /(Out): It reports the PM values measured over the entire granularity
intervals. I.e. the results of the HISTORY collected monitoring data relevant to the 1
hour period (or for 15 minutes, if the granularity was so set), for the Incoming
/(Outgoing) side of the port.
• HD 24h Inc. /(Out): it reports the results of the HISTORY collected monitoring data
relevant to the 24 hours period, for the Incoming /(Outgoing) side of the port.
• CD Rx /(Tx): It reports the PM values currently measured up to now, since the PM was
started. The monitored data can be updated by clicking on the PM Refresh “fast key”.
For the Receive and Transmit sides of the port
• Maintenance Inc. /(Out): it reports the results of the Maintenance monitoring data, for
the Incoming side /(Outgoing) of the port
• Interface Maintenance: (only for Local ports), it reports the results of the Maintenance
monitoring data relevant to the local physical interface.
The PM counters displayed in each folder are the following:
• HD1h Inc. (or HD15m Inc.) folder:
– Index: number of monitoring interval
– Period End Time: time when interval finished
– TRCF: number of Total Received Correct Frames
– TRCO: number of Total Received Correct ethernet Octets
– TRCF Unicast: number of Total Received Correct Frames, Unicast type
– TRCF Multicast: number of Total Received Correct Frames, Multicast type
– TRCF Broadcast: number of Total Received Correct Frames, Broadcast type
............................................................................................................................................................................................................................................................
4 - 29 2 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
– TRSEF: number of Total Received Service Errored ethernet Frames

– Start Time: indicating the time when the performance monitoring was started (by
means of “Configure Eth. Aggr. for an Ethernet Port” (p. 4-264)).
– Suspect Interval Flag: if this value is “true" it means the measurement data is
unreliable, if “false" it means the data is reliable.
• HD1h Out. (or HD15m Out.) folder:
– TTF: number of Total Transmitted ethernet Frames
– TTF Unicast: number of Total Transmitted Frames, Unicast type
– TTF Multicast: number of Total Transmitted Frames, Multicast type
– TTF Broadcast: number of Total Transmitted Frames, Broadcast type
– TTO: number of Total Transmitted ethernet Octets
– Start Time: as above explained
– Suspect Interval Flag: as above explained.
• HD24h Inc. folder:
it contains the same PM parameters as the above explained HD1h/15m Inc., but for a 24
h interval.
• HD24h Out. folder:
it contains the same PM parameters as the above explained HD1h/15m Out., but for a
24 h interval.
• CD Rx folder:
– TRCF: as above explained
– TRCO: as above explained
– TRCF Unicast: as above explained
– TRCF Multicast: as above explained
– TRCF Broadcast: as above explained
– TDF: as above explained
– TRSEF: as above explained
This folder presents also, in the Resource Information Area (A3), a dialog panel in
which the user can carry out a sampling in real time of the PM data (polling); for more
details see “PM Data Results (HISTORY and MAINTENANCE)” (p. 4-289).
• CD Tx folder:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 9 3
............................................................................................................................................................................................................................................................
– TTF: as above explained

– TTO: as above explained
– TTF Unicast: as above explained
– TTF Multicast: as above explained
– TTF Broadcast: as above explained
– TStart Time: as above explained
This folder presents also, in the Resource Information Area (A3), a dialog panel in
which the user can carry out a sampling in real time of the PM data (polling); for more
details see “PM Data Results (HISTORY and MAINTENANCE)” (p. 4-289).
• Maintenance Inc. folder:
– TRCF: as above explained
– TRCO: as above explained
– TRSEF: number of Total Received Service Errored Frames
– TRCF Unicast: as above explained
– TRCF Multicast: as above explained
– TRCF Broadcast: as above explained
– TDF: number of Total Discarded Frames for congestion or policing
– Retrieving Time: time of the last PM data refresh
The Maintenance folder presents also, in the Resource Information Area (A3), a dialog
pane in which the user can carry out a sampling in real time of the PM data (polling);
for more details see “PM Data Results (HISTORY and MAINTENANCE)” (p. 4-289).
• Maintenance Out. folder:
– TTF: as above explained
– TTO: as above explained
– TTF Unicast: as above explained
– TTF Multicast: as above explained
– TTF Broadcast: as above explained
– Retrieving Time: time of the last PM data refresh dialog panel for PM data
sampling (polling): as above explained.
• Interface Maintenance folder (only in LocalPorts):
............................................................................................................................................................................................................................................................
4 - 29 4 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
– Symbol Error: number of invalid data symbols (due to line code error) received by
the port when a valid carrier signal is present; (for 1000Mb/s i/f it is incremented
only once per frame, if one or more errors occurred); it is not incremented under a
collision event
– Media Available Exits: number of times the physical medium is not present (LOS
event)
– Jabber State Enters: number of times the physical interface enters in jabber state;
i.e. when Ethernet frames are longer than the MTU; (only for 10Mb/s i/f)
– False Carrier: number of times an invalid carrier signal is received, during IDLE
state; (only for 100 or 1000Mb/s interfaces)
– Retrieving Time: time of the last PM data refresh dialog panel for PM data
sampling (polling): as above explained
ETS InFlow PM data tables - History and Maintenance
WARNING
• This PM view is effective only if the InFlow ServiceType parameter is
Ethernet, see “Create ETS InFlow for an Ethernet Port” (p. 4-100).
• The PM Data view will report the History Data (HD) folders HD15m or
HD1h depending if the Granularity has been set to 15 minutes or 1 hour (see
“Granularity 15Minutes/1Hour for the MPLS Switch” (p. 4-263)).
CD = Current Data
HD = History Data
The application table area (A2) contains, for InFlow resources, the following PM data
folders:
• HD 1h/(15m): it reports the results of the HISTORY collected monitoring data relevant
to the 1 hour period (or for 15 minutes, if the granularity was so set).
• HD 24h: it reports the results of the HISTORY collected monitoring data relevant to the
24 hours period.
• CD: It reports the PM values currently measured up to now, since the PM was started.
The monitored data can be updated by clicking on the PM refresh “fast key”.
• QoS Maintenance: it reports the results of the Maintenance monitoring data, for the QoS
monitoring, with the indications about colorations of the afferent traffic and of the
discarded frames.
The PM data counters displayed in each folder are the following:
• HD1h/(15m) folder:
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 9 5
............................................................................................................................................................................................................................................................

– TRCFg: number of Total Received Correct Frames, green colored
– TRCFy: number of Total Received Correct ethernet Frames, yellow colored
– TRCOg: number of Total Received Correct ethernet Octets, green colored
means of “Configure InFlow for an ETS InFlow” (p. 4-267)).
• HD24h folder:
it contains the same PM parameters as the above explained HD1h or HD15m, but for a
24 h interval.
• CD folder:
– TRCFg: as above explained
– TRCOg: as above explained
– TRCFy: as above explained
– TRCOy: as above explained
This folder presents also, in the Resource Information Area (A3), a dialog pane in which
the user can carry out a sampling in real time of the PM data (polling); for more details
see “PM Data Results (HISTORY and MAINTENANCE)” (p. 4-289).
• QoS Maintenance folder:
– TRCOg: as above explained
– TRCFg: as above explained
– TRCFy: number of Total Received Correct Frames, yellow colored
– TRCOr: number of Total Received Correct ethernet Octets, red colored
– TRCFr: number of Total Received Correct Frames, red colored
............................................................................................................................................................................................................................................................
4 - 29 6 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
ETS OutFlow PM data tables - History and Maintenance
WARNING
This PM view on OutFlow resource is not effective.
The application table area (A2) contains, for OutFlow resources, the following PM data
folders:
• HD 1h/(15m): it reports the results of the HISTORY collected monitoring data relevant
to the 1 hour period (or for 15 minutes, if the granularity was so set).
• HD 24h: it reports the results of the HISTORY collected monitoring data relevant to the
24 hours period.
• CD: It reports the PM values currently measured up to now, since the PM was started.
The monitored data can be updated by clicking on the PM refresh “fast key”.
• QoS Maintenance: it reports the results of the Maintenance monitoring data, for the QoS
monitoring, with the indications about colorations of the afferent traffic and of the
discarded frames.
The PM data counters displayed in each folder are the following:
• HD1h/(15m) folder:
– TTFg: number of Total Transmitted Correct Frames, green colored
– TTOg: number of Total Transmitted Correct ethernet Octets, green colored
– TDFg: number of Total Discarded ethernet Frames, green colored
– TDFy: number of Total Discarded ethernet Frames, yellow colored
means of ConfigureOutFlow. or DataCollection).
• HD24h folder:
it contains the same PM parameters as the above explained HD1h or HD15m, but for
a 24 h interval.
• CD folder:
– TTFg: as above explained
– TTOg: as above explained
– TTFy: as above explained
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 4- 2 9 7
............................................................................................................................................................................................................................................................
– TDFg: as above explained

– TDFy: as above explained
– TTOy: as above explained
This folder presents also, in the Resource Information Area (A3), a dialog pane in which
the user can carry out a sampling in real time of the PM data (polling); for more details
see “PM Data Results (HISTORY and MAINTENANCE)” (p. 4-289).
• QoS Maintenance folder:
– TTOg: as above explained
– TTFg: as above explained
– TDFg: number of Total Discarded Frames due to congestion or policing, green
colored
– TDFy: number of Total Discarded Frames due to congestion or policing, yellow
colored
............................................................................................................................................................................................................................................................
4 - 29 8 P/N 8DG15785AAAA
5 Maintenance
Overview
This chapter describes all the details for periodic checks, faults locations, repair
procedures, and restore to normal operations.
• “General trouble-shooting flow-chart for ISA-ES boards” (p. 5-2)
• “Alarms, states and commands on ISA-ES board front cover” (p. 5-3)
• “Troubleshooting by means of the ES Craft Terminal” (p. 5-4)
• “ISA-ES Units replacement” (p. 5-18)
• “Software Upgrading/Downgrading” (p. 5-19)
The Maintenance general metodology is reported on the equipment-specific Operator
Handbooks; please refer to them for: equipment troubleshooting and relevant
interventions.
Only the maintenance issues relevant to hardware and software relative to ISA-ES board
are hereinafter reported.
............................................................................................................................................................................................................................................................
ISA ES1/4 Release 3.0 Maintenance
CT Operator’s Guide General trouble-shooting flow-chart for ISA-ES boards
............................................................................................................................................................................................................................................................
General trouble-shooting flow-chart for ISA-ES boards

In case of faults/defects/failures please follow the general troubleshooting procedure
illustrated by the following flow-chart.
Figure 5-1 General Flow-chart for ISA-ES board troubleshooting
START
AN ALARM
IS PRESENT
OBSERVE THE LEDS ON THE FRONT COVER

OF THE ISA-ES BOARD
(see page (5-3))
IS THE
NO
ISA-ES BOARD
BICOLOR LED RED?
YES
THROUGH PUSH-BUTTON
ON ISA-ES BOARD
RESTART THE UNIT
DOES
THE ALARM NO TRANSITORY
CONDITION FAILURE
PERSIST ?
YES
THE ISA-ES BOARD

IS FAULTY, REPLACE IT ACCORDING CONNECT THE PC TO THE
EQUIPMENT AND, ACCORDING TO
TO THE DESCRIBED PROCEDURE THE TYPE OF DETECTED ALARM,
(see page (5-18)) PROCEED AS STATED IN
page (5-4)
END END
............................................................................................................................................................................................................................................................
Maintenance ISA ES1/4 Release 3.0
Alarms, states and commands on ISA-ES board front cover CT Operator’s Guide
............................................................................................................................................................................................................................................................
Alarms, states and commands on ISA-ES board front cover

The state of the ISA-ES unit is indicated by a bi-colored LED, placed in the lower side of
the ISA-ES board front cover:
• when red, it indicates internal failure
• when green, it indicates in service unit
In order to give some commands, there is one RESTART push-button on the front of the
ISA-ES unit:
• restart push-button, to restart the unit's software
The positions of the LEDs and command push-buttons on the ISA-ES front cover plate are
shown on the equipment-specific Technical Handbook, listed in Table 1, (pg. 1-xxviii).
On-board Switches: see Table 5-8, (pg. 5-18).
............................................................................................................................................................................................................................................................
CT Operator’s Guide Troubleshooting by means of the ES Craft Terminal
............................................................................................................................................................................................................................................................
Troubleshooting by means of the ES Craft Terminal

The information about the alarms will be mainly obtained by means of the craft terminal
through the Alarms Surveillance (AS) data, the alarms/status indications presented in the
main view, and in the “properties windows", depending on the level of the resource
under observation.
The troubleshoot procedure by means of the the ES-CT consists of the following steps:
a. observing the active alarms on the Severity Alarms Synthesis, Domain Alarms
Synthesis and Management States Control Panel, see Figure 5-2, (pg. 5-5): they
resume all the active alarms on the ES-Node. Table 5-3, (pg. 5-7), Table 5-4, (pg.
5-8) and Table 5-5, (pg. 5-8), and up describe the meaning of these alarms/statuses
and the relevant maintenance actions. See the following “Alarms/states
organization in the main view” (p. 5-5).
b. observing the alarms reported in the tree-area A1; this structure immediately
helps to localize the alarmed resource, since the alarm condition is directly
indicated near every resource symbol. The meaning of these alarms is described in
“Alarms indications in the Resources TREE area (A1)” (p. 5-9).
c. the properties view (in the “Transmission" context) of each selected resource
contains the “Alarms" sector that gives information about the presence of alarms in
the resource under observation. See example in “Alarms indications in the resource
properties” (p. 5-10). The information about alarms can also be observed in the
resource-information-area A3 (reporting the same information as the property-
view). The “Maintenance Actions" in case of alarms is reported in Table 5-7, (pg.
5-17)
d. in case of alarm presence, open the Alarms Surveillance application to
troubleshoot. This application gives the details of the detected alarms and helps for
their localization. See “Alarms Surveillance (AS)” (p. 5-14) and, in particular,
Table 5-7, (pg. 5-17), indicating the “Probable Cause" of fault and relative
“Maintenance Action".
e. the synthesis of some alarms relevant to the ISA-ES boards is also reported on the
views presented in SDH-CT (RUM, RUTM, RUP, ICP, VM, etc...): the details
about these alarms and further maintenance interventions are reported in the
equipment-specific Operator Handbooks, listed in Table 1, (pg. 1-xxviii).
In case of unit replacement, follow the indications reported in “ISA-ES Units
replacement” (p. 5-18).
............................................................................................................................................................................................................................................................
Troubleshooting by means of the ES Craft Terminal CT Operator’s Guide
............................................................................................................................................................................................................................................................
Alarms/states organization in the main view

WARNING
The critical (CRI) or major (MAJ) alarms indicate severe alarms that could
have impact on the current traffic (interruption or degrade), thus requiring a
rapid intervention to restore the regular working condition of the equipment.
Figure 5-2 Alarms/statuses organization in the main-view

title
menu bar
tool bar
Severity Alarms Domain Alarms
curr. Appl. Synthesis Synthesis
Appl. tabs
A2
A3
Resource Alarms
Indications
A1
message
row
Manag. States
Control Panel
A message, activated by the mouse facility when passing over an alarm or status icon,
provides the alarm or status complete denomination: a text appears in the “message-row"
at the bottom left corner of the view.
The area A3 reports alarms indications too, related to the resource that has been selected in
the A2 area.
The tree-structure A1 immediately helps to localize the alarmed resource, since the alarm
condition is directly indicated near every resource symbol.
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Alarms synthesis indications

Referring to Figure 5-2, (pg. 5-5), the icons CRI, MAJ, MIN, WNG, IND are part of the
Severity Alarms Synthesis area, they are described in Table 5-2, (pg. 5-7); they report the
actual number of alarms grouped for different severities, and the relevant color as assigned
by the ASAP.
If not alarmed, every alarm icon is green and rectangular shaped.
If alarmed, every alarm icon is ASAP-colored and circular shaped.
The icon TRNS is part of the Domain Alarms Synthesis area, described in Table 5-4, (pg.
5-8). it reports the actual number of alarms pertaining to the transmission domain. Its color
corresponds to the highest severity among the set of the active alarms for this domain,
according to the rules in Table 5-1, (pg. 5-7).
The alarms SUP, LAC ("key"), COM, OS, MGR are part of the Management States
Control Panel, presented in Table 5-5, (pg. 5-8).
All these indications (except for SUP, LAC, COM, OS, MGR) are the summaries of
particular types of alarms detected by the equipment, further they report the total counting
of alarms per group; the specific cause of alarm is to be found as indicated in this and in
the following paragraphs.
Note: The customization of the ASAP's (Alarms Severity
Assignment Profile) can change the colors and the assignment of
each alarm to the various groups of alarms; the ASAP
configuration is reported in “Alarms Severity (ASAP management)
in Configuration menu” (p. 4-33) and in “Set Alarms Severities”
(p. 4-37).
Table 5-1, (pg. 5-7) reports the association between the colors of the Alarms and their
Severity.
Table 5-2 reports the colors of the Management States Control Panel when not in “normal"
condition.
Example of alarmed representation: (colored and with internal circular shape).
Example of non-alarmed representation: (green and with internal rectangular

shape)
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Table 5-1 Alarms colors and Severity association

Alarm Color Severity
RED CRITICAL (CRI)
ORANGE MAJOR (MAJ)
YELLOW MINOR (MIN)
PALE BLUE WARNING (WNG)
WHITE INDETERMINATE (IND)
GREEN NO ALARM
Table 5-2 Colors of the Management States when in “abnormal" condition

(alarmed)
State State Color
SUP: not supervised BROWN
“key" (LOCAL ACCESS STATE): denied CYAN
COM: NE unreachable RED
OS: NE managed by the OS CYAN
MGR: managed by RM CYAN
Table 5-3 Severity Alarms Synthesis indications

Mnemonic Alarm/Status Description Maintenance
CRI Critical alarms Synthesis of alarms that need immediate
troubleshooting (typical: NE isolation).
Note. Open the AS application: see detailed
indications in “Alarms Surveillance (AS)”
(p. 5-14).
MAJ Major (Urgent) alarms Synthesis of alarms that need immediate
troubleshooting.
(p. 5-14).
MIN Minor (Not urgent) alarms Synthesis of alarms for which a delayed
troubleshooting can be defined.
(p. 5-14).
WNG Warning alarms Synthesis of alarms due to failure of other NE
in the network.
(p. 5-14).
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................

IND Indeterminate alarms Synthesis of alarms not associated to the
previous severities. Not operative.
Open the AS application: see detailed
(p. 5-14).
Table 5-4 Domain Alarm Synthesis indication

TRNS Transmission alarms Synthesis of alarms of the Transmission
domain.
(Indicated as “Communications" Events in
the AS application, see “Alarms
Surveillance (AS)” (p. 5-14)
Table 5-5 Management States Control Panel

SUPs Supervision state Indicates whether or not the NE is under
supervision.
Used in the OS.
Local Access state Indicates whether the Craft Terminal has the
OS permission to manage the NE (granted:
rectangular shape) or not (denied: circular
shape).
COM Operative System Isolation Identifies the operational state of the
connection between NE and Craft Terminal:
“disabled" (NE: Unreachable), or “Enabled"
(NE: Reachable).
OS NE managed by the OS The NE is being managed by the OS.
MGR Upper Management Indicates that the NE is supervised by an
assignment Upper Manager (BM or RM, etc.).
Note: Alarms Severity Assignment Profile (ASAP) can modify the

assignment of each alarm root to the various synthesis.
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Alarms indications in the Resources TREE area (A1)
Figure 5-3 TREE area example
alarmed resource
not alarmed resource
Alarms Visualization
Alarms summary: (at level of ISA-ES node)
The Alarms summary is visualized only at the ES node level, reporting the colors of
the maximum alarm severities, detected in the current ATM switch (inner circle) and in
the contained resources (outer rings). If the inner circle is not colored, it means that the
alarms are in the contained resources and not in the parent one.
Alarms synthesis (only at the ports level):
The Alarms synthesis is visualized at all the ports, reporting all the alarm severity
colors (in form of concentric rings), detected in the current resource (inner circle) and
in the contained resources (outer rings). If the inner circle is not colored, it means that
the alarms are in the contained resources and not in the parent one.
No alarm:
The colors of the alarms indicate the associated severity as specified in Table 5-1, (pg.
5-7).
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Alarms indications in the resource properties

The properties view of each selected resource contains the “Alarms" sector that gives
information about the presence of alarms in the resource under observation.
Figure 5-4, (pg. 5-11) is an example of property view.
It is obtained by means of the menu path: Transmission Î Ethernet Port Management
Î Ethernet Port Properties.
The alarms properties are found also for the other ISA-ES resources where the alarms are
foreseen.
The conditions of alarms relevant to a selected resource (selected in the list of the A2 area)
can also be observed in the resource-information-area A3 (reporting the same information
as the property-view); see example in Figure 5-5, (pg. 5-12).
The non-alarmed condition of an alarm is represented by a green color icon and a “-" sign
in the box.
The alarmed condition is represented by a color and an “X" sign in the box (the color of
the relevant alarm is assigned by the ASAP: see Table 5-1, (pg. 5-7)):
Not alarmed condition:
Alarmed condition:
The alarms that can be found in the property-view are listed and described in
Table 5-7, (pg. 5-17), where the relevant maintenance actions are reported too.
............................................................................................................................................................................................................................................................
5 - 10 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 5-4 Example of Ethernet Port Properties alarms
Alarms indications
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 5-11
............................................................................................................................................................................................................................................................
Figure 5-5 Example of alarms reported in the “resource information area A3"
Resource Alarms Indication
............................................................................................................................................................................................................................................................
5 - 12 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Alarms relevant to ES-Boards observable on SDH-CT

The synthesis of some other alarms relevant to the ISA-ES boards are reported on the
views presented in SDH-CT: RUM (unit-missing), RUTM (unit-mismatch), RUP (unit-
problems), ICP (communications-problems), VM (version-mismatch), etc. The details
about these alarms and further maintenance interventions are reported in the equipment-
specific OMSN Operator Handbook, listed in Table 1, (pg. 1-xxviii).
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 5-13
............................................................................................................................................................................................................................................................
Alarms Surveillance (AS)

In case of presence of alarms, observed as seen in the previous paragraphs, open the
Alarms Surveillance (AS) application to troubleshoot. For this purpose select, in the
menu-bar, the Diagnosis pull down menu and then the Alarms cascading menu; the
following options are offered:
• ISA Alarms: all the ES-node alarms are listed in the Alarms Surveillance report that is
activated.
• Object Alarms: only the alarms relevant to the selected object are listed in the Alarms
Surveillance report.
• Transmission Alarms: only the alarms relevant to the Transmission context are listed
in the Alarms Surveillance report.
Selecting one of these latter options, the Alarms Surveillance (AS) report is displayed as
for the example in the following figures (this example is relative to “ISA Alarms" option).
This application shows a synthesis of the ES-NE alarms (“Counter Summary" window, see
Figure 5-6, (pg. 5-14)) with the sum of all alarms, and then a detailed list of alarms
belonging to a group selected in the previous window (see Alarms Supplest in
Figure 5-7, (pg. 5-15)).
Figure 5-6 AlarmsSurveill.-“Counter Summary" window (“ISA Alarms" example)
............................................................................................................................................................................................................................................................
5 - 14 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Figure 5-7 AlarmsSurveill.-“Alarm Sublist" window (“ISA Alarms" example)
Detailed information for each alarm is supplied in the “Alarm Sublist" window. For
example: the resource where the alarm is detected, its status, type, probable cause of the
relevant alarm, etc. The colors of the alarms indicate the associated severity as specified in
Table 5-1, (pg. 5-7).
The listing of all the Alarms or the filtering of a class of them is also possible. The filtering
is achieved by double clicking on a row of alarm, in the “Counter Summary" little window
(Figure 5-6, (pg. 5-14)); e.g. the alarms relative to the ISA-ES side are displayed, in the
“Alarm Sublist" window, by double clicking on the last row of the “Counter Summary"
window.
The alarms scenario is indicated by the colors of the alarms and by the information
displayed in the table. For instance, referring to Figure 5-7, (pg. 5-15), if an alarm is still
active, the whole row has the same color of its relevant “Perceived Severity"; else, if it has
been cleared, the color of the row is green (except the “Perceived Severity"). The same
information is reported in the “Clearing Status" column.
A more detailed description of the “Alarms Surveillance" (AS) application is given in the
“AS Operator's Handbook".
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 5-15
............................................................................................................................................................................................................................................................
The main information obtained by means of the AS application is shortly described in the
following Table 5-5, (pg. 5-8) and Table 5-4, (pg. 5-8). The maintenance action must take
into account the equipment or board or resource where the alarm is detected.
Table 5-6 Alarms Surveillance information general description

Title Description
• Perceived Severity The severity assigned to the alarm is indicated, with the
relevant color, i.e.: MAJOR, MINOR, WARNING....
• Event date and time Indicates year, month, day and hour of the alarm.
• Friendly Name Identifies the rack, subrack, board, port, and TP in which
the alarm is detected, e.g.: / r01sr1sl01/#port01-E1S
• Event Type Indicates the family type of the alarm as subdivided in the
ASAP list, i.e.: COMMUNICATIONS, etc.
• Probable Cause The fault/problem is indicated, i.e.: loss of signal,
transmitter degraded, replaceable unit missing,resource
isolation, ...
• Reservation Status Indicates if the alarm is reserved (RSV) or not (NRSV)
according to security management.
• Clearing status Indicates if the alarm condition is terminated (CLR) or is
still active (NCLR). If cleared it has a green background,
• Acknowledge status Indicates if the alarm has been acknowledged (ACK),
with the “Attend" button on the COMPACT ADM unit, or
not ( NACK).
• Correlated notification flag Not used
• Repetition counter Not used
............................................................................................................................................................................................................................................................
5 - 16 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Table 5-7 “Probable Cause" of alarms and relevant maintenance actions

Probable cause Name and/or
Acronym of Displayed Alarm Maintenance
LOS (Loss Of Signal) Local Port: problems on ethernet line receive path.
Check the line continuity on RX LAN.
LOF (Loss Of Frame GFP) Remote Port: problems on network RX path or on far-end
network source.
Check the network RX path, and far-end network source.
TSF (Trail Signal Fail) Remote Port: problems on SDH network receive path.
Check the integrity of network path RX (ports, cross-
connections, etc.) and relevant connections.
PLM (PayLoad Mismatch) Remote Port: the payload is not congruent with the
expected one.
Check the involved remote Ethernet ports configuration.
GTM (GFP Type Mismatch) Remote Port: the GFP frame is not congruent with the
expected one.
(not operative)
Check the involved remote Ethernet ports configuration.
DEG (Sdh Concatenation Remote Port: problems on SDH network path, when an L-
Degrade) CAS VirtualConcatenation is established.
Check the SDH network path.
CSF (Client Signal Fail) Remote Port: problems on far-end ethernet i/f, or on
network path (if CSF is bidirectional).
Check the far-end Ethernet port signal, or the network
path.
LAGD (Lag Degrade) Almost 1 member of the LAG is out-of-service.
Check the alarm status of the port that are involved in the
LAG.
LAGL (Lag Loss) All the members of the LAG are out-of-service.
Check the alarm status of the port that are involved in the
LAG.
TD (Traffic Disabled) Local Port: manual command for maintenance purpose
which set in down the in/out traffic for a port (see “Traffic
Management of an Ethernet Port” (p. 4-93)). Since is a
maintenance procedure it doesn’t require further check.
Note: cleared means that the alarm isn’t displayed by the ES-CT.
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 5-17
CT Operator’s Guide ISA-ES Units replacement
............................................................................................................................................................................................................................................................
ISA-ES Units replacement

WARNING
This procedure is applicable either for ES1 or ES4 board.
In case that the ISA-ES unit is faulty, replace it by doing the following operations:
1. remove the faulty unit from the equipment
2. insert a new unit into the same slot of the equipment.
(ensure the flash-card of the new unit is formatted: see Table 5-8, (pg. 5-18) for “MIB-
RESET”)
WARNING
For ISA-ES1-8FE or ISA-ES1-3FE equipped in 1642EM/1642EMC: pull out the
flash-card from ISA board and insert it into the “Main-Board”, in order to
format it. After finished format, insert it back into ISA board.
The start-up of the new unit can take some minutes.
The ISA-ES board contains two DIP-Switches I1-1 and I1-2 (whose position inside the
board is reported in MS documents indicated into the 1640FOX/1650SMC/1660SM
Technical Handbooks), in order to execute some special operations, as described in the
following table:
Table 5-8 DIP-SWITCHES operations

DIP-SWITCH I1-1 DIP-SWITCH I1-1 Function
OFF OFF Normal
OFF ON MIB RESET (Flash-ROM format)
ON OFF Reserved
ON ON Reserved
Note:
In case of board presetting by using the above dip switches:
– set the switches on desired configuration
– insert the board on the shelf
– wait some minutes until the CT will take the control again
– extract the board and return the switches in their “normal” configuration
– insert the board on the shelf again
– wait some minutes until the CT will take the control again.
............................................................................................................................................................................................................................................................
5 - 18 P/N 8DG15785AAAA
Software Upgrading/Downgrading CT Operator’s Guide
............................................................................................................................................................................................................................................................
Software Upgrading/Downgrading
The migration of the ISA-ES software from a version to another can be requested in
maintenance cases as:
a. software product evolution
b. roll back of the software product to older or previous versions.
In these cases, a software package installation (see “NE-ES package installation
procedure” (p. 3-28)) and a download operation (see “NE-ES software downloading”
(p. 3-36)) are necessary.
WARNING
In case of migration from a release to another one, the presence of the previous
release of SDH-USM software package (see 1320CT Operator Handbook, listed
in Table 1, (pg. 1-xxviii)) is necessary, in order to download the new software
release, otherwise the equipment-SW and the CT-SW are not aligned and the
equipment cannot be supervised anymore. Hence the operator is recommended
to keep the previous release of the SDH-USM, until the actual SW-package
will be downloaded into the equipment.
WARNING
In case of migration to a new release containing a new “ADD-ON" (Service
Specific packet such as the ES-swp), from an old release containing another
service packet (for instance an ATM-swp), the download of the software into the
NE must be done in two steps:
• first step downloading the new SDH packet associated with the known
service packet (e.g.: enhanced OMSN with ATM, see also “NE-ES package
installation procedure” (p. 3-28))
• second step downloading the new SDH packet associated with the new
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA 5-19
CT Operator’s Guide Software Upgrading/Downgrading
............................................................................................................................................................................................................................................................
WARNING
In case of UPGRADE from an OLD release to a NEW release that is not
consecutive, the download of the software into the NE must be done in two
steps:
• first step: the release of the software into the NE and the release of the CT
must be aligned (i.e., if the CT is in current release, it must be downgraded,
thus installing the CT aligned to the NE software resident into the NE); in
these conditions the new SW_package can be downloaded and activated,
using the old CT.
• second step: instal the new CT release and access the NE. If the Data Service
board (ES) was not present in the old release, then download the new SDH
packet associated with the new service packet (e.g.: enhanced OMSN with
ES)
............................................................................................................................................................................................................................................................
5 - 20 P/N 8DG15785AAAA
A Technical support
Overview
Purpose
This chapter provides important technical assistance information for the Alcatel-Lucent
ISA Board ES1 & ES4 (Alcatel-Lucent ISA ES1/4).
Contents
This appendix contains the following sections
“Technical assistance” (p. A-2)

“Accessing and navigating the On-Line Customer Support (OLCS) web site” (p. A-7)
“Other technical support services” (p. A-12)
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA A-1
ISA ES1/4 Release 3.0 Technical support
CT Operator’s Guide Technical assistance
............................................................................................................................................................................................................................................................
Technical assistance
Overview
Alcatel-Lucent provides the following Technical Support Services:
• Remote Technical Support (RTS) - remote technical support to troubleshoot and
resolve system problems.
• On-site Technical Support (OTS) - on-site assistance with operational issues and
remedial maintenance.
• Repair and Replacement (R&R) - technical support services for device repair/return or
parts replacement.
• Alcatel-Lucent On-Line Customer Support (OLCS) - online access to information and
services that can help resolve technical support requests.
Note: Technical Support Services are available 24 hours a day, 7
days a week.
For additional information regarding Alcatel-Lucent Worldwide Services, refer to the
Alcatel-Lucent web site at http://www.alcatel-lucent.com/solutions.
Select the appropriate category:
• Service Providers
• Enterprise
Note: Use the appropriate steps below for the above categories.
Service Providers:
1. Select Service Providers.
2. Select Services.
3. Select Network Support and Maintenance Services located in the Maintenance
section.
Note: An overview of services provided is displayed. If more
detailed information on a particular category is needed, then select
the appropriate information from the top tabs displayed.
Enterprises:
1. Select Enterprises.
2. Under the Evaluate section at the bottom of the page, select Products and Services.
3. At the Products and Services page, select Services.
Important! An overview of the services provided is displayed. For
more information, select one of the three categories shown at the
............................................................................................................................................................................................................................................................
A-2 P/N 8DG15785AAAA
Technical support ISA ES1/4 Release 3.0
Technical assistance CT Operator’s Guide
............................................................................................................................................................................................................................................................
bottom of the page: Consult & Design, Maintain & Operate, or

Integrate & Deploy.
Technical support
Many of our customers have established their own support procedures. These procedures
usually involve escalation within their own companies. However, some instances may
require additional assistance from Alcatel-Lucent.
Alcatel-Lucent has been and continues to be committed to providing excellence in
technical support for its products and services. Therefore, we provide a hierarchical
support structure ready and available to solve any Alcatel-Lucent product technical issue.
When additional assistance is required, the Alcatel-Lucent Welcome Center is the first
point of contact. An Alcatel-Lucent Welcome Center operator can direct the request to
engineers that are highly trained and skilled in resolving issues, involving Alcatel-Lucent
products. Technical assistance is available 24 hours a day, 7 days a week.
Alcatel-Lucent Welcome Center

1 866 582 3688, prompt 1 (continental U.S.)
+1 (630) 224 4672 (outside continental U.S.)
(24 hours a day, 7 days a week)
By using the Alcatel-Lucent Welcome Center as the entry point for Alcatel-Lucent support,
customers will be assured of a timely and effective technical support service.
On-line customer support
Overview
On-Line Customer Support (OLCS) is the Customer Support web site for our customers’
technical support needs. This customer web access tool provides an easy method to access
data about Alcatel-Lucent products using the World Wide Web. A customer must first
request access to this web site to gain access to the following customer support features:
• Ask AL Knowledgebase
• Customer Assistance Request Entry System (CARES)
• Data Drop Box
• Documentation
• Downloads
• Alcatel-Lucent Alerts
• Product Change Notices
• RMA (Repair and Exchange)
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Ask AL Knowledgebase
The Ask AL Knowledgebase web interface feature connects you to the Knowledge
Management solutions database. The Ask AL Knowledgebase feature lets you search for
solutions by using natural language queries. Many products have an extensive set of
Solutions available. Solutions are created by technicians to provide customers with a
method to resolve issues without calling for assistance. Solutions are displayed, showing
the percentage weight or percent match, based on search criteria. Searches can be
performed on all products that are entitled, through the level of service contract a customer
has for RTS services.
CARES
The CARES web interface feature makes it easy for you to submit an Assistance Request
(AR), subscribe to AR Notifications (be notified when an AR is updated), and view all the
customer ARs. The CARES feature lets you open an AR for low severity issues or
questions. Any high severity issue should be called into CTAM. Users can stay informed
about their ARs by using the flexible AR Notification subscriptions. Users can choose a
method for receiving updates: email, text messaging messages, or none. Users can choose
when updates are wanted (when the state of the AR changes, any update to the
investigation field occurs, or any time any text field is modified). Users can log into the
OLCS web site and view ARs 24 hours a day, 7 days a week.
Data Drop Box

The Data Drop Box feature allows Alcatel-Lucent support technicians to provide
customers with a quick method to share files. The Data Drop Box allows a technician to
provide or receive a file from a customer quickly. These files remain in place for 7 days.
Documentation
The Documentation feature on the OLCS web site contains three areas: Manuals and
Guides, Technical Notes, and Release Information.
• Manuals and Guides
This section contains the documents that are available in paper or electronic copy and
are distributed with a new product. These are the documents that are available within
the Alcatel-Lucent Product Documentation web site. The OLCS web site contains
links to the actual documents at the Customer Information Center (CIC) web site. The
following is a list of possible documents that are available from this site:
– Administration Guide
– Applications Planning Guide (APG)/Applications Planning and Ordering Guide
(APOG)
– Getting Started Guide
............................................................................................................................................................................................................................................................
Technical assistance CT Operator’s Guide
............................................................................................................................................................................................................................................................
– Installation Manual (IM)/Installation Guide (IG)

– Modification Implementation Procedure (MIP)
– User Guide
– Alarm Messaging and Trouble Clearing Guide (AMTCG)
– Framework User Guide
– Graphical User Interface (GUI) Guide
– Maintenance Guide, Provisioning Guide
– User Operations Guide (UOG)
• Technical Notes
This section contains documents that are specific to the product and are technical in
nature. Most of these documents will provide information in product data sheets or
white papers, which are technical documents that explain the operation of a particular
part of the system. The following documents are available in this section:
– Change Notice (CN)
– Ethernet Management Guide
– Method of Procedure (MOP)
– Planning Guide
– Service Assurance Guide
– Engineering Change Procedure (ECP)
– Feature Contents
– Operations Interworking (OI) Guide
– Screen Help
– White Papers
These documents will vary from product to product.
• Release Information
This section contains documents that are specific to the release of a product. The
following documents are available in this section:
– Acceptance Documents
– Software Release Descriptions (SRD)
– Specific SRD sections
– White Papers (release specific)
– Software Compatibility
– Upgrade Paths
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Downloads
Note: This may not apply to all products.
The Downloads area allows Alcatel-Lucent support technicians to provide access to
software downloads that are specific to a customers contract. This feature is only allowed
through negotiation with the Account Team and the Product Manager of the product.
Alcatel-Lucent Alerts
The Alcatel-Lucent Alerts tool is a subscription-based tool that provides the same
information that our Product Notifications (PNs) did previously provide. This new method
of communication is a vehicle to share product and support issues that are of
informational, maintenance, or preventive nature. Alcatel-Lucent Alerts contain detailed
text descriptions and urgency of Alcatel-Lucent product issues that need to be quickly
communicated to customers after the deployment of a release or product.
Product Change Notices

The Product Change Notices (PCN) area provides information on hardware changes for a
product. There is a selection of choices to help you search for Change Notices (CNs) or
Customer Change Notices (CCNs).
Return Material Authorization (RMA) (Repair and Exchange)

The RMA area provides a list of contact information on all Alcatel-Lucent products. There
is a “request an RMA number” on-line for most Alcatel-Lucent products. An RMA
number is required for all returned parts and this feature provides you with an easy method
to obtain the RMA number. Please check the warranty status before submitting a request.
............................................................................................................................................................................................................................................................
Accessing and navigating the On-Line Customer Support CT Operator’s Guide
............................................................................................................................................................................................................................................................
Accessing and navigating the On-Line Customer Support

(OLCS) web site
Description
This section provides the method to access the On-Line Customer Support (OLCS) web
site, obtain a login (if necessary), and navigate to each feature listed in this document.
Accessing the OLCS web site

To access the Alcatel-Lucent OLCS web site, enter: www.alcatel-lucent.com/support.
Once you are at this web page, select Lucent Global Support. This will bring you to the
web site where you can log in to gain access to the entitled products.
Obtaining a login for OLCS

To request a login, a customer must register, then and an email confirmation is sent within
2 business days. The following steps tell you how to register for a login:
1. Select “Register Here” on the top right (just below the Login and Password boxes) of
the Online Customer Support (https://support.alcatel-lucent.com/portal/olcsHome.do)
web site.
2. Follow this registration process:
• Select the role and accept the terms of use.
• Provide a business identification, and enter in all of the required information.
• Validate your email address.
• Confirm your business identity and set a password.
• Select content. (This will be verified against the current contract agreements.)
• Register for the selected content.
3. An email confirmation of the registration and the site access privileges is sent within 2
business days.
4. Customize the web view once you have gained access to the OLCS web site.
• After logging in, a personalized view of the Customer Support Home page
displays. This view is based on the user's and company support entitlements.
............................................................................................................................................................................................................................................................
CT Operator’s Guide Accessing and navigating the On-Line Customer Support
............................................................................................................................................................................................................................................................
Need Help while registering?
From the U.S. 1 (866) 582 3688, prompt 7

From outside the U.S. +1 (630) 218 7688
In Asia/Pacific Please contact the in-country technical
support hotline.
Via email Use the email address: olcshelp@alcatel-
lucent.com or use the site's “Contact Us”
form
Use the OLCS help desk number for OLCS access problems, registration
questions, password resets, navigation questions, etc.
View an OLCS website

After you have logged into the OLCS web site, a personalized view of the Customer
Support Home page is displayed. This view is based on the user's and company support
entitlements.
To set Customer Support as the default, if it is the primary destination on the www.alcatel-
lucent.com website, click “Select default home page” on the left column. The “My
Products” section provides you with quick navigation to the entitled products and also
quick access to the CARES tool. While navigating through the various tools, you can
establish bookmarks to certain tools, documents, or web pages (within OLCS) by clicking
“Add to Bookmarks.”
The Customer Support home page can be customized by selecting “Customize page
layout” and adjusting the fields to be displayed (uncheck the boxes to de-select those
elements). These fields can be adjusted at any time. The changes take effect immediately.
There are two methods to find product information. Click “My Products” to choose a
product, or click “Documentation” or “Downloads” to display a complete product listing.
When the full product list is displayed, use the alphabetic listing (default) or the category
list, whichever you prefer. Once a product is selected, a “Product Summary Page” is
displayed, which describes all of the tools and features available for this product.
Note: If content has been posted, but contract entitlements do not
allow access, then the following padlock icon is displayed:
Ask AL Knowledgebase
The Ask AL web page can be accessed from the left column on the Customer Support
homepage (unless you changed the view), from the “Technical Support” section in the
center of the page, or from the “My Bookmarks” section (if it was added there). Once at
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
the Ask AL Knowledgebase web page, enter a question or phrase using natural language,
and click the check boxes for only the products that should be searched; otherwise, all
products checked will be searched.
The results that return show a percentage weight or percent match based on the search
criteria. To refine a search, add more details to the question or phrase and answer the other
questions displayed. Once you find a solution of interest, select that solution, and the
complete solution will display.
Many of the solutions are based on generated ARs or Known Problems from the SRD. To
provide quality information, solutions go through a review process before being posted.
Content can grow daily as solutions move through the review cycle.
CARES
CARES ARs are accessed from the left column on the Customer Support homepage
(unless this view was changed), under the “Technical Support” section in the center of the
page, from the “My Bookmarks” section (if CARES was added there), or from the Quick
Link section “CARES Assistance Requests,” at the bottom of the Customer Support
homepage. Product Notifications and Solutions can also be selected in this section. These
are both legacy tools. The new tools, Alcatel-Lucent Alerts and Ask AL Knowledgebase,
are discussed in other sections of this document.
When you select CARES, a general web page displays. From that page, a particular
function can be selected from the left column. To provide more information on the
selected tool, select “More” from the center column.
ARs can be viewed (using “Find an AR” or “Advanced query”), created (using “Create an
AR”), or used to report a warranty defect (using “Report a warranty defect”). The CARES
web interface has features that keep you informed about the progress of ARs. With the
flexible AR Notification subscriptions, CARES can email or send text messages on a
variety of activities regarding an AR. A notification is sent when the AR state is changed
to Created, Resolved, Closed, or Pending Customer Action. Other conditions that generate
notifications are if the following fields are updated: Investigation, Short Description,
Current Summary, Description, and Resolution. You can set up (subscribe), remove
(unsubscribe), or change these conditions at any time.
Data Drop Box

You can access the Data Drop Box from the left column on the Customer Support
homepage (unless your view was changed), from the “Technical Support” menu in the
center of the page, or from the “My Bookmarks” section (if Data Drop Box has been
added there). Click the “Upload a file” button in the Data Drop Box window to send a file
to the Alcatel-Lucent support technician. An email address can also be entered so that the
............................................................................................................................................................................................................................................................
CT Operator’s Guide Accessing and navigating the On-Line Customer Support
............................................................................................................................................................................................................................................................
Alcatel-Lucent technician will be notified when the file has been sent. Click the
“Download a file” button from the Data Drop Box if the Alcatel-Lucent technician has
sent a file to be downloaded. These files will remain on the site for 7 days.
Documentation
You can access documentation by selecting a product from the “My Products” area.
Alternatively, documentation can also be accessed from the left column on the Customer
Support home page (unless this view has been changed), from the “Technical Support”
section in the center of the page, or from the “My Bookmarks” section (if Documentation
has been added there). If accessing Documentation by means other than the “My
Products” area, choose the product whose documentation you wish to access by selecting
the product from the alphabetical listing or the category list.
Once you are on the product web page, select “Manuals and Guides” from the list under
the “Documentation and downloads” section. The “Manuals and Guides” link brings you
to the Library of Manuals and Guides for the product you have chosen. The document
links bring you to the document stored in the Alcatel-Lucent Customer Information Center
(CIC) web site or to another OLCS webpage that contains the product documentation.
Within the “Documentation and Downloads” area, the “Technical Notes” link brings you
to a web page which contains documents that are not release specific and are technical in
nature.
Also, within the “Documentation and Downloads” area, the Release Information link
brings you to a Library of Release Notes web page that contains documents which are
release specific and are listed by release.
Click on these links to download or open a PDF file.
Downloads
You can access downloads by selecting a product from the “My Products” section.
Downloads can also be accessed from the left column on the Customer Support homepage
(unless this view has been changed), from the “Technical Support” section in the center of
the page, or from the “My Bookmarks” section (if Downloads was added there). If
accessing Downloads by means other than the “My Products” area, choose the product
whose Downloads you wish to access by selecting the product from the alphabetical
listing or the category list.
Once you are on the product web page, click the “Downloads: Electronic Delivery” link
from the list under the “Documentation and Downloads” area. Select the appropriate
release to be downloaded from the drop-down list, and click “Next.” Select the file to be
downloaded and click “Next.” On the next web page, enter the path where the file should
be downloaded and click “Download.”
............................................................................................................................................................................................................................................................
A - 10 P/N 8DG15785AAAA
............................................................................................................................................................................................................................................................
Alcatel-Lucent Alerts
You can access Alcatel-Lucent Alerts from the left column on the Customer Support
homepage (unless this view has been changed), from the “Technical Support” section in
the center of the page, or from the “My Bookmarks” section (if Alcatel-Lucent Alerts is
added there).
Once you are on the Alcatel-Lucent Alerts web page, a list of products are displayed.
Click on a product to see a list of Alerts for that product. Alternatively, use the “Enter the
number of the Alert” field to find a specific Alert, or use the text search to search for
Alerts with certain words.
To subscribe to Alcatel-Lucent Alerts, click the “Alerts Subscription Page” link. Once at
the “Alcatel-Lucent Alerts Subscription” page, fill out the form and choose the product
whose alerts you would like to subscribe to.
You have the option to click “Modify Subscription” or “Cancel Subscription.” Modify
Subscription allows you to modify the Urgency, Type, and/or Products selected. “Cancel
Subscription” will stop future Alcatel-Lucent Alerts email messages.
Product Change Notices (PCNs)

You can access Product Change Notices (PCNs) from the left column on the Customer
Support home page (unless this view has been changed), from the “Technical Support”
section in the center of the page, or from the “My Bookmarks” section (if PCNs were
added there).
Once on the PCN web page, a list of PCNs is displayed. You can search PCNs by clicking
one of the following links:
• PCN cross-reference
• Search for specific text in Class A PCNs
• PCNs added or updated within the past 30 day
• Change Notice summary report
Return Material Authorization (RMA) (Repair and Exchange)

Return Material Authorization (RMA) can be accessed from the left column on the
Customer Support home page (unless this view has been changed), from the “Technical
Support” section in the center of the page, or from the “My Bookmarks” section (if it was
added there).
Once on the RMA web page, a table with contact information is displayed. Use the contact
information provided or choose to fill in the online RMA request form at the bottom of
that web page.
............................................................................................................................................................................................................................................................
CT Operator’s Guide Other technical support services
............................................................................................................................................................................................................................................................
Other technical support services

The technical support services expert workshop series
Audience: Technicians, installers, maintenance engineers, technical support personnel,
product evaluators, and anyone who has a working knowledge of the products involved
and is interested in a hands-on workshop covering advanced troubleshooting issues.
Description: The same engineers that resolve the Assistance Requests (ARs) have
developed a series of advanced, hands-on workshops that can be customized to the unique
network applications. Individual product modules will provide the knowledge and skills to
perform troubleshooting and fault-finding activities at the equipment site or from a remote
operations center. There are lab exercises using Alcatel-Lucent network management
systems to simulate real-world provisioning and troubleshooting scenarios. In addition,
general technology modules will round out the understanding of the network element (NE)
troubleshooting performed.
Objectives: Each module has specific objectives. Some overall series objectives are listed
below:
• Understand advanced network element security features
• Setup and understand interworking between Alcatel-Lucent network elements
• Perform provisioning operations and remote trouble-shooting using CIT, EMS and
TL1 interfaces.
• Analyze Performance Monitoring Data
• Understand alarm handling / alarm management
• Provision and understand system synchronization techniques
• Provision and understand protection schemes (BLSR, UPSR, 1+1 APS)
• Understand network communication issues (OSI and TCP/IP interfacing)
Length: Product Modules are scheduled for 3 days. Technology Modules are scheduled
for 1 day.
Expected Foundation Knowledge: Suggested prerequisites are listed on each module's
workshop description. Generally, customers should have a basic understanding of digital
fundamentals and lightwave transmission systems. In addition, customers should have
taken a previous Alcatel-Lucent Operating & Maintenance course or have equivalent
experience with operations and maintenance issues related to the product
Activities Prior to Workshop Delivery: The effectiveness of this workshop series relies
on the fact that it allows a customer to address the issues experienced in their network
today. To achieve this, prior to the workshop, a conference call will be set up with the
engineers that will facilitate the workshop. During this call, the logistics of simulating the
customer's network environment will be discussed.
............................................................................................................................................................................................................................................................
A - 12 P/N 8DG15785AAAA
Other technical support services CT Operator’s Guide
............................................................................................................................................................................................................................................................
Workshop Location: This workshop will be delivered in the Customer Advocate System
Test Labs in Westford, MA. The format is 75% hands-on lab exercises, reinforced with
25% classroom instruction.
How to Sign Up:

To enroll in the training course:
• Within the United States,
– Visit https://training.alcatel-lucent.com
– Call 1 (888) 582 3688: Prompt 2.
• Outside the continental United States,
– Visit https://training.alcatel-lucent.com
– Contact your in-country training representative
– Call: +1 (407) 767 2798
– Fax: +1 (407)767 2677
• Enter “Advanced Workshops” in the search menu and click “Go.”
• Choose which Advanced Maintenance Workshop you’d like to register for by clicking
on the link.
• Read the workshop description(s) and follow the links to register.
............................................................................................................................................................................................................................................................
CT Operator’s Guide Other technical support services
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
A - 14 P/N 8DG15785AAAA
Glossary
Acronyms and Abbreviations

............................................................................................................................................................................................................................................................
ACD
Access Control Domain
ACL
Access Control List
ADM
Add and Drop Multiplexer
AIS
Alarm Indication Signal
ARP
Address Resolution Protocol
AS
Alarm Surveillance
ASAP
Alarm Severity Assignment Profile
ATM
Asynchronous Transfer Mode
AUI
Attachment Unit Interface
............................................................................................................................................................................................................................................................
BE
Best Effort
BGP
Border Gateway Protocol
BM
Bandwidth Manager
BPDU
Bridge Protocol Data Unit
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA GL-1
ISA ES1/4 Release 3.0 Glossary
CT Operator’s Guide Acronyms and Abbreviations
............................................................................................................................................................................................................................................................
BW
BandWidth
............................................................................................................................................................................................................................................................
C-VLAN
Customer V-LAN
CAC
Call Admission Control
CBS
Committed Burst Size
CC
Continuity Check
CD
Current Data
CD-ROM
Compact Disc Read Only Memory
CE
Customer Edge (device)
C&I
Classification and Identification
CFI
Canonical Field Identifier
CIR
Committed Information Rate
CIST
Common and Internal Spanning Tree
CLNP
ConnectionLess Network layer Protocol
CNLS
Connectionless Network Layer Service
CoS
Class of Service
CPE
Customer Premise Equipment
CR-LDP
Constraint based Routing Label Distribution Protocol
............................................................................................................................................................................................................................................................
GL-2 P/N 8DG15785AAAA
Glossary ISA ES1/4 Release 3.0
Acronyms and Abbreviations CT Operator’s Guide
............................................................................................................................................................................................................................................................
CRC
Cyclic Redundancy Check
CSF
Client Signal Failure
CT
Craft Terminal
............................................................................................................................................................................................................................................................
DA
Destination Address
DACM
Dual Attach Connectivity Message
DAPDU
Dual Attach Protocol data Unit
DB
Data Base
DCC
Data Communications Channel
DCE
Data Communications Equipment
DEI
Drop Eligible Indicator
DEMUX
Demultiplexer
DF
Default Forwarding
DLC
Digital Loop Carrier
DLP
Detailed Level Procedure
DP
Dropping Precedence
DPLL
Digital Phase-Locked Loop
DRI
Dual Ring Interworking
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
DS
Differentiated Service
DSCP
Differentiated Services Code Point
DSNE
Directory Services Network Element
DSX
Digital Cross-Connect Panel
DTE
Data Terminating Equipment
............................................................................................................................................................................................................................................................
EBS
Excess Burst Size
EC
Equipment Controller
EC-1
Electrical Carrier Level 1
ECI
Equipment Catalog Item
EEPROM
Electrically-Erasable Programmable Read-Only Memory
EIA
Electronic Industries Association
EF
Expedited Forwarding
EFC
Ethernet Flow Control
EFD
End Frame Delimiter
EFM
Ethernet First Mile
ELB
Event Log Browser
EMC
Electromagnetic Compatibility
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
EMI
Electromagnetic Interference
EOOF
Excessive Out of Frame
EPROM
Erasable Programmable Read-Only Memory
EQ
Equipped (memory administrative state)
ERO
Explicit Route Object
ES
Errored Seconds
ESn
Enhanced Service n-order
ESD
Electrostatic Discharge
ESF
Extended Super Frame
ETB
Ethernet Bridge
ETC
Ethernet Transport Classifier
ETS
Ethernet Transparent Service (or Ethernet Transport Service)
............................................................................................................................................................................................................................................................
FCC
Federal Communications Commission
FCS
Frame Check Sequence
FD
Full Duplex
FDDI
Fiber Distribution Data Interface
FDL
Facility Data Link
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
FE
Far End or Fast Ethernet
FEBE
Far End Block Error
FERF
Far End Receive Failure
FE SEL
Far End Select
FID
Filtering Database Identifier
............................................................................................................................................................................................................................................................
GE
Gigabit Ethernet
GDA
Group Destination Address
GFP
Generic Frame Procedure
GMII
Gigabit Media Independent Interface
GNE
Gateway Network Element
GRE
Generic Routing Encapsulation
GTP
General Telemetry Processor
GTSIP
Global Technical Support Information Platform
GUI
Graphical User Interface
............................................................................................................................................................................................................................................................
HD
History Data or Half Duplex
HEC
Header Error Control
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
ICI
Inter-Carrier Interface
ID
Identifier
IEC
International Electrotechnology Commission
IETF
Internet Engineering Task Force
IF-IB
In Fiber - In Band
IF-OOB
In Fiber - Out Of-Band
IGMP
Internet Group Multicast Protocol
IP
Internet Protocol
IPIP
IP in IP encapsulation
IPv6
Internet Protocol version 6
IS
In Service
ISDN
Integrated Services Digital Network
ISO
International Standards Organization
ISP
Internet Service Provider
IVHS
Intelligent Vehicle Highway System
IVL
Independent VLAN Learning
IWI
Inter-Working Interface
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
JRE
Java Running Environment
............................................................................................................................................................................................................................................................
LACP
Link Aggregation Control Protocol
LACPDU
Link Aggregation Control Protocol Data Unit
LAG
Link Aggregation Group
LAN
Local Area Network
LAPD
Link Access Procedure "D"
LB
Loopbackt
LCAS
Link Capacity Adjustment Scheme
LCN
Local Communications Network
LEC
Local Exchange Carrier
LED
Light-Emitting Diode
LER
Label Edge Router
LLC
Logical Link Control
LLCF
Link Loss Carry Forward
LOF
Loss of Frame
LOP
Loss of Pointer
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
LOS
Loss of Signal
LS
Low Speed
LSR
Label Switching Router
LT
Link Trace
............................................................................................................................................................................................................................................................
MA
Maintenance Association
MAC
Medium Access Control
MAU
Medium Access Unit or Management Attachment Unit
MD
Maintenance Domain or Mediation Device
ME
Maintenance Entity
MII
Media Independent Interface
MJ
Major Alarm
MN
Minor Alarm
MPLS
Multi-Protocol Label Switching
MRU
Maximum Receive Unit
MSDT
Multi-Services Distant Terminal
MSSPRING
Multiplex Section Switching Protection Ring
MSTI
Multiple Spanning Tree Instance
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
MSTP
Multiple Spanning Tree Protocol
MTU
Maximum Transmission Unit
MUX
Multiplex
............................................................................................................................................................................................................................................................
NE
Near End
NE
Network Element
NNI
Network to Network Interface
NARTAC
Lucent North American Regional Technical Assistance Center
call 1-866-LUCENT8 (866-582-3688): Prompt 1
NSA
Not Service Affecting
NSAP
Network Services Access Point
NTP
Network Time Protocol
............................................................................................................................................................................................................................................................
OAM
Operations, Administration, and Maintenance
OAM&P
Operations, Administration, Maintenance, and Provisioning
OAMPDU
OAM Protocol Data Unit
ODN
Object Deletion Notification
OLCS
OnLine Customer Support
OMSN
Optical Metro Service Node
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
OOF
Out of Frame
OS
Operations System
OSGNE
Operations System Gateway Network Element
OSI
Open Systems Interconnection
OSPF
Open Shortest Path First
OTN
Optical Transport Node
............................................................................................................................................................................................................................................................
P-VLAN
Provider (proprietary) VLAN
PBS
Peak Burst Size
PC
Personal Computer
PCP
Priority Code Point
PCS
Physical Coding Sub-layer
PDU
Protocol Data Unit
PE
Provider Edge
PFI
Payload FCS Identifier
PHB
Per-Hop Behavior
PHP
Penultimate Hop Popping
PID
Password Identifier
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
PIR
Peak Information Rate
PLI
PDU Length Indicator
PLS
Physical Layer Signaling
PM
Performance Monitoring
PMA
Physical Medium Attachment
PMD
Physical Medium Dependent
PR
Packet Ring
PSC
PHB Scheduling Class
PSN
Packet Switched Network
PTI
Payload Type Identifier
............................................................................................................................................................................................................................................................
QoS
Quality of Service
............................................................................................................................................................................................................................................................
RAM
Random Access Memory
RARP
Reverse Address Resolution Protocol
RDI
Remote Defect Indication
RPL
Ring Protection Link
RST
Rapid Spanning Tree
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
RSTP
Rapid Spanning Tree Protocol
RSVP-TE
Resource ReserVation Protocol – Traffic Engineering
RS232
Serial interface
............................................................................................................................................................................................................................................................
SA
Service Affecting
SD
Signal Degrade
SDH
Synchronous Digital Hierarchy
SEFS
Severely Errored Frame Seconds
SES
Severely Errored Seconds
SFD
Start Frame Delimiter
SFP
Small Form factor Pluggable
SID
Site Identifier
SID
System Identification
SL
Signal Label
SLA
Service Level Agreements
SONET
Synchronous Optical NETwork
SP
Service Provider
SSF
Server Signal Fail
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
STP
Spanning Tree Protocol
............................................................................................................................................................................................................................................................
T-MPLS
Transport - Multi-Protocol Label Switching
TABS
Telemetry Asynchronous Byte Serial (Protocol)
TARP
Target ID Address Resolution Protocol
TCP/IP
Transmission Control Protocol/Internet Protocol
TD
Traffic Descriptor or Traffic Disable
TDF
Total Discard Frame
TDM
Time Division Multiplexing
TID
Target Identifier
TNA
Transport Network Identifier
TOS
Type of Service
TPID
Tag Protocol ID
TR
Telcordia Technologies Technical Requirement
TRSEF
Total Received Service Errored Frames
TSA
Time Slot Assignment
TSF
Trail Signal Fail
TSO
Technical Support Organization
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
UAS
Unavailable Seconds
UID
User Identifier
UNI
User Network Interface
UOC
Universal Optical Connector
UPI
User Payload Identifier
URU
Underline Resource Unavailable
USB
Universal Serial Bus
............................................................................................................................................................................................................................................................
VC
Virtual Container
VCG
Virtual Concatenation Group
VLAN
Virtual Local Area Network
VLANID
Virtual Local Area Network Identifier
VoIP
Voice over Internet Protocol
VPL
Virtual Path Link
VPN
Virtual Private Network
VRRP
Virtual Router Redundancy Protocol
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
WDRR
Weighted Deficit Round Robin
WFQ
Weighted Fair Queue
WRED
Weighted Random Early Discard
............................................................................................................................................................................................................................................................
Terms and Definitions CT Operator’s Guide
............................................................................................................................................................................................................................................................
Terms and Definitions

............................................................................................................................................................................................................................................................
AIS - Alarm Indication Signal

A code transmitted downstream in a digital network that shows that an upstream failure has been
detected and alarmed.
Aggregate
A set of flows passing through the same Virtual Ethernet Interface.
ASCII - American Standard Code for Information Interchange
A standard 8-bit code used for exchanging information among data processing systems and
associated equipment.
Available Time
In performance monitoring, the 1-second intervals.
............................................................................................................................................................................................................................................................
BER - Bit Error Ratio

The ratio of bits received in error to the total bits sent.
BRIDGE MANAGEMENT
Refer to “ISA-ES1/4 System” (p. 1-3) for details.
............................................................................................................................................................................................................................................................
CV - Coding Violation
A performance monitoring parameter.
CVFE - Coding Violation Far-End
An indication returned to the transmitting terminal that an errored block has been detected at the
receiving terminal.
............................................................................................................................................................................................................................................................
DCE - Data Communications Equipment

In a data station, the equipment that provides the signal conversion and coding between the data
terminal equipment (DTE) and the line. The DCE may be separate equipment or an integral part of
the DTE or of intermediate equipment. A DCE may perform other functions usually performed at
the network end of the line.
............................................................................................................................................................................................................................................................
CT Operator’s Guide Terms and Definitions
............................................................................................................................................................................................................................................................
Demultiplexing
A process applied to a multiplexed signal for recovering signals combined within it and for restoring
the distinct individual channels of these signals.
Digital Multiplexer
Equipment that combines time-division multiplexing several digital signals into a single composite
digital signal.
DRI - Dual Ring Interworking
Two ring networks interconnected at two common nodes.
DTE - Data Terminating Equipment
That part of a data station that serves as a data source (originates data for transmission), a data sink
(accepts transmitted data), or both.
............................................................................................................................................................................................................................................................
ES - Errored Seconds
A performance monitoring parameter.
ETS - Ethernet Transparent Service
A provider service that emulates the functionality of a traditional Local Area Network.
Ethernet Flow
4-uple <MAC Source Address, MAC Destination Address, 802.1p Priority bits, VLAN tag >
representing an Ethernet connection between remote MAC address. Ethernet traffic is tagged with
802.1p VLAN and is classified with 8 Ethernet priority values.
Ethernet Ring
A collection of nodes (Ethernet Ring Nodes) forming a closed loop whereby each node is connected
(via 2 independent links) to two adjacent nodes in a duplex mode. In multi-ring topology this is
known as Major-Ring
Ethernet Ring Link
it is bounded by two adjacent nodes and a port for a ring link is called a ring port
Ethernet Ring Node
A NE with 2 ring ports, implementing the following basic functions:
• forwarding of R-APS control traffic at the Ring Maintenance Entity group Level (MEL);
• blocking and unblocking of traffic over the ring ports.
............................................................................................................................................................................................................................................................
FE - Far End
Any other network element in a maintenance subnetwork other than the one the user is at or working
on. Also called remote.
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
FEBE - Far End Block Error

An indication returned to the near-end transmitting node that an errored block has been detected at
the far end.
FEC - Forwarding Equivalence Class
A group of IP packets, which are forwarded in the same manner (e.g. over the same path, with the
same forwarding treatment).
FERF - Far End Receive Failure
An indication returned to the transmitting terminal that the receiving terminal has detected an
incoming section failure.
Flow
Set of Ethernet flows transmitted between two remote customer's sites with the same QoS.
............................................................................................................................................................................................................................................................
GNE - Gateway Network Element

A network element that has an active X.25 link.
............................................................................................................................................................................................................................................................
ID
See shelf ID and site ID.
InSegment
It represents an incoming segment in a LSR.
............................................................................................................................................................................................................................................................
Jabber
A condition wherein a station transmits for a period of time longer than the maximum permissible
packet length, usually due to a fault condition.
Jabber Function
A mechanism for controlling abnormally long transmission.
............................................................................................................................................................................................................................................................
Label
A short fixed length physically contiguous identifier, which is used to identify a FEC, usually of
local significance.
Label Stack
An ordered set of labels.
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
LED - Light Emitting Diode

Used on a circuit pack faceplate to show failure (red) or service state. It is also used to show the
alarm and status condition of the system.
LER - Label Edge Router
An MPLS node that connects an MPLS domain with a node, which is outside of the domain, either
because it does not run MPLS, and/or because it is in a different domain.
Link
The transmission path between any two interfaces of generic cabling (from ISO/IEC 11801)
Local
See Near-End.
LOF - Loss of Frame
A failure to synchronize to an incoming signal.
LOP - Loss of Pointer
A failure to extract good data from an STS-1 payload.
LOS - Loss of Signal
The complete absence of an incoming signal.
LSP - Label Switched Path
The path through one or more LSRs at one level of the hierarchy followed by a packet, in a
particular FEC.
LSR -Label Switching Router
An MPLS node, which is capable of forwarding native L3 packets.
............................................................................................................................................................................................................................................................
MPLS Node
A node wich is running MPLS. An MPLS node will be aware of MPLS control protocols, will
operate one or more L3 routing protocols, and will be capable of forwarding packets on labels. An
MPLS node may optionally be also capable of forwarding native L3 packets.
Multiplexing
The process of combining several distinct digital signals into a single composite digital signal.
............................................................................................................................................................................................................................................................
NE - Near End
The network element the user is at or working on. Also called local.
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
NE - Network Element
The basic building block of a telecommunications equipment within a telecommunication network
that meets SONET/SDH standards. Typical internal attributes of a network element include: onr or
more high- and low-speed transmission ports, built-in intelligence, synchronization and timing
capability, and access interfaces for use by technicians and/or operation systems. In addition, a
network element may also include a time slot interchanger.
NHLFE - Next Hop Label Forwarding Entry
It is used when forwarding a labeled packet. It contains the following information:
The packet's next hop
The operation to perform on the packet's label stack; this is one of the following operations:
Replace the label at the top of the label stack with a specified new label.
Pop the label stack.
Replace the label at the top of the label stack with a specified new label, and then
push one or more specified new labels onto the label stack.
It may also contain:
The data link encapsulation to use when transmitting the packet.

The way to encode the label stack when transmitting the packet.
Any other information needed in order to properly dispose of the packet.
Node
In SONET/SDH, a node is a line terminating element.
NSAP - Network Services Access Point
An address that identifies a network element. Used for maintenance subnetwork communication
using the OSI protocol.
............................................................................................................................................................................................................................................................
OS - Operations System
A central computer-based system used to provide operations, administration, and maintenance
functions.
OSI - Open Systems Interconnection
Referring to the OSI reference model, a logical structure for network operations standardized by the
Internation Standards Organization (ISO).
OutSegment
It represents an outgoing segment from a LSR.
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Plesiochronous Network
A network that contains multiple maintenance subnetworks, each internally synchronous and all
operating at the same nominal frequency, but whose timing may be slightly different at any
particular instant. For example, in SONET/SDH networks, each timing traceable to their own
Stratum 1 clock are considered plesiochronous with respect to each other.
PM - Performance Monitoring
Measures the quality of service and identifies degrading or marginally operating systems (before an
alarm would be generated).
Port
The physical, electrical, or optical interface on a system.
Promiscuous Mode
If active the MAC forwards to upper layers all the received packets. It can be active only on certain
type of media.
............................................................................................................................................................................................................................................................
Remote
See Far-End (FE).
Ring
A configuration of nodes comprised of network elements connected in a circular fashion. Under
normal conditions, each node is interconnected with its neighbor and includes capacity for
transmission in either direction between adjacent nodes. Path switched rings use a head-end bridge
and tail-end switch. Line switched rings actively reroute traffic over a protection line.
Ring MEL
It is the Maintenance Entity Group (MEG) level providing a communication channel for ring
automatic protection switching (R-APS) information
Ring Protection Link (RPL)
It is the ring link which under normal conditions, i.e. without any failure or request, is blocked (at
one end or both ends) for traffic channel, to prevent the formation of loops
RPL Node
It is an Ethernet Ring Node with the same behaviour of the previous one, except that it is not
responsible for the reverting activation
RPL Owner Node
It is an Ethernet Ring Node adjacent to the RPL that is responsible for blocking its end of the RPL
under normal conditions. Furthermore, it is responsible for activating reversion behaviour from
protected or MS/FS conditions
RT - Remote Terminal
An unstaffed equipment enclosure that may have a controlled or uncontrolled environment.
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
SES - Severely Errored Seconds

This performance monitoring parameter is a second in which a signal fail occurs, or more than a
preset amount of coding violations (dependent on the type of signal) occurs.
Status
The indication of a short-term change in the system.
Subnetwork
Group of SONET/SDH network elements that share a SONET/SDH data communications channel.
............................................................................................................................................................................................................................................................
UAS - Unavailable Seconds

In performance monitoring, the count of seconds in which a signal is declared failed or, in which,
10 consecutively severely errored seconds (SES) occurred, until the time when 10 consecutive non-
SES occur.
Unidirectional
A protection switching mode in which the system at each end of an optical span monitors both
service and protection lines and independently chooses the best signal (unless overridden by an
equipment failure or by an external request, such as a forced switch or lockout). In a system that
uses unidirectional line switching, both the service and protection lines may be active
simultaneously, with one line carrying traffic in one direction and other line carrying traffic in the
other direction. For a 1+1 protection scheme the K1 and K2 bytes in the SONET/SDH line overhead
are used to convey to the far end which line the near-end receiver has chosen, so that an "active"
indication may be made at the far end.
............................................................................................................................................................................................................................................................
XC
It represents a cross-connection, which is used to associate in and out segments toghether, in order
to form a cross-connection.
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Index
.............................................................................
CBS, 4-51 EML-USM, 4-46
1320CT, 3-4, 3-6 CIR, 4-51 ERP, 1-79
802_1X, 1-40 Class of Services, 1-27 ERP Management, 4-16
............................................................................. CLASSIFIER, 4-9 ES Node, 4-9
A Acceptable Frames, 1-11 Color-Aware, 4-55 ES-Craft Terminal, 3-1
ACL, 1-4, 4-18, 4-94 Color-Blind, 4-55 ES-CT, 1-88, 3-6, 3-8
ACL/ACE management, 4-96 Configure ISA, 4-62 ETB mode, 1-23
ACL/ACL setting, 4-95 Connectivity Fault Management, ETB Port, 4-9

1-86 ETB port, 1-12
Aggregation Port, 4-202
Continuity Check, 4-217 ETH on GFP, 4-92
Aggregator, 4-193
Control Panel, 3-5 ETH on LAPS, 4-92
Alarms Severities, 4-33
conventions used, xxvi Eth2ETS Classifier, 4-107
Alarms Surveillance, 4-41, 5-4
CSF alarm, 1-54 Ethernet OAM, 1-86
Alarms synthesis, 5-6
CT-K, 3-11, 3-24 ETHERNET port, 4-9
Alcatel-Lower-Layer, 3-11
Customer BPDU, 1-38, 1-39 Ethernet technique, 1-18
ASAP, 4-33
Customer Bridge, 1-38 ETS InFlow, 4-100
Asymmetric FC, 1-59
Customer Edge, 1-77 ETS mode, 1-21
Auto-Learning, 1-8
Customer GARP, 1-42 ETS OutFlow, 4-103
Auto-Negotiation, 1-58
Customer GMRP, 1-41 ETS ports, 1-13
.............................................................................
Customer-BPDU, 1-74 ETS Traffic Descriptor, 4-14
B Back Ground Service, 4-53
............................................................................. Ets XC One Step (MAC &
Bandwidth matching, 4-87 Virtual), 4-242, 4-256
D document
Best Effort Service, 4-52 conventions used, xxvi Ets XC One Step (Provider),
BPDU, 1-46 4-246
how to use, xxv
Bridge management, 1-40 Event Log Browser, 4-43
intended audience, xxv
Bridge Port (MAC), 4-133 download, 3-36 .............................................................................
Bridge Port (Provider), 4-125
Dual Homing, 1-75 F Flow Control, 1-59
Bridge Port (Virtual), 4-130
Dual-homing, 1-77 Frame Check Sequence, 1-31
Bridge Port Properties, 4-148 Frame Start, 1-31
.............................................................................
Bridge Type, 4-62
FullWindow, 4-28
E EFM Management, 4-210
.............................................................................
Electrostatic Discharge (ESD), .............................................................................
C C-BPDU, 1-75 xxvii G GARP, 1-38
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA IN-1
ISA ES1/4 Release 3.0 Index
............................................................................................................................................................................................................................................................
Gateway NE, 1-90 local Ethernet Port, 4-67 Point-to-Point, 1-19

GFP, 1-21 Local Ethernet Ports, 4-65 Port Mirroring, 1-4, 1-62
GMII, 1-7, 4-60, 4-80 Local interfaces, 4-49, 4-50 Port Vlan Identifier, 4-137
GMRP, 1-38 loop avoidance, 1-80 Port-to-Port, 4-40
Gold Service, 4-57 LoopBack, 4-217 Preamble, 1-31, 1-32, 1-33
Granularity, 4-263 ........................................................................... product disposal, xxix
Guaranteed Service, 4-52 product take-back, xxix
M Maintenance Entity, 1-87
GVRP, 1-38 Protocol Profile, 4-76, 4-82
Maintenance Entity Group, 1-87
............................................................................. Provider BPDU, 1-38
MAU, 4-70
Provider Bridge, 1-3, 1-15, 1-38
I ICP, 5-13 MEG End Point, 1-87
Provider GVRP, 1-41
IGMP, 1-4, 4-155 MEG Intermediate Point, 1-87
Provider InFlow, 4-112
IGMP Snooping, 1-67 Metro Ethernet Forum, 1-19
Provider OutFlow, 4-115
IGMP snooping statistics, 4-273 MIB, 4-47
In Fiber In Band management, MII, 1-7, 4-60, 4-80 ...........................................................................
4-206 MPLS, 1-90 Q Queue, 4-150

IN-FLOW, 4-9 MSTP, 1-48, 1-74 queueing, 4-56
Ingress Filtering, 1-11 MTU, 1-31, 4-64 ...........................................................................
intended audience, xxv MultiPoint-to-MultiPoint, 1-19
R Rapid Spanning Tree Protocol,
Inter Packets Gap, 1-31
........................................................................... 1-46
Internet Group Multicast
N NE-ES package, 3-28 Realign ISA board population,
Protocol, 1-66
3-41
ISA Alarms, 5-14 Network Element Synthesis,
3-28 recycle, xxix
ISA Navigate, 3-43
reference model, 1-90
ISA-ES board front cover, 5-3 ...........................................................................
Regulated Service, 4-52
ISA-ES1, 4-67, 4-80 O OAM, 1-4
remote Ethernet Port, 4-80
ISA-ES1 board, 4-49 OAM application, 4-217
Remote Ethernet Ports, 4-65
ISA-ES4, 4-67, 4-80 Object Alarms, 5-14
Remote interfaces, 4-49, 4-50
ISA-ES4 board, 4-50 on ES-CT, 4-4
Resource Management, 1-64
............................................................................. on SDH-CT, 4-4
Resources Availability, 4-122
OUT-FLOW, 4-9
J JRE, 3-11 RSTP, 1-74
.............................................................................
........................................................................... RUM, 5-13
P PBS, 4-51 RUTM, 5-13
L L2 Control Frame, 4-74
Per VLAN basis, 1-79 ...........................................................................
LAG, 1-68, 4-9
Performance application, 4-263
LAPS, 1-21 S SDH-NE software package, 3-6
per-port bridging, 1-79
LCAS, 1-52 Selective Tunnelling, 1-74
PIR, 4-51
Link Aggregation, 1-4, 1-68 Server Layer, 4-92
PM Data Results, 4-289
LinkTrace, 4-217 shaping, 4-56
............................................................................................................................................................................................................................................................
IN-2 P/N 8DG15785AAAA
Index ISA ES1/4 Release 3.0
............................................................................................................................................................................................................................................................
Silver Service, 4-57

Slow Protocols, 1-38, 1-39
SNMP, 1-90
SNMPCT, 3-20
SNMPCT-K-ADD-ON, 3-11,
3-20
software license, 2-3
software package, 3-36
software product, 2-3
software products, 2-2
Spanning Tree Protocol, 1-43
Stacked-Vlan frame, 4-54
STP, 1-74
S-VLAN, 1-7
Symmetric FC, 1-59
.............................................................................
T TabbedWindow, 4-28
Tag Control Information, 1-32,
1-33
TCIP, 1-33
Traffic Descriptor (TD), 4-51
Traffic Management, 4-93
Transmission Alarms, 5-14
trouble-shooting, 5-2
.............................................................................
U User Priority, 1-32

User Priority List, 4-136
.............................................................................
V VC-AIS alarm, 1-55

Virtual Bridge, 1-3
Virtual Concatenation, 1-52
VLAN, 1-7
VLAN Registration, 4-118
.............................................................................
W WDRR Bandwidth, 4-56
............................................................................................................................................................................................................................................................
P/N 8DG15785AAAA IN-3
ISA ES1/4 Release 3.0 Index
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
IN-4 P/N 8DG15785AAAA

ISA-ES1 - 4ENH 3.0 OPER - HDBK - Ed01 PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

ISA-ES1 - 4ENH 3.0 OPER - HDBK - Ed01 PDF

Caricato da

Copyright:

Formati disponibili

Alcatel-Lucent ISA Board

ETHERNET SWITCHING SYSTEM (ES1 & ES4) | RELEASE 3.0

Copyright © 2011 Alcatel-Lucent. All Rights Reserved.

Interference Information: Part 15 of FCC Rules

About this document

System alarm management ..................................................................................................................... 1-54

Software Uninstallation procedure .......................................................................................................... 3-33

4 Craft Terminal for ES1-ES4 Management

MIB Management ................................................................................................................................... 4-47

VLAN Registration ......................................................................................................................... 4-118

Configure LoopBack ...................................................................................................................... 4-232

2 Software Product and Licence

3-2 Initial presentation intermediate screen ...................................................................................... 3-9

3-35 Download Initiate (example) ..................................................................................................... 3-36

4-22 Log Retrieval -> Alarm (Report example) ................................................................................. 4-45

4-55 Substitute Server Layer (from GFP to LAPS) ........................................................................... 4-92

4-88 Bridge Port: CIST: MST Region Management ........................................................................ 4-145

4-121 Modify ERP Instance - Configuration tab .............................................................................. 4-180

4-154 EFM Properties ....................................................................................................................... 4-216

4-187 Topology for “Create Ets XC OneStep" (Provider) ................................................................. 4-247

4-220 IGMP <VLAN, Multicast> creation (Node resource) ............................................................. 4-284

About this document

4 Craft Terminal for ES1-ES4 Management

Reason for reissue

Issue Date Reason

How to use this document

Table 1 Alcatel-Lucent ISA ES1/4 Documentation Set

Document Number Document Title

Packaging collection and recovery requirements

Note: In the European Union, a solid bar under the crossed-out

• “System alarm management” (p. 1-54)

Table 1-1 Ethernet layer stack over SDH

3 NETWORK any network “packetized" data service

Unit Acronym (code) Local ports Remote ports

Local ports Remote ports Local ports Remote ports

Local ports Remote ports

Local ports Remote ports Local ports Remote ports

Unit Acronym (code) Local ports Remote ports

Local ports Remote ports Local ports Remote ports

Local ports Remote ports Local ports Remote ports

Table 1-2 Allowed board

MAC Addresses “on 8

Figure 1-1 ISA-ES subsystem, protocol stacking

3 any 3 any 3 any

S-VLAN S-VLAN MAC

VLAN and/or S-VLAN

Ethernet GFP Ethernet

Local: SONET/SDH equivalent capacity: Remote:

CIA = Classification, Identification, Aggregation.

Figure 1-2 Bridge representation example and relevant FDB table

Bridge operations examples:

Figure 1-3 System into SDH network, example

Remote Ports OMSN

Local SDH SONET NETWORK

Figure 1-5 Frames acceptance criteria

Figure 1-6 MAC Bridge distribution domain (example)

LAN or LAN or LAN or LAN or

ETB ETB ETB ETB

The frames are distributed to all the active ETB ports

Figure 1-7 Virtual Bridge distribution domain (example)

LAN or LAN or LAN or LAN or

ETB ETB ETB ETB

Figure 1-8 Provider Bridge distribution domain (example)