Watson SHDSL EFM Plug-in Operating Manual

Transcription

Watson SHDSL EFM Plug-in
Operating Manual
Document Identification
Watson-EFM-Plugin-Manual.docx
Document Version
6.0-00
Document Revision
2014-01-20
Distribution
Customer
Operating Manual
Version 6.0-00
Revision History
Revision
Date
Author Remarks
6.0-00
140120 MHe
Update for FW 3.01.01
5.0-00
130705 MHe
4.0-00
121211 MHe
3.0-00
120625 MHe
2.0-00
111202 MHe
Add CLI
1.0-00
110915 MHe
First edition
Copyright 2014 by Schmid Telecom AG, Zurich, Switzerland. All rights reserved. Reproduction of part or all of the
contents in any form is expressly prohibited without the prior written consent of Schmid Telecom AG.
Schmid Telecom has used its discretion, best judgments and efforts in preparing this document. Schmid Telecom
hereby disclaims any liability to any person for any kind of damage. Schmid Telecom may make improvements of this
document at any time.
ii
Revision: 2014-01-20
Declaration of Conformity
Plug-in
Watson EFM Plug-in, 4 x Ethernet, 4 x DSL
SZ.868.V654
Watson EFM Plug-in, 4 x Ethernet, 8 x DSL
SZ.868.V854
Watson EFM Regenerator
SZ.856.V320
Manufacturer:
Schmid Telecom AG, Binzstrasse 35, CH-8045 Zurich
The products mentioned above comply with the regulations of the following European Directives:
2004/108/EC
Directive containing requirements regarding
electromagnetic compatibility.
2006/95/EC
safety.
1999/5/EC
Radio & Telecommunication Terminal
Equipment.
2002/96/CE
the prevention of waste electrical and electronic equipment (WEEE), and in addition,
the reuse, recycling and other forms of recovery of such wastes so as to reduce the
The compliance of the above mentioned product with the requirements of the directive 2004/108/EC is ensured by complete application of the following harmonized European
Standards:
EN 300386:2010
The compliance of the above mentioned product with the requirements of the directive 2006/95/EC is ensured by complete application of the following harmonized European
Standards:
EN 60950:2006 (IEC 60950:2005)
The compliance of the above mentioned product with the requirements of the directive 1999/5/EC is ensured by complete
application of the following harmonized European Standards:
EN 55022:2006, EN 55024:1998
EN 60950:2006 (IEC 60950:2005)
Warning: This is a Class A product. In a domestic environment this product may cause radio interference in which case
the user may be required to take adequate measures.
The product mentioned above is labeled in accordance with
European Directive 2002/96/EC concerning waste electrical
and electronic equipment (WEEE). The Directive determines
the framework for the return and recycling of used appliances
as applicable throughout the European Union. This label is
Operating Manual
disposal of waste.
2002/95/CE
Directive containing requirements to approximate the laws of the Member States on the
restrictions of the use of hazardous substances (RoHS) in electrical and electronic
equipment and to contribute to the protection
of human health and the environmentally
sound recovery and disposal of waste electrical and electronic equipment.
Version 6.0-00
applied to the product to indicate that the product is not to be
thrown away, but rather reclaimed upon end of life per this
Directive.
The product mentioned above has been designed and produced following the Directive 2002/95/EC of the European
Parliament and of the Council of 27 January 2003 on the restriction of the use of certain hazardous substances in electrical and electronic equipment and is compliant to the allowed
concentration values defined by the European Committee.
The compliance of the above mentioned products with the specified requirements of the applicable directives
and harmonized and non-harmonized standards is shown in the following internal and external test reports:
 Watson_SHDSL_EFM_plugin_EMC_report_pre_series_III.doc
 20111116.A01.01_EFM_Plug-in_868.914_Schmid.pdf
 Watson_SHDSL_EFM_Plug-in_Safety-test-Report_20110913.pdf
CE Label attached to the product(s):
on tabletop housing, on 19’’ minirack and on 19” subrack
Issued by:
Schmid Telecom AG
Binzstrasse 35
CH-8045 Zurich
Place and date:
Zurich, 2013-06-13
Signature:
Signature
Peter Schmid CEO
iv
Important Safety Precautions
To reduce the risk of fire, bodily injury, and damage to the equipment the following precautions must be observed:
 Read and follow all warning notices and instructions marked on the product or
included in the manual.
 Installation of this equipment has to be done by qualified personnel only.
 To achieve safety and satisfactory EMC performance, the plug-in boards
have to be inserted into appropriate subracks. Subrack slots that are not used
must covered with a blanking plate.
 The subracks must be connected to earth. This is achieved by installing the
subracks into properly grounded rack or by connecting the protective ground
terminal provided on some subracks to the earthing network.
 If the subracks are installed in racks then these racks must be connected to
the earthing network according to ETS 300 253.
 Where protective ground terminals are available on the subracks these terminals are marked with the symbol
. The following rules must be observed:
The earthing network must be connected to the protective ground terminal
continuously and securely.
Where the subracks are fitted with an AC power connector the earthing
network must be connected securely to the protective ground terminal
even if the AC power cord is disconnected from the subracks.
The protective grounding may only be disconnected from the subracks after the DSL line has been disconnected from the plug-in.
 This product is to be used with telecommunications circuits. Take the following precautions:
Never install telephone wiring during a lightning storm.
Never install telephone jacks in wet locations unless the jack is specifically designed for wet locations.
Never touch uninsulated telephone wires or terminals unless the telephone line has been disconnected at the network interface.
Use caution when installing or modifying telephone lines.
Avoid using a telephone (other than a cordless type) during an electrical
storm. There may be a remote risk of electric shock from lightning.
Do not use the telephone to report a gas leak in the vicinity of the leak.
 Condensation may occur externally or internally if this product is moved from
a colder room to a warmer room. When moving this product under such conditions, allow ample time for this product to reach room temperature and to
dry before operating.
 This product is intended for use in environments as stated in the technical
specifications. Do not use this product in areas classified as hazardous locations. Such areas include patient care areas of medical and dental facilities,
oxygen-laden environments, or industrial facilities. Contact your local electrical authority governing building construction, maintenance, or safety for more
information regarding the installation of this product.
Operating Manual
Version 6.0-00
Slots and openings in this product are provided for ventilation and should
never be blocked or covered, since these ensure reliable operation of this
product and protect it from overheating. This product should not be placed in
a built-in apparatus such as a rack unless the apparatus has been specifically
designed to accommodate the product, proper ventilation is provided for the
product, and the product instructions have been followed.
 This product should be placed away from radiators, heat registers, stoves, or
other pieces of equipment that produce heat. Allow sufficient air circulation
around the product and the AC adapter during use to ensure adequate cooling of the device.
 Do not use this product in a wet location.
 Normal operation of this product is only possible when the external housing is
left in place.
 This product should be operated only from the type of power source indicated
on the product's electrical ratings label. If you have questions about the type
of power source to use, contact your local Schmid Distributor or local power
company.
 Be sure that the power outlet you plug the power cord into is easily accessible
and located as close to the equipment operator as possible. When you need
to disconnect power to this product, be sure to unplug the power cord from
the electrical outlet.
 Ensure that the voltage select switch, if provided on this product, is in the correct position for the type of voltage in your country (115 VAC or 230 VAC).
 Do not allow anything to rest on any of the attached cables and do not position this product where persons will walk or trip on the cables.
 Unplug this product from the wall outlet before cleaning. Do not use liquid
cleaners or aerosol cleaners. Use a damp cloth for cleaning.
 Never push a foreign object through an opening in this product.
 Unplug the product from the electrical outlet and contact your local Schmid
Distributor under the following conditions:
The power cord, extension cord, or plug is damaged.
Liquid has been spilled or an object has fallen into this product.
This product has been exposed to water.
This product has been dropped or damaged in any way.
There are noticeable signs of overheating.
This product does not operate normally when you follow the operating instructions.
 In order to prevent accidental injury to personnel, do not leave unused SFP
ports uncovered. When transceivers are not installed, end caps must be
used.
The metal edges of the SFP port are SHARP. To avoid injury, ALWAYS keep
the SFP port covered. If SFP module is not loaded be cautious to avoid injury.
 Do not attempt to service this product yourself, as opening or removing covers may expose you to dangerous high voltage points or other risks. Refer
all servicing to your local Schmid Distributor.
Upon completion of any service or repairs to this product, have your local Schmid
Distributor perform any safety checks required by the repair procedure or by
local codes to determine that the product is in proper operating condition.

vi
Limited Product Warranty
Schmid Telecom warrants that for two (2) years from the date of shipment to the
Customer, all products manufactured by Schmid Telecom will be free from defects in materials and workmanship. Schmid Telecom also warrants that products
will conform to the applicable specification and drawings for such products, as
contained in the Product Manual on in Schmid Telecom internal specifications
and drawings for such products (which may or may not be reflected in the Product Manual). This warranty only applies if Customer gives Schmid Telecom written notice of defects during the warranty period. Upon such notice, Schmid Telecom will, at its option, either repair or replace the defective item.
If Schmid Telecom is unable, in a reasonable time, to repair or replace any
equipment to a condition as warranted, Customers is entitled to a full refund of
the purchase price upon return of the equipment to Schmid Telecom. This warranty applies only to the original purchaser and is not transferable without Schmid
Telecom express written permission. This warranty becomes null and void if Customer modifies or alters the equipment in any way, other than as specifically authorized by Schmid Telecom.
Except for the limited warranty described above, the foregoing constitutes the
sole and exclusive remedy of the Customer and the exclusive liability of Schmid
Telecom and is in Lieu of any and all other warranties (expressed or implied).
Schmid Telecom specifically disclaims all other warranties, including (without limitation), all warranties of merchantability and fitness for a particular purpose.
Some states do not allow the exclusion of implied warranties, so this exclusion
may not apply to Customer.
In no event will Schmid Telecom or its suppliers be liable to Customer for any incidental, special, punitive, exemplary or consequential damages experienced by
either Customer or a third party (including, but not limited to, loss of data or information, loss of profits, or loss of use). Schmid Telecom is not liable for damages for any cause whatsoever (whether based in contract, tort, or otherwise) in excess of the amount paid for the item. Some states do not allow the limitation or
exclusion of liability for incidental or consequential damages, so the above limitation or exclusion may not apply to Customer.
vii
Waste Heat Management
The Watson Subrack supports energy efficient passive cooling albeit with some
practical limitations that arise from the significant heat output within a finite enclosure.
The System Integrator must void space above and below the sub-rack to allow a
well loaded system to be convection cooled using only the natural chimney effect.
Exhaust air (top) is up to thirty degrees above ambient and is not suitable for
cooling other equipment placed higher in the rack.
Peak exhaust temperature under extreme environmental conditions may exceed
the temperature ratings of system cable unless the inlet air is compliant with the
relevant climatogram. Route cables using the cable tray provided at the bottom of
the rack.
Take care that inlet (bottom) air is not pre-heated by equipment mounted below
the sub-rack.
Cabinet level forced-air flow is recommended when rack space is limited or when
other heat generating appliances must exist above or below the sub-rack.
Waste heat disposal requires a relatively low mass-flow of air though a cabinet
which can be generated silently with large diameter fans (6 or 8 inch in commodity fan trays) or building services. "Near passive" cooling gives high tolerance of
fan and air filter maintenance events. Clean air is required; fluff or dust will degrade cooling effectiveness.
Fan cooling may be conditional and will extend the temperature ceiling by up to
twenty centigrade beyond passive cooling. Fan switching may be controlled by
time-switch in noise or energy sensitive applications that are affected by day-time
solar heat loading.
It is recommended to populate alternate slots (only) if regenerators are used in a
passive cooling regime. Eighteen scenarios are defined in the table below. Yellow
indicates a limiting scenario where the environmental specifications are reached
only under ideal passive cooling scenarios. Red fields always require assisted
airflow.
SZ.868.V654Wxx
SZ.868.V854Wxx
Watson SHDSL
Watson SHDSL
EFM Plug-in 4xDSL EFM Plug-in 8xDSL
4xEth
4xEth
Operational Environment Class 3.1
# of Eth
4
4
4
4
4
4
Ideal passive cooling scenario
# of DSL
4
4
4
8
8
8
Limiting values give 30C temperature rise
regenerator stages
0
1
2
0
1
2
# of
heat
heat heat heat heat heat heat
plug-ins
limit (W)
(W)
(W)
(W)
(W) (W)
(W)
19" Subrack for WATSON DSL
SZ.379.V4Fx plug-ins + 1 ACU/CMU/SCU
6
146
82
94
106
98
122
146
12
196
164
188
212
196
244
292
plug-ins + 1 ACU/CMU/SCU
SZ.379.V4Fx 3x1 FAN-tray above rack
12
292
164
188
212
196
244
292
Table 1-1: 19” Subrack waste heat management
ix
Operating Manual
Version 6.0-00
Example 1:
 Watson Subrack equipped with 12 SZ.868.V854 EFM Plug-in cards, one
SCU and no RPU’s:
o 196W max power dissipation
o Passive cooling regime might be appropriate
Example 2:
 Watson Subrack equipped with 6 SZ.868.V854 EFM Plug-in cards and
one SCU populated in alternate slots. Each EFM Plug-in card is equipped
with two SZ.868.090V1x Remote Power Units (RPU) module each DSL
line is feeding one regenerator with remote power :
Example 3:
 Watson Subrack equipped with 6 SZ.868.V854 EFM Plug-in cards and
one SCU populated in alternate slots. Each EFM Plug-in card is equipped
with two SZ.868.090V1x Remote Power Units (RPU) modules and each
line is feeding 2x 4 regenerators (2 regenerator stages) with remote power :
INPUT CURRENT LIMITATION
The total sub-rack consumption shall be limited to 10A input current (at typically
50V) to ensure that fuses are de-rated and will not blow at low battery voltage.
Current can also be verified by measurement and will generally be lower than indicated which may make the marginal scenario (yellow) fully acceptable.
There are no power limitations when both battery inputs are bonded together.
SZ.868.V654Wxx
SZ.868.V854Wxx
Watson SHDSL
Watson SHDSL
EFM Plug-in 4xDSL EFM Plug-in 8xDSL
4xEth
4xEth
Operational Environment Class 3.1
Ideal passive cooling scenario
Limiting values maintain fuse de-rating
# of Eth
4
4
4
4
4
4
# of DSL
4
4
4
8
8
8
regenerator stages
0
1
2
0
1
2
# of
power
power power power power power power
plug-ins
limit (W)
(W)
(W)
(W)
(W)
(W)
(W)
plug-ins + 1 ACU/CMU/SCU
SZ.379.V4Fx Parallel battery input
6
501
82
166
250
98
266
434
12
501
164
332
500
196
532
868
12
1002
164
332
500
196
532
868
Table 1-2: 19” Subrack power management
Some legacy sub-racks have 10A fuses (rather than 16A) so proportionally lower
values will apply.
Systems using only switched-mode power supplies fed from AC power (without
battery back-up) do not encounter low battery conditions and require less derating that battery backup power systems.
Only configurations with both battery inputs bonded together can approach the
theoretical maximum consumption. Not all the input power is dissipated locally.
x
Table of Contents
1
Related Documents ......................................................................................................................... 1-1
2
Overview ........................................................................................................................................... 2-1
2.1 Introduction .............................................................................................................................. 2-1
2.2 Applications ............................................................................................................................. 2-2
3
Watson SHDSL EFM Plug-in Features ........................................................................................... 3-1
3.1 DSL .......................................................................................................................................... 3-1
3.1.1 Linerates and DSL sync rates...................................................................................... 3-1
3.1.2 Multi-pair operation ...................................................................................................... 3-2
3.1.3 Power Backoff .............................................................................................................. 3-2
3.1.4 Wetting Current ............................................................................................................ 3-3
3.1.5 Master (STU-C) / Slave (STU-R) ................................................................................. 3-4
3.1.6 DSL Clocking ............................................................................................................... 3-4
3.2 Ethernet ................................................................................................................................... 3-5
3.2.1 Ethernet over DSL ....................................................................................................... 3-5
3.2.2 Ethernet Switching ....................................................................................................... 3-6
3.2.1 VLANs and bridge modes ............................................................................................ 3-6
3.2.1.1 Customer Bridge Mode ................................................................................................ 3-6
3.2.1.2 Provider Bridge Mode (PB) (S-VLAN mode) ............................................................... 3-7
3.2.1.3 Transparent bridge mode ............................................................................................ 3-9
3.2.2 VLAN Examples ........................................................................................................... 3-9
3.2.3 Quality of Service (QoS) ............................................................................................ 3-11
3.2.4 Layer 2 Control Protocol Handling ............................................................................. 3-13
3.2.5 Ethernet Trunking (LAG) ............................................................................................ 3-13
3.2.6 Spanning Tree Protocol ............................................................................................. 3-14
3.2.7 Link OAM ................................................................................................................... 3-17
3.2.8 Service OAM .............................................................................................................. 3-17
3.2.9 Ethernet Clocking ...................................................................................................... 3-20
3.3 Management .......................................................................................................................... 3-20
3.3.1 SNMP......................................................................................................................... 3-20
3.3.1.1 SNMP Traps .............................................................................................................. 3-20
3.3.2 Command Line Interface (CLI) .................................................................................. 3-20
3.3.2.1 SSH - Secure remote communication ....................................................................... 3-21
3.3.2.2 Built-in SNMP tools .................................................................................................... 3-21
3.3.3 Web-Interface ............................................................................................................ 3-21
3.3.4 Management Access ................................................................................................. 3-21
3.4 Firmware Update ................................................................................................................... 3-21
3.5 Performance Monitoring / Statistics ....................................................................................... 3-22
3.5.1 DSL Parameters ........................................................................................................ 3-22
3.5.2 G.826 like Statistics ................................................................................................... 3-22
3.5.3 Interface Statistics ..................................................................................................... 3-23
3.5.4 RMON Statistics ........................................................................................................ 3-23
3.5.5 Packet Counters (QoS Statistics) .............................................................................. 3-23
3.5.6 DSL Performance Supervision function ..................................................................... 3-24
3.6 Service Activation Test .......................................................................................................... 3-24
xi
Operating Manual
Version 6.0-00
4
Watson EFM Regenerator ............................................................................................................. 4-25
4.1 Operating modes ................................................................................................................... 4-25
4.2 Interface Designation ............................................................................................................. 4-25
4.3 Cascading .............................................................................................................................. 4-25
4.4 Bonding Protocols ................................................................................................................. 4-26
4.5 Powering ................................................................................................................................ 4-26
4.5.1 Remote powering ....................................................................................................... 4-26
4.5.1.1 Remote powering and BACP protocol ....................................................................... 4-27
4.5.1.2 Remote powering and G.hs protocol ......................................................................... 4-27
4.5.2 Local powering ........................................................................................................... 4-28
5
Powering ........................................................................................................................................... 5-1
6
LEDs and Alarms ............................................................................................................................. 6-1
6.1 LEDs ........................................................................................................................................ 6-1
6.1.1 LED Indications ............................................................................................................ 6-1
6.2 Alarm Conditions ..................................................................................................................... 6-2
6.3 Alarm Relays ........................................................................................................................... 6-2
6.4 SNMP Traps ............................................................................................................................ 6-2
7
EFM Plug-in Management Overview .............................................................................................. 7-3
7.1 Introduction .............................................................................................................................. 7-3
7.2 Serial Line Connection Mode .................................................................................................. 7-3
7.3 Watson EFM Plug-in in Subrack with SCU ............................................................................. 7-4
7.3.1 Addressing of Plug-ins ................................................................................................. 7-4
7.3.2 Telnet Connection to SCU ........................................................................................... 7-4
7.4 EFM Plug-in in Minirack mechanics or tabletop housing ........................................................ 7-4
7.5 Naming of Ports ....................................................................................................................... 7-5
7.6 Built-in Command Line Interface (CLI) .................................................................................... 7-5
7.7 Built-in Web-Interface (CLI over HTTP) .................................................................................. 7-5
7.8 Built-in SNMP Tools ................................................................................................................ 7-6
7.9 Remote Line Connection Mode (SSH Access) ....................................................................... 7-1
7.9.1 Use of Secure Shell (SSH) .......................................................................................... 7-1
7.10 User Management ................................................................................................................... 7-2
8
Command Line Interface (CLI) ........................................................................................................ 8-3
8.1 CLI Command Structure .......................................................................................................... 8-3
8.1.1 Welcome Screen ......................................................................................................... 8-3
8.1.2 Menus .......................................................................................................................... 8-4
8.1.3 Prefixes an Shortcuts ................................................................................................... 8-4
8.1.4 Tab completion ............................................................................................................ 8-4
8.1.5 Help .............................................................................................................................. 8-4
8.1.6 Command History ........................................................................................................ 8-4
8.1.7 Continuous Displays .................................................................................................... 8-5
9
CLI Command Reference ................................................................................................................ 9-1
9.1 Introduction .............................................................................................................................. 9-1
9.2 Performance Management PM................................................................................................ 9-2
9.3 Fault and Maintenance Management FMM ............................................................................. 9-3
9.4 Configuration Management CM............................................................................................... 9-6
9.5 Security and Remote Management SM ................................................................................ 9-20
10
Set-up Remote Management Access and Load Configuration ............................................... 10-22
xii
Version 6.0-00
10.1
10.2
10.3
10.4
10.5
Operating Manual
Enable management access on dedicated Ethernet port ................................................... 10-22
Use setup command to configure the device .................................................................... 10-23
Usage of configuration files ................................................................................................. 10-23
Use setup command with DHCP to Configure Device ...................................................... 10-24
Loading Configuration Files ................................................................................................. 10-24
11
Supported SNMP MIBs ................................................................................................................ 11-26
11.1 MIB Reference ..................................................................................................................... 11-26
11.1.1 MIB II (RFC 1213) .................................................................................................... 11-26
11.1.2 SNMPv2-MIB (RFC 3418) ....................................................................................... 11-26
11.1.3 IF-MIB (RFC 2863) .................................................................................................. 11-27
11.1.4 IF-INVERTED-STACK-MIB (RFC 2863) ................................................................. 11-27
11.1.5 IP-MIB (RFC 4293) .................................................................................................. 11-27
11.1.6 IP-FORWARD-MIB (RFC 4292) .............................................................................. 11-27
11.1.7 EtherLike-MIB (RFC 3635) ...................................................................................... 11-27
11.1.8 MAU-MIB (RFC 4836) ............................................................................................. 11-27
11.1.9 ENTITY-MIB (RFC 4133) ......................................................................................... 11-27
11.1.10 DOT3-OAM-MIB (RFC 4878) .............................................................................. 11-27
11.1.11 EFM-CU-MIB (RFC 5066) ................................................................................... 11-27
11.1.12 IEEE8021-BRIDGE-MIB (part of IEEE802.1Q) ................................................... 11-27
11.1.13 IEEE8021-Q-BRIDGE-MIB (part of IEEE802.1Q) ............................................... 11-28
11.1.14 IEEE8021-SPANNING-TREE-MIB ...................................................................... 11-28
11.1.15 RMON-MIB .......................................................................................................... 11-28
11.1.16 HDSL2-SHDSL-LINE-MIB (RFC 4319) ............................................................... 11-28
11.1.17 DIFFSERV-MIB (RFC 2475) ............................................................................... 11-28
11.1.18 ARICENT-ECFM-MI-MIB..................................................................................... 11-28
11.1.19 ARICENT-ECFM-Y1731-MI-MIB ......................................................................... 11-28
11.1.20 SNMP-TARGET-MIB (RFC 3413) ....................................................................... 11-28
11.1.21 SNMP-NOTIFICATION-MIB (RFC 3413) ............................................................ 11-28
11.1.22 IEEE8021-PB-MIB ............................................................................................... 11-28
11.1.23 IEEE8021-CFM-MIB and IEEE8021-CFM-V2-MIB ............................................. 11-28
11.1.24 WATSON-MIB ..................................................................................................... 11-29
11.1.25 SCHMID-MIB ....................................................................................................... 11-29
12
Front Panels ................................................................................................................................. 12-30
12.1 Front Panel .......................................................................................................................... 12-30
13
Connectors and Cables ............................................................................................................... 13-31
13.1 DSL Interface ....................................................................................................................... 13-31
13.1.1 Connector ................................................................................................................ 13-31
13.2 Ethernet Interface ................................................................................................................ 13-32
13.3 Regenerator Connector ....................................................................................................... 13-32
14
Technical Specifications ............................................................................................................... 14-1
14.1 Interfaces ............................................................................................................................... 14-1
14.1.1 DSL Line Interface ..................................................................................................... 14-1
14.1.2 Ethernet Interfaces .................................................................................................... 14-1
14.1.3 Serial Interface ........................................................................................................... 14-2
14.1.4 Internal clock .............................................................................................................. 14-2
14.1.5 Clock Interface ........................................................................................................... 14-2
14.2 Power Consumption .............................................................................................................. 14-2
14.2.1 Plug-in ........................................................................................................................ 14-2
14.2.2 Regenerator ............................................................................................................... 14-2
14.3 Ethernet ................................................................................................................................. 14-2
xiii
Operating Manual
Version 6.0-00
14.4 Management Functions ......................................................................................................... 14-3
14.5 Environment........................................................................................................................... 14-4
14.5.1 Climatic Conditions .................................................................................................... 14-4
14.5.2 Safety ......................................................................................................................... 14-4
14.5.3 EMC ........................................................................................................................... 14-4
14.6 Physical dimensions and weight ........................................................................................... 14-4
14.6.1 Plug-in ........................................................................................................................ 14-4
14.6.2 Regenerator ............................................................................................................... 14-4
15
Terminology ................................................................................................................................... 15-5
16
Product Order Codes .................................................................................................................... 16-1
16.1 Modems ................................................................................................................................. 16-1
16.2 Accessories ........................................................................................................................... 16-1
Figures
Figure 2-1: Ethernet Services ............................................................................................................ 2-2
Figure 2-2: Campus Networks ........................................................................................................... 2-2
Figure 2-3: Linear Ethernet Network.................................................................................................. 2-3
Figure 3-1: G.SHDSL.bis standard linerates ..................................................................................... 3-1
Figure 3-2: Wetting current jumper location ...................................................................................... 3-3
Figure 3-3: EFM fragmentation and framing ...................................................................................... 3-5
Figure 3-4: Watson EFM Plug-in Block diagram ............................................................................... 3-6
Figure 3-5: Stacked VLAN frame format............................................................................................ 3-8
Figure 3-6: Simple VLAN Example .................................................................................................. 3-10
Figure 3-7: VLAN configuration for traffic concentration.................................................................. 3-10
Figure 3-8: VLAN configuration for Inband Management ................................................................ 3-11
Figure 3-9: Quality of Service functions ........................................................................................... 3-12
Figure 3-10: SAT setup .................................................................................................................... 3-24
Figure 4-1: Regenerator Interface Designation ............................................................................... 4-25
Figure 4-2: Cascading and addressing regenerators ...................................................................... 4-25
Figure 4-3: Regenerator powering reach vs. Loop resistance ........................................................ 4-27
Figure 4-4: Remote powering of a 4-segment span ........................................................................ 4-27
Figure 4-5: Remote powering of a 4-segment span ........................................................................ 4-28
Figure 7-1: Plug-in Addressing Scheme ............................................................................................ 7-4
Figure 12-1a: Front panel SZ.868.V654 ........................................................................................ 12-30
Figure 12-2b: Front panel SZ.868.V854 ........................................................................................ 12-30
Figure 13-1: DSL Connector .......................................................................................................... 13-31
Figure 13-2: Ethernet 1000base-T Connector ............................................................................... 13-32
xiv
Version 6.0-00
Operating Manual
Tables
Table 1-1: 19” Subrack waste heat management ................................................................................. ix
Table 1-2: 19” Subrack power management ......................................................................................... x
Table 3-1: Power Backoff .................................................................................................................. 3-2
Table 3-2: Wetting current jumper settings ........................................................................................ 3-3
Table 3-3: Recommended port cost values ..................................................................................... 3-16
Table 6-1: LED to wire-pair mapping ................................................................................................. 6-1
Table 6-2: Plug-in LED indications .................................................................................................... 6-1
Table 7-1: Bridge port naming ........................................................................................................... 7-5
Table 7-2: PME naming ..................................................................................................................... 7-5
Table 7-3: SNMP Tools ..................................................................................................................... 7-6
Table 8-1: Monitor Command Subsets .............................................................................................. 8-4
Table 8-2: Command Shortcuts ......................................................................................................... 8-4
Table 9-1: Command language elements ......................................................................................... 9-1
Table 13-1: DSL connector pin assignment .................................................................................. 13-31
Table 13-2: Ethernet 1000base-T Connector ................................................................................ 13-32
Table 16-1: Watson EFM Plug-in order codes ................................................................................ 16-1
Table 16-2: Accessories for plug-in ................................................................................................. 16-1
xv
1
Related Documents
[1] Schmid Telecom, Watson SHDSL EFM Plug-in MIB Overview
1-1
2
2.1
Overview
Introduction
The Watson SHDSL EFM Plug-in modems are SHDSL transmission systems
compliant to ITU-T G.991.2 Annex B/G (G.SHDSL.bis), to ETSI TS 101 524
(2006) and Ethernet in the First Mile (EFM) according to IEEE 802.3-2008 .
The Watson SHDSL EFM Plug-in provides transparent Ethernet services over up
to 8 single-pair DSL spans. Ethernet packets are mapped to DSL by using standard based IEEE 802.3 EFM encapsulation. DSL spans can be bonded using EFM
PAF.
SHDSL uses Trellis-coded PAM-16, PAM-32, PAM-64 and PAM 128 line codes
supporting multiple linerates as well as multiple pair bonding DSL transmission.
Depending on line distance and modem settings, symmetrical data rates of up to
15.3 Mbit/s per copper pair can be achieved.
The built-in Ethernet bridge allows VLAN switching according to IEEE 802.1Q2011 including support for single tagging (C-VLAN) and multiple tagging ‘Stacked
VLAN’ as well as C-VLAN – S-VLAN mapping. Quality of Service (QoS) is supported per service and allows classification, metering, scheduling and shaping to
achieve the required service quality.
Link protection and network resiliency is supported by Ethernet Link Aggregation
(LAG) according IEEE 802.3 and Rapid Spanning Tree protocol according IEEE
802.1Q.
For carrier class Operation Administration and Maintenance (OAM) the Watson
SHDSL EFM-Plug-in supports OAM functions according IEEE 802.3 clause 57
(Link OAM), IEEE 802.1ag (CFM) and ITU-T Y.1731 (Service OAM).
An integrated service activation test (SAT) feature according to Y.1564 is available as well.
The Watson SHDSL EFM Plug-in offers 4 Gigabit Ethernet User ports as well as
one SFP Combo Port which allows optionally loading 1000 Base Fx or other
modules as required.
The plug-in is designed for rack-based installation and fits into the Watson Subrack, the Watson Mini-Rack V2 Mechanics and the Table-Top housing. It can be
configured as both STU-C (master) and STU-R (slave) and can share the subracks with other Watson modems (e.g. E1-SHDSL-modems).
The Watson EFM Regenerator is used to extend the reach of a DSL link. The regenerator works in 1-pair and 2-pair modes, can be cascaded for very long links
and is available with a number of housing options.
The Watson SHDSL EFM Plug-in is fully manageable trough SNMP. Standardized Management Information Bases (MIBs) are provided for the extensive management of the modem. Typically the management and monitoring of the Watson
2-1
Operating Manual
Version 6.0-00
EFM Plug-in modems is done from a 3rd-party management platform (EMS /
NMS) with help of a graphical management tool using the SNMP protocol.
In cases where management access from a command line oriented Operator
Console is required, a Command Line Interface (CLI) and the SNMP-Tools are
available in the modem. They are accessible locally through the Subracks serial
interface or through Ethernet using the SSH-protocol from remote.
2.2
Applications
Figure 2-1 shows typical deployment scenarios of Watson EFM Plug-in to deliver
Metro Ethernet Services:
8 pairs
Ethernet
Transport
4 pairs
2 pairs
n x Ethernet
100 / 1000 Mbp
s
1 pair
Ethernet
Up to122.4 Mbp
s
Ethernet
Up to 61.2 Mbp
s
Ethernet
Up to 30.6 Mbp
s
Ethernet
Up to 15.3 Mbp
s
Figure 2-1: Ethernet Services
Several Watson EFM Plug-in modems are installed in a subrack at the central office or the point of presence. Depending on the service offered and the plug-in
type each plug-in can serve between one and eight customers. At the customer
premises either a tabletop modem or a Watson EFM Plug-in card in a tabletop
housing or in a minirack is installed. Traffic from each customer is available at a
dedicated Ethernet interface in the central office. Alternatively traffic from several
customers can be aggregated to a single Ethernet port. Advanced VLAN functions allow for customer isolation and traffic management.
Watson EFM Plug-in modems can also be used point-to-point as shown in Figure
2-2:
Figure 2-2: Campus Networks
2-2
Version 6.0-00
Operating Manual
For these applications two Watson EFM Plug-in modems in a tabletop housing or
in a 19’’ minirack are connected point-to-point with one of the modems being configured as DSL master and the other one as DSL slave. Depending on the distance and the number of wire pairs available line rates up to 45.6 Mbps are available. VLAN and MAC Address filtering functions allow for traffic management and
optimal use of the available DSL bandwidth.
Deployment in linear networks is supported with the Watson EFM Plug-in modems:
Figure 2-3: Linear Ethernet Network
In Figure 2-3 several sites (e.g. stations along a pipeline or a power line) are
connected with one or several pair DSL systems. In each site a single Watson
EFM Plug-in card terminates the DSL spans coming from "East" and "West"
sides and gives four local Ethernet interfaces e.g. to connect local station control
equipment. Traffic from the local interfaces can be aggregated with traffic on the
DSL and can be sent to either direction along the line. Traffic streams are kept
separate through VLANs.
The entire chain can be managed from a centralized site through inband management.
2-3
3
Watson SHDSL EFM Plug-in Features
3.1
DSL
3.1.1
Linerates and DSL sync rates
Watson EFM Plug-in modems support symmetrical DSL transmission as specified in ETSI TS 101 524 (SDSL) and ITU-T G.991.2 Annex B/G (G.SHDSL.bis).
The linecode used is either TC-PAM 16 or TC-PAM 32. With TC-PAM 16 the
maximum linerate rate per pair is 3’840 kbit/s (60 timeslots of 64 kbit/s). TC-PAM
32 uses a 32-level linecode and allows a maximum linerate per pair of 5'696
kbit/s (89 timeslots).
Figure 3-1: G.SHDSL.bis standard linerates
For certain linerates either TC-PAM 16 or TC-PAM 32 can be configured in the
modem. TC-PAM 16 has better DSL performance than TC-PAM 32. However
with linerates rates higher than 2’304 kbit/s (36 timeslots) and TC-PAM 16 the
symbol rate over the DSL becomes higher than what was specified in the original
version of ETSI TS 101 524. Higher symbol rates mean wider PSDs which in turn
can lead to higher interference to other DSL systems in the same cable binder,
e.g. ADSL, ADSL2, ADSL2+, VDSL2.
Watson EFM Plug-in modems support symmetrical DSL transmission as specified in ETSI TS 101 524 (SDSL) and ITU-T G.991.2 Annex B/G (G.SHDSL.bis).
The linecode used is either TC-PAM 16 or TC-PAM 32. With TC-PAM 16 the
maximum linerate rate per pair is 3’840 kbit/s (60 timeslots of 64 kbit/s). TC-PAM
32 uses a 32-level linecode and allows a maximum standard linerate per pair of
5'696 kbit/s (89 timeslots).
For certain linerates either TC-PAM 16 or TC-PAM 32 can be configured in the
modem. TC-PAM 16 has better DSL performance than TC-PAM 32. However
with linerates rates higher than 2’304 kbit/s (36 timeslots) and TC-PAM 16 the
symbol rate over the DSL becomes higher than what was specified in the original
version of ETSI TS 101 524.
3-1
Operating Manual
Version 6.0-00
In addition the Watson EFM Plug-in does also support the linecodes TC-PAM 64
and TC-PAM 128. With TC-PAM 64 the maximum linerate per pair is 11 Mbit/s.
TC-PAM 128 allows a maximum linerate per pair of 15.3 Mbit/s.
Higher symbol rates mean wider PSDs which in turn can lead to higher interference to other DSL systems in the same cable binder, e.g. ADSL, ADSL2,
ADSL2+, VDSL2.
3.1.2
Multi-pair operation
Watson EFM Plug-in modems support multi-pair operation, which allows aggregation of individual DSL wire pairs to be combined together in order to offer higher speeds or increased reach.
Multi-pair operation can be achieved by using the PME Aggregation Function
(PAF) mechanism, which is defined in Clause 61 of IEEE 802.3 and allows one or
more Physical Medium Entities (PMEs) to be combined together to form a single
logical Ethernet link.
PMEs can be bonded together choosing either:
 G.handshake according ITU-T G.994.1 or
 Bonding aggregation control protocol (BACP) according to ITU-T G.998.22005 Amendment 2.
PAF allows configuring different linerates on the different DSL wire pairs with a
maximum linerate ratio of 1 to 4. It is also resilient to DSL wire pair failure. If one
pair fails the link is maintained using the other pairs. The data service is running
at a lower speed, but is kept uninterrupted.
Note: Due to an architectural limitation only PME instances on the same DSL
Processor chip can be aggregated (ref. Figure 3-4).
3.1.3
Power Backoff
The transmit power of the modems can be decreased by activating the power
back-off mode. This reduces interference to other transmission systems operating on adjacent pairs bundled in the same cable.
With enabled power back-off the transmit power will be reduced adaptively in
function of the estimated cable attenuation:
Estimated Power
Loss(*)
Power Backoff
< 1 dB
6 dB
< 2 dB
5 dB
< 3 dB
4 dB
< 4 dB
3 dB
< 5 dB
2 dB
< 6 dB
1 dB
 6 dB
no backoff
(*) Calculated as Tx Power –
Estimated Rx Power
Table 3-1: Power Backoff
Note:
3-2
Power backoff can be configured individually for STU-C and STU-R.
Version 6.0-00
3.1.4
Operating Manual
Wetting Current
The Watson EFM Plug-in can source or sink wetting current over the DSL line.
Wetting current is configured per group of four wire pairs by jumpers. The lower
two jumpers configure lines A to D and the upper two jumpers configure lines E to
D. It is not possible to set only a single wire pair. The jumper configuration is for a
block of 4 wire pairs only.
Make sure that when one side of a line is set as wetting current source that the
other is set to be the sink. Also when one side has remote power active the other
side must be set to wetting current sink (no wetting current).
About 0.7 W is consumed when sourcing wetting current. If both modems are
configured as sink, no wetting current will flow.
Jumpers location
Wire pair E - H
Jumpers location
Wire pair A - D
Figure 3-2: Wetting current jumper location
Jumper Configuration
Wetting Current Function
No wetting current (off)
Wetting current source (on)
Table 3-2: Wetting current jumper settings
3-3
Operating Manual
3.1.5
Version 6.0-00
Master (STU-C) / Slave (STU-R)
To start up a DSL span, one system unit must be configured as master modem
(STU-C) and the other one as slave (STU-R). The master controls the span
startup procedure. If both system units are configured as master or as slave, no
startup will occur.
Usually, plug-ins are configured as master and tabletop modems as slave (default setting). However, it is possible to set up a DSL span between two plug-ins,
as long as one is configured as master and the other one as slave.
3.1.6
DSL Clocking
The Watson EFM Plug-in supports DSL clocking as follows:
 Clockmode 3a according to ITU-T G.991.2 and TS 101 524.
 Network clock on STU-C side taken from backplane or Ethernet if available. Falling back to internal 20MHz/25ppm crystal if no external network
clock is available.
 PME clock output on STU-C side
 PME as clock source on STU-R side
 Network clock sources for STU-C side:
o 6U subrack: clock input of SCU or ACU
o mini-rack V2 : front panel clock-input
o Ethernet copper ports (SZ.868.V854 only) as clock source
 Clock out on BNC connector on front panel
 Priority of clock source can be defined via SNMP
3-4
Version 6.0-00
3.2
Ethernet
3.2.1
Ethernet over DSL
Operating Manual
Ethernet packets are mapped on the DSL frame using the packet mode TPS-TC
layer of ETSI TS 101 524 / ITU-T G.991.2bis. As encapsulation method the IEEE
802.3 EFM 64b/65b framing is supported.
Figure 3-3: EFM fragmentation and framing
3-5
Operating Manual
3.2.2
Version 6.0-00
Ethernet Switching
The Watson EFM Plug-in card has a built-in Ethernet bridge that connects Ethernet ports, DSL spans and the plug-in controller:
MGMT2 2
(Backplane-Controller) .
MGMT1 1 [1]
(Bridge-Controller)
Controller
ETH1 (Uplink) 3 [2]
ETH2 (Uplink) 4 [3]
ETH3 (Uplink) 5 [4]
ETH4 (Uplink) 6 [5]
port 24
port 25
port 26
port 27
port 8
7 [6] PCS1 (Bridge-DSL)
SSMII 0
port 11
SSMII 3
port 9
channel 3 12 PME-B (SHDSL)
DSL Processor 1
SSMII 1
channel 1 13 PME-C (SHDSL)
port 10
SSMII 2
channel 2 14 PME-D (SHDSL)
port 0
SSMII 0
channel 0
19 PME-E (SHDSL)
port 3
SSMII 3
20 PME-F (SHDSL)
port 1
channel 3
DSL Processor 2
(8 pair variant only)
SSMII 1
channel 1
port 2
SSMII 2
22 PME-H (SHDSL)
Ethernet
Bridge
channel 0 11 PME-A (SHDSL)
channel 2
21 PME-G (SHDSL)
Figure 3-4: Watson EFM Plug-in Block diagram
3.2.1
VLANs and bridge modes
The Watson EFM Plug-in supports three bridge modes to handle VLAN tagged
Ethernet frames:
 Customer bridge mode (C-VLAN mode)
 Provider Bridge mode (PB) (S-VLAN mode)
 Transparent bridge mode (not recommended)
The implementation is based on IEEE 802.1Q-2011 standard. Please refer to the
standard for a detailed description of VLANs and bridge modes. In the following
we will give an overview of the supported VLAN functionality of the EFM Plug-in.
3.2.1.1
Customer Bridge Mode
Each of the Ethernet bridge ports (ETH1 ... ETH4, PCS1 … PCS8, MGMT1) can
be member of one or several VLANs. Up to 4094 VLANs can be configured in the
EFM Plug-in. Each VLAN has a VLAN Identifier (VID) between 1 and 4094.
Upon reception of an Ethernet packet at a bridge port, its VID is checked against
the VIDs of all VLANs this port is a member of. Packets that do not carry a VID of
one of these VLANs are discarded.
For untagged packets the Port VID (PVID) is used to determine VLAN membership.
Packets are only forwarded to ports that share membership of the same VLANs
as the packet.
3-6
Version 6.0-00
Operating Manual
If ingress filtering is disabled there is a slightly different treatment. Ingress Filtering will be described in the next chapter.
Each port can be configured to send packets tagged or untagged. . If the VLAN
egress tagging is configured to be untagged then the VLAN tag will be removed
and the packets will be sent untagged. . If the VLAN egress tagging is configured
to be tagged then the original VLAN tag or the PVID and Port Priority will be used
to send the packet tagged.
Upon transmission the packet will be tagged with the VLAN tag originally received (VLAN egress tagging configured to be tagged). If the packet was untagged then the PVID of the ingress port is added to the packet
3.2.1.1.1
Ingress filtering
The EFM Plug-in provides the possibility to set filtering options for incoming
Ethernet traffic (ingress). There are 4 possible options:
 Admit all -> tagged & untagged
o With this filter activated all frames are processed as described in
the chapter above. This is the standard option used in most of the
cases.
 Admit untagged and priority tagged
o If this filter is activated then only untagged and priority tagged
frames are processed. Tagged frames will be discarded.
 Admit tagged only
o If this filter is activated then only tagged frames are processed.
 disabled
o If ingress filtering is disabled then upon reception of an Ethernet
packet at a port its VID is not checked against the VIDs of all
VLANs this port is a member of but against the VIDs of all existing
VLANs in the Plug-in. Therefore packets are forwarded to all
VLANs with the same VID as the received packet even though the
ingress port itself is not a member of these VLANs.
3.2.1.1.2 Priority Tags
Ethernet packets with VID = 0 will be recognized by the EFM Plug-in as priority
tagged packets. In this case only the p-bit value of the tag will be used for QoS
handling but the VID is used in the same way as for untagged frames. VID 0 is
reserved for priority tag frames and can therefore not be used for VLAN definitions by the user.
Priority tag handling is available in the same way also in the PB mode.
3.2.1.2
Provider Bridge Mode (PB) (S-VLAN mode)
PB mode is a method to increase the number of available VLANs in a structured
and hierarchical fashion that is backward-compatible with single-tagged VLANs
as long as the network supports packet sizes of 1'526 bytes or more. It allows
separating the use of VLANs by the customer and the VLANs used by the provider.
This mode can place an extra tag (often referred to as the S-tag or Service Provider Tag) in front of the first tag (known as the C-tag or Customer Tag). The
double tag format is shown in Figure 3-5: Stacked VLAN frame format.
3-7
Operating Manual
Version 6.0-00
Figure 3-5: Stacked VLAN frame format
Whereas in customer bridge mode the TPID (Transport Protocol ID) is set automatically by the system to the value 0x8100, in PB mode the TPID has to be configured by the operator of the device. The standard TPID value as defined in the
standard IEEE 802.1Q-2011 for PB mode is 0x88A8. It is recommended to use
this value when operating in PB mode. Nevertheless the EFM Plug-in allows setting any other TPID value.
In PB mode three different port types are available to tell the system how a bridge
port shall behave:
Provider Network Port (PNP)
Customer Edge Port (CEP)
Customer Network Port (CNP)
3.2.1.2.1
Provider Network Port (PNP)
A Provider Network Port (PNP) type is the standard way to operate a bridge port
in PB mode. Ethernet traffic on a PNP will be handled in the same way as we already know it from the Customer Bridge Mode. The difference in PB mode is that
the bridge is now considering the S-tags (means, only tags with the same TPID
as configured in the Plug-in) and not C-tags for VLAN switching.
Ethernet packets received at a port are checked against the VID of all VLANs this
port is a member of (Ingress filtering modifies the behavior in the same way as
described above for the customer bridge mode). Packets that do not carry one of
these VIDs (in the S-VLAN Tag) will be discarded.
For untagged packets or C-VLAN tagged frames (where TPID is not equal to the
configured PB TPID) the port VID (PVID) is used to determine VLAN membership.
Packets are only forwarded to ports that share membership of the same VLANs
as the packet.
Upon transmission the packet will be tagged with the S-VLAN tag originally received. If the packet was untagged (or C-tagged) then the PVID of the ingress
port is added to the packet. If the VLAN egress tagging is configured to be untagged then the packets will be sent untagged (without an S-tag).
3.2.1.2.2
Customer Edge Port (CEP)
When selecting the Customer Edge Port (CEP) type for a port it is possible to
create the S-VLAN VID based on the C-VLAN VID of the received frames.
3-8
Version 6.0-00
Operating Manual
On CEP ports a mapping table for ingress traffic will be defined to describe how
the S-tags shall be created depending on the received C-VLAN values, e.g.
CEP mapping table:
Map C-VLAN VID(s) to S-VLAN VID:
--------------------------------10
 100
20,30
 200
The S-VLAN tag will then be used for the VLAN switching.
For untagged C-VLAN frames, the PVID is used as the input for the mapping.
The S-VLAN VID received from the mapping will then be used to determine
VLAN membership.
A CEP port has to be configured to egress untagged (for all VLANs it is member
of) to behave as expected.
3.2.1.2.3
Customer Network Port (CNP)
The Customer Network Port (CNP) is used in case when the TPID 0x8100 shall
be used for the PB mode which is normally used for C-VLAN TPIDs. In this case
the distinction between customer tags (C-tags) and provider tags (S-tags) cannot
be done through the TPID and therefore has to be defined explicitly. This is done
by declaring the port to be a Customer Network Port (CNP).
On a Customer Network Port (CNP) the EFM Plug-in will always add an additional VLAN tag (S-tag) using the Port default VID (PVID).
Each CNP port has to be configured to egress untagged (for all VLANs it is
member of) to behave as expected.
3.2.1.3
Transparent bridge mode
To operate the EFM Plug-in in transparent bridge mode you first have to create a
VLAN with VID 1 and add all the ports which shall be member of the transparent
bridge. Remind to add also MGMT1 into VLAN 1 because otherwise you will not
have management access to the EFM Plug-in anymore. The creation of VLAN 1
can be done either in Customer bridge mode or in Provider Bridge mode.
After VLAN 1 is created you can switch to transparent bridge mode. From now on
all Ethernet frames will be bridged transparently between the VLAN 1 member
ports. The transparent bridge does not care if the packets are tagged or untagged. Also the PVID and any ingress filtering have no effect in transparent
mode. The packets egresses the member ports untouched.
This operation mode is not recommended because also the management port
MGMT1 is part of the internal VLAN 1 and therefore MGMT1 may be loaded with
data traffic (e.g. broadcast messages) which may restrict management performance.
3.2.2
VLAN Examples
Figure 3-6 below shows a simple VLAN configuration example. Both on the DSL
and on the Ethernet side untagged packets are used. On the Watson EFM Plugin four VLANs (VLAN 1, VLAN 2, VLAN 3 and VLAN 4) are configured. Depend-
3-9
Operating Manual
Version 6.0-00
ing on its ingress port each packet gets a default tag between 1 and 4. This tag is
then used to switch the packet to the correct egress port, effectively connecting
ETH1 to DSL1, ETH2 to DSL2 etc. while blocking all traffic between Ethernet
ports and between DSL spans.
Figure 3-6: Simple VLAN Example
Figure 3-7 shows how the VLAN switching function can be used for traffic concentration:
Figure 3-7: VLAN configuration for traffic concentration
In this example four independent DSL customers are concentrated to a single
Ethernet trunk interface. On the DSL lines untagged packets are used. Upon ingress into the Watson Ethernet plug-in the packets get a default VLAN tag between 1 and 4 based on their ingress port. All traffic is switched to port ETH1
which is member of all four VLANs. The packets egress the Watson EFM Plug-in
with VLAN tags, allowing to separate traffic streams from the four DSL spans different customers. Ports ETH2 .. ETH4 are unused in this scenario.
Figure 3-8 shows how Ethernet user interfaces are used for inband management:
3-10
Version 6.0-00
Operating Manual
Figure 3-8: VLAN configuration for Inband Management
For user traffic we have the same configuration as in Figure 3-7. However we
have added one additional VLAN 4094 which is used for inband management.
Ports ETH1 and MGMT1 are members of this VLAN. Because the DSL spans are
not member of VLAN 4094 management traffic is isolated from user traffic and
there is no access to management function through the DSL spans.
Note that port MGMT1 must use untagged packets to properly interface with the
card controller. Management packets coming from the card controller are tagged
with VLAN 4094 upon ingress into the bridging function.
3.2.3
Quality of Service (QoS)
The Watson EFM Plug-in supports differentiated treatment of Ethernet packets
according to the service they belong to. The EFM plug-in supports service classification depending on one of the following criteria:
 depending on the ingress port
 depending by the layer 2 p-bit information (IEEE 802.1p bits in the VLAN
tag)
 depending on the VLAN ID (VID in the VLAN tag)
 depending on a combination of p-bit and VID
 depending on layer 3 DSCP information
The p-bit information is retrieved from the VLAN tag of the received Ethernet
packets. If the packets are untagged the p-bit information will be taken from the
default priority defined for the port (Port Priority).
It’s also supported to setup a mapping of DSCP to p-bit values.
For each service class one of three metering types can be selected:
 bypass
 srTCM (single rate three color marker)
 trTCM (two rate three color marker)
As the name TCM (three color marker) indicates the Ethernet frames will be, depending on the metering result, classified in three traffic categories (green, yellow, red) and assigned to one of the eight traffic classes.
Metering type ‘bypass’:
When the metering type ‘bypass’ is selected, all Ethernet frames are classified by
default as green traffic.
Metering type ‘srTCM’:
The metering type ‘srTCM’ meters a traffic stream and marks its packets according to three traffic parameters, Committed Information Rate (CIR), Committed
Burst Size (CBS), and Excess Burst Size (EBS), to be either green, yellow, or
red. A packet is marked green if it doesn't exceed the CBS, yellow if it does exceed the CBS, but not the EBS, and red otherwise. Packets marked red will be
discarded automatically.
For more details please refer to http://www.rfc-editor.org/rfc/rfc2697.txt .
Metering type ‘trTCM’:
The metering type ‘trTCM’ meters a traffic stream and marks its packets based
on two rates, Peak Information Rate (PIR), which is CIR + EIR, and Committed
Information Rate (CIR), and their associated burst sizes to be either green, yellow, or red. A packet is marked red if it exceeds the PIR and will be discarded
3-11
Operating Manual
Version 6.0-00
automatically. Otherwise it is marked either yellow or green depending on whether it exceeds or doesn't exceed the CIR.
For more details please refer to http://www.rfc-editor.org/rfc/rfc2698.txt .
Figure 3-9: Quality of Service functions
When a packet enters the Watson EFM Plug-in the service it belongs to is classified and, depending on the metering process, the packet is associated with a traffic class. Additional p-bit remarking or DSCP to p-bit mapping actions can be performed at this stage.
Afterwards the ingress QoS treatment is completed and the packet is bridged towards the egress ports, according to the VLAN bridging defined in the Plug-in,
where egress QoS treatment will be performed. A frame may be sent to several
egress ports, means the frame will be duplicated and sent to several queues.
Each port supports eight egress queues (Q1…Q8) for the processing of the outgoing traffic. Packets are mapped according to their traffic class (TC) to the
egress queues. TC1 is mapped to Q1, TC1 to Q1 and so on until TC8 and Q8.
Two schedulers are then available to empty the traffic queues. The two schedulers are:
a. Strict Priority scheduler (SP)
b. Weighted round robin scheduler (WRR)
Scheduling profiles can be configured to define whether the output from a queue
shall be connected to the SP- or WRR scheduler.
The output from the WRR- scheduler is connected as one input for the SPscheduler with the lowest priority.
The queues connected to the SP-scheduler will always be processed first, before
any queue connected to the WRR-scheduler is handled. Q7 is the highest priority
queue, Q0 has lowest priority. In weighted round robin mode (WRR mode) the
weights can be defined with values between 1 and 255 per queue.
There are up to eight profiles available to define the scheduling for the eight output queues. One profile defines one of the 8 possible settings for the eight egress
queues. A profile can be assigned to one or several ports to define scheduling for
that port. Therefore several ports might be simultaneously affected if a profile is
modified.
3-12
Version 6.0-00
Operating Manual
Finally the egress traffic can be shaped on a per port or per queue base. It can
be selected whether the rate limiting shall be in absolute or relative relation to the
interface speed. If relative is selected then it will be automatically adapted when
the interface speed is changed.
For the supervision of the QoS performance values there are packet counters
supported per meter color, per service and per EVC.
3.2.4
Layer 2 Control Protocol Handling
The Watson SHDSL EFM Plug-in allows to configure the handling of the layer 2
control protocols.
The default (standard) handling is according to IEEE 802.1Q.
It’s possible to configure per port whether the standard handling or a customized
handling shall apply. For the customized handling either filtering or forwarding of
the L2CP can be selected.
The customization can be performed for each of the following destination MAC
addresses:


3.2.5
01-80-C2-00-00-00 through 01-80-C2-00-00-0F (except 01-80-C2-00-0001) and
01-80-C2-00-00-30 through 01-80-C2-00-00-3F
Ethernet Trunking (LAG)
The Watson SHDSL EFM Plug-in supports the Ethernet Link Aggregation (LAG)
protocol according to IEEE 802.3 (Static mode).
Ethernet Link Aggregation can be used for the following applications:
1. to pool several physical connections together into one logical connection
(load balancing)
. This allows combining, for example, two EFM PAF groups, e.g. each with 4
DSL lines running at 2048 kbit/s, into one single Ethernet link with a total capacity of 16’384 kbit/s, which offers several advantages:
 A better scalability of the data rates.
 Increase the reach for a given data rate.
 Increase the availability. Even though one or several physical connections of a LAG were disconnected, the LAG allows sustaining the data
connection with a reduced data rate on the remaining links.
2. to implement a pair of active/standby connections
This allows e.g. a redundant connection which automatically switches from
one link to the other in case of a link failure. Two (or more) PCS or Ethernet
links are configured to form a protection group. One link within the group is
designated as working link and carries user traffic. The other link(s) is designated the protection link. On the protection link the DSL is synchronized but
this link carries no traffic. A priority can be set for each link to define which
link shall be active as per default (0 is highest priority value, the higher the
value the lower the priority). For two links with the same priority the system
will decide by internal measures which link is active.
3-13
Operating Manual
Version 6.0-00
If the working link fails then traffic is automatically switched to the protection
link. Protection is bi-directional i. e. transmit and receive directions are
switched simultaneously. Protection is revertive: once a working link has
failed and traffic has been switched to the protection link there will be an automatic switch back to the working link should this link become active again.
Protection groups need to be configured on the DSL master (STU-C) and the
DSL slave (STU-R) in the same way.
In the current implementation the trigger to switch-over from the active to the
standby link is the if-oper-status. By polling this link status value it is possible
to achieve switchover times of about 500 mS. In future implementations (interrupt driven) this can be lowered to <50 mS. Other solutions e.g. SOAM
CCMs based will also be possible.
Link Aggregation is standardized for full duplex point-to point connections. The
physical connections shall have the same line rate. To provide a better usability
for the DSL applications, the Watson SHDSL EFM Plug-in does allow LAGs for
physical connections with unequal line rates.
3.2.6
Spanning Tree Protocol
The Watson SHDSL EFM Plug-in supports the Rapid Spanning Tree (RSTP) protocol according to IEEE 802.1Q-2011.
The spanning tree network protocol provides a loop free topology for any bridged
LAN. It detects/disables network loops and provides backup links between bridges. If a loop is detected then the protocol blocks one or more redundant ports.
The bridges continually exchange information. When they recognize a change in
network topology then RSTP automatically reconfigures bridge ports to avoid
network failure. RSTP is enabled per port with the cm.stp portenabled Monitor command.
Bridge Protocol Data Units (BPDUs)
The bridges in a network continuously exchange RSTP information carried in
special frames called bridge protocol data units (BPDUs). BPDUs are exchanged
regularly at configurable intervals (the Hello time, 2 seconds by default) and enable bridges to keep track of network changes and activate or disable ports as required.
Topology Change Notification (TCN) BPDUs are used to inform other bridges of
port changes. TCNs are injected into the network by a non-root bridge and propagated to the root. Upon reception of the TCN the root bridge will set a Topology
Change flag in its normal BPDUs. This flag is propagated to all other bridges to
instruct them to rapidly age out their forwarding table entries.
Port states
Each port on a bridge can be in one of three states:
 Learning - the port processes BPDUs and awaits possible new information
that would cause it to return to the blocking state. While the port does not yet
forward frames it does learn source addresses from frames received and
adds them to the filtering database.
 Blocking – the port processes BPDUs but discards all other frames.
3-14
Version 6.0-00
Operating Manual
 Forwarding – the port forwards frames and processes BPDUs.
When a bridge port is initialized it will not immediately start to forward frames. It
will instead go into the Learning state while it processes BPDUs and determines
the topology of the network.
The port will go into Forwarding state after expiry of a timer (the forwarding delay
timer) unless RSTP determines that this port would cause a loop in the network.
In this case the port will transition to Blocking state.
Port state status can be displayed with the fmm.stp status command.
RSTP Protocol operation
 Root bridge election: one bridge in the network is selected as the root bridge.
The root bridge is the root of the tree spanning the entire network once the
RSTP has converged.
Selection is based on the Bridge Identifier (BID) which uniquely identifies
each bridge. A BID is composed of a configurable bridge priority and the MAC
address of the bridge. BPDU exchange results in the bridge with the numerically lowest BID to be selected as root bridge.
The bridge priority is normally left at its default value (32768) but can be reconfigured to a lower number if the network administrator wishes a particular
bridge to be elected as root bridge. This is done using the cm.stp priority command.
 Root port determination: each non-root bridge designates one root port. The
root port is the port through which this non-root bridge communicates with the
root bridge.
The root port is the port on the non-root bridge with the lowest path cost
(measured as sum the costs of all paths traversed to the root) to the root
bridge. The root port is in Forwarding state.
 Designated port determination: for each LAN segment (collision domain) the
RSTP configures one Designated port. The Designated port is the port on this
segment that has the lowest path cost to the root bridge. If more than one
port in the segment have the same path cost, the port of the bridge with the
lowest bridge ID is selected as a Designated port.
Designated ports are set to Forwarding state, all other ports are in Blocking
state.
Edge Ports
Ports which are known to be at the edge of the network i. e. not connected to
any other bridge can be configured as edge ports. Edge ports will immediately
transition into forwarding state since there is no possibility of it participating in a
loop.
Note that configuring a non-edge port as edge port might create loops in the network. Any port configured as edge port will automatically revert to non-edge configuration if a BPDU is received on this port. Configurable with the cm.stp
portedge Monitor command.
3-15
Operating Manual
Version 6.0-00
Point-to-point ports
Ports which connect to exactly one other bridge (no shared media) can be configured as point-to-point ports. Point-to-point ports can signal to the neighboring
bridge their desire to be Designated and Forwarding. Upon explicit acknowledgement from the neighboring bridge these ports can transition directly into forwarding state without waiting for a timer expiry. Configurable with the cm.stp
portptp Monitor command.
Path cost
Path cost is the total cost of transmitting a frame on to a LAN through that port to
the root bridge. This is the sum of the costs of each LAN segment or link along
the path.
Cost values are configured according to the bandwidth of the link. The slower the
media, the higher the cost. Configurable with the cm.stp portcost Monitor
command.
Recommended cost values are:
Link Speed
Recommended Cost
Recommended Cost Range
1 Mbps
20'000'000
2'000'000 – 200'000'000
2 Mbps
10'000'000
1'000'000 – 100'000'000
4 Mbps
5'000'000
500'000 – 50'000'000
8 Mbps
2'500'000
250'000 – 25'000'000
10 Mbps
2'000'000
200'000 – 20'000'000
100 Mbps
200'000
20'000 – 2'000'000
1 Gbps
20’000
2’000 – 200’000
Table 3-3: Recommended port cost values
Performance parameters
The operation of the RSTP is controlled by a set of configurable performance parameters:
 Hello Time: the interval between periodic transmissions of configuration messages by designated ports. Configurable with the cm.stp hello Monitor
command.
 Maximum Age: maximum age of a BPDU before it is discarded. The age of a
BPDU is incremented by one on each traversal through a bridge.
A bridge port that was disabled (e.g. through a reset or a link integrity failure)
will wait Maximum Age seconds before transiting into Learning state. The
Maximum Age parameter is controlled with the cm.stp maxage Monitor
command.
 Forwarding Delay timer: the delay used by the bridge in STP mode to transition Root and Designated Ports to Forwarding (this transition will take maximum Hello Time seconds in RSTP mode). Set with the cm.stp forward
Monitor command.
The following relationships are enforced by the Watson SHDSL EFM plug-in:
2 (Forward-Delay-Timer – 1.0 seconds)  Maximum-Age-Timer
Maximum-Age-Timer  2 (Hello-Time + 1.0 seconds)
3-16
Version 6.0-00

3.2.7
Operating Manual
Transmit Hold Count: the maximum number of bridging protocol data units
(BPDUs) transmitted per second. Controlled with the cm.stp txhold Monitor command.
Link OAM
The Watson EFM Plug-in supports Link OAM according IEEE 802.3 clause 57.
Link OAM provides mechanisms useful for monitoring link operation such as remote fault indication and remote loopback control. In general, Link OAM provides
network operators the ability to monitor the health of the network and quickly determine the location of failing links or fault conditions.
When using Link OAM the Watson EFM Plug-in can be either operated in active
mode or in passive mode. It supports the following Link OAM services:
 OAM discovery
o Active mode: initiate LOAM discovery process
o Passive mode: react to LOAM discovery process
 Remote Loopback
o Send loopback control OAMPDUs to put the peer in (near-end) intrusive loopback state. In this state all non-OAM packets are
looped back. Normal forwarding is suspended on such a link.
 Link monitoring
o Sends event notifications that permit the inclusion of diagnostic information.
 The following link events are supported:
o Errored Symbol
o Errored frame period
o Errored frame (100ms, frame)
o Errored frame seconds (100mS, seconds)
 The following link information can be provided:
o MAC address
o Vendor OUI
o Vendor Info
o Mode
o Max OAM PDU size
o Configuration revision
o Functions supported
3.2.8
Service OAM
The Watson EFM Plug-in supports Service OAM (Operation and Maintenance)
according IEEE 802.1ag CFM and ITU-T Y.1731.
The service-level OAM according IEEE 802.1ag CFM and ITU-T Y.1731 provides
tools to detect, isolate and report connectivity faults and to measure performance
parameters such as frame loss ratio, frame delay, and frame delay variation. One
can select whether the EFM Plug-in shall operate in CFM or in Y.1731 mode.
Changing the mode between CFM and Y.1731 may have an impact on the used
3-17
Operating Manual
Version 6.0-00
names since both standards support different naming conventions. IEEE 802.1ag
CFM uses the MAID (MDName and MAName) to identify PDUs and ITU-T
Y.1731 uses the MEGID (ICC and UMC) instead.
One important point to notice is that before the Service OAM functionality can be
used first the VLAN configuration of the network needs to be designed and implemented correctly. Since the Service OAM frames (OAM PDUs) use the same
VLAN path through the network as the data traffic it’s important to have the connections for the data traffic configured correct and up and running before any
Service OAM can be applied. Service OAM is not intended to support the operator to find configuration errors in a wrong network configuration. It’s intended to
supervise and measure connections in an up and running network.
Service OAM defines the following management components:
 Maintenance Entity Group (MEG)
A Maintenance Entity Group (MEG) consists of the MEs (see below) that
belong to the same service inside a common OAM domain. MEGs are
configured with a name and a level.
MEs belonging to the same MEG share a common MEG Level. Eight
MEG Levels (0 … 7) are available for the purposes of Service OAM
(where level 7 is the highest level).
E.g. for a Point-to-Point EVC, a MEG would contain a single ME, but for a
Multipoint-to-Multipoint EVC of n UNIs, a MEG would contain n*(n-1)/2
MEs.

Maintenance Entity (ME)
A ME represents an OAM entity that requires management. A ME is essentially an association between two maintenance end points within an
OAM Domain. MEs are configured with a name, the MEG-ID it belongs to
and a primary VLAN-ID. The VLAN-ID is the same as it is used in the
VLAN configuration of the device to define the path for the data traffic service that shall be supervised with the ME.
MEs contain a set of MEPs/MIPs, all of which are configured with the
same ME-ID.

MEG End Point (MEP)
A MEG End Point (MEP) is a management entity that is implemented at
the ends of a ME. It is a provisioned OAM reference point which can generate and receive OAM frames. A MEP can also initiate and react to diagnostic OAM frames.
Each MEP is configured with a MEP-ID, the ME-ID it belongs to, the
switch port related with the MEP and the VLAN-ID used for the OAM traffic and the data traffic.
 MEG Intermediate Points (MIP)
An MIP is a maintenance functional entity that is located at intermediate
points along the end-to-end path where Ethernet frames are bridged to a
set of transport links. It reacts and responds to diagnostic OAM frames initiated by MEPs. A MIP does not initiate proactive or diagnostic OAM
frames.
Service OAM occurs between the peer MEP instances of a ME. MEPs are associated to a Switch-port of the EFM Plug-in. A Switch-Port can implement multiple
MEPs and MIPs contingent on the number of ME levels.
3-18
Version 6.0-00
Operating Manual
The following Service OAM features are supported by the EFM Plug-in:
 Up to eight management domain levels
 MEG, ME, MEP and MIP creation / deletion
 Ethernet Continuity Check (ETH-CC)
These allow endpoints to detect an interruption in service. CCM’s
(Continuity Check Message’s) are sent from the source to destination node at periodic intervals. If either end does not receive a
CCM within a specified duration, then a fault is detected against
the service.
 Ethernet Loopback (ETH-LB)
These can be used during initial set-up or after a fault has been
detected to verify that the fault has occurred between two end
points.
 Ethernet Link Trace (ETH-LT)
Link Trace Protocol to trace the path to a target:
o
o
o
o
Multicast Link Trace from specific MEPs.
Link Trace replies to originating MEP.
Link Trace messages forwarding.
Response accumulation for examination.
Service OAM supports fault isolation through Linktrace Messages
(LTM) and Linktrace Reply (LTR). This serves two purposes. Under normal conditions, it allows to determine the path used by the
service through the network. While under fault conditions, it allows
to isolate the fault location without making a site visit.
SOAM Functions for Performance Monitoring:
 Frame Loss Measurement (ETH-LM)
Frame loss is calculated by sending transmit and receive counters within
the CCM for dual-ended measurements. The far end counters can then
be compared with those produced locally to derive frame loss as a percentage.
 Frame Delay Measurement (ETH-DM)
The EFM Plug-in currently supports two-way Y.1731 delay measurement.
The delay (or latency) is calculated by using a timestamp in the delay
measurement. The receiving end can derive the time delay experienced
across the network.
 Frame Delay Variation
Frame delay variation (or jitter) is calculated by tracking frame delay
measurements.
 Throughput
The EFM Plug-in Service OAM functionality supports throughput measurement.
3-19
Operating Manual
3.2.9
Version 6.0-00
Ethernet Clocking
The Watson EFM Plug-in supports Ethernet clocking as follows:
 Synchronous Ethernet clocks for SyncE according to ITU-T G.8262.
 Network clock on STU-C side taken from backplane or Ethernet if available. Falling back to internal 20MHz/25ppm crystal if no external network
clock is available.
 Synchronous Ethernet (SyncE) clock output on Ethernet (copper or SFP
ports) (SZ.868.V854 only)
 Synchronous Ethernet (SyncE) on Ethernet (copper or SFP ports)
(SZ.868.V854 only) as clock source
 Network clock sources for STU-C side:
o 6U subrack: clock input of SCU or ACU
o mini-rack V2 : front panel clock-input
o Ethernet copper ports (SZ.868.V854 only) as clock source
 Clock out on BNC connector on front panel
 Priority of clock source can be defined via SNMP
3.3
Management
3.3.1
SNMP
The Watson EFM Plug-in is fully manageable trough SNMP. Chapter 14.4 lists
the currently supported standardized Management Information Bases (MIBs).
Typically the management and monitoring of the Watson EFM Plug-in is performed from a 3rd-party management platform (EMS / NMS) e.g. with help of a
graphical management tool using the SNMP protocol, e.g. the Watson Element
Manager WEM 2.x.
Note: the SNMP read community has to be set to public and the write community has to be set to private to operate the EFM Plug-in.
3.3.1.1
SNMP Traps
The Watson EFM Plug-in does support SNMP Traps to forward events and
alarms towards a Network Management System (NMS). It is possible to configure
several trap destinations in the EFM Plug-in. Traps will be sent to all configured
destinations.
3.3.2
Command Line Interface (CLI)
When no SNMP Management System (EMS / NMS) is available or for local configuration of the device, the Watson EFM Plug-in provides a Command Line Interface (CLI). The CLI supports a selected set of management commands to perform the most important management tasks from a character oriented Operator
Console (Terminal /PC).
3-20
Version 6.0-00
3.3.2.1
Operating Manual
SSH - Secure remote communication
When working with the CLI, the SSH protocol (Secure Shell) is used for the remote access to the Watson EFM Plug-in. SSH allows a secure communication
over an unsecured Ethernet network.
3.3.2.2
Built-in SNMP tools
In addition to the CLI the Watson EFM Plug-in implements onboard SNMP Tools
to allow SNMP management for the device from a character oriented Operator
Console.
The character oriented built-in SNMP tools allow to generate the SNMP messages internally in the Watson EFM Plug-in. This allows to perform the complete
management of the device from a character oriented Operator Console.
3.3.3
Web-Interface
The Watson EFM Plug-in supports a Web-Interface for the management of the
device. Therefore a standard Web browser can be used by the operator to manage the Watson EFM Plug-in.
In the current release the Web-Interface provides a CLI over HTTP management
interface.
3.3.4
Management Access
Several interfaces are supported for the communication with the Watson EFM
Plug-in either for sending SNMP messages or for a character based communication with the built-in SNMP Tools:
 Serial interface (RS-232 port) of the Subrack SCU, ACU, Mini-rack or
Tabletop housing.
 Dedicated Ethernet Port, using one of the front-panels ETH1 – ETH4 user
interface connectors. In this case three interfaces are left for user traffic.
 Inband management by Ethernet through any of the Ethernet user interfaces (ETH1 – ETH4) by isolating management traffic from user traffic
with help of VLANs.
 Inband management by Ethernet over any of the EFM SHDSL user interfaces (DSL lines) if the remote modem is also setup accordingly.
No configuration limitations apply to any of the management access methods beside, that the initial setup must be on serial line.
3.4
Notes
Firmware Update
Firmware of the Watson EFM Plug-in can be updated remotely using the TFTP or
HTTP protocol. To load a new firmware package into a plug-in, an SNMP based
interface is available which can be triggered via SNMP protocol or via a CLI
command.
Starting with FW 3.01.01 and higher releases there is a restriction which doesn’t
allow to load (downgrade to) FW releases older than 3.01.01. The reason for this
is that starting with FW 3.01.01 the FW releases can be used for the EFM Plugin as well as for the SZ.468 EAD tabletop device.
3-21
Operating Manual
3.5
Version 6.0-00
Performance Monitoring / Statistics
The Watson EFM Plug-in provides various possibilities to monitor the performance for DSL and Ethernet traffic:
 DSL Parameters
 G.826 like DSL Statistics
 Interface Statistics
 RMON Statistics
 Packet Counters
3.5.1
DSL Parameters
The Watson EFM Plug-in provides information about the current Signal Noise
Margin (SNR Margin) and Attenuation of a DSL span.
Signal Noise Margin
The SNR Margin is the margin available compared to a signal to noise ratio that
gives a bit error rate of 10-7 in presence of average white Gaussian noise. The
SNR Margin can be evaluated by analyzing the error correction bits (Trellis bits)
in the line code.
Attenuation
The link attenuation is calculated by the modem assuming 0.4mm PE cable without bridged taps and measured at 150 kHz (for linerates of 200 kbit/s up to 1'992
kbit/s) or 200 kHz (for linerates of 2'056 kbit/s and above). This calculated attenuation may differ from the attenuation measured by other equipment for other cable configurations (other cable diameter, splices, bridged taps).
Both Signal Quality and Attenuation are effective maintenance tools for determining inadequate or bad cable pairs. They are available through SNMP (EFM-CUMIB::efmCuPmeStatusTable) or CLI (fmm.dsl status or diagnostic) or
WEM.
3.5.2
G.826 like Statistics
Watson SHDSL EFM Plug-ins support performance monitoring very similar to the
ITU-T G.826 specification. The G.826 like error performance parameters provide
quantitative performance information of a specific loop. They are intended to be
used for long-term evaluation of operating DSL spans.
The evaluation of the G.826 error performance parameters is based on CRC
(Cyclic Redundancy Check) error detection. The estimation of a bit-error rate is
not within the scope of the G.826 calculations.
On the DSL side, six CRC6 check bits are generated per DSL frame for each
channel and direction. The software counts block errors and evaluates the error
performance using these CRC6 bits.
G.826 like statistics are available through SNMP (EFM-CU-MIB:: efmCuPmeStatusTable, IF-MIB::ifTable, EFM-CU-MIB::efmCuPortStatusTable) or CLI (pm.dsl
statistics) or WEM.
3-22
Version 6.0-00
3.5.3
Operating Manual
Interface Statistics
The Watson SHDSL EFM Plug-in interface statistics provide basic measurements
for sent and received traffic. The amount of traffic as well as discarded packets
and errors can be monitored for incoming and outgoing traffic.
3.5.4
RMON Statistics
The RMON statistics available in the Watson SHDSL EFM Plug-in extend the
basic interface statistics and provide additional measurement information.
The following groups of the RMON-MIB are implemented:
The Ethernet Statistics Group:
The ethernet statistics group contains statistics measured by the
probe for each monitored Ethernet interface on this device. This
group consists of the etherStatsTable.
The History Control Group:
The history control group controls the periodic statistical sampling
of data from various types of networks. This group consists of the
historyControlTable.
The Ethernet History Group:
The ethernet history group records periodic statistical samples from
an ethernet network and stores them for later retrieval. This group
consists of the etherHistoryTable.
The Alarm Group:
The alarm group periodically takes statistical samples from variables
in the probe and compares them to previously configured thresholds.
If the monitored variable crosses a threshold, an event is generated.
A hysteresis mechanism is implemented to limit the generation of
alarms. This group consists of the alarmTable and requires the
implementation of the event group.
The Event Group:
The event group controls the generation and notification of events
from this device. This group consists of the eventTable and the
logTable.
3.5.5
Packet Counters (QoS Statistics)
The Watson EFM Plug-ins also supports traffic monitoring based on Packet
Counter which can be set:
 Per meter color
 Per service
 Per EVC
3-23
Operating Manual
3.5.6
Notes
3.6
Version 6.0-00
DSL Performance Supervision function
The quality of an entire link can be negatively affected even if the quality of only
one of the lines in a PAF-group (EFM aggregation) is bad. The reason for this lies
in the EFM protocol which splits Ethernet frames into smaller EFM packets and
distributes them over all available links of the aggregation. If the EFM packets on
one of the lines are damaged because of the bad line quality then this will also
damage the Ethernet frame itself and therefore the entire Ethernet traffic can be
drastically affected.
The Watson EFM Plug-in provides the DSL performance supervision feature to
cope with such cases. This feature allows to temporarily remove a line from an
aggregation when certain quality measures (SNR, Attenuation, Errored seconds)
are not in the defined range. When the measures are back in the accepted range
again for a certain time frame then the line can be put back into operation.
Use of BACP bonding protocol is required for this function.
Service Activation Test
The Watson SHDSL EFM Plug-in offers a built in Service Activation Tester (SAT)
according to ITU-T Y.1564. SAT can be used to verify the service attributes after
installing a new service or also for troubleshooting an already provisioned service.
The basic idea is that service attributes of several services can be verified. This is
done by starting a traffic generator on the local device and looping the traffic back
on the remote device so that it can be analyzed on the local device. Figure 3-10
shows the traffic flow during the test and the involved ingress- and egress policies of the devices.
Traffic
Analyzer
ETH1
MGMT1
I-Pol
MGMT1
E-Pol
E-Pol
ETH1
Traffic
Generator
I-Pol
ETH2
ETH2
E-Pol
Local Device
L2
Loop
I-Pol
E-Pol
ETH4
I-Pol
MEN
PCS1
ETH4
I-Pol
PCS1
ETH3
ETH3
E-Pol
Remote Device
Figure 3-10: SAT setup
Notes
3-24

In the current firmware release SAT configuration is only available via WEM2.
Version 6.0-00
Operating Manual
4
4.1
Operating modes
The Watson EFM regenerator has four DSL interfaces. It can be used either as
one regenerator for a two-pair system or as a dual regenerator for two independent 1-pair systems. No configuration is needed to select the operating mode. All
DSL parameters are defined by the DSL master settings.
4.2
Interface Designation
The regenerator interfaces are named according to the standard: the link towards
the LTU is called R-Side (REG-R) because it has the role of a DSL STU-R. The
link towards the NTU is called C-Side as it has the role of a DSL STU-C:
R - Side
(REG-R)
C - Side
(REG-C)
DSL A
STU-C
DSL-A
Regenerator
STU-R
DSL-B
DSL-B
Figure 4-1: Regenerator Interface Designation
4.3
Cascading
The Watson EFM Regenerator can be cascaded to form long links. The maximum allowed length of a link is 9 spans, i.e. 8 regenerators in series:
STUC
Remote Terminal
connection
REG
1
REG
2
CON 3
CON 4
...
REG
8
CON 10
STUR
CON 2 or
CON
Figure 4-2: Cascading and addressing regenerators
4-25
Operating Manual
4.4
Version 6.0-00
Bonding Protocols
The Watson EFM Regenerator supports two different bonding protocols:
 G.handshake (G.hs) according ITU-T G.994.1 or
 Bonding aggregation control protocol (BACP) according to ITU-T
G.998.2-2005 Amendment 2.
The choice of the bonding protocol has an impact on the maximum number of regenerators that can be remote powered in one link. With G.hs the maximum
number of remote powered regenerator is two. In case of BACP it’s four (see below for more details).
4.5
Powering
4.5.1
Remote powering
The Watson EFM Regenerator can be powered remotely from a Watson EFM
Plug-in modem equipped with the SZ.868.090 Remote Power Unit (RPU). The
RPU is an optional device which can be plugged on the EFM Plug-in when required.
The distance achievable with remote powering depends on both the cable characteristics (ohmic resistance) and the number of remotely powered regenerators.
As a general rule one node can be remotely powered per wire pair, i.e. one regenerator on a single-pair system and two regenerators on a two-pair system.
For longer links the additional regenerators must be powered locally.
Two factors limit the powering distance:
 The regenerator requires a minimal voltage (57 VDC) at its input for proper
operation
 The feeding current per pair is limited by the RPU to comply with relevant
safety requirements (the DSL link is classified as a TNV-3 circuit according to
EN60950-1:2006+A1:2010).
4-26
Version 6.0-00
Operating Manual
Figure 4-3 shows powering reach for single 1-pair and 2-pair regenerators (remote modem always locally powered):
Figure 4-3: Regenerator powering reach vs. Loop resistance
4.5.1.1
Remote powering and BACP protocol
If EFM Plug-in modems with remote powering facilities are used on both ends of
the DSL span and the BACP protocol is used then up to four regenerators can be
powered remotely:
Plug-in
STU-C
REG
1
REG
2
REG
3
REG
4
Plug-in
STU-R
Figure 4-4: Remote powering of a 4-segment span
It needs to be configured on STU-C side and on STU-R side if the Remote Power
Switch in the regenerator shall be ON or OFF. If it’s set to ON the regenerator will
forward remote powering to the next stage. After reset, the Remote Power
Switches on the Regenerators are all switched OFF by default.
4.5.1.2
Remote powering and G.hs protocol
If a EFM Plug-in modem with remote powering facilities is used and the G.hs protocol is used then up to two regenerators can be powered remotely:
4-27
Operating Manual
Plug-in
STU-C
Version 6.0-00
REG
1
REG
2
STU-R
Figure 4-5: Remote powering of a 4-segment span
Warning
4.5.2
Warning
When the G.hs protocol is used but no G.hs session can be established during
the first 10 seconds of link startup then the regenerator directly connected to the
STU-C (the 1st one) will automatically activate his own Remote Power Switch (set
it to ‘ON’). By doing so the regenerator will forward the remote power to the next
(2nd) regenerator and this will then allow the startup of a link with two regenerators.
Be aware that this also means that you will have the remote power voltage on
the DSL output connectors or the output cable during this phase even when the
output of the regenerator is not connected to the next device yet. It must be ensured that in such cases the DSL output lines of the regenerator will not be
touched during the link startup phase when the remote power voltage is on that
output.
Local powering
Alternatively a local DC power source can be connected to the regenerator directly, see 13.3. The alternative is to use remote powering from the LTU. Both local
and remote powering can be present simultaneously. No powering configuration
has to be done in the regenerator.
The local powering inputs are galvanically connected to the DSL wire pairs.
Power supplies used for local powering must be certified for connection
to TNV-3 interfaces according to EN 60950-1:2006+A1:2010.
If a battery is used for local powering then all other devices connected to this
battery must be protected against overvoltage from the DSL wire pairs.
Installation of the local powering circuitry from the power supply or the battery
must ensure that it is not possible to touch any conductive parts of the installation that are connected directly or indirectly with the local powering inputs.
For spans with 5 or more regenerators local powering is mandatory for regenerators 3, 4 .. n-2 where n is the number of regenerators in the span. Regenerators 1
and 2 can be powered remotely from the STU-C, Regenerator n and n-1 can be
powered remotely from the STU-R (if an EFM Plug-in with RPU is used as STUR).
4-28
5
Powering
Each Watson EFM Plug-in is fed via the subrack backplane with dual -48VDC
(referenced to 0VDC of the exchange battery). The plug-in generates the used
voltages onboard.
Additionally, the plug-in is fed over the backplane with an auxiliary +5VDC supply
(referenced to ground) generated on the ACU or SCU. The only purpose of this
voltage is to drive the alarm circuitry on each plug-in, even in the case of a failure
of the plug-in onboard powering circuitry
5-1
6
6.1
LEDs and Alarms
LEDs
The plug-in is equipped with four or eight LEDs depending on the model. The
SZ.868.V654 has four LEDs and the SZ.868.V854 has eight LEDs. Each LED reports the local status of one DSL wire-pair:
LED Wire-Pair
Function
Remarks
A
xDSL A
Local Status
B
xDSL B
Local Status
C
xDSL C
Local Status
D
xDSL D
Local Status
E
xDSL E
Local Status SZ.868.V854 only
F
xDSL F
G
xDSL G
H
xDSL H
Table 6-1: LED to wire-pair mapping
The "Local Status" LED indicates the status of the local end of the DSL wire-pair.
6.1.1
LED Indications
Status
LED
Modem Power failure
Off
DSL wire-pair not in use/inactive/not configured Off
Normal operation
Green
Urgent alarms
Red
Non urgent alarms
Yellow
Fail Safe Mode
All blinking
red
Table 6-2: Plug-in LED indications
6-1
Operating Manual
6.2
Version 6.0-00
Alarm Conditions
An alarm condition is displayed on the LEDs if one of the following condition is
met:
Urgent alarm (red):
 Loss of signal / frame alignment on the DSL side (LOSW)
 DSL block-error-rate according G.826  30% (BER-H)
Non urgent alarm (yellow):
 Link Attenuation threshold exceeded
 SNR Margin threshold exceeded
6.3
Note:
Alarm Relays
Plug-in alarms can be signaled through relay contacts present on the SCU (and
the ACU2R) which are are strongly recommended to be present in the subrack.
In total two relays are present to signal urgent and non-urgent alarms.
The ACU-48R is not compatible with the Watson EFM Plug-in.
Under normal plug-in power conditions the two output stages of each plug-in are
controlled by its microcontroller. In case of a power failure on an plug-in, both the
“Urgent” and “Non-urgent” alarms will be activated on the SCU or ACU. (The
SCU and the ACU generate an auxiliary +5 VDC which is used to pull-up the open
collector alarm output stages of the plug-ins.)
Both minirack mechanics and the plug-in tabletop housing have urgent and nonurgent alarm relay contacts.
Urgent Alarm:
 At least one of the plug-in – LEDs displays an urgent alarm
 Power failure of any one of the plug-ins
 Power failure of the auxiliary +5VDC auxiliary supply on the SCU or ACU
 Power failure of both –48VDC supplies
Non-urgent Alarm:
 At least one of the plug-in – LEDs displays a non-urgent alarm and none of
the plug-in – LEDs displays an urgent alarm
 Power failure of any one of the plug-ins
 Power failure of the auxiliary +5VDC auxiliary supply on the SCU or ACU
 Power failure of one of the –48 VDC supplies
6.4
SNMP Traps
SNMP Traps can be used to send alarm conditions towards a Network Management System (NMS). Currently the traps cold-start, link up, link down are supported.
6-2
Version 6.0-00
7
7.1
Operating Manual
EFM Plug-in Management Overview
Introduction
The Watson EFM- Plug-in is fully SNMP managed. Either a 3rd-party NMS platform is used to send SNMP messages to the Watson EFM Plug-in, or a character
oriented Operator Console or the Web-Interface with a standard browser is used
to operate the EFM Plug-in via the Command Line Interface (CLI).
Two connection modes are available for the character oriented communication
with the Watson EFM Plug-in:
 Serial Line Connection Mode
 Remote Line Connection Mode (SSH Access)
With the factory default configuration in place the initial configuration has to be
carried out in the Serial Line Connection Mode with a character oriented Operator
Console.
7.2
Serial Line Connection Mode
The Serial Line Connection Mode is the factory default setting for the Watson
EFM Plug-in. For this mode the modems have a serial interface to connect a
character oriented Operator Console (a terminal or a PC with terminal emulation
software). The serial interface (RS-232) is available on the SCU, the ACU, the
miniracks mechanics and the tabletop housing.
The Operator Console terminal or terminal emulation must be VT100 compatible
and must be configured as follows:
 9600 baud, asynchronous
 8 bits, no parity, one stop bit
 No new line on carriage return (i.e. no line feed on carriage return)
 XON/XOFF enabled
Notes:


Between plug-in and the terminal the XON/XOFF protocol is used for flow
control. In order to re-enable communication with an plug-in occasionally left
in XOFF state, it is recommended to start each session with Ctrl-Q (=XON)
followed by an ECHO command.
If you use the HyperTerm terminal emulator delivered with Windows® then
you must configure HyperTerm for VT100 emulation in the "Settings" tab of
the connection properties (File – Properties).
7-3
Operating Manual
Version 6.0-00
7.3
Watson EFM Plug-in in Subrack with SCU
7.3.1
Addressing of Plug-ins
The Operator Console terminal connects through the SCU or ACU to a serial bus
on the subrack backplane which is accessible by all plug-ins.
At any time, only one of the plug-ins in the subrack can be logically connected to
the Operator Console. The appropriate plug-in interface is addressed (i.e. selected) according to its physical position in the subrack, starting with the leftmost slot
number 01 and ascending rightwards to number 12. To select a plug-in in slot
number nn just type %nn in the terminal, e.g. to select the plug-in in slot 7 type
%07.
%01
%02
%03
%04
%05
%06
%07
%08
%09
%10
%11
%12
Figure 7-1: Plug-in Addressing Scheme
To see which units in a rack are available, you can use the ECHO command.
Each unit will respond with its associated slot number (%SN).
The response could be: %01 %03 %08 %10 %11
Notes:
7.3.2



The ECHO command is not echoed on the terminal
The selection command (%nn) is not echoed on the terminal
Each command must be terminated by a carriage return.
Telnet Connection to SCU
By using a SCU a remote Telnet connection can be established with the SCU
and then the SCU establishes the communication to the Watson EFM Plug-in.
See SCU documentation for further information
Notes:


7.4
The exit command is available on the plug-in if it is accessed via
SCU/Telnet and the ACU serial port from an Operator Console.
To address another plug-in in the subrack after exit type %nn (nn = slot
number)
EFM Plug-in in Minirack mechanics or tabletop housing
No addressing procedure is required in these cases. After power-up the prompt
on the Operator Console appears directly.
7-4
Version 6.0-00
7.5
Operating Manual
Naming of Ports
In SNMP communication (SNMP Tools or MIBs references) the Watson EFM
Plug-in ports are identified through indexes and not through their names:


one for all manageable interfaces  IF-MIB::ifIndex
one for interfaces that are used for bridge configurations
 IEEE8021-BRIDGE-MIB::ieee8021BridgeBasePortIfIndex
Bridge Ports: Name to Index Mapping
interface 
MGMT1 ETH1
ETH2
ETH3
ETH4
applicable interfaces
ifIndex
1
3
4
5
6
all
bridge index
[1]
[2]
[3]
[4]
[5]
port bit set
8000
4000
2000
1000
0800
only those being
connected to a bridge
interface 
PCS1
PCS2
PCS3
PCS4
PCS5
PCS6
PCS7
PCS8
ifIndex
7
8
9
10
15
16
17
18
bridge index
[6]
[7]
[8]
[9]
[10]
[11]
[12]
[13]
port bit set
0400
0200
0100
0080
0040
0020
0010
0008
Table 7-1: Bridge port naming
Non-Bridge Ports: Name to Index Mapping
Interface 
MGMT2 PME-… A
ifIndex
2

1 1
B
C
D
E
F
G
H
1 2
1 3
1 4
1 9
2 0
2 1
2 2
Table 7-2: PME naming
Cf. also Figure 3-4.
The number of DSL spans varies depending on the card type and configuration.
7.6
Built-in Command Line Interface (CLI)
The Watson EFM Plug-in provides a Command Line Interface (CLI) to perform
the most important management tasks from a character oriented Operator Console. A reference to the supported CLI commands is provided in chapter 9.
7.7
Built-in Web-Interface (CLI over HTTP)
The Watson EFM Plug-in implements a Web-Interface which can be accessed
via HTTP by using a standard Web browser.
The Ethernet port where you connect the computer with the Web browser must
be assigned to the management VLAN in order to grant access to management
and an IP address must be assigned to the EFM Plug-in.
After that you can open the web browser and type the IP address of EFM Plug-in
in the address bar and press Enter (e.g. http://192.168.0.72).
The Login window will be prompting for a Username and Password.
7-5
Operating Manual
7.8
Version 6.0-00
Built-in SNMP Tools
The Watson EFM Plug-in implements onboard SNMP Tools to allow SNMP management for the device from a character oriented Operator Console. The open
source NET-SNMP™ software suite is used for the built-in SNMP tools.
The NET-SNMP commands are invoked from the command prompt displayed on
the Operator Console (terminal). The same environment and commands are
available in serial and remote line connection mode.
The table below provides an overview of the available commands:
Tools/Commands
Purpose:
snmpget
retrieve one or multiple management values from a
network entity
snmpset
write one ore multiple management values to a network entity
snmpwalk
retrieve a subtree of management values from a
network entity
snmptable
retrieve an SNMP table from a network entity ans
display it in tabular form
Table 7-3: SNMP Tools
Please refer to the NET-SNMP documentation available on the internet for further
information about the usage of NET-SNMP:


Manual: http://www.net-snmp.org/docs/man/
Tutorials: http://www.net-snmp.org/tutorial/tutorial-5/commands/index.html
Issue a First SNMP Command
Example: Ask for the current firmware revision by issuing the following SNMP
command:
LTU_1> snmpget localhost ENTITY-MIB::entPhysicalFirmwareRev.1
The output will look similar to:
ENTITY-MIB::entPhysicalFirmwareRev.1 = STRING: application firmware: SZ.868.A1-2.03.02
Note: The leading “LTU_1>” denotes the prompt and must not be typed in when
using a command.
7-6
7.9
Remote Line Connection Mode (SSH Access)
Remote Line Connection Mode is not available with the default settings of the
Watson EFM Plug-in. It first has to be configured by using an Operator Console
in Serial Line Connection Mode according to the specific needs of a user project.
Several ways for remote SNMP management connections are available:
 dedicated Ethernet Port, using one of the front-panels ETH1 – ETH4 user
interface connectors. In this case three interfaces are left for user traffic.
 inband management by Ethernet through any of the Ethernet user interfaces (ETH1 – ETH4) by isolating management traffic from user traffic
with help of VLANs.
 through the Ethernet payload carried over any of the EFM SHDSL user interfaces (DSL lines) if the remote modem is also setup accordingly.
 through VLAN separated inband traffic on a DSL Line (Remote Site,
Tagged)
Prerequisites
To enable remote access to the modem through SSH the modems IP address
and a suitable VLAN setup has to be configured using the serial interface (described in Chapter 7).
Note:
Please be aware that care should be taken while modifying the IP and VLAN configuration to avoid being locked out from remote management. Add and test new
IP address and Management VLANs before deleting the old one. Prepare a
fallback scenario for serial access or telnet over SCU access.
After the required Remote Line Connection Mode has been configured on the
Watson EFM Plug-in two ways of management communication over the remote
connection are possible:
1. Direct SNMP protocol based communication
2. Character oriented communication with the Command Line Interface and
the built-in SNMP tools over a secure SSH access.
Option 1 is seen as the typical way for the management and monitoring of the
Watson EFM Plug-in modems where a 3rd-party management platform (EMS /
NMS) is used.
Option 2 provides a SSH character oriented interface to the CLI and the SNMPTools as already known from the Serial Line Connection.
7.9.1
Use of Secure Shell (SSH)
For the remote access to the command oriented management the SSH protocol
(Secure Shell) is used.
SSH is a protocol that allows a secure, authentified and encrypted connection to
the Watson EFM Plug-in over an unsecured network. SSH is a replacement of
formerly used solutions like rlogin, telnet and rsh.
SSH applications are available for all major operating systems e.g.:
7-1
Operating Manual
Version 6.0-00
 Microsoft Windows™: PuTTY (http://www.putty.org/)
 Unix like operating systems like Linux: built-in ssh client (usually OpenSSH)
Please refer to the documentation of the selected SSH application for further information about installation und usage.
After having logged into the modem via SSH the same command interface with
identical capabilities is provided as if logged in over the serial interface or telnet
through the subracks SCU.
You will see the Operator Console prompt:
Monitor V3.01.01
Copyright (C) 2001-2013 by Schmid Telecom AG Zuerich, Switzerland
+-----------------------+
|
Main Menu
|
+-----------------------+
1.
2.
3.
4.
5.
Performance management (PM)
Fault and maintenance management (FMM)
Configuration management (CM)
Security and remote management (SM)
Exit
LTU_01>
Enter username and password if asked for.
Note:
7.10
The default username is admin, the default password is admin. It is possible to
change these by using the User Management as described in the next chapter.
User Management
The default username is admin and the default password is admin (factory default). These values can be modified and additional management accounts can
be created as required.
There are two management roles defined for the Watson EFM Plug-in:
 Administrator (admin)
 Operator
Operators can perform the same commands as an administrator except the creation and modification of other management user accounts and password modification management.
Note:
7-2
User management and password usage shall be handled with care to prevent
dead locks where management access to the device is lost because user credentials are lost.
A factory default reset will recover the initial admin account and delete all other
user accounts.
Version 6.0-00
8
Operating Manual
Command Line Interface (CLI)
8.1
CLI Command Structure
8.1.1
Welcome Screen
After connecting the Terminal/PC the welcome screen is shown with information
about the modem type and Firmware Version, e.g.:
Monitor V3.01.01
Copyright (C) 2001-2013 by Schmid Telecom AG Zuerich, Switzerland
+-----------------------+
|
Main Menu
|
+-----------------------+
1.
2.
3.
4.
5.
Performance management (PM)
Fault and maintenance management (FMM)
Configuration management (CM)
Security and remote management (SM)
Exit
LTU_01>
To select the desired sub-menu, type the appropriate number.
The available CLI commands are described in chapter 8.
Notes:


The Exit command is only available on the plug-in if it is installed in a subrack or accessed via Telnet..
To address another plug-in in the subrack after Exit type %nn (nn = slot
number)
8-3
Operating Manual
8.1.2
Version 6.0-00
Menus
The Monitor menu is structured in the following sub-sets:
Performance management
PM
Fault and maintenance management
FMM
Configuration management
CM
Security and remote management
SM
Table 8-1: Monitor Command Subsets
Typing m at any submenu will bring you back to the main menu.
8.1.3
Prefixes an Shortcuts
The available commands depend on the submenu currently active.
To access a command from a different submenu the command can be prefixed
with the name of the submenu and a . (Dot), e.g. you can use
FMM.diagnostic to display the DSL diagnostic display while in the Configuration submenu.
The most popular commands are available in all submenus as shortcuts:
diagnostic
dia
Table 8-2: Command Shortcuts
8.1.4
Tab completion
You can use tab completion to simplify typing of long commands. By typing the
<TAB> character in after entering the first character(s) of a command word the
CLI will try to complete the command as much as possible. Example:
LTU_01_CM> set <TAB> will do a partial completion of the command to
LTU_01_CM> setup
Notes:
8.1.5

Tab completion is only possible for commands, not for parameters.
Help
Typing h or help at any submenu will list all commands available in that submenu in alphabetical order. Typing h command (or help command) will display
help for a particular command.
8.1.6
Command History
The Watson EFM Plug-in keeps a command history. To recall a command recently entered use the up-arrow and down-arrow keys to scroll through the histo-
8-4
Version 6.0-00
Operating Manual
ry of commands. Commands may be edited by using the DEL key and the cursor
keys.
8.1.7
Continuous Displays
Some commands (diagnostic) continuously update the screen with the latest
information. These commands will stop updating the screen if the user presses a
key.
8-5
Version 6.0-00
9
9.1
Operating Manual
CLI Command Reference
Introduction
This chapter defines the CLI command language. The language is made up of
the following elements:
command
Commands are written in lowercase
keyword
Keywords are written in lowercase
<Parameter>
Parameters are enclosed in < brackets >. Replace the parameter with the actual value.
<Parameter|Parameter>
<keyword | keyword>
Choices are denoted with vertical bars |. In a
choice group one of the parameters must be
specified.
[ Parameter ]
[ keyword ]
Optional parameters are enclosed in [ brackets ]. Optional parameters can be specified
but are not required.
{ Parameter-List }
A parameter list is enclosed in { braces }. A
list of parameters is a sequence of parameters
separated by one or more spaces.
Table 9-1: Command language elements
The CLI commands are listed in alphabetic order. First the command syntax is
listed in bold face, followed by a short help text describing the command. The descriptions are held brief and most parameters are not explained in more details
because it’s assumed that they are self-explaining.
Examples of often used self-explaining Parameters:
<eth1…4>
Ethernet ports on the front plane.
<pme-a…d/h>
the PME name. E.g. pme-a or pme-b.
Note: SZ868.V654 allows names a – d; SZ868.V854 allows names a – h. This
difference between the two EFM Plug-in model is showed with a..d/h. In a similar
way we will write <pcs1..4/8> to describe the different amount of PCSs
available in SZ868.V654 and SZ868.V854.
When considered useful additional description is given for a command.
9-1
Operating Manual
9.2
Version 6.0-00
Performance Management PM
dsl statistics <pme-a..d/h> [<abs|reset>]
Show SHDSL statistics for the given PME relative
to the values stored at the last reset.
abs: Shows the absolute counter values
reset: Stores the counter values as a reference
to show relative counter values.
eth statistics <eth1..4|pcs1..4/8|mgmt1>
<show|reset>
Show|Reset Ethernet performance/statistics of a
port
loam statistics <eth1..4|pcs1..4/8> <show|reset>
Show/reset OAM statistics
loam eventlog <eth1..4|pcs1..4/8>
Show OAM eventlog
SOAM mode: IEEE
soam statistics <ma no> <show|reset>
Show/reset statistics of all MEPs within MA
<ma no> is the MA 'No' field from the command
'cm.soam show' result
SOAM mode: Y.1731
soam statistics <meg no> <show|reset>
Show/reset statistics of all MEPs within MEG
<meg no> is the MEG 'No' field from the command
soam delay <mep no> <start <mepid>
[count]|stop|show>
Start/stop/show two-way Y.1731 delay measurement
on MEP <mep no> towards remote MEP <mepid>.
9-2
Version 6.0-00
Operating Manual
count: No of DM messages to send [1..8192] (default: count=100)
mep no: the MEP 'No' field from the command
soam floss <mep no> <start <mepid> [count [interval
[prio [drop]]]]|stop|show>
Start/stop/show one-way Y.1731 frame loss measurement on MEP <mep no> towards remote MEP <mepid>.
count: No of LMM messages to send [1..8192]
interval: 100ms, 1s, 10s, 1min or 10min
prio: priority [0..7]
drop: drop enable [false..true]
(default: count=100, interval=100ms prio=7,
drop=false)
9.3
Fault and Maintenance Management FMM
clock status
Show clock status
diagnostic (dia) [pme-a .. d/h]
Activate diagnostic display. Detailed information about a single span is displayed if an
optional PME is given as an argument.
9-3
Operating Manual
Version 6.0-00
The diagnostic (or dia) command is available from all menus by typing dia.
LTU_01_FMM> dia
-------------------------------------------+--------------Port | Network
SNR Attn
PWR Status | Alarms
| Element
[dB] [dB]
[dBm]
|
-------------------------------------------+--------------PME-A| STU-C
19
0
14.5
Sync |
| SRU1-R
18
0
14.5
Sync |
| SRU1-C
19
0
14.5
Sync |
| STU-R
19
0
14.5
Sync |
PME-B| STU-C
19
0
14.5
Sync |
| SRU1-R
18
0
14.5
Sync |
| SRU1-C
19
0
14.5
Sync |
| STU-R
19
0
14.5
Sync |
PME-C| STU-C
18
0
14.5
Sync |
| SRU1-R
19
0
14.5
Sync |
| SRU1-C
19
0
14.5
Sync |
| STU-R
19
0
14.5
Sync |
PME-D| STU-C
19
0
14.5
Sync |
| SRU1-R
18
0
14.5
Sync |
| SRU1-C
19
0
14.5
Sync |
| STU-R
19
0
14.5
Sync |
-------------------------------------------+---------------
After dia the screen is continuously updated until the user presses a key.
Note
SQ
Attn
Signal Quality
PWR
Transmit power
Status
Synchronization status
Alarms
List of all active alarms
Link attenuation
Only STU-C information will be displayed in the current release. The value
65535 will be displayed when no measured value is available.
dsl inventory <pme-a..d/h>
Show SHDSL inventory
dsl status [<core|all|power|supervision>]
Show SHDSL interface status.
default: core
eth status
Show Ethernet interfaces status
9-4
Version 6.0-00
Operating Manual
loam status <eth1..4|pcs1..4/8>
Show OAM status
reset card
Reboots the card
SOAM mode: IEEE
soam lb <mep no> <mepid> [count]
Start loopback measurement on MEP <mep no>
towards remote MEP <mepid>.
count: No of LBM messages to send [1..8192]
(default: count=100)
soam ltr <mep no> <mepid> [ttl [timeout]]
Perform a link trace from MEP <mep no> to remote
MEP <mepid>
ttl: max number of hops [1..255]
timeout: [1..10] seconds
(default: ttl=32, timeout=5)
soam status <ma no>
Show status of all MEPs within MA <ma no> is the
MA 'No' field from the command 'cm.soam show'
result
SOAM mode: Y.1731
soam lb <mep no> <mepid> [count]
Start loopback measurement on MEP <mep no>
towards remote MEP <mepid>.
count: No of LBM messages to send [1..8192]
(default: count=100)
soam ltr <mep no> <mepid> [ttl [timeout]]
Perform a link trace from MEP <mep no> to remote
MEP <mepid>
ttl: max number of hops [1..255]
timeout: [1..10] seconds
(default: ttl=32, timeout=5)
soam status <meg no>
9-5
Operating Manual
Version 6.0-00
Show status of all MEPs within MEG <meg no> is
the MEG 'No' field from the command 'cm.soam
show' result
stp status
Show RSTP status
9.4
Configuration Management CM
bridge show [<core|all|cepmap|l2cp>]
Show bridge configuration
default: core
bridge mode <cvlan|svlan|dbridge>
Set the bridge mode (component type)
bridge tpid <id>
Set TPID for S-VLAN
(<id> range is 0x0000..0xffff)
bridge addrlearning <on|off>
Enable/disable MAC address learning on the
bridge
bridge vlanlearning <shared|individual>
Set the type of learning constraint
shared: all VLANs share the same filtering database.
independent: each VLAN uses an independent filtering database
bridge porttype <mgmt1|eth1..4|pcs1..8> <type>
Set port in Provider Bridge to <type>
pnp: Provider Network Port
cnp: Customer Network Port
cep: Customer Edge Port
bridge cep <mgmt1|eth1..4|pcs1..8> <cvid>
<svid>|remove
9-6
Version 6.0-00
Operating Manual
Add/remove C-VID to S-VID mapping on
Customer Edge Port
bridge l2cp <mgmt1|eth1..4|pcs1..8> <profile>
Set L2CP filtering behaviour to <profile>
standard: according to IEEE 802.1Q
custom: according to custom table
bridge l2cpcustom <da> <filter|forward>
Set action for L2CP filtering custom profile
da: last octet of the multicast MAC destination
address.
Valid entries are 0x00,0x02-0x0F,0x30.
The entry 0x30 is a wildcard for 0x30-0x3F.
filter: filter frames
forward: forward frames
clock show
Show clock configuration
clock src <backplane|pme-a..h|sfp|eth1..4>
<0..1000|disable>
Set clock source priority
clock out <frontpanel|pme-a..h|sfp|eth1..4>
<on|off>
Set clock output
conffile show
Show all local configuration names
conffile load <name|url>
Load and activate local or remote configuration.
Caution: reboots device! (protocols: FTP, TFTP
or HTTP)
To load factory-default configuration, type:
conffile load factory-default
The configuration of the EFM Plug-in will be loaded and activated with the
specified File. The File can be either a local configuration file stored on the
EFM Plug-in and specified by the Name or it can be loaded from a remote
9-7
Operating Manual
Version 6.0-00
TFTP storage as specified by the URL. Anonymous FTP or HTTP protocols
are also supported for the access to the remote storage. Device reboots automatically upon successful configuration load.
Parameters:
name
Name of a valid configuration file available in the local
storage of the EFM Plug-in.
URL
Name of a valid configuration file available in a remote
storage as specified by the URL.
e.g. tftp:://192.168.203.1/tftp/efmp/conffiles/bhaul-conf
conffile load factory-default
The predefined conffile name “factory-default”
is defined in the EFM Plug-in to easily allow to
load and activate the factory default configuration.
(caution: reboots device!)
Afterwards all interfaces are admin-status down
(except CLI/serial RS232). Configuration files
previously stored to the device with conffile
save will not be removed by this command.
conffile save <name|url>
Save current
to remote url
configuration
to
local
file
or
The conffile save command saves the current active configuration of the EFM
Plug-in into a file which is either stored locally on the EFM Plug-in or in a remote
TFTP server if given an URL. TFTP server must be configured to accept anonymous uploads.
conffile copy <source> [<dest>]
Copy configuration locally or to/from url
Default destination: local configuration with
the same file name as <source>.
conffile merge <source> [<dest>]
Merge configuration locally or to/from url
Default destination: local configuration with
the same file name as <source>.
9-8
Version 6.0-00
Operating Manual
Whereas the conffile load and conffile copy commands will replace the
current modem configuration entirely, conffile merge will only change the
values that are defined in the conffile but will leave all other values of the current
configuration untouched.
conffile del <name>
Delete local configuration
dsl show [<core|all|supervision>]
Show SHDSL configuration
Default:core
dsl aggregate <mode> <master|slave>
Configure PME aggregation. This command reconfigures all SHDSL lines.
mode: {1|2|4} number of aggregated PMEs
master: ieee2BaseTLO (SHDSL master)
slave: ieee2BaseTLR (SHDSL slave)
per PCS
dsl adminstatus <pme-a..d/h|pcs1..4/8> <up|down>
Set SHDSL admin status
dsl linerate <pme-a..d/h> <n>
Set line rate for a SHDSL port to n * 64 kbit/s:
Standard linerates (n=3..89)
Extended linerates (n=90..240)
Note: according to EFM standard, the ratio between the linerates used in one aggregation group shall not exceed 4.
E.g. an aggregation group with 2 lines, one with 192kbps and the other with 768
kbps is ok, but when one line has 192 kbps and the other shall have 1’920 kbps
then it’s not possible.
For details see IEEE802.3-2008 (section 5): 61.2.2.5.
dsl master <pme-a..d/h> <on|off>
Set SHDSL port subtype
on: ieee2BaseTLO (SHDSL master)
off: ieee2BaseTLR (SHDSL slave)
dsl backoff <pme-a..d/h> <on|off>
Enable/disable power backoff on selected PME
9-9
Operating Manual
Version 6.0-00
dsl pairbonding <ghs|bacp>
Set pair bonding mode for all PCS ports
ghs: G.hs-based protocol
bacp: Ethernet frame-based BACP
dsl power <pcs1..4/8> <on|off> [<stages>]
Enable/disable remote power on PMEs aggregated
to the selected PCS and set number of Regenerators on which remote power shall be transferred
(stages=0..2, default 0)
dsl supervision <pcs1..8> <conditions> [<dt> <ct>
<rt>]
Configure the DSL Performance Supervision conditions: sum of following values:
1: SNR margin, 2: Attenuation,
4: Errored seconds
The value 0 disables the supervision.
dt: [10..600]s defect period. Default: 20
ct: [0|10..100000]s clear period.
Default: 20, 0 means infinite period
rt: [60..100000]s recovery timeout.
Default: 120
eth show <eth1..4>
Show Ethernet port configuration
eth adminstatus <eth1..4|mgmt1> <up|down>
Set administrative status of Ethernet and SFP
port
eth autoneg <eth1..4> <on|off>
Set auto negotiation of Ethernet port
eth fdx <eth1..4> <mode>
Set duplex mode and speed of Ethernet port to
<10H|10F|100H|100F|1000H|1000F>
eth flow <eth1..4> <on|off>
Set port's Flow-Control. <on|off> are forced
ip show
9-10
Version 6.0-00
Operating Manual
Show layer 3 configuration
ip addr add <ip-addr>[/<prefix>]
Add <ip-addr> to MGMT1 port prefix: the network
prefix length [bits]
ip addr del <ip-addr>
Delete <ip-addr> from MGMT1 port
ip addr show
Show all configured IP addresses from MGMT1 port
ip dhcp <on|off>
Enable/disable DHCP client
ip route add <net-addr>[/<prefix>] <dest-addr>
Add <net-addr> to routing table
prefix: the network prefix length [bits]
if ommited the prefix is chosen according to the
network class address
dest-addr: route destination address
ip route del <net-addr>[/<prefix>]
Delete <net-addr> from routing table Keyword
'default' can also be specified
prefix: the network prefix length [bits]
if ommited the prefix is chosen according to the
network class address
ip route default <dest-addr>
Set the default gateway
ip route show
Show all configured routes
lag show
Show LAG configuration
lag add <lag> <port>
Add a port to LAG
lag: 1..6
port: eth1..4|pcs1..4/8
9-11
Operating Manual
Version 6.0-00
lag remove <port>
Remove a port from LAG
port: eth1..4|pcs1..4/8
lag mode <lag> <lb|as>
Set LAG mode
lb: load balancing mode
as: active/standby mode
lag prio <port> <0..65535>
Set priority
loam show <eth1..4|pcs1..4/8>
Show all OAM configuration
loam adminstate <eth1..4|pcs1..4/8> <up|down>
Set OAM admin status
loam mode <eth1..4|pcs1..4/8> <passive|active>
Set OAM mode
loam rx_loopback <eth1..4|pcs1..4/8> <process|ignore>
Set OAM RX loopback
loam remote_loopback <eth1..4|pcs1..4/8> <on|off>
Set OAM remote loopback
loam dying_gasp_event <eth1..4|pcs1..4/8> <on|off>
Configure dying gasp event
loam errored_symbol_event <eth1..4|pcs1..4/8>
<on|off> [<window> <threshold>]
Configure OAM errored symbol event
window: number of symbols (64-bit)
threshold: number of symbol errors (64-bit)
default: 1
loam errored_frame_event <eth1..4|pcs1..4/8>
9-12
Version 6.0-00
Operating Manual
Configure OAM errored frame event
window: time period [0.1s]. Default: 10
threshold: number of frame errors default: 1
loam errored_frame_period_event <eth1..4|pcs1..4/8>
Configure OAM errored frame period event
window: number of frames
threshold: number of frame errors
default: 1
loam errored_frame_secs_event <eth1..4|pcs1..4/8>
Configure OAM errored frame secs event
window: time period 100..9000 [0.1s]
default: 100
threshold: number of errored frames 1..900
default: 1
mgmtip
Note: The CLI commands named mgmtip is discontinued and is replaced
starting in FW 3.00.00 with the new name ip . Please refer to the new ip commands instead.
qos show [<core|all|ingress|egress>]
Show QoS configuration
Default: core
qos clfradd <mgmt1|eth1..4|pcs1..4/8> <match> <meter> <green> [<yellow> <cir> <cbs> <eir> <ebs>]
[<green remark> [<yellow remark>]]
Configure classifier and meters
match: VID,CoS ID type,CoS ID values
VID: any | 1..4094
CoS ID type: 802.1p, dscp
CoS ID values: [802.1p] 0..7, [dscp] 0..63
meter: bypass | trtcm | srtcm
green: Queue number 1..8 | drop
yellow: Queue number 1..8
cir: 1-1000000 [kbps]
cbs: 0-1000000000 [bytes]
eir: 0-1000000 [kbps]
ebs: 0-1000000000 [bytes]
green remark: (802.1p) 0..7 | keep
yellow remark: (802.1p) 0..7 | keep
9-13
Operating Manual
Version 6.0-00
qos clfrdel <mgmt1|eth1..4|pcs1..4/8> <match>
Remove classifier and meters
match: VID,CoS ID type,CoS ID values
VID: any | 1..4094
CoS ID type: 802.1p, dscp
CoS ID values: [802.1p] 0..7, [dscp] 0..63
qos esp <profile> <queue> <method> [<weight>]
Configure egress scheduling profiles
profile: 1..8
queue: 1..8
method: wrr | strict
weight: 0..255
qos espselect <mgmt1|eth1..4|pcs1..4/8> <profile>
Select a egress scheduling profile for an interface.
profile: 1..8
qos eshaper <profile> <per> <relative|absolute|
disable> [<rate>]
Configure egress shaper
profile: 1..8
per: port | 1..8, per port or per queue
relative: <rate> is a value relative to the interface speed
absolute: <rate> is an absolute value
rate: 1..999 per mill if relative or
1..1000000 kbps if absolute
setup <ip-addr[/<prefix>]|dhcp> eth1..4 [<vlan-id>
<egress-mode>] [<url>]
Set up management access via one front Ethernet
interface, including IP address and VLAN. Optionally choose the vlan-id and the egress mode
(tagged/untagged, defaults: 4094, untagged).
Optionally pass an URL to the remote configuration to be merged (protocols: FTP, TFTP or
HTTP). The device reboots upon successful configuration merge. If no URL is passed, it is
taken from DHCP if available
9-14
Version 6.0-00
Operating Manual
The setup command allows to easily load a configuration to the device over one
of the Ethernet ports at the front panel. Therefore the IP address for the device
management is specified as well as the used Ethernet port and the VLAN-Id of
the management VLAN (tagged or untagged) that shall be used. Alternatively
dhcp can be selected to load the IP address from a DHCP server. The last parameter allows to specify a local configuration filename or with an URL a configuration file from a remote TFTP storage (or anonymous FTP or HTTP). If DHCP
mode is used and no URL is passed, the URL information is taken from DHCP if
it is provided by the DHCP server.
When the configuration file is loaded the modem reboots automatically. After the
reboot the device will use the Management IP address specified with the setup
command or the one received via DHCP.
Parameters:
IP-Address/
Prefix
IP address and prefix used for the configuration setup.
Use the /nn prefix notation for the network mask,
e.g. 10.100.249.67/16.
dhcp
Activates the DHCP client in the modem to receive the
IP address from a DHCP server.
eth1…4
One of the 4 Ethernet ports from the front panel of the
modem that shall be used for the setup of the configuration file.
vlanId
Defines the VLAN-Id temporarily used for the setup of
the configuration file
Defines if tagged or untagged VLAN traffic is expected
tagged|untagged
URL
Name of a valid configuration file available in a remote
storage as specified by the URL.
e.g. tftp:://192.168.203.1/tftp/efmp/conffiles/bhaul-conf
snmp show
Show SNMP configuration
snmp trapdest add <ip> [p [v [c]]]
Add trap destination IP address using:
port p, version v=[v1,v2], community name c
(default: p=162, v=v1, c=public)
snmp trapdest del <trapid>
Delete a trap destination
soam mode <ieee|y.1731>
Select Service OAM mode
ieee: IEEE 802.1Q CFM
9-15
Operating Manual
Version 6.0-00
y.1731: ITU-T Y.1731
HINT: Service OAM CLI view and command set are
mode dependent
soam show
Show Service OAM configuration
SOAM mode: IEEE
soam mdcreate <level> <format> [name]
Create Maintenance Domain at MD level.
level 0..7
format: charString, none
name is according to format. For format none,
name is ignored.
soam mddel <md no>
Delete MD
<md no> is the MD 'No' field from the command
soam macreate <name> <md no> <vlan id>
Create Maintenance Association <name> on MD <md
no> with primary <vlan id> CCM PDUs are enabled
with 1sec period
soam maccm <ma no> <period>
Set MA CCM mode to one of:
disabled, 1s, 10s, 1min or 10min
soam madel <ma no>
Delete MA
<ma no> is the MA 'No' field from the command
soam mepcreate <mepid> <ma no> <eth1..4|pcs1..4/8>
<vlan id> <up|down>
Create Maintenance End Point with <mepid> in MA
<ma no> with primary <vlan id> and attach it to
specified interface.
soam mepccm <mep no> <on|off>
Enable/disable CCM on MEP
9-16
Version 6.0-00
Operating Manual
soam mepdel <mep no>
Delete MEP
<mep no> is the MEP 'No' field from the command
soam mipcreate <eth1..4|pcs1..4/8> <level> <vlan
id>
Create Maintenance Intermediate Point on primary
<vlan id> and specified interface
<level> 0..7
<vlan id> 1..4094
soam mipdel <mip no>
Delete MIP
<mip no> is the MIP 'No' field from the command
soam rmepadd <mepid> <ma no>
Add remote MEP to MA's MEP list
soam rmeprm <mepid> <ma no>
Remove remote MEP from MA's MEP list
SOAM mode: Y.1731
soam megcreate <icc> <umc> <level> <vlan id>
Create Maintenance Entity Group with primary
<vlan id>
icc: ITU Carrier Code
umc: Unique MEGID Code
CCM PDUs are enabled with 1sec period
soam megccm <meg no> <period>
Set MEG CCM mode to one of: disabled, 1s, 10s,
1min or 10min
soam megdel <meg no>
Delete MEG <meg no> is the MEG 'No' field from
the command 'cm.soam show' result
9-17
Operating Manual
Version 6.0-00
soam mepcreate <mepid> <meg no> <eth1..4|pcs1..4/8>
<vlan id> <up|down>
Create Maintenance End Point with <mepid> in MEG
<meg no> with primary <vlan id> and attach it to
specified interface.
soam mepccm <mep no> <on|off>
Enable/disable CCM on MEP
soam mepdel <mep no>
Delete MEP
<mep no> is the MEP 'No' field from the command
soam mipcreate <eth1..4|pcs1..4/8> <level> <vlan
id>
Create Maintenance Intermediate Point on primary
<vlan id> and specified interface
<level> 0..7
<vlan id> 1..4094
soam mipdel <mip no>
Delete MIP
<mip no> is the MIP 'No' field from the command
soam rmepadd <mepid> <ma no>
Add remote MEP to MA's MEP list
soam rmeprm <mepid> <ma no>
Remove remote MEP from MA's MEP list
stp show
Show RSTP configuration
stp protocol <stp/rstp>
Use STP/RSTP protocol
stp priority <0,4096,..,61440>
Set RSTP Bridge Priority
9-18
Version 6.0-00
Operating Manual
stp hello <1..10>
Set RSTP Hello Time
stp maxage <6..40>
Set RSTP Max Age
stp forward <4..30>
Set RSTP Forward Delay
stp txhold <1..10>
Set RSTP Transmit Hold Count
stp portenabled <eth1..4|pcs1..4/8> <on/off>
Enable/Disable RSTP on port
stp portprio <eth1..4|pcs1..4/8> <0,16,..240>
Set RSTP port priority
stp portcost <eth1..4|pcs1..4/8>
<1..200000000/auto>
Set RSTP port cost
stp portforce <eth1..4|pcs1..4/8>
Force RSTP protocol migration
stp portedge <eth1..4|pcs1..4/8> <on/off>
Define port as edge port
stp portptp <eth1..4|pcs1..4/8> <on/off/auto>
Define port as point-to-point link
vlan show
Show VLAN configuration
vlan create <vid> <"description">
Create VLAN
vid: VLAN-ID (1..4094)
vlan name <vid> <"description">
Set VLAN description.
9-19
Operating Manual
Version 6.0-00
(max length is 32 characters)
vlan frametype <a|t|u> <mgmt1|eth1..4|pcs1..8>
Set acceptable frame types
a: admit all frames
t: admit only tagged frames
u: admit only untagged and priority frames
vlan pprio <0..7> <mgmt1|eth1..4|pcs1..4/8>
Set port default priority. Highest priority corresponds to 7.
vlan pvid <id> <mgmt1|eth1..4|pcs1..4/8>
Set Port VLAN-ID assigned to untagged or priority tagged frames received.
(<id> range is 1..4094)
vlan add <vid> <mgmt1|eth1..4|pcs1..4/8> <t|u>
Add bridge port to VLAN and specify if it should
transmit egress packets as untagged
vlan remove <vid> <mgmt1|eth1..4|pcs1..4/8>
Remove bridge port from VLAN
vlan del <vid>
Delete VLAN
9.5
Security and Remote Management SM
firmware show
Show info about currently installed FW packages
firmware update <url> [<timeout>]
Download a firmware package from a URL, activate
and reboot
Supported protocols: HTTP, TFTP
timeout: 0..3600 [s]; default 60
Start update in background with timeout=0
system inventory
Show system information
9-20
Version 6.0-00
Operating Manual
user show
Show all configured users.
user add <user> [<role>]
Add new user with name <user> and role 'operator' or 'admin'. The default value for role is
'operator'.
user del <user>
Delete user with name <user>.
user password [<username>]
Change the user's password
(default: current user).
vt connect <pme-a..h> [<address>] [<standard|reliable>]
Connect virtual terminal over chosen PME to
remote unit at EOC <address> 2..10
(default 2) using the standard (default)
or a proprietary and reliable EOC protocol.
vt disconnect <pme-a..h>
Disonnect virtual terminal over chosen PME.
vt show
Show active virtual terminals
9-21
Operating Manual
Version 6.0-00
10 Set-up Remote Management Access
and Load Configuration
Remote management access can be through a dedicated Ethernet port or trough
Ethernet inband management, either from an Ethernet user interface or over the
DSL Ethernet payload.
This chapter contains the quick start information necessary to configure the Remote Management Access through a dedicated Ethernet port and shows the usage of configuration files.
MGMT2 2
(Backplane-Controller) .
management
MGMT1 1 [1]
(Bridge-Controller)
.
Controller
192.168.203.41
untagged
ETH1 (Uplink) 3 [2]
ETH2 (Uplink) 4 [3]
ETH3 (Uplink) 5 [4]
ETH4 (Uplink) 6 [5]
10.1
port 24
port 25
port 26
port 27
port 8
SSMII 0
port 11
SSMII 3
port 9
channel 3 12 PME-B (SHDSL)
DSL Processor 1
SSMII 1
channel 1 13 PME-C (SHDSL)
port 10
SSMII 2
channel 2 14 PME-D (SHDSL)
port 0
SSMII 0
channel 0
19 PME-E (SHDSL)
port 3
SSMII 3
20 PME-F (SHDSL)
port 1
channel 3
DSL Processor 2
(8 pair variant only)
SSMII 1
channel 1
port 2
SSMII 2
22 PME-H (SHDSL)
Ethernet
Bridge
channel 0 11 PME-A (SHDSL)
channel 2
21 PME-G (SHDSL)
Enable management access on dedicated Ethernet port
The required steps to enable SNMP management access via a dedicated Ethernet port are:
 Configure the Management IP address
 Configure the Management VLAN
10-22
Version 6.0-00
Operating Manual
We assume here that the EFM Plug-in is in factory default configuration for this
initial setup. Otherwise it’s recommended to reset the Watson EFM Plug-in to the
factory default settings in order to have a well-defined starting point for our configuration:
LTU_1> cm.conffile load factory-default
[...]
Note: Restoring the factory default configuration inevitably reboots the plug-in
and established management access via Ethernet will be disconnected.
Preconditions
 Connect an operator console via serial connection to the device.
Refer to chapter 7 on how to connect an Operator Console to the Watson EFM
Plug-in in order to enter the commands showed in this chapter.
10.2
Use setup command to configure the device
In our example we will set the following IP address:
192.168.203.41
And we will use the VLAN ID (VID) for the management VLAN:
4094
The setup command will configure the involved interface and mark it for transmitting untagged management frames. In our example we use the port Eth1.
LTU_1> setup 192.168.203.41/24 eth1 4094 untagged
[...]
With this we have now configured the IP address and the management VLAN of
the device and have now management access via Ethernet port 1 (eth1).
The next sections describe the usage of a configuration.
10.3
Usage of configuration files
The Watson EFM Plug-in allows to save its current configuration to a configuration file. Either to a local file located in the local flash storage of the device or to a
remote TFTP-file-storage. Such a file can be loaded back to any EFM Plug-in,
which allows us to easily configure the entire configuration of a device simply by
loading a pre-defined configuration file.
For our example we assume the existence of a TFTP-server with address
192.168.203.1 and a configuration file called 8x1auto-noip located on that TFTP
storage.
Precondition

Configure the device as required for your needs (by using CLI commands, the
Watson Element Manager (WEM) or another SNMP management system)
and save this configuration without IP address to a file. The IP address shall
be removed in order to have a configuration file which can be loaded also to
other EFM Plug-ins which uses other IP addresses. To remove the IP address, use the command: cm.ip addr del <ip-addr> and then save the
10-23
Operating Manual
Version 6.0-00
configuration. To save the configuration, use the command: cm.conffile
save <name|url> (see also chapter 10.5).
Note: Make sure that the TFTP- and the NMS- server is setup and configured in
your network and that the Watson EFM Plug-in has network access to it. In case
the device and the servers are located in different networks the default gateway
has to be set accordingly (e.g. ip route default 192.168.203.1).
Use the following command to set the required management access via Ethernet
and to load the predefined configuration file 8x1auto-noip. In this example it is
located on a remote TFTP file storage 192.168.203.1/tftp-storage/conffiles/.:
LTU_1> setup 192.168.203.41/24 eth1 4094 untagged \
tftp://192.168.203.1/tftp-storage/conffiles/8x1auto-noip
[...]
In case a configuration file is used which contains also an IP address, then this
address will be added to the IP address set by the setup command and you will
have to remove the IP address if not needed (after the modem has finished the
reboot).
10.4
Use setup command with DHCP to Configure Device
The Watson EFM Plug-in implements a DHCP client which allows to set the IP
address of the device automatically via the DHCP protocol.
Use the setup command with the DHCP option as follows:
LTU_1> setup dhcp eth1 4094 untagged \
tftp://192.168.203.1/tftp-storage/conffiles/8x1auto-noip
[...]
In order to use the DHCP based configuration you have to make sure that a
DHCP server is setup and configured in your network and that the Watson EFM
Plug-in has network access to it.
The Watson EFM Plug-in does also support to receive the information about the
TFTP server directly from the DHCP server. If the DHCP server supports this
“TFTP path indication” and if it is configured accordingly the command. setup
dhcp eth1 4094 untagged would be sufficient to get the TFTP path from the
DHCP server and then load that file from TFTP storage.
10.5
Loading Configuration Files
There are two ways how a configuration file can be loaded:
 cm.conffile load <filename>
 cm.conffile merge <filename>
10-24
Version 6.0-00
Operating Manual
Whereas conffile load will replace the current modem configuration entirely,
conffile merge will only change the values that are defined in the conffile but
will leave all other values of the current configuration untouched.
To get a ‘mergable’ conffile without an IP address value, you can use the command: cm.ip addr del <ip-addr> to remove the IP address from your configuration and then save the configuration, e.g. cm.conffile save 8x1autonoip. Such a conffile with no IP address can then be used on several modems.
The dedicated IP address for each modem can then be set either via the setup
or the ip command or via DHCP.
By using a ‘mergable’ conffile without an IP address value you can keep the IP
address already set for a Watson EFM Plug-in and merge the configuration settings from a configuration file without modifying the IP address of the device.
10-25
Operating Manual
11
Version 6.0-00
Supported SNMP MIBs
The Watson EFM Plug-in is fully manageable trough SNMP. The SNMP messages are received according to the SNMP communication configured for the modem
(see chapter 8.1 for more details).
Standardized Management Information Bases (MIBs) are used to represent the
managed objects of the Watson EFM Plug-in, its interfaces, the DSL spans, the
Ethernet bridging functions etc.
This chapter contains an overview of the supported SNMP MIBs. Please refer to
[1] and to the Watson EFM Plug-in MIBs for more detailed information of the supported objects.
Unless otherwise noted the variables are available in the public context for
read access and private context for write access.
11.1
MIB Reference
The management information of the Watson EFM Plug-in is modeled according
to standardized MIBs. Additionally two vendor-specific MIBs are supported: the
WATSON-MIB and SCHMID-MIB.
11.1.1
MIB II (RFC 1213)
The Watson EFM Plug-in provides functionality under the following MIB-II groups:
 system: SNMPv2-MIB
 snmp: SNMPv2-MIB
 interfaces: IF-MIB
 ip: IP-FORWARD-MIB
11.1.2
SNMPv2-MIB (RFC 3418)
Defines a list of objects that pertain to system operation, such as the system uptime, system contact, and system name.
Measures the performance of the underlying SNMP implementation on the managed entity and tracks things such as the number of SNMP packets sent and received.
11-26
Version 6.0-00
11.1.3
Operating Manual
IF-MIB (RFC 2863)
Keeps track of the status of each interface on a managed entity. Provides information about which interfaces are up or down and tracks such things as octets
sent and received, errors and discards, etc. Controls Aggregation of SHDSL wirepairs.
11.1.4
IF-INVERTED-STACK-MIB (RFC 2863)
Provides the inverse mapping of the SHDSL Aggregation Configuration of the IFMIB.
11.1.5
IP-MIB (RFC 4293)
Used to configure the Watson EFM Plug-in remote management access (IP address part).
11.1.6
IP-FORWARD-MIB (RFC 4292)
Used to configure the Watson EFM Plug-in remote management access (gateway configuration).
11.1.7
EtherLike-MIB (RFC 3635)
Used to configure flow control of the Ethernet interfaces (PAUSE frames).
11.1.8
MAU-MIB (RFC 4836)
Controls and monitor speed/duplex mode of the Ethernet interfaces and Auto negotiation.
11.1.9
ENTITY-MIB (RFC 4133)
Provides Watson EFM Plug-in related information including hardware and firmware versions, serial numbers etc.
11.1.10
DOT3-OAM-MIB (RFC 4878)
Used to configure and monitor link operation such as remote fault indication and
remote loopback control.
11.1.11
EFM-CU-MIB (RFC 5066)
Configure and monitor SHDSL lines (e.g. linerates) and monitor pair aggregation
functionality. Aggregation itself is controlled by the IF-MIB and IF-INVERTEDSTACK-MIB.
11.1.12
IEEE8021-BRIDGE-MIB (part of IEEE802.1Q)
Control the bridge type (D-Bridge or Q-Bridge). Derived from IETF BRIDGE-MIB
(RFC 4188).
11-27
Operating Manual
11.1.13
Version 6.0-00
IEEE8021-Q-BRIDGE-MIB (part of IEEE802.1Q)
Controls the VLAN functions of the Ethernet bridge of the Watson EFM Plug-in.
11.1.14
IEEE8021-SPANNING-TREE-MIB
This MIB module defines a collection of objects for managing the RSTP functionality according IEEE 802.1Q.
11.1.15
RMON-MIB
The RMON-MIB provides support for traffic monitoring.
11.1.16
HDSL2-SHDSL-LINE-MIB (RFC 4319)
This MIB module
HDSL2/SHDSL lines.
11.1.17
defines
a
collection
of
objects
for
managing
DIFFSERV-MIB (RFC 2475)
This MIB defines the objects necessary to manage a device that
uses the Differentiated Services Architecture described in RFC 2475.
11.1.18
ARICENT-ECFM-MI-MIB
ECFM MIB with multiple instance capability.
11.1.19
ARICENT-ECFM-Y1731-MI-MIB
The Proprietary MIB for Aricent ECFM-Y1731 module with multiple
instance capability.
11.1.20
SNMP-TARGET-MIB (RFC 3413)
This MIB module defines MIB objects which provide mechanisms to remotely
configure the parameters used by an SNMP entity for the generation of SNMP
messages.
11.1.21
SNMP-NOTIFICATION-MIB (RFC 3413)
This MIB module defines MIB objects which provide mechanisms to remotely
configure the parameters used by an SNMP entity for the generation of notifications.
11.1.22
IEEE8021-PB-MIB
Controls the Provider Bridge VLAN functions of the Ethernet bridge of the Watson
EFM Plug-in.
11.1.23
IEEE8021-CFM-MIB and IEEE8021-CFM-V2-MIB
Connectivity Fault Management module for managing IEEE 802.1ag.
11-28
Version 6.0-00
11.1.24
Operating Manual
WATSON-MIB
Provides vendor-specific data structures for Watson EFM Plug-in modems like
e.g. firmware update, network entity maintenance status, rebooting control, reading the state of front panel LEDs and backplane relays.
11.1.25
SCHMID-MIB
The Schmid MIB contains vendor-specific hardware identifiers (called the model
codes) for Schmid DSL modems.
The model code is provided by SNMPv2-MIB::sysObjectID by ENTITY-MIB::
entPhysicalVendorType.
11-29
Operating Manual
12
12.1
Front Panels
Front Panel
Figure 12-1a: Front panel SZ.868.V654
12-30
Version 6.0-00
Figure 12-2b: Front panel SZ.868.V854
Version 6.0-00
Operating Manual
13
Connectors and Cables
13.1
13.1.1
DSL Interface
Connector
Connector Type RJ45-8
....
1
8
Front View
Figure 13-1: DSL Connector
The connector pin assignment is as shown below:
Pin
Signal
Description
1
d1
Wire pair d, tip
2
d2
Wire pair d, ring
3
b1
Wire pair b, tip
4
a1
Wire pair a, tip
5
a2
Wire pair a, ring
6
b2
Wire pair b, ring
7
c1
Wire pair c, tip
8
c2
Wire pair c, ring
Table 13-1: DSL connector pin assignment
13-31
Operating Manual
13.2
Version 6.0-00
Ethernet Interface
1
....
8
Type: RJ45-8 (Front View)
Figure 13-2: Ethernet 1000base-T Connector
Pin No
Signal Name
Description
1
BI_DA +
Bi-directional pair A+ (transmit)
2
BI_DA -
Bi-directional pair A- (transmit)
3
BI_DB +
Bi-directional pair B+ (receive)
4
BI_DC +
Bi-directional pair C+
5
BI_DC -
Bi-directional pair C -
6
BI_DB -
Bi-directional pair B – (receive)
7
BI_DD +
Bi-directional pair D+
8
BI_DD -
Bi-directional pair D -
Table 13-2: Ethernet 1000base-T Connector
13.3
Regenerator Connector
The regenerator has one DIN-C/2 type male connector:
2a
Tip REG C, Loop B
2c
Ring REG C, Loop B
4a
Tip REG C, Loop A
4c
Ring REG C, Loop A
6a
n.c.
6c
n.c.
8a
Local Power positive
8c
Local Power positive
10a
Local Power negative
10c
Local Power negative
12a
n.c.
12c
n.c.
14a
Tip REG R, Loop B
14c
Ring REG R, Loop B
16a
Tip REG R, Loop A
16c
Ring REG R, Loop A
n.c. = not connected
13-32
14
Technical Specifications
14.1
Interfaces
14.1.1
DSL Line Interface
Standard referred:
ETSI TS 101 524 V1.4.1 (2006-02),
ITU-T G.991.2 Annex B/G (Revision 2005) (G.SHDSL.bis)
IEEE 802.3 2008 clause 57 (EFM 2Base-TL)
Number of Pairs:
Up to 4 (SZ.868.V654) or up to 8 (SZ.868.V854)
Standard Line Rate per
Pair:
192 – 5696 kbit/s
Extended Line Rate per
pair:
5760 kbit/s – 15360 kbit/s
Line Code:
Trellis-coded PAM-16, PAM-32, PAM-64, PAM-128
DSL Clock mode:
3a
Nominal Line Impedance:
135
Transmit Power @ 135:
According to ETSI TS 101 524
Protection:
ITU-T K.20 (basic level)
Connector Type:
RJ-45, 8 pin,
(1x RJ-45 for SZ.868.V654, 2x RJ-45 for SZ.868.V854)
OvOvervoltage Protection:
PluPlug-in: ITU-T K.20 basic level (enhanced level with
external protection)
Regenerator: ITU-T K.45 basic level
Wetting current
14.1.2
1.8 mA @ 48VDC per pair (two Plug-ins connected with 0
Ohm loop resistance)
Ethernet Interfaces
Standard referred:
1000base-T IEEE 802.3ab
Crossover
Auto-Crossover
Bitrates
10/100/1000 Mbps (Auto-negotiation)
Duplex Mode
Half/Full Duplex (Auto-negotiation)
Flow control
PAUSE Frames (full duplex)
Backpressure (half duplex)
14-1
14.1.3
14.1.4
14.1.5
Serial Interface
Signal Level:
RS-232
Data Rate:
9600 Baud, Asynchronous
Protocol:
8 Bit, No Parity, 1 Stop Bit
No Linefeed with Carriage Return
XON/XOFF enabled
Connector Type:
SubD9 female
Internal clock
Frequency
2'048 kHz  32 ppm
Jitter
< 8 ns
Clock Interface
2048 kHz clocking OUT.
14.2
Power Consumption
14.2.1
Plug-in
Notes
14.2.2
14.3
14-2
Supply Voltage:
-40.5VDC .. -72VDC
Power Consumption:
Max 16 W
The power consumption value above are measured without remote powering. If
remote powering is used then the power consumption increases by 7 W per
powered pair.
Regenerator
Local power supply
60 VDC .. 115 VDC , 5W
Power consumption
3.0 W
Ethernet
Maximum Frame Size
2'047 bytes
Number of MAC addresses
16'384
Number of address databases
4094
Number of VLANs
4094
Version 6.0-00
Frame buffer size
14.4
Operating Manual
12 Mbit shared between all
queues
Management Functions
Management Protocols
SNMPv1 (RFC 1157), SNMPv2c (RFC 1901, 1908)
Secure Shell (SSH), HTTP
Management transport
IPv4 and IPv6
Supported MIBs
MIB II (RFC 1213)
SNMPv2-MIB (RFC 3418)
IEEE8023-LAG-MIB
IF-MIB (RFC 2863)
IF-INVERTED-STACK-MIB (RFC 2863)
IP-MIB (RFC 4293)
IP-FORWARD-MIB (RFC 4292)
EtherLike-MIB (RFC 3635)
MAU-MIB (RFC 4836)
ENTITY-MIB (RFC 4133)
DOT3-OAM-MIB (RFC 4878)
EFM-CU-MIB (RFC 5066)
IEEE8021-BRIDGE-MIB (part of IEEE802.1Q)
IEEE8021-Q-BRIDGE-MIB (part of IEEE802.1Q)
IEEE8021-PB-MIB
IEEE8021-SPANNING-TREE-MIB
RMON-MIB
HDSL2-SHDSL-LINE-MIB (RFC 4319)
DIFFSERV-MIB (RFC 2475)
ARICENT-ECFM-MI-MIB
ARICENT-ECFM-Y1731-MI-MIB
SNMP-TARGET-MIB (RFC 3413)
SNMP-NOTIFICATION-MIB (RFC 3413)
IEEE8021-CFM-MIB
IEEE8021-CFM-V2-MIB
WATSON-MIB
SCHMID-MIB
Firmware Upgrade
TFTP (RFC 783), HTTP
14-3
14.5
Environment
14.5.1
Climatic Conditions
14.5.2
Storage:
ETS 300 019-1-1 Class 1.2
-25C … +55C, 10% .. 100% RH
Transportation:
ETS 300 019-1-2 Class 2.3
-40C … +70C, max. 95% RH
Operation:
ETS 300 019-1-3 Class 3.1
-5C … +45C, 5% .. 95% RH
Safety
According to EN 60950:2006 (IEC60950:2005)
14.5.3
EMC
According to EN 300386 V1.5.1 (2010-10)
14.6
Physical dimensions and weight
14.6.1
Plug-in
19” Plug-in unit: height: 259mm (6 HE), width: 30mm
PCB dimensions: height: 233.35mm, length: 220mm
Weight: SZ.868.V854.WNA  500g
SZ.868.V654.WNA  411g
14.6.2
Regenerator
Width 105 mm, depth 154 mm, height 27 mm
Weight 350g
14-4
Version 6.0-00
Operating Manual
15 Terminology
Throughout this document the following terminology is used:
Term
Meaning
CoS
Class of Service
DSL Linerate
Data rate of a DSL span available to the application
DSL Master
Synonymous for STU-C
DSL Payload rate
Synonymous to DSL Linerate
DSL Slave
Synonymous for STU-R
DSL Span
Connection between STU-C and STU-R, composed of one or
more wire pairs.
DSL Sync rate
Physical synchronization rate of a DSL wire pair
EFM
Ethernet in the First Mile
EMS
Element Management System
EOC
Embedded Operations Channel, an overhead channel available in
SHDSL for management purposes
Linerate
cf. DSL Linerate
LTU
Line Termination Unit, functionally equivalent to STU-C
NMS
Network Management System
NTU
Network Termination Unit, functionally equivalent to STU-R
Payload rate
Synonymous to linerate
PAF
PME Aggregation Function
PCS
Physical Coding Sublayer
PME
Physical Medium Entities
STU-C
Synchronous Terminal Unit – Central Office Side. The end of a
DSL span that starts up and controls the link. Typically installed at
the central office
STU-R
Synchronous Terminal Unit – Remote Side. The end of a DSL
span that is controlled by the STU-C. Typically installed at the customer premises
Sync rate
Cf. DSL Sync rate
VID
Virtual LAN Identifier, a.k.a "VLAN Number". The unique identifier
of a VLAN. Carried in the VLAN Tag of an Ethernet frame.
VLAN
Virtual LAN (IEEE 802.1q)
15-5
16
16.1
Product Order Codes
Modems
The following Watson EFM Plug-in modems are available:
Description
Order Code
Watson EFM Plug-in 4xDSL 4xEthernet
SZ.868.V654
Watson EFM Plug-in 8xDSL 4xEthernet
SZ.868.V854
Table 16-1: Watson EFM Plug-in order codes
16.2
Accessories
The following accessories for the Watson EFM Plug-in modems are available:
Description
Order Code
SZ.856.V320
19" Subrack for WATSON HDSL (for 12 plug-in + 1 ACU/SCU) SZ.379.V3
Alarm Control Unit (2 Relays) with ext. Clock, for 19" Subrack
SZ.369.V5
Watson Subrack Control Unit
SZ.366.V350
19" Minirack Mechanics for Plug In 2xDC Power
SZ.876.V200
19" Minirack Mechanics for Plug In AC & 2xDC Power
SZ.876.V201
Tabletop Housing for Watson Plug-in DC Powering
SZ.875.V100
Tabletop housing for Watson Plug In AC + DC Power
SZ.875.V110
Watson Element Manager - WEM 2.x
SZ.366.V7xx
Table 16-2: Accessories for plug-in
16-1

Watson SHDSL EFM Plug-in Operating Manual

Transcription

Similar documents

Tech Forum - Episerver

Contents - February 2002

A New Strategy To Bring Advanced Technology

Measurement and Automation Systems

Curriculum Vitae Claire M. Vanston PhD

group test photoshop cs3 plug-ins

JDSU HST-3000 - Ibis Instruments

Track Busway - Core Power, Inc.

Kid Racer School Teaches Them Young