Isa-es16 2.5 Oper.hdbk_ed05 operation manual...
Alcatel-Lucent ISA Board ETHERNET SWITCHING SYSTEM (ES16) | RELEASE 2.5 CT OPERATOR’S GUIDE
P/N 8DG15624AAAA ISSUE 05 FEBRUARY 2010
This material is protected by the copyright laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Alcatel-Lucent), except in accordance with applicable agreements, contracts, or licensing, without the express written consent of Alcatel-Lucent and the business management owner of the manual. THIS PRODUCT COMPLIES WITH D.H.H.S. RADIATION PERFORMANCE STANDARDS 21 CFR, 1040.10, FOR A CLASS 1 LASER PRODUCT. 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. This manual applies to software. Release notes describing revisions to this software may impact operations described in this manual. This transfer of commodities, technology, or software, if from the United States, is an export in accordance with the U.S. Export Administration Regulations. Diversion contrary to U.S. law is prohibited. The export or re-export (further transfer) of such commodities, technology, software or products made from such technology is prohibited without proper authorization(s) from the U.S. Department of Commerce or other appropriate U.S. government agency(s). All rights reserved. No part of this manual may be reproduced, translated, stored in a retrieval system, or transmitted or distributed by any means, electronic or mechanical, by photocopying, recording, or otherwise, without the written permission of Alcatel-Lucent. Preparing derivative works or providing instruction based on the material is prohibited unless agreed to in writing by Alcatel-Lucent. The product specification and/or performance levels contained in this document are for information purposes only and are subject to change without notice. They do not represent any obligation on the part of Alcatel. Such obligations will only be committed to in a written sales agreement signed by Alcatel. Trademarks
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. 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. Documentation
Product documentation is available on Alcatel-Lucent Online Support Documentation and Software web site at http://www.alcatel-lucent.com/osds. To offer comments on this documentation, visit Alcatel-Lucent Online Support Documentation and Software web site at http://www.alcatel-lucent.com/osds and select Online Services Helpdesk.
Developed by Alcatel-Lucent
Contents About this document Purpose ...................................................................................................................................................... xxi Reason for reissue ..................................................................................................................................... xxi Intended audience ...................................................................................................................................... xxi How to use this document ........................................................................................................................ xxii Safety information .................................................................................................................................... xxii Conventions used ..................................................................................................................................... xxiii Related documentation .............................................................................................................................xxiv Training ....................................................................................................................................................xxiv Document support .....................................................................................................................................xxv Technical support ......................................................................................................................................xxv How to order ..............................................................................................................................................xxv How to comment .......................................................................................................................................xxv Packaging collection and recovery requirements ......................................................................................xxv Recycling/take-back/disposal of product ................................................................................................ xxvi 1
Introduction ES16 System ............................................................................................................................................. 1-3 MAC-Ethernet Technique ......................................................................................................................... 1-7 MPLS Technique ....................................................................................................................................... 1-8 Ethernet Applications .............................................................................................................................. 1-10 MEF (Metro Ethernet Forum) Applications ............................................................................................ 1-20 Ethernet Private Line (EPL), end to end implementation example ......................................................... 1-22 E-Lan/E-VLan, end to end implementation example .............................................................................. 1-24 E-VPL, end to end implementation example .......................................................................................... 1-27 MPLS Applications ................................................................................................................................. 1-31 Protocols .................................................................................................................................................. 1-43 STP functionality (Spanning Tree Protocol) ........................................................................................... 1-55 Virtual Concatenation and LCAS ............................................................................................................ 1-64 GFP Packets Concatenation .................................................................................................................... 1-65
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA iii Issue 05 February 2010
Contents ............................................................................................................................................................................................................................................................
Loop-Back management ......................................................................................................................... 1-66 System alarm management ..................................................................................................................... 1-67 Auto-Negotiation management ............................................................................................................... 1-73 Flow-Control management ..................................................................................................................... 1-74 Port Mirroring management .................................................................................................................... 1-77 Bridging Data Plane ................................................................................................................................ 1-79 Link Aggregation management ............................................................................................................... 1-81 Control Protocols management in a Transport Network ......................................................................... 1-87 Redundancy features ............................................................................................................................... 1-90 Ethernet OAM ......................................................................................................................................... 1-93 Management software ............................................................................................................................. 1-95 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 Summary procedure for ES software installation ..................................................................................... 3-6 ES-CT Installation procedure .................................................................................................................... 3-8 NE-ES package installation procedure ................................................................................................... 3-26 Software Uninstallation procedure .......................................................................................................... 3-31 NE-ES software downloading ................................................................................................................. 3-34 Start-Up of the ES Craft Terminal management software ...................................................................... 3-38
4
Craft Terminal for ES Management Summary procedure for ES Management ................................................................................................. 4-4 Main view ................................................................................................................................................. 4-5 List of the menus options ........................................................................................................................ 4-14 Supervision management ........................................................................................................................ 4-31 Generic and common functions .............................................................................................................. 4-33 Diagnosis and Alarms Configuration ...................................................................................................... 4-39 MIB Management ................................................................................................................................... 4-53 Transmission ........................................................................................................................................... 4-55
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA iv Issue 05 February 2010
Contents ............................................................................................................................................................................................................................................................
OAM ...................................................................................................................................................... 4-226 Connection ............................................................................................................................................ 4-244 Performance .......................................................................................................................................... 4-305 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 ISA-ES Units replacement ...................................................................................................................... 5-18 Software Upgrading/Downgrading ......................................................................................................... 5-19
A
Technical support Technical assistance ................................................................................................................................. A-2 Accessing and navigating the On-Line Customer Support (OLCS) web site .......................................... A-7 Other technical support services ............................................................................................................ A-12
GL
Glossary Acronyms and Abbreviations .................................................................................................................GL-1 Terms and Definitions ..........................................................................................................................GL-17
IN
Index
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA v Issue 05 February 2010
Contents ............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA vi Issue 05 February 2010
List of figures 1
Introduction 1-1
ISA-ES16 subsystem, protocol stacking ...................................................................................... 1-6
1-2
Network application for ISA-ES System ..................................................................................... 1-6
1-3
Bridge representation example and relevant FDB table ............................................................. 1-10
1-4
VLAN Bridge representation example and relevant FDB table ................................................. 1-11
1-5
Generic VLAN Classification-Identification-Aggregation (example) ....................................... 1-13
1-6
Stacked VLAN management (example) .................................................................................... 1-14
1-7
Transparent Mac/Virtual Port-to-Port XC “OneStep" (Example) .............................................. 1-15
1-8
MAC Bridge distribution domain (example) ............................................................................. 1-16
1-9
Virtual Bridge distribution domain (example) ........................................................................... 1-16
1-10
Provider Bridge distribution domain (example) ......................................................................... 1-17
1-11
End-to-End ETS link Example ................................................................................................... 1-19
1-12
MEF-Network application for OMSN+ISA-ES System ............................................................ 1-21
1-13
EPL application example ........................................................................................................... 1-23
1-14
Example of E-Lan/E-VLan implementation (1: centralized LAN) ............................................ 1-25
1-15
Example of E-Lan/E-VLan implementation (2: distributed LAN) ............................................ 1-26
1-16
EVPL implementation example ................................................................................................. 1-29
1-17
MPLS-Network application for ISA-ES System ....................................................................... 1-31
1-18
Generic MPLS aggregation scheme (Tunnelling) ...................................................................... 1-32
1-19
MPLS Tunnelling scheme example ........................................................................................... 1-34
1-20
MPLS Tunnelling over SONET/SDH Example ......................................................................... 1-40
1-21
MPLS tunnelling over Ethernet structure ................................................................................... 1-42
1-22
Ethernet Packet format ............................................................................................................... 1-43
1-23
Ethernet packet and MAC frame format .................................................................................... 1-43
1-24
Ethernet “Q-Tagged" MAC 802.3 frame format ........................................................................ 1-44
1-25
TCI Field format (802.1Q VLAN Tag) ...................................................................................... 1-44
1-26
Ethernet “Stacked VLAN" frame format ................................................................................... 1-45
1-27
Ethernet frame format for “MPLS over Ethernet" ..................................................................... 1-45
1-28
MPLS label format ..................................................................................................................... 1-45
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA vii Issue 05 February 2010
List of figures ............................................................................................................................................................................................................................................................
1-29
GFP Framing (from G.7041/Y.1303) ......................................................................................... 1-46
1-30
Ethernet encapsulation into GFP frame (from G.7041/Y.1303) ................................................ 1-47
1-31
Ethernet/LAPS encapsulation (ITU-T X.86) ............................................................................. 1-47
1-32
Ethernet (and MPLS over Ethernet) Framing (Local Ethernet Port) ......................................... 1-48
1-33
Ethernet over SDH Framing (Remote Ethernet Port) ................................................................ 1-48
1-34
Ethernet over MPLS over SDH Framing (MPLS Port) ............................................................. 1-49
1-35
STP/RSTP BPDU Frame format ............................................................................................... 1-55
1-36
Spanning Tree function (STP) example ..................................................................................... 1-56
1-37
Some examples of Bridges and Ports roles in xSTP network .................................................... 1-57
1-38
PER-VLAN Spanning Tree example ......................................................................................... 1-58
1-39
PER-VLAN Spanning Tree - example of active topology ......................................................... 1-59
1-40
MSTP BPDU Frame format ....................................................................................................... 1-60
1-41
MSTP Network topology example ............................................................................................ 1-61
1-42
MSTP “collapsed” topology example ........................................................................................ 1-62
1-43
MSTP, VLAN differentiated routing example ........................................................................... 1-63
1-44
Virtual Concatenation (example) ............................................................................................... 1-64
1-45
GFP Packets Concatenation ....................................................................................................... 1-65
1-46
Internal & Line Loop Back scheme ........................................................................................... 1-66
1-47
CSF alarm management ............................................................................................................. 1-67
1-48
LLCF in Hub-Spoke network topology ..................................................................................... 1-68
1-49
LLCF propagation ...................................................................................................................... 1-69
1-50
VC-AIS alarm management ....................................................................................................... 1-70
1-51
Configure (remote) Ethernet Port: GFP: VC-AIS setting .......................................................... 1-72
1-52
Configure (local) Ethernet Port: MAU: Flow Control and ShutDown disabling ....................... 1-72
1-53
Flow Control scheme ................................................................................................................. 1-75
1-54
Configure (local) Ethernet Port: MAU: Flow Control setting ................................................... 1-76
1-55
Port Mirroring example .............................................................................................................. 1-78
1-56
Segregation application example ............................................................................................... 1-79
1-57
IGMP application example ........................................................................................................ 1-80
1-58
LACPDU Frame format ............................................................................................................. 1-84
1-59
Link Aggregation example ......................................................................................................... 1-85
1-60
Customer BPDU Selective Tunnelling capability ...................................................................... 1-88
1-61
EPS 1+1 protection .................................................................................................................... 1-90
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA viii Issue 05 February 2010
List of figures ............................................................................................................................................................................................................................................................
2
1-62
Dual-homing BPDU STP - dual (PE) node ................................................................................ 1-91
1-63
Dual-homing BPDU (network) STP tunnel ............................................................................... 1-92
1-64
Dual-homing BPDU (local) STP tunnel .................................................................................... 1-92
1-65
Connectivity Fault Management ................................................................................................ 1-93
1-66
Protocol stack for ATM/MPLS/Ethernet over SDH management ............................................. 1-97
1-67
Example of management of an SDH network with SDH and ES traffic ................................... 1-98
1-68
OSI and IP addressing example ............................................................................................... 1-100
Software Product and Licence 2-1
3
Management Software, generic structure ..................................................................................... 2-2
ES Software Installation 3-1
Craft Terminal components versions ............................................................................................ 3-2
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 in progress, temporary windows sequence presentation .................................................. 3-16
3-12
Successive installation, temporary windows presentation ......................................................... 3-17
3-13
Installation procedure menu window (2nd step) ........................................................................ 3-18
3-14
Craft Terminal master setup, list of detected Components on the media ................................... 3-18
3-15
Selecting SNMPCT component ................................................................................................. 3-19
3-16
Existing different SNMPCT release to be uninstalled ............................................................... 3-20
3-17
Existing previous similar release to be maintained: “REPAIR" ................................................ 3-21
3-18
SNMP CT Add On setup ............................................................................................................ 3-22
3-19
SNMPCT setup in progress temporary window ........................................................................ 3-23
3-20
Maintenance Finished ................................................................................................................ 3-24
3-21
SNMPCT installation completed ............................................................................................... 3-24
3-22
Selecting installation procedure (end step) ................................................................................ 3-25
3-23
Descriptor files administration ................................................................................................... 3-26
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA ix Issue 05 February 2010
List of figures ............................................................................................................................................................................................................................................................
4
3-24
Software Package Administration-ES service specific .............................................................. 3-27
3-25
File-Browser for Software Package installation ........................................................................ 3-28
3-26
Software Package Administration - create Enhanced OMSN ................................................... 3-28
3-27
Software Package Administration - add ES service ................................................................... 3-29
3-28
Add/Remove Programs icon selection ....................................................................................... 3-31
3-29
Add/Remove Programs view ..................................................................................................... 3-32
3-30
Delete confirmation (example) .................................................................................................. 3-32
3-31
Delete completed (example) ...................................................................................................... 3-33
3-32
Download Initiate (example) ..................................................................................................... 3-34
3-33
Download confirmation box ...................................................................................................... 3-35
3-34
Download progress .................................................................................................................... 3-35
3-35
NE Software package activation (example) ............................................................................... 3-36
3-36
Activate SW package confirmation ........................................................................................... 3-36
3-37
SW package details .................................................................................................................... 3-37
3-38
1320CT software start-up .......................................................................................................... 3-38
3-39
NES view example ..................................................................................................................... 3-39
3-40
ES view example ........................................................................................................................ 3-40
3-41
Login dialog box ........................................................................................................................ 3-40
3-42
ISA USM starting ...................................................................................................................... 3-41
Craft Terminal for ES Management 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-13
4-5
Set Manager list ......................................................................................................................... 4-32
4-6
Configuration -> Options ........................................................................................................... 4-34
4-7
Configuration -> Options - Program (“Full Window Mode" example) ..................................... 4-35
4-8
Configuration -> Options - Program (“Tabbed Window Mode" example) ................................ 4-35
4-9
Views -> Search ......................................................................................................................... 4-37
4-10
Views -> Print ............................................................................................................................ 4-38
4-11
ASAP Management dialog ........................................................................................................ 4-40
4-12
ASAP: Severities profile example ............................................................................................. 4-41
4-13
ASAP: Set Alarm Severities (example) ..................................................................................... 4-45
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA x Issue 05 February 2010
List of figures ............................................................................................................................................................................................................................................................
4-14
Loop Back Management dialog ................................................................................................. 4-46
4-15
Alarms Surveillance (“ISA Alarms" example) .......................................................................... 4-48
4-16
Log Retrieval: Event (Filter example) ........................................................................................ 4-50
4-17
Log Retrieval: Event (Report example) ..................................................................................... 4-50
4-18
Log Retrieval: Alarm (Filter example) ....................................................................................... 4-51
4-19
Log Retrieval: Alarm (Report example) .................................................................................... 4-51
4-20
MIB management -> Backup/Restore DB ................................................................................. 4-53
4-21
Backup info boxes ...................................................................................................................... 4-54
4-22
Backup/restore selection ........................................................................................................... 4-54
4-23
Configuration: ETS Traffic Descriptor (example) ..................................................................... 4-57
4-24
Create an ETS Traffic Descriptor (example) .............................................................................. 4-58
4-25
ETB Virtual/MAC Bridge Scheduling Mode ............................................................................. 4-63
4-26
Provider Bridge, 8P0D Scheduling Model ................................................................................. 4-64
4-27
Configuration: MPLS Traffic Descriptor (example) .................................................................. 4-67
4-28
Create an MPLS Traffic Descriptor (example) .......................................................................... 4-68
4-29
Configure ISA - System Info ..................................................................................................... 4-71
4-30
Configure ISA - Bridge Management ........................................................................................ 4-73
4-31
Configure ISA - MIB Default Value .......................................................................................... 4-74
4-32
ISA Properties (example) ........................................................................................................... 4-74
4-33
ISA-ES node: transmission application table ............................................................................. 4-75
4-34
Configure (local) Ethernet Port - Configuration ........................................................................ 4-80
4-35
Configure (local) Ethernet Port - MAU ..................................................................................... 4-83
4-36
Configure (local) Ethernet Port - L2 Control Frame .................................................................. 4-84
4-37
Configure (local) Ethernet Port - Port Mirroring ....................................................................... 4-85
4-38
Configure (local) Ethernet Port - Alarms ................................................................................... 4-86
4-39
List of Protocol Profile ............................................................................................................... 4-87
4-40
Create Protocol Profile ............................................................................................................... 4-88
4-41
(Local) Ethernet Port Properties ................................................................................................. 4-89
4-42
Configure (remote) Ethernet Port - Configuration ..................................................................... 4-93
4-43
Configure (remote) Ethernet Port - GFP .................................................................................... 4-94
4-44
Configure (remote) Ethernet Port - L2 Control Frame .............................................................. 4-95
4-45
Configure (remote) Ethernet Port - Alarms ................................................................................ 4-96
4-46
Configure (remote) Ethernet Port - LAPS ................................................................................. 4-96
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA xi Issue 05 February 2010
List of figures ............................................................................................................................................................................................................................................................
4-47
Rate Limiting Combination example (VC4 case) ...................................................................... 4-99
4-48
Virtual Concatenation Granularity example (MII, VC12 case) ............................................... 4-100
4-49
Inconsistency error on Port Configuration ............................................................................... 4-100
4-50
(Remote) Ethernet Port Properties ........................................................................................... 4-101
4-51
Substitute Server Layer (from GFP to LAPS) ......................................................................... 4-102
4-52
Substitute Server Layer (from LAPS to GFP) ......................................................................... 4-102
4-53
Configure ACL ......................................................................................................................... 4-104
4-54
ACL list setting ........................................................................................................................ 4-106
4-55
ACL/ACE setting ..................................................................................................................... 4-109
4-56
Port: ACL Properties ................................................................................................................ 4-110
4-57
Port: Disassociate ACL ............................................................................................................ 4-111
4-58
Create ETS InFlow ................................................................................................................... 4-114
4-59
List of Color Profile ................................................................................................................. 4-115
4-60
Create Color Profile ................................................................................................................. 4-115
4-61
Create ETS OutFlow ................................................................................................................ 4-118
4-62
Create VLAN Management ..................................................................................................... 4-120
4-63
Create Provider InFlow ............................................................................................................ 4-122
4-64
Provider Inflow: S-VID Filter .................................................................................................. 4-123
4-65
Create Provider OutFlow ......................................................................................................... 4-124
4-66
Delete ETS InFlow ................................................................................................................... 4-126
4-67
Create ETH2ETS Classifier ..................................................................................................... 4-129
4-68
Substitute Ethernet -> PPP ....................................................................................................... 4-131
4-69
Substitute PPP -> Ethernet ....................................................................................................... 4-132
4-70
Configure PPP Port .................................................................................................................. 4-135
4-71
PPP Port Properties .................................................................................................................. 4-136
4-72
Configure MPLS Port (Remote side) ....................................................................................... 4-139
4-73
Configure MPLS Port (Local side, 1GbETH. i/f) .................................................................... 4-140
4-74
Inconsistency error on MPLS Port Configuration ................................................................... 4-140
4-75
MPLS Port Properties .............................................................................................................. 4-141
4-76
Configure MPLS Port - Configuration (Multi Client Layer, over GFP) .................................. 4-143
4-77
Configure MPLS Port - GFP (Multi Client Layer, over GFP) ................................................. 4-144
4-78
Configure MPLS Port - Label Range (Multi Client Layer, over GFP) .................................... 4-145
4-79
Configure MPLS Port - Alarm (Multi Client Layer, over GFP) .............................................. 4-146
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA xii Issue 05 February 2010
List of figures ............................................................................................................................................................................................................................................................
4-80
MPLS InSegment Properties .................................................................................................... 4-147
4-81
MPLS OutSegment Properties ................................................................................................. 4-149
4-82
Create ETS InFlow (into Inner Tunnel) ................................................................................... 4-150
4-83
Create ETS OutFlow (into Inner Tunnel) ................................................................................. 4-151
4-84
Substitute Port Type (from ETS to ETB) ................................................................................. 4-154
4-85
Substitute Port Type (from ETB to ETS) ................................................................................. 4-154
4-86
Substitute Client Type (from ETS to Link Aggregator) ........................................................... 4-154
4-87
VLAN Registration .................................................................................................................. 4-156
4-88
Static VLAN Registration Management (Provider case) ......................................................... 4-158
4-89
Configure Provider Bridge Port (“PERVLANSTP" case) ....................................................... 4-163
4-90
Configure Bridge Port (MSTP case) ........................................................................................ 4-166
4-91
Configure MAC Bridge Port .................................................................................................... 4-168
4-92
Port VLAN Identifier (PVID) association ............................................................................... 4-169
4-93
Bridge Port: Default User Priority ........................................................................................... 4-170
4-94
Bridge Port: Regenerated Priority List ..................................................................................... 4-171
4-95
Bridge Port: STP-Per Bridge Management .............................................................................. 4-174
4-96
Bridge Port: STP-Per Bridge Management (MSTI case) ......................................................... 4-174
4-97
Bridge Port: STP-Per Port Management .................................................................................. 4-177
4-98
BridgePort: STP-Per Port Management (MSTI case) .............................................................. 4-177
4-99
Bridge Port: CIST: MST Region Management ........................................................................ 4-179
4-100 Bridge Port: CIST: MST Region List ....................................................................................... 4-179 4-101 Bridge Port: MSTI: MSTI Management .................................................................................. 4-181 4-102 Bridge Port: MSTI: MSTID/VLAN Assignment ..................................................................... 4-181 4-103 Bridge Port: MSTI: MSTID/VLAN List .................................................................................. 4-181 4-104 Bridge Port Properties (Provider/MSTP case) ......................................................................... 4-182 4-105 Show VLAN Info ..................................................................................................................... 4-183 4-106 Queue (QoS) Management ....................................................................................................... 4-186 4-107 QoS Management: Forwarding Class Number ........................................................................ 4-186 4-108 QoS Management: Queue Number and weighting .................................................................. 4-186 4-109 QoS Management: Queue Properties ....................................................................................... 4-186 4-110 Queue (QoS) Properties ........................................................................................................... 4-188 4-111 QoS Properties: Forwarding Class Mapping ............................................................................ 4-188 4-112 QoS Properties: Queue Number List ........................................................................................ 4-189 ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA xiii Issue 05 February 2010
List of figures ............................................................................................................................................................................................................................................................
4-113 ISA: IGMP Snooping Management List .................................................................................. 4-191 4-114 ISA: IGMP Snooping, VLAN association ............................................................................... 4-192 4-115 Port: IGMP Services Management .......................................................................................... 4-195 4-116 Port: IGMP Services Management: VLAN ID ........................................................................ 4-195 4-117 Port: IGMP Services Properties List ........................................................................................ 4-197 4-118 Port: IGMP Request Membership Group ................................................................................ 4-198 4-119 Aggregator: Creation ............................................................................................................... 4-201 4-120 Aggregator: Set Protocol List .................................................................................................. 4-201 4-121 Aggregator: Configure Aggregator/Configuration ................................................................... 4-205 4-122 Aggregator: Configure Aggregator/Information ...................................................................... 4-206 4-123 Aggregator: Configure Aggregator/Alarm ............................................................................... 4-206 4-124 Aggregator Properties .............................................................................................................. 4-207 4-125 Delete Aggregator .................................................................................................................... 4-208 4-126 Aggregation Port: Configure .................................................................................................... 4-211 4-127 Aggregation Port: Set Actor Admin Key ................................................................................. 4-211 4-128 Aggregation Port: Properties .................................................................................................... 4-212 4-129 In Fiber In Band : Create ........................................................................................................ 4-214 4-130 In Fiber In Band : Modify ....................................................................................................... 4-215 4-131 In Fiber In Band : Delete ........................................................................................................ 4-216 4-132 In Fiber In Band : Properties .................................................................................................... 4-216 4-133 Configure Hub-Spoke ............................................................................................................. 4-217 4-134 EFM Management: Configuration .......................................................................................... 4-220 4-135 EFM Management: Statistics .................................................................................................. 4-223 4-136 EFM Management: Alarms ..................................................................................................... 4-224 4-137 EFM Management: Properties ................................................................................................ 4-225 4-138 OAM: Configure Resources ..................................................................................................... 4-227 4-139 OAM: Configure Resources: Create MD ................................................................................. 4-228 4-140 OAM: Configure Resources: Delete MD ................................................................................. 4-229 4-141 OAM: Configure Resources: MA Navigation ......................................................................... 4-229 4-142 OAM: Configure: MA Navig.: Create MA .............................................................................. 4-230 4-143 OAM: Configure: MA Navig.: Create: Vid ............................................................................ 4-231 4-144 OAM: Configure: MA Navig.: MEP Navigation .................................................................... 4-231 4-145 OAM: Configure: MA Navig.: MEP Navigation: Create MEP ............................................... 4-232 ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA xiv Issue 05 February 2010
List of figures ............................................................................................................................................................................................................................................................
4-146 OAM: Configure: MA Navig.: MEP Navigation: Loop Back ................................................ 4-233 4-147 OAM: Configure: MA Navig.: MEP Navigation: Link Trace ................................................ 4-234 4-148 OAM: Configure: MA Navig.: MEP Navigation: Details ....................................................... 4-235 4-149 OAM: Configure: MA Navig.: Show All MEP ....................................................................... 4-236 4-150 OAM: Configure: MA Navig.: MA-MEP List ID .................................................................. 4-237 4-151 OAM: Configure: MA Navig.: Modify ................................................................................... 4-237 4-152 OAM: Configure: MA Navig.: Modify: Show ........................................................................ 4-238 4-153 OAM: Configure: MA Navig.: Details .................................................................................... 4-238 4-154 OAM: Configure: MA Navig.: Delete .................................................................................... 4-239 4-155 OAM: Properties Resources ..................................................................................................... 4-239 4-156 OAM: Configure ...................................................................................................................... 4-240 4-157 OAM: Properties ...................................................................................................................... 4-241 4-158 OAM: Configure LoopBack ..................................................................................................... 4-241 4-159 OAM: Configure Loop Back: Test List ................................................................................... 4-242 4-160 OAM: Configure Loop Back: Test List: Modify ...................................................................... 4-243 4-161 OAM: Loop Back Properties .................................................................................................... 4-243 4-162 Filtering Data Base/Dynamic Filtering Database (Virtual Bridge case) .................................. 4-246 4-163 Filtering Data Base/Static Unicast Filtering (Virtual Bridge case) .......................................... 4-248 4-164 Filtering Data Base/Static Multicast Filtering (Virtual Bridge case) ....................................... 4-249 4-165 Filtering Data Base/Dynamic Multicast Filtering (Virtual Bridge case) ................................. 4-250 4-166 Filtering Data Base/Learned Mac Address Details .................................................................. 4-250 4-167 Segregated Port Management ................................................................................................... 4-251 4-168 Ethernet Port: Connection application table ............................................................................ 4-253 4-169 Create ETS XC “One Step" - Ethernet example ...................................................................... 4-258 4-170 Topology Classification Properties (examples) ........................................................................ 4-258 4-171 Protocol List ............................................................................................................................. 4-259 4-172 Create ETS XC “One Step" - ETS Virtual Switch example .................................................... 4-260 4-173 Create ETS XC “One Step" - MPLS Tunnel (TAIL) ............................................................... 4-263 4-174 Create ETS XC “One Step" ..................................................................................................... 4-266 4-175 Error message on “Create ETS XC One Step" ........................................................................ 4-266 4-176 Topology for “Create ETS XC One Step" (Provider) .............................................................. 4-268 4-177 Create ETS XC “One Step" (Provider, UNI-UNI) ................................................................... 4-272 4-178 Create ETS XC “One Step" (Provider, UNI-NNI) ................................................................... 4-273 ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA xv Issue 05 February 2010
List of figures ............................................................................................................................................................................................................................................................
4-179 Create ETS XC “One Step" (Provider, NNI-UNI) .................................................................. 4-275 4-180 SVID Filter ............................................................................................................................... 4-275 4-181 Delete ETS XC “One Step" (ETS & MPLS Tunnel) ............................................................... 4-277 4-182 Delete ETS XC “One Step" (MAC & Virtual) ........................................................................ 4-279 4-183 Topology for Delete ETS XC “One Step" (Provider) .............................................................. 4-281 4-184 Delete ETS XC “One Step" (Provider, UNI-UNI) .................................................................. 4-281 4-185 Delete ETS XC “One Step" (Provider, UNI-NNI) .................................................................. 4-282 4-186 Delete ETS XC “One Step" (Provider, NNI-UNI) .................................................................. 4-283 4-187 ETS XC Properties ................................................................................................................... 4-285 4-188 MPLS XC Properties ............................................................................................................... 4-288 4-189 Create Outer Head Tunnel ....................................................................................................... 4-292 4-190 Create Outer Transit Tunnel ..................................................................................................... 4-294 4-191 Create Outer Tail Tunnel .......................................................................................................... 4-295 4-192 Create Inner (“Head") MPLS Tunnel ....................................................................................... 4-299 4-193 Create Inner (“Tail") MPLS Tunnel ......................................................................................... 4-299 4-194 Outer MPLS Tunnel Properties ................................................................................................ 4-301 4-195 Delete Outer MPLS Tunnel ..................................................................................................... 4-301 4-196 Inner (“Head”) MPLS Tunnel Properties ................................................................................. 4-303 4-197 Ethernet Port Configure Monitoring (example) ....................................................................... 4-307 4-198 Ethernet Port Monitoring Properties (example) ....................................................................... 4-309 4-199 InFlow Configure Monitoring (example) ................................................................................. 4-310 4-200 InFlow Monitoring Properties (example) ................................................................................ 4-312 4-201 OutFlow Configure Monitoring (example) .............................................................................. 4-313 4-202 OutFlow Monitoring Properties (example) .............................................................................. 4-315 4-203 PM data results (Port example) ................................................................................................ 4-318 4-204 PM data results (InFlow example) ........................................................................................... 4-318 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-10
5-4
Example of EthernetPort 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA xvi Issue 05 February 2010
List of figures ............................................................................................................................................................................................................................................................
5-7 A
AlarmsSurveill.-“Alarm Sublist" window (“ISA Alarms" example) ......................................... 5-15
Technical support
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA xvii Issue 05 February 2010
List of figures ............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA xviii Issue 05 February 2010
List of tables About this document 1 1
2
Alcatel-Lucent ISA ES16 Documentation Set ............................................................................xxiv
Introduction 1-1
Ethernet over SDH layer stack ..................................................................................................... 1-7
1-2
Ethernet over MPLS SDH layer stacking .................................................................................... 1-9
1-3
MPLS over ETHERNET layer stacking ...................................................................................... 1-9
1-4
L2 Control Protocols .................................................................................................................. 1-50
1-5
IEEE 802.3 Slow Protocols ........................................................................................................ 1-51
Software Product and Licence 2-1
Software product part number ...................................................................................................... 2-3
2-2
Software licenses part numbers ................................................................................................... 2-3
3
ES Software Installation
4
Craft Terminal for ES Management
5
4-1
Alarms & Severities association in predefined ASAPs.............................................................. 4-43
4-2
Typical association between TD, UP and P-CoS (ETB ports MAC/Virtual Bridge .................. 4-63
4-3
Provider Bridge - Traffic Scheduling in 8P0D mode ................................................................ 4-64
4-4
Provider Bridge - Traffic Scheduling in 5P3D mode ................................................................ 4-65
4-5
Provider Bridge - Traffic Scheduling in 6P2D mode ................................................................ 4-66
4-6
Provider Bridge - Traffic Scheduling in 7P1D mode ................................................................ 4-66
4-7
Traffic Descriptor, Policing Mode and Color Profile for INFLOW resource: ......................... 4-116
4-8
Prioritization for OUTFLOW resource with “Stacked-VLAN Management" ......................... 4-120
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-8
5-4
Domain Alarm Synthesis indication ............................................................................................ 5-8
5-5
Management States Control Panel ............................................................................................... 5-9
5-6
Alarms Surveillance information general description ................................................................ 5-16
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA xix Issue 05 February 2010
List of tables ............................................................................................................................................................................................................................................................
A
5-7
“Probable Cause" of alarms and relevant maintenance actions ................................................. 5-17
5-8
DIP-SWITCHES operations ...................................................................................................... 5-18
Technical support
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA xx Issue 05 February 2010
About this document
Purpose This document provides general information and operational procedures common to all Alcatel-Lucent ISA Board ES16 performing ES16 functions (Alcatel-Lucent ISA ES16). Reason for reissue This document is the fourth issue of Release 2.5. History Issue
Date
Reason
01
September 2008
First validated issue of this guide
02
October 2008
SW features alignment
03
April 2009
13352 DTT’s modification request (“Port Mirroring
sector:” (p. 4-85) 04
October 2009
Re-structuring to OneDoc and incorporation of features (Dual homing and Customer BPDU tunneling)
05
February 2010
General upgrading and incorporation of features. 34733 DTT’s modification request (“Ethernet Port -> Configure ACL / ACE management” (p. 4-107)).
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 ES16 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-xxiv). 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 ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA xxi Issue 05 February 2010
About this document ............................................................................................................................................................................................................................................................
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. 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 ES16 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA xxii Issue 05 February 2010
About this document ............................................................................................................................................................................................................................................................
Conventions used The following typographical conventions are used in this guide: Appearance
Description
italicized text
• • • •
italicized bold text
• •
GUI reference or key name
• •
File and directory names Emphasized information Titles of publications A value that the user supplies Emphasized information A value that the user supplies 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
For the remainder of this document, “Alcatel-Lucent ISA ES16” is used in place of Alcatel-Lucent ISA Board ES16 in most cases.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA xxiii Issue 05 February 2010
About this document ............................................................................................................................................................................................................................................................
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. 4.5. The following table provide additional information about the Alcatel-Lucent ISA Board : Table 1
Alcatel-Lucent ISA ES16 Documentation Set
Document Number
Document Title
3AL 79551 AAAA
1320CT-Basic Operator Handbook AS Operator's Handbook ELB Operator's Handbook
OMSN-Operator Handbook Alcatel-Lucent 1640FOX Operator Handbook Alcatel-Lucent 1650SMC Operator Handbook Alcatel-Lucent 1660SM Operator Handbook OMSN-Technical Handbooks Alcatel-Lucent 1640FOX Technical Handbooks Alcatel-Lucent 1650SMC Technical Handbooks 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.lucent.com.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA xxiv Issue 05 February 2010
About this document ............................................................................................................................................................................................................................................................
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). 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://www.alcatel-lucent-info.com/comments) or email your comments to the Comments Hotline (
[email protected]). 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, contact the Alcatel-Lucent Field Services/Installation Environmental Health and Safety organization. For installations not performed by Alcatel-Lucent, 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA xxv Issue 05 February 2010
About this document ............................................................................................................................................................................................................................................................
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 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 AlcatelLucent 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, contact your Alcatel-Lucent Account Manager or Alcatel-Lucent Take-Back Support at
[email protected].
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA xxvi Issue 05 February 2010
1
Introduction
Overview This chapter describes the main features of the graphical interface for the ISA-ES 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: •
“ES16 System” (p. 1-3)
•
“MAC-Ethernet Technique” (p. 1-7)
•
“MPLS Technique” (p. 1-8)
•
“Ethernet Applications” (p. 1-10) “Example of end-to-end ETS link creation (“none” Bridge case)” (p. 1-17) “MEF (Metro Ethernet Forum) Applications” (p. 1-20) “Ethernet Private Line (EPL), end to end implementation example” (p. 1-22) “E-Lan/E-VLan, end to end implementation example” (p. 1-24) “E-VPL, end to end implementation example” (p. 1-27) “MPLS Applications” (p. 1-31) •
• • • • •
“MPLS Tunnel: Labelling and Bandwidth Matching” (p. 1-32) • “Example of MPLS over SDH Tunnelling creation” (p. 1-34) • “Example of MPLS over Ethernet Tunnelling creation” (p. 1-40) “Protocols” (p. 1-43) •
•
•
“Data frames” (p. 1-43)
•
“Protocol list” (p. 1-50) “STP functionality (Spanning Tree Protocol)” (p. 1-55) “Virtual Concatenation and LCAS” (p. 1-64)
•
“GFP Packets Concatenation” (p. 1-65)
• •
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-1 Issue 05 February 2010
Introduction
Overview
............................................................................................................................................................................................................................................................
• •
“Loop-Back management” (p. 1-66) “System alarm management” (p. 1-67)
•
“CSF alarm management” (p. 1-67) • “LLCF (Link Loss Carry Forward) in Hub-and-Spoke” (p. 1-68) • “VC-AIS alarm management” (p. 1-70) “Auto-Negotiation management” (p. 1-73)
•
“Flow-Control management” (p. 1-74)
•
“Port Mirroring management” (p. 1-77)
•
“Bridging Data Plane” (p. 1-79)
•
• •
“Segregated Ports management” (p. 1-79) “IGMP Snooping management” (p. 1-79)
“IGMP Snooping management” (p. 1-79) “Link Aggregation management” (p. 1-81) •
•
“Link Aggregation, implementation example” (p. 1-85) “Control Protocols management in a Transport Network” (p. 1-87) •
•
“Selective Tunnelling” (p. 1-87) • “Dual-homing” (p. 1-88) “Redundancy features” (p. 1-90) •
•
“EPS 1+1 management” (p. 1-90) • “Dual-homing (via selective BPDU tunnelling)” (p. 1-91) “Ethernet OAM” (p. 1-93) •
•
“Connectivity Fault Management” (p. 1-93) “Control Protocols management in a Transport Network” (p. 1-87) •
•
• •
“Ethernet over SDH Management” (p. 1-97) “ES-CT main management menus” (p. 1-101)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-2 Issue 05 February 2010
Introduction
ES16 System
............................................................................................................................................................................................................................................................
ES16 System The Alcatel-Lucent ISA-ES16 (Integrated Services Adapter-Ethernet Switching) is a system operating at layer 2 of the ISO-OSI stack by means of the MAC protocol and/or the MPLS protocol. By virtue of the MAC layer processing, it acts as an Ethernet Switch (or bridge), used to interconnect and route Ethernet data flows transiting on the afferent LAN's. 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. By virtue of the MPLS layer processing, it acts as a Label Switch Router (LSR), used to route ethernet data flows, inserting them, and if possible aggregating, into virtual tunnels (LSP, Label Switched Path) marked by labels; the MPLS tunnels are then laid on SDH containers by means of the EOS encapsulation (Ethernet over MPLS over SDH). The Alcatel-Lucent ES16 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. It has an SDH equivalent capacity of: 16 VC4 (on 1660SM-10Gb), 8 VC4 (on 1660SMEnhSlot and 1662SMC), 4 VC4 (on 1660SM and 1650SMC). Its maximum packets throughput is 4.4 Gb/s, of which 2.4 Gb/s are for remote ports and the remaining for local ones. It is accessed by 14 Fast Ethernet Local ports, or 4 Giga Ethernet Local port, and 64 Remote ports; local ports are located on independent access modules. The Fast Ethernet and Giga Ethernet local ports are alternative between them. The Ethernet Bridge (ETB) function may be automatically carried out by means of the “MAC autolearning" (also called “MAC Bridge") procedure (802.1D Rec.), or by means of manual “engineered" cross-connections. The MAC-Bridge representation is schematically illustrated in Figure 1-3, (pg. 1-10), see also Figure 1-8, (pg. 1-16). 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. The Virtual Bridge representation is schematically illustrated in Figure 1-4, (pg. 1-11). See also Figure 1-9, (pg. 1-16). ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-3 Issue 05 February 2010
Introduction
ES16 System
............................................................................................................................................................................................................................................................
A Provider Bridge application is illustrated in Figure 1-10, (pg. 1-17). Some generic examples about VLAN and S-VLAN utilization are reported in Figure 1-5, (pg. 1-13) and Figure 1-6, (pg. 1-14). 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, Per-VLAN-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 Recs. Some more details and examples about STP are reported in “Protocol list” (p. 1-50). Furthermore, ES16 System supports the following functions: •
IGMP (Internet Group Multicast Protocol), see “IGMP Snooping management” (p. 1-79).
•
Link Aggregation , see “Link Aggregation management” (p. 1-81).
•
OAM (Operation, Administration, Maintenance), see “OAM” (p. 4-226).
•
Port Mirroring, see “Link Aggregation management” (p. 1-81).
•
ACL (Access Control List), see “Transmission -> Ethernet Port -> ACL -> Configure ACL” (p. 4-104).
The MPLS Label Switch Router (LSR) can manage packets data streams transported over “local" Ethernet FE or GE (Fast Ethernet, Gigabit Ethernet) and “remotized" ethernet over GFP/SDH; the packets are identified and classified with a first label (by inspecting the ethernet frame header), marked again by the label switching router with a second label, and then sent into the MPLS Network Port, aggregated and encapsulated into PPP/HDLC/SDH frames. If coming from the MPLS Network Port, the packets can be terminated towards the ethernet ports or routed towards other routers, if possible they are also aggregated into a common FEC; the routing operation is performed by the swapping of the top label. The MPLS LSR is accomplished, in current release, by means of manual “engineered" cross-connections, and the labels assignment to the LSP Tunnels is also manually engineered.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-4 Issue 05 February 2010
Introduction
ES16 System
............................................................................................................................................................................................................................................................
The various Ethernet frames formats are illustrated in Figure 1-22, (pg. 1-43) till to Figure 1-31, (pg. 1-47). The mpls label is illustrated in Figure 1-28, (pg. 1-45). The other frames formats are reported in the related OMSN equipment Technical Handbooks, listed in Table 1, (pg. 1-xxiv), and in the standard recommendations. The Ethernet/GFP framing is illustrated in Figure 1-29, (pg. 1-46) and Figure 1-30, (pg. 1-47). The Ethernet/LAPS framing is illustrated in Figure 1-31, (pg. 1-47). The ISA-ES16 system and protocol stacking is illustrated in Figure 1-1, (pg. 1-6). Some Ethernet applications are reported in “Ethernet Applications” (p. 1-10) and “Example of end-to-end ETS link creation (“none” Bridge case)” (p. 1-17). Some Ethernet applications compliant with MEF (Metro Ethernet Forum) are reported in “MEF (Metro Ethernet Forum) Applications” (p. 1-20) till to “E-VPL, end to end implementation example” (p. 1-27). Some MPLS applications are reported in “MPLS Applications” (p. 1-31) till “Example of MPLS over Ethernet Tunnelling creation” (p. 1-40). The framing procedures are illustrated in “Protocols” (p. 1-43). The Ethernet (and MPLS over Ethernet) Framing (Local Ethernet Port) is illustrated in Figure 1-32, (pg. 1-48). The Ethernet over SDH Framing (Remote Ethernet Port) is illustrated inFigure 1-33, (pg. 1-48). The Ethernet over MPLS over SDH Framing (MPLS Port) is illustrated in Figure 1-34, (pg. 1-49). The insertion of the ES system into the SDH network is illustrated in Figure 1-2, (pg. 1-6). The Ethernet Bridge representation is schematically illustrated in Figure 1-3, (pg. 1-10). A generic example of Ethernet over SDH link is illustrated in Figure 1-11, (pg. 1-19). A generic link structure example of MPLS tunnelling over SDH is illustrated in Figure 1-20, (pg. 1-40). A generic link structure example of MPLS tunnelling over Ethernet is illustrated in Figure 1-21, (pg. 1-42). A generic scheme of MPLS classification and aggregation is illustrated in Figure 1-18, (pg. 1-32).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-5 Issue 05 February 2010
Introduction
ES16 System
............................................................................................................................................................................................................................................................
Figure 1-1
ISA-ES16 subsystem, protocol stacking 3
3
any
any
Optionally: - VLAN - S-VLAN
MAC
MPLS
Optionally: - VLAN - S-VLAN
2 MAC 1 FE or GE
2 3
any
3
any
2
MAC
2
MAC
GFP or LAPS 1
SDH/SONET (remote Ethernet)
MAC CIA Local Ethernet (optionally MPLS over Ethernet)
FE, GE
MAC and/or MPLS CIA
Ethernet over SDH/SONET
GFP or LAPS over SDH/SONET
Ethernet (or MPLS) Switch
64 ports MPLS CIA
ES16: 14 FE or 4 GE ports
Ethernet over MPLS over SONET/SDH
MPLS/PPP/HDLC over SDH/SONET
Max. trunk capacity:: - 16 VC4 on 1660SM - 4 VC4 on 1650SMC
Max throughput = 44 Gb/s 3
any
3
MAC 2
MPLS
MPLS
MPLS
MPLS
2 CIA = Classification, Identification, Aggregation. MAC-CIA: MAC layer processing, optionally including VLAN or S-VLAN processing. MPLS-CIA: MPLS layer processing.
PPP
1
Figure 1-2
any MAC
HDLC SDH/ SONET
Network application for ISA-ES System
Remote Ports Ethernet over SONET/SDH (POS)
B4
OMSN + ISA-ES OMSN + ISA-ES
Ethernet Bridge or LSR
Local Ethernet Ports
B2
SDH SONET NETWORK B1 OMSN + ISA-ES
B3
OMSN + ISA-ES
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-6 Issue 05 February 2010
Introduction
MAC-Ethernet Technique
............................................................................................................................................................................................................................................................
MAC-Ethernet Technique The Ethernet (also called MAC 802.3) technique, 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 multiaccess 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-22, (pg. 1-43), and then are sent into the Ethernet physical layer (level1), after conversion using the Manchester encoding procedure. For more information about Ethernet/MAC refer to IEEE 802.3 standard. Table 1-1 Ethernet over SDH layer stack 3
NETWORK
any network “packetized" data service
2
DATA LINK
ETHERNET
1
PHYSICAL
SDH
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-7 Issue 05 February 2010
Introduction
MPLS Technique
............................................................................................................................................................................................................................................................
MPLS Technique The MPLS (Multi Protocol Label Switching) technique is used in Alcatel-Lucent transport systems in order to distribute and route data packets originated by the network layer (level 3 of the protocol stack) and encapsulated into the Ethernet 802.3 frame; it can be seen as a server layer for the Ethernet client layer (called “MPLS over SDH"). The data may also be “MPLS-packed" at the network edge, and transported over Ethernet; this transport modality is called “MPLS over Ethernet". MPLS over SDH operates at the level 2 of the protocol stack and uses the SDH as its physical layer to transport and aggregate the various streams of data packets; see Table 1-2, (pg. 1-9). The MPLS over Ethernet layering is illustrated in Table 1-3, (pg. 1-9). The MPLS technique consists of binding one or more Labels to the packets, in this way permitting the forwarding of a packet to the other nodes of the network without inspecting the level 3 header, only the look up of the attached label(s) is needed. The classification of the incoming packets are performed only once, at the edge of the MPLS network; the inner MPLS routers have only to select the next hop to which forwarding the incoming packets, by looking the top label. It is a path oriented connection less service; all the packets belonging to the same stream and assigned to the same class of service are all treated the same way by a router. In other words, when they enter the network, the packets are assigned to a Forwarding Equivalence Class (FEC); the subsequent packets with the same destination and the same quality of service are assigned to the same FEC; also other packets belonging to different streams can be assigned to the same FEC, in this way aggregating various packets streams to a common path. This common path is called LSP (Label Switched Path) and can be treated by the intermediate nodes as a Tunnel. The intermediate inner nodes have in charge the only forwarding of the packets, and all the incoming packets within the same LSP will be forwarded toward the same direction. By using MPLS processing, the ES system is able to aggregate, at the edge of the MPLS network (ring topology), many mpls packets communications. For more information about MPLS refer to RFC_3031, RFC_3032, RFC_3209, RFC_3270, ITU-T_ Y1311, etc.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-8 Issue 05 February 2010
Introduction
MPLS Technique
............................................................................................................................................................................................................................................................
Table 1-2 Ethernet over MPLS SDH layer stacking 3
NETWORK
2
DATA LINK
any network “packetized" data service ETHERNET MPLS
1
PHYSICAL
SDH
Table 1-3 MPLS over ETHERNET layer stacking 3
NETWORK
any network “packetized" data service
2
DATA LINK
MPLS
1
PHYSICAL
SDH
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-9 Issue 05 February 2010
Introduction
Ethernet Applications
............................................................................................................................................................................................................................................................
Ethernet Applications Figure 1-3
Bridge representation example and relevant FDB table C10
C28 C23
L1
1
L2
2
L3
3 C15
4 B1
C26
L4 L5
5 L6
6 BRIDGE (OMSN+ES)
NOTES: - 1, 2, 3, 4, 5, 6 : ports of the bridge - L1, L2, L3, L4, L5, L6: LANs
Cn
: Computer with its own MAC address
Cn
: new inserted computer
C24
C21
FDB table (Filtering Data Base table) Computer Address MAC-C10 MAC-C15 MAC-C23 MAC-C24 MAC-C26 MAC-C28
Port 1 3 5 6 5 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. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 10 Issue 05 February 2010
Introduction
Ethernet Applications
............................................................................................................................................................................................................................................................
Figure 1-4 VLAN Bridge representation example and relevant FDB table VLAN-C
VLAN-A
VLAN-A
C10
C28
C31
A, C
L1
B
L2
B, A
L3
C15
VLAN-A
1 2
A
4 B1
3
5
C23
C26
L4 L5
A
6
VLAN-B
VLAN-A
A, B
BRIDGE (OMSN+ES)
C15
VLAN-B
L6
C24
C21
VLAN-A
VLAN-A C21 moved
NOTES: - 1, 2, 3, 4, 5, 6 : ports of the bridge - L1, L2, L3, L4, L5, L6: LANs - A, B, C: VLANs
Cn
: Computer with its own MAC address
Cn
: new inserted (or moved) Computer
FDB table (Filtering Data Base table) Computer Address MAC-C10 MAC-C15 MAC-C23 MAC-C24 MAC-C26 MAC-C28 MAC-C31
Port 1 3 5 6 5 4 1
VLAN A B B A A A C
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).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-11 Issue 05 February 2010
Introduction
Ethernet Applications
............................................................................................................................................................................................................................................................
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: Admit All / Admit Only Vlan Tagged 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 frames are accepted by the port 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 8DG15624AAAA 1 - 12 Issue 05 February 2010
Introduction
Ethernet Applications
............................................................................................................................................................................................................................................................
Figure 1-5 Generic VLAN Classification-Identification-Aggregation (example) Classifier
C
Pri3 VLAN#25
ETS InFlow (TD,Pol.) LAN1
L-ETH Port (E-Rate)
C
C
LAN2
LAN3
L-ETH Port (E-Rate)
L-ETH Port (E-Rate)
VLAN#150 Pri7
VLAN#200 Pri5
C
ETS InFlow (TD,Pol.)
ETS OutFlow
ETS InFlow (TD,Pol.)
ETS OutFlow
VLAN#500-700 Pri3 - 6
C
ETS OutFlow
ETS XC
ETS InFlow (TD,Pol.)
R-ETH Port (VCG-Rate)
SDH SONET
ETS OutFlow
R-ETH Port (VCG-Rate)
ETS OutFlow
R-ETH Port (VCG-Rate)
ETS OutFlow
R-ETH Port (VCG-Rate)
VLAN#1000-2000 Pri3 - 6
EOS
EOS
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).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-13 Issue 05 February 2010
Introduction
Ethernet Applications
............................................................................................................................................................................................................................................................
Figure 1-6 SVLAN Registr.
LAN1
SVLAN Registr.
LAN2
Stacked VLAN management (example)
ETS port
ETS port
ETS InFlow
ETS(Prov) OutFlow
ETS InFlow
ETS(Prov) OutFlow
PUSH SVLAN
PUSH SVLAN
POP SVLAN
ETS(Prov) InFlow
SVLAN Registr.
ETH port
SVLAN Registr.
network
POP SVLAN
ETH port
ETS(Prov) InFlow
XC SVLAN Registr.
LAN3
ETS port
ETS InFlow
XC
ETS(Prov) OutFlow
UNI to NNI XC
PUSH SVLAN
POP SVLAN
ETS(Prov) InFlow
Provider or "none" Bridge
Provider or "none" Bridge
NNI to UNI XC
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 One-Step" procedures. PB = Provider Bridge domain. Classification and Identification of the single data flows is possible, as seen in Figure 1-5, (pg. 1-13). 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..
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 14 Issue 05 February 2010
Introduction
Ethernet Applications
............................................................................................................................................................................................................................................................
Figure 1-7 Transparent Mac/Virtual Port-to-Port XC “OneStep" (Example) SONET/SDH Network
S XC Ethernet Data
L-ETH Port (Rate)
R-ETH Port (Rate)
InFlow
OutFlow XC
OutFlow
InFlow 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-15 Issue 05 February 2010
Introduction
Ethernet Applications
............................................................................................................................................................................................................................................................
Figure 1-8
MAC Bridge distribution domain (example) LAN or SDH/ SONET
LAN or SDH/ SONET
LAN or SDH/ SONET
LAN or SDH/ SONET
ETB port (rate)
ETB port (rate)
ETB port (rate)
ETB port (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" crossconnection. This configuration is used for “Point-to-Multipoint", “Multipoint-to-Multipoint", or so called “ELan" applications.
Figure 1-9
Virtual Bridge distribution domain (example)
(rate)
LAN or SDH/ SONET
LAN or SDH/ SONET
LAN or SDH/ SONET
LAN or SDH/ SONET
ETB port (RP)
ETB port (RP)
ETB port (RP)
ETB port (RP)
VLAN Reg
VLAN Reg
VLAN Reg
VLAN 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)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 16 Issue 05 February 2010
Introduction
Ethernet Applications
............................................................................................................................................................................................................................................................
Figure 1-10 Provider Bridge distribution domain (example) LAN or SONET
ETS port
SVID Registr.
UNI to NNI
Classifier (VLAN, Pri)
ETS InFlow (TD, Polic.)
XC
PUSH SVID
SVID Registr.
ETB port (RP, PT)
Provider OutFlow
LAN or SONET
Provider Bridge LAN or SONET
ETS port
SVID Registr.
UNI to NNI ETS OutFlow
XC
POP SVID
SVID distrib. Domain
Provider InFlow (TD0)
SVID Registr.
ETB port (RP, PT)
LAN or SONET
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, in “Connection -> Ethernet Port -> Create ETS XC One Step (MAC & Virtual)” (p. 4-264), provides to create a bidirectional Uni-Nni connection over the same Ets Port. The “S-tag” is related to the outer shim header, while the “V-tag” is related to the inner one. On ETB ports the PCP decoding can be applied on S-tagged frames, for Provider scheduling. 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 users (UNI) connection is accomplished by means of “Connection: Create Xc One-Step" procedure, for classified and differentiated traffic. The “one-step” UNI-NNI XC creates a bidirectional connection over a Port in one single step. The ETS and ETB ports may also be connected, statically and dynamically, by means of the FDB feature (in this case the InFlow/OutFlow/Classifier resources are not used, and the PCP bits are used for scheduling).
Example of end-to-end ETS link creation (“none” Bridge case) Figure 1-11, (pg. 1-19) shows an application example of unidirectional, end-to-end ETS 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. See also the NOTES reported in “Example of MPLS over SDH Tunnelling creation” (p. 1-34). ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-17 Issue 05 February 2010
Introduction
Ethernet Applications
............................................................................................................................................................................................................................................................
•
On the first end (OMSN+ES A):
1. In Transmission context, configuration of the Bridge (in none mode): Transmission -> Bridge Management -> Configure (R)Stp Bridge
set the Bridge Type = none and the Protocol Type 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; AdminStatus = 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 “Connection -> Ethernet Port -> Create ETS XC One Step (MAC & Virtual)” (p. 4-264) and “Connection -> Ethernet Port -> Create ETS XC One Step (Provider)” (p. 4-267); 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. 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 18 Issue 05 February 2010
Introduction
Ethernet Applications
............................................................................................................................................................................................................................................................
Figure 1-11 End-to-End ETS link Example Transport Network
Originating Point
Terminating Point
SDH Network
SDH XC
SDH XC
R-ETH Port (Rate)
R-ETH Port (Rate)
OMSN+ES (A)
OMSN+ES (B)
L-ETH Port (Rate)
Ethernet Data
POP S-VLAN (ColorProf.)
InFlow
(ColorProf.)
(ColorStack)
InFlow
OutFlow
(TD, polic.)
VLAN Classifier
VLAN Classifier (Priority) (VLAN)
POP S-VLAN
POP S-VLAN
ETS XC
(Priority) (VLAN)
L-ETH Port (Rate)
Ethernet Data
POP S-VLAN (ColorStack)
OutFlow
(TD, polic.)
ETS XC
Note: •
Cross-Connections Creations are managed by means of “Create-XC OneStep" procedure.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-19 Issue 05 February 2010
Introduction
MEF (Metro Ethernet Forum) Applications
............................................................................................................................................................................................................................................................
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-13, (pg. 1-23).
•
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-14, (pg. 1-25) (centralized LAN) and Figure 1-15, (pg. 1-26) (distributed LAN).
•
An example of EVPL with Services Multiplexing and differentiated CoS is shown in Figure 1-16, (pg. 1-29).
•
The Bundling service can be achieved in Provider and Virtual Bridge configuration, by registering more VLAN's over one Ethernet Port. 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 Ethernet Port. See EVPL, Figure 1-16, (pg. 1-29).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 20 Issue 05 February 2010
Introduction
MEF (Metro Ethernet Forum) Applications
............................................................................................................................................................................................................................................................
Figure 1-12 MEF-Network application for OMSN+ISA-ES System
Remote Ports (EOS) or Local Ports
B4
OMSN+ES
Ethernet Bridge OMSN+ES MEN
B2 EVC1
Local/ Remote Ethernet Ports
B1
EVC2
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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-21 Issue 05 February 2010
Introduction
Ethernet Private Line (EPL), end to end implementation example
............................................................................................................................................................................................................................................................
Ethernet Private Line (EPL), end to end implementation example Refer to Figure 1-13, (pg. 1-23). For details about the specific configurations here recalled, see their relative paragraphs. All involved ports are in ETS mode, concerning the client layer: see “Transmission -> Ethernet Port/Aggregator -> Substitute Client Layer” (p. 4-153) . •
On the first end (OMSN+ES A):
1. In Transmission context, activation of the desired Local Ethernet Port (L-ETH): Transmission -> Ethernet Port Management -> Configure Ethernet Port
set Promiscuous Mode = enabled; AdminStatus = up 2. In Transmission context, configuration of GFP or LAPS framing on the desired Remote Ethernet Port (R-ETH): Transmission -> Ethernet Port Management -> Substitute Server Layer
3. In Transmission context, activation of the desired Remote Ethernet Port (R-ETH): Transmission -> Ethernet Port Management -> Configure Ethernet Port
set Promiscuous Mode = enabled; AdminStatus = 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, choose the Port->Port option) then follow the procedure described in the relevant paragraph “Connection -> Ethernet Port -> Create Ets Xc One-Step", selecting Connection Type = Bidirectional. 5. Connection into the transport SDH network 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 crossconnected. 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 –
LCAS configuration, if used
–
Bidirectional cross-connection of VC12 to TU12
–
Association of TU12 to AU4
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 22 Issue 05 February 2010
Introduction
Ethernet Private Line (EPL), end to end implementation example
............................................................................................................................................................................................................................................................
– •
Optical fibers connection
On the second end (OMSN+ES B): The same operations as in the first end.
Figure 1-13 EPL application example SONET/SDH Network
STM link Ethernet OMSN+ES (A) Data L-ETH Port
SXC
SXC
R-ETH Port
R-ETH Port
OMSN+ES (B) Ethernet
(E-Rate)
(VCG-Rate)
InFlow
(VCG-Rate)
OutFlow
Data
(E-Rate)
InFlow
XC OutFlow
L-ETH Port
OutFlow XC
InFlow
OutFlow
XC
InFlow 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. This link is EPL (Ethernet Private Line) type (also called point-to-point).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-23 Issue 05 February 2010
Introduction
E-Lan/E-VLan, end to end implementation example
............................................................................................................................................................................................................................................................
E-Lan/E-VLan, end to end implementation example Refer to Figure 1-14, (pg. 1-25) (centralized LAN) or Figure 1-15, (pg. 1-26) (distributed LAN). For details about the specific configurations here recalled, see their relative paragraphs. All involved ports are in ETB mode (except if the Bridge is Provider). In case of Provider Bridge, see next for more information. •
On the first end (OMSN+ES A):
1. In Transmission context, configuration of the Bridge (MAC or Virtual or Provider): Transmission -> Node Management -> Configure Node
set the Bridge Type and the Protocol Type 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 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, configuration of Regenerated Priority mapping on the involved Ports: Transmission -> Ethernet Port Management -> Configure Ethernet Port
select the Regeneration User Priority item 5. In Transmission context, activation of all the involved ETB ports: Transmission -> Ethernet Port Management -> Configure Ethernet Port
set Promiscuous Mode = enabled; AdminStatus = 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
8. 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 > Filtering Data Base” (p. 4-244), selecting Static Unicast Filtering folder. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 24 Issue 05 February 2010
Introduction
E-Lan/E-VLan, end to end implementation example
............................................................................................................................................................................................................................................................
9. Connection into the transport SDH network 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. 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 connections as indicated in the figure.
On the other involved OMSN+ES equipment: Similar operations as in the first equipment
Figure 1-14 Example of E-Lan/E-VLan implementation (1: centralized LAN) OMSN+ES (B) SONET/SDH NETWORK
OMSN+ES (A) Vid 1 LAN or SONET/SDH
SXC
Vid 1,2 Port ETB
Port ETB
Vid 1,2
Vid 1,2
Port ETB
Br.
Port ETB
LAN or SONET/SDH
SXC
OMSN+ES (C) Vid 3
Vid 2 LAN or SONET/SDH
LAN or SONET/SDH
Port ETB
Br.
Vid 3
Vid 3 Port ETB
SXC
Port ETB
SXC
SXC
Vid 1 Port ETB
Vid 3
Port ETB
Br.
Port ETB
LAN or SONET/SDH
OMSN+ES (D) Vid 1 SXC
Port ETB
Vid 1 Br.
Port ETB
LAN or 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-25 Issue 05 February 2010
Introduction
E-Lan/E-VLan, end to end implementation example
............................................................................................................................................................................................................................................................
•
The E-VPL an 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.
• •
Figure 1-15 Example of E-Lan/E-VLan implementation (2: distributed LAN)
V1
ETB Br.
ETB
V1 V2 V3
ETB
V1 V2 V3
SXC
SXC
V1 V2 V3
SXC
SONET/SDH link
V2 V3
ETB Br.
ETB
ETB
V1 V2 V3
SXC
OMSN+ES
Br.
LAN or SONET /SDH
OMSN+ES
V2 V3
ETB
ETB
LAN or SONET /SDH
OMSN+ES
OMSN+ES
LAN or SONET /SDH
V1
ETB Br.
ETB
V1 V2 V3
SXC
SONET/SDH link
ETB
V1 V2 V3
SXC
V1 V2 V3
SXC
ETB V1 V2 V3
SXC
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 26 Issue 05 February 2010
Introduction
E-VPL, end to end implementation example
............................................................................................................................................................................................................................................................
E-VPL, end to end implementation example Refer to Figure 1-16, (pg. 1-29) illustrating an EVPL example with Service Multiplexing and Differentiated Class of Services. 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 (Provider): Transmission -> Node Management -> Configuration
set the Bridge Type and the Protocol Type 2. In Transmission context, substitution of relevant ports from ETS to ETB mode: Transmission -> Ethernet Port Management -> Substitute Client Layer
set ETS -> ETB Layer 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, configuration of Regenerated Priority (if used) on the involved Ports: Transmission -> Ethernet Port Management -> Configure Ethernet Port
select the Regeneration User Priority item 5. In Transmission context, activation of all the involved ETB ports: Transmission -> Ethernet Port Management -> Configure Ethernet Port
set Promiscuous Mode = enabled; AdminStatus = 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
8. 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 > Filtering Data Base” (p. 4-244), 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 “Connection -> Ethernet Port -> Create ETS XC One Step (Provider)” (p. 4-267). ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-27 Issue 05 February 2010
Introduction
E-VPL, end to end implementation example
............................................................................................................................................................................................................................................................
10. Connection into the transport SDH network 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. 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 28 Issue 05 February 2010
LAN or SONET /SDH
XC
XC
P-IF = Provider InFlow
TD0 = Traffic Descriptor "null"
RSVid1
STM OC link
STM OC link
STM OC link
SXC = SONET/SDH XC
PT = Protocol Type option
(RP, PT)
ETB port
(RP, PT)
SXC
(RP, PT)
ETB port
RSVid3
OMSN+ES (D)
SXC
ETB port
RSVid2
OMSN+ES (C)
RP = Regenerated Priority option
Pol = Policing
(f)
(RP, PT)
ETB port SXC
RSVid3
(e)
(RP, PT)
SXC
ETB port SXC
RSVid2
(d)
(RP, PT)
ETB port
SXC
RSVid1
OMSN+ES (C)
EVPLapplication example with Services Multiplexing and differentiated CoS
P-OF = Provider OutFlow
SVID 3 distrib. Domain
dd = Distribution Domain
-SVid3
+SVid3
SVID 2 distrib. Domain
E-OF = ETS OutFlow
(TD0)
P-IF
P-OF
-SVid2
+SVid2
SVID 1 distrib. Domain
E-IF = ETS InFlow
XC
NNI to UNI E-OF
P-IF (TD0)
UNI to NNI
XC
P-OF
-SVid1
+SVid1
Pr.Br = Provider Bridge
(c)
(TDc, Pol. c)
E-IF
(TD0)
P-IF
P-OF
UNI to NNI
XC
NNI to UNI E-OF
Classifier (VLAN7, Pri 6)
(b)
(TDb, Pol. b)
E-IF
XC
UNI to NNI
NNI to UNI E-OF
Classifier (VLAN6, Pri 3)
(a)
(TDa, Pol. a)
E-IF
Classifier (VLAN1.5, Pri 3..6)
RSVid1,2,3
Provider Bridge
RSVid = S-Vlan Registration
ETS port
OMSN+ES (A)
SONET/SDH Network
Pr. Br. dd3
Pr. Br. dd2
Pr. Br. dd1
XC
NNI to UNI (TD0)
P-IF
Classifier
E-OF
ETS port
P-IF
XC
NNI to UNI (TD0)
P-IF
RSVid3
Classifier
E-OF
Pol. b)
Pol. c)
UNI to NNI (VLAN7, Pri 6) +SVid3 E-IF P-OF XC (TDc,
-SVid3
Classifier
E-OF
RSVid2
UNI to NNI (VLAN6, Pri 3) E-IF P-OF XC (TDb,
XC
NNI to UNI (TD0) +SVid2
-SVid2
Pol. a)
ETS port
ETS port
UNI to NNI (VLAN5, Pri 3..6) +SVid1 E-IF P-OF XC (TDa,
-SVid1
RSVid1
Introduction E-VPL, end to end implementation example
............................................................................................................................................................................................................................................................
Figure 1-16 EVPL implementation example
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-29 Issue 05 February 2010
Introduction
E-VPL, end to end implementation example
............................................................................................................................................................................................................................................................
Note: • • • • • • • • • • • • • • • •
about Figure 1-16, (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 “Connection -> Ethernet Port -> Create ETS XC One Step (MAC & Virtual)” (p. 4-264)).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 30 Issue 05 February 2010
Introduction
MPLS Applications
............................................................................................................................................................................................................................................................
MPLS Applications Figure 1-17 MPLS-Network application for ISA-ES System
Remote Ports MPLS over SONET/SDH
B4
OMSN+ES
LSR OMSN+ES SONET/SDH NETWORK
B2
LSP1 Local/ Remote Ethernet Ports
B1
LSP2
OMSN+ES
B3
OMSN+ES
Note: • •
LSP (Label Switched Path) is a connection between two or more MPLS enabled Network Elements (such as OMSN+ISA-ES). The Bridge is configured as “none” type.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-31 Issue 05 February 2010
Introduction
MPLS Applications
............................................................................................................................................................................................................................................................
Figure 1-18 Generic MPLS aggregation scheme (Tunnelling) Classifier
InFlow
ETS XC OutFlow
VLAN#1
C ETS Flow Local or Remote Ethernet
Inner Tunnel (label_1)
C VLAN#i
ETH Port VLAN#m
C ETS Flow
Inner Tunnel (label_#)
ETS Flow
Inner Tunnel (label_n)
ETS Flow
Inner Tunnel (label_1)
OUTER TUNNEL (label_1)
MPLS Port
PPP Port
MPLS over SONET/SDH
C VLAN#n
Local or Remote Ethernet
Local or Remote Ethernet
Local or Remote Ethernet
ETH Port
C
ETH Port
C
VLAN#1...n
VLAN#1...n
OUTER TUNNEL (label_n) ETH Port
C
VLAN#1...n
ETS Flow
Inner Tunnel (label_n)
Generic classification and aggregation scheme at an originating edge node (Head)
Note: • • •
At the terminating edge node the scheme is specular. At the intermediate MPLS nodes, only the outer tunnel is processed. The VLAN links may be specified individually or by a range, and may be addressed to a single or more ETSFlows.
MPLS Tunnel: Labelling and Bandwidth Matching The following notes are referred to the MPLS Tunnelling scheme reported on Figure 1-19, (pg. 1-34). About MPLS Labelling: 1. The Labels assigned at the Outer Tunnel HEAD points must be equal to the labels assigned at the Outer_TRANSIT and Outer_TAIL points. 2. Label_a1 and Label_b1 may be different in the TRANSIT Tunnel, but necessarily: – Transit_Label_a1 must be equal to the Head_Label_a1 –
Transit_Label_b1 must be equal to the Tail_Label_b1.
3. The Labels assigned at the Inner Tunnel HEAD points must be equal to the labels assigned at the TAIL points; e.g.: Head_label_1 = Tail_label_1, Head_label_2 = Tail_label_2, ... and so on. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 32 Issue 05 February 2010
Introduction
MPLS Applications
............................................................................................................................................................................................................................................................
About Bandwidth and Traffic Descriptors Matching: the creation of the Traffic Descriptors (TD) is described in: “Configuration -> Traffic Descriptor -> ETS Traffic Descriptor” (p. 4-56) (ETS-TD), “Prioritization, S-VLAN, Policing, Color Profile, Scheduling” (p. 4-60) “Configuration -> Traffic Descriptor -> MPLS Traffic Descriptor” (p. 4-67) (MPLS-TD). The Traffic Descriptors (TD) must be coherent in all the path, for instance: At the HEAD: the Sum of (InFlow_ETS_CIR/PIR) < Ethernet Port Rate 1. InFlow_ETS_CIR/PIR < Inner Tunnel_MPLS_CIR/PIR; further, the Traffic Types of the two TD should be consistent, i.e.: If ETS Traffic = RS --> Inner Tunnel Traffic = AF If ETS Traffic = GS --> Inner Tunnel Traffic = EF If ETS Traffic = BE --> Inner Tunnel Traffic = DE 2. Sum of (Inner Tunnel_MPLS_CIR/PIR) < Outer Tunnel_MPLS_CIR/PIR; further, the Traffic Types of the two tunnels' TD should be consistent, with the following restrictions: If Outer Tunnel Traffic = AF --> Inner Tunnel Traffic = AF or EF or DE If Outer Tunnel Traffic = EF --> Inner Tunnel Traffic = EF or DE If Outer Tunnel Traffic = DE --> Inner Tunnel Traffic = DE 3. 4. 5. 6.
Sum of (Outer Tunnel_MPLS_CIR/PIR) < MPLS_Port Rate MPLS_Port Rate < PPP_Port Rate PPP_Port Rate < SDH_VC rate Further, the Sum of (InFlow_ETS_CIR/PIR) < Ethernet Port Rate
At the TRANSIT and at the TAIL, the bandwidth matching should be carried out in the same way. ETS traffic:
RS = Regulated Service; GS = Guaranteed Service; BE = Best Effort
MPLS traffic: AF = Assured Forwarding; EF = Expedited Forwarding; DE = Default Behavior The consistence of the rules above reported (about Bandwidth and Traffic Descriptors Matching) are checked by the CAC (Connection Admission Control), that does not permit the establishment of the connection, if these rules are not respected. Similar considerations have to be taken into account along the all pathway, at TRANSIT and HEAD points.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-33 Issue 05 February 2010
Introduction
MPLS Applications
............................................................................................................................................................................................................................................................
Figure 1-19 MPLS Tunnelling scheme example Rate ETH Port
ETS InFlow
ETS InFlow
MPLS TD
MPLS TD
ETS TD
ETS XC
ETS XC
ETS OutFlow
Inner Tunnel (label_1)
ETS OutFlow
Inner Tunnel (label_n)
HEAD OUTER TUNNEL (label_a1)
Rate SONET/ SDH Port
PPP Port
MPLS Port
SONET/ SDH Port
PPP Port
SONET/ SDH VC
MPLS Port
TAIL OUTER TUNNEL (label_b1)
Rate
MPLS Port
PPP Port
Rate
SONET/SDH network
TRANSIT OUTER TUNNEL (label_a1)
SONET/ SDH VC
Rate
SONET/ SDH VC
TRANSIT OUTER TUNNEL (label_b1)
SONET/SDH network
SONET/ SDH VC
Inner Tunnel (label_1)
ETS InFlow
Inner Tunnel (label_n)
ETS InFlow
SONET/ SDH Port
MPLS Port
PPP Port
SONET/ SDH Port
ETS XC
ETS XC
ETS OutFlow
ETH Port
ETS OutFlow
Note:
see notes on “MPLS Tunnel: Labelling and Bandwidth Matching” (p. 1-32). Example of MPLS over SDH Tunnelling creation The following Figure 1-20, (pg. 1-40) reports an example of MPLS Tunnelling. It contains: an originating point (head), where an ethernet flow enters the Ethernet Port, then it is classified and inserted into inner and outer MPLS Tunnels, then mapped over an SDH container and thus transported over the SDH network; a transit point, where the data
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 34 Issue 05 February 2010
Introduction
MPLS Applications
............................................................................................................................................................................................................................................................
flow is dropped up to the outer tunnel and then inserted again into the SDH network; a terminating point (tail), where the ethernet flow is delivered to the destination Ethernet Port.
WARNING The Remote Ethernet Ports and PPP Ports are to be configured at the SDH side, before their usage, associating them with SDH containers; the choice of the SDH containers should be done according to the rate of the total forecast mpls/ethernet traffic; (SDH-CT option: Configuration -> ISA Port Configuration); see OMSN Operator's Handbook listed in Table 1, (pg. 1-xxiv) for details about SDH configuration and connection. Once a port (PPP Port or ETH Port) is associated to an SDH container, its bandwidth is automatically fixed by the system to the rate of the SDH container. The correspondence of Ports numbering/denomination between ES-CT side and SDH-CT side is reported in “Ethernet Ports denomination and numbering” (p. 4-55).
WARNING The example reported is referred to unidirectional link, since the ETS/MPLS resources are unidirectional (except Ethernet Ports, that can be bidirectional). This means that all the involved ETS InFlows must have the parameter Flow Type set to UnicastNoAutolearn (see “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111)). The case of “multicast" connection is not reported in this example, but can be created in the same way, after setting the parameter Flow Type to multicastOptionA (see “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111)). If a bidirectional link is to be established, then a duplication of all the ETS/MPLS resources, towards the opposite direction, is necessary, creating a couple of OutFlow and InFlow for each data-flow, and so on.
WARNING Only one “child" is considered in this example, but the user can add more resources “children", for instance: more than one Inner Tunnel into an Outer Tunnel; more classifiers into an InFlow; more “InFlows" or “outFlows" on an Ethernet Port (local or remote); with the following restrictions: only one InFlow/OutFlow into an Inner Tunnel; only one InFlow/OutFlow into an Outer Tunnel used for MPLS -over-Ethernet; only one MPLS Port into a PPP Port or Local ETH Port.
WARNING For Labelling and Traffic Descriptors associations see “MPLS Tunnel: Labelling and Bandwidth Matching” (p. 1-32). ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-35 Issue 05 February 2010
Introduction
MPLS Applications
............................................................................................................................................................................................................................................................
WARNING The applications here reported are not possible in Bridge modality, i.e. they are possible only if the Bridge Type is set to none. 1. HEAD creation, (on OMSN+ES A) a. In Transmission context, configuration of the Bridge (in none mode): Transmission -> ISA Management -> Configure ISA -> Bridge Management
set the Bridge Type = none and the Protocol Type = RSTP b. Creation of the required Traffic Descriptors (TD) for MPLS side and Ethernet side, with the appropriate CIR/PIR and CBS/PBS values for both sides: Configuration -> Traffic Descriptor-> ETS Traffic Descriptor / MPLS Traffic Descriptor
c. In Transmission context, configuration of GFP or LAPS framing on the involved Remote Ethernet Ports: Transmission -> Ethernet Port Management -> Substitute Server Layer
d. In Transmission context, activation of the desired originating Ethernet Port: Transmission -> Ethernet Port Management -> Configure Ethernet Port
set Promiscuous Mode = enabled; AdminStatus = up; the Asap Name e. In Transmission context, creation of a PPP port: select a “down" remote ETH Port: Transmission -> Ethernet Port Management -> Substitute Ethernet-PPP
Select the previous PPP Port and set Admin Status = up: Transmission ->PPP Port Management -> Configure PPP Port
Set the Bandwidth (bps) (SDH VCG rate) in the TP/GFP (or LAPS) SDH Configuration Sector f. In Transmission context, configuration of the MPLS Port contained into the previous PPP port Transmission -> MPLS Port Management -> Configure MPLS Port
set the parameters Admin Status = up, and the appropriate Effective Line Rate g. In Connection context, creation of a Head Outer Tunnel: Select the “Main" MPLS Tunnel on the resources Tree Connection -> MPLS Tunnel Management -> Create Outer Head Tunnel
set Client Type = mpls; associate, to this tunnel, the MPLS Port of point (e) in the field MPLS Port; assign the appropriate Traffic Descriptor (according to the list) and Label (according to the Label Range field).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 36 Issue 05 February 2010
Introduction
MPLS Applications
............................................................................................................................................................................................................................................................
h. In Connection context, creation of a Head Inner Tunnel inside the previous Outer Tunnel: Select the previous created Outer Tunnel Connection -> Outer MPLS Tunnel-> Create Inner MPLS Tunnel
assign, to this tunnel, the appropriate Traffic Descriptor and Label i. Cross-Connections creation, by means of the option: Connection -> Ethernet Port -> Create Ets XC One-Step
This operation is described in “Connection -> Ethernet Port -> Create ETS XC One Step (MAC & Virtual)” (p. 4-264); it permits to create all the necessary resources (InFlows/OutFlows, Classifiers, VLAN Management, etc.) j. 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 OMSN Operator's Handbook listed in Table 1, (pg. 1-xxiv) 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.
Connection into the transport SDH network The created MPLS tunnels are passed through the SDH network; the involved PPP Ports are associated to suitable SDH-VC's (VC12 or VC3 or VC4) and then crossconnected. These operations are done on SDH-CT (see OMSN Operator's Handbook listed in Table 1, (pg. 1-xxiv) for details about SDH configuration and connection). Example (VC12 case): k. incoming PPP Port association to a VC12, or to a group of VC12 (VC12-xv), in case of VCG link l. LCAS configuration, if used m. cross-connection of VC12 to a TU12 n. association of this TU12 to an AU4 o. association of TU12 to VC4, and VC4 connection towards OMSN+ES B.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-37 Issue 05 February 2010
Introduction
MPLS Applications
............................................................................................................................................................................................................................................................
2. TRANSIT creation into an intermediate MPLS network, (on OMSN+ES B) The transit is carried out at the intermediate nodes of an MPLS network, where the Outer Tunnel can be passed-through as a whole, without de-assembling the contained Inner Tunnels. The transit tunnel is used in nodes where some outer tunnels of a port are to be terminated or originated and somebody else are passed-through. a. In Transmission context, creation and activation of a PPP port: Transmission -> Ethernet Port Management -> Substitute Ethernet-PPP
Select the previous PPP Port and set Admin Status = up: Transmission -> PPP Port Management -> Configure PPP Port
b. In Transmission context, configuration of the MPLS Port contained into the previous PPP port, setting the parameter Admin Status = up: Transmission -> MPLS Port Management -> Configure MPLS Port
c. In Transmission context, creation and activation of a PPP port: Transmission -> Ethernet Port Management -> Substitute Ethernet-PPP
Select the previous PPP Port and set Admin Status = up d. In Transmission context, configuration of the MPLS Port contained into the previous PPP port, setting the parameter Admin Status = up, and the appropriate Effective Line Rate: Transmission -> MPLS Port Management -> Configure MPLS Port
e. In Connection context, creation of a Transit Outer Tunnel: Select the Main MPLS Tunnel Connection -> MPLS Tunnel Management -> Create Outer Transit Tunnel
–
associate the appropriate Traffic Descriptor;
–
associate, at the InSegment side of this tunnel, the MPLS Port of point (b) in the field MPLS Port; assign, in the field Label Selected, the same label as assigned in point (1)-(g); set the Policing Mode.
– associate, at the OutSegment side of this tunnel, the MPLS Port of point (d) in the field MPLS Port; assign, in the field Label Selected, the same label as the previous one or a new one. Connection into the transport SDH network After an MPLS Transit point, the data link is continued by passing again through the SDH network. The SDH connections operations are carried out as described in point (b), with STM connections towards OMSN+ES A and OMSN+ES C.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 38 Issue 05 February 2010
Introduction
MPLS Applications
............................................................................................................................................................................................................................................................
3. TAIL creation, (on OMSN+ES C) a. In Transmission context, creation and activation of a PPP port: select a remote ETH Port, Transmission -> Ethernet Port Management -> Substitute Ethernet-PPP
Select the previous PPP Port and set Admin Status = up: Transmission -> PPP Port Management -> Configure PPP Port
b. In Transmission context, configuration of the MPLS Port contained into the previous PPP port, setting the parameter Admin Status = up, and the appropriate Effective Line Rate: Transmission -> MPLS Port Management -> Configure MPLS Port
c. In Connection context, creation of a Tail Outer Tunnel: Select the “Main" MPLS Tunnel Connection -> MPLS Tunnel Management -> Create Outer Tail Tunnel
set Client Type = mpls; assign, to this tunnel, the appropriate Traffic Descriptor and associate the MPLS Port of point (b) in the field MPLS Port; assign a label: the label must be the same as assigned in point (2)-(b) at the OutSegment side; then set the Policing Mode. d. In Connection context, creation of a Tail Inner Tunnel inside the previous Outer Tunnel: Select the previous created Outer Tunnel Connection -> Outer MPLS Tunnel -> Create Inner MPLS Tunnel
assign, to this tunnel, the appropriate Traffic Descriptor and a label: the label must be the same as assigned in point (1)-(h) at the OutSegment side; then set the Policing Mode. e. In Transmission context, activation of the desired destination Ethernet Port: Transmission -> Ethernet Port Management -> Configure Ethernet Port
set Promiscuous Mode = enabled; Admin Status = up f. Cross-Connections creation, by means of the option: Connection -> Ethernet Port -> Create Ets XC One-Step
This operation is described in “Connection -> Inner (Outer) MPLS Tunnel -> Create ETS XC One Step (Tunnel-Tail)” (p. 4-260); it permits to create all the necessary resources (InFlows/OutFlows, Classifiers, VLAN Management, etc.) Connection into the transport SDH network The SDH connections operations are carried out as described in point (), with STM connections towards OMSN+ES B.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-39 Issue 05 February 2010
Introduction
MPLS Applications
............................................................................................................................................................................................................................................................
Figure 1-20 MPLS Tunnelling over SONET/SDH Example Originating (HEAD) Point
Transport Network
Transit Point
SONET/SDH Network
S-XC
Terminating (TAIL) Point
Transport Network
SONET/SDH Network
S-XC
S-XC
S-XC
OMSN+ES (A)
OMSN+ES (C)
ETH Port (Rate)
Ethernet Data
PPP Port (Rate) MPLS Port
PPP Port (Rate) MPLS Port
PPP Port (Rate) MPLS Port
PPP Port (Rate) MPLS Port
HEAD Outer Tunnel
TRANSIT Outer Tunnel
TAIL Outer Tunnel
(Label+TD)
(Label+TD)
(Label+TD)
HEAD Inner Tunnel
POP S-VLAN
OMSN+ES (B)
(Label+TD)
ETH Port (Rate)
TAIL Inner Tunnel
PUSH S-VLAN
(Label+TD)
(ColorProf.)
(ColorStack)
InFlow
OutFlow
(TD, polic.)
VLAN Classifier (Priority) (VLAN)
Ethernet Data
ETS XC
InFlow
OutFlow
(TD, polic.)
ETS XC
S-XC = SONET/SDH Cross-Connection
Example of MPLS over Ethernet Tunnelling creation Figure 1-21, (pg. 1-42) shows an application example of “MPLS over Ethernet". In this case the resources structure, at the network edge (originating and/or terminating points), changes as below indicated. The example illustrates a case where MPLS over Ethernet is used either at the ingress point and at the egress point, but in reality it may also be used in only one point. This paragraph describes only the construction of the ingress and egress ethernet points; the rest of the tunnelling procedure is the same as explained in previous “Example of MPLS over SDH Tunnelling creation” (p. 1-34). Note:
In this case the DA (Destination Address) field of the Ethernet frame is advisable to be set to all 1 (bin) (broadcast), by the user terminal. Important!
See also the NOTES reported in “Example of MPLS over SDH Tunnelling creation” (p. 1-34).
1. MPLS over Ethernet “ingress" a. In Transmission context, activation of the desired originating local Ethernet Port: Transmission -> Ethernet Port Management -> Configure Ethernet Port
set Promiscuous Mode = disabled; AdminStatus = up; the Asap Name
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 40 Issue 05 February 2010
Introduction
MPLS Applications
............................................................................................................................................................................................................................................................
b. In Transmission context, configuration of the MPLS Port contained into the previous local ethernet port, setting the parameter Admin Status = up, and the appropriate Effective Line Rate: Transmission -> MPLS Port Management -> Configure MPLS Port
c. In Connection context, creation of a Tail Outer Tunnel: Select the “Main" MPLS Tunnel Connection -> MPLS Tunnel Management -> Create Outer Tail Tunnel
set Client Type = ethernet; assign, to this tunnel, the appropriate Traffic Descriptor and associate the MPLS Port of point (b) in the field MPLS Port; assign a label: the label must be the same assigned by the ethernet terminal equipment; then set the Policing Mode. d. From this step on, the procedure can be completed continuing in the same way as from step (1)-(c), (head creation) in previous “Example of MPLS over SDH Tunnelling creation” (p. 1-34). 2. MPLS over Ethernet “egress" a. In Transmission context, activation of the desired terminating local Ethernet Port: Transmission -> Ethernet Port Management -> Configure Ethernet Port
set Promiscuous Mode = disabled; AdminStatus = up; the Asap Name b. In Transmission context, configuration of the MPLS Port contained into the previous local ethernet port, setting the parameter Admin Status = up, and the appropriate Effective Line Rate: Transmission -> MPLS Port Management -> Configure MPLS Port
c. In Connection context, creation of a Head Outer Tunnel: Select the “Main" MPLS Tunnel Connection -> MPLS Tunnel Management -> Create Outer Head Tunnel
set Client Type = ethernet; assign, to this tunnel, the appropriate Traffic Descriptor and associate the MPLS Port of point (b) in the field MPLS Port; assign a label: the label must be the same assigned by the ethernet terminal equipment; then set the Policing Mode. d. From this step on, the procedure can be completed continuing in the same way as described in previous “Example of MPLS over SDH Tunnelling creation” (p. 1-34), part (3) (tail creation), but skipping the point (e).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-41 Issue 05 February 2010
Introduction
MPLS Applications
............................................................................................................................................................................................................................................................
Figure 1-21 MPLS tunnelling over Ethernet structure
Originating Point
Transport Network
Transit Point
Transport Network
SONET/SDH Network
S-XC
Terminating Point
SONET/SDH Network
S-XC
S-XC
S-XC
OMSN+ES (A) Ethernet Data MPLS over Ethernet
OMSN+ES (C)
ETH Port (Rate)
PPP Port (Rate) MPLS Port
TAIL Outer Tunnel
PPP Port (Rate) MPLS Port
PPP Port (Rate) MPLS Port
PPP Port (Rate) MPLS Port
HEAD Outer Tunnel
TRANSIT Outer Tunnel
TAIL Outer Tunnel
(Label+TD)
(Label+TD)
(Label+TD)
(Label+TD)
HEAD Inner Tunnel (Label+TD)
InFlow
OutFlow
(TD, polic.)
ETS XC
OMSN+ES (B)
ETH Port (Rate)
HEAD Outer Tunnel
Ethernet Data MPLS over Ethernet
(Label+TD)
TAIL Inner Tunnel (Label+TD)
InFlow
OutFlow
(TD, polic.)
ETS XC
S-XC = SONET/SDH Cross-Connection
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 42 Issue 05 February 2010
Introduction
Protocols
............................................................................................................................................................................................................................................................
Protocols Data frames
IPG ....
• • • •
Preamble (7 Bytes)
SFD
Figure 1-22 Ethernet Packet format Ethernet Frame (64 to "maxFrame" Bytes)
(1)
IPG ....
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 = 1518 bytes if the frame is “untagged"
–
MTU/MRU = 1600 bytes for NNI interface
–
MTU/MRU = 1574 bytes for UNI interface
Jumbo Frame (JF): frames with length greater than 1574 (UNI) or 1600 (NNI): –
JF-MTU/MRU = 9600 bytes, tagged;
–
JF-MTU/MRU = 9600 bytes, tagged/untagged
(7)
DA
SA
(6)
(6)
(1)
L/T
Preamble
FS
Figure 1-23 Ethernet packet and MAC frame format Data + Pad
FCS
(46 to n)
(4)
(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-32)) 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 8DG15624AAAA 1-43 Issue 05 February 2010
Introduction
Protocols
............................................................................................................................................................................................................................................................
Figure 1-24 Ethernet “Q-Tagged" MAC 802.3 frame format
SA
(6)
(6)
(1)
• • • •
L/T
DA
TCI
(7)
1Q
Preamble
FS
Q-TAG
(2)
(2)
(2)
Data
Pad
FCS
(0 to n)
(42 to 0)
(4)
PRE: preamble; FS: Frame Start; DA: Destination Addr.; SA: Source Addr. 1Q: “Protocol Type" 802.1Q field (a constant fixed value = hex“0x8100") TCI : Tag Control Information = (3 bits: user priority 802.1p) + (1 bit: CFI) + (12 bits: 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. •
n: max number of bytes contained in the data field, depending from the MTU value (see Figure 1-23, (pg. 1-43))
Figure 1-25 TCI Field format (802.1Q VLAN Tag) 0 0
1 UP
• • • •
•
2
3 C
4
5
6
7
8
9
1 0
1
2
3
4
5
VID
UP: User Priority (3 bits) C: CFI, Canonical Field Identifier (1 bit) VID: VLAN Identifier (12 bits) 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’t Care"; in this case, all ethernet frames will be forwarded, either tagged or untagged.
Priority: to define the ethernet priority level; possible values:
Note: This field is settable only if, in the relative InFlow, the Classification Mode has been set to “priority” pri000 , pri010 , don't Care , 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’t Care" means that all frames will be forwarded, either tagged or untagged
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 44 Issue 05 February 2010
Introduction
Protocols
............................................................................................................................................................................................................................................................
Figure 1-26 Ethernet “Stacked VLAN" frame format
(6)
(2)
• • • • • •
(2)
L/T
SA
(6)
TCI
DA
(1)
1Q
(7)
TCIP
FS
Preamble
Q-TAG 1QP
S-TAG
(2)
(2)
(2)
Data
Pad
FCS
(0 to n)
(38 to 0)
(4)
PRE: preamble; FS: Frame Start; DA: Destination Addr.; SA: Source Addr. 1Q: “Protocol Type" (PT) 802.1Q field (default value = hex“0x8100") TCI : “Tag Control Information" = (3 bits: user priority 802.1p) + (1 bit: CFI) + (12 bits: VLAN identifier 802.1q); [CFI: Canonical Field Id.] L/T: MAC client Length/Type 1QP: 2 bytes “provider-Protocol Type", 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) + (1 bit: CFI) + (12 bits: 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. •
n: max number of bytes contained in the data field, depending from the MTU value (see Figure 1-23, (pg. 1-43)).
FS
Preamble (7)
DA
SA
(6)
(6)
(1)
• •
L/T
Figure 1-27 Ethernet frame format for “MPLS over Ethernet" MPLS label
(2)
(4)
Data
Pad
FCS
(0 to n)
(42 to 0)
(4)
PRE: preamble; FS: Frame Start; DA: Destination Addr.; SA: Source Addr. 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. •
n: max number of bytes contained in the data field, depending from the MTU value (see Figure 1-23, (pg. 1-43))
Figure 1-28 MPLS label format 0 0
1
2
3
4
5
6
7
8
9
1 0
Label
• • • •
1
2
3
4
5
6
7
8
9
2 0
1 Exp
2
3 S
4
5
6
7
8
9
3 0
1
TTL
Label: Label Value (20 bits) Exp: Experimental (3 bits) S: Bottom of Stack (1 bit) TTL: Time To Live (8 bits)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-45 Issue 05 February 2010
Introduction
Protocols
............................................................................................................................................................................................................................................................
Figure 1-29 GFP Framing (from G.7041/Y.1303) 1 2 3 4
octect transmission order
4
GFP Core Header
GFP Payload Area
4 to 65535 octets
n octet
1 bit
2
3
4
5
6
7
8
bit transmission order
GFP Frame size and transmission order
GFP Core Header
16-bit Payload length indicator
2 bytes
cHEC (CRC-16)
2 bytes
Payload headers (4-64 bytes)
GFP Payload Area
X = 4 to 64 bytes
Client payload information field (Ethernet frame)
Optional payload FCS (CRC-32)
N= 0 to 65535-X bytes
4 bytes
Fields constituting a GFP client frame
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 46 Issue 05 February 2010
Introduction
Protocols
............................................................................................................................................................................................................................................................
Figure 1-30 Ethernet encapsulation into GFP frame (from G.7041/Y.1303) Ethernet MAC Frame
GFP Frame Octets
Preamble Start of frame delimiter Destination Address (DA) Source Address (SA) Length Type MAC client data PAD Frame Check Sequence (FCS)
7 1 6 6 2
4 Octets
1
2
3
4
5
6
7
PLI cHEC Type tHEC GFP Extension Header
2 2 2 2 0-60
GFP Payload
8
1
2
3
4
5
6
7
8
Bits
Figure 1-31 Ethernet/LAPS encapsulation (ITU-T X.86) nr. of bytes
LAPS Frame nr. of bytes
Ethernet Frame 7 1 6 6 2 46 to 1500 4
Preamble Start of Frame Delimiter Destination Address (DA) Source Address (SA) Length/Type Client data PAD FCS
0-60
Flag (0x7E) Address (0x04 Control (0x03) 1st byte of SAPI (0xFE) 2nd byte of SAPI (0x01) Destination Address (DA) Source Address (SA) Length/Type Client data PAD FCS FCS of LAPS Flag (0x7E)
1 1 1 1 1 Ethernet frame
4 1
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-47 Issue 05 February 2010
Introduction
Protocols
............................................................................................................................................................................................................................................................
Figure 1-32 Ethernet (and MPLS over Ethernet) Framing (Local Ethernet Port) DA SA L/T
P-VLAN
Ethernet payload
FCS
C-VLAN
S-VLAN management opportunity
DA SA
S-VLAN
L/T
Ethernet payload
FCS
Ethernet frame
Ethernet MAU (E, FE, GbE)
PRE FS
Ethernet frame
Ethernet Packet
Note: • •
P-VLAN = Provider VLAN C-VLAN = Customer VLAN
Figure 1-33 Ethernet over SDH Framing (Remote Ethernet Port) Ethernet Packet Ethernet MAU (E, FE, GbE)
P-VLAN
PRE FS
DA
SA L/T
DA
SA L/T
DA
SA
FCS
Ethernet payload
FCS
C-VLAN
S-VLAN management opportunity
S-VLAN L/T
Ethernet payload
FCS
Ethernet frame
GFP or LAPS
Header
Ethernet frame
FCS
EOS Frame SDH payload VC-4 or VC-3 or VC-12 frame
POH
SDH payload
Note: • • •
The FCS on GFP or LAPS is optionally included. P-VLAN = Provider VLAN C-VLAN = Customer VLAN
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 48 Issue 05 February 2010
Introduction
Protocols
............................................................................................................................................................................................................................................................
Figure 1-34 Ethernet over MPLS over SDH Framing (MPLS Port) Ethernet MAU PRE FS DA SA L/T
Ethernet Payload
FCS
DA SA L/T
Ethernet Payload
FCS
Ethernet Packet
MPLS
Label Label 1 2
Ethernet Packet
Labelled Packet (MPLS)
PPP
HDLC
MPLS packet
PPP Header
Flag Addr Control
PPP frame
PPP PAD
FCS
HDLC frame SDH VC4 or VC3 or VC12 frame
POH
SDH payload
Notes: P-VLAN = Provider VLAN C-VLAN = Customer VLAN
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-49 Issue 05 February 2010
Introduction
Protocols
............................................................................................................................................................................................................................................................
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-4 L2 Control Protocols MAC Address 01-80-C2-00-00-00 01-80-C2-00-00-01 01-80-C2-00-00-02 01-80-C2-00-00-03 01-80-C2-00-00-04 01-80-C2-00-00-05 01-80-C2-00-00-06 01-80-C2-00-00-07 01-80-C2-00-00-08 01-80-C2-00-00-09 01-80-C2-00-00-0A 01-80-C2-00-00-0B 01-80-C2-00-00-0C 01-80-C2-00-00-0D 01-80-C2-00-00-0E
Protocol Description Customer BPDU (STP, RSTP, MSTP) (see “Customer BPDU” (p. 1-51)) 802.3 Pause Frames (see Note: ) Slow Protocols (see “Slow Protocols” (p. 1-51)) 802.1X PAE (see “802_1X” (p. 1-52)) Reserved for future MAC applications Reserved for future Bridge operations Provider BPDU (STP, RSTP, MSTP) Reserved for future Bridge operations Reserved for future Provider Bridge operations Reserved for Provider GVRP (see “Provider GVRP” (p. 1-53)) Reserved for future Customer Bridge operations
01-80-C2-00-00-0F 01-80-C2-00-00-10 01-80-C2-00-00-20 01-80-C2-00-00-21 01-80-C2-00-00-22
Bridge Management “Bridge management” (p. 1-52) Customer GMRP (see “Customer GMRP” (p. 1-53)) Customer GVRP
.....
Reserved for future GARP applications (see “Customer GARP” (p. 1-54))
01-80-C2-00-00-2F 01-00-5e-00-00-12
MAC Destination Address for VRRP packets (not available in current 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). ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 50 Issue 05 February 2010
Introduction
Protocols
............................................................................................................................................................................................................................................................
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-5. 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-5 IEEE 802.3 Slow Protocols MAC Address 01-80-C2-00-00-02 01-80-C2-00-00-02 01-80-C2-00-00-02 01-80-C2-00-00-02
EtherType Sub-type 0x01 0x8809 0x02 0x8809 0x03 0x04
Protocol Description
0x8809
…
Reserved for future 802.3 Slow Protocols
0x8809
0x0A Other
Illegal values (see Note:
802.3 LACP and LAMP 802.3 EFM OAM
)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-51 Issue 05 February 2010
Introduction
Protocols
............................................................................................................................................................................................................................................................
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 mediaaccess algorithms. Examples of popular link layer protocols include Ethernet, Token Ring, and FDDI. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 52 Issue 05 February 2010
Introduction
Protocols
............................................................................................................................................................................................................................................................
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 8DG15624AAAA 1-53 Issue 05 February 2010
Introduction
Protocols
............................................................................................................................................................................................................................................................
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 54 Issue 05 February 2010
Introduction
STP functionality (Spanning Tree Protocol)
............................................................................................................................................................................................................................................................
STP functionality (Spanning Tree Protocol) The STP procedure is managed by means of special control frames BPDU (Bridge Protocol Data Unit), periodically sent, in band, as data payload, by the bridges into the network. BPDU (Bridge Protocol Data Unit) Frame (from IEEE Std. 802.1w-2001): Figure 1-35 STP/RSTP BPDU Frame format
Protocol Idenifier Protocol Version Idenifier BPDU Type Flags
Root Identifier
Root Path Cost
Bridge Identifier
Port Identifier Message Age Max Age Hello Time Forward Delay
Octets 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-55 Issue 05 February 2010
Introduction
STP functionality (Spanning Tree Protocol)
............................................................................................................................................................................................................................................................
Figure 1-36 Spanning Tree function (STP) example A B
C E
D
H
F
G
PHYSICAL TOPOLOGY (example) Active (forwarding) Port Active link
A
Active (forwarding) Port Active link
B Root Bridge
C
Blocking (discarding) Port
D
F
E
H
G
ACTIVE SPANNING TREE TOPOLOGY (example)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 56 Issue 05 February 2010
Introduction
STP functionality (Spanning Tree Protocol)
............................................................................................................................................................................................................................................................
Figure 1-37 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 for Bridge A
L1
B
L4
Root Bridge
L13
L9
C
DesignatedPort for path H - I L15
DesignatedPort for L4
L2
D
L7
E
L10
H
DesignatedBridge for L4, L5, L7
L3
L16 BackupPort for path H - I
L11
L5
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 in this handbook, where they will be used (see “Configure Bridge Port” “Transmission -> Ethernet Port -> Create Provider OutFlow” (p. 4-123) and subsequents. See also, for instance:“Bridge Port -> STP-Per Bridge Management” (p. 4-171), “Bridge Port -> ControlPlane -> STP-Per Port Management” (p. 4-174), etc.).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-57 Issue 05 February 2010
Introduction
STP functionality (Spanning Tree Protocol)
............................................................................................................................................................................................................................................................
Figure 1-38 PER-VLAN Spanning Tree example A 7,8
Registered VLAN's
B
3,5,7
5,3 7,8
C
4,5
E
5,7
D 6,7
8,9
H
9
7,9
6
F
9
7,9
G
PHYSICAL TOPOLOGY and Registered VLAN's
b7
A
Blocking port towards VLAN 7 7,8
b5
B
3,5,7
5,3
Root Bridge for VLAN 5
7,8
C
4,5 5,7
D
8,9
E
H
9
b9 6,7
b7
7,9
6
F
7,9
9
G
Root Bridge 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 8DG15624AAAA 1 - 58 Issue 05 February 2010
Introduction
STP functionality (Spanning Tree Protocol)
............................................................................................................................................................................................................................................................
Figure 1-39 PER-VLAN Spanning Tree - example of active topology
A
Blocking port towards VLAN 7
b7
7,8
B
3,5,7
7,8
C 5,7
6,7
b7
E
7,9
F
7,9
G
Root Bridge for VLAN 7
: Blocking Port with respect to the indicated VLAN
PER-VLAN ACTIVE SPANNING TREE TOPOLOGY (example for VLAN 7)
The RSTP (Rapid Spanning Tree Protocol) The RSTP 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 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. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-59 Issue 05 February 2010
Introduction
STP functionality (Spanning Tree Protocol)
............................................................................................................................................................................................................................................................
Figure 1-40 MSTP BPDU Frame format Octet Protocol Identifier Protocol Version Identifier BPDU Type CIST Flags CIST Root Identifier CIST External Path Cost CIST Regional Root Identifier CIST Port dentifier Message Age Max Age Hello Time Forward Delay Version 1 Length = 0 Version 3 Length MST Configuration Identifier CIST Internal Root Path Cost CIST Bridge Identifier CIST Remaining Hops MSTI Configuration Messages (may be absent)
1-2 3 4 5 6-13 14-17 18-25 26-27 28-29 30-31 32-33 34-35 36 37-38 39-89 90-93 94-101 102 103-39 + Version 3 Length
MSTI BPDU parameters and format Octet MSTI Flags MSTI Regional Root Identifier MSTI Internal Root Path Cost MSTI Bridge Priority MSTI Port Priority MSTI Remaining Hops
1 2-9 10-13 14 15 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
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. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 60 Issue 05 February 2010
Introduction
STP functionality (Spanning Tree Protocol)
............................................................................................................................................................................................................................................................
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-43, (pg. 1-63). The setting of the MSTP parameters is done by means of the option “Configure Bridge Port”, described in “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Virtual)” (p. 4-164), and subsequent ones. Figure 1-41 MSTP Network topology example Region 1 D
B
C
A
E
H
Region 2 X
Y F
Region 4
G
Region 5 Region 3 MSTP TOPOLOGY Example
Note: •
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. Bridges A,C and D are in the same MST Region (Region1) because they have the same “MST Configuration Identifier”. Bridges B,E and H belong to Region2 because they have the same “MST Configuration Identifier”, but different from those contained in Region1. Bridge G is in Region3 because its “MST Configuration Identifier” is different from the Bridges contained in Region1 and Region2. 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-42, (pg. 1-62).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-61 Issue 05 February 2010
Introduction
STP functionality (Spanning Tree Protocol)
............................................................................................................................................................................................................................................................
Figure 1-42 MSTP “collapsed” topology example
Region 1
RB1 RB2
Region 2 X Region 4
Y Region 5
F
G Region 3
MSTP "collapsed" TOPOLOGY
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 62 Issue 05 February 2010
Introduction
STP functionality (Spanning Tree Protocol)
............................................................................................................................................................................................................................................................
Figure 1-43 MSTP, VLAN differentiated routing example Region 1 5,7,10,11
A
Registered VLANs 5,7,10,11
5,7,10,11
Notes: all the VLANs involved in a Region should be registred at all the port of the Region (recommended)
5,7,10,11 5,7,10,11
C
5,10
D 5,7,10,11 7,11
7,11
5,10
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 F 5,10 F 7,11
A
F 5,10 F 7,11
Instance 1 Instance 2
F 5,10 F 7,11
b 5,10 F 7,11
F 5,10 F 7,11
D
C F5,10 F7,11
F5 F 10
X
The path A-D for VLANs 7 and 11 may be chosen by MSTP if, for example, the PathCost are the relevant ports, for MSTID 2, has benn set at lower value than that on path A-C The same pratice can be followed to route VLANs 5,10 on path A-C If a failure occurs, for example on path A-D, then the MSTIP procedure will re-route VLANs 7 and 11 on path AC-D-Y
F7 F 11
Y
Notes: F7: VLAN 7 is forwarded, at the relevant Port b7: VLAN 7 is blocked, at the relevant Port
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-63 Issue 05 February 2010
Introduction
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 SDHcontainer are transported over more individual containers, indicated with the symbol VCnXv (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-44 Virtual Concatenation (example) Byte
time slot
"big" Ethernet frame
a1
a2
a3
a4
a5
a6
a7
a8
a9 a10 a11 a12
b1
b2
b3
b4
b5
b6
b7
b8
b9 b10 b11 b12
1
2
3
4
5
6
7
8
9
10
11
Originating Point
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
b1
b4
b7 b10
b2
b5
b8 b11
b3
b6
b9 b12
a1
a2
a3
a4
a5
a6
a7
a8
a9 a10 a11 a12
b1
b2
b3
b4
b5
b6
b7
b8
b9 b10 b11 b12
SONET/SDH Network
Terminating Point
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 64 Issue 05 February 2010
Introduction
GFP Packets Concatenation
............................................................................................................................................................................................................................................................
GFP Packets Concatenation The packet concatenation consists in the transmission of packets over concatenated SDHVCs', in this case a packet is transported as a whole, on a single VC, without fragmentation. It is used to transport ethernet packets over SDH, by means of the GFP framing on the Remote Ethernet Ports. See figure below (example with concatenation granularity = 3). Figure 1-45 GFP Packets Concatenation RXEthernet I/F
TXEthernet I/F
ETH Pack 3 ETH Pack 2
ETH Pack 1 ETH Pack 2
ETH Pack 1
ETH Pack 3
ETH Pack 3 ETH Pack 2
ETH Pack 1 ETH Pack 2
SDH network
ETH Pack 1 GFP Frame
ETH Pack 3
VC number 1
GFP Frame
Pack 1 Remote Ethernet Port
VC number 2
Remote Ethernet Port
Pack 2 VC number 3 Pack 3
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-65 Issue 05 February 2010
Introduction
Loop-Back management
............................................................................................................................................................................................................................................................
Loop-Back management The ISA-ES system supports the Internal and Line Loop-Back feature, in order to check the network link integrity. The loop-back configuration is done by means of “Configure (LOCAL) Ethernet Port", see “Transmission -> Ethernet Port -> Configure (LOCAL) Ethernet Port” (p. 4-76). The loop-back scheme is illustrated in the Figure 1-46, (pg. 1-66). Figure 1-46 Internal & Line Loop Back scheme Line Internal LB LB Remote Port IF
XC OF
DTE OF XC
IF
Remote Port SONET SDH
Local Port OF XC
IF DTE
IF
XC OF
Local Port Shutdown on TX laser in case of internal LoopBack
Note: • • • • • • •
The internal LB is possible only in case of Port-to-Port connection (P2P). The Internal and Line LB are mutually exclusive. LB = Loopback IF = InFlow OF = OutFlow XC = Cross-connection DTE = Data Terminal Equipment
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 66 Issue 05 February 2010
Introduction
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 “Transmission -> Ethernet Port -> Configure (LOCAL) Ethernet Port” (p. 4-76). The CSF is managed by means of Transmit Capability, see “Transmission -> Ethernet Port -> Configure (REMOTE) Ethernet Port” (p. 4-90). 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 Transmit Capability 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-47, (pg. 1-67). Figure 1-47 CSF alarm management CSF insertion (bidir) LOF, TSF, PLM detection (P2P) DTE
Shutdown in case of CSF detection
Local Port
IF
XC OF
OF XC
IF
Remote Port
SONET SDH
Remote Port
IF
XC O F
IF
XC O F
Local Port
DTE
X
(P2P) CSF detection (if Conf.RemoteClient= Shutdown)
CSF insertion
LOS detection
(if GFP - Transmit Capability is enabled)
CSF insertion modality: (if GFP-Transmit Capability 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
Local Port Tx ShutDown: triggered by CSF detection, if Conf. Remote Client = 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 DTE = Data Terminal Equipment
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-67 Issue 05 February 2010
Introduction
System alarm management
............................................................................................................................................................................................................................................................
LLCF (Link Loss Carry Forward) in Hub-and-Spoke In case of Hub-and-spoke network topology, consisting of both Hub NE and multiple Spoke NE’s shown in Figure 1-48 and in front of: •
Either Ethernet PHY Interface failure (even if forced from Management operator for Maintenance), detected over Hub NE or Spoke NEs;
or •
Server Layer (e.g. SDH VCG) Failures (even if forced from Management operator for Maintenance) detected over either Hub NE or Spoke NEs,
Figure 1-48 LLCF in Hub-Spoke network topology Router IP Client Hub
Hub SDH A
Spoke Hub A Client A
CPE
SDH B
Spoke B Client B
CPE
The System, as HUB NE and provisioned as ETS/MPLS Switch, supports additional capabilities in Downstream (from Hub to Spokes) and Upstream (From Spokes to Hub) directions: •
DOWNSTREAM to Hub NE egress ports (towards Spoke NE’s) supports Downstream Consequent actions (either Operational GFP CSF Insertion on remote Ethernet interface or Operational transmitter shutdown on local Ethernet interface), where Downstream Consequent Actions are triggered: –
either from detected Ethernet PHY Interface failures detected on local Ethernet interface between Router and Hub NE;
or – from Server Layer failures detected on remote Ethernet interface between Router and Hub NE; Figure 1-49, (pg. 1-69) shows the emission of Unidirectional GFP CSF frames from Hub NE over multiple remote “SDH-based” Ports in order to propagate (towards remote Spoke NEs Spoke A and B) failure conditions (Ethernet PHY Interface failure, Server layer failures) detected on the link with Router IP.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 68 Issue 05 February 2010
Introduction
System alarm management
............................................................................................................................................................................................................................................................
•
UPSTREAM from a list of Hub NE ingress ports (towards Spoke NE¡¦s) triggers Upstream Consequent Actions on Hub NE Outbound port (towards Router IP). Upstream Consequent Actions (Operational transmitter shutdown on local Ethernet interface, GFP CSF Insertion on remote Ethernet interface) between Hub NE and IP Router are requested to be triggered from: –
detected Server Layer failures (occurring on SDH links between Spoke NE and Hub NE);
and/or – detected Ethernet PHY Interface failures (occurring on Ethernet Interface links between Spoke NE and Hub NE). Figure 1-49 LLCF propagation Router IP
Router IP
Client Hub
(1)
(5)
Hub SDH A GFP CSF (2)
Hub SDH B
GFP CSF (2)
SDH A
Spoke B (3)
SDH B
GFP CSF (2)
Spoke A Client A
Client Hub
(3)
CPE
Client B
CPE
Downstream
GFP CSF (4)
Spoke A Client A
Spoke B (1)
CPE
(3)
Client B
CPE
Upstream
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-69 Issue 05 February 2010
Introduction
System alarm management
............................................................................................................................................................................................................................................................
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 Portto-Port connection. The VC-AIS insertion is unidirectional. The VC-AIS function is supported on 10/100 Mbps ports as well as 1000 Mbps ports. The VC-AIS is managed by means of Transmit Capability item (see Figure 1-36, (pg. 1-56) and “Transmission -> Ethernet Port -> Configure (REMOTE) Ethernet Port” (p. 4-90)). 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-67). The VC-AIS mechanism scheme is illustrated in Figure 1-50, (pg. 1-70). Figure 1-50 VC-AIS alarm management LOS detection VC-AIS insertion
DTE
Local Port
IF
XC OF
Remote Port
SONET 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 DTE = Data Terminal Equipment
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 70 Issue 05 February 2010
Introduction
System alarm management
............................................................................................................................................................................................................................................................
This option is obtained, after selecting a REMOTE Ethernet Port, by means of the contextual pop-up menu, or by selecting in the menu-bar: Transmission -> Ethernet Port Management -> Configure Ethernet Port.
An example of the window displayed (GFP sector) is reported in figure below. For a correct working, 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 “Link Aggregation management” (p. 1-81)). This is done by means of Transmission -> Ethernet Port Management > Configure Ethernet Port: MAU -> Default Pause = disabled, AutoNegotiation- AdminStatus = enabled , AutoNegotiationLocal Capability Options (current) = b10baseTFD (in case of 10Mbps) / b100baseTXFD (in case of 100Mbps) / b1000baseXFD (in case of 1000Mbps). See Figure 1-52, (pg. 1-72) 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-52, (pg. 1-72) and “Transmission -> Ethernet Port -> Configure (LOCAL) Ethernet Port” (p. 4-76). 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 -> Asap Name = TSF_cleared.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-71 Issue 05 February 2010
Introduction
System alarm management
............................................................................................................................................................................................................................................................
Figure 1-51 Configure (remote) Ethernet Port: GFP: VC-AIS setting
Figure 1-52 Configure (local) Ethernet Port: MAU: Flow Control and ShutDown disabling
Flow Control Pause ShutDown disabling
Flow Control disabling
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 72 Issue 05 February 2010
Introduction
Auto-Negotiation management
............................................................................................................................................................................................................................................................
Auto-Negotiation management The ES16 system supports the start up of a communication link by means of the AutoNegotiation functionality. Possible only in Point-To-Point links. 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 FullDuplex 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 “Transmission -> Ethernet Port -> Configure (LOCAL) Ethernet Port” (p. 4-76). See also next Figure 1-53, (pg. 1-75).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-73 Issue 05 February 2010
Introduction
Flow-Control management
............................................................................................................................................................................................................................................................
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 farend 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, the FC is started also if the received rate exceeds the value set on “Fractional Rate”.
WARNING In occurrence of Flow Control enabled, the traffic Policing should be disabled. The setting of the Flow Control function is done by means of the “Transmission -> Ethernet Port -> Configure (LOCAL) Ethernet Port” (p. 4-76). The “Local Port-MAU Configuration” dialog window is also reported in next Figure 1-54, (pg. 1-76). 1. In case of AutoNegotiation disabled (i.e. with AutoNegotiation: Admin. Status = ”disabled”), the Flow Control 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 Flow Control is configured as follows: – Flow Control enabling: for 100Mbps case, Asymmetric FC: ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 74 Issue 05 February 2010
Introduction
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.
for 10Mbps case, Asymmetric FC: –
select: b10baseTFD, bFdxAPause and bFdxPause.
for 10Mbps case, Symmetric FC: –
select: b10baseTFD, bFdxSPause and bFdxPause.
for 1000Mbps case, Asymmetric FC: –
select: b1000baseXFD, bFdxAPause and bFdxPause.
for 1000Mbps case, Symmetric FC: – –
select: b1000baseXFD, bFdxSPause and bFdxPause.
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.
Figure 1-53 Flow Control scheme ETH Rx BW
SDH Tx BW (P2P)
Eth DTE
PF-R
Local Port
PF-T
IF
XC OF
OF XC
IF
Remote Port
ETH Tx BW
SONET /SDH
SDH Rx 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 Local Port
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 Local Port and the Tx-rate towards ETH-DTE is slowed down Note: –
The Flow Control is supported only in case of Port-to-Port Connection (P2P)
–
The Traffic policing should be disabled, in case of FC enabled.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-75 Issue 05 February 2010
Introduction
Flow-Control management
............................................................................................................................................................................................................................................................
–
IF = InFlow, OF = OutFlow, BW = Bandwidth
–
PF-R = Pause Frame received
–
PF-T = Pause Frame transmitted
–
XC = Cross Connection
–
DTE = Data Terminal Equipment
Figure 1-54 Configure (local) Ethernet Port: MAU: Flow Control setting MAU - 1GE Port
Flow Control1
AutoNegotiation enabling/disabling
FlowControl2
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 76 Issue 05 February 2010
Introduction
Port Mirroring management
............................................................................................................................................................................................................................................................
Port Mirroring management This function is activated in Transmission context, in the Configure Ethernet Port (Local) window, see “Transmission -> Ethernet Port -> Configure (LOCAL) Ethernet Port” (p. 4-76). 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-55, (pg. 1-78). The ES16 system provides some pre-defined ports (mirror-port) dedicated for mirroring the other ports, in the following combinations: Fast Ethernet Electrical access Card: •
input Port 65 to 74, 77 and 78 = = > mirrorable on mirror-ports 75 and 76
•
(input port 75 can be mirrored on port 76 and vice versa) output Port 65 to 76 = = > mirrorable on mirror-ports 77 and 78 (output port 77 can be mirrored on port 78 and vice versa)
WARNING Only one single port at a time can be mirrored over a mirror-port. If a port is used as a mirror, the same port can not be contemporarily mirrored on another port. I.e.: if for instance, input port 78 is mirrored on port 75, then port 78 can not be used in the same time to mirror output port 65. 1GE Optical access Card: •
input Port 79, 80, and 82 = = > mirrorable on mirror-ports 81
•
output Port 79, 80, and 81 = = > mirrorable on mirror-ports 82
WARNING Only one single port at a time can be mirrored over a mirror-port. If a port is used as a mirror, it can not be contemporarily mirrored on another port. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-77 Issue 05 February 2010
Introduction
Port Mirroring management
............................................................................................................................................................................................................................................................
Fast Ethernet Optical access Card: •
input Port 83, 84, 85, 88 and 89 = = > mirrorable on mirror-ports 86 and 87
•
(input port 86 can be mirrored on port 87 and vice versa) output Port 83, 84, 85, 86 and 87 = = > mirrorable on mirror-ports 88 and 89 (output port 88 can be mirrored on port 89 and vice versa)
WARNING Only one single port at a time can be mirrored over a mirror-port. If a port is used as a mirror, the same port can not be contemporarily mirrored on another port. Figure 1-55 Port Mirroring example Rx1-mir
Rx1-mir
p3 p3 Rx1
Tx2 p1
p2
XC
Tx1
Rx2 p3
Tx1-mir
p3
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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 78 Issue 05 February 2010
Introduction
Bridging Data Plane
............................................................................................................................................................................................................................................................
Bridging Data Plane Segregated Ports management This function is activated in “Connection”, in the Segregated Port Management menu option (see “Connection -> Bridge -> Segregated Port Management” (p. 4-251) and “” (p. 4-251)). It is not allowed in case of “none” Bridge (see “Transmission -> ISA -> Configure ISA” (p. 4-71)). The function of this option is to set the segregation state, in order to exclude some Ports (only ETB ports for MAC/Virtual Bridges, ETS and ETB for Provider Bridge) from the exchanging of frames with a given list of ports. In case of Virtual or Provider Bridge, the ports to be segregated can be also registered over the same VLAN. In this way a segregated port can exchange frames only with a non-segregated port. This function is used to save band and resources on the node and on the ports, and also to improve the security and the privacy of the transmission. An application example is reported in figure below. Figure 1-56 Segregation application example p1, p2,..p4 are segregated ports p1
p2
p5 is a non-segregated port
p5
BRIDGE
p3
p4
ports p1, p2, p3, p4 can exchange frames with p5, but not between them
IGMP Snooping management The ISA-ES system supports the IGMP function (Internet Group Multicast Protocol), as specified in international standard Recs. IETF-RFC 1112, 2236, 3376. It is configurable by means of the Transmission menu, ISA: Configure IGMP and Ethernet Port: Configure IGMP options (see“Transmission -> Ethernet Port -> IGMP -> Configure IGMP” (p. 4-193) till to “Transmission -> Aggregator -> IGMP -> IGMP Properties” (p. 4-198)). It is not allowed in case of MAC Bridge (see “Transmission -> ISA -> Configure ISA” (p. 4-71)). 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 level3 transporting IGMP information. In this way the ISA-ES16 (that is a level2 Switch) can check prospective ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-79 Issue 05 February 2010
Introduction
Bridging Data Plane
............................................................................................................................................................................................................................................................
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 (“Join Reports” and “Leave Reports”) 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. Figure 1-57 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-g6
g1-g3 DSLAM1 g1 U1
g2 U2
g3 U3
g4
DSLAM2 g6 U4
g4 g5 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 80 Issue 05 February 2010
Introduction
Link Aggregation management
............................................................................................................................................................................................................................................................
Link Aggregation management The ES16 system supports 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 GE (1Gbps) and FE/FX (10Mbps and 100Mbps). 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 16; (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-58, (pg. 1-84). 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 = 1Gbps, LAG-size = 5, number of ports = 7, then 2 ports (those ones having lower priorities) are classified as “stand-by” by the system.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-81 Issue 05 February 2010
Introduction
Link Aggregation management
............................................................................................................................................................................................................................................................
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 slowprotocol 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 and is accomplished within 1 second. In case that one or more links failed, the alarm LAG-DEG is raised by the system. In case that all links of the bundle fail, the alarm LAG-LOS is raised 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 xSTPBPDU, 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 8DG15624AAAA 1 - 82 Issue 05 February 2010
Introduction
Link Aggregation management
............................................................................................................................................................................................................................................................
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 Flow Control.
•
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-59, (pg. 1-85); the implementation procedure is described in “Link Aggregation, implementation example” (p. 1-85).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-83 Issue 05 February 2010
Introduction
Link Aggregation management
............................................................................................................................................................................................................................................................
Figure 1-58 LACPDU Frame format LACPDU frame (from IEEE Std. 802.3ad-2000) Octets 5 5 2 1 1 1 1 2 5 2 2 2 OCTETS 1 WITHIN FRAME 3 TRANSMITTED 1 TOP-TO1 BOTTOM 2 6
Destination Address Source Address Length/Type Subtype = LACP Version Number TLV_type = Actor Information Actor_Information_Length = 20 Actor_System_Priority Actor_System Actor _Key Actor_Port_Priority Actor_Port Actor_State Reserved TLV_type = Partner Information Partner_Information_Length = 20 Partner_System_Priority Partner_System Partner _Key Partner_Port_Priority Partner_Port Partner_State Reserved TLV_type = Collector Information Collector_Information_Length = 15 CollectorMaxDelay Reserved TLV_type = Terminator Terminal_Length = 0 Reserved
2 2 2 1 3 1 1 2 12 1 1 50 4
FCS LSB
MSB b0
b7 BITS WITHIN FRAME TRANSMITTED LEFT-TO-RIGHT
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 84 Issue 05 February 2010
Introduction
Link Aggregation management
............................................................................................................................................................................................................................................................
Figure 1-59 Link Aggregation example 10Gbps link using only 5 Gbps of bandwidth (Partner System)
(Actor System) Active links 1 Gb
1 Gb
10 Gb p1
X
(LagSize=5) 5 Gbps Aggregate Link
p1
1 Gb
1 Gb p5
1 Gb
p5 Stand-By links
p6
1 Gb p6
1 Gb
1 Gb p7
OMSN & ES16-A
X
p7 OMSN & ES16-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= 1 Gbps, 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 5 Gbps packets stream, is transported on an incoming segment over a 10 Gbps 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-59, (pg. 1-85), 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-85 Issue 05 February 2010
Introduction
Link Aggregation management
............................................................................................................................................................................................................................................................
1. On the first node (OMSN+ES16-A): a. In Transmission context, creation of the Aggregator (select the symbol “Agg Group Management”): Transmission -> Aggregator Management -> Create Aggregator set the Name (e.g. #1), the Actor Admin 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 Admin State = enable c. In Transmission context, transformation of one selected Local Ethernet Ports Client Layer in “LinkAgg Layer”: 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 Actor Port Priority parameter as indicated in Figure 1-59, (pg. 1-85). 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+ES16-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 8DG15624AAAA 1 - 86 Issue 05 February 2010
Introduction
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-87)). 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 ETHIWI Interfaces. •
•
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-87 Issue 05 February 2010
Introduction
Control Protocols management in a Transport Network
............................................................................................................................................................................................................................................................
'Customer Edge Dual Homing' interconnection is a redundant interconnection (see Figure 1-60, (pg. 1-88)) 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-60 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 PBPDU, both sharing the same MAC Address, as referred in Table 1-4, “L2 Control Protocols” (p. 1-50). and –
VRRP frames generated from VRRP protocol, as referred in Table 1-4, “L2 Control Protocols” (p. 1-50).
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 8DG15624AAAA 1 - 88 Issue 05 February 2010
Introduction
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 (supported from Rel.1.3 onward), constrained ONLY to frames whose destination address matches ”Bridge Group Address” for CE Dual Homing interconnection.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-89 Issue 05 February 2010
Introduction
Redundancy features
............................................................................................................................................................................................................................................................
Redundancy features EPS 1+1 management EPS scheme protects ISA Board and VCG ports against HW failures. EPS 1+1 mechanism requires the definition of a main board, chosen as working board per default when the protection is configured, and of a spare one, in stand-by status. When a failure on the working board occurs or the operator performs a forced command, the EPS protection causes a non revertive switching on the stand-by board. EPS protects the active board and all the persistent data (ISA-ES ports and switching configuration). Volatile data (like PM data and alarm history) are not involved in the cold stand-by process of the EPS scheme. Hereafter a picture explaining how the switch is performed in case of resilient access module. Figure 1-61 EPS 1+1 protection
ISA_PROT Card
Access Card
M A I N
S P A R E
ISA-ES board
In case of fault of the main board, the access traffic is protected if resilient access modules are used. The HW protection performs the redirection of the acceess traffic towards the spare board. Board switchin time is in the range of 150 ms, while the Ethernet traffic protection due to re-learning facility is in the range of 1 s.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 90 Issue 05 February 2010
Introduction
Redundancy features
............................................................................................................................................................................................................................................................
The full EPS configuration is composed of: –
nr. 2 ISA-ES16 (or ISA-ES16HC) boards
–
nr. 1 access module (resilient 4xGBE or 7xFXETH)
–
nr. 1 High Speed Protection unit
–
Appropriate SDH software release (rel. 4.6/5.4A2 or higher)
–
Appropriate ISA-ES16 software release (rel. 2.2B or higher) Note:
If resilient access modules and ISA-PROT unit are not used, the access traffic is lost in case of fault/switching of the main board, only the traffic at remote port is protected. Dual-homing (via selective BPDU tunnelling) The ISA-ES16 supports the Customer Edge (CE) “dual-homing” connection on “dual node topology. The following network scenario are supported: Figure 1-62 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. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-91 Issue 05 February 2010
Introduction
Redundancy features
............................................................................................................................................................................................................................................................
Specifically, “primary” and “secondary” connections are linked on two different systems (ISA-ES16 boards) and from the PE (Provider Edge) Ethernet point of view this configuration it is considered as dual node. Figure 1-63 Dual-homing BPDU (network) STP tunnel
Figure 1-64 Dual-homing BPDU (local) STP tunnel
Important! In ISA-ES16, the BPDU Tunnelling between two UNI in the same ISA-ES16 board (PE single node dual attachment is admitted) is not supported.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 92 Issue 05 February 2010
Introduction
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-65. 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-65 Connectivity Fault Management
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-93 Issue 05 February 2010
Introduction
Ethernet OAM
............................................................................................................................................................................................................................................................
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 8DG15624AAAA 1 - 94 Issue 05 February 2010
Introduction
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-xxiv); the hardware configuration, features and functionalities of AlcatelLucent Network Elements supporting ES services are described in the relevant Technical Handbooks listed in Table 1, (pg. 1-xxiv); 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-xxiv). 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: •
signal rate, bandwidth, interface type, traffic contract, cross-connections, manual and automatic switching, alarms, performance monitorings, etc.
The ES traffic and network management signaling inside the existing SDH network is accomplished by means of a dedicated communication protocol, as indicated in “Ethernet over SDH Management” (p. 1-97). 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-95 Issue 05 February 2010
Introduction
Management software
............................................................................................................................................................................................................................................................
This CD-ROM contains: •
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 dialog 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 8DG15624AAAA 1 - 96 Issue 05 February 2010
Introduction
Management software
............................................................................................................................................................................................................................................................
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-66, (pg. 1-97). An example of Ethernet/MPLS/SDH network management is shown in Figure 1-67, (pg. 1-98). 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-66 Protocol stack for ATM/MPLS/Ethernet over SDH management
Internet protocols
Application
Lay 7
Presentation
Lay 6
SNMP
Session
Lay 5
UDP
Transport (TP4)
Lay 4
IP
4
Network (CLNP)
802.3
1.
Lay 3
3 2
TMN protocols (QB3)
ISO/OSI protocols
1
LAPD
Lay 2 TMN protocols (F/Qecc)
Q3
Qecc/F
Lay 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)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-97 Issue 05 February 2010
Introduction
Management software
............................................................................................................................................................................................................................................................
Figure 1-67 Example of management of an SDH network with SDH and ES traffic OS SONET/SDH-OS & ES-OS
SONET/SDH (OSI) & ES (SNMP)
TMN Q3 802.3
QECC F
CT
QECC
LAPD
Gateway NE (GNE)
OSI LAPD
SONET/SDH-CT & ES-CT
SONET/SDH + ES NE
SNMP
SONET/SDH NE
QECC
CT
LAPD
LAPD
F
OSI
QECC SONET/SDH NE
OSI
SONET/SDH-CT
SONET/SDH + ES NE
OSI LAPD
F
SNMP
QECC LAPD
F
OSI
QECC SNMP
SONET/SDH + ES NE
Protocol stack at different interfaces: Q3
Data (SNMP) SNMP UDP IP
Tunnel
F
SONET/SDH (OSI) Appl. Pres. Sess. TP4 CLNP MAC Eth-Q3
Data (SNMP) SNMP UDP IP
Tunnel
QECC
SONET/SDH (OSI) Appl. Pres. Sess. TP4 CLNP LAPD RS232-F
Data (SNMP) SNMP UDP IP
SONET/SDH (OSI) Appl. Pres. Sess. TP4 CLNP LAPD SDH-Qcc
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 8DG15624AAAA 1 - 98 Issue 05 February 2010
Introduction
Management software
............................................................................................................................................................................................................................................................
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-xxiv) 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-xxiv) 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-xxiv) for these operations.
An illustrative example is reported in Figure 1-68, (pg. 1-100).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1-99 Issue 05 February 2010
Introduction
Management software
............................................................................................................................................................................................................................................................
Figure 1-68 OSI and IP addressing example OSI Address + IP Address IP Over OSI Tunnel
OS
(Operations System)
Managed NE (adjacent) NE + ISA ES
(Local manager) OSI Address + IP Address
Q3
CT
Ethernet Config
EC
F
OSI Address IP Address IP over OSI IP Router/CLNP Tunnel
SDH port LAPD = Network
Qecc
SDH port
LAPD = User
SDH SONET LAPD Config SDH SONET LAPD
VLAN
DATA port
for In Fiber In Band management
DATA#1
DATA#n
SNMP
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 10 0 Issue 05 February 2010
Introduction
Management software
............................................................................................................................................................................................................................................................
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1- 1 0 1 Issue 05 February 2010
Introduction
Management software
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 1 - 10 2 Issue 05 February 2010
2
Software Product and Licence
Overview Purpose This chapter describes the software packages list, the software licenses list, and their relevant part-numbers. Contents This chapter provides information on the following topics: •
“Software product and licenses description” (p. 2-2)
•
“Software products, licenses and part numbers” (p. 2-3)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 2-1 Issue 05 February 2010
Software Product and Licence
Software product and licenses description
............................................................................................................................................................................................................................................................
Software product and licenses description Overview 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 dialog 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
Common Platform
CT-K
Communication Lower Layer
ALL
SNMP
... JRE
JRE: Java Running Environment CT-K: Craft Terminal Kernel ALL: Alcatel-Lucent Lower Layer
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 2-2 Issue 05 February 2010
Software Product and Licence
Software products, licenses and part numbers
............................................................................................................................................................................................................................................................
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
ANV Part Number
Factory Part Number
SWP-ES16 R.2.5 (CD-ROM)
8DG 15652 AA
-.-.-
Note
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
ANV Part Number
Factory Part Number
Note
SWL-OMNSN METRO Vers. “A” ETH LP
8DG 15540 AB
-.-.-
a
SWL ENH ETH(ES16): PING, EPS...
8DG 15540 AC
-.-.-
b
SWL ENH ETH(ES16): OAM, LAG...
8DG 15540 AH
-.-.-
c
Note:
a. For OMSN equipped with ES16 (“DATA”-ES functionality) b. For “Ping, Eps,...” functionalities. c. For “OAM, LAG, ...” functionalities. Note: This product includes software developed by the Apache Software Foundation (http://www.apache.org).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 2-3 Issue 05 February 2010
Software Product and Licence
Software products, licenses and part numbers
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 2-4 Issue 05 February 2010
3
ES Software Installation
Overview Purpose 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. Contents This chapter provides information on the following topics: •
“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-26)
•
“Software Uninstallation procedure” (p. 3-31)
•
“NE-ES software downloading” (p. 3-34)
•
“Start-Up of the ES Craft Terminal management software” (p. 3-38)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3-1 Issue 05 February 2010
ES Software Installation
Software Version
............................................................................................................................................................................................................................................................
Software Version The edition of this Handbook refers to the features of ISA-ES16 product developed in •
MPLS FAST ETH 2.5.xx (CT_ES16-sw) that is the released versions for ISA-ES16 Rel. 2.5 (see next figure) and where “xx” is the file 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3-2 Issue 05 February 2010
ES Software Installation
Start-up of the Personal Computer
............................................................................................................................................................................................................................................................
Start-up of the Personal Computer Overview 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 ESCT software package. At this point the Windows application starts automatically and the operator will see the Windows desktop.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3-3 Issue 05 February 2010
ES Software Installation
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-xxiv) 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 1320CTBasic Handbook listed in Table 1, (pg. 1-xxiv); 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 -> SNMPCTK-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 & Restore Tools -> System Backup (see 1320CT Operator Handbook listed in Table 1, (pg. 1-xxiv) for details). ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3-4 Issue 05 February 2010
ES Software Installation
Host Computer Configuration
............................................................................................................................................................................................................................................................
Verification of IP address assignment for the host computer
WARNING The following procedure is here described only for WINDOWS-NT environment, but for WINDOWS-XP or others it is similar; refer to 1320CT Basic Handbook listed in Table 1, (pg. 1-xxiv) for details. 1. Verify that the LLman Lower Layers adapter is installed: a. In WINDOWS environment: Start -> Setting -> Control Panel; 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 Lower Layer Adapter is listed 2. Verify that the IP address to the PC is assigned: a. In WINDOWS environment: Start -> Setting -> Control Panel; 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 Lower Layer Adapter 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-xxiv) for the Alcatel-Lucent Lower Layer manager installation and for the IP address assignment.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3-5 Issue 05 February 2010
ES Software Installation
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-xxiv)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-xxiv) (see also note below). 2. Installation of SDH-NE software package into the PC, see 1320CT Basic Handbook, listed in Table 1, (pg. 1-xxiv). 3. Download of SDH-NE software into the NE, see the specific OMSN Operator's Handbook, listed in Table 1, (pg. 1-xxiv). 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-26). 6. Download of ES-NE software into the NE, see“NE-ES software downloading” (p. 3-34). 7. Activation of the ES-NE software into the NE, see “Start-Up of the ES Craft Terminal management software” (p. 3-38).
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-26))
•
second step downloading the new SDH packet associated with the new service packet (e.g.: enhanced OMSN with ES).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3-6 Issue 05 February 2010
ES Software Installation
Summary procedure for ES software installation
............................................................................................................................................................................................................................................................
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3-7 Issue 05 February 2010
ES Software Installation
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.
These differences will be explained. 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:
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3-8 Issue 05 February 2010
ES Software Installation
ES-CT Installation procedure
............................................................................................................................................................................................................................................................
Figure 3-2 Initial presentation intermediate screen
Figure 3-3 Selecting installation procedure (1st step)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3-9 Issue 05 February 2010
ES Software Installation
ES-CT Installation procedure
............................................................................................................................................................................................................................................................
Note:
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. 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 unistallation of the application has to be done in the Windows-NT environment, see instructions at “Software Uninstallation procedure” (p. 3-31).
–
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 OK to have the next dialog box:
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3 - 10 Issue 05 February 2010
ES Software Installation
ES-CT Installation procedure
............................................................................................................................................................................................................................................................
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_FASTETH REL... (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-xxiv), therefore they are not described in this manual; refer to the 1320CT Basic Handbook, listed in Table 1, (pg. 1-xxiv), for their installation. 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 8DG15624AAAA 3-11 Issue 05 February 2010
ES Software Installation
ES-CT Installation procedure
............................................................................................................................................................................................................................................................
In case of CT-K upgrading, the system Backup from WINDOWS environment is recommended : Start -> Programs -> Important!
ALCATEL -> 1320CT Backup & Restore Tools -> System Backup
(see 1320CT Operator Handbook, listed in Table 1, (pg. 1-xxiv), 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 check box 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3 - 12 Issue 05 February 2010
ES Software Installation
ES-CT Installation procedure
............................................................................................................................................................................................................................................................
6. Refer to Figure 3-6, (pg. 3-12). This view presents the terms of the license for the usage of the ES-CT. Click 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 8DG15624AAAA 3-13 Issue 05 February 2010
ES Software Installation
ES-CT Installation procedure
............................................................................................................................................................................................................................................................
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).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3 - 14 Issue 05 February 2010
ES Software Installation
ES-CT Installation procedure
............................................................................................................................................................................................................................................................
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. Then, a series of automatic windows presentation will be displayed, showing the setup in progress; see an example in next figure:
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3-15 Issue 05 February 2010
ES Software Installation
ES-CT Installation procedure
............................................................................................................................................................................................................................................................
Figure 3-11 Setup in progress, temporary windows sequence presentation
11. Refer to Figure 3-11, (pg. 3-16). 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-12, (pg. 3-17) 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-13, (pg. 3-18) will be displayed.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3 - 16 Issue 05 February 2010
ES Software Installation
ES-CT Installation procedure
............................................................................................................................................................................................................................................................
Figure 3-12 Successive installation, temporary windows presentation
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3-17 Issue 05 February 2010
ES Software Installation
ES-CT Installation procedure
............................................................................................................................................................................................................................................................
12. Refer to Figure 3-12, (pg. 3-17). The sequence of successive components installation procedure continues and, after intermediate automatic screens, the procedure will continue as detailed in the point Step 16. Figure 3-13 Installation procedure menu window (2nd step)
13. Refer to Figure 3-13, (pg. 3-18). 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-14, (pg. 3-18). . Figure 3-14 Craft Terminal master setup, list of detected Components on the media
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3 - 18 Issue 05 February 2010
ES Software Installation
ES-CT Installation procedure
............................................................................................................................................................................................................................................................
14. Refer to Figure 3-14, (pg. 3-18). The screen lists the installed Software Components detected. Click on OK to present next dialog box: Figure 3-15 Selecting SNMPCT component
15. Refer to Figure 3-15, (pg. 3-19). 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 check box to SNMPCT-K-ADD-ON component to mark it with a check, and then click on Next. 16. 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-18, (pg. 3-22), then Figure 3-19, (pg. 3-23), then Figure 3-21, (pg. 3-24), and then Figure 3-22, (pg. 3-25). • 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-16, (pg. 3-20), then Figure 3-18, (pg. 3-22), and so on, skipping Figure 3-20, (pg. 3-24).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3-19 Issue 05 February 2010
ES Software Installation
ES-CT Installation procedure
............................................................................................................................................................................................................................................................
–
Equal or similar release: in this case (maintenance) the procedure will continue displaying Figure 3-17, (pg. 3-21), then Figure 3-18, (pg. 3-22), and so on.
If another release of SNMPCT software has been detected, then the following figure will be displayed: Figure 3-16 Existing different SNMPCT release to be uninstalled
17. Refer to Figure 3-16, (pg. 3-20). 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-18, (pg. 3-22). If another release of SNMPCT software has been detected, then the following figure will be displayed:
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3 - 20 Issue 05 February 2010
ES Software Installation
ES-CT Installation procedure
............................................................................................................................................................................................................................................................
Figure 3-17 Existing previous similar release to be maintained: “REPAIR"
18. Refer to Figure 3-17, (pg. 3-21). Select the Repair item, to maintain the software release. Then click on Next button to continue to the following:
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3-21 Issue 05 February 2010
ES Software Installation
ES-CT Installation procedure
............................................................................................................................................................................................................................................................
Figure 3-18 SNMP CT Add On setup
19. Refer to Figure 3-18, (pg. 3-22). 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-19, (pg. 3-23).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3 - 22 Issue 05 February 2010
ES Software Installation
ES-CT Installation procedure
............................................................................................................................................................................................................................................................
Figure 3-19 SNMPCT setup in progress temporary window
20. Refer to Figure 3-19, (pg. 3-23). This is a temporary window showing the setup progress.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3-23 Issue 05 February 2010
ES Software Installation
ES-CT Installation procedure
............................................................................................................................................................................................................................................................
Maintenance case (skipped in case of first installation): Figure 3-20 Maintenance Finished
21. Refer to Figure 3-20, (pg. 3-24). This window informs that maintenance is completed. Click on Finish to continue. Figure 3-21 SNMPCT installation completed
22. Refer to Figure 3-21, (pg. 3-24). This window informs that the installation of the SNMPCT software has been completed. Click the OK button, then the following figure will be shown:
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3 - 24 Issue 05 February 2010
ES Software Installation
ES-CT Installation procedure
............................................................................................................................................................................................................................................................
Figure 3-22 Selecting installation procedure (end step)
23. Refer to Figure 3-22, (pg. 3-25). 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 -> SNMPAddOn Customization.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3-25 Issue 05 February 2010
ES Software Installation
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-38), then the following window will be displayed: Figure 3-23 Descriptor files administration
1. Refer to Figure 3-23, (pg. 3-26). In this window, select the menu options: Supervision -> Files Administration -> SWP Administrator. The Software Package Administration window will be opened:
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3 - 26 Issue 05 February 2010
ES Software Installation
NE-ES package installation procedure
............................................................................................................................................................................................................................................................
Figure 3-24 Software Package Administration-ES service specific
2. Refer to Figure 3-24, (pg. 3-27). 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-25, (pg. 3-28). 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 8DG15624AAAA 3-27 Issue 05 February 2010
ES Software Installation
NE-ES package installation procedure
............................................................................................................................................................................................................................................................
Figure 3-25 File-Browser for Software Package installation
Figure 3-26 Software Package Administration - create Enhanced OMSN
3. Refer to Figure 3-27, (pg. 3-29). 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.
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-xxiv)).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3 - 28 Issue 05 February 2010
ES Software Installation
NE-ES package installation procedure
............................................................................................................................................................................................................................................................
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-27 Software Package Administration - add ES service
4. Refer to Figure 3-24, (pg. 3-27). 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 addon service is already installed
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 service packet (e.g.: enhanced OMSN with ES).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3-29 Issue 05 February 2010
ES Software Installation
NE-ES package installation procedure
............................................................................................................................................................................................................................................................
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 EMLUSM environment, as described in “NE-ES software downloading” (p. 3-34). 5. Refer to Figure 3-24, (pg. 3-27). At the end of the operation, exit this application by means of the Close button.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3 - 30 Issue 05 February 2010
ES Software Installation
Software Uninstallation procedure
............................................................................................................................................................................................................................................................
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 -> Control Panel) and select the Add/Remove Programs icon, as for the following figure. Figure 3-28 Add/Remove Programs icon selection
2. Refer to Figure 3-28, (pg. 3-31). Click twice on the Add/Remove Programs icon to open it; then the next window will appear:
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3-31 Issue 05 February 2010
ES Software Installation
Software Uninstallation procedure
............................................................................................................................................................................................................................................................
Figure 3-29 Add/Remove Programs view
3. Refer to Figure 3-29, (pg. 3-32). Select, in the Install/Uninstall tab of this window, the application “MPLS_FASTETH_USM x.x.x" (or other CT components) and click on the Change/Remove button. A confirmation message is presented: Figure 3-30 Delete confirmation (example)
4. Refer to Figure 3-30, (pg. 3-32). After confirmation with Yes button, next figure (example) appears, indicating the deleting process:
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3 - 32 Issue 05 February 2010
ES Software Installation
Software Uninstallation procedure
............................................................................................................................................................................................................................................................
Figure 3-31 Delete completed (example)
Refer to Figure 3-31, (pg. 3-33). 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 8DG15624AAAA 3-33 Issue 05 February 2010
ES Software Installation
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-38)). 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-32 Download Initiate (example)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3 - 34 Issue 05 February 2010
ES Software Installation
NE-ES software downloading
............................................................................................................................................................................................................................................................
2. Refer to Figure 3-32, (pg. 3-34). In this box, select the software package containing the ES service, i.e. that one with the E suffix (in this example 1650SME). 3. Click the Ok button to start, a confirmation box ask for a confirmation. Figure 3-33 Download confirmation box
4. Click the OK button to start, a box showing the progress of the downloading process will be then displayed. Figure 3-34 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-32, (pg. 3-34). 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 8DG15624AAAA 3-35 Issue 05 February 2010
ES Software Installation
NE-ES software downloading
............................................................................................................................................................................................................................................................
Figure 3-35 NE Software package activation (example)
7. Refer to Figure 3-35, (pg. 3-36). Select the appropriate equipment-version tab of this window. Select the Activate option of the Current State\Action pull-down field, and then the Ok button, to activate the selected Software package. 8. Click the Ok button on the further displayed confirmation box. Figure 3-36 Activate SW package confirmation
Refer to Figure 3-35, (pg. 3-36). The SW Units Det. button opens another box giving some information about the selected downloaded package.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3 - 36 Issue 05 February 2010
ES Software Installation
NE-ES software downloading
............................................................................................................................................................................................................................................................
Figure 3-37 SW package details
Refer to Figure 3-35, (pg. 3-36). Click on Cancel button to close this box.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3-37 Issue 05 February 2010
ES Software Installation
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-38 1320CT software start-up
2. Then, the NES (Network Elements Synthesis) window will be displayed (see next figure).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3 - 38 Issue 05 February 2010
ES Software Installation
Start-Up of the ES Craft Terminal management software
............................................................................................................................................................................................................................................................
Figure 3-39 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-40, (pg. 3-40)), 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 8DG15624AAAA 3-39 Issue 05 February 2010
ES Software Installation
Start-Up of the ES Craft Terminal management software
............................................................................................................................................................................................................................................................
Figure 3-40 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-41 Login dialog box
8. Digit the Login and Password and the ISA USM starts.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3 - 40 Issue 05 February 2010
ES Software Installation
Start-Up of the ES Craft Terminal management software
............................................................................................................................................................................................................................................................
Figure 3-42 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 “NE-ES software downloading” (p. 3-34)
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 -> IP Configuration -> ISA Board IP Address) are necessary. See “NE-ES software downloading” (p. 3-34) for details about download procedure, the OMSNOperator Handbook for the board IP address setting, and the 1320CT Basic Handbook, listed in Table 1, (pg. 1-xxiv), for the PC IP address setting.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3-41 Issue 05 February 2010
ES Software Installation
Start-Up of the ES Craft Terminal management software
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 3 - 42 Issue 05 February 2010
4
Craft Terminal for ES Management
Overview Purpose This chapter describes all the views presented by the ES-Craft Terminal, including all the information needed to set the various ISA-ES parameters and configurations. Contents This chapter provides information on the following topics: •
“Summary procedure for ES Management” (p. 4-4)
•
“Main view” (p. 4-5)
•
“List of the menus options” (p. 4-14)
•
“Supervision management” (p. 4-31)
•
“Generic and common functions” (p. 4-33)
•
“Diagnosis and Alarms Configuration” (p. 4-39)
•
“MIB Management” (p. 4-53)
•
“Transmission” (p. 4-55)
•
“OAM” (p. 4-226)
•
“Connection” (p. 4-244)
•
“Performance” (p. 4-305)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-1 Issue 05 February 2010
Craft Terminal for ES Management
Overview
............................................................................................................................................................................................................................................................
Overview 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-xxiv), 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-xxiv), 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-xxiv), for details about IP address setting for ES board.
WARNING If, for any reason, the IP address is changed, the following customization WINDOWS command is necessary: Start->Programs->Alcatel->SNMPCT-KADDON->SNMP-Add On 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-2 Issue 05 February 2010
Craft Terminal for ES Management
Overview
............................................................................................................................................................................................................................................................
Figure 4-1 Logon view
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-3 Issue 05 February 2010
Craft Terminal for ES Management
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): on SDH-CT: 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) c. cross-connection of virtual SDH containers transporting Ethernet on ES-CT: d. Bridge configuration: none or bridge 802.1S-AD (Provider) or bridge 802.1Q (Virtual) or bridge 802.1D (MAC) e. Ethernet or Bridge Ports definition: ETS or ETB f. Local and Remote Ethernet ports configuration and GFP or LAPS interface definition g. Bridge Ports configuration, in case of bridge mode h. traffic contract definition (TD) i. Ethernet to PPP substitution, in case of MPLS j. Outer and Inner Tunnel creation, in case of MPLS k. V-LAN Registration, in case of Virtual or Provider Bridge l. InFlow/OutFlows creation: see Note: m. Classifiers definition: see Note: n. Cross-Connections creations: see Note: o. Configuration of Performance Monitoring points Note: The points ( l), ( m), ( n) must be done in one single step by means of the Connection wizard: Create ETS XC One Step. See “Connection -> Ethernet Port -> Create ETS XC One Step (MAC & Virtual)” (p. 4-264) and subsequent paragraphs. Some examples about ETS Connection, MPLS Tunnelling, etc., are reported in “Example of end-to-end ETS link creation (“none” Bridge case)” (p. 1-17) till to “Example of MPLS over Ethernet Tunnelling creation” (p. 1-40).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-4 Issue 05 February 2010
Craft Terminal for ES Management
Main view
............................................................................................................................................................................................................................................................
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-14)). •
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-31).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-5 Issue 05 February 2010
Craft Terminal for ES Management
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-6 Issue 05 February 2010
Craft Terminal for ES Management
Main view
............................................................................................................................................................................................................................................................
Figure 4-2 Main view title menu bar tool bar Domain Alarms Synthesis
Severity Alarms 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-12)). 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-7 Issue 05 February 2010
Craft Terminal for ES Management
Main view
............................................................................................................................................................................................................................................................
Figure 4-3
TREE area example
ISA-ES Switch
not usable ETH Port
usable ETH Port
expanded branch
leaf Ethernet port not expanded branch
All the ports are visualized automatically by the system in the tree; if not yet defined, they are greyed.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-8 Issue 05 February 2010
Craft Terminal for ES Management
Main view
............................................................................................................................................................................................................................................................
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. •
PPP Port:
•
MPLS Port:
•
IN-FLOW Point:
•
OUT-FLOW Point: The presence of a little upper cross (“X") means that the point is connected.
•
CLASSIFIER Point:
•
IN-SEGMENT Point:
•
OUT-SEGMENT Point:
:
The presence of a little upper cross (“X") means that the point is connected. •
Main TUNNEL:
•
Virtual MPLS PORT:
•
Outer TUNNEL (HEAD):
•
Outer TUNNEL (TRANSIT):
•
Outer TUNNEL (TAIL):
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-9 Issue 05 February 2010
Craft Terminal for ES Management
Main view
............................................................................................................................................................................................................................................................
•
Inner TUNNEL (HEAD):
•
Inner TUNNEL (TAIL):
•
Bridge:
•
ETB Port:
•
Bridge
orange colored (also called “(R)STPBridgePort")
When the type of a port is changed, e.g. from ETS to ETB, its relevant symbol changes form and color. AggGroup-Root”: named AggGroup-Management”, it collects all created LAGs
•
LAG,
•
RSTP Port:
i.e., “Link Aggregation Group” (not operative in current release):
Note: • •
• • • •
•
ES Node: representing the ISA-ES virtual node LOCAL ETHERNET PORT: representing the local ethernet access Important! The local ETH port can be FE (numbered 65 to 78) or GE (numbered 79 to 82), depending on the type of equipped Access Card. Therefore, if the Access Card is FE type, only the FE ports can be used and GE ports are unusable, and vice versa. Unusable ports are displayed with a different graphical symbol. REMOTE ETHERNET PORT: representing the remote ethernet access (ethernet 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), in order to classify the ethernet user data flow; it defines the user-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. When defined, the only frames indicated in the classifier will be transported by the ETS (Ethernet Transport System). PPP PORT: representing the Point-to-Point interface towards the interior of the MPLS network, to accomplish the MPLS over SDH transport. It is obtained by substituting a remote Ethernet port with a PPP one.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 10 Issue 05 February 2010
Craft Terminal for ES Management
Main view
............................................................................................................................................................................................................................................................
•
•
•
• •
•
•
MPLS PORT: representing the MPLS port towards the interior of the MPLS network (active into the PPP ports, and also into the local Ethernet Ports with Promiscuous Mode = Disabled) IN-SEGMENT: resource used into the MPLS network, into an MPLS port, defining an incoming data flow from the interior of the MPLS network; it is correlated to the tunnel resources, and is automatically created after the creation of a related tunnel OUT-SEGMENT: resource used into the MPLS network, into an MPLS port, defining an outgoing data flow towards the interior of the MPLS network; it is correlated to the tunnel resources, and is automatically created after the creation of a related tunnel “Main" TUNNEL: representing the logical tunnel point to group the “Tunneling" resources Virtual MPLS PORT: representing a “virtual" MPLS port, automatically created under the “main tunnel", that is used to group the outSegment resources created for the Inner Tunnel “head" connections Outer TUNNEL: representing the tunnel that can aggregate more “Inner tunnels"; three Outer Tunnels types are possible: Head (at the originating edge point), “Transit" (at an intermediate network point) and Tail (at the terminating edge point) Inner TUNNEL: representing the tunnel that can transport Ethernet data flows; two Inner Tunnels types are possible: Head (at the originating edge point) and Tail (at the terminating edge point).
•
Bridge: representing the logical bridge point to group the “Bridging" resources that have to work in “autolearning" modality. Note: The name of this resource is changed to SWITCH, in the Connection context.
•
ETB Port (also called “(R)STP Bridge Port"): representing the Ethernet Port that has been configured to work in “autolearning" modality RSTP Port (not operative): representing the logical Port that contains the parameters to define the STP/RSTP bridge modality Aggregate Group Management: representing the logical point to organize all the “Link Aggregated" 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)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-11 Issue 05 February 2010
Craft Terminal for ES Management
Main view
............................................................................................................................................................................................................................................................
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”. 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-13)); 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 12 Issue 05 February 2010
Craft Terminal for ES Management
Main view
............................................................................................................................................................................................................................................................
Figure 4-4 Spontaneous information message example
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-13 Issue 05 February 2010
Craft Terminal for ES Management
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-15).
– Configuration (second column). See options in “Configuration menu introduction” (p. 4-16). –
Diagnosis (third column). See options in “Diagnosis menu introduction” (p. 4-16).
–
Supervision (fourth column). See options in “Supervision menu introduction”
(p. 4-17). –
MIB-Management (fifth column). See options in “Mib-Management menu
introduction” (p. 4-17). –
OAM Domain (sixth column). See options in “OAM Domain menu introduction”
(p. 4-17). – Help (last column: it activates the help system). See options in “Help menu introduction” (p. 4-30). •
Specific alternative Menus –
Transmission (seventh column) See options in “Transmission menu introduction”
(p. 4-18). –
Connection (seventh column). See options in “Connection menu introduction”
(p. 4-25). – Performance (seventh column). See options in “Performance menu introduction” (p. 4-28).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 14 Issue 05 February 2010
Craft Terminal for ES Management
List of the menus options
............................................................................................................................................................................................................................................................
•
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 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-18). It yields the Transmission menu in the seventh column of the menu bar. •
Connection: to enter the Connection application. See options in “Connection menu
introduction” (p. 4-25). •
It yields the Connection menu in the seventh column of the menu bar. Performance: to enter the Performance application. See options in “Performance menu introduction” (p. 4-28).
•
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 “Views -> Search” (p. 4-35)). •
Filter...: not yet operative
•
Print: It causes the printing of details for the selected resource list shown in the
Application Table area. (See “Views -> Print” (p. 4-38)). •
Close...: not yet operative
•
Exit: To close the ES-CT session.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-15 Issue 05 February 2010
Craft Terminal for ES Management
List of the menus options
............................................................................................................................................................................................................................................................
Configuration menu introduction It contains the following entries: •
Alarms Severities: To manage the Alarms Severity Assignment Profile (ASAP). See
“Configuration -> Alarms Severity (ASAP management)” (p. 4-39). •
Set Alarms Severities: To associate an ASAP to a resource. See “Set Alarms
Severities” (p. 4-43). •
Loop-Back Management: See “Configuration -> Loop Back Management” (p. 4-46).
•
List CEPST Instances: not operative in current release.
•
Set ACD level: not operative in current release.
•
Traffic Descriptor: To manage the parameters defining the traffic.
It contains the following sub-options: – ETS Traffic Descriptor: to manage the Ethernet traffic parameters. See “Configuration -> Traffic Descriptor -> ETS Traffic Descriptor” (p. 4-56). •
•
•
Link Creation Wizard: not operative in current release.
To start a wizard program for helping during the Links configurations. This procedure recalls, in the right order, the necessary dialog windows to configure the links parameters. Connection Wizard: not operative in current release. To start a wizard program for helping during the Connections configurations. This procedure recalls, in the right order, the necessary dialog 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 “Configuration -> Options” (p. 4-33). Diagnosis menu introduction It contains the following entries: •
Alarms: To enter the Alarms Surveillance (AS) application. See “Alarms Surveillance
(Diagnosis -> Alarms option)” (p. 4-47). 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-49). It contains the following sub-options: – Event: to “browse" the logs relevant to the ES events. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 16 Issue 05 February 2010
Craft Terminal for ES Management
List of the menus options
............................................................................................................................................................................................................................................................
– •
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
“Diagnosis -> Navigation to EML-USM” (p. 4-52). Supervision menu introduction It contains the following entries: •
Access State: To manage the supervision access states. See “Access state (allow or
inhibit ES-Craft access)” (p. 4-31). It contains the following sub-options: – 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.
It contains the following sub-options: – Re-synchronize: See “Alarms re-synchronization” (p. 4-47). –
Allow Notification: See “Allow/Inhibit Alarms Notifications” (p. 4-47).
– Inhibit Notification: See “Allow/Inhibit Alarms Notifications” (p. 4-47). •
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-32). •
Restart ISA: To restart the equipment software. See “Restart ISA (Not operative)”
(p. 4-32). Not operative in current release. Mib-Management menu introduction It contains the following entries: •
Backup/Restore DB: To manage the backup and restore of the MIB (configuration
data-base). See “Backup/Restore DB” (p. 4-53). •
Compare two Backup Files: Not operative in current release. See “Compare two
Backup Files” (p. 4-54). OAM Domain menu introduction It contains the following entries: •
Configure Resources (OAM): To manage the resources of OAM Domain. See “OAM
Domain -> Configure Resources (OAM)” (p. 4-227). •
Properties Resources (OAM): To show properties for resources of OAM Domain. See
“OAM Domain -> Properties Resources (OAM)” (p. 4-239).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-17 Issue 05 February 2010
Craft Terminal for ES Management
List of the menus options
............................................................................................................................................................................................................................................................
•
Configure (OAM): To manage the “Global” parameters for OAM. See “OAM Domain
-> Configure (OAM)” (p. 4-240). •
Properties (OAM): To show the “Global” parameters for OAM. See “OAM Domain ->
Properties (OAM)” (p. 4-240). •
Configure LoopBack (OAM): To manage the parameters for “Alcatel-Lucent-
Proprietary” LoopBack. See “OAM Domain -> Configure LoopBack (OAM)” (p. 4-241). •
LoopBack Properties (OAM):To show the parameters for “Alcatel-Lucent-
Proprietary” LoopBack. See “OAM Domain -> Loop Back Properties (OAM)” (p. 4-243). Transmission menu introduction It contains the following entries: •
ISA Management: To manage the transmission parameters for the ISA-ES unit.
It contains the following sub-options: – Configure ISA: See “Transmission -> ISA -> Configure ISA” (p. 4-71). – VLAN Registration: See “Transmission -> ISA -> VLAN Registration” (p. 4-155). –
Private VLAN Registration: not operative in current release.
–
Resources Availability: not operative in current release.
–
IGMP Management:
–
Configure IGMP: See “Transmission -> ISA -> IGMP Management ->
Configure IGMP” (p. 4-190). –
IGMP Properties: See “Transmission -> ISA -> IGMP Management -> IGMP
Properties” (p. 4-193). – ISA Properties: See “Transmission -> ISA -> ISA Properties” (p. 4-74). •
PPP Port Management: To manage the transmission parameters for a PPP port. (Active only if Bridge Type = none). It contains the following sub-options:
–
Substitute PPP -> Ethernet: See “Transmission -> PPP Port -> Substitute PPP ->
Ethernet” (p. 4-131). –
Configure PPP Port: See “Transmission -> PPP Port -> Configure PPP Port”
(p. 4-132). –
PPP Port Properties: See “Transmission -> PPP Port -> PPP Port Properties”
(p. 4-136). •
Ethernet Port Management: To manage the transmission parameters for an Ethernet
port (Local or Remote). It contains the following sub-options: –
Substitute Ethernet -> PPP: See “Transmission -> Ethernet Port -> Substitute
Ethernet -> PPP” (p. 4-131). ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 18 Issue 05 February 2010
Craft Terminal for ES Management
List of the menus options
............................................................................................................................................................................................................................................................
–
Substitute Server Layer: See “Transmission -> Ethernet Port -> Substitute Server
Layer” (p. 4-102). – –
–
ETH on GFP ETH on LAPS
Substitute Client Layer: See “Transmission -> Ethernet Port/Aggregator ->
Substitute Client Layer” (p. 4-153).
–
– –
ETB Layer ETS Layer
–
LinkAgg Layer (only Local Port)
Queue (QoS) Management:
–
Configure Queue: see “Transmission -> Ethernet Port -> Queue (QoS) -> Configure Queue” (p. 4-184).
–
Properties Queue: see “Transmission -> Ethernet Port -> Queue (QoS) ->
Properties Queue” (p. 4-187). –
GFP Client Layer Management: (only on Remote Port)
–
Client Layer Single->Multi: See “Transmission -> Ethernet Port (Remote) ->
GFP Client Layer Management” (p. 4-141). –
Bridge Port Management:To manage transmission parameters for an ETB Port. It
contains the following sub-options: –
Configure Bridge Port (Virtual): See “Transmission -> Ethernet Port ->
Bridge Port -> Configure Bridge Port (Virtual)” (p. 4-164) – Configure Bridge Port (Provider): See “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Provider)” (p. 4-159) –
Configure Bridge Port (MAC): See, “Transmission -> Ethernet Port -> Bridge
Port -> Configure Bridge Port (MAC)” (p. 4-167) –
Bridge Port Properties: See “Transmission -> Ethernet Port -> Bridge Port ->
Bridge Port Properties” (p. 4-182) –
Show VLAN info: See “Transmission -> Ethernet Port -> Bridge Port -> Show
VLAN Info” (p. 4-183). – CEPST Management: not operative in current release. –
Aggregation Port:
–
Configure: See “Transmission -> Ethernet Port -> Aggregation Port ->
Configure” (p. 4-208). – Properties: See “Transmission -> Ethernet Port -> Aggregation Port -> Properties” (p. 4-212). –
Create Flow Group: not operative in current release.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-19 Issue 05 February 2010
Craft Terminal for ES Management
List of the menus options
............................................................................................................................................................................................................................................................
–
Create ETS InFlow: See “Transmission -> Ethernet Port -> Create ETS InFlow”
(p. 4-111). –
Create ETS OutFlow: See “Transmission -> Ethernet Port -> Create ETS
OutFlow” (p. 4-117). –
Create Provider InFlow: See “Furthermore, this OutFlow does not support
VLAN-Management function.” (p. 4-153). – Create Provider OutFlow: See “Transmission -> Ethernet Port -> Create Provider OutFlow” (p. 4-123). –
Configure Ethernet Port:
–
Local port: See “Transmission -> Ethernet Port -> Configure (LOCAL)
Ethernet Port” (p. 4-76). –
Remote port: See “Transmission -> Ethernet Port -> (REMOTE) Ethernet
Port Properties” (p. 4-101). – IGMP Management: –
Configure IGMP: See “Transmission -> ISA -> IGMP Management ->
Configure IGMP” (p. 4-190). –
IGMP Properties: See “Transmission -> ISA -> IGMP Management -> IGMP
Properties” (p. 4-193). – Characterization Service: –
Other: See “Transmission -> Ethernet Port -> Characterization Service”
(p. 4-103). –
ETS Virtual Switch (Service): See “Transmission -> Ethernet Port ->
Characterization Service” (p. 4-103). – Port To Port (Service): See “Transmission -> Ethernet Port -> Characterization Service” (p. 4-103). –
Traffic Management:
–
Traffic Enabled: See “Transmission -> Ethernet Port -> Traffic Management”
(p. 4-103). – Traffic Disabled: See “Transmission -> Ethernet Port -> Traffic Management” (p. 4-103). –
ACL Management:
–
Configure ACL: See “Transmission -> Ethernet Port -> ACL -> Configure
ACL” (p. 4-104). – Properties ACL: See “Transmission -> Ethernet Port -> ACL -> Properties ACL” (p. 4-110). – Disassociate ACL: See “Transmission -> Ethernet Port -> ACL -> Disassociate ACL” (p. 4-110) ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 20 Issue 05 February 2010
Craft Terminal for ES Management
List of the menus options
............................................................................................................................................................................................................................................................
–
In Fiber In Band Management:
–
Create In Fiber In Band: See “Transmission -> Ethernet Port -> In Fiber In
Band -> Create” (p. 4-213). –
– –
Modify In Fiber In Band: See “Transmission -> Ethernet Port -> In Fiber In
Band -> Modify” (p. 4-214). – Delete In Fiber In Band: See “Transmission -> Ethernet Port -> In Fiber In Band -> Delete” (p. 4-215). – Properties In Fiber In Band: See “Transmission -> Ethernet Port -> In Fiber In Band -> Properties” (p. 4-216). Configure Hub Spoke: See “Transmission -> Ethernet Port -> Hub-Spoke” (p. 4-217). EFM Management: –
Configure EFM: See “Transmission -> Ethernet Port -> EFM Management ->
Configuration” (p. 4-219). – EFM Properties: “Transmission -> Ethernet Port -> EFM Management -> Properties” (p. 4-224) – Create Ip Port: not operative in current release. –
Ethernet Port Properties:
–
Local port: See “Transmission -> Ethernet Port -> Configure (LOCAL)
Ethernet Port” (p. 4-76). –
Remote port: See “Transmission -> Ethernet Port -> (REMOTE) Ethernet
Port Properties” (p. 4-101). •
Aggregator Management:
– Create Aggregator: See “Transmission -> Aggregator -> Create Aggregator” (p. 4-199). •
Aggregator: (for LAG resource).
To manage the transmission parameters for a Link Aggregation Group. It contains the following sub-options: – Substitute Client Layer: See “Transmission -> Ethernet Port/Aggregator -> Substitute Client Layer” (p. 4-153)
–
–
ETB Layer
–
ETS Layer
Bridge Port Management:
–
Configure Bridge Port (Provider): See “Transmission -> Ethernet Port ->
Bridge Port -> Configure Bridge Port (Provider)” (p. 4-159) – Configure Bridge Port (Virtual): See “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Virtual)” (p. 4-164) ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-21 Issue 05 February 2010
Craft Terminal for ES Management
List of the menus options
............................................................................................................................................................................................................................................................
–
Configure Bridge Port (MAC): See “Transmission -> Ethernet Port -> Bridge
Port -> Configure Bridge Port (MAC)” (p. 4-167) – Bridge Port Properties: See “Transmission -> Ethernet Port -> Bridge Port -> Bridge Port Properties” (p. 4-182). –
Show VLAN Info: See “Transmission -> Ethernet Port -> Bridge Port -> Show
VLAN Info” (p. 4-183). –
CEPST Management: not operative in current release.
–
Create Flow Group: not operative in current release.
–
Create ETS InFlow: See “Transmission -> Ethernet Port -> Create ETS InFlow”
(p. 4-111). –
Create ETS OutFlow: See “Transmission -> Ethernet Port -> Create ETS
OutFlow” (p. 4-117). –
Create Provider InFlow: See “Transmission -> Ethernet Port -> Create Provider
InFlow” (p. 4-121). – Create Provider OutFlow: See “Transmission -> Ethernet Port -> Create Provider OutFlow” (p. 4-123). –
Configure Aggregator/Ethernet Port: See “Transmission -> Aggregator ->
Configure Aggregator” (p. 4-202). – Delete Aggregator: See “Transmission -> Aggregator -> Delete Aggregator” (p. 4-208). –
IGMP Management:
–
Configure IGMP: See “Transmission -> Aggregator -> IGMP -> Configure
IGMP” (p. 4-198). –
IGMP Properties: See “Transmission -> Aggregator -> IGMP -> IGMP
Properties” (p. 4-198). – Characterization Service: –
Other: See “Transmission -> Ethernet Port -> Characterization Service”
(p. 4-103). –
ETS Virtual Switch (Service): “Transmission -> Ethernet Port -> Characterization Service” (p. 4-103)
–
Port To Port (Service): See “Transmission -> Ethernet Port ->
Characterization Service” (p. 4-103). –
Traffic Management: See “Transmission -> Aggregator -> Traffic Management”
(p. 4-104) –
Traffic Enable
–
Traffic Disable
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 22 Issue 05 February 2010
Craft Terminal for ES Management
List of the menus options
............................................................................................................................................................................................................................................................
–
Aggregator/Ethernet Port Properties: See “Transmission -> Aggregator ->
Aggregator Properties” (p. 4-207). •
MPLS Port Management: (available only with Bridge Type = none, on Local Port with
Promiscuous Mode = disabled, or on PPP ports). To manage the transmission parameters for an MPLS Port. It contains the following sub-options: – Create MPLS InSegment: See “Transmission -> MPLS Port -> Create MPLS InSegment (not operative)” (p. 4-146). –
Create MPLS OutSegment: See “Transmission -> MPLS Port -> Create MPLS
OutSegment (not operative)” (p. 4-148). –
GFP Client Layer Management: (available only in the case of GFP Client = Multi Client), i.e. MPLS Over GFP Port) Client Layer Multi->Single: See “Transmission
-> MPLS Port (over GFP) -> GFP Client Layer Management” (p. 4-141). –
Configure MPLS Port: See “Transmission -> MPLS Port -> Configure MPLS Port”
(p. 4-137) (for MPLS Over PPP). –
Configure MPLS Port (over GFP): See “Transmission -> MPLS Port (over GFP) ->
Configure MPLS Port” (p. 4-142) (for MPLS Over GFP, i.e. multi-layer GFP). –
MPLS Port Properties: See “Transmission -> MPLS Port -> MPLS Port
Properties” (p. 4-140). •
Group Flow Management: not operative in current release.
•
MPLS InSegment Management: To manage the transmission parameters for an InSegment (available only with Bridge Type = none). It contains the following sub-
options: –
Modify MPLS InSegment: See “Transmission -> MPLS InSegment -> Modify MPLS InSegment (not operative)” (p. 4-146).
–
Delete MPLS InSegment: See “Transmission -> MPLS InSegment -> Delete
MPLS InSegment (not operative)” (p. 4-149). – MPLS InSegment Properties: See “Transmission -> MPLS InSegment -> MPLS InSegment Properties” (p. 4-146). •
MPLS OutSegment Management:To manage the transmission parameters for an Out Segment (available only with Bridge Type = none). It contains the following sub-
options: –
Modify MPLS OutSegment: See “Transmission -> MPLS OutSegment -> Modify
MPLS OutSegment (not operative)” (p. 4-148). –
Delete MPLS OutSegment: See “Transmission -> MPLS OutSegment -> Delete
MPLS OutSegment (not operative)” (p. 4-149). –
MPLS OutSegment Properties: See “Transmission -> MPLS OutSegment ->
MPLS OutSegment Properties” (p. 4-148). ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-23 Issue 05 February 2010
Craft Terminal for ES Management
List of the menus options
............................................................................................................................................................................................................................................................
•
ETS InFlow Management:To manage the transmission parameters for an InFlow point.
It contains the following sub-options: – Create ETH2ETS Classifier: See “Transmission -> ETS InFlow -> Create ETH2ETS Classifier” (p. 4-126). –
Modify ETS InFlow: See “Transmission -> ETS InFlow -> Modify ETS InFlow”
(p. 4-124). –
Delete ETS InFlow: See “Transmission -> ETS InFlow -> Delete ETS InFlow”
(p. 4-125). –
ETS InFlow Properties: See “Transmission -> ETS InFlow -> ETS InFlow
Properties” (p. 4-124). •
ETS OutFlow Management:To manage the transmission parameters for an OutFlow
point. It contains the following sub-options: – Modify ETS OutFlow: See “Transmission -> ETS OutFlow -> Modify ETS OutFlow” (p. 4-125). –
Delete ETS OutFlow: See “Transmission -> ETS OutFlow -> Delete ETS
OutFlow” (p. 4-126). – ETS OutFlow Properties: See “Transmission -> ETS OutFlow -> ETS OutFlow Properties” (p. 4-125). •
Classifier Management: To manage the transmission parameters for an ETS-Classifier
point. It contains the following sub-options: – Modify Classifier: See “Transmission -> Classifier -> Modify Classifier” (p. 4-130). –
Delete Classifier: See “Transmission -> Classifier -> Delete Classifier” (p. 4-130).
–
Classifier Properties: See “Transmission -> Classifier -> Classifier Properties”
(p. 4-130). •
Inner MPLS Tunnel: To manage the transmission parameters for an Inner MPLS
Tunnel. Note: This option is visible only after selecting an Inner Tunnel, created in Connection context; (available only with Bridge Type = none).
It contains the following sub-options: –
Create ETS InFlow: See “Transmission -> Inner MPLS Tunnel -> Create ETS
InFlow” (p. 4-150). –
Create ETS OutFlow: See “” (p. 4-150).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 24 Issue 05 February 2010
Craft Terminal for ES Management
List of the menus options
............................................................................................................................................................................................................................................................
•
Outer MPLS Tunnel:To manage the transmission parameters for an Outer MPLS
Tunnel (used for MPLS over Ethernet modality). This option is visible only after selecting an Outer Tunnel, created in Connection context; (available only with Bridge Type = none). Note:
It contains the following sub-options: – Create ETS InFlow: See “Transmission -> Outer MPLS Tunnel -> Create ETS InFlow” (p. 4-152). –
Create ETS OutFlow: See “Transmission -> Outer MPLS Tunnel -> Create ETS
OutFlow” (p. 4-152). Connection menu introduction It contains the following entries: •
Bridge Management: To manage the connection parameters for the Bridge. It contains
the following sub-options: –
Filtering Data Base: See “Connection -> Bridge -> Filtering Data Base”
(p. 4-244). – Segregated Port management: See “Connection -> Bridge -> Segregated Port Management” (p. 4-251). •
MPLS InSegment Management: To manage the connections parameters for an In
Segment. It contains the following sub-options: –
Create MPLS XC: See “Connection -> MPLS InSegment -> Create MPLS XC (not
operative)” (p. 4-286); –
Create MPLS Terminating XC: See “Connection -> MPLS InSegment -> Create
MPLS Terminating XC (not operative)” (p. 4-286); –
Modify MPLS XC: See “Connection -> MPLS InSegment -> Modify MPLS XC (not
operative)” (p. 4-287); –
Delete MPLS XC: See “Connection -> MPLS InSegment -> Delete MPLS XC (not
operative)” (p. 4-287); –
MPLS XC Properties: See “Connection -> MPLS InSegment -> MPLS XC
Properties” (p. 4-287). •
MPLS OutSegment Management: To manage the connections parameters for an Out
Segment It contains the following sub-options: –
Create MPLS XC: See“Connection -> MPLS OutSegment -> Create MPLS XC
(not operative)” (p. 4-288).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-25 Issue 05 February 2010
Craft Terminal for ES Management
List of the menus options
............................................................................................................................................................................................................................................................
–
Create MPLS Originating XC: See “Connection -> MPLS OutSegment -> Create
MPLS Originating XC (not operative)” (p. 4-289). –
Modify MPLS XC: See “Connection -> MPLS OutSegment -> Modify MPLS XC
(not operative)” (p. 4-289). –
Delete MPLS XC: See “Connection -> MPLS OutSegment -> Delete MPLS XC
(not operative)” (p. 4-289). –
MPLS XC Properties: See “Connection -> MPLS OutSegment -> MPLS XC
Properties” (p. 4-289). •
Ethernet Port Management: To manage the connection parameters for an Ethernet
port. It contains the following sub-options: –
Segregated Port Set: See “Connection -> Bridge -> Segregated Port
Management” (p. 4-251). –
Create ETS XC One Step (ETS & MPLS-Head): See “Connection -> Ethernet Port -
> Create ETS XC One Step (ETS & MPLS Tunnel-Head)” (p. 4-254). –
Create ETS XC One Step (ETS Virtual Switch): See “Connection -> Ethernet Port
-> Create ETS XC One Step (ETS Virtual Switch)” (p. 4-259). –
Create ETS XC One Step (Mac/Virtual): See “Connection -> Ethernet Port ->
Create ETS XC One Step (MAC & Virtual)” (p. 4-264). –
Create ETS XC One Step (Provider): See “Connection -> Ethernet Port -> Create
ETS XC One Step (Provider)” (p. 4-267). –
Delete ETS XC One Step (Mac/Virtual): See “Connection -> Ethernet Port ->
Delete ETS XC One Step (MAC & Virtual)” (p. 4-278). –
Delete ETS XC One Step (Provider): See “Connection -> Ethernet Port -> Delete
ETS XC One Step (Provider)” (p. 4-280). •
Link Aggregator Group Management: To manage the connection parameters for a
LAG. These options are the same as the above “Ethernet Port Management”. Note:
It contains the following sub-options: – Segregated Port Set: See “Connection -> Ethernet Port -> Segregated Port Set” (p. 4-252). –
Create ETS XC One Step (ETS & MPLS-Head): See“Connection -> Ethernet Port -
> Create ETS XC One Step (ETS & MPLS Tunnel-Head)” (p. 4-254). –
Create ETS XC One Step (ETS Virtual Switch): See “Connection -> Ethernet Port
-> Create ETS XC One Step (ETS Virtual Switch)” (p. 4-259). –
Create ETS XC One Step (Mac/Virtual): See“Connection -> Ethernet Port -> Create ETS XC One Step (MAC & Virtual)” (p. 4-264).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 26 Issue 05 February 2010
Craft Terminal for ES Management
List of the menus options
............................................................................................................................................................................................................................................................
–
Create ETS XC One Step (Provider): See“Connection -> Ethernet Port -> Create
ETS XC One Step (Provider)” (p. 4-267). –
Delete ETS XC One Step (Mac/Virtual): See “Connection -> Ethernet Port ->
Delete ETS XC One Step (MAC & Virtual)” (p. 4-278). –
Delete ETS XC One Step (Provider): See “Connection -> Ethernet Port -> Delete
ETS XC One Step (Provider)” (p. 4-280). •
ETS InFlow Management: To manage the connection parameters for an InFlow point.
It contains the following sub-options: –
Create ETS XC: (not operative) See “Connection -> ETS InFlow -> Create ETS XC (not operative)” (p. 4-284).
–
Modify ETS XC: See “Connection -> ETS InFlow -> Modify ETS XC” (p. 4-284)
–
Delete ETS XC: See “Connection -> ETS InFlow -> Create ETS XC (not
operative)” (p. 4-284) –
ETS XC Properties: See “Connection -> ETS InFlow -> ETS XC Properties”
(p. 4-284) •
ETS OutFlow Management: To manage the connection parameters for an OutFlow
point. It contains the following sub-options: –
Create ETS XC: (not operative) See “Connection -> ETS OutFlow -> Create ETS
XC (not operative)” (p. 4-285); –
Modify ETS XC: See “Connection -> ETS OutFlow -> Modify ETS XC (not
operative)” (p. 4-286); (not operative) –
Delete ETS XC: See “Connection -> ETS OutFlow -> Delete ETS XC (not
operative)” (p. 4-286) –
ETS XC Properties: See “Connection -> ETS OutFlow -> ETS XC Properties”
(p. 4-286) •
MPLS Tunnel Management:To manage the tunnelling resources of the “Main" MPLS
Tunnel. It contains the following sub-options: –
Create Outer Head Tunnel: See “Connection -> MPLS Tunnel Management ->
Create Outer Head Tunnel” (p. 4-289). –
Create Outer Transit Tunnel: See “Connection -> MPLS Tunnel Management ->
Create Outer Transit Tunnel” (p. 4-292). –
Create Outer Tail Tunnel: See “Connection -> MPLS Tunnel Management ->
Create Outer Tail Tunnel” (p. 4-294). •
Outer MPLS Tunnel:To manage the connections parameters for a Outer MPLS Tunnel. Note:
This option is visible only after selecting an Outer Tunnel.
It contains the following sub-options:
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-27 Issue 05 February 2010
Craft Terminal for ES Management
List of the menus options
............................................................................................................................................................................................................................................................
–
Create Inner MPLS Tunnel: See “Transmission -> Ethernet Port -> Substitute
Ethernet -> PPP” (p. 4-131) –
Modify Outer MPLS Tunnel: See “Connection -> Outer MPLS Tunnel -> Modify
Outer MPLS Tunnel” (p. 4-300) – Delete Outer MPLS Tunnel: See “Connection -> Outer MPLS Tunnel -> Delete Outer MPLS Tunnel” (p. 4-301) –
Outer MPLS Tunnel Properties: See “Connection -> Inner MPLS Tunnel -> Inner
MPLS Tunnel Properties” (p. 4-302) –
Create ETS XC One Step (MPLS-Tail): See “Connection -> Inner (Outer) MPLS
Tunnel -> Create ETS XC One Step (Tunnel-Tail)” (p. 4-260). – Delete ETS XC One Step (MPLS-Tail): See “” (p. 4-275). •
Inner MPLS Tunnel:To manage the connections parameters for an Inner MPLS
Tunnel. Note:
This option is visible only after selecting an Inner Tunnel.
It contains the following sub-options: – Modify Inner MPLS Tunnel: See “Connection -> Inner MPLS Tunnel -> Modify Inner MPLS Tunnel” (p. 4-302) –
Delete Inner MPLS Tunnel: See “Connection -> Inner MPLS Tunnel -> Delete
Inner MPLS Tunnel” (p. 4-304) –
Inner MPLS Tunnel Properties: See “Connection -> Inner MPLS Tunnel -> Inner MPLS Tunnel Properties” (p. 4-302)
–
Create ETS XC One Step (MPLS-Tail): See “Connection -> Inner (Outer) MPLS
Tunnel -> Create ETS XC One Step (Tunnel-Tail)” (p. 4-260). – Delete ETS XC One Step (MPLS-Tail): See “” (p. 4-275). Some examples of Ethernet, VLAN, or SVLAN link creation are reported in “Ethernet Private Line (EPL), end to end implementation example” (p. 1-22), and subsequent paragraphs. An example of MPLS over SDH tunnel creation is reported in “Example of MPLS over SDH Tunnelling creation” (p. 1-34). An example of MPLS over Ethernet tunnel creation is reported in “Example of MPLS over Ethernet Tunnelling creation” (p. 1-40). Performance menu introduction It contains the following entries: •
MPLS Switch Management:
To manage the Performance Monitoring (PM) Granularity for the Bridge. It contains the following sub-options: ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 28 Issue 05 February 2010
Craft Terminal for ES Management
List of the menus options
............................................................................................................................................................................................................................................................
–
Granularity 15 Minutes: See “Performance -> MPLS Switch -> Granularity
15Minutes/1Hour” (p. 4-306) –
Granularity 1 Hour: See “Performance -> MPLS Switch -> Granularity
15Minutes/1Hour” (p. 4-306). •
MPLS Port Management: not operative in current release.
To manage the Performance Monitoring (PM) parameters for an MPLS port. It contains the following sub-options: – MPLS Port Properties: not operative in current release. •
MPLS InSegment Management: not operative in current release.
To manage the Performance Monitoring (PM) parameters for an In Segment point. It contains the following sub-options: – InSegment Properties: •
MPLS OutSegment Management: not operative in current release.
To manage the Performance Monitoring (PM) parameters for an Out Segment point. It contains the following sub-options: – OutSegment Properties: •
Ethernet Port Management:
To manage the Performance Monitoring (PM) parameters for an Ethernet port. It contains the following sub-options: – Configure ETH Aggr: See “Performance -> Ethernet Port -> Configure ETH. Aggr.” (p. 4-307) –
ETH Aggr Properties: See “Performance -> Ethernet Port -> ETH Aggr.
Properties” (p. 4-308). •
Flow Group Management: not operative in current release.
To manage the Performance Monitoring (PM) parameters for a Flow Group. It contains the following sub-options: – Flow Group Properties: •
ETS InFlow Management: To manage the Performance Monitoring (PM) parameters
for an InFlow point. It contains the following sub-options: –
Configure InFlow: See “Performance -> ETS InFlow -> Configure InFlow”
(p. 4-310) –
InFlow Properties: See “Performance -> ETS InFlow -> InFlow Properties”
(p. 4-311). •
ETS OutFlow Management: To manage Performance Monitoring (PM) parameters for
an OutFlow point. It contains the following sub-options: – Configure OutFlow: not operative in current release. See “Performance -> ETS OutFlow -> Configure OutFlow” (p. 4-313) ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-29 Issue 05 February 2010
Craft Terminal for ES Management
List of the menus options
............................................................................................................................................................................................................................................................
–
OutFlow Properties: not operative in current release. See “Performance -> ETS
OutFlow -> OutFlow Properties” (p. 4-314). Help menu introduction It contains the following entries: •
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 8DG15624AAAA 4 - 30 Issue 05 February 2010
Craft Terminal for ES Management
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 dialog 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-31 Issue 05 February 2010
Craft Terminal for ES Management
Supervision management
............................................................................................................................................................................................................................................................
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 dialog 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 8DG15624AAAA 4 - 32 Issue 05 February 2010
Craft Terminal for ES Management
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
Configuration -> Options 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-35). 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 -> Ethernet Port 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:
Tabular Mode, or Graphical Mode; the Graphical Mode (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: “Full Window" and “Tabbed Window"” (p. 4-34). – •
Views Layout: the only option is Tabbed Mode.
Measurement Units:
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-33 Issue 05 February 2010
Craft Terminal for ES Management
Generic and common functions
............................................................................................................................................................................................................................................................
–
Time: possible options: MicroSec or MilliSec
–
Size: possible options: Octet
–
Bit Rate: possible options: kbps or Mbps
Figure 4-6
Configuration -> Options
Windows Presentation: “Full Window" and “Tabbed Window" This function is accessible by selecting, in the menu bar: Configuration -> Options and then clicking on Program tab, Secondary Window Layout 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 dialog
windows.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 34 Issue 05 February 2010
Craft Terminal for ES Management
Generic and common functions
............................................................................................................................................................................................................................................................
Figure 4-7 Configuration -> Options - Program (“Full Window Mode" example)
Figure 4-8 Configuration -> Options - Program (“Tabbed Window Mode" example)
Views -> Search This function is accessible by selecting, in the menu bar: Views -> Search. An example of the displayed dialog window is reported in Figure 4-9, (pg. 4-37). 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. 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 Inflow, MPLS InSegment, MPLS OutSegment, ETS2 MPLS Mapping, MPLS2 ETS Mapping, ETS Xc, MPLS Xc, etc. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-35 Issue 05 February 2010
Craft Terminal for ES Management
Generic and common functions
............................................................................................................................................................................................................................................................
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 OutFlow:
–
Status: up / down
–
XC Status: Cross Connected / Not Cross Connected
–
Server Type: Ethernet
ETS InFlow:
–
Status: up / down
–
XC Status: Cross Connected / Not Cross Connected
–
Service Type: Ethernet
Ethernet Port:
–
Ethernet Port Type: Local / Remote
–
Status: up / down
–
Client Type: ets / etb
MPLS Port:
– •
ETS2MPLS Mapping:
– •
Status: up / down
MPLS2ETS Mapping:
– •
Status: up / down
Status: up / down
MPLS Inner Tunnel:
– Status: up / down
•
•
–
Role: tail / head
–
Client Type: mpls / ethernet
MPLS Outer Tunnel:
–
Status: up / down
–
Role: tail / head / transit
–
Client Type: mpls / ethernet
MPLS OutSegment:
–
Status: up / down
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 36 Issue 05 February 2010
Craft Terminal for ES Management
Generic and common functions
............................................................................................................................................................................................................................................................
•
•
–
XC Status: Cross Connected / Not Cross Connected
–
MPLS Port Range: from... to...
–
Label Range: from... to... (only if Service Type = Ethernet)
MPLS InSegment:
–
Status: up / down
–
XC Status: Cross Connected / Not Cross Connected
–
MPLS Port Range: from... to...
–
Label Range: from... to...
Agg Group:
–
Status: up / down
–
Client Type: ets / etb
Figure 4-9 Views -> Search
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-37 Issue 05 February 2010
Craft Terminal for ES Management
Generic and common functions
............................................................................................................................................................................................................................................................
•
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 “Views ->
Print” (p. 4-38). •
Help: to get helps about this function.
Views -> Print This function is accessible by selecting, in the menu bar: Views -> Print An example of the displayed dialog window is reported in Figure 4-10. 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. Click on Ok to print, on Preview to preview, or on Cancel to leave the dialog without printing. Figure 4-10 Views -> Print
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 38 Issue 05 February 2010
Craft Terminal for ES Management
Diagnosis and Alarms Configuration
............................................................................................................................................................................................................................................................
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
Configuration -> Alarms Severity (ASAP management) 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 set 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 dialog is displayed, as follows:
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-39 Issue 05 February 2010
Craft Terminal for ES Management
Diagnosis and Alarms Configuration
............................................................................................................................................................................................................................................................
Figure 4-11 ASAP Management dialog
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-43). By clicking on any of the keys: Details or Create or Modify, a window as that of Figure 4-12, (pg. 4-41) is displayed (example). At the bottom of the window shown in Figure 4-11, (pg. 4-40) there are the following other buttons: •
Delete: to delete the selected ASAP.
•
Cancel: to close the window.
•
Print: to print the list of ASAPs.
•
Help: to get helps about this function.
•
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 40 Issue 05 February 2010
Craft Terminal for ES Management
Diagnosis and Alarms Configuration
............................................................................................................................................................................................................................................................
Figure 4-12 ASAP: Severities profile example
Creating an ASAP As soon as the previous window shown in Figure 4-11, (pg. 4-40) is presented, only the Create button is available, therefore, by clicking on this key the window of Figure 4-12, (pg. 4-41) 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-43).; 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-41 Issue 05 February 2010
Craft Terminal for ES Management
Diagnosis and Alarms Configuration
............................................................................................................................................................................................................................................................
•
Print: to print a detail list of this ASAP.
•
Help: to get helps about this function.
Getting details on ASAPs After selecting a profile in the window of Figure 4-11, (pg. 4-40) and clicking on the Details key, details about it are given on the displayed ASAP Severity window, the same as Figure 4-12, (pg. 4-41). 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 dialog. Modifying an ASAP After selecting a profile in the window of Figure 4-11, (pg. 4-40) and clicking on the Modify key, the user can modify it, on the displayed ASAP Severity window shown in Figure 4-12, (pg. 4-41). 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 pulldown 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-11, (pg. 4-40) will be recalled, then select the desired ASAP and click on Ok button.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 42 Issue 05 February 2010
Craft Terminal for ES Management
Diagnosis and Alarms Configuration
............................................................................................................................................................................................................................................................
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
minor
minor
DACM (Dual Attachment Connectivity Message)
cleared
major
major
DEG (SDH Concatenation 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 ESCT. 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 Ethernet Port, 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 dialog is displayed, as for the window shown in Figure 4-13, (pg. 4-45). The ASAP currently operative on the selected object (only if Ethernet Port) 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-43 Issue 05 February 2010
Craft Terminal for ES Management
Diagnosis and Alarms Configuration
............................................................................................................................................................................................................................................................
•
List of ASAPs sector:
the list reports all the existing ASAP's. One of them can be highlighted, if an Ethernet Port 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 “Configuration -> Alarms Severity (ASAP management)” (p. 4-39). •
Apply to sector:
(active only if an ASAP has been selected in the list of ASAPs) –
Choose Scope items: Selected Object Only: it is active only if an Ethernet Port 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 (i.e. Local Ethernet Port or Remote Ethernet Port or PPP Port). 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
•
Help: to get helps about this function. 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 ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 44 Issue 05 February 2010
Craft Terminal for ES Management
Diagnosis and Alarms Configuration
............................................................................................................................................................................................................................................................
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 “Transmission -> Ethernet Port -> Configure (LOCAL) Ethernet Port” (p. 4-76)). Figure 4-13 ASAP: Set Alarm Severities (example)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-45 Issue 05 February 2010
Craft Terminal for ES Management
Diagnosis and Alarms Configuration
............................................................................................................................................................................................................................................................
Configuration -> Loop Back Management The Local Ethernet ports support the Internal Loopback function, as described in “LoopBack management” (p. 1-66). This option is recalled from the Configuration pull down menu, selecting the Loop-Back Management item. The Loopback Management dialog is displayed in Figure 4-14, (pg. 4-46). 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 “Transmission -> Ethernet Port -> Configure (LOCAL) Ethernet Port” (p. 4-76). Note:
Line Loopback and Internal Loopback are mutually exclusive. Figure 4-14 Loop Back Management dialog
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 46 Issue 05 February 2010
Craft Terminal for ES Management
Diagnosis and Alarms Configuration
............................................................................................................................................................................................................................................................
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 dialog 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 dialog 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-47 Issue 05 February 2010
Craft Terminal for ES Management
Diagnosis and Alarms Configuration
............................................................................................................................................................................................................................................................
Select the Diagnosis pull down menu and then the Alarms cascading menu; the following options are offered: •
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-15 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. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 48 Issue 05 February 2010
Craft Terminal for ES Management
Diagnosis and Alarms Configuration
............................................................................................................................................................................................................................................................
The listing of all the Alarms or the filtering of a class of them is also possible. 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-xxiv). 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-xxiv). 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-16, (pg. 4-50).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-49 Issue 05 February 2010
Craft Terminal for ES Management
Diagnosis and Alarms Configuration
............................................................................................................................................................................................................................................................
Figure 4-16 Log Retrieval: Event (Filter example)
Click on Filter key and the Event report is then displayed as for Figure 4-17, (pg. 4-50). Figure 4-17 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-18, (pg. 4-51).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 50 Issue 05 February 2010
Craft Terminal for ES Management
Diagnosis and Alarms Configuration
............................................................................................................................................................................................................................................................
Figure 4-18 Log Retrieval: Alarm (Filter example)
•
Click on Filter key and the Event report is then displayed as for Figure 4-19, (pg. 4-51).
Figure 4-19 Log Retrieval: Alarm (Report example)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-51 Issue 05 February 2010
Craft Terminal for ES Management
Diagnosis and Alarms Configuration
............................................................................................................................................................................................................................................................
Diagnosis -> Navigation to EML-USM 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 52 Issue 05 February 2010
Craft Terminal for ES Management
MIB Management
............................................................................................................................................................................................................................................................
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.
An example of the displayed dialog window is reported in Figure 4-20, (pg. 4-53). 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-21, (pg. 4-54). 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-22, (pg. 4-54). 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-20 MIB management -> Backup/Restore DB
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-53 Issue 05 February 2010
Craft Terminal for ES Management
MIB Management
............................................................................................................................................................................................................................................................
Figure 4-21 Backup info boxes
Figure 4-22 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.
•
Help: to get helps about this function.
Compare two Backup Files Not operative in current release.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 54 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
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 dialog windows described in this handbook are reported in “Full Window" mode, the information fields reported in the “Tabbed Window" mode are the same as described in “Windows Presentation: “Full Window" and “Tabbed Window"” (p. 4-34).
WARNING ISA-ES16 supports (in mutually exclusive mode) the following workings modalities (see “Transmission -> ISA -> ISA Properties” (p. 4-74)): • General Bridge Management modalities: –
none: for “non-bridge" functions (ETS and MPLS)
–
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. 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-xxiv), 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 = z
Remote Ethernet Ports:
ETHRemPort#10q
Port Number = q
Note:
10q stands for 1000+q
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-55 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
ES16 board can manage: •
64 Remote ETH ports numbered 1001 to 1064 on ES-CT and 1 to 64 on SDH-CT;
•
14 Electrical Fast Ethernet Local ETH ports, numbered 65 to 78 on ES-CT (1 to 14 on SDH-CT), accessed by means of the Electrical Fast Ethernet Access Card.
•
4 Optical Gigabit Ethernet Local ETH ports, numbered 79 to 82 on ES-CT (1 to 4 on SDH-CT), accessed by means of the Gigabit Ethernet Access Card.
•
7 Optical Fast Ethernet Local ETH ports, numbered 83 to 89 on ES-CT (1 to 7 on SDH-CT), accessed by means of the Optical Fast Ethernet Access Card.
WARNING The local ethernet ports cannot be mixed, since the Access Card for Fast Ethernet and for Gigabit Ethernet are two different boards. On ES-CT the unusable Loc ETH ports are graphically represented by a different symbol.
WARNING The Local Ethernet Ports, on the front panel of the Access Cards, are numbered from the top to the down side of the board (1 to 4 for optical 1GE , 1 to 14 for electrical FE, 1 to 7 for optical FE ports).
WARNING In case of Access Card changing (between FE and GE), all existing resources must be set in down state, firstly, (or, in alternative, the Flash-card of ISA board can be formatted). Configuration -> Traffic Descriptor -> ETS Traffic Descriptor This option is obtained by selecting, in the menu-bar: Configuration -> Traffic Descriptor -> ETS Traffic Descriptor.
An example of the displayed dialog window is reported in Figure 4-23, (pg. 4-57). 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 56 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-23 Configuration: ETS Traffic Descriptor (example)
The parameters listed in Figure 4-23, (pg. 4-57) 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-58)). •
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-58). The keys presented at the bottom of Figure 4-23, (pg. 4-57) are: •
Create (see “Creating a new ETS Traffic Descriptor” (p. 4-58)), Details (see “To confirm the inserted values click on Ok button.” (p. 4-60)), Modify (see “Modifying an
ETS Traffic Descriptor” (p. 4-60)): to create a new Traffic Descriptor, or to get details about or to modify a Traffic Descriptor •
Delete: to delete the selected Traffic Descriptor
•
Close: to close the window
•
Print: to print details about the selected Traffic Descriptor
•
Help: to get helps about this function.
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).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-57 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Creating a new ETS Traffic Descriptor After clicking on Create key in the panel of Figure 4-23, (pg. 4-57), the following dialog is popped-up (example): Figure 4-24 Create an ETS Traffic Descriptor (example)
Referring to Figure 4-24, (pg. 4-58), 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)
–
Regulated Service3 - available only in Bridge Type = bridge 802.1S-AD (Provider)
–
Regulated Service4 - available only in Bridge Type = bridge 802.1S-AD (Provider)
–
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-24, (pg. 4-58): •
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 set 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. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 58 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
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. It is set 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.
WARNING In case of Bridge Type = bridge 802.1S-AD (Provider), the Best Effort traffic can be configured with CIR and CBS values different from zero, and differing from PIR and PBS. This same rule is valid for BackGround traffic. Thus it is “regulated”-like, but assigned to lower-priorities queues.
WARNING In case of Bridge Type = bridge 802.1S-AD (Provider), the Regulated Service (1, 3, and 4) 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-64).
WARNING In case of Bridge Type = none, CIR and PIR values must be lesser than SDH rate of the virtual container, in case of remote connection, otherwise the system will not permit the requested Cross Connection (CAC function).
WARNING In case of Bridge Type = bridge 802.1S-AD (Provider), the Guaranteed Service and Guaranteed Service2 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-64).
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 “Prioritization, S-VLAN, Policing, Color Profile, Scheduling” (p. 4-60) (Prioritization, Scheduling), “Configuration -> Traffic Descriptor -> MPLS Traffic Descriptor” (p. 4-67) (MPLS-TD), “MPLS Tunnel: Labelling and Bandwidth Matching” (p. 1-32) (Bandwidth matching).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-59 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
To confirm the inserted values click on Ok button. Getting details about ETS Traffic Descriptor After selecting a Traffic Descriptor and clicking on Details key as for Figure 4-23, (pg. 4-57), a dialog window similar to Figure 4-24, (pg. 4-58) 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-58). Modifying an ETS Traffic Descriptor After selecting a Traffic Descriptor and clicking on Modify key as for Figure 4-23, (pg. 4-57), a dialog as that in Figure 4-24, (pg. 4-58) 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-23, (pg. 4-57) will be recalled, then select the desired TD and click on Apply button. Prioritization, S-VLAN, Policing, Color Profile, Scheduling The prioritization of an Ethernet data flow can be indicated on the 3 “user-priority" bits (802.1p) of the VLAN-Tagged-Ethernet frame and also on the 3 “provider-priority" bits of the Stacked-VLAN frame; (see frames formats in “MAC-Ethernet Technique” (p. 1-7)). 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 Default User Priority (i.e. incoming frames, “untagged”, without priority information are forwarded with a unique priority value) or Regenerated User Priority (i.e. on “tagged” frames, incoming priority values are mapped versus outgoing priorities by using a configurable priority table), as described in “Bridge Port -> Regenerated User Priority List” (p. 4-170) and “Bridge Port -> Default User Priority” (p. 4-169) (in case Bridge Type = bridge 802.1D (MAC), the Default User Priority is possible only).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 60 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
The Priority bits, on the S-VLAN frames (available only in Bridge Type = bridge 802.1SAD (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-64). In Bridge Type = bridge 802.1S-AD (Provider) and none cases, the Prioritization and Classification modes on ETS ports are managed by means of the options Create ETS Inflow ( “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111)) and Create ETS Outflow ( “Transmission -> Ethernet Port -> Create ETS OutFlow” (p. 4-117)). 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-116)).
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" color is used for frames to be passed in any case, “yellow" color is used for frames to be passed if the band is available, “red" color 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. 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-64)). In case of Bridge Type = bridge 802.1D (MAC) or bridge 802.1Q (Virtual ) or none, the Queueing is fixed by default, into three queues, as indicated in “Traffic Scheduling in Provider Bridge case (ETB ports)” (p. 4-64). ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-61 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
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: –
Work Conserving: empty queues are skipped
–
Non Work Conserving: (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 “Transmission -> Ethernet Port -> Queue (QoS) -> Configure Queue” (p. 4-184). 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, “Transmission -> ISA -> Configure ISA” (p. 4-71)196; other two modes (7P1D and 6P2D) can be set in “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Provider)” (p. 4-159). The various PCP scheduling modes are illustrated in “Traffic Scheduling in Provider Bridge case (ETB ports)” (p. 4-64).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 62 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Traffic Scheduling in Virtual/MAC Bridge case Figure 4-25 ETB Virtual/MAC Bridge Scheduling Mode IN
BPDU
Regen. Ingress or ETBPort frames Default Prior.
OUT
SCHEDULER
Prior. Decod
Queue 3
Guar. (pr. 7,6)
Queue 2
Regul. (pr. 5,4)
Queue 1
BestEffort (pr. 3,2,1,0)
Queue 0
(pr. BPDU)
SP
(pr.7, 6)
Shaping
Egress ETBPort
(pr. 5,4) (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
The Table 4-2, (pg. 4-63). 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 BEST EFFORT
User Priority (802.1p) 0, 1, 2, 3
REGULATED
4, 5
GUARANTEED BPDU
6, 7
Provider-Class of Service Silver Service (into Low priority queue, Queue0) Gold Service (into Medium priority queue, Queue1) Network Service (into High priority queue, Queue2)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-63 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Traffic Scheduling in Provider Bridge case (ETB ports) Figure 4-26 Provider Bridge, 8P0D Scheduling Model IN
OUT
SCHEDULER BPDU
Regen. Ingress or ETBPort frames Default Prior.
PCP Decod
Queue 8
Guar. (pr. 7)
Queue 7
Guar.2 (pr. 6)
Queue 6
Reg.1 (pr. 5)
Queue 5
Reg. (pr. 4)
Queue 4
Reg.3 (pr. 3) Reg.4 (pr. 2) BE (pr. 0) BKG (pr. 1)
SP
Shaping
Egress ETBPort
W5
W4
DROP Queue 3 Queue 2
W3 W2
WDRR
W1
Queue 1 Queue 0
W0
DROP Note: Regenerated Priority is used 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 W0 to W5 are the weights values applied to differentiate the queues priorities. The queue with greater weight is emptied first SP: Strict Priority, highest priority queue is emptied first 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.
The same schema can be summarized as indicated in the following Table 4-3, (pg. 4-64). 8P0D-PCP decoding mode: (configurable per-Node and per-ETB Port) Table 4-3 Provider Bridge - Traffic Scheduling in 8P0D mode In-Pri
Traffic Type
Queue
7 6 5 4 3 2 0 1
Guar. Guar. 2 Regul. 1 Regul. Regul. 3 Regul. 4 Best Effort Background
Q7 Q6 Q5 Q4 Q3 Q2 Q1 Q0
Note:
Weight (default) 0 0 64 32 16 8 2 1
Que-Type
Out-Pri
SP SP WDRR WDRR WDRR WDRR WDRR WDRR
7 6 5 5 5 5 0 1
The default weights values can be changed by the operator.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 64 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
The other PCP scheduling modes (5P3D, 6P2D, 7P1D) can be obtained from the 8P0D model, as illustrated in the following pages. 5P3D-PCP Scheduling Mode: The 5P3D mode is obtained from the 8P0D scheduling model, by using only 5 Queues and three priorities combination for the yellow coloration of three classes of services. 5P3D-PCP decoding mode: (configurable per-Node and per-ETB Port) Table 4-4 Provider Bridge - Traffic Scheduling in 5P3D mode In-Pri 7 6 4, 5
Traffic Type Guar. Guar. 2 Regul.
2, 3
Regul. 4
0, 1
Best Effort
-
-
DP Green Green 5 = Green 4 = Yellow 3 = Green 2 = Yellow 1 = Green 0 = Yellow -
Queue Q7 Q6 Q5 (not used) Q4
Que-Type SP SP WDRR
Out-Pri 7 6 4, 5
Q3 (not used) Q2
WDRR
2, 3
Q1
WDRR
0, 1
Q0 (not used)
-
-
Note: DP (Discarding Precedence) column indicates the color 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.
In Regulated and Best Effort cases, the DP (green/yellow mark) is determined by CIR and PIR values: packets rated above PIR are marked red (to be discarded); rates between PIR and CIR are marked yellow; packets rated below CIR are marked green. Note:
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-65 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
6P2D-PCP Scheduling Mode: The 6P2D mode is obtained from the 8P0D scheduling model, by using only 6 Queues and two priorities combination for the yellow coloration of two classes of services. 6P2D-PCP decoding mode: (configurable only per-ETB Port) Table 4-5 Provider Bridge - Traffic Scheduling in 6P2D mode In-Pri 7 6 4, 5
Traffic Type Guar. Guar. 2 Regul.
2, 3
Regul. 4
0 1
Best Effort Background Note:
DP Green Green 5 = Green 4 = Yellow 3 = Green 2 = Yellow Green Green
Queue Q7 Q6 Q5 (not used) Q4
Que-Type SP SP WDRR
Out-Pri 7 6 4, 5
Q3 (not used) Q2
WDRR
2, 3
Q1 Q0
WDRR WDRR
0 1
DP (Discarding Precedence), described in the previous
table 7P1D-PCP Scheduling Mode: The 7P1D mode is obtained from the 8P0D scheduling model, by using only 7 Queues and one priority combination for the yellow coloration of one classes of services. 7P1D-PCP decoding mode: (configurable only per-ETB Port) Table 4-6 Provider Bridge - Traffic Scheduling in 7P1D mode In-Pri 7 6 4, 5
Traffic Type Guar. Guar. 2 Regul.
3 2 0 1
Regul. 3 Regul. 4 Best Effort Background Note:
DP Green Green 5 = Green 4= Yellow Green Green Green Green
Queue Q7 Q6 Q5 (not used) Q4
Que-Type SP SP WDRR
Out-Pri 7 6 4, 5
Q3 Q2 Q1 Q0
WDRR WDRR WDRR WDRR
3 2 0 1
DP (Discarding Precedence), described in the previous
table
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 66 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Configuration -> Traffic Descriptor -> MPLS Traffic Descriptor This option is obtained by selecting, in the menu-bar: Configuration -> Traffic Descriptor -> MPLS Traffic Descriptor.
An example of the displayed dialog window is reported in Figure 4-27, (pg. 4-67). Note:
This option is active only if Bridge Type = none.
The function of this option is to show the existing traffic descriptions related to the MPLS 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-27 Configuration: MPLS Traffic Descriptor (example)
The parameters listed in Figure 4-27, (pg. 4-67) are: •
Traffic Descriptor: 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-58)). •
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-58). The keys presented at the bottom of Figure 4-27, (pg. 4-67) are: •
Create (see “Creating a new ETS Traffic Descriptor” (p. 4-58)),
•
Details (see “Getting details about ETS Traffic Descriptor” (p. 4-60)),
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-67 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
Modify (see “Modifying an ETS Traffic Descriptor” (p. 4-60)):
•
to create a new Traffic Descriptor, or to get details about or to modify a Traffic Descriptor Delete: to delete the selected Traffic Descriptor
•
Close: to close the window
•
Print: to print details about the selected Traffic Descriptor
•
Help: to get helps about this function. Note:
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 MPLS Traffic Descriptor After clicking on Create key (Figure 4-27, (pg. 4-67)), the following dialog is popped-up (example): Figure 4-28 Create an MPLS Traffic Descriptor (example)
Referring to Figure 4-28, (pg. 4-68), 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: a. Default Behaviour Service (DE) to be associated to the ETS BestEffort Traffic (see “Creating a new ETS Traffic Descriptor” (p. 4-58)) b. Expedited Forwarding Service (EF) to be associated to the ETS GuaranteedService Traffic (see “Creating a new ETS Traffic Descriptor” (p. 4-58))
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 68 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
c. Assured Forwarding Service (AF1) to be associated to the ETS RegulatedService Traffic (see “Creating a new ETS Traffic Descriptor” (p. 4-58)) According to the Traffic Type, the following QoS parameters will be displayed in the dialog of Figure 4-28, (pg. 4-68): • CIR (kbits/sec): Committed Information Rate; range = 0 to PIR (expressed in kb/sec). It is the normal medium rate of the data flow. 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 (kbits/sec): Peak Information Rate; range = 64 to physical-line-rate (not greater than 1.2Gbps) 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 (bytes): Committed Burst Size (committed number of bytes for which the source may transmit the PIR); range = 0 to 67 MBytes; 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 PBS value. A value greater than MTU (e.g. 2000) is advisable. • PBS (bytes): Peak Burst Size (maximum number of bytes for which the source may transmit the PIR); range = 1 to 67 MBytes. A value greater than MTU (e.g. 2000) is advisable. Note: NOTE: for more details see also “Configuration -> Traffic Descriptor -> ETS Traffic Descriptor” (p. 4-56), “Prioritization, SVLAN, Policing, Color Profile, Scheduling” (p. 4-60) and “MPLS Tunnel: Labelling and Bandwidth Matching” (p. 1-32). To confirm the inserted values click on Ok button. Getting details about MPLS Traffic Descriptor After selecting a Traffic Descriptor and clicking on Details key (Figure 4-27, (pg. 4-67)), a dialog window similar to Figure 4-28, (pg. 4-68) 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 paragraph “Creating a new MPLS Traffic Descriptor” (p. 4-68). Modifying an MPLS Traffic Descriptor After selecting a Traffic Descriptor and clicking on Modify key (Figure 4-27, (pg. 4-67)), a dialog as that in Figure 4-28, (pg. 4-68) is popped-up. The displayed dialog permits to change only the name, in the Traffic Descriptor Name field.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-69 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Associating an MPLS Traffic Descriptor to a resource The TrafficDescriptor association to a resource is carried out from the options Configure or Modify... (a resource), in the Transmission context; e.g.: for an MplsTunnel configuration (in the Connection application), in the presented window there is the Traffic Descriptor field, where the desired TD can be configured: clicking on the [...] button, the window of Figure 4-27, (pg. 4-67) will be recalled, then select the desired TD and click on Apply button.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 70 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> ISA -> Configure ISA This option is obtained, after selecting the ISA-ES node ( contextual pop-up menu, or by selecting in the menu-bar:
), by means of the
Transmission -> ISA Management -> Configure ISA.
An example of the displayed dialog window is reported in Figure 4-29, (pg. 4-71).
WARNING To swap the Bridge Type, the de-activation of every underlying resource (Ethernet Ports, InFlows, OutFlows, etc.) is necessary, before the swapping. Some details about STP bridged network and relevant xSTP roles are reported in “Protocol list” (p. 1-50). The function of this option is to manage the transmission parameters of the selected ISAES 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) Figure 4-29 Configure ISA - System Info
•
Bridge Management sector: •
•
Bridge Type: (see note 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
Protocol Type: possible pull-down options:
–
STP: for simple Spanning Tree Protocol functions
–
RSTP: for Rapid Spanning Tree Protocol functions
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-71 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
–
RSTP+: for enhanced RSTP functions (not operative)
–
PERVLANSTP: for “per-VLAN" Spanning Tree Protocol functions; this option is not available in Bridge Type = bridge 802.1D (MAC) case.
–
MSTP: for “Multiple" Spanning Tree Protocol functions; this option is not available in Bridge Type = bridge 802.1D (MAC) case.
– •
•
Learning: (displayed only in Bridge Type = bridge 802.1D (MAC) case), to enable
or disable the “MAC-learning” function; possible pull-down options: enabled / disabled Fast Aging: (displayed only in Bridge Type = bridge 802.1D (MAC) case), to enable or disable the Fast-aging function (fast removal of an entry, after 100 sec, from Filtering Data Base (FDB), in case of FDB overload); possible pull-down options: – enabled: in case of FDB overload, an entry (expired or invalid, etc.) is deleted. –
•
manual Disable: to disable the Spanning Tree Protocol functions.
disabled: in case of FDB overload, the new entry is discarded.
PB Profile: (displayed only in case of Bridge Type = bridge 802.1S-AD (Provider)
case); 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 Scheduling in Virtual/MAC Bridge case” (p. 4-63), –
5P3D: see details in “Traffic Scheduling in Virtual/MAC Bridge case” (p. 4-63).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 72 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-30 Configure ISA - Bridge Management Provider Bridge case
MAC Bridge case
Virtual Bridge case
None case
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-73 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
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. Figure 4-31 Configure ISA - MIB Default Value
Transmission -> ISA -> ISA Properties This option is obtained, after selecting the ISA-ES node ( contextual pop-up menu, or by selecting in the menu-bar:
), by means of the
Transmission -> ISA Management -> ISA Properties.
An example of the window displayed is reported in Figure 4-32, (pg. 4-74). The function of this option is to show the transmission parameters set for the selected ISAES node. All the reported information fields are read-only, and are the same as those explained ones for “Transmission -> ISA -> Configure ISA” (p. 4-71). Figure 4-32 ISA Properties (example)
ISA: application table in the Transmission context An example of Application Table associated to the ISA-ES node is illustrated in Figure 4-33, (pg. 4-75). 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 three folders: Local Ethernet Ports, Remote Ethernet Ports and, PPP Ports. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 74 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
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". PPP Ports lists the main parameters related to this topic: “Alarms Synthesis", “Name", “Total Bandwidth (indicated by the supporting pipe)”, “Oper. Status", “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. Figure 4-33 ISA-ES node: transmission application table
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-75 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> Configure (LOCAL) Ethernet Port This option is obtained, after selecting a LOCAL Ethernet Port ( contextual pop-up menu, or by selecting in the menu-bar:
), by means of the
Transmission -> Ethernet Port Management -> Configure Ethernet Port.
An example of the window displayed (in Tabbed Window mode) is reported in Figure 4-34, (pg. 4-80) to Figure 4-38, (pg. 4-86). The function of this option is to manage the transmission parameters of the selected local Ethernet Port. The board ISA-ES16 supports: •
14 Electrical Fast Ethernet Local ETH ports, numbered 65 to 78 on ES-CT (1 to 14 on SDH-CT), accessed by means of the Electrical Fast Ethernet Access Card.
•
4 Optical Gigabit Ethernet Local ETH ports, numbered 79 to 82 on ES-CT (1 to 4 on SDH-CT), accessed by means of the Gigabit Ethernet Access Card.
•
7 Optical Fast Ethernet Local ETH ports, numbered 83 to 89 on ES-CT (1 to 7 on SDH-CT), accessed by means of the Optical Fast Ethernet Access Card.
WARNING •
The local ethernet ports FE and GE cannot be mixed, since the Access Card for Fast Ethernet and for Gigabit Ethernet are two different boards. On ESCT the unusable Loc ETH ports are graphically represented by a different symbol.
•
The Local Ethernet Ports, on the front panel of the Access Card, are numbered from the top to the down side of the board.
To configure a local Ethernet Port, fill fields and areas as follows: •
Configuration sector:
Refer to Figure 4-34, (pg. 4-80). • 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 ethernet Csmacd)
•
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; permitted values are ranged from a minimum of 1518 to a max value depending on the type of Port; in particular: – ETS: 2000; MPLS Over ETH: 2026; MAC/Virtual-ETB: 2000, Provider-ETB: 2026 Jumbo Frames are supported with a max MTU of 9600 on any port type.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 76 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
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 “Transmission -> Ethernet
Port/Aggregator -> Substitute Client Layer” (p. 4-153)), indicating the transported layer: – 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 “Transmission ->
Ethernet Port -> Characterization Service” (p. 4-103), indicating the Service for which this Port is dedicated: – 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: 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 (only in Bridge Type = none case).
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 Port-To-Port.
Traffic Enabled: (read only field, settable by means of “Transmission -> Ethernet
Port -> Traffic Management” (p. 4-103)), 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) cases (ref. to “Transmission -> ISA -> Configure ISA” (p. 4-71)). •
Admin. Status: Administration status, possible pull-down options:
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-77 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
–
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: – 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: 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.
Note:
It is allowed only if the above Client-Type parameter is
ets). •
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 dialog described in “Configuration -> Alarms Severity (ASAP management)” (p. 4-39) the
key gives the asap properties currently associated to this resource
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 78 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
Protocol Profile: (allowed only in Bridge Type = bridge 802.1S-AD (Provider)
case) name of the 2-bytes customer VLAN-protocol-type (PT) of the ethernet frames afferent to the current Port (incoming frames with different value will be discarded): the key permits to choose and associate a provider protocol-tag (PT) to this resource, recalling the dialog described in “Create Protocol Profile” (p. 4-86) the
key gives the Prot.-tag properties currently associated to this resource
•
Access Control List: (read only field, settable by means “Transmission -> Ethernet
•
Port -> ACL -> Configure ACL” (p. 4-104)), 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.
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-79 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-34 Configure (local) Ethernet Port - Configuration
•
MAU sector (ref. to Figure 4-35, (pg. 4-83): •
MAU Identifier: assigned by the system (read only field, fixed to “1")
•
Front Panel Port: assigned by the system; identifier of the physical port on the
• • •
front of the Access Card Type: symbolic name of the mau interface 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 signaling. It applies only in the case that the Auto Negotiation-Admin Status 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 80 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
–
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-73) and “FlowControl management” (p. 1-74). • •
•
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 “Loop-Back management” (p. 1-66) and “CSF alarm management” (p. 1-67). Note: The shut-down mechanism is supported only in P2P Connection (Port-to-Port).
•
Jabber State: (read only field); state of the jabber process (checking about
•
abnormal data transmissions longer than the max permissible packet length) Default Type: possible pull-down options: – 10BaseTFD: for E-10Mbps LAN (FD = Full Duplex) –
100BaseTXFD: for FE-100Mbps LAN
–
1000Base: for GE-1000Mbps LAN
•
Type List: list of available interfaces types
•
Auto Neg. Support: indicating if the auto-negotiation is supported; possible
values: true or false. • Fractional Rate: (only for 1GbE i/f), to indicate the value (in kb/s) at which the port rate is “throttled” down, in order to match with a connected remote Port on which its rate has been reduced as well, in order to fit over an SDH VCx transport container. Thus it is recommended that this value is congruent with the corresponding value indicated in “Transmission -> Ethernet Port -> Configure (REMOTE) Ethernet Port” (p. 4-90). Loop-Back sub-sector: •
Internal Loop-Back: possible pull-down options:
–
enabled: the internal LB (from Remote Port-Rx to Remote Port-Tx) is enabled (for more details see “Loop-Back management” (p. 1-66))
Note:
The enabling is available only in case of P2P (Point-toPoint) Connection. – •
disabled: Loopback disabling
Line Loop-Back: possible pull-down options:
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-81 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
–
enabled: the Line LB (from DTE to DTE) is enabled (for more details see “Loop-Back management” (p. 1-66))
–
disabled: Loopback disabling
Auto Negotiation sub-sector: Note:
Some details about AutoNegotiation and Flow Control are reported in “Auto-Negotiation management” (p. 1-73) and “FlowControl management” (p. 1-74).
•
Admin. Status: Administration status, possible pull-down options:
–
enabled: auto-neg. enabling
–
disabled: auto-neg. disabling
•
Remote Signaling: notification about the detection of auto-neg. remote signaling
•
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 Auto
Negotiation is active. If the AutoNeg is disabled, then the above parameter Default Pause is instead considered. It contains two fields: Available and Current, set of capabilities advertised by the local auto-negotiation for Flow Control signaling (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.
–
for 10Mbps case, Asymmetric FC: select: b10baseTFD, bFdxAPause and bFdxPause.
–
for 10Mbps case, Symmetric FC: select: b10baseTFD, bFdxSPause and bFdxPause.
–
for 1000Mbps case, Asymmetric FC: select: b1000baseXFD, bFdxAPause and bFdxPause.
–
for 1000Mbps case, Symmetric FC: select: b1000baseXFD, bFdxSPause and bFdxPause.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 82 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
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-35 Configure (local) Ethernet Port - MAU
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-83 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
L2 Control Frame sub-sector (ref. to Figure 4-36, (pg. 4-84)): (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), as referred
in “Protocols” (p. 1-43), 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.
Figure 4-36 Configure (local) Ethernet Port - L2 Control Frame
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 84 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
Port Mirroring sector:
Refer to Figure 4-37, (pg. 4-85). 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-76). Some details about this feature are reported in “Link Aggregation management” (p. 1-81). 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 “Views -> Search” (p. 4-35). Ports to be mirrored must be active and in service. Figure 4-37 Configure (local) Ethernet Port - Port Mirroring
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-85 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
Alarms sector (ref. to Figure 4-38, (pg. 4-86) ):
This group reports the alarms relevant to the Ethernet Port; their color is green if notalarmed, 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-38 Configure (local) Ethernet Port - Alarms
After setting all the desired parameters, click on the Ok key to send the chosen parameters to the Ethernet Port. 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-34, (pg. 4-80), after clicking on the key of the Protocol Profile item. An example of the window displayed is reported in Figure 4-39, (pg. 4-87).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 86 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
The function of this option is to manage the Protocol Profiles to be associated to the Ethernet Ports resources. The Protocol Profile 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-26, (pg. 1-45). 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 Protocol Profile as explained below;
•
the Details button, permitting to see the properties of an existing Protocol Profile;
•
the Modify button, permitting to change the name of an existing Protocol Profile;
•
the Delete button, permitting to delete an existing Protocol Profile;
•
the Apply button, permitting “to bind" the selected Protocol Profile to the related port;
•
the Cancel button, permitting to close the window without associating a Protocol Profile;
•
the Print button, permitting to print the properties of a selected Protocol Profile;
•
the Help button, permitting to have information about this current function.
Figure 4-39 List of Protocol Profile
To create a Protocol Profile, click on Create key as shown in Figure 4-39, (pg. 4-87) and then the dialog box indicated in Figure 4-40, (pg. 4-88) will be displayed; fill fields and areas as follows: •
Protocol Profile Name: type a mnemonic name
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-87 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
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 “SVLAN-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-SVLANtagged. 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 Protocol Profile;
–
click on the Cancel button, to close the dialog without saving the new Protocol Profile;
–
click on the Help button, to get information about this window.
Figure 4-40 Create Protocol Profile
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 88 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> (LOCAL) Ethernet Port Properties This option is obtained, after selecting a Local Ethernet Port ( the contextual pop-up menu, or by selecting in the menu-bar:
or
), by means of
Transmission -> Ethernet Port Management -> Ethernet Port Properties.
An example of the window displayed is reported in Figure 4-41, (pg. 4-89). The function of this option is to show the transmission parameters set for the selected local Ethernet port. All the reported information fields are read-only, and are the same as those explained ones for “Transmission -> Ethernet Port -> Configure (LOCAL) Ethernet Port” (p. 4-76), except for the following extra field, displayed in the Configuration sector: •
ETH.Avail.Bandwidth (kbs): remaining bandwidth that is not yet occupied by
“children" resources (in kb/s) Figure 4-41 (Local) Ethernet Port Properties
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-89 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> Configure (REMOTE) Ethernet Port This option is obtained, after selecting a REMOTE Ethernet Port ( contextual pop-up menu, or by selecting in the menu-bar:
), by means of the
Transmission -> Ethernet Port Management -> Configure Ethernet Port.
An example of the window displayeds are reported from Figure 4-42, (pg. 4-93) to Figure 4-46, (pg. 4-96). Note:
The switch between GFP and LAPS framing type is done by means of “Transmission -> Ethernet Port -> Substitute Server Layer” (p. 4-102).
The function of this option is to manage the transmission parameters of the selected remote Ethernet Port. The ISA-ES16 board supports 64 Remote ETH ports numbered 1001 to 1064 on ES-CT corresponding to 1 to 64 on SDH-CT.
WARNING Before doing this operation, the user should have done, on SDH-CT application, the configuration of this same port, defining its SDH specific container. See also the note in “Inconsistency error on Port configuration” (p. 4-100). To configure a remote Ethernet Port, fill fields and areas as follows: •
Configuration sector (ref. to Figure 4-42, (pg. 4-93): •
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 MTU: Maximum Transmit Unit; size of the largest packet which can be sent/received on the interface, specified in octets, permitted values are ranged from a minimum of 1518 to a max value depending on the type of Port; in particular: – ETS: 2000; MPLS Over PPP: 2012; MPLS Over GFP: 2016; MAC/VirtualETB: 2000, Provider-ETB: 2026. Jumbo Frames are supported with a max MTU of 9600 on any port type.
•
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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 90 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
Client Type: (read only field), set by means of Substitute Client Layer), indicating
the transported layer: – ets: for Ethernet Transparent System – •
etb: for Ethernet Bridge System
ETS Service Type: (read only field, settable by means of “Transmission ->
Ethernet Port -> Characterization Service” (p. 4-103)), indicating the Service for which this Port is dedicated: – portToPort: in this case it supports only Port-To-Port connections
•
•
•
–
other: in this case it is ETB port, or supports UNI-Bridged connections
–
ETSVirtSw: in this case it is used for ETS Virtual Switch connections (only in Bridge Type = none case).
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 Port-To-Port.
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 – •
•
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 (read only field, set by the system). 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 –
•
down: the port is unavailable
disabled: possible only on ETS ports; 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-91 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
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 dialog described in “Configuration -> Alarms Severity (ASAP management)” (p. 4-39) the •
key gives the asap properties currently associated to this resource
Protocol Profile: (allowed only in Bridge Type = bridge 802.1S-AD (Provider)
case) name of the 2-bytes customer VLAN-protocol-type (PT) of the ethernet frames afferent to the current Port (incoming frames with different value will be discarded): the key permits to choose and associate a provider protocol-tag (PT) to this resource, recalling the dialog described in “Create Protocol Profile” (p. 4-86) •
Access Control List: (read only field, settable by means of “Transmission ->
•
Ethernet Port -> ACL -> Configure ACL” (p. 4-104)), 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: – true (default value) indicates the interface is enabled to transmit broadcast traffic, –
•
false value indicates the interface is denied to transmit broadcast traffic.
Unknown Traffic: specifies 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.
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 “Rate limiting and Virtual Concatenation Setting” (p. 4-97). • Concatenation Type Set: available only if Underlying Layer = 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 Underlying Layer = 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 92 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
– •
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 dialog described in “Rate limiting and Virtual Concatenation Setting” (p. 4-97). –
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-42 Configure (remote) Ethernet Port - Configuration
•
GFP sector, displayed only if the port is GFP type ( Figure 4-43, (pg. 4-94)): • •
• •
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-nonspecific" code). TxSL / RxSL / ExpSL: Signal Label management (Tx = transmitted, Rx = received, Exp = expected). Transmit Capability: management of alarms CSF (Client Signal Fail) and VC-AIS
(SDH Virtual Container- Alarm Indication Signal). For details see “CSF alarm management” (p. 1-67) and “VC-AIS alarm management” (p. 1-70). Possible options: – disabled: alarms management is not managed ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-93 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
–
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-67).
–
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-70).
–
Backward (and Backward UPI-LOF): not supported in current release.
Figure 4-43 Configure (remote) Ethernet Port - GFP
•
L2 Control Frame sector (ref. to Figure 4-44, (pg. 4-95): (not displayed in case of
ETB port) it permits to enable or disable the Protocol Frames that can accede to this port:
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 94 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
Protocol List: it reports all the available Protocol frames (Bit Name), as referred in
“Protocols” (p. 1-43), 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.
Figure 4-44 Configure (remote) Ethernet Port - L2 Control Frame
•
Alarms sector: (see Figure 4-45, (pg. 4-96):
This group reports the alarms relevant to the Ethernet Port; their color is green if notalarmed, if alarmed their color will be congruent with the severity assigned in the associated ASAP; the alarms colors are described in Chapter 5, “Maintenance”.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-95 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-45 Configure (remote) Ethernet Port - Alarms
•
LAPS sector, displayed only if the port is LAPS type (Figure 4-46, (pg. 4-96)): • •
•
Flag Ins.: insertion of Flag byte in the LAPS frame; possible pull-down options:
single (means consecutive frames) or two (means non-consecutive frames). Send Control: assignment of Signal Label code (SL inserted into LAPS frame); possible pull-down options: automatic (means the tx SL shall be automatically calculated) or forced (means the tx SL will be always forced to the “equipped-nonspecific" code). TxSL / RxSL / ExpSL: Signal Label management (Tx = transmitted, Rx = received, Exp = expected).
Figure 4-46 Configure (remote) Ethernet Port - LAPS
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 96 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
After setting all the desired parameters, click on the Ok key to send the chosen parameters to the Ethernet Port. The window will be closed without doing any operation by clicking on Cancel key. The Help key gives helps about this function. Rate limiting and Virtual Concatenation Setting This option is obtained, in the Configure (remote) Ethernet Port window, shown in Figure 4-42, (pg. 4-93), after clicking on the key of the Bandwidth item.
WARNING Before doing this operation, the user should have done, on SDH-CT application (with ISA Port Configuration option), the configuration of this same port, defining its SDH specific container. See also the note in “Inconsistency error on Port configuration” (p. 4-100). The user is recommended to configure the Ethernet-bandwidth and the SDHcontainers in a congruent mode. For more details see: “Configuration -> Traffic Descriptor -> ETS Traffic Descriptor” (p. 4-56), “Prioritization, SVLAN, Policing, Color Profile, Scheduling” (p. 4-60), “Configuration -> Traffic Descriptor -> MPLS Traffic Descriptor” (p. 4-67), and “MPLS Tunnel: Labelling and Bandwidth Matching” (p. 1-32). 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 Virtual Concatenation 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 (Best Effort traffic), a single afferent flow's PIR must not exceed that limit. The window displayed is different, depending on the Underlying Layer parameter. –
If Underlying Layer = SDH (Rate Limiting): a window as Figure 4-47, (pg. 4-99) will be displayed.
–
If Underlying Layer = vconc (Virtual Conc): a window as Figure 4-48, (pg. 4-100) will be displayed.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-97 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
1. Rate Limiting case (Figure 4-47, (pg. 4-99)). 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 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 SDH-CT), 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 SDH-VC = VC4, the possibilities are: 149,760,000; 100,000,000 –
if SDH-VC = VC3, the possibilities are: 48,384,000; 10,000,000
–
if SDH-VC = VC12, the possibilities are: 2,176,000
Furthermore it contains: • the Ok button, permitting “to bind" the selected Rate Limiting to the related port; • the Cancel button, permitting to close the window without associating a Rate Limiting; • the Help button, permitting to have information about this current function.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 98 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-47 Rate Limiting Combination example (VC4 case)
2. Virtual Concatenation Granularity case (Figure 4-48, (pg. 4-100)). The function of this option is to manage the Virtual Concatenation Granularity to be associated to the current remote Ethernet Port. It is used to transport ethernet frames when ports at rates higher than an available SDH container are interworking. E.g. if a 1Gbps port is connected to a 1Gbps port by means of VC4 SDH links, then a concatenation of 7 VC4 (VC4kb-7v) is needed. 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: – Vconc Granularity: permitting to set the number (n) of concatenated containers, depending on the type of concatenated VC chosen at the SDH side: if SDH-VC = VC4, then n_max = 8 if SDH-VC = VC3, then n_max = 12 if SDH-VC = VC12, then n_max = 63 –
VCi: Total Vconc Bandwidth: (VCi = VC12 or VC3 or VC4); indicating the total concatenated bandwidth
–
SDH Bandwidth: indicating the actual, configured and active SDH bandwidth.
Furthermore it contains: •
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;
•
the Help button, permitting to have information about this current function.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4-99 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-48 Virtual Concatenation Granularity example (MII, VC12 case)
Inconsistency error on Port configuration
WARNING In case that the selected port has not been configured on SDH-CT 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-49 Inconsistency error on Port Configuration
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 10 0 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> (REMOTE) Ethernet Port Properties This option is obtained, after selecting a Remote Ethernet Port ( of the contextual pop-up menu, or by selecting in the menu-bar:
or
), by means
Transmission -> Ethernet Port Management -> Ethernet Port Properties.
An example of the window displayed is reported in Figure 4-50, (pg. 4-101). The function of this option is to show the transmission parameters of the selected remote Ethernet port. All the reported information fields are read-only, and are the same as those explained in “Transmission -> Ethernet Port -> Configure (REMOTE) Ethernet Port” (p. 4-90), except for the following extra field, displayed in the Configuration sector: •
Eth.Avail.Bandwidth (kbs): remaining bandwidth that is not yet occupied by
“children" resources (in kb/s) Figure 4-50 (Remote) Ethernet Port Properties
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 0 1 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> Substitute Server Layer This option is obtained, after selecting a remote Ethernet Port ( with Admin Status = 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-51 and Figure 4-52. This option permits to switch the server layer where the ethernet frames are encapsulated, between GFP over SDH and LAPS over SDH. Figure 4-51 Substitute Server Layer (from GFP to LAPS)
Figure 4-52 Substitute Server Layer (from LAPS to GFP)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 10 2 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> Characterization Service This option is obtained, after selecting a Local or Remote Ethernet Port ( with Admin Status = 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): available only in Bridge Type = none case. It allows 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. Transmission -> Ethernet Port -> Traffic Management 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 Aggregated Port (when an ETB-AggrPort 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: •
Auto negotiation parameters, MTU/MRU, Prototypal (i.e. “protocol-profile”).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 0 3 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Aggregator -> Traffic Management 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 “Transmission -> Ethernet Port -> Traffic Management” (p. 4-103). Transmission -> Ethernet Port -> ACL -> Configure ACL 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.
An example of the window displayed is reported in Figure 4-53, (pg. 4-104).
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 “Ethernet Port -> Configure ACL / ACL setting” (p. 4-105). Figure 4-53 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. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 10 4 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Ethernet Port -> Configure ACL / ACL setting This option is obtained, in the previous Configure ACL window, after clicking on the key of the ACL Index item. An example of the window displayed is reported in Figure 4-54, (pg. 4-106). 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-107). 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 8DG15624AAAA 4- 1 0 5 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-54 ACL list setting
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 10 6 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Ethernet Port -> Configure ACL / ACE management This option is obtained, in the previous ACL management window, after clicking on the Configure key. An example of the window displayed is reported in Figure 4-55, (pg. 4-109). 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-54, (pg. 4-106) 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. –
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 0 7 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
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 “Protocols” (p. 1-43)). •
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 VLANuntagged. •
ETHer. Type Range: not supported.
•
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
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. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 10 8 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
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.
Figure 4-55 ACL/ACE setting
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 0 9 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> ACL -> Properties ACL 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 menubar: Transmission -> Ethernet Port Management -> ACL Management-> Properties ACL.
An example of the window displayed is reported in Figure 4-56, (pg. 4-110). 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 “Transmission -> Ethernet Port -> ACL -> Configure ACL” (p. 4-104). Figure 4-56 Port: ACL Properties
Transmission -> Ethernet Port -> ACL -> Disassociate ACL 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. 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-57, (pg. 4-111) The function of this option is to disassociate the ACL profile that has been set for the selected Port.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 11 0 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-57 Port: Disassociate ACL
Transmission -> Ethernet Port -> Create ETS InFlow 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 pop-up menu, or by selecting in the menu-bar: 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 Admin Status = up.
WARNING His creation must be done in one single step by means of the Connection wizard. See “Connection -> Ethernet Port -> Create ETS XC One Step (MAC & Virtual)” (p. 4-264) and subsequents. The scope of this paragraph is to describe the settings and meanings of the resource parameters. An example of the window displayed is reported in Figure 4-58, (pg. 4-114). 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) 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 1 1 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
Traffic Descriptor indicating the name of the associated traffic descriptor (TD). (See
warning below. For other details see “Prioritization, S-VLAN, Policing, Color Profile, Scheduling” (p. 4-60): the key permits to choose and associate a traffic descriptor to the data flow, recalling the dialog described in “Configuration -> Traffic Descriptor -> ETS Traffic Descriptor” (p. 4-56). 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 “Configuration -> Traffic Descriptor -> ETS Traffic Descriptor” (p. 4-56) and “MPLS Tunnel: Labelling and Bandwidth Matching” (p. 1-32)). •
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
WARNING Only one type of classification Mode is allowed, per port (i.e. all “dscpInflows” or all “priority-Inflows” in a port). •
VLAN Pop: possible values: disabled or enabled; if enabled it pops out the “provider
Stacked-VLAN" shim fields of the ethernet frame.
WARNING If this is enabled, the Priority field of the relevant Classifier must be different from “untagged" or “don't care". •
Color Profile: indicating the name of the association between the user-priorities and
the Provider-priority;
WARNING If a Color Profile is associated, the Priority field of the relevant Classifier must be different from untagged or don't care. the key permits to choose and associate a color profile, recalling the dialog described in “Transmission -> Ethernet Port -> Create InFlow/Color Profile” (p. 4-114) the key gives the properties of the color profile currently associated the Unbind key permits to untie the data flow from the color profile ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 11 2 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
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
–
color-blind: the policing is based on the associated TD,
–
color-aware: the policing is based on the associated TD and on the priority colors of the associated Color Profile explained below
Flow Type: possible options:
–
unicastNoAutolearning: for unicast link
–
multicastOptionA: (not available in current release) for multicast cross-connection link
•
Service Id: (set by the system); indicating the suffix number of the mother-port
•
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), as referred in “Protocols” (p. 1-43), 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. Important! More information about the traffic description,
Policing, Color Profile is reported in “Traffic Descriptor, Policing Mode and Color Profile for ETS InFlow” (p. 4-116). Important! More information about the traffic description is reported in “Prioritization, S-VLAN, Policing, Color Profile, Scheduling” (p. 4-60).
WARNING Under the same mother ETH. Port, all the inflows in color-aware mode must have the same Color Profile; i.e. only one Color Profile 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 1 3 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-58 Create ETS InFlow
Transmission -> Ethernet Port -> Create InFlow/Color Profile This option is obtained, in the Create ETS Inflow window as depicted in Figure 4-58, (pg. 4-114), after clicking on the key of the Color Profile item. An example of the window displayed is reported in Figure 4-59, (pg. 4-115). 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. Furthermore it contains: •
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;
•
the Help button, permitting to have information about this current function. 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-116).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 11 4 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-59 List of Color Profile
To create a Color Profile, click on Create key (Figure 4-59, (pg. 4-115)) and then the dialog box indicated in Figure 4-60 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”
•
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-60 Create Color Profile
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 1 5 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Traffic Descriptor, Policing Mode and Color Profile for ETS InFlow Table 4-7 Traffic Descriptor, Policing Mode and Color Profile for INFLOW resource: Traffic Descriptor
Policing Mode
Color Profile(1)
“disabled" BEST EFFORT
Scheduler-Color (2) YELLOW
only “Unbound" “color-blind"
YELLOW or RED
“disabled" GUARANTEED
GREEN only “Unbound"
“color-blind"
GREEN or RED “Unbound"
GREEN
“Bound" (3)
GREEN or YELLOW
“color-blind"
“Unbound"
GREEN or YELLOW or RED
“color-aware"
“Bound" (3)
as assigned by the “Color Profile"
“disabled" REGULATED
Notes on Table 4-7. See “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111). 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 8DG15624AAAA 4 - 11 6 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> Create ETS OutFlow This option is obtained, after selecting an ETS Remote or Local Ethernet 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 -> Create ETS OutFlow.
This description applies also in case of LAG (when an ETB-LAG has been selected): Transmission ->Aggregator -> Create ETS OutFlow.
WARNING The option is available only if the selected ethernet port is ETS type (and not ETB), with Admin Status = up.
WARNING This creation must be done in one single step by means of the Connection wizard. See“Connection -> Ethernet Port -> Create ETS XC One Step (MAC & Virtual)” (p. 4-264) and “Connection -> Ethernet Port -> Create ETS XC One Step (Provider)” (p. 4-267). The scope of this paragraph is to describe the settings and meanings of the resource parameters. An example of the window displayed is reported in Figure 4-61, (pg. 4-118). The function of this option is to create an OutFlow resource into the selected ETS Ethernet Port. 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 •
User Label: optional name assigned by the user to describe this resource
•
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
–
down: the resource is out-of-service
VLAN Management: automatic incremental index identifying the Stacked-VLAN-
management profile; value “0" means that the SVLAN-management is disabled (“Unbound"): in this case the Stacked-VLAN shim header is not “pushed" into the ethernet frame. The relation among OuFlow prioritization and VLAN management is
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 1 7 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
reported in “Prioritization for OUTFLOW resource with “Stacked-VLAN Management”” (p. 4-120). (For other details see “Prioritization, S-VLAN, Policing, Color Profile, Scheduling” (p. 4-60)); the key permits to choose and associate a VLAN-management profile, recalling the dialog described in “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111) 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: The relation among OutFlow prioritization and VLAN management is reported in “Prioritization for OUTFLOW resource with “Stacked-VLAN Management”” (p. 4-120). Note:
More information about the traffic description, is reported in “Prioritization, S-VLAN, Policing, Color Profile, Scheduling” (p. 4-60).
WARNING In case of Multicast (not yet available), all the multi-casted outflows must have the same SVLAN-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. The window will be closed without doing any operation by clicking on Cancel key. The Help key gives helps about this function. Figure 4-61 Create ETS OutFlow
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 11 8 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Create ETS OutFlow / VLAN Management This option is obtained, in the Create ETS Outflow window depicted in Figure 4-61, (pg. 4-118), after clicking on the key of the VLAN Management item. An example of the window displayed is reported in Figure 4-62, (pg. 4-120). 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-Shim Header) to the ethernet frame. To create a SVLAN-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 that will be pushed into the ethernet frame;
range = 0 to 4095 •
Priority Mode: (see details in“Prioritization, S-VLAN, Policing, Color Profile,
Scheduling” (p. 4-60)); 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 color is identified by attaching, to the ethernet frames, the priority value selected into the Stack Priority field
–
the “yellow" Provider's color 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-color; possible
options: – •
pri000 to pri111 (min. priority = “pri000", max = pri111)
Stack Priority Yellow: as above, but referred to the priority value to be associated with
“yellow" provider-color •
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 “Prioritization, S-VLAN, Policing, Color Profile, Scheduling” (p. 4-60). After setting the desired parameters, click on the Ok key to create this new VLANManagement profile. The window will be closed without doing any operation by clicking on Cancel key. The Help key gives helps about this function. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 1 9 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Important!
When this window is recalled by the “Create XC One Step" ( “Connection -> Ethernet Port -> Create ETS XC One Step (MAC & Virtual)” (p. 4-264) and subsequents), it reports a further key: Reset, in order to detach the S-VLAN. Figure 4-62 Create VLAN Management
Prioritization for OUTFLOW resource with “Stacked-VLAN Management” Table 4-8 Prioritization for OUTFLOW resource with “Stacked-VLAN Management" Stacked-VLAN Management “Unbound"(1)
Priority Mode “color blind"
VLAN Provider-Prioritization no provider-prioritization the frames are passed without any information about Provider's colors • green packets are assigned to the priority as
“Bound"(1) “color aware"
Note on:
defined into the “Stack Priority" field •
yellow packets are assigned to the priority as defined into the “Stack Priority Yellow" field
Table 4-8.
See “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111). 1.
Unbound means that “0" value is associated to the VLAN Management field, or the Unbind key has been clicked; Bound means that a VLAN-management profile has been assigned to this Outflow: in this case the Stacked-VLAN “shim" header is “pushed" into the ethernet frame.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 12 0 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> Create Provider InFlow This option is obtained, after selecting an ETS Remote or Local Ethernet 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 -> Create Provider InFlow.
This description applies also in case of LAG (when an ETB-LAG has been selected): Transmission ->Aggregator -> Create Provider InFlow.
WARNING The option is available only if the selected ethernet port is ETS type (and not ETB), with Admin Status = up; further the Bridge Type = bridge 802.1S-AD (Provider).
WARNING This creation must be done in one single step by means of the Connection wizard: see “Connection -> Ethernet Port -> Create ETS XC One Step (Provider)” (p. 4-267). The scope of this paragraph is to describe the settings and meanings of the resource parameters. The window displayed is reported in Figure 4-63, (pg. 4-122). The function of this option is to create an InFlow resource into the selected ETS Ethernet Port, 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
•
User Label: optional name assigned by the user to describe this resource
•
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 dialog described in “Configuration -> Traffic Descriptor -> ETS Traffic Descriptor” (p. 4-56). 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 ;
–
down: the resource is out-of-service
Service Id: (set by the system); indicating the suffix number of the mother-port
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 2 1 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
•
•
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: the policing is based on the associated TD and on the priority colors of the associated Color Profile.
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 dialog described in “Create Provider InFlow / S-VID Management” (p. 4-122). Figure 4-63 Create Provider InFlow
Create Provider InFlow / S-VID Management This option is obtained as described in the “Transmission -> Ethernet Port -> Create Provider InFlow” (p. 4-121), or “Transmission -> Ethernet Port -> Create Provider OutFlow” (p. 4-123), 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 StackedVLAN (provider-Shim Header) 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 12 2 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-64 Provider Inflow: S-VID Filter
Transmission -> Ethernet Port -> Create Provider OutFlow This option is obtained, after selecting an ETS Remote or Local Ethernet 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 -> Create Provider OutFlow.
This description applies also in case of LAG (when an ETB-LAG has been selected): Transmission -> Aggregator -> Create Provider OutFlow.
WARNING The option is available only if the selected ethernet port is ETS type (and not ETB), with Admin Status = up; further the Bridge Type = bridge 802.1S-AD (Provider).
WARNING This creation must be done in one single step by means of the Connection wizard: see “Connection -> Ethernet Port -> Create ETS XC One Step (Provider)” (p. 4-267). The scope of this paragraph is to describe the settings and meanings of the resource parameters. The window displayed is reported in Figure 4-65, (pg. 4-124). The function of this option is to create an OutFlow resource into the selected ETS Ethernet Port, 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 •
User Label: optional name assigned by the user to describe this resource
•
Server Type: upper layer service type (read only field): ProviderBridge
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 2 3 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
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
•
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 dialog described in “Create Provider InFlow / S-VID Management” (p. 4-122). Figure 4-65 Create Provider OutFlow
Transmission -> ETS InFlow -> 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 “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111). It contains, further, in the Protocol List, the extra field Actual Status. Transmission -> ETS InFlow -> ETS InFlow Properties 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 -> 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 “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111). It contains, further, in the Protocol List, the extra field Actual Status. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 12 4 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> ETS OutFlow -> 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. The function of this option is to modify the transmission parameters set for the selected OutFlow point. All the reported information fields are the same as those explained ones for “Transmission -> Ethernet Port -> Create ETS OutFlow” (p. 4-117). Transmission -> ETS OutFlow -> ETS OutFlow Properties 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 -> ETS OutFlow Properties. The function of this option is to show the transmission parameters set for the selected OutFlow point. All the reported information fields are read-only, and the same as those explained ones for “Transmission -> Ethernet Port -> Create ETS OutFlow” (p. 4-117). Transmission -> ETS InFlow -> Delete ETS InFlow This option is obtained, after selecting an InFlow object ( contextual pop-up menu, or by selecting in the menu-bar:
), by means of the
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. An example of the window displayed is reported in Figure 4-66, (pg. 4-126). This option permits to delete the selected InFlow point.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 2 5 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-66 Delete ETS InFlow
Transmission -> ETS OutFlow -> Delete ETS OutFlow This option is obtained, after selecting an OutFlow object ( contextual pop-up menu, or by selecting in the menu-bar:
), by means of the
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-66, (pg. 4-126). This option permits to delete the selected OutFlow point. Transmission -> ETS InFlow -> Create ETH2ETS Classifier This option is obtained, after selecting an ETS InFlow object ( contextual pop-up menu, or by selecting in the menu-bar:
), by means of the
Transmission -> ETS InFlow Management -> Create ETH2ETS Classifier.
WARNING This creation must be done in one single step by means of the Connection wizard: see“Connection -> Ethernet Port -> Create ETS XC One Step (ETS & MPLS Tunnel-Head)” (p. 4-254) and subsequents. The scope of this paragraph is to describe the settings and meanings of the resource parameters.
WARNING The creation of the classifier is not possible if the InFlow is part of an MPLS Tunnel or if the inflow is a “PB InFlow”. An example of the window displayed is reported in Figure 4-67, (pg. 4-129).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 12 6 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
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 Topology Class
field. •
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’t Care; 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
Important! In cases that the related InFlow has been set with VLAN-Pop = enabled or Color Profile = bound, then this value
must be different from don’t Care 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 Topology Class = 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 Classification Mode = priority) to indicate that the IP-DSCP field is not considered, either if present or not present. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 2 7 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Note:
This item is active only when the above item (Priority) is set to don’t Care 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. Possible values: priority
or dscp) •
•
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. •
Max IP Dscp: max IP Dscp value associable to this classifier, in decimal format; value '0' means only one priority, a value greater than the value set in IP Dscp field defines
the IP Dscp 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: ETH Type, and the other parameters will be fixed to set the frame as “untagged”
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 12 8 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
–
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 don’t Care.
in case of Classification Mode = “dscp”: –
Untagged+IP_DSCP: in this case, the following parameters are editable, in the dialog box: IpDscp or MaxIpDscp.
–
VLAN+IP_DSCP: in this case, the following parameters are editable, in the dialog box: VLAN or MaxVLAN, IpDscp or MaxIpDscp.
–
Untagged/No_IP: in this case, no parameter is editable, and the other parameters will be fixed to set the frame as untagged
–
VLAN/No_IP+ETHType: in this case, the following parameters are editable, in the dialog box: VLAN or MaxVLAN, ETHType.
–
Untagged/No_IP+ETHType: in this case, the following parameters are editable, in the dialog box: ETH Type, and the other parameters will be fixed to set the frame as untagged.
–
VLAN/No_IP: in this case, the following parameters are editable, in the dialog box: VLAN or MaxVLAN
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. The window will be closed without doing any operation by clicking on Cancel key. The Help key gives helps about this function. Figure 4-67 Create ETH2ETS Classifier
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 2 9 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Classifier -> Modify Classifier This option is obtained, after selecting a Classifier object ( ), by means of the contextual pop-up menu, or by selecting in the menu-bar: Transmission -> Classifier Management -> Modify Classifier. The function of this option is to modify the transmission parameters set for the selected Classifier point. All the reported information fields are the same as those explained ones for “Transmission -> ETS InFlow -> Create ETH2ETS Classifier” (p. 4-126). Transmission -> Classifier -> Classifier Properties This option is obtained, after selecting a Classifier object ( ), by means of the contextual pop-up menu, or by selecting in the menu-bar: Transmission -> Classifier Management -> Classifier Properties. The function of this option is to show the transmission parameters set for the selected Classifier point. All the reported information fields are read-only, and the same as those explained ones for “Transmission -> ETS InFlow -> Create ETH2ETS Classifier” (p. 4-126). Transmission -> Classifier -> Delete Classifier This option is obtained, after selecting a Classifier object ( ), by means of the contextual pop-up menu, or by selecting in the menu-bar: Transmission -> Classifier Management -> Delete Classifier. The window displayed is similar to that reported in Figure 4-66, (pg. 4-126). 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 8DG15624AAAA 4 - 13 0 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> Substitute Ethernet -> PPP This option is obtained, after selecting a Remote Ethernet Port ( with Admin Status = down), by means of the contextual pop-up menu; or by selecting, in the menu-bar: Transmission -> Ethernet Port Management -> Substitute Ethernet -> PPP.
An example of the window displayed is reported in Figure 4-68, (pg. 4-131). Important! This option is active only if the Bridge Type = none.
The function of this option is to substitute a remote ethernet port with a PPP port. The remote ethernet port will be changed into a ppp port, by clicking on the Yes button, and then a new PPP port will be visualized in the bottom side of the resource tree, where the ppp ports are grouped. In this way the port will manage Ethernet over MPLS over SDH transportation. Figure 4-68 Substitute Ethernet -> PPP
Transmission -> PPP Port -> Substitute PPP -> Ethernet This option is obtained, after selecting a PPP Port ( with Admin Status = down), by means of the contextual pop-up menu; or by selecting, in the menu-bar: Transmission -> PPP Port Management -> Substitute PPP -> Ethernet. Important! This option is active only if the Bridge Type = none.
It contains two sub-options (not available in current release): •
On GFP Standard: in this case the ethernet packets will be encapsulated into the
standard GFP frame (refer to ITU-T G.7041 Rec.) •
On GFP Proprietary: in this case the ethernet packets will be encapsulated into an
Alcatel-Lucent-Proprietary GFP frame; this option supports the Packet Concatenation modality. An example of the window displayed is reported in Figure 4-69, (pg. 4-132). The function of this option is to substitute a PPP port with a remote ethernet port. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 3 1 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
The PPP port will be changed into a remote ethernet port, by clicking on the Yes button, and then a new remote ethernet port will be visualized in the central side of the resource tree, where the remote ethernet ports are grouped. Figure 4-69 Substitute PPP -> Ethernet
Transmission -> PPP Port -> Configure PPP Port This option is obtained, after selecting a PPP Port t ( with Admin Status = down), by means of the contextual pop-up menu; or by selecting, in the menu-bar: Transmission -> PPP Port Management -> Configure PPP Port.
An example of the window displayed is reported in Figure 4-70, (pg. 4-135).
WARNING The PPP Port is available only after the substitution of a remote Ethernet Port to a PPP Port (see “Transmission -> Ethernet Port -> Substitute Ethernet -> PPP” (p. 4-131)). Important!
Before doing this operation, the user should have done, on SDH-CT application, the configuration of this same port, defining its SDH specific container. See also the note in “Inconsistency error on Port configuration” (p. 4-100). The function of this option is to manage the transmission parameters of the selected PPP Port. To configure a PPP Port, fill fields and areas as follows: •
Configuration sector: •
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 PPP)
•
Last Change: the value of System Time when the port entered its current
operational state
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 13 2 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
•
• • • •
•
•
MTU: Maximum Transmit Unit; size of the largest packet which can be
sent/received on the interface, specified in octets (read only field, set to the value of the “mother port”) 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 . TX SL: SL (SDH Signal-Label) value transmitted in the outgoing direction readonly field. Expected SL: SL value expected in the incoming directionread-only field. RX SL: SL value received in the incoming direction; read-only field. SL Control: defining if the transmit SL (SDH container Signal Label). Possible values: automatic (defined by the agent according to the payload type) or forced (equipped-non-specific code). 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
•
Alias: friendly name for the interface, it can be specified by the user
•
Connector: (true/false) indicating if the interface has a physical connector (read
only field) •
Scrambling: (true/false); to activate/deactivate the scrambling of the PPP frames.
•
FCS Size: size of the provisioned ppp-FCS (Frame Check Sequence), in bits, that
• •
•
the local node will use without negotiating it; possible values: 16 or 32 bits Encaps. Method: encapsulation method used by the local PPP entity; possible options: standardPP (not operative), or “alcatelproprietaryPPP". Conf MRU: it permits to configure the Maximum Receive Unit (MRU) that the local PPP entity will accept. This text field is enabled only when the Encapsulation Method is set to “alcatelproprietaryPPP". The default value is 1600 (max = 2012). Conf MTU: it permits to configure the Maximum Transmit Unit (MTU) that the local PPP entity will use when sending packets to the remote entity. This text field is enabled only when the 'Encapsulation Method' is set to 'alcatelproprietaryPPP'. The default value is 1600 (max = 2012).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 3 3 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
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 dialog described in “Configuration -> Alarms Severity (ASAP management)” (p. 4-39) the •
key gives the asap properties currently associated to this resource
TP/SDH Configuration sub-sector:
this group (similar to what described in “Transmission -> Ethernet Port -> (REMOTE) Ethernet Port Properties” (p. 4-101)) permits to configure the matching between the SDH container and the ethernet bandwidth used by the current port. • Underlying Layer: possible pull-down options: – vconc: (virtual concatenation); to permit the setting of the virtualconcatenation 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 dialog described in “Rate limiting and Virtual Concatenation Setting” (p. 4-97). 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.
Alarms sector:
this group reports the alarms relevant to the PPP Port; their color is green if notalarmed, if alarmed their color will be congruent with the severity assigned in the associated ASAP; the alarms colors are described in Chapter 5, “Maintenance”. After setting all the desired parameters, click on the Ok key to send the chosen parameters to the Ethernet Port. The window will be closed without doing any operation by clicking on Cancel key. The Help key gives helps about this function.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 13 4 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-70 Configure PPP Port
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 3 5 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> PPP Port -> PPP Port Properties or This option is obtained, after selecting a PPP Port ( contextual pop-up menu; or by selecting, in the menu-bar:
), by means of the
Transmission -> PPP Port Management -> PPP Port Properties.
An example of the window displayed is reported in Figure 4-71, (pg. 4-136). The function of this option is to show the transmission parameters set for the selected PPP port. All the reported information fields are read-only, and are the same as those explained in “Transmission -> PPP Port -> Configure PPP Port” (p. 4-132). Figure 4-71 PPP Port Properties
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 13 6 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> MPLS Port -> Configure MPLS Port This option is obtained, after selecting an MPLS Port ( under a PPP Port or a Loc ETH Port with Promisc.Mode = disabled), by means of the contextual pop-up menu; or by selecting, in the menu-bar: Transmission -> MPLS Port Management -> Configure MPLS Port.
An example of the window displayed is reported in Figure 4-72, (pg. 4-139) (in the case of Remote PPP Port), and in Figure 4-73, (pg. 4-140) (in the case of Local Port). See Important!
at the end of this paragraph.
The function of this option is to manage the transmission parameters of the selected MPLS Port. To configure an MPLS Port, fill fields and areas as follows: •
Configuration sector: •
MPLS Port Name: indicating the name assigned by the system to the Port (read
only field). •
•
Label Space: the 'perPlatform' (label values are unique over the whole LSR ISA-
ES node) or 'perInterface' (label values are unique only over this interface) options are possible. The option actually supported is 'perInterface' only. Effective Line Rate: to set the effective amount of usable bandwidth on this interface (in bit/s); it depends on the bandwidth associated to the parent ethernet or PPP port (see relevant paragraphs:“Transmission -> Ethernet Port -> Configure (LOCAL) Ethernet Port” (p. 4-76) or “Transmission -> PPP Port -> Configure PPP Port” (p. 4-132)).
WARNING This value must be consistent (i.e.: less or equal) with the mother ETH Port_Rate or PPP Port_Rate. •
Available Bandwidth: remaining available bandwidth (in kb/s) for this resource
•
(set by the system). Owner: indicating the entity that created and is responsible for managing this resource.
•
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: port actual status (availability), (read only field) possible options: up
/ down
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 3 7 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
Label Range sector: •
InSegment: to define the range of the incoming labels for this MPLS Port, that can
be associated to the InSegment resources; the minimum and maximum values of the range can be changed after marking the relevant check-off box; the following label types are available: – Total / Manual The 'Total' range is the InSegment Label range stored in the LSR MIB; the default values are 1024 (min) and 5119 (max). •
•
OutSegment: (read-only); range of the outgoing labels for this MPLS Port, that
can be associated to the OutSegment resources; the default values are 16 (Min) and (2^20)-1 = 1048575 (Max). Dual Attach sector: (see Figure 4-73, (pg. 4-140))
WARNING •
This sector is displayed only in case of GigaBitETH. Local Port.
•
This feature is Alcatel-Lucent-proprietary and can be used only in interworking applications with Alcatel-Lucent ISA-PR boards. This function is used to protect against local interface failures and board failures, when ISA-ES16 is involved in ring interconnections. The protection is triggered by LOS alarm or ES board failure or Access Card failure, or by a Dual Attach switch message from remote connected node.
• •
•
The ISA-ES board must be protected in EPS 1+1 (see OMSN Operator Handbook, listed in Table 1, (pg. 1-xxiv), for details about EPS operation).
Topology: to define the type of protection; the following options are available:
–
Prot.Disabled: the Dual Attach (DA) protection is disabled
–
Hub: the protection is active in HUB topology, i.e. one single OMSN equipped with 2 ISA-ES16 boards and 2 GbE i/f access cards, protected in EPS 1+1. The 2 Gbe i/f are connected to the PR ring.
Protocol Mode: the Dual Attach messaging is transported over special MPLS
packets that are exchanged between the two connected equipment (OMSN+ES and OMSN+PR) – Disabled: the Dual Attach (DA) messaging is not active –
Full: final messaging modality (see notes below)
–
Basic RX: starting messaging modality (see notes below)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 13 8 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
WARNING 1. In order to prevent false failures alarms on the starting up of the DA procedure, the DA activation should be done in the following ordered steps: a. activation of DA with Protocol Mode = BasicRX on ES boards b. activation of DA on connected ISA-PR c. activation of DA with Protocol Mode = Full on ES boards 2. For the same reason, the DA disabling should be done in the following ordered steps: a. change of DA Protocol Mode from Full to BasicRX on ES boards b. deactivation of DA on connected ISA-PR c. deactivation of DA switching Protocol Mode from BasicRX to Disabled on ES boards. •
DA Peer Status: Status of the connected equipment (ISA-PR)
– •
Active: read-only value.
Alarms sub-sector:
This group reports the alarms relevant to the Dual Attachment feature of the Port; 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”. After setting all the desired parameters, click on the Ok key to send the chosen parameters to the MPLS 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-72 Configure MPLS Port (Remote side)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 3 9 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-73 Configure MPLS Port (Local side, 1GbETH. i/f)
Important! If the MPLS Port belongs to a Local Ethernet Port, it is configurable only if the Promiscuous Mode parameter of the Local Ethernet Port has been set to disable, in order to support MPLS over Ethernet mode (see “Transmission -> Ethernet Port -> Configure (LOCAL) Ethernet Port” (p. 4-76)), otherwise the following dialog box will be displayed: Figure 4-74 Inconsistency error on MPLS Port Configuration
Transmission -> MPLS Port -> MPLS Port Properties This option is obtained, after selecting an MPLS Port ( contextual pop-up menu; or by selecting, in the menu-bar:
), by means of the
Transmission -> MPLS Port Management -> MPLS Port Properties.
An example of the window displayed is reported in Figure 4-75, (pg. 4-141). The function of this option is to show the transmission parameters set for the selected MPLS port.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 14 0 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
All the reported information fields are read-only, and are the same as those explained in “Transmission -> MPLS Port -> Configure MPLS Port” (p. 4-137). Note:
In case of MPLS over GFP port, the properties of the resource will be as explained in “Transmission -> MPLS Port (over GFP) -> Configure MPLS Port” (p. 4-142). Figure 4-75 MPLS Port Properties
Transmission -> Ethernet Port (Remote) -> GFP Client Layer Management This option is obtained, after selecting a Remote Ethernet Port ( with Admin Status = down), by means of the contextual pop-up menu, or by selecting in the menu-bar: Transmission -> Ethernet Port Management -> GFP Client Layer Management.
it contains the sub-option: Client Layer Single->Multi. Important! This option is allowed only in Bridge Type = none,
and the Remote Port must be down. The function of this option is to create an MPLS port for transporting the ethernet data by using the MPLS over GFP over SDH protocol, i.e. “Multi Client” layer. After selecting this option, the Remote Ethernet port is transformed into an MPLS port over GFP, and displayed at the bottom of the Resources Tree. Transmission -> MPLS Port (over GFP) -> GFP Client Layer Management This option is obtained, after selecting an MPLS Port ( displayed at the bottom of the Tree), in down state, by means of the contextual pop-up menu, or by selecting in the menu-bar: Transmission -> MPLS Port Management -> GFP Client Layer Management.
it contains the sub-option: Client Layer Multi ->Single Important! This option is allowed only in Bridge Type = none
case, and the MPLS Port must be down. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 4 1 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
The function of this option is to swap a port from MPLS over GFP protocol to Remote Ethernet protocol. After selecting this option, the MPLS Over GFP port is transformed into a normal Remote Ethernet port. Transmission -> MPLS Port (over GFP) -> Configure MPLS Port This option is obtained, after selecting an MPLS Port ( displayed at the bottom of the Tree), by means of the contextual pop-up menu; or by selecting, in the menu-bar: Transmission -> MPLS Port Management -> Configure MPLS Port.
An example of the window displayed is reported in Figure 4-79, (pg. 4-146). Important!
The MPLS Port over GFP is available, at the bottom of the Tree, only after the substitution of a remote Ethernet Port to a MPLS Over GFP Port, i.e. from GFP Single Client to Multi Client (see “Transmission -> Ethernet Port (Remote) -> GFP Client Layer Management” (p. 4-141).
WARNING Before doing this operation, the user should have done, on SDH-CT application, the configuration of this same port, defining its SDH specific container. See also the note in “Inconsistency error on Port configuration” (p. 4-100). The function of this option is to manage the transmission parameters of the selected MPLS Over GFP Port. To configure an MPLS Over GFP Port, fill fields and areas as follows: •
Configuration sector: •
MPLS Port Name: indicating the name assigned by the system to the Port (read
only field). •
Label Space: the 'perPlatform' (label values are unique over the whole LSR ISA-
•
ES node) or 'perInterface' (label values are unique only over this interface) options are possible. The option actually supported is 'per Interface' only. Effective Line Rate: to set the effective amount of usable bandwidth on this interface (in bit/s); it depends on the bandwidth associated to the parent ethernet and SDH port (see relevant paragraphs: “Transmission -> Ethernet Port -> Configure (REMOTE) Ethernet Port” (p. 4-90).
WARNING This value must be consistent (i.e.: less or equal) with the ETH Port_Rate and SDH Rate.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 14 2 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
• • •
Available Bandwidth: remaining available bandwidth (in kb/s) for this resource
(set by the system). Admin. Status: Administration status, possible pull-down options: up (to set the port in-service) or down (to set the port out-of-service) Oper. Status: port actual status (availability), (read only field) possible options: up / down
Figure 4-76 Configure MPLS Port - Configuration (Multi Client Layer, over GFP)
•
GFP sector: • •
• • •
•
Enable FCS: (read-only); 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). Client Layer Type: read-only value, set by the system to Multi Client Layer. Transmit Capability: management of alarms CSF (Client Signal Fail) and VC-AIS (SDH Virtual Container- Alarm Indication Signal); its description is reported in “Transmission -> Ethernet Port -> Configure (REMOTE) Ethernet Port” (p. 4-90). MTU: Maximum Transmit Unit; size of the largest packet which can be sent / received on the interface, specified in octets (read only field); max value is 2016.
– TP/GFP SDH Configuration sub-sector: this group (similar to what described in “Transmission -> Ethernet Port -> Configure (REMOTE) Ethernet Port” (p. 4-90)) permits to configure the matching between the SDH container and the ethernet bandwidth used by the current port. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 4 3 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
–
Underlying Layer: possible pull-down options: vconc (virtual concatenation to
permit the setting of the virtual-concatenation granularity mode i.e. adaptation of SDH rate to an Ethernet rate bigger than VC-SDH used) or SDH (to permit the setting of the Rate-Limiting mode i.e. adaptation of SDH rate to an Ethernet rate smaller than VC-SDH used). –
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 dialog described in “Rate limiting and Virtual Concatenation Setting” (p. 4-97). 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-77 Configure MPLS Port - GFP (Multi Client Layer, over GFP)
•
Label Range sector: •
InSegment: to define the range of the incoming labels for this MPLS Port, that can
be associated to the InSegment resources; the minimum and maximum values of the range can be changed after marking the relevant check-off box; the following label types are available: – Total / Manual The 'Total' range is the InSegment Label range stored in the LSR MIB; the default values are 1024 (min) and 5119 (max).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 14 4 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
OutSegment: (read-only); range of the outgoing labels for this MPLS Port, that
can be associated to the OutSegment resources; the default values are 16 (Min) and (2^20)-1 = 1048575 (Max). Figure 4-78 Configure MPLS Port - Label Range (Multi Client Layer, over GFP)
•
Alarms sector:
this group reports the alarms relevant to the Port; 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”. After setting all the desired parameters, click on the Ok key to send the chosen parameters to the Port. The window will be closed without doing any operation by clicking on Cancel key. The Help key gives helps about this function.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 4 5 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-79 Configure MPLS Port - Alarm (Multi Client Layer, over GFP)
Transmission -> MPLS Port -> Create MPLS InSegment (not operative)
WARNING This option is not operative because the InSegment resource is automatically created by means of the Connection -> Create Tunnel options. Nevertheless the parameters of the existing InSegments can be visualized with the option “InSegment Properties" and are described in “Transmission -> MPLS InSegment -> MPLS InSegment Properties” (p. 4-146). Transmission -> MPLS InSegment -> Modify MPLS InSegment (not operative)
WARNING This option is not operative because the InSegment resource is automatically created by means of the Connection -> Create Tunnel options. Nevertheless the parameters of the existing InSegments can be visualized with the option “InSegment Properties" and are described in “Transmission -> MPLS InSegment -> MPLS InSegment Properties” (p. 4-146). Transmission -> MPLS InSegment -> MPLS InSegment Properties This option is obtained, after selecting an InSegment object ( see note below), by means of the contextual pop-up menu; or by selecting, in the menu-bar: Transmission -> MPLS InSegment Management -> MPLS InSegment Properties.
An example of the window displayed is reported in Figure 4-80, (pg. 4-147). Note:
The InSegment resource is automatically created by means of the Connection -> Create Tunnel options. The scope of this paragraph is to describe the relevant parameters. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 14 6 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
The function of this option is to show the transmission parameters set for the selected InSegment point; all fields are readable only: •
MPLS Port Name: indicating the name of the parent MPLS Port;
•
Label: incoming label of the packets associated to this InSegment; the label range is as
specified in “Transmission -> MPLS Port -> Configure MPLS Port” (p. 4-137). •
Label To Pop: number of labels to pop from the incoming packets. By default, only the
top label is popped from a packet and used for all switching decisions for that packet, then this value is set to “1" by the system. •
Traffic Param. indicating the name of the associated traffic descriptor (TD):
the key gives the properties of the traffic descriptor currently associated, recalling the dialog described in “Configuration -> Traffic Descriptor -> ETS Traffic Descriptor” (p. 4-56). the key gives the traffic descriptor properties currently associated to this resource. •
Status: possible pull-down options:
–
up: the resource is in-service
–
down: the resource is out-of-service
•
Policing Mode: indicating the Policing activation
•
possible options: disabled or color blind Owner: indicating the entity that created and is responsible of this InSegment.
The window will be closed by clicking on Close key. The Help key gives helps about this function. Figure 4-80 MPLS InSegment Properties
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 4 7 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> MPLS Port -> Create MPLS OutSegment (not operative)
WARNING This option is not operative because the OutSegment resource is automatically created by means of the Connection -> Create Tunnel options. Nevertheless the parameters of the existing OutSegments can be visualized with the option “InSegment Properties" and are described in “Transmission -> MPLS OutSegment -> MPLS OutSegment Properties” (p. 4-148). Transmission -> MPLS OutSegment -> Modify MPLS OutSegment (not operative)
WARNING This option is not operative because the OutSegment resource is automatically created by means of the Connection -> Create Tunnel options. Nevertheless the parameters of the existing OutSegments can be visualized with the option “InSegment Properties" and are described in “Transmission -> MPLS OutSegment -> MPLS OutSegment Properties” (p. 4-148). Transmission -> MPLS OutSegment -> MPLS OutSegment Properties This option is obtained, after selecting an OutSegment object ( see note below), by means of the contextual pop-up menu; or by selecting, in the menu-bar: Transmission -> MPLS OutSegment Management -> MPLS OutSegment Properties.
An example of the window displayed is reported in Figure 4-81, (pg. 4-149). Note:
The OutSegment resource is automatically created by means of the Connection -> Create Tunnel options. The scope of this paragraph is to describe the relevant parameters. The function of this option is to show the transmission parameters set for the selected OutSegment point. All the reported information fields are read-only: •
MPLS Port Name: indicating the name of the parent MPLS Port;
•
MPLS OutSegment: incremental index name of the resource;
•
Top Label: label number that has been pushed onto the top of the outgoing packet's
label stack, if the Push Top Label parameter is marked; the label range is as specified in “Transmission -> MPLS Port -> Configure MPLS Port” (p. 4-137). •
Traffic Param. indicating the name of the associated traffic descriptor (TD):
•
the key gives the properties of the traffic descriptor currently associated, recalling the dialog described in “Configuration -> Traffic Descriptor -> ETS Traffic Descriptor” (p. 4-56). the key gives the traffic descriptor properties currently associated to this resource.. Status: possible pull-down options:
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 14 8 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
–
up: the resource is in-service
–
down: the resource is out-of-service
Push Top Label: to indicate whether or not a top label should be pushed onto the
outgoing packet's label stack (set by the system). •
Owner: indicating the entity that created and is responsible of this OutSegment.
The window will be closed by clicking on Close key. The Help key gives helps about this function. Figure 4-81 MPLS OutSegment Properties
Transmission -> MPLS InSegment -> Delete MPLS InSegment (not operative)
WARNING This option is not operative because the InSegment resource is automatically deleted by means of the Connection -> Delete Tunnel options. Transmission -> MPLS OutSegment -> Delete MPLS OutSegment (not operative)
WARNING This option is not operative because the OutSegment resource is automatically deleted by means of the Connection -> Delete Tunnel options.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 4 9 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Inner MPLS Tunnel -> Create ETS InFlow This option is obtained, after selecting an Inner Tail Tunnel ( see next note), by means of the contextual pop-up menu; or by selecting, in the menu-bar: Transmission -> Inner MPLS Tunnel -> Create ETS InFlow.
WARNING This creation must be done in one single step by means of the Connection wizard: see “Connection -> Ethernet Port -> Create ETS XC One Step (ETS & MPLS Tunnel-Head)” (p. 4-254) and subsequents. The scope of this paragraph is to describe the settings and meanings of the resource parameters.
WARNING This option is available only if an Inner Tunnel has been already created in the Connection Context, see “Connection -> Outer MPLS Tunnel -> Create Inner MPLS Tunnel” (p. 4-296). Furthermore, the Inner Tunnel should not contain another InFlow, since it can support only one InFlow. An example of the window displayed is reported in Figure 4-82, (pg. 4-150). The function of this option is to create an Ethernet InFlow resource into the selected Inner Tunnel, in this way the ethernet flow can be tunneled into the MPLS network. The reported information fields are the same as explained in “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111), except for: –
the Service Type field, in this case fixed to MPLS;
–
the Service Id in this case is an incremental index;
–
the Policing Mode options are restricted to disabled and color-blind;
–
furthermore, this InFlow does not support VLAN-Pop and Color-Profile functions.
Figure 4-82 Create ETS InFlow (into Inner Tunnel)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 15 0 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Inner MPLS Tunnel -> Create ETS OutFlow This option is obtained, after selecting an Inner Head Tunnel ( see next note), by means of the contextual pop-up menu; or by selecting, in the menu-bar: Transmission -> Inner MPLS Tunnel -> Create ETS OutFlow.
WARNING This creation must be done in one single step by means of the Connection wizard: see “Connection -> Ethernet Port -> Create ETS XC One Step (ETS & MPLS Tunnel-Head)” (p. 4-254) and subsequents. The scope of this paragraph is to describe the settings and meanings of the resource parameters.
WARNING This option is available only if an Inner Tunnel has been already created in the Connection Context, see “Connection -> Outer MPLS Tunnel -> Create Inner MPLS Tunnel” (p. 4-296). Furthermore, the Inner Tunnel should not contain another InFlow, since it can support only one InFlow. An example of the window displayed is reported in Figure 4-83, (pg. 4-151). The function of this option is to create an Ethernet OutFlow resource into the selected Inner Tunnel, in this way the ethernet flow can be tunneled into the MPLS network. The reported information fields are the same as those explained in “Transmission -> Ethernet Port -> Create ETS OutFlow” (p. 4-117), except for: –
the Server Type field, in this case fixed to MPLS;
–
the Server Id in this case is an incremental index;
–
furthermore, this OutFlow does not support VLAN-Management function.
Figure 4-83 Create ETS OutFlow (into Inner Tunnel)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 5 1 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Outer MPLS Tunnel -> Create ETS InFlow This option is obtained, after selecting an Outer Tail Tunnel for MPLS over Ethernet ( see next note), by means of the contextual pop-up menu; or by selecting, in the menu-bar: Transmission -> Outer MPLS Tunnel -> Create ETS InFlow.
WARNING This creation must be done in one single step by means of the Connection wizard: see “Connection -> Ethernet Port -> Create ETS XC One Step (ETS & MPLS Tunnel-Head)” (p. 4-254) and subsequents. The scope of this paragraph is to describe the settings and meanings of the resource parameters.
WARNING This option is available only if an Outer Tail Tunnel (for MPLS over Ethernet, i.e. with parameter Client Type = Ethernet) has been already created in the Connection context, see “Connection -> MPLS Tunnel Management -> Create Outer Tail Tunnel” (p. 4-294). Furthermore, this Tunnel should not contain another InFlow, since it can support only one InFlow. The function of this option is to create an Ethernet InFlow resource into the selected Outer Tunnel, used for MPLS over Ethernet modality. The reported information fields are the same as those explained in “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111), except for the Service Type field, in this case fixed to MPLS; the Service Id in this case is an incremental index; the Policing Mode options are restricted to disabled and color-blind. Furthermore, this InFlow does not support VLAN-Pop and Color-Profile functions. Transmission -> Outer MPLS Tunnel -> Create ETS OutFlow This option is obtained, after selecting an Outer Head Tunnel for MPLS over Ethernet ( ), by means of the contextual pop-up menu; or by selecting, in the menu-bar: Transmission -> Outer MPLS Tunnel -> Create ETS OutFlow.
WARNING This creation must be done in one single step by means of the Connection wizard: see “Connection -> Ethernet Port -> Create ETS XC One Step (ETS & MPLS Tunnel-Head)” (p. 4-254) and subsequents. The scope of this paragraph is to describe the settings and meanings of the resource parameters.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 15 2 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
WARNING This option is available only if an Outer Head Tunnel (for MPLS over Ethernet, i.e. with parameter Client Type = Ethernet) has been already created in the Connection context, see “Connection -> MPLS Tunnel Management -> Create Outer Head Tunnel” (p. 4-289). Furthermore, this Tunnel should not contain another OutFlow, since it can support only one OutFlow. The function of this option is to create an Ethernet OutFlow resource into the selected Outer Tunnel, used for MPLS over Ethernet modality. The reported information fields are the same as those explained in “Transmission -> Ethernet Port -> Create ETS OutFlow” (p. 4-117), except for the Server Type field, in this case fixed to MPLS; the Server Id in this case is an incremental index. Furthermore, this OutFlow does not support VLAN-Management function. Transmission -> Ethernet Port/Aggregator -> Substitute Client Layer 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 contextual pop-up menu, or by selecting in the menu-bar: Transmission -> Ethernet Port Management -> Substitute Client Layer
or, for LAG resource: Transmission -> Aggregator Management -> Substitute Client Layer
It contains these sub-options: •
ETB Layer: to change this selected Port into ETB type: i.e. the afferent traffic is
automatically switched by means of Mac Autolearning procedure. •
ETS Layer: to change this selected Port into ETS type: i.e. the afferent traffic switching
is manually engineered. •
Link Aggr 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-84, (pg. 4-154) and Figure 4-85, (pg. 4-154). This option permits to switch the ethernet port resource, between “engineered" ETS and “bridged" ETB. After this operation, the Port will change its symbol and color, correspondingly to the defined type.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 5 3 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-84 Substitute Port Type (from ETS to ETB)
Figure 4-85 Substitute Port Type (from ETB to ETS)
Figure 4-86 Substitute Client Type (from ETS to Link Aggregator)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 15 4 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> ISA -> VLAN Registration This option is obtained, after selecting the Bridge ISA-ES node ( contextual pop-up menu, or by selecting in the menu-bar:
), by means of the
Transmission -> ISA Management -> VLAN Registration.
An example of the displayed dialog window is reported in Figure 4-87, (pg. 4-156).
WARNING This option is not operative if Bridge Type = bridge 802.1D (MAC) as referred in “Transmission -> ISA -> Configure ISA” (p. 4-71)). 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 “Member Set" of the corresponding VLAN domain (i.e. frames are accepted, at the relevant port, if having Priority and VLAN fields)
–
untagged means that the Port is part of the “Untagged Set" (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 or untagged or 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. •
Learning: max number of MAC-learning entries on the FDB table (default is 10000).
This value can be changed by clicking twice on the shown value in the cell. •
Fast Aging: a pull-down button is present on each cell of this item, by means of which
the current value can be changed to enable or disable the Fast-aging function (fast removal of an entry, after 100 sec, from Filtering Data Base (FDB), in case of FDB overload); possible pull-down options: ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 5 5 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
–
enabled: in case of FDB overload, an entry (expired or invalid, etc.) is deleted.
–
disabled: in case of FDB overload, the new entry is discarded.
Flooding: a pull-down button is present on each cell of this item, by means of which
the max limit of unicast dynamic filtering entries that can be learnt for the relevant VLAN. Possible pull-down options: enabled or disabled. •
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 “ISA -> Static VLAN Registration Management” (p. 4-157). c. then follow the instructions on this latter paragraph. d. then the new VLAN will be listed on the table. The max number of VLAN static registration entries is 1024. Figure 4-87 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 8DG15624AAAA 4 - 15 6 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
The Help key gives helps about this function. ISA -> Static VLAN Registration Management This function is activated in the VLAN Registration List window, shown in Figure 4-87, (pg. 4-156), after typing the desired VLANId. on the New VLAN field and then clicking on Create key. An example of the window displayed is reported in Figure 4-88, (pg. 4-158) (Provider case). 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. •
Configuration sector: •
•
•
VLAN Identifier: (read-only), current VLAN (as typed in the calling window) to be
associated to one or more ports Port Tagged Set: 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 Tagged Ports list by selecting it and then clicking on 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. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 5 7 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
The window will be closed without doing any operation by clicking on Cancel key. The Help key gives helps about this function. Figure 4-88 Static VLAN Registration Management (Provider case)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 15 8 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> Bridge Port -> 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.
This description applies also in case of LAG (when an ETB-LAG has been selected): Transmission -> Aggregator -> Bridge Port Management -> Configure Bridge Port.
An example of the displayed dialog window is reported in Figure , (pg. 4-164).
WARNING This option is available only if Bridge Type = bridge 802.1S-AD (Provider), as referred in “Transmission -> ISA -> Configure ISA” (p. 4-71)). The function of this option is to manage the transmission parameters of the selected 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 yet operative) 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: used to configure the Provider-priority mode for traffic scheduling. Possible values: – 0: (default), the PCP value, defined in “Transmission -> ISA -> Configure ISA” (p. 4-71), is not overridden. –
•
5P3D / 8P0D / 6P2D / 7P1D: in this case, the PCP value defined in “Configure ISA“ is overridden. For more details about these parameters see “Traffic Scheduling in Provider Bridge case (ETB ports)” (p. 4-64). See also “Transmission -> Ethernet Port -> Queue (QoS) -> Configure Queue” (p. 4-184).
Port VLAN Identifier:
settable only if the ETB port is in down state, (default value is 1). It is the PVID parameter, i.e. the VID to assign to untagged or only-priority-tagged S-VLAN frames retransmitted by this port. In consequence, this Port is included in the “Untagged Set" of this indicated VLAN id. The key permits to choose the PVID value for this resource, recalling the dialog described in “Bridge Port -> STP-Per Bridge Management” (p. 4-171). •
Ingress Filtering: to enable/disable the receive frame filter. Possible values:
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 5 9 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
–
true: it discards all the frames having VLAN-ID that do not have this port on their relevant “Member Set". 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 all types of ethernet frames (tagged & untagged).
–
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 relayed frames.
WARNING Its setting is possible only if the ETB port is in down state. the key permits to show and associate the Default User Priority for this resource, recalling the dialog described in “Bridge Port -> Default User Priority” (p. 4-169). •
Regen. User Priority: to define the Regenerated User Priority table to be assigned
to already prioritized relayed frames.
WARNING This option is operative only if the selected ETB Port is in down state. the key permits to show and associate the Regenerated User Priority for this resource, recalling the dialog described in “Bridge Port -> Regenerated User Priority List” (p. 4-170). •
Control Plane Configuration sector:
WARNING These parameters are not applicable if the (STP)-Protocol Type is set in manual Disable (see “Transmission -> ISA -> Configure ISA” (p. 4-71)).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 16 0 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
(X)STP Per Bridge Management: the value reported is a Bridge Instance number;
if the Stp Protocol is STP or RSTP then this value is 0, else if Stp Protocol 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-Per Bridge dialog described in “Bridge Port -> STP-Per Bridge Management” (p. 4-171) the key permits to view the STP-Per Bridge properties, i.e. the same window as described in “Bridge Port -> STP-Per Bridge Management” (p. 4-171), 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-Per Port dialog described in “Bridge Port > ControlPlane -> STP-Per Port Management” (p. 4-174) the key permits to view the STP-Per Port properties, i.e. the same window as described in “Bridge Port -> ControlPlane -> STP-Per Port Management” (p. 4-174), but in read-only mode. •
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 “Protocol list” (p. 1-50). MSTP case:
WARNING In case that the Bridge STP-Protocol is MSTP, the Control Plane sector is displayed as reported in Figure , (pg. 4-164). Some details about STP-RSTP-MSTP feature are reported in “Protocol list” (p. 1-50). An example of MSTP Bridge network and MSTID use is shown in Figure 1-41, (pg. 1-61), and subsequents. 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). ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 6 1 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
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 dialog described in “Bridge Port -> CIST -> MST Region Management” (p. 4-178).
•
The fields Per Bridge and per Port Management, are used as above explained for the other STP options. Important! The Per Bridge and Per Port parameters can be differentiated for different Regions.
MSTI Bridge Management (Multiple Spanning Tree Instance). This panel is used to
define MST Instances and the roles of the Ports from the MSTI point of view. It reports: •
MSTID: to define the MST Configuration Table. This setting is valid for all the
Bridge; the value displayed in the adjacent field is relative only to the last created Instance: the key permits to open the MSTID dialog described in “Bridge Port -> MSTI -> MSTID Management” (p. 4-179). • •
Per Bridge Management is used as in the other above explained STP cases, but
recalls the dialog reported in Figure 4-96, (pg. 4-174). Per Port Management is used as in the other above explained STP cases, but recalls the dialog reported in Figure 4-98, (pg. 4-177). Important! The Per Bridge and Per Port 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-101, (pg. 4-181), and then click Ok; then the above field MSTID will report the value 3, then the parameters Beriberi and Per Port can be modified for the Instance 3.
After setting the desired parameters, click on the Ok key to confirm. The window will be closed without doing any operation by clicking on Cancel key. The Help key gives helps about this function.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 16 2 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-89 Configure Provider Bridge Port (“PERVLANSTP" case)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 6 3 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Virtual) 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.
This description applies also in case of LAG (when an ETB-LAG has been selected): Transmission -> Aggregator -> Bridge Port Management -> Configure Bridge Port.
An example of the displayed dialog window is reported in Figure 4-90, (pg. 4-166).
WARNING This option is available only if the Bridge Type = bridge 802.1Q (Virtual) as referred in “Transmission -> ISA -> Configure ISA” (p. 4-71). The function of this option is to manage the transmission parameters of the selected Virtual Bridge port. To configure the Virtual Bridge (ETB) port, fill fields and areas as follows: •
Bridge Port Management sector: •
Bridge Port Name: settable “alias" name for this port
•
Port VLAN Identifier: the use of this parameter is the same as what explained for
•
Provider Bridge Port, see “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Provider)” (p. 4-159). 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 all types of ethernet frames (tagged & untagged).
–
admitOnlyVLANTagged: to accept only VLAN tagged ethernet frames
Bridge Port QoS sub-sector: •
Default User Priority: the use of this parameter is the same as what explained for
Provider Bridge Port, see “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Provider)” (p. 4-159).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 16 4 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
•
Regen. User Priority: the use of this parameter is the same as what explained for
Provider Bridge Port, see “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Provider)” (p. 4-159). Control Plane Configuration sector:
WARNING These parameters are not applicable if the “(STP)-Protocol Type” is set in manual Disable (see “Transmission -> ISA -> Configure ISA” (p. 4-71)). •
(X)STP Per Bridge Management: the value reported is a Bridge Instance number;
if the “Stp Protocol" is STP or RSTP then this value is 0, else if “Stp Protocol" 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-Per Bridge dialog described in “Bridge Port -> STP-Per Bridge Management” (p. 4-171) the key permits to view the STP-Per Bridge properties, i.e. the same window as described in “Bridge Port -> STP-Per Bridge Management” (p. 4-171), 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-Per Port dialog described in “Bridge Port > ControlPlane -> STP-Per Port Management” (p. 4-174) the key permits to view the STP-Per Port properties, i.e. the same window as described in “Bridge Port -> ControlPlane -> STP-Per Port Management” (p. 4-174), but in read-only mode •
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 “Protocol list” (p. 1-50).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 6 5 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
MSTP case: The management of this option is the same as what explained for Provider Bridge Port, see “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Provider)” (p. 4-159). After setting the desired parameters, click on the Ok key to confirm. The window will be closed without doing any operation by clicking on Cancel key. The Help key gives helps about this function. Figure 4-90 Configure Bridge Port (MSTP case)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 16 6 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (MAC) 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.
This description applies also in case of LAG (when an ETB-LAG has been selected): Transmission -> Aggregator -> Bridge Port Management -> Configure Bridge Port.
An example of the displayed dialog window is reported in Figure 4-91, (pg. 4-168).
WARNING This option is available only if Bridge Type = bridge 802.1D (MAC), as referred in “Transmission -> ISA -> Configure ISA” (p. 4-71). 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 Management sector: •
Bridge Port Name: settable “alias" name for this port
•
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.
Default User Priority: the use of this parameter is the same as what explained for
Provider Bridge Port, see “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Provider)” (p. 4-159). •
Control Plane Configuration sector:
WARNING These parameters are not applicable if the (STP)-Protocol Type is set in manual Disable (see “Transmission -> ISA -> Configure ISA” (p. 4-71)). ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 6 7 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
(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 the key permits to open the STP-Per Bridge dialog described in “Bridge Port -> STP-Per Bridge Management” (p. 4-171) the key permits to view the STP-Per Bridge properties, i.e. the same window as described in “Bridge Port -> STP-Per Bridge Management” (p. 4-171), but in read-only mode. •
(R)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-Per Port dialog described in “Bridge Port > ControlPlane -> STP-Per Port Management” (p. 4-174) the key permits to view the STP-Per Port properties, i.e. the same window as described in “Bridge Port -> ControlPlane -> STP-Per Port Management” (p. 4-174), but in read-only mode. After setting the desired parameters, click on the Ok key to confirm. The window will be closed without doing any operation by clicking on Cancel key. The Help key gives helps about this function. Figure 4-91 Configure MAC Bridge Port
Transmission -> Bridge Port -> Modify Port VLAN Identifier (PVID) This function is activated in the Virtual or Provider Bridge Port Management window (see “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Provider)” (p. 4-159), or “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Virtual)” (p. 4-164)), after clicking on the key of the Port VLAN Identifier item. An example of the window displayed is reported in Figure 4-92, (pg. 4-169).
WARNING T
This option is not operative if Bridge Type = bridge 802.1D (MAC) or none. This option is operative only if the selected ETB Port is in down state.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 16 8 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
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 Untagged Set of the VLAN under consideration. The VLAN to be used as PVID must be already registered, on the selected Port. The displayed table lists all the already registered VLAN; the meanings of parameters in this window are the same as explained in “Transmission -> ISA -> VLAN Registration” (p. 4-155). The learning and fast aging parameters can be modified. To assign the PVID to the port, select one VLAN on the list, and then click on Apply. The window will be closed without doing any operation by clicking on Cancel key. Figure 4-92 Port VLAN Identifier (PVID) association
Bridge Port -> Default User Priority This function is activated in the Virtual or Provider Bridge Port Management window (see “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Provider)” (p. 4-159), or “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Virtual)” (p. 4-164)), after clicking on the key of the Default User Priority item. An example of the window displayed is reported in Figure 4-93, (pg. 4-170). The function of this option is to set the User Priority to be assigned by default on the selected ETB Port, when incoming frames do not have the priority information. In this case, all relayed frames will have the same priority value that is indicated in this field. Important! It is settable only if the port is in down state, and the
Client-Type parameter is etb. See also “Prioritization, S-VLAN, Policing, Color Profile, Scheduling” (p. 4-60). This association is set by selecting one priority from the list, and then clicking on the Apply key ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 6 9 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
The window will be closed without doing the association, by clicking on Cancel key. Figure 4-93 Bridge Port: Default User Priority
Bridge Port -> Regenerated User Priority List This function is activated in the Virtual or Provider Bridge Port Management window (see “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Provider)” (p. 4-159) or “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Virtual)” (p. 4-164)), after clicking on the key of the Regen.UserPriority item. An example of the window displayed is reported in Figure 4-94, (pg. 4-171). The function of this option is to manage the Regenerated User Priority on the selected ETB port; i.e. the association of a Virtual or Provider User Priority profile to the retransmitted 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 “Prioritization, S-VLAN, Policing, Color Profile, Scheduling” (p. 4-60)). 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 17 0 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-94 Bridge Port: Regenerated Priority List
Bridge Port -> STP-Per Bridge Management This function is activated in the Control Plane -> Configure Virtual (or MAC or Provider) Bridge Port window (see “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Provider)” (p. 4-159) or “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Virtual)” (p. 4-164)), after clicking on the key of the (X)STP Per Bridge Management item. An example of the window displayed is reported in Figure 4-95, (pg. 4-174). In case of MSTP bridge, the MSTI sector reports the parameters as shown in Figure 4-96, (pg. 4-174). The function of this option is to manage the STP-Per Bridge 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 (Designated Bridges, Root Ports, Designated Ports), according to Path Cost criteria. If there are two or more paths with the same ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 7 1 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Path Cost, then the priority parameters of the involved elements will be used to select the best path. Some details about STP functionality, and some examples of bridged network and relevant xSTP roles are reported in “Protocol list” (p. 1-50). To set the Per Bridge 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 “Bridge Port -> ControlPlane -> STPPer Port Management” (p. 4-174)) of the Root Port for this bridge •
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 17 2 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
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. The window will be closed without doing any operation by clicking on Cancel key. The Help key gives helps about this function.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 7 3 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-95 Bridge Port: STP-Per Bridge Management
Figure 4-96 Bridge Port: STP-Per Bridge Management (MSTI case)
Bridge Port -> ControlPlane -> STP-Per Port Management This function is activated in the Control Plane -> Configure Virtual (or MAC or Provider) Bridge Port window (see “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Provider)” (p. 4-159) or “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Virtual)” (p. 4-164)), after clicking on the key of the (X)STP Per Port Management item. An example of the displayed dialog window is reported in Figure 4-97, (pg. 4-177). In case of MSTP bridge, the MSTI sector reports the parameters as shown in Figure 4-98, (pg. 4-177). The function of this option is to manage the STP-Per Port Instances to be associated to this ETB port. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 17 4 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Some details about STP functionality, and some examples of bridged network and relevant xSTP roles are reported in “Protocol list” (p. 1-50). To set the Per Port 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 Force Port State). 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 Rec.):
–
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.
–
designated: the port is connecting a LAN, through the current Bridge, to the Root Bridge
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 7 5 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
•
• • • • • •
–
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 transitioned 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 topology 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.
–
pointtopoint: the port is directly connected, in point-to-point mode, to another bridge of the network
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 17 6 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
–
•
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. After setting the desired parameters, click on the Ok key to confirm. The window will be closed without doing any operation by clicking on Cancel key. The Help key gives helps about this function. Figure 4-97 Bridge Port: STP-Per Port Management
Figure 4-98 BridgePort: STP-Per Port Management (MSTI case)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 7 7 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Bridge Port -> CIST -> MST Region Management This function is activated, when the STP-Protocol Type is MSTP, in the Configure Bridge Port (Virtual or Provider) window (see “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Provider)” (p. 4-159) or “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Virtual)” (p. 4-164)), after clicking on the key of the Region Number item on the CIST management area. An example of the window displayed is reported in Figure 4-99, (pg. 4-179). 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-100, (pg. 4-179) showing the MST Region Instance List. Note:
The Show List will be updated only after the operations described in next “Bridge Port -> MSTI -> MSTID Management” (p. 4-179).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 17 8 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-99 Bridge Port: CIST: MST Region Management
Figure 4-100
Bridge Port: CIST: MST Region List
Bridge Port -> MSTI -> MSTID Management This function is activated in the Configure (Virtual or Provider) Bridge Port window (see Figure , (pg. 4-164) after clicking on the key of the MSTID item on the MSTI management area. An example of the window displayed is reported in Figure 4-101, (pg. 4-181). 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).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 7 9 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
Status: this status can be changed from notInService to active by using the Create key or from active to notInService by using the Delete key.
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-102, (pg. 4-181), 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 key on the keyboard; or individually, by using the mouse button and the 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-103, (pg. 4-181). (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 , (pg. 4-164), where the Per Bridge and Per Port parameters related to this selected MSTID can then be configured.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 18 0 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-101
Bridge Port: MSTI: MSTI Management
Figure 4-102
Bridge Port: MSTI: MSTID/VLAN Assignment
Figure 4-103
Bridge Port: MSTI: MSTID/VLAN List
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 8 1 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> Bridge Port -> Bridge Port Properties 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).
This description applies also in case of LAG (when an ETB-LAG has been selected): Transmission -> Aggregator -> Bridge Port Management -> Bridge Port Properties.
An example of the window displayed is reported in Figure 4-104, (pg. 4-182) (Provider Bridge case) The function of this option is to show the transmission parameters set for the selected Bridge ETB Port. All the reported information fields are read-only, and are the same as those explained ones for “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Provider)” (p. 4-159), “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Virtual)” (p. 4-164), “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (MAC)” (p. 4-167). Figure 4-104 Bridge Port Properties (Provider/MSTP case)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 18 2 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> Bridge Port -> Show VLAN Info 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 means of the contextual pop-up menu, or by selecting in the menu-bar: Transmission -> Ethernet Port Management -> Bridge Port Management -> Show VLAN Info
This description applies also in case of LAG (when an ETB-LAG has been selected): 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 “Transmission -> ISA -> Configure ISA” (p. 4-71)). An example of the window displayed is reported in Figure 4-105, (pg. 4-183). 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 “Bridge Port -> ControlPlane -> STP-Per Port Management” (p. 4-174)). Figure 4-105
Show VLAN Info
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 8 3 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> Queue (QoS) -> Configure Queue This option is obtained, after selecting an Ethernet port ( contextual pop-up menu, or by selecting in the menu-bar:
or
), by means of the
Transmission -> Ethernet Port Management -> Queue (Qos) Management-> Configure Queue
An example of the window displayed is reported in Figure 4-106, (pg. 4-186). For more details see explanations in “Prioritization, S-VLAN, Policing, Color Profile, Scheduling” (p. 4-60). 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 has to be taken into account together with the Rate Limiting parameter defined in Configure remote Port (see “Rate limiting and Virtual Concatenation Setting” (p. 4-97)), and with the Fractional Rate defined in Configure local Port (see “Transmission -> Ethernet Port -> Configure (LOCAL) Ethernet Port” (p. 4-76)). •
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 Bridge Type = bridge 802.1S-AD (Provider) case: •
•
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 “Transmission -> ISA -> Configure ISA” (p. 4-71), or in “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Provider)” (p. 4-159). The key opens the Forwarding Class Mapping dialog as in Figure 4-107, (pg. 4-186), that permits to set: ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 18 4 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
–
Egress FC Queue: it indicates the egress queue where the Forwarding Class will be sent. (not operative) the key permits to view the Forwarding Class Mapping properties, as above described, but in read-only mode
•
Queue Number: range 0 to 7 by means of the pull down; this field (together with
the following Forwarding Class Number) permits to create a QoS Customer Profile (not operative in current release). Only the Queue Weight can be set. For more details see “Prioritization, S-VLAN, Policing, Color Profile, Scheduling” (p. 4-60). the key opens the Management Queue dialog as in Figure 4-108, (pg. 4-186), that permits to set: Queue Type: possible options: Important! One of the following values will be displayed,
according to the Queue Number and the PCP-decoding; e.g. if the PCP-decoding is 8P0D and the Queue Number is 7, then the strict Priority value will be shown. Otherwise, if Queue Number = 3, then the Weighted Bandwidth value will be shown. The PCP mode is set in “Transmission -> ISA -> Configure ISA” (p. 4-71), or in “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Provider)” (p. 4-159).
•
–
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: (settable only in case of weighted bandwidth); weight to be
applied for the selected Queue, on forwarding operations. It is a proportional factor for the bandwidth reserved for the selected queue. In case of ETS Port the default value cannot be changed. Example: For PCP = 8P0D, by default, the Queue Weight (QW) value is assigned to
the Forwarding Queues (FQ) in the following way: (FQ = 0 ->QW = 1), (FQ = 1>QW = 2), (FQ = 2 ->QW = 8), (FQ = 3 ->QW = 16), (FQ = 4 ->QW = 32), (FQ = 5 ->QW = 64). FQ = 6 and FQ = 7 have no QW as they are in strict Priority. the key permits to view the Management Queue properties, as above described, but in read-only mode
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 8 5 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-106 Queue (QoS) Management
Virtual/MAC Bridge case
Provider Bridge case
Figure 4-107 QoS Management: Forwarding Class Number
Figure 4-108 QoS Management: Queue Number and weighting
Figure 4-109 QoS Management: Queue Properties
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 18 6 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> Queue (QoS) -> Properties Queue This option is obtained, after selecting an Ethernet port ( contextual pop-up menu, or by selecting in the menu-bar:
or
), by means of the
Transmission -> Ethernet Port Management -> Queue (Qos) Management -> Properties Queue.
An example of the window displayed is reported in Figure 4-110, (pg. 4-188). 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 “Transmission -> Ethernet Port -> Queue (QoS) -> Configure Queue” (p. 4-184). In case of Bridge Type = bridge 802.1S-AD (Provider) only, it reports also the Scheduling Discipline value and: •
List Forwarding Class button: (see Figure 4-111, (pg. 4-188)):
•
it reports the Forwarding Class Mapping; i.e. the association between the Priority Forwarding Class, (FC) and Forwarding Queue (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 in “Transmission -> ISA -> Configure ISA” (p. 4-71) or in “Transmission -> Ethernet Port -> Bridge Port -> Configure Bridge Port (Provider)” (p. 4-159). List Queue button: (see Figure , (pg. 4-188)): it reports the List of the Queues and their relevant parameters: • Queue Number: it is the number of the Forwarding Queue (FQ) • Queue Type: strict Priority or Weighted Bandwidth • Queue Weight: value of the weights for the queues, assigned by default or by the operator as seen in Figure 4-108, (pg. 4-186). The other values Hi Admin Status, Hi Start Average, Hi Max Average, Hi Max Probability, Lo Admin Status, Lo Start Average, Lo Max Average, Lo Max Probability are used as DropperParameters as seen in Figure 4-109, (pg. 4-186).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 8 7 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-110 Queue (QoS) Properties
Virtual/MAC Bridge case
Provider Bridge case
Figure 4-111 QoS Properties: Forwarding Class Mapping 5P3D
6P2D
8P0D
7P1D
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 18 8 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-112
QoS Properties: Queue Number List 5P3D
8P0D
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 8 9 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> ISA -> IGMP Management -> Configure IGMP This option is obtained, after selecting the ISA-ES Node ( contextual pop-up menu, or by selecting in the menu-bar:
), by means of the
Transmission -> ISA Management -> IGMP Management-> Configure IGMP.
WARNING This option is not allowed for Bridge Type = bridge 802.1D (MAC) or none cases. The VLAN’s to be associated to IGMP should be already registered. An example of the window displayed is reported in Figure 4-113, (pg. 4-191). 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 “IGMP Snooping management” (p. 1-79). 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-114, (pg. 4-192). See next “ISA -> IGMP Snooping Management -> VLAN association” (p. 4-191). 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
•
Help: to get helps about this function.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 19 0 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-113
ISA: IGMP Snooping Management List
ISA -> IGMP Snooping Management -> VLAN association After clicking on the Create key of the window described in the previous paragraph, the dialog box reported in Figure 4-114, (pg. 4-192) 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 VLANId 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 9 1 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
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 Last Member
Query Interval, 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: 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. (not yet supported in current release)
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-114 ISA: IGMP Snooping, VLAN association
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 19 2 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> ISA -> IGMP Management -> IGMP Properties This option is obtained, after selecting the ISA Node ( pop-up menu, or by selecting in the menu-bar:
), by means of the contextual
Transmission -> ISA Management -> IGMP Management -> IGMP Properties
WARNING This option is not allowed for Bridge Type = bridge 802.1D (MAC) 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 “Transmission -> ISA -> IGMP Management -> Configure IGMP” (p. 4-190). Transmission -> Ethernet Port -> IGMP -> Configure IGMP This option is obtained, after selecting an active Port ( pop-up menu, or by selecting in the menu-bar:
), 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). An example of the window displayed is reported in Figure 4-115, (pg. 4-195). Some general details about IGMP are described in “IGMP Snooping management” (p. 1-79). The function of this option is to set the IGMP parameters for this selected Port, such as Fast Leave, Static Router Port, 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. It contains the following parameters: •
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 (as shown in Figure 4-116, (pg. 4-195)) ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 9 3 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
Fast Leave Per Port Possible values:
–
enabled means that this Port permits the Fast Leave, 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 Fast Leave 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 Ok key confirms the selected parameters. The Cancel key permits to close the window without confirming this setting. Click on Help to get aids about this function.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 19 4 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-115
Port: IGMP Services Management
Figure 4-116
Port: IGMP Services Management: VLAN ID
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 9 5 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> IGMP -> IGMP Properties This option is obtained, after selecting an active Port ( pop-up menu, or by selecting in the menu-bar:
), by means of the contextual
Transmission -> Ethernet Port Management -> IGMP Management -> IGMP Properties.
WARNING This option is not possible for Bridge Type = bridge 802.1D (MAC) case. 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). An example of the window displayed is reported in Figure 4-117, (pg. 4-197). Some general details about IGMP are described in “IGMP Snooping management” (p. 1-79). The function of this option is to show the IGMP parameters and services set for this selected Port. The following parameters are displayed: •
Port ID: read-only field, set by the system, index of the selected Port.
•
Port Name: read-only field, set by the system, name of the 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 Fast Leave feature is enabled on this VLAN.
–
down the Fast Leave 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).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 19 6 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
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-118, (pg. 4-198), 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)
–
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-117
Port: IGMP Services Properties List
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 9 7 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-118 Port: IGMP Request Membership Group
Transmission -> Aggregator -> IGMP -> Configure IGMP This option is obtained, after selecting an active Aggregator (LAG contextual pop-up menu, or by selecting in the menu-bar:
), by means of the
Transmission -> Aggregator -> IGMP Management -> Configure IGMP.
WARNING This option is not possible for Bridge Type = bridge 802.1D (MAC) case. 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 Ethernet Port described in “Transmission -> Ethernet Port -> IGMP -> Configure IGMP” (p. 4-193). Transmission -> Aggregator -> IGMP -> IGMP Properties This option is obtained, after selecting an active Aggregator (LAG contextual pop-up menu, or by selecting in the menu-bar:
), by means of the
Transmission -> Aggregator -> IGMP Management -> IGMP Properties
WARNING This option is not possible for Bridge Type = bridge 802.1D (MAC) case. 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 Ethernet Port described in “Transmission -> Ethernet Port -> IGMP -> IGMP Properties” (p. 4-196).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 19 8 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Aggregator -> 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
An example of the window displayed is reported in Figure 4-119, (pg. 4-201). Some general details about Link Aggregation are described in “Link Aggregation management” (p. 1-81). 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 indicate the LAG “Key”, the parameter identifying this LAG; up
to 2 for Gigabit Ethernet or 7 for Fast Ethernet. •
•
•
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 dialog described in “Configuration -> Alarms Severity (ASAP management)” (p. 4-39). the key gives the asap properties currently associated to this resource 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 dialog described in “Create Protocol Profile” (p. 4-86). 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. Note:
It is allowed only if the above Client-Type parameter is ets.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 1 9 9 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
•
•
Protocol List:
the key permits to set the Protocol List (as referred in “Protocols” (p. 1-43)), recalling the dialog reported in Figure 4-120, (pg. 4-201); 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 “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111). 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 “Transmission -> Aggregator -> Configure Aggregator” (p. 4-202); 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 4 for GigaBit Ethernet or up to 14 for Fast Ethernet. •
ETH Client Type: (read only field, settable by means of “Transmission -> Ethernet
Port/Aggregator -> Substitute Client Layer” (p. 4-153)), indicating the transported layer:
•
–
ets: for Ethernet Transparent System
–
etb: for Ethernet Bridge System
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. Allowed values are integers in the range 1574 to 9216. •
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 Ok key confirms the selected parameters. The Cancel key permits to close the window without creating the LAG. Click on Help to get aids about this function.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 20 0 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-119
Aggregator: Creation
Figure 4-120
Aggregator: Set Protocol List
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 0 1 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Aggregator -> 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. An example of the window displayed is reported in Figure 4-121, (pg. 4-205). Some general details about Link Aggregation are described in “Link Aggregation management” (p. 1-81). The function of this option is to configure an existing LAG, Link Aggregation Group (already created as described in “Transmission -> Aggregator -> Create Aggregator” (p. 4-199)), defining its main parameters. To configure a created Link Aggregation Group, fill fields and areas as follows: •
Configuration sector: • • • •
•
Name: (read-only), name of the LAG, as set in previous paragraph Create
Aggregator. 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 indicate the LAG “Key”, the parameter identifying this LAG; up to 2 for Gigabit Ethernet or 7 for Fast Ethernet. 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 Actor System Priority. 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. ETH Client Type: (read only field, settable by means of “Transmission -> Ethernet Port/Aggregator -> Substitute Client Layer” (p. 4-153)), indicating the transported layer:
•
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 20 2 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
–
ets: for Ethernet Transparent System
–
etb: for Ethernet Bridge System
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. •
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.
Protocol List:
the key permits to set the Protocol List (as referred in “Protocols” (p. 1-43)), recalling the dialog reported in Figure 4-120, (pg. 4-201); 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 “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111). the •
key gives the Protocol List properties currently associated to this resource
Traffic Enabled: read-only value, it can be set by using the menu-option:
Enabled/Disabled, see “Transmission -> Aggregator -> Traffic Management” (p. 4-104). – 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
–
logicPortCreatFailed: failure on creation
–
qReservationFailed: failure on reservation
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 0 3 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
• • •
• •
Bandwidth: indicating the actually used Bandwidth (expressed in MBit) 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 (expressed in kBit) of the LAG, not yet used by Aggregated Ports Flooding Rate: (parameter not available) to set the maximum rate of packets having unknown Addresses, for this LAG, that can be flooded to all 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 4 for GigaBit Ethernet or up to 14 for Fast Ethernet. 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 dialog described in “Configuration -> Alarms Severity (ASAP management)” (p. 4-39). 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. Allowed values are integers in the range 1574 to 9216. •
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 dialog described in“Create Protocol Profile” (p. 4-86). the key gives the Protocol Type properties currently associated to this resource the •
key permits to delete the Protocol Type for this LAG
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.
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 20 4 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-121
•
Aggregator: Configure Aggregator/Configuration
Information sector (Figure 4-122, (pg. 4-206)): • • • • •
• •
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, integer in the range 0 to 122 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 MacAddress, 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 Primary Port,
•
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.). Primary Port is the first one created in the LAG. Primary Port Position: (read only field, fixed by the system); indicating the position of the Primary Port on the equipment connectors Number: (read only field, fixed by the system); indicating the reference number of this LAG, as set by the system.
•
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 0 5 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-122 Aggregator: Configure Aggregator/Information
•
Alarm sector (Figure 4-123, (pg. 4-206)):
this area reports the alarms relevant to the selected LAG; their color is green if notalarmed, if alarmed their color will be congruent with the severity assigned in the associated ASAP. The management and reparation of alarms and their severities colors are reported in next Chapter 5, “Maintenance”. Figure 4-123 Aggregator: Configure Aggregator/Alarm
The Ok key confirms the selected parameters. The Cancel key permits to close the window without confirming these parameters values. Click on Help to get aids about this function. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 20 6 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Aggregator -> Aggregator Properties This option is obtained, after selecting an existing LAG ( contextual pop-up menu, or by selecting in the menu-bar:
), by means of the
Transmission -> Aggregator -> Aggregator Properties.
An example of the window displayed is reported in Figure 4-124, (pg. 4-207). The function of this option is to show the transmission parameters set for the selected LAG. All the reported information fields are read-only, and are the same as those explained in “Transmission -> Aggregator -> Configure Aggregator” (p. 4-202). Figure 4-124
Aggregator Properties
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 0 7 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Aggregator -> Delete Aggregator This option is obtained, after selecting a disabled LAG ( pop-up menu, or by selecting in the menu-bar:
), 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. An example of the window displayed is reported in Figure 4-125, (pg. 4-208). This option permits to delete the selected LAG. Figure 4-125 Delete Aggregator
Transmission -> Ethernet Port -> Aggregation Port -> Configure 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 “Transmission -> Ethernet Port/Aggregator -> Substitute Client Layer” (p. 4-153)), before using this option. An example of the window displayed is reported in Figure 4-126, (pg. 4-211). Some general details about Link Aggregation are described in “Link Aggregation management” (p. 1-81). The function of this option is to configure an existing Aggregation Port, (already created as described in Substitute Client Layer), 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) ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 20 8 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
• • • • •
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 Primary Port 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 Actor Admin Key: (read only field, fixed by the system); indicating the owner LAG-Key. This Key is set by means of “Transmission -> Aggregator -> Configure Aggregator” (p. 4-202); the key permits to choose and associate a LAG-Key to this resource, recalling the dialog reported in Figure 4-127, (pg. 4-211). 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 0 9 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
•
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, as set by the system. 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 TimeOut (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 definitely 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 IEEEStd.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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 21 0 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Note:
The listed parameters are encoded into the LACPDU frame, in the “Partner-State” byte, as specified in IEEEStd.802.3ad-2000. The Ok key confirms the selected parameters. The Cancel key permits to close the window without confirming these parameters values. Click on Help to get aids about this function. Figure 4-126
Aggregation Port: Configure
Figure 4-127
Aggregation Port: Set Actor Admin Key
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 1 1 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> Aggregation Port -> Properties 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 “Transmission -> Ethernet Port/Aggregator -> Substitute Client Layer” (p. 4-153)), before using this option. An example of the window displayed is reported in Figure 4-128, (pg. 4-212). The function of this option is to show the transmission parameters set for the selected Aggregation Port. All the reported information fields are read-only, and are the same as those explained in “Transmission -> Ethernet Port -> Aggregation Port -> Configure” (p. 4-208). Figure 4-128 Aggregation Port: Properties
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 21 2 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> In Fiber In Band 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);
•
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 “Transmission -> ISA -> Configure ISA” (p. 4-71). Transmission -> Ethernet Port -> In Fiber In Band -> Create This option is obtained, after selecting an existing Ethernet Port ( ), on the resources Tree, by means of the contextual pop-up menu, or by selecting in the menu-bar: 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. An example of the window displayed is reported in Figure 4-129, (pg. 4-214). The function of this option is allowing to user configure the port in order to support the “In Fiber In Band”.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 1 3 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-129 In Fiber In Band : Create
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. •
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. The Ok key confirms the selected parameters. The Cancel key permits to close the window without confirming these parameters values. Click on Help to get aids about this function. Transmission -> Ethernet Port -> In Fiber In Band -> Modify This option is obtained, after selecting an existing Ethernet Port ( ), on the resources Tree, by means of the contextual pop-up menu, or by selecting in the menu-bar: 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. An example of the window displayed is reported in Figure 4-130, (pg. 4-215). The function of this option is allowing the user modify some parameters related to the “In Fiber In Band”. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 21 4 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
All the reported information fields are the same as those explained in “Transmission -> Ethernet Port -> In Fiber In Band -> Create” (p. 4-213) 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-130
In Fiber In Band : Modify
The Ok key confirms the selected parameters. The Cancel key permits to close the window without confirming these parameters values. Click on Help to get aids about this function. Transmission -> Ethernet Port -> In Fiber In Band -> Delete This option is obtained, after selecting an existing Ethernet Port ( ), on the resources Tree, by means of the contextual pop-up menu, or by selecting in the menu-bar: 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-131, (pg. 4-216) message box is displayed.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 1 5 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-131 In Fiber In Band : Delete
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. Transmission -> Ethernet Port -> In Fiber In Band -> Properties This option is obtained, after selecting an existing Ethernet Port ( ), on the resources Tree, by means of the contextual pop-up menu, or by selecting in the menu-bar: 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-132, (pg. 4-216). All the reported information fields are read-only, and are the same as those explained in “Transmission -> Ethernet Port -> In Fiber In Band -> Create” (p. 4-213) Figure 4-132 In Fiber In Band : Properties
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 21 6 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> Hub-Spoke This option is obtained, after selecting an existing Local Ethernet Port ( ), on the resources Tree, by means of the contextual pop-up menu, or by selecting in the menu-bar: Transmission -> Ethernet Port Management -> Configure Hub-Spoke
An example of the window displayed is reported in Figure 4-133, (pg. 4-217).
WARNING This option is allowed in Bridge Type = none (see “Transmission -> ISA -> Configure ISA” (p. 4-71)). Figure 4-133
Configure Hub-Spoke
This window is used to manage/configure the functionality Hub and Spoke, described in “Control Protocols management in a Transport Network” (p. 1-87), related to selected interface. •
Downstream Ports sector contains the following widgets:
–
Available Network Ports lists all active Ethernet ports present on board.
–
Downstream Ports lists all ports which an operator wants to configure as set downstream.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 1 7 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
Upstream Ports sector contains the following widgets:
–
Available Network Ports lists all active Ethernet ports present on board.
–
Upstream Ports lists all ports which an operator wants to configure as set upstream.
The
widget-button is used to add a specific port to downstream/upstream set.
This widget-button is used to remove a specific port from downstream/upstream set, The Ok key confirms the selected parameters. The Cancel key permits to close the window without confirming these parameters values. Click on Help to get aids about this function.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 21 8 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Transmission -> Ethernet Port -> EFM Management 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 through 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; 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.
Transmission -> Ethernet Port -> EFM Management -> Configuration This option is obtained, after selecting an existing Ethernet Port ( ), on the resources Tree, by means of the contextual pop-up menu, or by selecting in the menu-bar: Transmission -> Ethernet Port Management -> EFM Management -> Configure EFM
An example of the window displayed is reported in Figure 4-134, (pg. 4-220). The function of this option is to configure the primary controls and status for the OAM capabilities of an Ethernet like interface. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 1 9 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-134 EFM Management: Configuration
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: –
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 22 0 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
•
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 through 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.
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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 2 1 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
determine additional information about the peer entity. The format of the vendor information is unspecified within the 32-bit field. This value is initialized 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 8DG15624AAAA 4 - 22 2 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Clicking on Statistics tab the window contents change as shown in the following: Figure 4-135
EFM Management: Statistics
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 2 3 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Clicking on Alarms tab the window contents change as shown in the following: Figure 4-136 EFM Management: Alarms
This window reports the alarms relevant to the selected EFM; their color is green if notalarmed, if alarmed their color will be congruent with the severity assigned in the associated ASAP. The management and reparation of alarms and their severities colors are reported in next Chapter 5, “Maintenance”. The Ok key confirms the selected parameters. The Cancel key permits to close the window without confirming these parameters values. Click on Help to get aids about this function. Transmission -> Ethernet Port -> EFM Management -> Properties This option is obtained, after selecting an existing Ethernet Port ( ), on the resources Tree, by means of the contextual pop-up menu, or by selecting in the menu-bar: Transmission -> Ethernet Port Management -> EFM Management -> EFM Properties
This selection shows the same windows of the “Transmission -> Ethernet Port -> EFM Management -> Configuration” (p. 4-219), but with the previous editable fields, in readonly format as shown in the following picture.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 22 4 Issue 05 February 2010
Craft Terminal for ES Management
Transmission
............................................................................................................................................................................................................................................................
Figure 4-137
EFM Management: Properties
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 2 5 Issue 05 February 2010
Craft Terminal for ES Management
OAM
............................................................................................................................................................................................................................................................
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; (not supported in current release).
•
LoopBack: a test signal is sent by an originating point and is reflected back at a destination point of a bridged network.
•
Link Trace: 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 only in Bridge Type = bridge 802.1S-AD (Provider) or bridge 802.1Q (Virtual) as referred in “Transmission -> ISA -> Configure ISA” (p. 4-71)). 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 8DG15624AAAA 4 - 22 6 Issue 05 February 2010
Craft Terminal for ES Management
OAM
............................................................................................................................................................................................................................................................
OAM Domain -> Configure Resources (OAM) This option is obtained, by selecting in the menu-bar: OAM Domain -> Configure Resources (OAM)
An example of the window displayed is reported in Figure 4-138, (pg. 4-227). The function of this option is to configure the parameters for the OAM. Figure 4-138
OAM: Configure Resources
After creation
The window shown in Figure 4-138 reports in tabular form the existing MD (Maintenance Domain), created as described within next Figure 4-139, (pg. 4-228).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 2 7 Issue 05 February 2010
Craft Terminal for ES Management
OAM
............................................................................................................................................................................................................................................................
OAM Configure Resources (Figure 4-138) -> Create key (Figure 4-139) Figure 4-139 OAM: Configure Resources: Create MD
The window of Figure 4-139 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. It contains the following parameters: •
Operator Label: read-only, set by the system
•
Name: to type a name chosen by the user
•
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 22 8 Issue 05 February 2010
Craft Terminal for ES Management
OAM
............................................................................................................................................................................................................................................................
OAM Configure Resource (see Figure 4-138) -> Modify key
(same content as the Create key, see Figure 4-139). The Modify window can be used to modify some parameters of the created MD. OAM Configure Resource (see Figure 4-138) -> Delete key (Figure 4-140) Figure 4-140
OAM: Configure Resources: Delete MD
It will delete the MD# selected in the table. OAM Configure Resource (Figure 4-138) -> MA Navig. key (Figure 4-141) Figure 4-141
OAM: Configure Resources: MA Navigation
The window of Figure 4-141. 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 2 9 Issue 05 February 2010
Craft Terminal for ES Management
OAM
............................................................................................................................................................................................................................................................
OAM Configure Resource (Figure 4-138) -> MA Navig. key (Figure 4-141) -> Create key (Figure 4-142) Figure 4-142 OAM: Configure: MA Navig.: Create MA
The window in Figure 4-142 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. It contains the following parameters: •
Maintenance Domain: a pull-down menu permits to choose the MD among those
already created. •
Index MA: read-only incremental index, set by the system
•
CCM Interval: (not operative); 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-143.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 23 0 Issue 05 February 2010
Craft Terminal for ES Management
OAM
............................................................................................................................................................................................................................................................
OAM Configure Resource (Figure 4-138) -> MA Navig. key (Figure 4-141) -> Create key (Figure 4-142) -> Vid key (Figure 4-143) Figure 4-143
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. OAM Configure Resource (Figure 4-138) -> MA Navig. key (Figure 4-141) -> MEP Navigation key (Figure 4-144)
(Available after MA-Create, after selecting an MA in the table of Figure 4-141) Figure 4-144
OAM: Configure: MA Navig.: MEP Navigation
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 3 1 Issue 05 February 2010
Craft Terminal for ES Management
OAM
............................................................................................................................................................................................................................................................
The window of Figure 4-144 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. OAM Configure Resource (Figure 4-138) -> MA Navig. key (Figure 4-141) -> MEP Navigation key (Figure 4-144) -> Create key (Figure 4-145) Figure 4-145 OAM: Configure: MA Navig.: MEP Navigation: Create MEP
The window in Figure 4-145 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. It contains the following parameters: •
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 “Views -> Search” (p. 4-35)), 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-142, (pg. 4-230))
•
Cci Enabled: (true / false), to enable CCI, only false; (not operative)
•
Ltm Priority: to associate a priority (0 to 7) to the Link Trace Message, inserted into
VLAN-Tag; default is 7 •
Status: actual state of this MEP (up/down), i.e. in-service/out-of-service
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 23 2 Issue 05 February 2010
Craft Terminal for ES Management
OAM
............................................................................................................................................................................................................................................................
•
•
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
OAM Configure Resource (Figure 4-138) -> MA Navig. key (Figure 4-141) -> MEP Navigation key (Figure 4-144) -> Modify key
This Modify key permits to change some parameters of the selected MEP, after it has been created as seen in Figure 4-145. OAM Configure Resource (Figure 4-138) -> MA Navig. key (Figure 4-141) -> MEP Navigation key (Figure 4-144) -> LoopBack key (Figure 4-146).
(Available after MEP-Create, after selecting a MEP in the table of Figure 4-144). Figure 4-146
OAM: Configure: MA Navig.: MEP Navigation: Loop Back
The window in Figure 4-146 permits to define and start a LoopBack message. It contains the following parameters: •
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-148) •
Target MAC Address: MAC address of the target MEP that has to respond to this
LoopBack message. This Address can be read in the far MEP-Properties of the node to be reached. Note:
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 3 3 Issue 05 February 2010
Craft Terminal for ES Management
OAM
............................................................................................................................................................................................................................................................
•
LoopBack Type: the only permitted value is Dest. MACADDRESS; i.e. the LB is done
in base of the only MacAddress 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.
OAM Configure Resource (Figure 4-138) -> MA Navig. key (Figure 4-141) -> MEP Navigation key (Figure 4-144) -> LinkTrace key (Figure 4-147)
(Available after MEP-Creation, after selecting a MEP in the table of Figure 4-144) Figure 4-147 OAM: Configure: MA Navig.: MEP Navigation: Link Trace
The window in Figure 4-147 permits to define and start a Link Trace (LT) message. It contains the following parameters: •
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 MacAddress 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 23 4 Issue 05 February 2010
Craft Terminal for ES Management
OAM
............................................................................................................................................................................................................................................................
•
Transmit Ltm TTL: max rnumber of bridge nodes this message can traverse before
expiring •
LinkTrace Result: reporting the result (OK/KO) of the Link Trace test, after having clicked on the Start key. After having clicked on Show Result key, it will report, on
any row of the table, the parameters corresponding to each bridge that responded to this LTM. The Show Result key displays the detailed test results. It causes the displaying of LT results on the above Link Trace Result table. Reported parameters (for each crossed bridge): – Entry; TTL; Forwarded; Terminal Mep; LastEgressIdentifier; NextEgressIdentifier; Relay; Ingress; IngressMac; Egress; EgresMac OAM Configure Resource (Figure 4-138) -> MA Navig. key (Figure 4-141) -> MEP Navigation key (Figure 4-144) -> Details key (Figure 4-148) Figure 4-148
OAM: Configure: MA Navig.: MEP Navigation: Details
This window in Figure 4-148 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 3 5 Issue 05 February 2010
Craft Terminal for ES Management
OAM
............................................................................................................................................................................................................................................................
OAM Configure Resource (Figure 4-138) -> MA Navig. key (Figure 4-141) -> Show All MEP key (Figure 4-149) Figure 4-149 OAM: Configure: MA Navig.: Show All MEP
The window in Figure 4-149 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 for Figure 4-148, (pg. 4-235).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 23 6 Issue 05 February 2010
Craft Terminal for ES Management
OAM
............................................................................................................................................................................................................................................................
OAM Configure Resource (Figure 4-138) -> MA Navig. key (Figure 4-141) -> MA-MEP List ID key (Figure 4-150) Figure 4-150
OAM: Configure: MA Navig.: MA-MEP List ID
The window in Figure 4-150 permits to search all existing MEP’s. It contains the same fields described for Figure 4-149. OAM Configure Resource (Figure 4-138) -> MA Navig. key (Figure 4-141) -> Modify key (Figure 4-151) (Available after MA-Creation, after selecting a MA in the table of Figure 4-141) Figure 4-151
OAM: Configure: MA Navig.: Modify
The window in Figure 4-151 is very similar to Figure 4-142 (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-152.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 3 7 Issue 05 February 2010
Craft Terminal for ES Management
OAM
............................................................................................................................................................................................................................................................
OAM Configure Resource -> MA Navig. key -> Modify key -> Show key Figure 4-152 OAM: Configure: MA Navig.: Modify: Show
OAM Configure Resource (Figure 4-138) -> MA Navig. key (Figure 4-141) -> Details key (Figure 4-153) (Available after MA-Creation, after selecting a MA in the table of Figure 4-141) Figure 4-153 OAM: Configure: MA Navig.: Details
The window in Figure 4-153 permits to get details about the selected MA. It contains the same parameters described for Figure 4-142 (Create MA).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 23 8 Issue 05 February 2010
Craft Terminal for ES Management
OAM
............................................................................................................................................................................................................................................................
OAM Configure Resource (Figure 4-138) -> MA Navig. key (Figure 4-141) -> Delete key (Figure 4-154) (Available after MA-Creation, after selecting a MA in the table of Figure 4-141) Figure 4-154
OAM: Configure: MA Navig.: Delete
The window in Figure 4-154 permits to delete the selected MA, and all MEP’s related to it. OAM Domain -> Properties Resources (OAM) This option is obtained, by selecting in the menu-bar: OAM Domain -> Properties Resources (OAM)
An example of the window displayed is reported in Figure 4-155, (pg. 4-239). The function of this option is to show the parameters configured for OAM. It reports, in read-only mode, the same parameters described in “OAM Domain -> Configure Resources (OAM)” (p. 4-227). Figure 4-155
OAM: Properties Resources
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 3 9 Issue 05 February 2010
Craft Terminal for ES Management
OAM
............................................................................................................................................................................................................................................................
OAM Domain -> Configure (OAM) This option is obtained, by selecting in the menu-bar: OAM Domain -> Configure (OAM)
An example of the window displayed is reported in Figure 4-156. The function of this option is to configure the global OAM parameters for this bridge. Important!
These parameters will be used either for StandardOAM (see “OAM Domain -> Configure Resources (OAM)” (p. 4-227)), and for Proprietary loop-back (see “OAM Domain -> Configure LoopBack (OAM)” (p. 4-241)).
Figure 4-156 OAM: Configure
The window in Figure 4-156 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. OAM Domain -> Properties (OAM) This option is obtained, by selecting in the menu-bar: OAM Domain -> Properties (OAM)
An example of the window displayed is reported in Figure 4-157. The function of this option is to show, in read-only mode, the configured parameters, described in “OAM Domain -> Configure (OAM)” (p. 4-240).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 24 0 Issue 05 February 2010
Craft Terminal for ES Management
OAM
............................................................................................................................................................................................................................................................
Figure 4-157
OAM: Properties
OAM Domain -> Configure LoopBack (OAM) This option is obtained, by selecting in the menu-bar: OAM Domain -> Configure Loop Back (OAM)
An example of the window displayed is reported in Figure 4-158. The function of this option is to configure a Proprietary Loop Back. These parameters are thus independent from configurations described in “OAM Domain -> Configure Resources (OAM)” (p. 4-227). The only parameters used here will be those ones set as seen in “OAM Domain -> Configure (OAM)” (p. 4-240). 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-158
OAM: Configure LoopBack
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 4 1 Issue 05 February 2010
Craft Terminal for ES Management
OAM
............................................................................................................................................................................................................................................................
The window in Figure 4-158 contains the following fields: •
MAC Address Dest.: MAC address of remote NE to be reached.
This parameter can be read in the (global) OAM Properties of the far bridge to be reached, as seen in Figure 4-157, (pg. 4-241).
Note:
•
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-158, (pg. 4-241).
Click on Start key to initiate this LB message. Figure 4-159 OAM: Configure Loop Back: Test List
This window in Figure 4-159 contains the list of executed LB tests, available only if saved by using Add Test key seen in Figure 4-158, (pg. 4-241). 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-158, (pg. 4-241). ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 24 2 Issue 05 February 2010
Craft Terminal for ES Management
OAM
............................................................................................................................................................................................................................................................
•
Modify: it permits to change some parameters for the selected LB test. It opens the
window reported in Figure 4-160. •
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-160
OAM: Configure Loop Back: Test List: Modify
This window in Figure 4-160 permits to change some parameters relevant to the LB-Test selected in Figure 4-159, (pg. 4-242). Test parameters are described within previous Figure 4-158, (pg. 4-241). OAM Domain -> Loop Back Properties (OAM) This option is obtained, by selecting in the menu-bar: OAM Domain -> Loop Back Properties (OAM)
An example of the window displayed is reported in Figure 4-161. The function of this option is to show, in read-only mode, the same parameters described in “OAM Domain -> Configure LoopBack (OAM)” (p. 4-241), in particular, Figure 4-158, (pg. 4-241). Figure 4-161
OAM: Loop Back Properties
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 4 3 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
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 relevant tab of the main view. Note:
All the dialog windows described in this handbook are reported in Full Window mode, the information fields reported in the Tabbed Window mode are the same (see “Windows Presentation: “Full Window" and “Tabbed Window"” (p. 4-34)). Important!
ISA-ES16 supports (in mutually exclusive mode) the following working modalities (see“Transmission -> ISA -> Configure ISA” (p. 4-71)): General Bridge Management modalities: –
none: for non-bridge functions (ETS and MPLS)
–
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. Connection -> Bridge -> Filtering Data Base This option is obtained, after selecting the Switch symbol ( contextual pop-up menu, or by selecting in the menu-bar:
), by means of the
Connection -> Bridge Management -> Filtering Data Base.
WARNING This option is not allowed in in Bridge Type = none as referred in “Transmission -> ISA -> Configure ISA” (p. 4-71)). An example of the window displayeds are reported from Figure 4-162, (pg. 4-246) to Figure 4-165, (pg. 4-250). 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 24 4 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
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. 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/MacAddres 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 tabled: 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/MacAddresses. 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 (see Figure 4-162, (pg. 4-246)):
It reports all the Dynamic auto-learnt FDB instances. •
• • •
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 couple. MAC Address: MacAddress 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 4 5 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
•
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-166, (pg. 4-250). Figure 4-162 Filtering Data Base/Dynamic Filtering Database (Virtual Bridge case)
•
Static Unicast Filtering sector (see Figure 4-163, (pg. 4-248)):
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 8DG15624AAAA 4 - 24 6 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
The MAC address must be written separating each octet with a colon, e.g.: “28:29:30:aa:bb:cc”. Note:
Keep the following steps, in order to insert a new static forwarding instance: 1. click on New key 2. choose, on VLANID field, the desired value, by means of the pull-down menu (all the registered VLAN’s are listed) 3. type, on MAC ADDRESS field, the appropriate MacAddress 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. 4. choose the port on which the frames having the selected VID/MacAddresses 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. 5. 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 “Member Set" associated with the selected VLAN (i.e. registered, see “Transmission -> ISA -> VLAN Registration” (p. 4-155)). – In the Bridge Type = bridge 802.1S-AD (Provider) case, it reports all the active ETB and ETS ports registered on the selected VLANID.
•
–
In the Bridge Type = bridge 802.1Q (Virtual) case, it reports all the active ETB ports registered on the selected VLANID.
–
In the Bridge Type = bridge 802.1D (MAC) case, it reports all the active ETB ports.
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 4 7 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Figure 4-163 Filtering Data Base/Static Unicast Filtering (Virtual Bridge case)
•
Static Multicast Filtering sector (see Figure 4-164, (pg. 4-249)):
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 mostsignificant-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/MacAddresses couple) can be sent to a group of stations and, correspondingly, to a group of ports (Egress Ports).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 24 8 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Figure 4-164
•
Filtering Data Base/Static Multicast Filtering (Virtual Bridge case)
Dynamic Multicast Filtering sector, (see Figure 4-165, (pg. 4-250)):
It reports the Dynamic-Multicast FDB instances, in particular the IGMP dynamic instances. • VLANID: applicable only in case of Bridge Type = bridge 802.1S-AD (Provider) or Bridge Type = bridge 802.1Q (Virtual) (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 MacAddress 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 4 9 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Figure 4-165 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 Help key gives helps about this function. 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-166 Filtering Data Base/Learned Mac Address Details
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 25 0 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Connection -> Bridge -> Segregated Port Management This option is obtained, after selecting the Node resource ( contextual pop-up menu, or by selecting in the menu-bar:
), by means of the
Connection -> Bridge Management -> Segregated Port Management.
An example of the window displayed is reported in Figure 4-167.
WARNING This option is not allowed in Bridge Type = none as referred in “Transmission -> ISA -> Configure ISA” (p. 4-71)). The function of this option is to activate the Segregation capability of the node and to show the List of Segregated Ports of the Bridge (only ETB ports in case MAC/Virtual, ETB and ETS in Provider Bridge). For more details see also “Bridging Data Plane” (p. 1-79). The dialog window contains the following items: •
Segregation Status: possible options:
–
up: it activates the Segregation capability of the node
–
down: it deactivates the Segregation capability of the node Important! This item must be set in up state, before using the option
described in next “” (p. 4-251), otherwise it will not be possible. •
Segregated Port List:
It reports the list of the existing segregated port, configured by means of the option described in next “” (p. 4-251). Figure 4-167
Segregated Port Management
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 5 1 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Connection -> Ethernet Port -> Segregated Port Set This option is obtained, after selecting a 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: Connection -> Ethernet Port Management -> Segregated Port Set.
or, if a LAG resource has been selected: Connection -> Link Aggregator Group Management -> Segregated Port Set.
WARNING This option is not allowed in Bridge Type = none as referred in “Transmission -> ISA -> Configure ISA” (p. 4-71)). Important! It is possible only after the configuration of the bridge Segregation Status in up state, as described in the previous
“Connection -> Bridge -> Segregated Port Management” (p. 4-251). See also “Bridging Data Plane” (p. 1-79) Note:
This procedure applies also in case of LAG resource.
This function permits to enable or disable the Segregation Status of a Port/LAG (only ETB ports in case MAC/Virtual, ETB and ETS in Provider Bridge). This option contains two sub-options: •
Enable Participation: it includes the selected port into the segregated group of the
bridge. •
Disable Participation: it excludes the selected port from the segregated group of the
bridge. After this operation, the ports set in Enable Participation will be displayed in the Segregated Port List displayed in the window described in the previous “Connection -> Bridge -> Segregated Port Management” (p. 4-251). Ethernet Port: application table in the Connection context An example of Application Table associated to the Ethernet Port is illustrated in Figure 4-168. It is displayed in the area A2, after selecting the Ethernet Port in the resource-tree. It reports, in tabular form, the main parameters related to the existing connections into the selected Port: ETS InFlow, Status, ETS OutFlow. Note:
The Connection view displays in the tool-bar a further fastkey, for quick recalling the Ethernet Port option Create XC One Step.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 25 2 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
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-168
Ethernet Port: Connection application table
Create XC One Step "Fast Key"
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 5 3 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Connection -> Ethernet Port -> Create ETS XC One Step (ETS & MPLS Tunnel-Head) This option is obtained, after selecting an active ETS Ethernet 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: 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. Note:
This option can also be quickly recalled by the further fastkey added into the tool bar.
WARNING •
This description applies only if Bridge Type = none as referred in “Transmission -> ISA -> Configure ISA” (p. 4-71)); for Bridge Type = bridge 802.1D (MAC) or Bridge Type = bridge 802.1Q (Virtual) or Bridge Type = bridge 802.1S-AD (Provider) cases see“Connection -> Ethernet Port -> Create ETS XC One Step (MAC & Virtual)” (p. 4-264) and “Connection -> Ethernet Port -> Create ETS XC One Step (Provider)” (p. 4-267).
•
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-xxiv), for details about SDH configuration and connection.
•
In order to create an XC for MPLS Tunnel, the involved Tunnels resources must have been already created, as specified in “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111).
•
The traffic descriptors (TD, ETS and MPLS) for the involved resources have to be created as described in “Configuration -> Traffic Descriptor -> ETS Traffic Descriptor” (p. 4-56) and “Configuration -> Traffic Descriptor -> MPLS Traffic Descriptor” (p. 4-67). The bandwidth matching and MPLS Labelling rules are described in “MPLS Tunnel: Labelling and Bandwidth Matching” (p. 1-32).
An example of the window displayed is reported in Figure 4-169, (pg. 4-258). A structure example of Ethernet over SDH link is illustrated in Figure 1-11, (pg. 1-19). A generic link structure example of MPLS tunnelling over SDH is illustrated in Figure 1-20, (pg. 1-40). A generic link structure example of MPLS tunnelling over Ethernet is illustrated in Figure 1-21, (pg. 1-42).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 25 4 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Some examples of Ethernet XC link creations are reported in “Ethernet Private Line (EPL), end to end implementation example” (p. 1-22) till to “E-VPL, end to end implementation example” (p. 1-27). Some examples of MPLS XC link creations are reported in “MPLS Applications” (p. 1-31) till to “Example of MPLS over Ethernet Tunnelling creation” (p. 1-40). The function of this option is to create a One-Step cross-connection, i.e. the connection point of an ETS Ethernet Port in automatic mode, starting from the parent ethernet port (Ingress); it is also used to create connections between ETS resources and MPLS tunnels (Head). Connections starting from MPLS tunnels (Tail) are described in next paragraph. The Ingress and Egress connection points can also be contained in the same port. The necessary InFlow/Classifier/OutFlow, etc. resources will be automatically created. To create a One Step connection, fill fields and areas as follows: •
Port Eth. Ingress: name of the selected Ethernet Port, fixed to “ingress" by the system.
•
Topology Xc: fixed by the system to XC ETS Unicast or to XC ETS multicast,
depending if one or more egress legs have been added by means of the contiguous Add key. •
Port Egress: name of the “egress" Ethernet Port
this item is browsed by means of the in “Views -> Search” (p. 4-35).
key, that recalls the Search dialog described
WARNING The “Egress" may also be an “Inner MPLS Tunnel (HEAD)", that must have been already created as described in “Transmission -> ETS InFlow -> Create ETH2ETS Classifier” (p. 4-126). •
Add: after selecting the “Egress" port, this key adds it as a leg of the XC in the adjacent
field, to build a “multicast” connection. •
Traffic Section: Traffic Descriptor: to indicate the name of the associated traffic
descriptor (TD); the key permits to choose and associate a traffic descriptor to the data flow, recalling the dialog described in “Configuration -> Traffic Descriptor -> ETS Traffic Descriptor” (p. 4-56).
WARNING This TD (relative to the ingress) has to be consistent with the type of resource connected at the egress, and also with the associated Policing and Color Profile (see “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111)); in case of MPLS tunnel, it must be consistent with the TD associated to the tunnel, see “MPLS Tunnel: Labelling and Bandwidth Matching” (p. 1-32). •
Classifier section: parameters meanings and setting are as explained in “Transmission
-> ETS InFlow -> Create ETH2ETS Classifier” (p. 4-126). ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 5 5 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Note:
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:
–
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 (ETH Type 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: ETH Type; 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: ETH Type (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-170, (pg. 4-258), permitting to view the Topology Classification Properties. •
Inflow Section: parameters meanings and setting are as explained in “Transmission ->
Ethernet Port -> Create ETS InFlow” (p. 4-111).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 25 6 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
•
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-171, (pg. 4-259), that lists all the available protocols (Bit Name as referred in “Protocols” (p. 1-43)) 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 statuses.
Outflow Section: parameters meanings and setting are as explained in “Transmission -
> Ethernet Port -> Create ETS OutFlow” (p. 4-117).
WARNING In case of connection to MPLS Tunnel, the “VLAN Management" option must not be used. •
History area: reporting the operations executed by the procedure on doing the current
connection. This procedure will create the following resources: – one ETS InFlow under the Ingress port, with its associated Classifier; –
one (or more, if Multicast) OutFlow under the Egress port;
–
one XC between the InFlow and the OutFlow;
if the egress is MPLS, it will create also the necessary MPLS InSegment/OutSegment resources. After setting all the desired parameters, click on the Apply key to set up the cross connection. The window will be closed without doing any operation by clicking on Cancel key. 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. The Help key gives helps about this function.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 5 7 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Figure 4-169 Create ETS XC “One Step" - Ethernet example
Figure 4-170 Topology Classification Properties (examples)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 25 8 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Figure 4-171
Protocol List
Connection -> Ethernet Port -> Create ETS XC One Step (ETS Virtual Switch) This option is obtained, after selecting an active ETS Ethernet 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: 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. Note:
This option can also be quickly recalled by the further Fast-key added into the tool bar.
WARNING •
This description applies only in Bridge Type = none as referred in “Transmission -> ISA -> Configure ISA” (p. 4-71).
•
The traffic descriptors (TD) for the involved resources have to be created as described in “Configuration -> Traffic Descriptor -> ETS Traffic Descriptor” (p. 4-56).
•
The ETS Virtual Switch connection can be done only if the two involved Ethernet Ports have been configured for this type of service, as described in “Transmission -> Ethernet Port -> Characterization Service” (p. 4-103).
An example of the window displayed is reported in Figure 4-172, (pg. 4-260). The ETS Virtual Switch connection permits to create unicast cross-connections among inflows and outflows belonging to two Ethernet Ports characterized for “ETS Virtual Service”.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 5 9 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
In order to create a bidirectional connection, a unicast XC is done over an ETH Port, and then a second unicast XC must be done over the other partner port, for the opposite direction. Many differentiated data-flows connections can be done between the two partner ports, but they can not be connected to third different ports. The procedure and parameters meanings are the same as what described in “Connection > Ethernet Port -> Create ETS XC One Step (ETS & MPLS Tunnel-Head)” (p. 4-254). Figure 4-172 Create ETS XC “One Step" - ETS Virtual Switch example
Connection -> Inner (Outer) MPLS Tunnel -> Create ETS XC One Step (Tunnel-Tail) This option is obtained, after selecting an active Inner MPLS Tunnel (TAIL), or (in case of MPLS over Ethernet) an Outer MPLS Tunnel (TAIL), by means of the contextual pop-up menu, or by selecting in the menu-bar: •
in case of Inner MPLS Tunnel (TAIL
):
Connection -> Inner MPLS Tunnel (TAIL) -> Create ETS XC One Step. •
in case of MPLS over Ethernet, selecting an Outer MPLS Tunnel (TAIL ): Connection -> Outer MPLS Tunnel (TAIL) -> Create ETS XC One Step.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 26 0 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Note:
This option can also be quickly recalled by the further fastkey added into the tool bar.
WARNING •
This description applies also for connections starting from an Outer MPLS Tunnel (TAIL) in case of MPLS over Ethernet.
•
This description applies only in Bridge Type = none as referred in “Transmission -> ISA -> Configure ISA” (p. 4-71); for Bridge Type = bridge 802.1D (MAC) or Bridge Type = bridge 802.1Q (Virtual) or Bridge Type = bridge 802.1S-AD (Provider) cases see“Connection -> Ethernet Port -> Create ETS XC One Step (MAC & Virtual)” (p. 4-264) and “Connection -> Ethernet Port -> Create ETS XC One Step (Provider)” (p. 4-267).
•
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-xxiv), for details about SDH configuration and connection.
•
To connect an MPLS Tunnel (HEAD) follow the procedure described in “Connection -> Ethernet Port -> Create ETS XC One Step (ETS & MPLS Tunnel-Head)” (p. 4-254).
•
In order to create an XC for MPLS Tunnel, the involved Tunnels resources must have been already created, as specified in “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111).
•
The traffic descriptors (TD, ETS and MPLS) for the involved resources have to be created as described in “Configuration -> Traffic Descriptor -> ETS Traffic Descriptor” (p. 4-56) and “Configuration -> Traffic Descriptor -> MPLS Traffic Descriptor” (p. 4-67). The bandwidth matching and MPLS Labelling rules are described in “MPLS Tunnel: Labelling and Bandwidth Matching” (p. 1-32).
An example of the window displayed is reported in Figure 4-173, (pg. 4-263). A structure example of Ethernet over SDH link is illustrated in Figure 1-11, (pg. 1-19). A generic link structure example of MPLS tunnelling over SDH is illustrated in Figure 1-20, (pg. 1-40). A generic link structure example of MPLS tunnelling over Ethernet is illustrated in Figure 1-21, (pg. 1-42). Some examples of Ethernet XC link creations are reported in “Ethernet Private Line (EPL), end to end implementation example” (p. 1-22) till to “E-VPL, end to end implementation example” (p. 1-27). Some examples of MPLS XC link creations are reported in “MPLS Applications” (p. 1-31) till to “Example of MPLS over Ethernet Tunnelling creation” (p. 1-40). ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 6 1 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
The function of this option is to create a One-Step cross-connection, i.e. the connection point in automatic mode, starting from the parent Ingress resource (TAIL_MPLS Tunnel). The Ingress and Egress connection points can also be contained in the same port. The necessary InFlow/OutFlow, InSegment/OutSegment, etc. resources will be automatically created. To create a One Step connection, fill fields and areas as follows: •
Inner MPLS Tail: name of the selected MPLS Tunnel, fixed to ingress by the system.
•
Topology Xc: fixed by the system to XC ETS Unicast or to XC ETS multicast, depending if one or more legs have been added by means of the contiguous Add key.
•
Port Egress: name of the egress Ethernet Port
this item is browsed by means of the in “Views -> Search” (p. 4-35).
key, that recalls the Search dialog described
WARNING The Egress may also be an Outer MPLS Tunnel (HEAD) that must have been already created (see WARNING above). •
Add: after selecting the Egress port, this key adds it as a leg of the XC in the adjacent field
•
Traffic Section -> Traffic Descriptor: to indicate the name of the associated traffic
descriptor (TD); the key permits to choose and associate a traffic descriptor to the data flow, recalling the dialog described in “Configuration -> Traffic Descriptor -> ETS Traffic Descriptor” (p. 4-56).
WARNING This TD (relative to the ingress) has to be consistent with the type of resource connected at the egress; in case of MPLS tunnel, it must be consistent with the TD associated to the tunnel, see “MPLS Tunnel: Labelling and Bandwidth Matching” (p. 1-32). •
Inflow Section: parameters meanings and setting are as explained in “Transmission ->
Ethernet Port -> Create ETS InFlow” (p. 4-111). •
Outflow Section: parameters meanings and setting are as explained in “Transmission -
> Ethernet Port -> Create ETS OutFlow” (p. 4-117).
WARNING In case of MPLS over Ethernet, the VLAN Management option must not be used. •
History area: reporting the operations executed by the procedure on doing the current
connection. This procedure will create the following resources: – one ETS InFlow under the MPLS Tunnel; ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 26 2 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
–
one OutFlow under the Egress port;
–
one XC between the InFlow and the OutFlow;
it will create also the necessary MPLS InSegment/OutSegment resources. After setting all the desired parameters, click on the Apply key to set up the cross connection. The window will be closed without doing any operation by clicking on Cancel key. 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. The Help key gives helps about this function. Figure 4-173
Create ETS XC “One Step" - MPLS Tunnel (TAIL)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 6 3 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Connection -> Ethernet Port -> Create ETS XC One Step (MAC & Virtual) This option is obtained, after selecting an active ETS Ethernet 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: 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 “Transmission -> ISA -> Configure ISA” (p. 4-71); for the Provider bridge case see “Connection -> Ethernet Port -> Create ETS XC One Step (Provider)” (p. 4-267). 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-xxiv), for details about SDH configuration and connection. This connection is possible only if the Characterization Service for the two involved ports has been set as Port-To-Port: see “Transmission -> Ethernet Port -> Characterization Service” (p. 4-103). An example of the window displayed is reported in Figure 4-174, (pg. 4-266). An example of Mac/Virtual Port-to-Port (p2p) XC structure is illustrated in Figure 1-7, (pg. 1-15). An example of Port-to-Port XC (or EPL) link creation is reported in “Ethernet Private Line (EPL), end to end implementation example” (p. 1-22). The function of this option is to create a One-Step cross-connection, i.e. the connection point of an ETS Ethernet Port 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-175, (pg. 4-266)). 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 One Step connection, fill fields and areas as follows: •
Port ETH. Ingress: name of the selected Ethernet Port, fixed to ingress by the system.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 26 4 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
•
•
•
Port ETH. Egress: name of the egress Ethernet Port
this item is browsed by means of the key, that recalls the Search dialog described in “Views -> Search” (p. 4-35). Connection Type: (settable only after the choice of the above egress Ethernet Port) possible pull-down options: –
UniDirectional: to create 1 Inflow into the Ingress Port and 1 OutFlow into the Grasshopper, 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. The window will be closed without doing any operation by clicking on Cancel key. 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. The Help key gives helps about this function.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 6 5 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Figure 4-174 Create ETS XC “One Step"
Figure 4-175 Error message on “Create ETS XC One Step"
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 26 6 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Connection -> Ethernet Port -> Create ETS XC One Step (Provider) This option is obtained, after selecting an active ETS Ethernet 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: 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. Note:
This option can also be quickly recalled by the further fastkey added into the tool bar.
WARNING This option is not available if the Port is ETB type. This description applies only in Bridge Type case set to bridge 802.1S-AD (Provider) as referred in “Transmission -> ISA -> Configure ISA” (p. 4-71); for the bridge 802.1S-AD (MAC) or bridge 802.1Q (Virtual) see “Connection -> Ethernet Port -> Create ETS XC One Step (MAC & Virtual)” (p. 4-264). 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-xxiv), for details about SDH configuration and connection. 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 “Transmission -> ISA -> VLAN Registration” (p. 4-155). The traffic descriptors (TD) for the involved resources have to be created as described in “Configuration -> Traffic Descriptor -> ETS Traffic Descriptor” (p. 4-56). The bandwidth matching and MPLS -Labelling rules are described in “MPLS Tunnel: Labelling and Bandwidth Matching” (p. 1-32). 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. The type of cross-connection that can be done is defined as described in “Transmission -> Ethernet Port -> Characterization Service” (p. 4-103): PortTo-Port, or Other for Uni-Uni / Uni-Nni / Nni-Uni services. This connection is possible only if the Characterization Service for the two involved ports has been set as Other: see “Transmission -> Ethernet Port -> Characterization Service” (p. 4-103). An example of Provider domain distribution is illustrated in Figure 1-10, (pg. 1-17), other examples and procedures for this connection are reported in “MEF (Metro Ethernet Forum) Applications” (p. 1-20). ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 6 7 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
An example of the window displayed is reported in Figure 4-176, (pg. 4-268). The function of this option is to create a One-Step cross-connection, i.e. the connection point of an ETS Ethernet Port 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. 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 One Step connection, fill fields and areas as follows (see Figure 4-176): •
Topology: to choose the XC type; possible pull-down options: •
UNI->UNI: to create an XC from a User-Interface to another User-Interface, (i.e.
•
between two ETS Ports) passing through the Bridge domain; in this case the procedure will continue, after clicking on Next >> key, as explained in point 1. (p. 4-268). UNI->NNI: to create an XC from a User-Interface to a Network-Interface, (i.e. from an ETS Port to the Bridge) 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-272).
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, (i.e. from
the Bridge to an ETS Port) 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 3. (p. 4-273). Figure 4-176 Topology for “Create ETS XC One Step" (Provider)
1. UNI->UNI: refer to Figure 4-177, (pg. 4-272): • Port Ingress: name of the selected Ethernet Port, fixed by the system.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 26 8 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
•
Port Egress: name of the egress Ethernet Port
this item is browsed by means of the key, that recalls the Search dialog described in “Views -> Search” (p. 4-35). • •
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 dialog described in “Configuration -> Traffic Descriptor -> ETS Traffic Descriptor” (p. 4-56).
–
Provider Traffic Descriptor: name of the associated Provider traffic descriptor; Note: The operations are the same as explained above, but 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.
•
Classifier Section: parameters meanings and setting are as explained in “Transmission
-> ETS InFlow -> Create ETH2ETS Classifier” (p. 4-126). 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: – 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 (ETH Type is without IP values)
–
VLAN/No_Ip: in this case, the following parameters will be displayed, and thus editable: VLAN / MaxVLAN, (ETH Type is fixed without IP values)
–
Untagged+ETHType: in this case, the following parameters will be displayed, and thus editable: ETH Type; 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: ETH Type (without IP values); the other parameters will be fixed to set the frame as “untagged”
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 6 9 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
–
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-180, (pg. 4-275), permitting to view the Topology Classification Properties. •
Bridge Management section:
Parameters meanings and setting are as explained in “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111). •
•
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: the policing is based on the associated TD and on the priority colors of the associated Color Profile explained below
Color Profile: (see “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111); indicating the name of the association between the VLAN userpriorities and the Provider-VLAN traffic coloring; Note: If a Color Profile is associated, the Traffic Descriptor 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 dialog described in “Transmission -> Ethernet Port -> Create InFlow/Color Profile” (p. 4-114). the
key gives the properties of the color profile currently associated
the X key permits to untie the data flow from the color profile •
VLAN Pop: possible values: disabled or enabled; if enabled it pops out the “VLAN" shim fields of the ethernet frame. Note:
If this is enabled, the priority field of the relevant Classifier must be different from untagged or don't care
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 27 0 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
•
S-VID: (this parameter is described in “Unbound means that “0" value is associated to the VLAN Management field, or the Unbind key has been clicked; Bound means that a VLAN-management profile has been assigned to this Outflow: in this case the Stacked-VLAN “shim" header is “pushed" into the ethernet frame.” (p. 4-120) and also in “Transmission -> Ethernet Port -> Create Provider OutFlow” (p. 4-123)) 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 dialog as in Figure 4-180, (pg. 4-275); 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 “Transmission -> ISA -> VLAN Registration” (p. 4-155). •
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-182, (pg. 4-279), that lists all the available protocols (Bit Name as referred in “Protocols” (p. 1-43)) 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.
User Label section:
optional name that can be assigned by the user to describe the involved resources. • OutFlow VLAN Stack: it permits to “push” the VLAN-tag into the frames; its setting is described in “Transmission -> ETS OutFlow -> Modify ETS OutFlow” (p. 4-125). •
History area: reporting the operations executed by the program (after clicking on Apply) on doing the current connection.
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;
–
one Provider InFlow under the Egress port;
–
one ETS OutFlow under the Egress port;
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 7 1 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
–
one XC between the ETS OutFlow and the Provider InFlow under the Egress port;
See more details about the created resources reported in the Note: at the end of this paragraph. Figure 4-177 Create ETS XC “One Step" (Provider, UNI-UNI)
2. UNI->NNI: refer to Figure 4-178, (pg. 4-273): • Port Ingress: name of the selected Ethernet Port, 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 dialog described in “Configuration -> Traffic Descriptor -> ETS Traffic Descriptor” (p. 4-56). •
Classifier section:
Parameters meanings and setting are as explained in UNI-UNI procedure in point 1. (p. 4-268). See also “Transmission -> ETS InFlow -> Create ETH2ETS Classifier” (p. 4-126). ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 27 2 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
•
Bridge Management section:
•
Parameters meanings and setting are as explained in UNI-UNI procedure in point 1. (p. 4-268). See also “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111). User Label section: Parameters meanings and setting are as explained in UNI-UNI procedure in point 1. (p. 4-268). See also “Transmission -> Ethernet Port -> Create ETS OutFlow” (p. 4-117).
Figure 4-178
Create ETS XC “One Step" (Provider, UNI-NNI)
3. NNI->NNI: refer to Figure 4-179, (pg. 4-275): • Port Ingress: name of the selected Ethernet Port, 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 dialog described in “Configuration -> Traffic Descriptor -> ETS Traffic Descriptor” (p. 4-56). ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 7 3 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
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.
Note:
•
Bridge Management section:
•
Parameters meanings and setting are as explained in UNI-UNI procedure in point 1. (p. 4-268). See also “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111). User Label section:
•
Parameters meanings and setting are as explained in UNI-UNI procedure in point 1. (p. 4-268). See also “Transmission -> Ethernet Port -> Create ETS OutFlow” (p. 4-117). History area: reporting the operations executed by the program on doing the current connection. This option will create the following resources: – one Provider InFlow under the Ingress port; –
one ETS OutFlow under the Ingress port;
–
one XC between the Provider InFlow and the ETS OutFlow under the Ingress port;
See more details about the created resources reported hereunder. Note:
For the meanings and settings of parameters of the created resources see: –
Create ETS InFlow, “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111).
–
Create ETS OutFlow, “Transmission -> Ethernet Port -> Create ETS OutFlow” (p. 4-117).
–
Create ETH2ETS Classifier, “Transmission -> ETS InFlow -> Create ETH2ETS Classifier” (p. 4-126).
–
ETS XC Properties, “Connection -> ETS InFlow -> ETS XC Properties” (p. 4-284).
–
Create Provider InFlow “Furthermore, this OutFlow does not support VLANManagement function.” (p. 4-153) and “Create Provider InFlow / S-VID Management” (p. 4-122) and also
–
Create Provider OutFlow “Transmission -> Ethernet Port -> Create Provider OutFlow” (p. 4-123), for more details about “S-VID", the parameter configurable in the above explained “Bridge Management section”.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 27 4 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Figure 4-179
Create ETS XC “One Step" (Provider, NNI-UNI)
After setting all the desired parameters, click on the Apply key to set up the cross connection. The window will be closed without doing any operation by clicking on Cancel key. The procedure will return to the previous window, if clicking on Delete ETS XC One Step (ETS & MPLS) This option is obtained, after selecting an active ETS Ethernet Port ( with Admin Status = up) or a LAG ( with Admin Status = up), or an MPLS Tunnel ( ), by means of the contextual pop-up menu, or by selecting in the menu-bar: Connection -> Ethernet Port Management -> Delete ETS XC One Step. •
or, if a LAG (
) resource has been selected:
Connection -> Link Aggregator Group Management -> Delete ETS XC One Step. •
in case of “Inner MPLS Tunnel (TAIL
)":
Connection -> Inner MPLS Tunnel (TAIL) -> Delete ETS XC One Step. •
in case of MPLS over Ethernet, selecting an “Outer MPLS Tunnel (TAIL )": Connection -> Outer MPLS Tunnel (TAIL) -> Delete ETS XC One Step.
WARNING This option is not available if the Port is ETB type. This description applies only for Bridge Type = none as referred in “Transmission -> ISA -> Configure ISA” (p. 4-71); for Bridge Type = bridge 802.1D (MAC) or bridge 802.1Q (Virtual) see “Connection -> Ethernet Port -> Create ETS XC One Step (MAC & Virtual)” (p. 4-264) and “Connection -> Ethernet Port -> Create ETS XC One Step (Provider)” (p. 4-267). An example of the window displayed is reported in Figure 4-181, (pg. 4-277). The function of this option is to delete a One-Step cross-connection, that was created with the Create ETS XC One Step (ETS and/or MPLS) option detailed in “Connection -> Ethernet Port -> Create ETS XC One Step (ETS & MPLS Tunnel-Head)” (p. 4-254). To delete a One Step connection: •
Ethernet / Tunnel: name of the selected resource (set by the system)
Click on Search key to search the cross-connections existing over the indicated resource. The existing cross-connections will be listed into the Active Cross Connection area. Select, on the list, the XC to be deleted and then click on Apply key to delete it. The other parts of the window are: •
History area: reporting the operations executed by the procedure on doing the current connection.
The window will be closed without doing any operation by clicking on Cancel key. 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. The Help key gives helps about this function.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 27 6 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Figure 4-181
Delete ETS XC “One Step" (ETS & MPLS Tunnel)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 7 7 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Connection -> Ethernet Port -> Delete ETS XC One Step (MAC & Virtual) This option is obtained, after selecting an active ETS Ethernet 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: Connection -> Ethernet Port Management -> Delete ETS XC One Step.
or, if a LAG resource has been selected: Connection -> Link Aggregator Group Management -> Delete ETS XC One Step.
WARNING This option is not available if the Port is ETB type. This description applies only in Bridge Type = bridge 802.1D (MAC) or bridge 802.1Q (Virtual) as referred in “Transmission -> ISA -> Configure ISA” (p. 4-71); for the Bridge Type = bridge 802.1S-AD (Provider) see “Connection -> Ethernet Port -> Delete ETS XC One Step (Provider)” (p. 4-280). An example of the window displayed is reported in Figure 4-182, (pg. 4-279). The function of this option is to delete a One-Step cross-connection, that was created with the Create ETS XC One Step option detailed in “Connection -> Ethernet Port -> Create ETS XC One Step (MAC & Virtual)” (p. 4-264). To delete a One Step connection, fill fields and areas as follows: •
Port Ethernet: name of the selected Ethernet Port, fixed by the system.
•
Connection Type: (settable only after the choice of the above egress Ethernet Port).
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.
History area: reporting the operations executed by the program on doing the current
deletion. After setting all the desired parameters, click on the Apply key to delete the cross connection. The window will be closed without doing any operation by clicking on Cancel key. 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. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 27 8 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
The Help key gives helps about this function. Figure 4-182
Delete ETS XC “One Step" (MAC & Virtual)
History box after Apply
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 7 9 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Connection -> Ethernet Port -> Delete ETS XC One Step (Provider) This option is obtained, after selecting an active ETS Ethernet Port or a LAG, by means of the contextual pop-up menu, or by selecting in the menu-bar: Connection -> Ethernet Port Management -> Delete ETS XC One Step.
or, if a LAG resource has been selected: Connection -> Link Aggregator Group Management -> Delete ETS XC One Step.
WARNING This option is not available if the Port is ETB type. This description applies only in Bridge Type = bridge 802.1S-AD (Provider) as referred in “Transmission -> ISA -> Configure ISA” (p. 4-71); for the Bridge Type = bridge 802.1D (MAC) or Bridge Type = bridge 802.1Q (Virtual) cases see “Connection -> Ethernet Port -> Delete ETS XC One Step (MAC & Virtual)” (p. 4-278). An example of the window displayed is reported in Figure 4-183, (pg. 4-281). The function of this option is to delete a One-Step cross-connection, that was created with the Create ETS XC One Step option detailed in “Connection -> Ethernet Port -> Create ETS XC One Step (MAC & Virtual)” (p. 4-264) or “Connection -> Ethernet Port -> Create ETS XC One Step (Provider)” (p. 4-267). To delete a One Step connection, fill fields and areas as shown in Figure 4-183, (pg. 4-281): •
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 “Connection -> Ethernet Port -> Delete ETS XC One Step (MAC & Virtual)” (p. 4-278).
–
Provider: to delete an XC in case the bridge is bridge 802.1S-AD (Provider) type, 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-281), if “XC Topology" is UNI->UNI.
–
point b. (p. 4-282), if “XC Topology" is UNI->NNI.
–
point c. (p. 4-283), if “XC Topology" is NNI->UNI.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 28 0 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Figure 4-183
Topology for Delete ETS XC “One Step" (Provider)
a. “XC Topology" = UNI->UNI: refer to Figure 4-184, (pg. 4-281): – Ethernet Port A: name of the selected Ethernet Port, fixed by the system. –
Ethernet Port B: name of the second connected Ethernet Port
this item is browsed by means of the key, that recalls the Search dialog described in “Views -> Search” (p. 4-35). –
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 UNIUNI 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. Figure 4-184
Delete ETS XC “One Step" (Provider, UNI-UNI)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 8 1 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
b. “XC Topology" = UNI->NNI: refer to Figure 4-185, (pg. 4-282): – Ethernet Port Ingress: name of the selected Ethernet Port, fixed by the system. –
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 UNINNI 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. Figure 4-185 Delete ETS XC “One Step" (Provider, UNI-NNI)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 28 2 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
c. “XC Topology" = NNI->UNI: refer to Figure 4-186, (pg. 4-283): – Ethernet Port Egress: name of the selected Ethernet Port, fixed by the system. –
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 NNIUNI 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 (as shown in each figures). Figure 4-186
Delete ETS XC “One Step" (Provider, NNI-UNI)
The other parts of the window are: •
History area: reporting the operations executed by the program on doing the current
connection. The window will be closed without doing any operation by clicking on Cancel key. 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.
The Help key gives helps about this function.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 8 3 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Connection -> ETS InFlow -> Create ETS XC (not operative)
WARNING This option is not operative; his creation has to be executed by means of the option Connection -> Ethernet Port (or Tunnel) -> Create ETS XC One Step described in “Connection -> Ethernet Port -> Create ETS XC One Step (ETS & MPLS Tunnel-Head)” (p. 4-254) and subsequents. The scope of this paragraph is to describe the settings, meanings and properties of the resource parameters. Connection -> ETS InFlow -> Modify ETS XC This option is obtained, after selecting a connected InFlow, by means of the contextual pop-up menu, or by selecting in the menu-bar: 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 “Connection -> ETS InFlow -> Create ETS XC (not operative)” (p. 4-284). Connection -> ETS InFlow -> ETS XC Properties This option is obtained, after selecting a connected InFlow, by means of the contextual pop-up menu, or by selecting in the menu-bar: Connection -> ETS InFlow Management -> ETS XC Properties.
An example of the window displayed is reported in Figure 4-187, (pg. 4-285). 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 “Connection -> ETS InFlow -> Create ETS XC (not operative)” (p. 4-284). 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 28 4 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Figure 4-187
ETS XC Properties
Connection -> ETS InFlow -> Delete ETS XC (not operative)
WARNING This option is not operative; his deletion has to be executed by means of the procedure described in “Connection -> Ethernet Port (MPLS Tunnel) -> Delete ETS XC One Step (ETS & MPLS)” (p. 4-276) and subsequents.
Connection -> ETS OutFlow -> Create ETS XC (not operative)
WARNING This option is not operative; his creation has to be executed by means of the option Connection -> Ethernet Port (or Tunnel) -> Create ETS XC One Step described in “Connection -> Ethernet Port -> Create ETS XC One Step (ETS & MPLS Tunnel-Head)” (p. 4-254) and subsequents.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 8 5 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Connection -> ETS OutFlow -> Modify ETS XC (not operative)
WARNING This option is not operative; his modification has to be executed by means of the procedure described in “Connection -> ETS InFlow -> Modify ETS XC” (p. 4-284) and subsequents. Connection -> ETS OutFlow -> ETS XC Properties This option is obtained, after selecting a connected OutFlow, by means of the contextual pop-up menu, or by selecting in the menu-bar: 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 “Connection -> ETS InFlow -> ETS XC Properties” (p. 4-284). Connection -> ETS OutFlow -> Delete ETS XC (not operative)
WARNING This option is not operative; his creation has to be executed by means of the option Connection -> Ethernet Port (or Tunnel) -> Delete ETS XC One Step described in “Connection -> Ethernet Port (MPLS Tunnel) -> Delete ETS XC One Step (ETS & MPLS)” (p. 4-276) and subsequents.
Connection -> MPLS InSegment -> Create MPLS XC (not operative)
WARNING This option is not operative because the InSegment MPLSXC is automatically created by means of the Connection -> Create Tunnel options. Nevertheless the parameters of the InSegment MPLSXC can be visualized with the option InSegment MPLSXC Properties and are described in the relevant paragraph.
Connection -> MPLS InSegment -> Create MPLS Terminating XC (not operative)
WARNING This option is not operative because the InSegment MPLSXC is automatically created by means of the Connection -> Create Tunnel options. Nevertheless the parameters of the InSegment MPLSXC can be visualized with the option InSegment MPLSXC Properties and are described in the relevant paragraph.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 28 6 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Connection -> MPLS InSegment -> Modify MPLS XC (not operative)
WARNING This option is not operative because the InSegment MPLSXC is automatically created by means of the Connection -> Create Tunnel options. Nevertheless the parameters of the InSegment MPLSXC can be visualized with the option InSegment MPLSXC Properties and are described in the relevant paragraph.
Connection -> MPLS InSegment -> Delete MPLS XC (not operative)
WARNING This option is not operative because the InSegment MPLSXC is automatically created by means of the Connection -> Delete Tunnel options.
Connection -> MPLS InSegment -> MPLS XC Properties
WARNING This option is not operative because the InSegment MPLSXC is automatically created by means of the Connection -> Create Tunnel options. Nevertheless the parameters of the InSegment MPLSXC can be visualized with this option. This option is obtained, after selecting a connected InSegment, by means of the contextual pop-up menu; or by selecting, in the menu-bar: Connection -> MPLS InSegment Management -> MPLS XC Properties.
An example of the window displayed is reported in Figure 4-188, (pg. 4-288). The function of this option is to show the parameters set for the selected cross-connection. All the reported information fields are read-only: •
General Info sector:
–
Admin.(istration) Status: up (in service) or down (out-of-service)
–
Oper.(ational) Status: up (active) or down (inactive)
–
Owner: indicating the entity that created and is responsible for managing this
resource. •
Cross Connection sector:
–
MPLS InSegment: indicating the point from which the connection starts (fixed by the system to the selected InSegment)
–
Location: parent resource of this InSegment for the individuation of its position
–
MPLS OutSegment/[...]: this field is not applicable
–
MPLS OutSegment/Location: this area indicates the OutSegment where the
connection is closed and the corresponding location of its parent resource ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 8 7 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
–
Add Leg key: not applicable
–
Del Leg key: not applicable
–
XC Topology sub-area:
this area contains two figures, the first of which represents the current state of the connection, while the second one its future state (not applicable):
Not cross connected points
Unidirectional, unicast cross connected points
Unidirectional, multicast cross connected points
The window will be closed by clicking on Close key. The Help key gives helps about this function. Figure 4-188 MPLS XC Properties
Connection -> MPLS OutSegment -> Create MPLS XC (not operative)
WARNING This option is not operative because the OutSegment MPLSXC is automatically created by means of the Connection -> Create Tunnel options. Nevertheless the parameters of the OutSegment MPLSXC can be visualized with the option OutSegment MPLSXC Properties and are described in the relevant paragraph.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 28 8 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Connection -> MPLS OutSegment -> Create MPLS Originating XC (not operative)
WARNING This option is not operative because the OutSegment MPLSXC is automatically created by means of the Connection -> Create Tunnel options. Nevertheless the parameters of the OutSegment MPLSXC can be visualized with the option OutSegment MPLSXC Properties and are described in the relevant paragraph.
Connection -> MPLS OutSegment -> Modify MPLS XC (not operative)
WARNING This option is not operative because the OutSegment MPLSXC is automatically created by means of the Connection -> Create Tunnel options. Nevertheless the parameters of the OutSegment MPLSXC can be visualized with the option OutSegment MPLSXC Properties and are described in the relevant paragraph.
Connection -> MPLS OutSegment -> MPLS XC Properties
WARNING The OutSegment MPLSXC is automatically created by means of the Connection -> Create Tunnel options. Nevertheless the parameters of the OutSegment MPLSXC can be visualized with this option. This option is obtained, after selecting a connected OutSegment, by means of the contextual pop-up menu; or by selecting, in the menu-bar: Connection -> MPLS OutSegment Management -> MPLS 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“Connection -> MPLS InSegment -> MPLS XC Properties” (p. 4-287). Connection -> MPLS OutSegment -> Delete MPLS XC (not operative)
WARNING This option is not operative because the OutSegment MPLSXC is automatically deleted by means of the Connection -> Delete Tunnel options.
Connection -> MPLS Tunnel Management -> Create Outer Head Tunnel This option is obtained, after selecting the “Main" Tunnel ( contextual pop-up menu; or by selecting, in the menu-bar:
), by means of the
Connection -> MPLS Tunnel Management -> Create Outer Head Tunnel. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 8 9 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
An example of the window displayed is reported in Figure 4-189, (pg. 4-292). The function of this option is to create an Outer Tunnel that can aggregate more Inner Tunnels, in order to transport data generated by client layers; the data flows are inserted into a tunnel that can be treated as a link, without inspecting the individual data packets. Data packets are marked at the originating point (Head) and recognized at the terminating point (Tail), by means of their MPLS Label values; in the intermediate nodes (Transit) the packets are not processed, but only forwarded in transit tunnels. The Outer Tunnel is used also for the MPLS over Ethernet functionality. An example of MPLS over SDH tunnel creation is reported in “Example of MPLS over SDH Tunnelling creation” (p. 1-34). An example of MPLS over Ethernet tunnel creation is reported in “Example of MPLS over Ethernet Tunnelling creation” (p. 1-40). To create an Outer Head MPLS Tunnel, fill fields and areas as follows: •
Index: (read-only, set by the system) numerical index assigned to the resource.
•
Instance: indicating a numerical index of the resource (read-only field).
•
Ingress LSR: indicating an IP address for the incoming side (read-only field).
•
Egress LSR: indicating an IP address for the outgoing side (read-only field).
•
Owner: indicating the entity that created and is responsible for managing this resource
(read-only field). •
Sign. Protocol: (read-only field); indicating, if any, the signaling protocol used to set-
up this tunnel. •
Admin.(istration) Status: possible pull-down options:
–
up: to set the tunnel in-service.
–
down: to set the tunnel out-of-service.
•
Descr.: optional description text assigned by the user to this resource.
•
Client Type: to indicate the upper layer type, possible pull-down options:
•
–
mpls: if transporting MPLS data
–
ethernet: if transporting ethernet data (for MPLS over Ethernet modality)
Role: possible pull-down options:
–
head: (read-only) indicating that this is the originating point of the Tunnel
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 29 0 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
•
Traffic Descr.: indicating the name of the associated MPLS traffic descriptor:
the key permits to choose and associate a traffic descriptor to the data flow, recalling the dialog described in “Configuration -> Traffic Descriptor -> MPLS Traffic Descriptor” (p. 4-67). the key gives the properties of the traffic descriptor currently associated.
WARNING The MPLS rate associated to this resource must be congruent with the CIR/PIR values of the connected ETS resource, with the band indicated in the motherMPLS-port, etc., and in the SDH-Logical Port associated by means of the SDHCraft Terminal application (see “Configuration -> Traffic Descriptor -> MPLS Traffic Descriptor” (p. 4-67) and “MPLS Tunnel: Labelling and Bandwidth Matching” (p. 1-32)). •
OutSegment Management box: parameters of the associated OutSegment resource,
(that will be automatically created and cross-connected under the indicated MPLS Port): MPLS Port: name of the parent MPLS Port (syntax: MPLSPort#port_number):
WARNING The MPLS Port must be active; for MPLS-over-SDH, the chosen MPLS Port should belong to a PPP Port, else, for MPLS-over-Ethernet, the chosen MPLS Port should belong to a Local ETH Port)).
•
the key permits to choose an MPLS Port, recalling the Search dialog described in “Views -> Search” (p. 4-35). The user can set, on the MPLS Port tab of this dialog, some search criteria (such as Status, etc.), to facilitate the search, otherwise the search will be widened on all the existing MPLS Ports; the search is carried out by clicking on the Search key, after which the desired MPLS Port is set by selecting an item in the search result and then clicking on the Apply key of the same search window. the key gives the properties of the MPLS Port currently associated. Label Range: (read-only), range of possible labels
•
Label Selected: to indicate the label number for this tunnel (for details see “MPLS
Tunnel: Labelling and Bandwidth Matching” (p. 1-32)).
WARNING The label assigned here must be equal to the label assigned at the TRANSIT and HEAD points. •
MPLS OutSeg.: (read-only) index number of the OutSegment associated to this tunnel.
After setting all the desired parameters, click on the Ok key to set up the tunnel. The window will be closed without doing any operation by clicking on Cancel key. The Help key gives helps about this function. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 9 1 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Figure 4-189 Create Outer Head Tunnel
Connection -> MPLS Tunnel Management -> Create Outer Transit Tunnel This option is obtained, after selecting the “Main" Tunnel ( contextual pop-up menu; or by selecting, in the menu-bar:
), by means of the
Connection -> MPLS Tunnel Management -> Create Outer Transit Tunnel.
An example of the window displayed is reported in Figure 4-190, (pg. 4-294). The function of this option is to create a Transit tunnel, necessary at the intermediate MPLS nodes of the network, where all the links (Inner Tunnels) contained in this Outer Tunnel are not disassembled but only forwarded. The transit tunnel may be useful in nodes where some outer tunnels are to be terminated or originated and some of them are passedthrough. An example of MPLS over SDH tunnel creation is reported in “Example of MPLS over SDH Tunnelling creation” (p. 1-34). An example of MPLS over Ethernet tunnel creation is reported in “Example of MPLS over Ethernet Tunnelling creation” (p. 1-40). To create an Outer Transit MPLS Tunnel, fill fields and areas as described in “Connection -> MPLS Tunnel Management -> Create Outer Head Tunnel” (p. 4-289). The role of the tunnel is automatically set by the system to transit. Further, the Transit Tunnel window
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 29 2 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
contains, in addition to the OutSegment, also the InSegment; after compilating this window they will be automatically created and cross-connected in order to accomplish the data pass-through: •
InSegment Management box: parameters of the associated InSegment resource:
– MPLS Port: name of the parent MPLS Port (syntax: MPLSPort#port_number). The MPLS Port must be active. –
Label Range: (read-only), range of possible labels
–
Label Selected: to indicate the label number for this tunnel
WARNING The label assigned here must be equal to the label assigned at the TAIL and HEAD points.For details see “MPLS Tunnel: Labelling and Bandwidth Matching” (p. 1-32). –
Policing Mode: to set the policing on the MPLS traffic; possible pull-down
options: –
disabled: no policing is performed
–
color-blind.: it polices by checking only the rate defined in the associated TD.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 9 3 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Figure 4-190 Create Outer Transit Tunnel
Connection -> MPLS Tunnel Management -> Create Outer Tail Tunnel This option is obtained, after selecting the “Main" Tunnel ( contextual pop-up menu; or by selecting, in the menu-bar:
), by means of the
Connection -> MPLS Tunnel Management -> Create Outer Tail Tunnel.
An example of the window displayed is reported in Figure 4-191, (pg. 4-295). The function of this option is to create a Tail tunnel at the terminating MPLS node of the network, where the links (Inner Tunnels) contained in this Outer Tunnel are disassembled. This type of tunnel may also be used to accomplish MPLS over Ethernet links. An example of MPLS over SDH tunnel creation is reported in “Example of MPLS over SDH Tunnelling creation” (p. 1-34). An example of MPLS over Ethernet tunnel creation is reported in “Example of MPLS over Ethernet Tunnelling creation” (p. 1-40). To create an Outer Tail MPLS Tunnel, fill fields and areas as described in “Connection -> MPLS Tunnel Management -> Create Outer Head Tunnel” (p. 4-289). The role of the tunnel is automatically set by the system to tail. The Tail Tunnel window contains, in place of the OutSegment of the head, the: •
InSegment Management box: parameters of the associated InSegment resource, (that
will be automatically created and cross-connected under the indicated MPLS Port): ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 29 4 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
–
MPLS Port: name of the parent MPLS Port (syntax: MPLSPort#port_number).
The MPLS Port must be active. –
Label Range: (read-only), range of possible labels
–
Label Selected: to indicate the label number for this tunnel
WARNING The label assigned here must be equal to the label assigned at the TRANSIT and HEAD points.For details see “MPLS Tunnel: Labelling and Bandwidth Matching” (p. 1-32). –
Policing Mode: to set the policing on the MPLS traffic; possible pull-down
options: –
disabled: no policing is performed
–
color-blind.: it polices by checking only the rate defined in the associated TD.
Figure 4-191
Create Outer Tail Tunnel
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 9 5 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Connection -> Outer MPLS Tunnel -> Create Inner MPLS Tunnel This option is obtained, after selecting an “Outer" Tunnel (Head or Tail), by means of the contextual pop-up menu; or by selecting, in the menu-bar: Connection -> Outer MPLS Tunnel -> Create Inner MPLS Tunnel.
WARNING The involved Outer MPLS Tunnel must have been already created, otherwise this option will not be displayed. An example of the window displayed is reported in Figure 4-192, (pg. 4-299), and in Figure 4-193, (pg. 4-299). The function of this option is to create an Inner Tunnel that can transport data generated by client layers (in this case Ethernet); the data flows (Ethernet InFlow/OutFlow resources) are inserted into this tunnel and then treated as a link, without inspecting the individual data packets. Data packets are marked at the originating point and recognized at the terminating point, by means of their MPLS Label values; in the intermediate nodes the packets are not processed, but only forwarded in transit tunnels. Unlike of Outer Tunnels, Inner Tunnels are not visible in the transit nodes. An example of MPLS over SDH tunnel creation is reported in “Example of MPLS over SDH Tunnelling creation” (p. 1-34). An example of MPLS over Ethernet tunnel creation is reported in “Example of MPLS over Ethernet Tunnelling creation” (p. 1-40). To create an Inner MPLS Tunnel, fill fields and areas as follows: •
Index: (read-only, set by the system) numerical index assigned to the resource.
•
Instance: indicating a numerical index of the resource (read-only field).
•
Ingress LSR: indicating an IP address for the incoming side (read-only field).
•
Egress LSR: indicating an IP address for the outgoing side (read-only field).
•
Owner: indicating the entity that created and is responsible for managing this resource
(read-only field). •
Sign. Protocol: (read-only field); indicating, if any, the signaling protocol used to set-
up this tunnel. •
Admin.(istration) Status: possible pull-down options:
–
up: to set the tunnel in-service.
–
down: to set the tunnel out-of-service.
•
Descr.: optional description text assigned by the user to this resource.
•
Client Type: to indicate the upper layer type, possible pull-down options:
–
ethernet: if transporting ethernet data (set by the system)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 29 6 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
•
•
Role: possible pull-down options:
–
head: (read-only) indicating that this is the originating point of the Tunnel, when the parent Outer Tunnel’s role is Head; (set by the system); see Figure 4-192, (pg. 4-299).
–
tail: (read-only) indicating that this is the terminating point of the Tunnel, when the parent Outer Tunnel’s role is Tail; (set by the system); see Figure 4-193, (pg. 4-299).
Traffic Descr.: indicating the name of the associated MPLS traffic descriptor:
the key permits to choose and associate a traffic descriptor to the data flow, recalling the dialog described in “Configuration -> Traffic Descriptor -> MPLS Traffic Descriptor” (p. 4-67). the key gives the properties of the traffic descriptor currently associated.
WARNING The MPLS rate associated to this resource must be congruent with the CIR/PIR values of the connected ETS resource, with the band indicated in the motherMPLS-port, etc., and in the SDH-Logical Port associated by means of the SDHCraft Terminal application (see “Configuration -> Traffic Descriptor -> MPLS Traffic Descriptor” (p. 4-67) and “MPLS Tunnel: Labelling and Bandwidth Matching” (p. 1-32)). 1. Case of HEAD tunnel, if a parent HEAD Outer Tunnel is selected, (see Figure 4-192, (pg. 4-299)): • OutSegment Management box: parameters of the associated OutSegment resource, (that will be automatically created and cross-connected under the indicated MPLS Port): – MPLS Port: name of the parent MPLS Port (syntax: MPLSPort#port_number); it is automatically set by the system to Virtual MPLS Port, that is created by the system under the “Main" Tunnel. –
Label Range: (read-only), range of possible labels
–
Label Selected: to indicate the label number for this tunnel
WARNING The label assigned here must be equal to the label assigned at the corresponding TAIL point.For details see “MPLS Tunnel: Labelling and Bandwidth Matching” (p. 1-32). –
MPLS OutSeg.: (read-only) index number of the OutSegment associated to this
tunnel. 2. Case of TAIL tunnel, if a parent TAIL Outer Tunnel is selected, (see Figure 4-193, (pg. 4-299)):
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 9 7 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
•
InSegment Management box: parameters of the associated InSegment resource,
(that will be automatically created and cross-connected under the indicated MPLS Port): – MPLS Port: name of the parent MPLS Port (syntax: MPLSPort#port_number); it is automatically set by the system to the same MPLS Port of the parent Outer Tunnel. – Label Range: (read-only), range of possible labels –
Label Selected: to indicate the label number for this tunnel
WARNING The label assigned here must be equal to the label assigned at the corresponding HEAD point.For details see “MPLS Tunnel: Labelling and Bandwidth Matching” (p. 1-32). –
Policing Mode: to set the policing on the MPLS traffic; possible pull-down options: disabled (no policing is performed) or color-blind (it polices by checking only the rate defined in the associated TD).
After setting all the desired parameters, click on the Ok key to set up the tunnel. The window will be closed without doing any operation by clicking on Cancel key. The Help key gives helps about this function.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 29 8 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Figure 4-192
Create Inner (“Head") MPLS Tunnel
Figure 4-193
Create Inner (“Tail") MPLS Tunnel
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 2 9 9 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Connection -> Outer MPLS Tunnel -> Modify Outer MPLS Tunnel This option is obtained, after selecting an Outer MPLS Tunnel, by means of the contextual pop-up menu; or by selecting, in the menu-bar: Connection -> Outer MPLS Tunnel -> Modify Outer MPLS Tunnel.
The function of this option is to modify the parameters set for the selected Outer MPLS Tunnel (anyway only the field Descr. can be changed). All the reported information fields are the same as those explained in “Connection -> MPLS Tunnel Management -> Create Outer Head Tunnel” (p. 4-289). Connection -> Outer MPLS Tunnel -> Outer MPLS Tunnel Properties This option is obtained, after selecting an Outer MPLS Tunnel, by means of the contextual pop-up menu; or by selecting, in the menu-bar: Connection -> Outer MPLS Tunnel -> Outer MPLS Tunnel Properties.
The window displayed (example) is reported in Figure 4-194, (pg. 4-301) (it is relevant to a head tunnel). The function of this option is to show the parameters set for the selected Outer MPLS Tunnel. The reported information fields are read-only; two sectors are displayed: Configuration and Information. The Configuration sector reports the same information as that explained in “Connection > MPLS Tunnel Management -> Create Outer Head Tunnel” (p. 4-289), except for the following extra fields: •
Available Bandwidth: remaining bandwidth that is not yet occupied by “children"
resources (in kb/s) •
XC Pointer: information about the cross-connection accomplished by this tunnel;
further:
•
the key gives the properties of the MPLS XC currently associated, recalling the window described in“Connection -> MPLS InSegment -> MPLS XC Properties” (p. 4-287). the key is not applicable Oper. Status: current operational status of the resource.
The Information sector (it reports other detailed information about the Tunnel): •
Is Interface, Local Protection, Primary Instance, Primary Timeup, Path Changes, Interface, Path In Use, Creation Time, State Transition, Last Path Change.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 30 0 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Figure 4-194
Outer MPLS Tunnel Properties
Connection -> Outer MPLS Tunnel -> Delete Outer MPLS Tunnel This option is obtained, after selecting an Outer MPLS Tunnel, by means of the contextual pop-up menu; or by selecting, in the menu-bar: Connection -> Outer MPLS Tunnel -> Delete Outer MPLS Tunnel.
The window displayed (example) is reported in Figure 4-195, (pg. 4-301). This option permits to delete a selected Outer MPLS Tunnel. The Outer MPLS Tunnel will be deleted, together with its related cross-connections and InSegment/OutSegment resources, after clicking on the Yes key. Figure 4-195
Delete Outer MPLS Tunnel
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 3 0 1 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Connection -> Inner MPLS Tunnel -> Modify Inner MPLS Tunnel This option is obtained, after selecting an Inner MPLS Tunnel, by means of the contextual pop-up menu; or by selecting, in the menu-bar: Connection -> Inner MPLS Tunnel -> Modify Inner MPLS Tunnel.
The function of this option is to modify the parameters set for the selected Inner MPLS Tunnel (anyway only the field Descr. can be changed). All the reported information fields are the same as those explained in “Connection -> Outer MPLS Tunnel -> Create Inner MPLS Tunnel” (p. 4-296). Connection -> Inner MPLS Tunnel -> Inner MPLS Tunnel Properties This option is obtained, after selecting an Inner MPLS Tunnel, by means of the contextual pop-up menu; or by selecting, in the menu-bar: Connection -> Inner MPLS Tunnel -> Inner MPLS Tunnel Properties.
The window displayed (example) is reported in Figure 4-196, (pg. 4-303) (it is relevant to a head tunnel). The function of this option is to show the parameters set for the selected Inner MPLS Tunnel. The reported information fields are read-only; two sectors are displayed: Configuration and Information. The meanings of the reported information fields are the same as the described in “Connection -> Outer MPLS Tunnel -> Outer MPLS Tunnel Properties” (p. 4-300).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 30 2 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Figure 4-196
Inner (“Head”) MPLS Tunnel Properties
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 3 0 3 Issue 05 February 2010
Craft Terminal for ES Management
Connection
............................................................................................................................................................................................................................................................
Connection -> Inner MPLS Tunnel -> Delete Inner MPLS Tunnel This option is obtained, after selecting an Inner MPLS Tunnel, by means of the contextual pop-up menu; or by selecting, in the menu-bar: Connection -> Inner MPLS Tunnel -> Delete Inner MPLS Tunnel.
The window displayed is similar to that reported in Figure 4-195, (pg. 4-301). This option permits to delete a selected Inner MPLS Tunnel. The Inner MPLS Tunnel will be deleted, together with its related cross-connections and InSegment/OutSegment resources, after clicking on the Yes key of the dialog window
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 30 4 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
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 relevant tab of the main view.
WARNING All the dialog windows described in this handbook are reported in “Full Window" mode, the information fields reported in “Windows Presentation: “Full Window" and “Tabbed Window"” (p. 4-34).
WARNING The following paragraphs report the terms green, yellow and red (added as suffix “g”, “y”, “r”; e.g. “TRCFg” is intended as TRCF green marked). 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 MacDestination 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 MacDestination 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”
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 3 0 5 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
Performance -> MPLS Switch -> Granularity 15Minutes/1Hour This option is obtained, after selecting the ES-Switch symbol, by means of the contextual pop-up menu, or by selecting in the menu-bar: Performance -> MPLS Switch Management -> Granularity 15 Minutes
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-316). 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 black bold, 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 black bold, 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 30 6 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
Performance -> Ethernet Port -> Configure ETH. Aggr. 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.
An example of the displayed dialog window is reported in Figure 4-197, (pg. 4-307). The function of this option is to manage the Performance Monitoring (PM) parameters of the selected Ethernet Port (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 Ethernet Port 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 Ethernet Port outgoing 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.
Figure 4-197
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 3 0 7 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
Performance -> Ethernet Port -> ETH Aggr. Properties This option is obtained, after selecting a monitored Ethernet Port, by means of the contextual pop-up menu, or by selecting in the menu-bar: Performance -> Ethernet Port Management -> ETH Aggr Properties.
An example of the displayed dialog window is reported in Figure 4-198, (pg. 4-309). 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 “Performance -> Ethernet Port -> Configure ETH. Aggr.” (p. 4-307). 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 “Performance -> Ethernet Port -> Configure ETH. Aggr.” (p. 4-307).
Outgoing - Information sector:
these fields indicate the current PM collected values – 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
–
TDF: number of Total Discarded ethernet Frames for congestion or policing
–
Start Time: indicating the time when the performance monitoring was started as described in “Performance -> Ethernet Port -> Configure ETH. Aggr.” (p. 4-307).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 30 8 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
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-198
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 Ethernet Port in the tree-area (see example reported in “PM Data Results (History and Maintenance)” (p. 4-316)). 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-319).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 3 0 9 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
Performance -> ETS InFlow -> Configure InFlow This option is obtained, after selecting a connected InFlow, by means of the contextual pop-up menu, or by selecting in the menu-bar: Performance -> ETS InFlow Management -> Configure ETS InFlow
WARNING •
The selected InFlow has to be already cross-connected, otherwise the PM menu is not active.
•
This option is possible only in Bridge Type = bridge 802.1S-AD (Provider) or none as referred in “Transmission -> ISA -> Configure ISA” (p. 4-71).
•
This option is possible only if the InFlow Service Type parameter is Ethernet, see “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111).
An example of the displayed dialog window is reported in Figure 4-199, (pg. 4-310). The function of this option is to manage the Performance Monitoring (PM) parameters of 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)
–
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.
Figure 4-199 InFlow 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 31 0 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
Performance -> ETS InFlow -> InFlow Properties This option is obtained, after selecting a monitored InFlow, by means of the contextual pop-up menu, or by selecting in the menu-bar: Performance -> ETS InFlow Management -> ETS InFlow Properties.
WARNING •
The selected InFlow has to be already cross-connected, otherwise the PM menu is not active.
•
This option is possible only in Bridge Type = bridge 802.1S-AD (Provider) or none as referred in “Transmission -> ISA -> Configure ISA” (p. 4-71).
•
This option is possible only if the InFlow Service Type parameter is Ethernet, see “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111).
An example of the displayed dialog window is reported in Figure 4-200, (pg. 4-312). The function of this option is to show the Performance Monitoring (PM) parameters and the currently collected values for the selected InFlow. All the reported information fields are read-only. It contains the following information fields: •
InFlow Cd - Configuration sector: Note:
•
Cd = Current Data
these parameters are relative to the current monitoring configuration parameters; their meanings are described in “Performance -> ETS InFlow -> Configure InFlow” (p. 4-310). InFlow Cd - Information sector: these fields indicate the current PM collected values (Cd = Current Data) – 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
–
Start Time: indicating the time when the performance monitoring was started, as described in “Performance -> ETS InFlow -> Configure InFlow” (p. 4-310).
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 3 1 1 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
Figure 4-200 InFlow 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 ETS InFlow in the tree-area (see example reported in “PM Data Results (History and Maintenance)” (p. 4-316)). 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-322).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 31 2 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
Performance -> ETS OutFlow -> Configure OutFlow This option is obtained, after selecting a connected OutFlow, by means of the contextual pop-up menu, or by selecting in the menu-bar: Performance -> ETS OutFlow Management -> Configure ETS OutFlow.
WARNING •
The selected OutFlow has to be already cross-connected, otherwise the PM menu is not active.
•
This option is possible only in Bridge Type = bridge 802.1S-AD (Provider) or none as referred in “Transmission -> ISA -> Configure ISA” (p. 4-71).
An example of the displayed dialog window is reported in Figure 4-201, (pg. 4-313). The function of this option is to manage the Performance Monitoring (PM) parameters of 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)
–
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.
Figure 4-201
OutFlow 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 3 1 3 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
Performance -> ETS OutFlow -> OutFlow Properties This option is obtained, after selecting a monitored OutFlow, by means of the contextual pop-up menu, or by selecting in the menu-bar: 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 option is possible only in Bridge Type = bridge 802.1S-AD (Provider) or none as referred in “Transmission -> ISA -> Configure ISA” (p. 4-71)..
An example of the displayed dialog window is reported in Figure 4-202, (pg. 4-315). The function of this option is to show the Performance Monitoring (PM) parameters and the currently collected values for the selected OutFlow. All the reported information fields are read-only. It contains the following information fields: •
OutFlow Cd - Configuration sector: (Cd = Current Data)
•
these parameters are relative to the current monitoring configuration parameters; their meanings are described in “Performance -> ETS OutFlow -> Configure OutFlow” (p. 4-313). 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
–
Start Time: indicating the time when the performance monitoring was started, as described in “Performance -> ETS InFlow -> Configure InFlow” (p. 4-310).
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 31 4 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
Figure 4-202
OutFlow 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 ETS OutFlow in the tree-area (see example reported in “PM Data Results (History and Maintenance)” (p. 4-316)). 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-324).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 3 1 5 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
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 relevant resource in the tree-area; as examples see Figure 4-203, (pg. 4-318) and Figure 4-204, (pg. 4-318). 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: Graphical PM: save an image of the graph, Graphical PM: switch between decimal and exponential format and Graphical PM: 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 “Performance -> MPLS Switch -> Granularity 15Minutes/1Hour” (p. 4-306)). Important!
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 8DG15624AAAA 4 - 31 6 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
•
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 subparagraphs). Note:
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/Graphical Area item, as described in “Configuration -> Options” (p. 4-33). When in Graphical Format, 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 Graphical PM: 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-203, (pg. 4-318) and Figure 4-204, (pg. 4-318)), in tabular form, the same PM parameters that are described in “Ethernet Port PM data tables (History and Maintenance)” (p. 4-319) for the ETH Port, or “ETS InFlow PM data tables - History and Maintenance” (p. 4-322) for the InFlow, or “ETS OutFlow PM data tables - History and Maintenance” (p. 4-324) for the OutFlow.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 3 1 7 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
Figure 4-203 PM data results (Port example)
PM fast key
A2
A3
Figure 4-204 PM data results (InFlow example)
PM Refresh fast key
A2
A3
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 31 8 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
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 “Performance -> MPLS Switch -> Granularity 15Minutes/1Hour” (p. 4-306)). Acronyms used in PM views: CD = Current Data HD = History Data The application table area (A2) contains, for Ethernet Port 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 results of the HISTORY collected monitoring
data relevant to the 1 hour period, for the Incoming /(Outgoing) side of the port. Important! The values reported for HD15m or HD1h are the
difference between the current period and the previous one. The tool tip appearing at the mouse cursor, if passed over one value, shows the absolute value. •
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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 3 1 9 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
•
–
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 (by means of “Performance -> Ethernet Port -> Configure ETH. Aggr.” (p. 4-307)).
–
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:
–
Index: number of monitoring interval
–
Period End Time: time when interval finished
–
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
–
TDF: number of Total Discarded ethernet Frames for congestion or policing
–
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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 32 0 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
–
•
•
•
Start 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-316). CD Tx folder: –
TTF: as above explained
–
TTO: as above explained
–
TTF Unicast: as above explained
–
TTF Multicast: as above explained
–
TTF Broadcast: as above explained
–
TDF: 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-316). 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-316). Maintenance Out. folder: –
TTF: as above explained
–
TTO: as above explained
–
TDF: as above explained
–
TTF Unicast: as above explained
–
TTF Multicast: as above explained
–
TTF Broadcast: as above explained
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 3 2 1 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
– •
Retrieving Time: time of the last PM data refresh dialog panel for PM data sampling (polling): as above explained.
Interface Maintenance folder (only in Local Ports):
–
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 Service Type parameter is Ethernet, see “Transmission -> Ethernet Port -> Create ETS InFlow” (p. 4-111).
•
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 “Performance -> MPLS Switch -> Granularity 15Minutes/1Hour” (p. 4-306)).
Acronyms used in PM views: 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”.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 32 2 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
•
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:
–
Index: number of monitoring interval
–
Period End Time: time when interval finished
–
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
–
TRCOy: number of Total Received Correct ethernet Octets, yellow colored
–
Start Time: indicating the time when the performance monitoring was started (by means of “Performance -> ETS InFlow -> Configure InFlow” (p. 4-310)).
–
Suspect Interval Flag: if this value is “true" it means the measurement data is unreliable, if “false" it means the data is reliable.
•
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
–
Start Time: 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-316). QoS Maintenance folder: –
TRCOg: as above explained
–
TRCFg: as above explained
–
TRCOy: number of Total Received Correct ethernet Octets, yellow colored
–
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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 3 2 3 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
–
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-316). ETS OutFlow 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 “Performance -> MPLS Switch -> Granularity 15Minutes/1Hour” (p. 4-306)). Acronyms used in PM views: CD = Current Data HD = History Data 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:
–
Index: number of monitoring interval
–
Period End Time: time when interval finished
–
TTFg: number of Total Transmitted Correct Frames, green colored
–
TTOg: number of Total Transmitted Correct 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 32 4 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
–
Start Time: indicating the time when the performance monitoring was started (by means of Configure Out Flow. or Data Collection).
–
Suspect Interval Flag: if this value is “true" it means the measurement data is unreliable, if “false" it means the data is reliable.
•
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
–
TDFg: as above explained
–
TDFy: as above explained
–
TTOy: as above explained
–
Start Time: 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-316). •
QoS Maintenance folder:
–
TTOg: as above explained
–
TTFg: as above explained
–
TDFg: number of Total Discarded Frames due to congestion or policing, green colored
–
TTOy: number of Total Transmitted ethernet Octets, yellow colored
–
TTFy: number of Total Transmitted ethernet Frames, yellow colored
–
TDFy: number of Total Discarded Frames due to congestion or policing, yellow colored
–
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-316).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4- 3 2 5 Issue 05 February 2010
Craft Terminal for ES Management
Performance
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 4 - 32 6 Issue 05 February 2010
5
Maintenance
Overview Purpose This chapter describes all the details for periodic checks, faults locations, repair procedures, and restore to normal operations. Contents This chapter provides information on the following topics: •
“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)
Overview The Maintenance general methodology is reported on the equipment-specific Operator Handbooks; refer to them for: equipment troubleshooting and relevant interventions. Only the maintenance issues relevant to hardware and software relative to ISA-ES board are reported.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 5-1 Issue 05 February 2010
Maintenance
General trouble-shooting flow-chart for ISA-ES boards
............................................................................................................................................................................................................................................................
General trouble-shooting flow-chart for ISA-ES boards In case of faults/defects/failures 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 on 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 CONDITION PERSIST ?
NO
TRANSITORY FAILURE
YES
THE ISA-ES BOARD IS FAULTY, REPLACE IT ACCORDING TO THE DESCRIBED PROCEDURE (see on page (5-18))
END
CONNECT THE PC TO THE EQUIPMENT AND, ACCORDING TO THE TYPE OF DETECTED ALARM, PROCEED AS STATED IN on page (5-4)
END
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 5-2 Issue 05 February 2010
Maintenance
Alarms, states and commands on ISA-ES board front cover
............................................................................................................................................................................................................................................................
Alarms, states and commands on ISA-ES board front cover The state of the ISA-ES unit is indicated by a bicolor 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 coverplate are shown on the equipment-specific Technical Handbook, listed in Table 1, (pg. 1-xxiv). On-board Switches: see Table 5-8, (pg. 5-18).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 5-3 Issue 05 February 2010
Maintenance
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 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-8), Table 5-4, (pg. 5-8) and Table 5-5, (pg. 5-9), 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-10). 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-11). The information about alarms can also be observed in the resource-information-area A3 (reporting the same information as the propertyview). 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 syntheses 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-xxiv). In case of unit replacement, follow the indications reported in “ISA-ES Units replacement” (p. 5-18).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 5-4 Issue 05 February 2010
Maintenance
Troubleshooting by means of the ES Craft Terminal
............................................................................................................................................................................................................................................................
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 Synthesis
curr.Appl. Appl. tabs
Domain Alarms Synthesis
A2
A3
A1
message row
Resource Alarms Indications
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 5-5 Issue 05 February 2010
Maintenance
Troubleshooting by means of the ES Craft Terminal
............................................................................................................................................................................................................................................................
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-9). 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 “Configuration -> Alarms Severity (ASAP management)” (p. 4-39) and in “Set Alarms Severities” (p. 4-43). 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:
Example of non-alarmed representation: shape)
(colored and with internal circular shape).
(green and with internal rectangular
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 5-6 Issue 05 February 2010
Maintenance
Troubleshooting by means of the ES Craft Terminal
............................................................................................................................................................................................................................................................
Table 5-1 Alarms colors and Severity association Alarm Color RED ORANGE YELLOW PALE BLUE WHITE GREEN
Severity CRITICAL (CRI) MAJOR (MAJ) MINOR (MIN) WARNING (WNG) INDETERMINATE (IND) NO ALARM
Table 5-2 Colors of the Management States when in “abnormal" condition (alarmed) State SUP: not supervised “key" (LOCAL ACCESS STATE): denied COM: NE unreachable OS: NE managed by the OS MGR: managed by RM ISA Access Card (alarmed)
State Color BROWN CYAN RED CYAN CYAN RED
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 5-7 Issue 05 February 2010
Maintenance
Troubleshooting by means of the ES Craft Terminal
............................................................................................................................................................................................................................................................
Table 5-3 Severity Alarms Synthesis indications Mnemonic CRI
MAJ
MIN
WNG
IND
Alarm/Status Description Critical alarms
Major (Urgent) alarms
Minor (Not urgent) alarms
Warning alarms
Indeterminate alarms
Maintenance 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). Synthesis of alarms that need immediate troubleshooting. Note. Open the AS application: see detailed indications in “Alarms Surveillance (AS)” (p. 5-14). Synthesis of alarms for which a delayed troubleshooting can be defined. Note. Open the AS application: see detailed indications in “Alarms Surveillance (AS)” (p. 5-14). Synthesis of alarms due to failure of other NE in the network. Note. Open the AS application: see detailed indications in“Alarms Surveillance (AS)” (p. 5-14). Synthesis of alarms not associated to the previous severities. Not operative. Open the AS application: see detailed indications in “Alarms Surveillance (AS)” (p. 5-14).
Table 5-4 Domain Alarm Synthesis indication Mnemonic TRNS
Alarm/Status Description Transmission alarms
Maintenance Synthesis of alarms of the Transmission domain. (Indicated as “Communications" Events in the AS application, see “Alarms
Surveillance (AS)” (p. 5-14)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 5-8 Issue 05 February 2010
Maintenance
Troubleshooting by means of the ES Craft Terminal
............................................................................................................................................................................................................................................................
Table 5-5 Management States Control Panel Mnemonic SUPs
Alarm/Status Description Supervision state
Local Access state
COM
Operative System Isolation
OS MGR
NE managed by the OS Upper Management assignment Access Card: FastEthernet or GigaEthernet
Maintenance Indicates whether or not the NE is under supervision. Used in the OS. Indicates whether the Craft Terminal has the OS permission to manage the NE (granted: rectangular shape) or not (denied: circular shape). Identifies the operational state of the connection between NE and Craft Terminal: “disabled" (NE: Unreachable), or“Enabled" (NE: Reachable). The NE is being managed by the OS. Indicates that the NE is supervised by an Upper Manager (BM or RM, etc.). Indicates whether the ISA AccessCard is FastEthernet or GigabitEthernet (see note Note 2 below).
Note 1: Alarms Severity Assignment Profile (ASAP) can modify the assignment of each alarm root to the various synthesis. Note 2:
The actual state information (if FE or GE) of the board is obtained by positioning the mouse over the symbol: the information is reported into the “Message Row" displayed at the bottom of the view.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 5-9 Issue 05 February 2010
Maintenance
Troubleshooting by means of the ES Craft Terminal
............................................................................................................................................................................................................................................................
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).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 5 - 10 Issue 05 February 2010
Maintenance
Troubleshooting by means of the ES Craft Terminal
............................................................................................................................................................................................................................................................
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. Figure 5-4 Example of EthernetPort Properties alarms
Alarms indications
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 5-11 Issue 05 February 2010
Maintenance
Troubleshooting by means of the ES Craft Terminal
............................................................................................................................................................................................................................................................
Figure 5-5
Example of alarms reported in the “resource information area A3"
Resource Alarms Indications
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 5 - 12 Issue 05 February 2010
Maintenance
Troubleshooting by means of the ES Craft Terminal
............................................................................................................................................................................................................................................................
Alarms relevant to ES-Boards observable on SDH-CT The syntheses 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 (unitproblems), ICP (communications-problems), VM (version-mismatch), etc. The details about these alarms and further maintenance interventions are reported in the equipmentspecific OMSN Operator Handbook listed in Table 1, (pg. 1-xxiv).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 5-13 Issue 05 February 2010
Maintenance
Troubleshooting by means of the ES Craft Terminal
............................................................................................................................................................................................................................................................
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 AlarmsSurveillance 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 Sublist in Figure 5-7, (pg. 5-15)). Figure 5-6
AlarmsSurveill.-“Counter Summary" window (“ISA Alarms" example)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 5 - 14 Issue 05 February 2010
Maintenance
Troubleshooting by means of the ES Craft Terminal
............................................................................................................................................................................................................................................................
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". The main information obtained by means of the AS application is shortly described in the following Table 5-5, (pg. 5-9) 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. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 5-15 Issue 05 February 2010
Maintenance
Troubleshooting by means of the ES Craft Terminal
............................................................................................................................................................................................................................................................
Table 5-6 Alarms Surveillance information general description Title • Perceived Severity • •
Event date and time Friendly Name
•
Event Type
•
Probable Cause
•
Reservation Status
•
Clearing status
•
Acknowledge status
• •
Correlated notification flag Repetition counter
Description The severity assigned to the alarm is indicated, with the relevant color, i.e.: MAJOR, MINOR, WARNING.... Indicates year, month, day and hour of the alarm. Identifies the rack, subrack, board, port, and TP in which the alarm is detected, e.g.: / r01sr1sl01/#port01-E1S Indicates the family type of the alarm as subdivided in the ASAP list, i.e.: COMMUNICATIONS, etc. The fault/problem is indicated, i.e.: loss of signal, transmitter degraded, replaceable unit missing, resource isolation, ... Indicates if the alarm is reserved (RSV) or not (NRSV) according to security management. Indicates if the alarm condition is terminated (CLR) or is still active (NCLR). If cleared it has a green background, Indicates if the alarm has been acknowledged (ACK), with the “Attend" button on the COMPACT ADM unit, or not (NACK). Not used Not used
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 5 - 16 Issue 05 February 2010
Maintenance
Troubleshooting by means of the ES Craft Terminal
............................................................................................................................................................................................................................................................
Table 5-7 “Probable Cause" of alarms and relevant maintenance actions Probable cause Name and/or Acronym of Displayed Alarm
LOS (Loss Of Signal)
Maintenance Problems on receive path or on remote transmitter.
LOF (Loss Of Frame GFP)
Check the ISA-ES continuity connections on RX path and remote transmitter. Problems on receive path or on remote transmitter.
TSF (Trail Signal Fail)
Check the RX path (ports, cross-connections, etc.) and remote transmitter. Problems on receive line.
PLM (PayLoad Mismatch)
GTM (GFP Type Mismatch)
DACM (Dual Attachment Connectivity Message) DEG (SDH Concatenation Degrade) CSF (Client Signal Fail)
Check the integrity of RX line and relevant connections. Problems on far-end or near-end i/f configuration. The payload type (as indicated by the VC-SignalLabel byte) is not congruent with the expected one. Check the far-end and near-end EthernetPort configuration. Problems on far-end or near-end i/f configuration. The GFP frame (as indicated by the GFP-Type byte) is not congruent with the expected one. Check the far-end and near-end EthernetPort configuration. Problems on Dual Attach protection configuration. Check the correctness and integrity of Dual Attach protection configuration. Problems on SDH network receive line (failure on one or more concatenated SDH paths). Check the integrity of RX line and relevant connections. Remote Port: problems on far-end ethernet i/f, or on network path (if CSF is bidirectional).
LAGD (Lag Degrade)
Check the far-end Ethernet port signal, or the network path. Almost 1 member of the LAG is out-of-service.
LAGL (Lag Loss)
Check the alarm status of the port that are involved in the LAG. All the members of the LAG are out-of-service.
TD (Traffic Disabled)
Check the alarm status of the port that are involved in the LAG. Manual command for maintenance purpose which set in down the in/out traffic for a port. Since is a maintenance procedure it doesn’t require further check.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 5-17 Issue 05 February 2010
Maintenance
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 “MIBRESET”) 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, listed in Table 1, (pg. 1-xxiv)), in order to execute some special operations, as described in the following table: Table 5-8 DIP-SWITCHES operations DIP-SWITCH I1-1 OFF OFF ON ON
DIP-SWITCH I1-1 OFF ON OFF ON
Function Normal MIB RESET (Flash-ROM format) Reserved Reserved
The other switches on ISA-ES16 board (I2-1,2 and I4-1,2,3,4) are for factory use only. 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 5 - 18 Issue 05 February 2010
Maintenance
Software Upgrading/Downgrading
............................................................................................................................................................................................................................................................
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-26)) and a download operation (see “NE-ES software downloading” (p. 3-34)) are necessary.
WARNING In case of software installation, refer to “ES-CT Installation procedure” (p. 3-8).
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 5-19 Issue 05 February 2010
Maintenance
Software Upgrading/Downgrading
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA 5 - 20 Issue 05 February 2010
A
Technical support
Overview Purpose This chapter provides important technical assistance information for the Alcatel-Lucent ISA Board ES16 (Alcatel-Lucent ISA ES16). 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 8DG15624AAAA A-1 Issue 05 February 2010
Technical support
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 ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA A-2 Issue 05 February 2010
Technical support
Technical assistance
............................................................................................................................................................................................................................................................
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)
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA A-3 Issue 05 February 2010
Technical support
Technical assistance
............................................................................................................................................................................................................................................................
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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA A-4 Issue 05 February 2010
Technical support
Technical assistance
............................................................................................................................................................................................................................................................
•
–
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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA A-5 Issue 05 February 2010
Technical support
Technical assistance
............................................................................................................................................................................................................................................................
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) Note:
This may not apply to all products.
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. check the warranty status before submitting a request.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA A-6 Issue 05 February 2010
Technical support
Accessing and navigating the On-Line Customer Support (OLCS) web site
............................................................................................................................................................................................................................................................
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA A-7 Issue 05 February 2010
Technical support
Accessing and navigating the On-Line Customer Support (OLCS) web site
............................................................................................................................................................................................................................................................
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:
[email protected] 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.alcatellucent.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 ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA A-8 Issue 05 February 2010
Technical support
Accessing and navigating the On-Line Customer Support (OLCS) web site
............................................................................................................................................................................................................................................................
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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA A-9 Issue 05 February 2010
Technical support
Accessing and navigating the On-Line Customer Support (OLCS) web site
............................................................................................................................................................................................................................................................
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 Note:
This may not apply to all products.
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.” ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA A - 10 Issue 05 February 2010
Technical support
Accessing and navigating the On-Line Customer Support (OLCS) web site
............................................................................................................................................................................................................................................................
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) Note:
This may not apply to all products.
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. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA A-11 Issue 05 February 2010
Technical support
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. ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA A - 12 Issue 05 February 2010
Technical support
Other technical support services
............................................................................................................................................................................................................................................................
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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA A-13 Issue 05 February 2010
Technical support
Other technical support services
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA A - 14 Issue 05 February 2010
Glossary Acronyms and Abbreviations ............................................................................................................................................................................................................................................................
A 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 ............................................................................................................................................................................................................................................................
B BE
Best Effort BGP
Border Gateway Protocol BM
Bandwidth Manager BPDU
Bridge Protocol Data Unit ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-1 Issue 05 February 2010
Glossary
Acronyms and Abbreviations
............................................................................................................................................................................................................................................................
BW
BandWidth ............................................................................................................................................................................................................................................................
C 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-2 Issue 05 February 2010
Glossary
Acronyms and Abbreviations
............................................................................................................................................................................................................................................................
CRC
Cyclic Redundancy Check CSF
Client Signal Failure CT
Craft Terminal ............................................................................................................................................................................................................................................................
D 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-3 Issue 05 February 2010
Glossary
Acronyms and Abbreviations
............................................................................................................................................................................................................................................................
DS
Differentiated Service DSCP
Differentiated Services Code Point DSNE
Directory Services Network Element DSX
Digital Cross-Connect Panel DTE
Data Terminating Equipment ............................................................................................................................................................................................................................................................
E 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-4 Issue 05 February 2010
Glossary
Acronyms and Abbreviations
............................................................................................................................................................................................................................................................
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) ............................................................................................................................................................................................................................................................
F FCC
Federal Communications Commission FCS
Frame Check Sequence FD
Full Duplex FDDI
Fiber Distribution Data Interface FDL
Facility Data Link
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-5 Issue 05 February 2010
Glossary
Acronyms and Abbreviations
............................................................................................................................................................................................................................................................
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 ............................................................................................................................................................................................................................................................
G GE
Gigabit Ethernet GDA
Group Destination Address GFP
Generic Frame Procedure GNE
Gateway Network Element GRE
Generic Routing Encapsulation GTP
General Telemetry Processor GTSIP
Global Technical Support Information Platform GUI
Graphical User Interface ............................................................................................................................................................................................................................................................
H HD
History Data or Half Duplex HEC
Header Error Control
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-6 Issue 05 February 2010
Glossary
Acronyms and Abbreviations
............................................................................................................................................................................................................................................................ ............................................................................................................................................................................................................................................................
I 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-7 Issue 05 February 2010
Glossary
Acronyms and Abbreviations
............................................................................................................................................................................................................................................................ ............................................................................................................................................................................................................................................................
J JRE
Java Running Environment ............................................................................................................................................................................................................................................................
L 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-8 Issue 05 February 2010
Glossary
Acronyms and Abbreviations
............................................................................................................................................................................................................................................................
LOS
Loss of Signal LS
Low Speed LSR
Label Switching Router LT
Link Trace ............................................................................................................................................................................................................................................................
M 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-9 Issue 05 February 2010
Glossary
Acronyms and Abbreviations
............................................................................................................................................................................................................................................................
MSTP
Multiple Spanning Tree Protocol MTU
Maximum Transmission Unit MUX
Multiplex ............................................................................................................................................................................................................................................................
N NE
Near End NE
Network Element NNI
Network to Network Interface NARTAC
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 ............................................................................................................................................................................................................................................................
O 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 ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-10 Issue 05 February 2010
Glossary
Acronyms and Abbreviations
............................................................................................................................................................................................................................................................
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 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-11 Issue 05 February 2010
Glossary
Acronyms and Abbreviations
............................................................................................................................................................................................................................................................
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 ............................................................................................................................................................................................................................................................
Q QoS
Quality of Service ............................................................................................................................................................................................................................................................
R RAM
Random Access Memory RARP
Reverse Address Resolution Protocol RDI
Remote Defect Indication RST
Rapid Spanning Tree RSTP
Rapid Spanning Tree Protocol ............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-12 Issue 05 February 2010
Glossary
Acronyms and Abbreviations
............................................................................................................................................................................................................................................................
RSVP-TE
Resource ReserVation Protocol – Traffic Engineering RS232
Serial interface ............................................................................................................................................................................................................................................................
S 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-13 Issue 05 February 2010
Glossary
Acronyms and Abbreviations
............................................................................................................................................................................................................................................................ ............................................................................................................................................................................................................................................................
T 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-14 Issue 05 February 2010
Glossary
Acronyms and Abbreviations
............................................................................................................................................................................................................................................................ ............................................................................................................................................................................................................................................................
U 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
............................................................................................................................................................................................................................................................
V 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
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-15 Issue 05 February 2010
Glossary
Acronyms and Abbreviations
............................................................................................................................................................................................................................................................ ............................................................................................................................................................................................................................................................
W WDRR
Weighted Deficit Round Robin WFQ
Weighted Fair Queue WRED
Weighted Random Early Discard
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-16 Issue 05 February 2010
Glossary
Terms and Definitions
............................................................................................................................................................................................................................................................
Terms and Definitions ............................................................................................................................................................................................................................................................
A 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. ............................................................................................................................................................................................................................................................
B BER - Bit Error Ratio
The ratio of bits received in error to the total bits sent. ............................................................................................................................................................................................................................................................
C 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. ............................................................................................................................................................................................................................................................
D 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. Demultiplexing
A process applied to a multiplexed signal for recovering signals combined within it and for restoring the distinct individual channels of these signals.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-17 Issue 05 February 2010
Glossary
Terms and Definitions
............................................................................................................................................................................................................................................................
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. ............................................................................................................................................................................................................................................................
E 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 representing an Ethernet connection between remote MAC address. Ethernet traffic is tagged with 802.1p VLAN and is classified with 8 Ethernet priority values. ............................................................................................................................................................................................................................................................
F 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-18 Issue 05 February 2010
Glossary
Terms and Definitions
............................................................................................................................................................................................................................................................ ............................................................................................................................................................................................................................................................
G GNE - Gateway Network Element
A network element that has an active X.25 link. ............................................................................................................................................................................................................................................................
I ID
See shelf ID and site ID. InSegment
It represents an incoming segment in a LSR. ............................................................................................................................................................................................................................................................
J 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. ............................................................................................................................................................................................................................................................
L 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-19 Issue 05 February 2010
Glossary
Terms and Definitions
............................................................................................................................................................................................................................................................
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. ............................................................................................................................................................................................................................................................
M 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. ............................................................................................................................................................................................................................................................
N 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-20 Issue 05 February 2010
Glossary
Terms and Definitions
............................................................................................................................................................................................................................................................
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. ............................................................................................................................................................................................................................................................
O 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. ............................................................................................................................................................................................................................................................
P 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-21 Issue 05 February 2010
Glossary
Terms and Definitions
............................................................................................................................................................................................................................................................ ............................................................................................................................................................................................................................................................
R 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. RT - Remote Terminal
An unstaffed equipment enclosure that may have a controlled or uncontrolled environment. ............................................................................................................................................................................................................................................................
S 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. ............................................................................................................................................................................................................................................................
U 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 nonSES 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.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-22 Issue 05 February 2010
Glossary
Terms and Definitions
............................................................................................................................................................................................................................................................ ............................................................................................................................................................................................................................................................
X XC
It represents a cross-connection, which is used to associate in and out segments toghether, in order to form a cross-connection.
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-23 Issue 05 February 2010
Glossary
Terms and Definitions
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA GL-24 Issue 05 February 2010
Index .............................................................................
.............................................................................
B
P
BPDU Selective Tunnelling, 1-87
product take-back, xxvi
.............................................................................
C
D
Provider Bridge, 1-4
conventions used, xxiii
.............................................................................
document conventions used, xxiii how to use, xxii
.............................................................................
R
.............................................................................
E
recycle, xxvi
.............................................................................
T
intended audience, xxi dual-homing, 1-88, 1-91
product disposal, xxvi
TAIL, 1-33 TRANSIT, 1-33
.............................................................................
V
Virtual Bridge, 1-3
Electrostatic Discharge (ESD), xxiii EPS 1+1, 1-90 Ethernet Bridge, 1-3 Ethernet OAM, 1-93
.............................................................................
H
HEAD, 1-33
.............................................................................
I
intended audience, xxi
.............................................................................
M
MAC-Bridge, 1-3 Maintenance Entity, 1-94 Maintenance Entity Group, 1-94 MEF, 1-20 MEG End Point, 1-94 MEG Intermediate Point, 1-94 MPLS, 1-8 MPLS technique, 1-8 MPLS Tunnelling, 1-32
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA IN-1 Issue 05 February 2010
Index ............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................ P/N 8DG15624AAAA IN-2 Issue 05 February 2010
