Siemens Dslam user manual hiX 5625/30/35

SURPASS hiX 5625/30/35 R2.8Commission

IP-DSLAM

2

Commission

Id:0900d8058025d977

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMEN-TATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright Nokia Siemens Networks 2008. All rights reserved.

f Important Notice on Product SafetyElevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangslufig bestimmte Teile der Gerte unter Span-nung. Einige Teile knnen auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverlet-zungen und Sachschden fhren.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Gerte mssen die zutreffenden Sicherheitsbestimmungen erfllen.

3

Commission

Id:0900d8058025d977

Table of ContentsThis document has 95 pages.

Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.1 Scope of the ITMN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.2 Error Reports Concerning the Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.3 Dealing with Defective Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.4 Procedure in the Event of Faults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.5 Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2 Protective Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.1 General Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.2 Protection Against Excessive Contact Voltage . . . . . . . . . . . . . . . . . . . . . . 132.3 Protection Against Escaping Laser Light . . . . . . . . . . . . . . . . . . . . . . . . . . 142.4 Protection Against Fire in Racks or Housings. . . . . . . . . . . . . . . . . . . . . . . 152.5 Protection Against Hot Surfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.6 Components Subject to Electrostatic Discharge. . . . . . . . . . . . . . . . . . . . . 152.7 Handling Modules (General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.8 Handling Optical Fiber Connectors and Cables . . . . . . . . . . . . . . . . . . . . . 172.9 Virus Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.10 RoHS Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.11 Declaration of CE Conformity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.12 WEEE Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3 General Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.1 Visual Inspection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.2 Plan of Activities for Commissioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4 Configuring the FTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224.1 Windows FTP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224.2 Solaris FTP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

5 Startup the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295.2 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295.3 Load the Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

6 Slot Numbering on the hiX 5625/30/35 Shelves and Plug-in Units. . . . . . . 346.1 M1200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346.2 M1100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356.3 G1100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366.4 M600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376.5 G600/G600R. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386.6 M400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396.7 G400/G400R. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

7 Commissioning the Network Element HiX 5625/30/35 . . . . . . . . . . . . . . . . 417.1 Insert the Network Element. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417.2 Synchronize Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

4

Commission

Id:0900d8058025d977

7.3 Configure the FTP User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447.4 Synchronize the Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467.5 Configure Transmission Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467.6 Saving the NE Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477.7 Configure Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477.7.1 Configure CXU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477.7.2 Preparing System for Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497.7.3 Configure CXU Ethernet Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507.7.4 Create Interface Unit Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517.7.5 Reset of an Interface Unit Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527.7.6 Configure Interface Unit Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537.8 Configure Bridges and VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537.8.1 Configure Bridge Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537.8.2 Configure VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557.8.3 Configure IGMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567.8.3.1 IGMP Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567.8.3.2 IGMP Multicast Groups and Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587.8.4 Configure UMAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617.8.5 Configure QOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617.8.6 Configure MSTP/ERP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627.8.6.1 CIST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627.8.6.2 ERP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637.8.6.3 MSTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647.8.7 Configure DHCP and PPPoE Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667.8.7.1 Configuring of CXU Modes and ID Format . . . . . . . . . . . . . . . . . . . . . . . . . 667.8.7.2 DHCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677.8.7.3 Simplified DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687.8.7.4 PPPoE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697.9 Configure Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707.9.1 Configure ADSL Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707.9.2 Configure ADSL RFI Band Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717.9.3 Configure ADSL Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727.9.4 Configure Priority Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737.9.5 Configure Shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747.9.6 Configure TPID to VLAN Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757.9.7 Configure SHDSL Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767.9.8 Configure SHDSL Span . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777.9.9 Configure xDSL Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777.9.10 Configure xDSL Custom Notch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797.9.11 Configure xDSL Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807.9.12 Configure xDSL Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817.9.13 Configure xDSL PSD Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847.9.14 Configure Alarm Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857.9.15 Configure Metering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867.10 Configure Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867.10.1 Configure ADSL- and XDSL-Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867.10.2 Configure SHDSL-Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

5

Commission

Id:0900d8058025d977

7.11 Lock / Unlock Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917.12 Database Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

8 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

6

Commission

Id:0900d8058025d977

List of FiguresFigure 1 Power Rating Label. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Figure 2 High Leakage Current. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Figure 3 Warning Label According to IEC 60825/EN 60825. . . . . . . . . . . . . . . . . 14Figure 4 Warning Label for Class 1 Laser Equipment . . . . . . . . . . . . . . . . . . . . . 14Figure 5 Symbol Label for Hot Surfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 6 Text on Label for Hot Surfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 7 ESD Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 8 Prohibition Label According to DIN 4844-2. . . . . . . . . . . . . . . . . . . . . . . 16Figure 9 Defining a New User (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Figure 10 Defining the Password (Example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Figure 11 Assigning User Rights (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Figure 12 Dialog Security Policy Setting (Example) . . . . . . . . . . . . . . . . . . . . . . . 24Figure 13 Dialog Internet Information Services (Example) . . . . . . . . . . . . . . . . . . 25Figure 14 FTP Site Tab (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Figure 15 Home Directory Tab (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Figure 16 Change the Access to "ftproot" (Example) . . . . . . . . . . . . . . . . . . . . . . . 28Figure 17 CXU RJ45 Connector for the Console Interface . . . . . . . . . . . . . . . . . . . 29Figure 18 Console Cable for the HyperTerminal. . . . . . . . . . . . . . . . . . . . . . . . . . . 29Figure 19 Dialog hiX - HyperTerminal (Example SNMP V2 for Outband) . . . . . . 30Figure 20 Dialog hiX - HyperTerminal (Example SNMP V2 for Inband) . . . . . . . . 31Figure 21 NE Maintenance Window(Example). . . . . . . . . . . . . . . . . . . . . . . . . . . 33Figure 22 Inserting an SNMP Network Element (Example) . . . . . . . . . . . . . . . . . . 41Figure 23 SNMP Settings Tab (Example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Figure 24 SNMP Authorization Tab (Example). . . . . . . . . . . . . . . . . . . . . . . . . . . 42Figure 25 Network View (Example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Figure 26 Date/Time Tab (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Figure 27 FTP Server Tab (Example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Figure 28 Clock Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Figure 29 Configuration Tab (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Figure 30 General Tab of CXU (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Figure 31 Status Tab of CXU (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Figure 32 Protection Tab (Example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Figure 33 Ethernet Port Tab of CXU (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . 50Figure 34 BCSC Tab of CXU (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Figure 35 NE - Bridge (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Figure 36 Bridge Port (Example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Figure 37 Overview Tab of VLAN (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Figure 38 VLAN Assignment (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Figure 39 IGMP Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Figure 40 General Tab of IGMP(Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Figure 41 Groups Tab of IGMP (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Figure 42 UMAS Tab of Bridge (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Figure 43 QoS Configuration (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Figure 44 CIST Tab of MSTP/ERP (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Figure 45 ERP Tab of MSTP/ERP (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

7

Commission

Id:0900d8058025d977

Figure 46 MSTP Tab of MSTP/ERP (Example). . . . . . . . . . . . . . . . . . . . . . . . . . 65Figure 47 MST Instance Tab of MSTP (Example). . . . . . . . . . . . . . . . . . . . . . . . 65Figure 48 DHCP/PPPoE Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Figure 49 DHCP Tab of Provider (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Figure 50 Simplified DHCP Tab of Provider (Example). . . . . . . . . . . . . . . . . . . . 69Figure 51 PPPoE Tab of Provider (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Figure 52 New ADSL Event Profile (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . 71Figure 53 New ADSL RFI Band Mask Profile (Example). . . . . . . . . . . . . . . . . . . 72Figure 54 ADSL Line Tab of Profiles (Example) . . . . . . . . . . . . . . . . . . . . . . . . . 73Figure 55 Priority Mapping Tab of Profiles (Example) . . . . . . . . . . . . . . . . . . . . . 74Figure 56 Shaping Tab of Profiles (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Figure 57 TPID to VLAN Mapping Tab of Profiles (Example) . . . . . . . . . . . . . . . 76Figure 58 SHDSL Event Tab of Profiles (Example). . . . . . . . . . . . . . . . . . . . . . . 76Figure 59 SHDSL Span Tab of Profiles (Example) . . . . . . . . . . . . . . . . . . . . . . . 77Figure 60 xDSL Channel Tab of Profiles (Example) . . . . . . . . . . . . . . . . . . . . . . 78Figure 61 xDSL Event Tab of Profiles (Example) . . . . . . . . . . . . . . . . . . . . . . . . 80Figure 62 xDSL Line Tab of Profiles (Example) . . . . . . . . . . . . . . . . . . . . . . . . . 81Figure 63 xDSL Extention Tab of Profiles (Example) . . . . . . . . . . . . . . . . . . . . . 84Figure 64 xDSL PSD Mask Tab of Profiles (Example) . . . . . . . . . . . . . . . . . . . . 85Figure 65 XDSL Port, Line Tab Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Figure 66 ADSL - PVC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Figure 67 SHDSL Port Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Figure 68 Database Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Figure 69 Backup Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

8

Commission

Id:0900d8058025d977

List of TablesTable 1 Overview of Chapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Table 2 Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Table 3 Sequence for Commissioning the NE hiX 5625/30/35 . . . . . . . . . . . . . . 21Table 4 M1200 Slot Numbering and Plug-in Units . . . . . . . . . . . . . . . . . . . . . . . 34Table 5 M1100 Slot Numbering and Plug-in Units . . . . . . . . . . . . . . . . . . . . . . . 35Table 6 G1100 Slot Numbering and Plug-in Units . . . . . . . . . . . . . . . . . . . . . . . 36Table 7 M600 Slot Numbering and Plug-in Units . . . . . . . . . . . . . . . . . . . . . . . . 37Table 8 G600/G600R Slot Numbering and Plug-in Units . . . . . . . . . . . . . . . . . . 38Table 9 M400 Slot Numbering and Plug-in Units . . . . . . . . . . . . . . . . . . . . . . . . 39Table 10 G400/G400R Slot Numbering and Plug-in Units . . . . . . . . . . . . . . . . . . 40Table 11 SNMP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Table 12 Settings for the FTP Server Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Table 13 Settings for the Clock sync tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Table 14 Settings of CXU Ethernet Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Table 15 Interfaces Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Table 16 Tagging Modes of the Bridge Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Table 17 Set up of IGMP Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Table 18 Settings for the Groups Tab of IGMP . . . . . . . . . . . . . . . . . . . . . . . . . 60Table 19 DHCP/PPPoE Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Table 20 DHCP Suboptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Table 21 Shaping Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Table 22 Settings for New xDSL Channel Profile . . . . . . . . . . . . . . . . . . . . . . . . 79Table 23 XDSL Custom Notch Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Table 24 XDSL Line Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Table 25 XDSL Line Profile - Expert Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Table 26 Settings XDSL Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Table 27 PVC Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Table 28 Settings SHDSL Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

9

Commission Change History

Id:0900d8058025dba1

Change History1. Update (10.12.2008)

Commissioning the Network Element HiX 5625/30/35 (7) Changes for configuring xDSL profiles

Initial release (28.11.2008)

10

Commission

Id:0900d8058025dba1

Change History

11

Commission Introduction

Id:0900d8058025ddc8

1 IntroductionThe ITMN describes in detail the required steps for commissioning SURPASS hiX 5625/30/35 R2.8. The name of the corresponding network element is hiX 5625/30/35 R2.8.It contains the following sections:

Table 1 briefly describes the structure of this document.

This section gives information in general about the manual and the handling with error reports. It contains the following subsections: Scope of the ITMN Error Reports Concerning the Manual Dealing with Defective Modules Procedure in the Event of Faults Typographical Conventions Protective Measures CE Declaration of Conformity

1.1 Scope of the ITMNThe Installation and Test Manual (ITMN) explains the commissioning procedures for the hiX 5625/30/35 R2.8 network element (NE) including the following information: Commissioning procedures for NEs or parts thereof Settings for configuring interfaces.

1.2 Error Reports Concerning the Manual Full details of any incorrect or unclear sections of the ITMN should be described in detail in a document as error report (in the Helpdesk).

Chapter Description

1 Introduction There are information about commissioning in general.

3 General Requirements Gives an overview about first steps and contains a check list of visual inspection handlings.

4 Configuring the FTP Server Describes the configuration of the FTP server.

5 Startup the System Describes the startup procedure and the loading of the software.

6 Slot Numbering on the hiX 5625/30/35 Shelves and Plug-in Units

Gives an overview about the plug-in units and their mnemo-code and slot numbers.

7 Commissioning the Network Element HiX 5625/30/35

Describes the commissioning of the network element hiX 5625/30/35 R2.8.

Table 1 Overview of Chapters

12

Commission

Id:0900d8058025ddc8

Introduction

1.3 Dealing with Defective Modules If a module is defective, it should be carefully re-packed and returned to the repair center along with the correct documentation.For details, please contact the repair-service.

1.4 Procedure in the Event of FaultsFaults occurring during on-line operation should have been identified and rectified in accordance with the instructions given in the Branch to Maintenance, see system description (SYD) or maintenance manual (MMN).If this is not possible, an error report is to be created in the Helpdesk and is to include the following detailed information: Description of the test step attempted Detailed list of the preceding operating and configuration actions at hiX 5625/30/35

and at other components in the network Description of the system response Description of any system activities taking place at the same time, such as work

being done by other testers while hardware and software changes are being made.

1.5 Typographical ConventionsIn all sections of this manual, the following conventions are applied:

Style of Representation Meaning

Courier Inputs and outputsExample: Enter LOCAL as the server nameCommand not found

Italics VariablesExample: name can be up to eight letters long.

Italics Variables fin procedures and title basExample:General NE Parameter. -CXU#...

Boldface Special emphasisExample: This name may not be deleted

Quotation marks Labels on the user interface (e.g. windows, menu items, buttons)Example: Activate the OK buttonMake a selection in the File menu.

Key combinationsExample: +

Successive menu itemsExample: File Close

Additional items of information

Warnings at critical points in the activity sequence

Table 2 Typographical Conventions

J

13

Commission Protective Measures

Id:0900d80580241489

2 Protective Measures

2.1 General NotesThis Section contains requirements with regard to protection of people, equipment and environment.All assembly, installation, operation and repair work may only be undertaken by service personnel.In the event of any injury (e.g. burns and acid burns) being sustained, seek medical help immediately. Generally, to avoid danger, the operator is instructed to read the desig-nated manual before beginning e.g. a maintenance task.

This section includes the following topics: General Notes Protection Against Excessive Contact Voltage Protection Against Escaping Laser Light Protection Against Fire in Racks or Housings Protection Against Hot Surfaces Components Subject to Electrostatic Discharge Handling Modules (General) Handling Optical Fiber Connectors and Cables Virus Protection RoHS Requirements Declaration of CE Conformity WEEE Requirements.

2.2 Protection Against Excessive Contact VoltageWhen dealing with the power supply, observe the safety measures described in the specifications of the European Norm EN 50110, Part 1 and Part 2 (operation of electrical installations) and the valid applicable national standards as VDE 0105 (operation of high-voltage equipment) Part 1, Section 9.3 (safety measures to be carried out) at all times. Be sure to follow local national regulations regarding the handling of high-voltage equipment.Figure 1 shows the label on the subrack with information on the subrack power supply (limits for battery voltage and load current). ** Numerical values for load current. Check the power rating label for the actual value.

!The system can have several power supplies. Note that to switch off the power supply completely, you also have to switch off the redundant power supply. Switch off all con-cerned devices!

!Please pay attention also to the high leakage current.A ground connection is essential before connecting the system to the telecommunica-tion network.

14

Commission

Id:0900d80580241489

Protective Measures

g In ANSI applications only 48 V is permitted!

Figure 1 Power Rating Label

Figure 2 shows the label on the front side of the subrack with information that a high leakage current can occur if the shelf is not grounded.

Figure 2 High Leakage Current

2.3 Protection Against Escaping Laser LightIn order to avoid health risks, take care to ensure that any laser light escaping is not directed towards the eyes. Plug-in units equipped with laser light units may carry the laser symbol, but it is not required, see Figure 3. For operation in closed systems the laser light units comply with Laser class 1. Such units can be identified by an adhesive label as well as by a warning label, see Figure 4.

Figure 3 Warning Label According to IEC 60825/EN 60825

Figure 4 Warning Label for Class 1 Laser Equipment

!

Never look directly into the beam, not even with optical instruments.

15


Id:0900d80580241489

2.4 Protection Against Fire in Racks or HousingsIf shelves are used in housing, the shelves must comply with the conditions for fire pro-tection housing according to DIN EN 60950-1.To comply with fire protection standards as defined in DIN EN 60950-1, a protective plate (C42165-A320-C684) must be fitted into the floor of ETSI and 19-inch standard racks. The rack must also meet the requirements of fire-resistant housing as defined in DIN EN 60950-1.

2.5 Protection Against Hot SurfacesIf temperatures higher than 70C can be present on components inside the transmission equipment, following labels are attached to this equipment, see Figure 5 and Figure 6.

Figure 5 Symbol Label for Hot Surfaces

Figure 6 Text on Label for Hot Surfaces

2.6 Components Subject to Electrostatic Discharge

Figure 7 ESD Symbol

!

Plug-in units bearing the symbol shown in Figure 7, are equipped with components subject to electrostatic discharge (ESD). Adhere to the relevant safety provisions.

16

Commission

Id:0900d80580241489

Protective Measures

When packing, unpacking, touching, pulling out, or plugging in plug-in units bearing the ESD symbol, it is essential to wear a grounding bracelet. This ensures that the plug-in units are not subject to electrostatic discharge.Under no circumstances should you touch the printed conductors or components of plug-in units. Take hold of plug-in units by the edge only.Once removed, place the plug-in units in the conductive plastic sleeves intended for them. Keep or dispatch them in the special boxes or transport cases bearing the ESD symbol.Treat defective plug-in units with the same degree of care as new ones in order to avoid further damage.Plug-in units in a closed and intact housing are protected in any case.European Norm EN 50082-1 provides information on the proper handling of compo-nents which are subject to electrostatic discharge.

2.7 Handling Modules (General)To pull out or plug in plug-in units, use the front-mounted levers.In shelters fans are used for cooling. To indicate positions where there is a danger of being caught up in a fan, following label is attached, see Figure 8.

Figure 8 Prohibition Label According to DIN 4844-2

When working with modules (plug-in units, subracks and shelters) the following points should be noted: Existing ventilation equipment must not be changed. To ensure a sufficient air circu-

lation, the flow of air must not be obstructed.

All slide-in units can be removed or inserted with the power still applied. To remove and insert the units you should use the two locking screws fitted to the front of the unit. A type label is fixed on the handhold above the locking screw on the bottom of the board providing information on the hardware and software version of the unit.

A label with the words HOT AREA is fixed to hot surfaces. This indicates severe danger of injury.

Shelters with a front door may only be operated when this door is closed.

!Beware of rotating parts.

!There is a danger of injury if the door is left open.

17


Id:0900d80580241489

You should therefore remove the front door before doing the necessary work and replace it once you have finished your work.

When inserting and removing shelves and when transporting them, take their weight into consideration.

Cables may never be disconnected by pulling on the cable. Disconnection/connec-tion may only be undertaken by pushing in/pulling out the connector involved.

2.8 Handling Optical Fiber Connectors and CablesOptical connectors are precision-made components and must be handled accordingly. To ensure faultless functioning, the following points must be observed: Install protective caps on unplugged optical connectors under all circumstances to

protect against physical damage and dirt. Before making connections, use isopropyl alcohol and non-fibrous cellulose to clean

the faces of the connectors. Avoid impact stresses when handling connectors.

Physical damage to the faces of optical connections impair transmission quality (higher attenuation).

Avoid a bend radius less than 30 mm for fiber optic links. Mechanical damage to the surfaces of optical connectors impairs transmission

quality by higher attenuation. For this reason, do not expose the connectors to impact and tensile load. Once the protective dust caps have been removed, you must check the surfaces

of the optical fiber connectors to ensure that they are clean, and clean them if necessary. For cleaning, the C42334-A380-A926 optical fiber cleaning tool or a clean, lint-free cellulose cloth or a chamois leather is suitable. Isopropyl alcohol can be used as a cleaning fluid.

2.9 Virus Protection

Even when exchanging data via a network or external data media (e.g. floppy disks) there is a possibility of infecting your system with a virus. The occurrence of a virus in your system may lead to a loss of data and breakdown of functionality.

You have to do the following: You have to check every data medium (used data media as well as new ones) for

viruses before reading data from it. You must ensure that an up-to-date virus scanning program is always available. This

program has to be supplied with regular updates by a certified software provider. It is recommended that you make periodic checks for viruses in your OS.

!To prevent a virus infection you may not use any software other than that is released for the Operating System (OS based on Basis AccessIntegrator), Local Craft TerminalLCT) and transmission system.

!The operator is responsible for protecting against viruses and for carrying out repair procedures when the system is infected.

18

Commission

Id:0900d80580241489

Protective Measures

It is recommended to integrate the virus scanning program into the start-up sequence on the LCT.

2.10 RoHS RequirementsNokia Siemens Networks considers the protection of the environment and the preserva-tion of natural resources as a major duty and thus undertakes great efforts to design its products to be environmental friendly. Therefore, as of July 1st, 2006, all contract products of Nokia Siemens Networks to which the RoHS (Restriction of Hazardous Substances) directive applies to and which are put on the market within the countries where the RoHS requirements

are transposed into national law are in compliance with the requirements of the RoHS. Nokia Siemens Networks reserves the right to apply the exemptions to the RoHS requirements as set out in the Annex to the RoHS directive, in particular lead in solders for network infrastructure equipment for switching, signaling, transmission as well as network management for telecommunication.

2.11 Declaration of CE Conformityg The CE (Conformit Europenne) Declaration of Conformity for the product is ful-

filled only if all construction and cabling is undertaken in accordance with the manual and the documentation listed therein, e.g. installation instructions, cabling lists, etc.

2.12 WEEE RequirementsNokia Siemens Networks considers the protection of the environment and the preserva-tion of natural resources as a major duty.This includes waste recovery with a view to reducing the quantity of waste for disposal and saving natural resources, in particular by treatment, recycling and recovering energy from waste electrical and electronic equipment (WEEE). Therefore Nokia Siemens Networks complies with its obligations as producer in terms of the WEEE directive for all its products to which the WEEE directive applies to and which are put on the market within the countries where the WEEE requirements

are transposed into national law,unless any deviant allocation of such obligations have been agreed between Nokia Siemens Networks and its contractual partners. According to WEEE-requirements since August 13, 2005 such products are marked with the symbol of a crossed out

!

Deviations from the specifications or unstipulated changes during construction, e.g. the use of cable types with lower shielding values is a violation of the CE requirements. In such cases, the conformity declaration is invalidated and the manufacturer is refused from responsibility. All liability passes immediately to those persons undertaking any unauthorized deviations.

19


Id:0900d80580241489

wheeled bin with bar, indicating separate collection for electrical and electronic equip-ment, as shown below.

20

Commission

Id:0900d8058025ddcb

General Requirements

3 General RequirementsThe commissioning of hiX 5625/30/35 can be performed with the element manager (EM GX R2.8) or the LCT locally connected to the RJ45 connector of the TMN interface on the CXU. The commissioning of hiX 5625/30/35 requires the following facilities depending on what is used: Management network

The ftp server must be accessible in the management network. The ftp server can be separately installed on several hosts, see Section 4 Configuring the FTP Server.

Management single PC The ftp server must be installed on the PC, see Section 4 Configuring the FTP

Server.

3.1 Visual Inspection Check the following points before commissioning:1. All deliverables were supplied and the installation work is completed.

The delivery of hiX 5625/30/35 hardware is all right. The racks and shelves are assembled. Using the part lists, check that all deliverables were supplied. The power supply is connected and constantly available. The emergency power

supply system is operational. The circuit breakers for the power supply must be in position 0 or OFF during the visual inspection.

The cabling and positioning of the modules should be checked with the installa-tion instructions.

Both internal and external cables were correctly routed and connected. The racks, shelves and cables are labeled correctly. Visual check of the complete installation (particularly the protection devices, e.g.

.overvoltage and lightning protection). The system power supply is connected but is not switched on yet (the emer-

gency supply is functional).2. The hardware modules are in delivery condition

The hardware settings of the racks and modules must be checked. The modules are equipped with the current firmware and correspond to the

correct hardware version (compare for this the existing FW and HW with the release note of the current SW-APS package). Note the MAC addresses.

3. The hardware of the OS meets the requirements, the software is present.4. The required documentation is available on site.5. The required tooling/test equipment is available.6. The EM GX R2.8 or the LCT is installed and ready for service.

3.2 Plan of Activities for Commissioning The following tasks must be performed before/during commissioning.1. Preparatory measures

Visual inspection of the hiX 5625/30/35, see Section 3.1. Switch the circuit breakers to 1 or ON

21

Commission General Requirements

Id:0900d8058025ddcb

Connect the EM GX R2.8 or the LCT with the hiX 5625/30/352. Startup the system and loading the software

The procedure for startup the system is described in Section 5.2 Procedure. For loading the software see Section 5.3 Load the Software.

3. Commissioning the NE hiX 5625/30/35.The commissioning contains the required instructions to take the network element hiX 5625/30/35 in operation. Detailed information about the parameter settings is provided by a context-sensitive online help and in the element manager documentation.The hiX 5625/30/35 should be commissioned in the following sequence:

Steps Action

1. Insert the NE, configure the NE parameters see Section 7.1

2. Synchronize Date and Time see Section 7.2

3. Configure the FTP User see Section 7.3

4. Synchronize the clock see Section 7.4

5. Configure Transmission Capabilities see Section 7.5

6. Saving NE Configuration Data see Section 7.6

7. Configure Modules see Section 7.7

8. Configure Bridge see Section 7.8

9. Configure Profiles see Section 7.9

10. Configure Ports see Section 7.10

11. Lock/Unlock Ports see Section 7.11

12. Database Backup see Section 7.12

Table 3 Sequence for Commissioning the NE hiX 5625/30/35

22

Commission

Id:0900d8058025f5a0

Configuring the FTP Server

4 Configuring the FTP ServerThis chapter describes step-by-step how to install and configure a File Transfer Protocol (FTP). The FTP server for the hiX 5625/30/35 can be installed on the same PC/laptop used for the EM GX (LCT) or can run separately on a PC located in the same management network. The hiX 5625/30/35 was tested with FTP servers running on both OS Windows Server 2003 and Solaris 9.

4.1 Windows FTP ConfigurationRequirementsThe following software requirements must be fulfilled: Windows Server 2003 Current Windows service pack Microsoft Internet Information Services (IIS) Active directory service configured Virus scanner available (optional) Configuration files for hiX 5625/30/35 available Released SAPS (System Application Program Software).The FTP service is not automatically installed during installation of Windows Server 2003.

Installation1. Click Start Control Panel Add or Remove Programs2. Click Add/Remove Windows Components to display the Components list.3. Click Application Server Internet Information Services (IIS) (but do not select or

clear the check box), and then click Details.4. Click to select the check boxes (if they are not already selected): Common Files,

File Transfer Protocol (FTP) Service, and Internet Information Services Manager. Click OK button and then click Next button.

5. When you are prompted, insert the Windows Server 2003 CD-ROM into the CD-ROM drive or provide a path to the location of the files, and then click OK.

6. Click Finish button finish the installation.

ConfigurationTo transmit data between Windows Server 2003 and hiX 5625/30/35 via FTP, a user with login and password for hiX 5625/30/35 must be configured with the Windows user management system.1. Click Start Programs Administrative Tools Active Directory Users and

Computers Users to expand the folder containing current user objects. Click Action New User in the window menu to display the New Object - User dialog box.

2. Enter an User logon name at least and then click Next button.

23

Commission Configuring the FTP Server

Id:0900d8058025f5a0

Figure 9 Defining a New User (Example)3. Type the Password and retype it.

Click to select the Password never expires check box. Click to clear check marked boxes and then click Next button.

Figure 10 Defining the Password (Example)4. Click Finnish button to confirm the settings.In order to give user locally logon rights following steps are required:1. Click Start Programs Administrative Tools Domain Controller Security Policy

to display the Default Domain Controller Security Settings dialog box.

24

Commission

Id:0900d8058025f5a0


Figure 11 Assigning User Rights (Example)In the console tree click User Rights Assignment and then douple-click Allow log on locally in the detail pane to change user right. Click Properties to display the Security Policy Setting dialog box.

Figure 12 Dialog Security Policy Setting (Example)2. Click Add User or Group... button to display the Add User or Group search field .3. Click the Browse... button to choose the created user (for example ftp) from the

Select Users or Groups list. Then click Add.4. Click OK button to confirm.1. Click Start Programs Administrative Tools Internet Services Manager to

display the Internet Information Services dialog.

25


Id:0900d8058025f5a0

Figure 13 Dialog Internet Information Services (Example)Click Default FTP Site in the console tree and then click Properties item to open the Default FTP Site Properties dialog. Following properties must be set: On FTP Site tab enter the IP Address and click to select Unlimited in the

FTP site connections section, see Figure 14.Click OK and then Apply button to confirm the settings.

26

Commission

Id:0900d8058025f5a0


Figure 14 FTP Site Tab (Example) Click Home Directory tab and enter the home directory into the Local path

field (for example, drive c, e or d:\InetPub\ftproot), if not yet available, see Figure 15.In order to write a backup file, the configured FTP user must be granted write permissions on the FTP server. Click to select the Read and Write check boxes (if they are not already selected).Click OK and then Apply button to confirm the settings.

27


Id:0900d8058025f5a0

Figure 15 Home Directory Tab (Example)2. After installation, the ftproot directory has to be configured for access via the

network environment. To do this, the ftproot directory must be set to shared in the File Manager. Right-click ftproot in the Explorer, and then click Sharing tab to display the ftproot Properties property panel.

28

Commission

Id:0900d8058025f5a0


Figure 16 Change the Access to "ftproot" (Example)3. Click OK and then Apply button to confirm the settings.

4.2 Solaris FTP ConfigurationTo establish a connection between Solaris clients and Solaris FTP server the following steps are required:1. Create a separate FTP-user on the Solaris machine that shall be run the FTP server.2. Create a directory for FTP server files. Give the FTP-user rights to transfer and

change files for it.3. Share this directory with nfs share command, for example:

share -F nfs -o rw -d g Store the share command in /etc/dfs/dfstab to undertake that after restart all will

work.4. Store at minimum one valid file in this directory.5. Install and start FTP server on Solaris machine.On a Solaris machine on that will be run the ACI server:Mount the FTP directory in mounttab:mount -F nfs :g After a restart it is not necessary to repeat the command.In order to configure the ACI Solaris client following settings are necessary:1. Folder ftp Section FTP-folder: write in the mountpoint.2. In section SAPS write in the subfolder(s).

29

Commission Startup the System

Id:0900d8058025f652

5 Startup the System

5.1 Requirements Establish a Hyper Terminal connection between PC and CXU (front access RJ45

console interface) using a straight serial V.24 connecting cable, see Figure 18 Hyper Terminal settings: 38400 8-N-1 speed: 38400 bit/s 8 data bits no parity no flow control 1 stop bit

Figure 17 CXU RJ45 Connector for the Console Interface

Figure 18 Console Cable for the HyperTerminal An EM GX R2.8 must be installed and configured on the local PC.

5.2 ProcedureThe CXU and the interface units are already pre-installed with software. The presetting procedure contains the two parts: Configuring the Outband Interface Configuring the Inband Management Channel

Configuring the Outband Interface1. The first time it is switched on, the CXU starts and stops automatically in the

following menu at SWITCH login:, see Figure 19.

7654321

8

1 2 3 4 5 6 7 89-pin SUB-D connector to Com PortRJ45 plug to Console Interface

Pin 1

Pin 4Pin5Pin 6Pin 7Pin 8Pin 9

Pin 1Pin 2Pin 3 - TXDPin 4 - GNDPin 5 - GNDPin 6 - RXDPin 7Pin 8

Pin 3Pin 2 5 4 3 2 1

6789

30

Commission

Id:0900d8058025f652

Startup the System

Figure 19 Dialog hiX - HyperTerminal (Example SNMP V2 for Outband)2. In order to configure the outband management interface, follow the next steps after

login with login-name root and password, according to Figure 19: enable (ena) configure terminal (conf t) exec-timeout 100 show running-config netif-cfg netdevice mod ipaddr / You can get the index from the table shown by the show running-config netif-cfg command, see the command above (e.g. index 1). For example, netdevice mod ipaddr 1 10.2.30.96/24

netif-route / For example, netif-route default 0.0.0.0/0 192.168.52.5route name: e.g. default destination IP address with subnet mask: e.g. 0.0.0.0/0gateway address: e.g. 192.168.52.5

The SNMP (Simple Network Management Protocol) must be configured for both inband and outband ports, see Configuring the Inband Management Channel Point 3 and Point 4.

write mem (storing of the configuration) exit

3. Connect the EM GX R2.8 (LCT) via Outband.4. Exit the menu using exit 5. Once the CXU has fully booted (indicated in the hyper terminal log), local startup

using the EM GX R2.8 (LCT) will be possible.Configuring the Inband Management Channel1. In order to configure the inband management interface, follow the next steps after

login with login-name root and password according to Figure 20: enable (ena) configure terminal (conf t) exec-timeout 100

31


Id:0900d8058025f652

Figure 20 Dialog hiX - HyperTerminal (Example SNMP V2 for Inband)2. A VLAN for inband communication has to be created and assigned to an uplink port

with the following commands: netdevice / {} (VLAN-ID: 1 to 4092, e.g. 2952) For example, netdevice 192.168.52.97/24 inband_mgmt 2952

bridge (br) vlan add tagged

VLAN-ID: 1 to 4092 port number: x/y for CXU, with x: CLI slot number, for CXU always slot number 0 y: used port of the CXU: 1 to 4Example for CXU port 2: vlan add 2952 0/2 tagged

exit netif-route / For example, netif-route default 0.0.0.0/0 192.168.52.5route name: e.g. default destination IP address with subnet mask: e.g. 0.0.0.0/0gateway address: e.g. 192.168.52.5

3. The SNMP (Simple Network Management Protocol) must be configured for both inband and outband ports. Only the SNMP trap-hosts need to be configured for SNMP V2, see Point 4. SNMP V3 authorizes users and user groups access to agents in accordance with SNMP access rights. To configure SNMP V3, use the following SNMP commands (these commands must only be run once per system, the entries in curly brackets are optional). snmp user

{ } For example, snmp user TMN md5 12345678

snmp group For example, snmp group myGrp v3 TMN

snmp view included {} or snmp view excluded {} For example, snmp view myView included .1.3.6.1

snmp access For example, snmp access myGrp v3 auth readview writeview

4. SNMP trap-hosts must be configured for both inband and outband ports. Configuring SNMP trap-hosts for SNMP V2:

32

Commission

Id:0900d8058025f652

Startup the System

snmp trap2-host For example, snmp trap2-host 192.168.1.1

write mem (store configuration data) exit Configuring SNMP trap-hosts for SNMP V3: snmp trap3-host

{ }

write mem (store configuration data) exit

33


Id:0900d8058025f652

5.3 Load the SoftwareTo upgrade an NE with the current APS, software can be downloaded via EM. The FTP server must be available.1. In the main window of EM GX, click on menu Maintenance -> NE Maintenance,

the following NE Maintenance window opens.2. In the NE dropdown-list box, select the NE to be updated.3. Users have the option to load the software manually from the FTP server to the NE.

The software can be updated automatically if you select 'Activation after download.

Figure 21 NE Maintenance Window(Example)

34

Commission

Id:0900d8058025ddce

Slot Numbering on the hiX 5625/30/35 Shelves and Plug-in Units

6 Slot Numbering on the hiX 5625/30/35 Shelves and Plug-in Units

6.1 M1200g The slot numbering on the M1200 shelf differs from the slot numbering in the

management CLI, see Table 4. Table 4 also contains the plug-in unit names used in the OS (mnemo code).

Slot number on the shelf 201 to 208 209 210 211 to 217

Slot number in the CLI 1 to 8 0 or 9 2) 0 or 10 2) 11 to 17

Plug-in Unit Mnemo code

CXU_B M:CXUGE:4E:E o o 1)

IU_SHDSL48.bis M:IUSHDSL:48B:E o o 1) o

IU_SHDSL48 (-A2) M:IUSHDSL:48E:E o o 1) oIU_ADSL48 M:IUADSL:48P:E o o 1) o

IU_ADSL72-ADL (-A1) M:IUADSL:72AI:WC o o 1) oIU_ADSL72-ADL (-D1) M:IUADSL:72J:CGH o o 1) oIU_ADSL72 (-C1) Annex A

M:IUADSL:72A:CG o o 1) o

IU_ADSL72 (-C1) Annex B

M:IUADSL:72B:CG o o 1) o

IU_ADSL72 (-D1) Annex A

M:IUADSL:72A:CGH o o 1) o

IU_ADSL72 (-D1) Annex B

M:IUADSL:72B:CGH o o 1) o

IU_ADSL72 Annex A (Infineon)

M:IUADSL:72P:IFX o o 1) o

IU_ADSL72 Annex B (Infineon)

M:IUADSL:72I:IFX o o 1) o

IU_VDSL24 (-A3) M:IUVDSL:24D2:IFX o o 1) oIU_VDSL24P (-A1) M:IUVDSL:24P:E o o 1) oIU_VDSL48P (-A1) M:IUVDSL:48P:E o o 1) o1) CXU or IU (slot number in CLI is 10 for this IU) can be pluged-in on plug-in place 210. 2) Slot number in CLI is 0 for CXU for port commands. Slot number in CLI is 9 or 10 for CXU for the following commands: reset card, card admin-state, card alarm-severity-profile, switchover commands, slot card commands and show commands.

Table 4 M1200 Slot Numbering and Plug-in Units

35

Commission Slot Numbering on the hiX 5625/30/35 Shelves andPlug-in Units

Id:0900d8058025ddce

6.2 M1100

g The slot numbering on the M1100 shelf differs from the slot numbering in the management CLI, see Table 5.

Table 5 also contains the plug-in unit names used in the OS (mnemo code).




CXU_B1 M:CXUGE:4E:E o o

CXU_B2 M:CXUB2GE:4:E o o



IU_SHDSL48.bis M:IUSHDSL:48B:E o o 1) o

IU_SHDSL48 (-A2) M:IUSHDSL:48E:E o o 1) oIU_ADSL72-ADL (-A1) M:IUADSL:72AI:WC o o 1) oIU_ADSL72-ADL (-D1) M:IUADSL:72J:CGH o o 1) oIU_ADSL72 (-C1) Annex A

M:IUADSL:72A:CG o o 1) o


M:IUADSL:72B:CG o o 1) o


M:IUADSL:72A:CGH o o 1) o


M:IUADSL:72B:CGH o o 1) o


M:IUADSL:72P:IFX o o 1) o


M:IUADSL:72I:IFX o o 1) o

IU_VDSL24 (-A3) M:IUVDSL:24D2:IFX o o 1) oIU_VDSL24P (-A1) M:IUVDSL:24P:E o o 1) oIU_VDSL48P (-A1) M:IUVDSL:48P:E o o 1) o1) IU (slot number in CLI is 10 for this IU) can be pluged-in on plug-in place 110 instead of the CXU (only possible in M1100 shelf). 2) Slot number in CLI is 0 for CXU for port commands. Slot number in CLI is 9 or 10 for CXU for the following commands: reset card, card admin-state, card alarm-severity-profile, switchover commands, slot card commands and show commands.


36

Commission

Id:0900d8058025ddce


6.3 G1100g The slot numbering on the G1100 shelf differs from the slot numbering in the

management CLI, see Table 6. Table 6 also contains the plug-in unit names used in the OS (mnemo code).




CXU_B1 M: CXUB1GE: 4E: E o o




IU_SHDSL48.bis M:IUSHDSL:48B:E o o

IU_SHDSL48 (-A2) M:IUSHDSL:48E:E o oIU_ADSL72-ADL (-A1) M:IUADSL:72AI:WC o oIU_ADSL72-ADL (-D1) M:IUADSL:72J:CGH o oIU_ADSL72 (-C1) Annex A

M:IUADSL:72A:CG o o


M:IUADSL:72B:CG o o


M:IUADSL:72A:CGH o o


M:IUADSL:72B:CGH o o


M:IUADSL:72P:IFX o o


M:IUADSL:72I:IFX o o

IU_VDSL24 (-A3) M:IUVDSL:24D2:IFX o oIU_VDSL24P (-A1) M:IUVDSL:24P:E o oIU_VDSL48P (-A1) M:IUVDSL:48P:E o o1) Slot number in CLI is 0 for CXU for port commands. Slot number in CLI is 9 or 10 for CXU for the following commands: reset card, card admin-state, card alarm-severity-profile, switchover commands, slot card commands and show commands.

Table 6 G1100 Slot Numbering and Plug-in Units

37


Id:0900d8058025ddce

6.4 M600

g The slot numbering on the M600 shelf differs from the slot numbering in the management CLI, see Table 7. The same is true for slots: 1 and 201, 7 and 207, etc.





CXU_C M:CXU_CGE:E o o

CXU_C2 M:CXUC2GE:4:E o o




IU_SHDSL48 (-A2) M:IUSHDSL:48E:E o oIU_ADSL48 M:IUADSL:48P:E o o

IU_ADSL72-ADL (-A1) M:IUADSL:72AI:WC o oIU_ADSL72-ADL (-D1) M:IUADSL:72J:CGH o oIU_ADSL72 (-C1) Annex A

M:IUADSL:72A:CG o o


M:IUADSL:72B:CG o o











38

Commission

Id:0900d8058025ddce


6.5 G600/G600R

g The slot numbering on the G600/G600R shelf differs from the slot numbering in the management CLI, see Table 8. The same is true for slots: 1 and 201, 7 and 207, etc.









IU_SHDSL48 (-A2) M:IUSHDSL:48E:E o oIU_ADSL48 M:IUADSL:48P:E o o

IU_ADSL72-ADL (-A1) M:IUADSL:72AI:WC o oIU_ADSL72-ADL (-D1) M:IUADSL:72J:CGH o oIU_ADSL72 (-C1) Annex A

M:IUADSL:72A:CG o o


M:IUADSL:72B:CG o o










Table 8 G600/G600R Slot Numbering and Plug-in Units

39


Id:0900d8058025ddce

6.6 M400

g The slot numbering on the M400 shelf differs from the slot numbering in the management CLI, see Table 9.


Slot number on the shelf 202 203 204 to 207

Slot number in the CLI 0 or 1 2) 0 or 2 2) 3 to 6


CXU_C M:CXU_CGE:E o o 1)

CXU_C2 M:CXUC2GE:4:E o o 1)

CXU_B21 M:CXUB21GE:4:E o o 1)

CXU_B3 M:CXUB3GE:4:E o o 1)

IU_SHDSL48.bis M:IUSHDSL:48B:E o 1) o

IU_SHDSL48 (-A2) M:IUSHDSL:48E:E o 1) oIU_ADSL72-ADL (-A1) M:IUADSL:72AI:WC o 1) oIU_ADSL72-ADL (-D1) M:IUADSL:72J:CGH o 1) oIU_ADSL72 (-C1) Annex A M:IUADSL:72A:CG o 1) oIU_ADSL72 (-C1) Annex B M:IUADSL:72B:CG o 1) oIU_ADSL72 (-D1) Annex A M:IUADSL:72A:CGH o 1) oIU_ADSL72 (-D1) Annex B M:IUADSL:72B:CGH o 1) oIU_ADSL72 Annex A (Infineon) M:IUADSL:72P:IFX o 1) oIU_ADSL72 Annex B (Infineon) M:IUADSL:72I:IFX o 1) oIU_VDSL24 (-A3) M:IUVDSL:24D2:IFX o 1) oIU_VDSL24P (-A1) M:IUVDSL:24P:E o 1) oIU_VDSL48P (-A1) M:IUVDSL:48P:E o 1) o1) CXU or IU (slot number in CLI is 2 for this IU) can be pluged-in on plug-in place 203. 2) Slot number in CLI is 0 for CXU for port commands. Slot number in CLI is 1 or 2 for CXU for the following commands: reset card, card admin-state, card alarm-severity-profile, switchover commands, slot card commands and show commands.


40

Commission

Id:0900d8058025ddce


6.7 G400/G400R

g The slot numbering on the G400/G400R shelf differs from the slot numbering in the management CLI, see Table 10.





CXU_C M:CXU_CGE:E o o





IU_SHDSL48 (-A2) M:IUSHDSL:48E:E o oIU_ADSL72-ADL (-A1) M:IUADSL:72AI:WC o oIU_ADSL72-ADL (-D1) M:IUADSL:72J:CGH o oIU_ADSL72 (-C1) Annex A

M:IUADSL:72A:CG o o


M:IUADSL:72B:CG o o










Table 10 G400/G400R Slot Numbering and Plug-in Units

41

Commission Commissioning the Network Element HiX 5625/30/35

Id:0900d8058025f9f0

7 Commissioning the Network Element HiX 5625/30/35

7.1 Insert the Network ElementProceed as follows to access the NEs with the EM GX R2.81. Select View Network View in the EM GX R2.8 main window.

The Network View opens, see Figure 252. In the Network View, select the icon root, see Figure 253. Select in the menu Configuration Insert NE.

The dialog for creating an SNMP NE opens, see Figure 22

Figure 22 Inserting an SNMP Network Element (Example)Enter the required SNMP parameters:

4. Select the SNMP Settings tab, see Figure 23.

NE Property Description

Type Select the SNMP NE in the drop-down list (e.g. hiX 5625 R2.8).

SNMP Version Select the SNMP version from the drop-down list (e.g. SNMP V3 or SNMP V2c).

IP Address Enter the IP address of the highlighted SNMP NE in accordance with the project documentation.

Name (Optional) Name according to project documentation (The characters : / \ $ *) are not permitted).If nothing is entered, the EM uses the combination by default.

R Community Change the fields R Community and R/W Community in accordance with the project documentation. Defaults are public for R Community and pri-vate for R/W Community. R/W Community

Table 11 SNMP Parameters

42

Commission

Id:0900d8058025f9f0

Commissioning the Network Element HiX 5625/30/35

Figure 23 SNMP Settings Tab (Example)Enter the relevant interface parameters.

5. Once parameter SNMP V3 is selected as SNMP Version in the NE properties tab, an additional tab called SNMP authorization will appear, see Figure 24

Figure 24 SNMP Authorization Tab (Example)6. Confirm your entries with Apply.7. Click the + sign on the left-hand side of root to open the SNMP tree.

The SNMP NE hiX ... is displayed, see Figure 25

43


Id:0900d8058025f9f0

Figure 25 Network View (Example)If during startup inconsistencies should occur in the NE, you can display the current data for the NE by means of a consistency check.Users can perform a consistency check manually.If alarms are displayed, carry out any corrections using the EM GX R2.8 tool branch to maintenance

7.2 Synchronize Date and TimeThe NE is normally synchronized automatically every 24 hours.Immediate synchronization can be performed manually during startup:1. Select the icon for the SNMP NE hiX in the Network View , see Figure 25.2. In the main menu, select the menu item Configuration Equipment Configuration

and select the NE to open the NE window in the Equipment Configuration dialog. Open the Date/Time tab.

44

Commission

Id:0900d8058025f9f0


Figure 26 Date/Time Tab (Example) Click the Synchronize NE button The NE hiX assumes the date and time from the EM GX R2.8 server.

3. Click the Refresh button to confirm.

7.3 Configure the FTP User1. Select the icon for the SNMP NE hiX in the Network View , see Figure 25.2. In the main menu, select the menu item Configuration Equipment Configuration

and select the NE to open the NE window in the Equipment Configuration dialog. Open the FTP Server tab.

45


Id:0900d8058025f9f0

Figure 27 FTP Server Tab (Example) Enter the values for the SAPS FTP server in the SAPS download settings

dialog box, see Table 12. Click Use same FTP server for NE and ACI if SAPS and data are saved on the

same FTP server. If SAPS and data are saved on different FTP servers, enter the values for the

data FTP server in the Data/Backup files settings dialog box, see Table 12.

3. Click the Apply button to confirm.

Input field Required settingsSever address: IP address of the FTP server User name: User name of the FTP server Password: Password of the FTP server Confirm password: Enter the password a second time Rel. path: Dialog box SAPS download settings: Enter the path to be

used for the APS. Dialog box Data/Backup files settings: Enter the path to be used for the backup files.

Table 12 Settings for the FTP Server Tab

46

Commission

Id:0900d8058025f9f0


7.4 Synchronize the Clock 1. Select the icon for the SNMP NE hiX in the Network View , see Figure 25.2. In the main menu, select the menu item Configuration Equipment Configuration

and select the NE to open the NE window in the Equipment Configuration dialog.

3. Open the Clock Sync tab.

Figure 28 Clock SynchronizationEnter the required settings:

4. Click the Apply button to confirm.

7.5 Configure Transmission Capabilities1. Select the icon for the SNMP NE hiX in the Network View , see Figure 25.2. In the main menu, select the menu item Configuration Equipment Configuration

and select the NE to open the NE window in the Equipment Configuration dialog.

3. Open the Configuration tab.

Input field Required settings

Wait time to restore (s) The switchover between the different clock sources is delayed for this time

Alarm Severity Profile Alarm severity profile in accordance with the planning documenta-tion

Table 13 Settings for the Clock sync tab

47


Id:0900d8058025f9f0

Figure 29 Configuration Tab (Example) Mark the required transmission capabilities according to the project documenta-

tion Confirm with Apply.

7.6 Saving the NE Configuration DataClick the Write NE Data button to store configuration data into the reset-safely memory, see Figure 29.

7.7 Configure Modules

7.7.1 Configure CXU1. Select the icon for the SNMP NE hiX in the Network View , see Figure 25.2. In the main menu, select the menu item Configuration Equipment Configuration.3. Click on the icon for CXU and open the General tab, see Figure 30.

If automatic reset after software download was not made the plug-in unit must be reset in the Module menu. Choose reset system from the Recovery Level drop-down list.g Reset system with defaults overwrites all configuration data and set the

system values to the delivery state. The inband and outband management

48

Commission

Id:0900d8058025f9f0


interfaces must be reconfigured via CLI. Choose this item only if the database is corrupt.

Figure 30 General Tab of CXU (Example)Click Start button to reset the system.

4. Click on the icon for CXU and open the Status tab, see Figure 31.

49


Id:0900d8058025f9f0

Figure 31 Status Tab of CXU (Example)

7.7.2 Preparing System for Redundancy1. Select the icon for the SNMP NE hiX in the Network View , see Figure 25.2. In the main menu, select the menu item Configuration Equipment Configuration,

select the NE to open the NE window in the Equipment Configuration dialog.3. Open the Protection tab, see Figure 32.

Figure 32 Protection Tab (Example)If optical splitters are used for redundancy, you must select use optical splitter in the Feature field.

4. Click Apply to confirm changes.

50

Commission

Id:0900d8058025f9f0


7.7.3 Configure CXU Ethernet Ports1. Select the icon for the SNMP NE hiX in the Network View , see Figure 25.2. In the main menu, select the menu item Configuration Equipment Configuration.3. Click on the icon Bridge under CXU and open the Ethernet Port tab, Figure 33.

The operational and alarm state and the line parameters as well as the parameters of the used SFP module are shown. The required settings are provided in Table 14.

Figure 33 Ethernet Port Tab of CXU (Example)

Setting Description

Alarm severity profile according to the planning documents.

Type 1) Select electrical or optical according to the used SFP module. Negotiation mode 1) depending on the SFP:

auto is recommended in any case,forced can only be used for electrical Ethernet ports of the CXU combined with defined bitrate setting.

Tx rate 1) Port speed in accordance with your planning documentation. Duplex mode 1) Signal mode in accordance with your planning documentation. Flow control 1) Configure flow control in accordance with your planning documentation. Standby laser Disable has to be selected, if optical splitters are used for redundancy.

Switch over Yes has to be selected, to enable automatic switchover in the case of optical link failures.

1) The values in these fields may only be modified on the LCT

Table 14 Settings of CXU Ethernet Ports

51


Id:0900d8058025f9f0

Enter the parameters and confirm with Apply. 4. Click on the icon Bridge under CXU and open the BCSC tab, see Figure 34.

Figure 34 BCSC Tab of CXU (Example)Enter the parameters and confirm with Apply.

7.7.4 Create Interface Unit CardsInterface unit cards can also be created in NE when they are not plugged physical. The Admin state of those IUs is set to Planned and can not be changed until the card is real plugged in.1. Select the icon for the SNMP NE hiX in the Network View , see Figure 25.2. In the main menu, select the menu item Configuration Equipment Configuration.3. In the SNMP navigation tree click ...hiX -> Not configured# to display the Gen-

eral dialog page.Click

52

Commission

Id:0900d8058025f9f0


5. Click the Create button to insert the IU card.6. Select Alarm severity profile.7. Click Apply button to confirm the configuration.

7.7.5 Reset of an Interface Unit Card1. Select the icon for the SNMP NE hiX in the Network View , see Figure 25.2. In the main menu, select the menu item Configuration Equipment Configuration.3. In the SNMP navigation tree click ...hiX -> IU... -> General tab.

Choose reset modul from the Level drop-down list.4. Click the Start button to initiate the reset.

IU_ADSL72-B1 Annex B72-port ADSL2+ interface unitAnnex B (Infineon)

S50010-M1499-B101 M:IUADSL:72I:IFX

IU_ADSL72-C1 Annex A72-port ADSL2+ interface unitAnnex A (Infineon)

S50010-M1498-C1 M:IUADSL:72A:CG

IU_ADSL72-C1 Annex B72-port ADSL2+ interface unitAnnex B (Infineon)

S50010-M1499-C1 M:IUADSL:72B:CG

IU_ADSL72-D1 Annex A72-port ADSL2+ interface unit (Annex A) with Convergate D and Geminax-Max V2.1

S50010-M1498-D1 M:IUADSL:72A:CGH

IU_ADSL72-D1 Annex B72-port ADSL2+ interface unit (Annex A) with Convergate D and Geminax-Max V2.1

S50010-M1499-D1 M:IUADSL:72B:CGH

IU_ADSL72-ADL-A172-port ADSL2+ interface unitAll Digital Loop (Infineon)

S50028-Q2038-A1 M:IUADSL:72AI:WC

IU_ADSL72-ADL-D172-port ADSL2+ interface unitAll Digital Loop (Infineon)

S50028-Q2038-D1 M:IUADSL:72J:CGH

IU_SHDSL48.bis 48-port SHDSL interface unit(Conexant, 4-wired bonding) Bis and wetting current support

S50028-Q2029-A1 M:IUSHDSL:48B:E

IU_SHDSL48-A2 48-port SHDSL interface unitSimultaneous support of 2-wire and 4-wire

S50028-Q2029-A2 M:IUSHDSL:48E:E

IU_VDSL24-A3 S50028-Q2028-A3 M:IUVDSL:24D2:IFX

IU_VDSL24P-A1 S50028-Q2027-A1 M:IUVDSL:24P:E

IU_VDSL48P-A1 S50028-Q2066-A1 M:IUVDSL:48P:E

Interface Unit Part Number Mnemo Code

Table 15 Interfaces Units (Cont.)

53


Id:0900d8058025f9f0

7.7.6 Configure Interface Unit CardsPorts1. Select the icon for the SNMP NE hiX in the Network View , see Figure 25.2. In the main menu, select the menu item Configuration Equipment Configuration.3. In the SNMP navigation tree click ...hiX -> IU -> VDSL Port# / ADSL Port# to

display the xDSL-Line dialog page.Change default settings according to the planning documentation.

4. Click Apply button to confirm changes.

7.8 Configure Bridges and VLANs1. Select the icon for the SNMP NE hiX in the Network View , see Figure 25.2. In the main menu, select the menu item Configuration Equipment Configuration

and click Bridges to open the Bridge window in the Equipment Configuration dialog, see Figure 35.

Figure 35 NE - Bridge (Example)3. Enter the parameters in accordance with the project-specific planning documenta-

tion and confirm with Apply button.

7.8.1 Configure Bridge Ports1. Select the icon for the SNMP NE hiX in the Network View , see Figure 25.2. In the main menu, select the menu item Configuration Equipment Configuration

and click IUVDSL/IUADSL VDSL/ADSL Port# PVC in the Equipment Configuration Window.

54

Commission

Id:0900d8058025f9f0


3. Open the Bridge tab and Choose the "Tagging mode", see Figure 36.

Figure 36 Bridge Port (Example)

Enter the data in accordance with the project-specific planning documentation.

Mode Description

"untagged" user frames

g Enter of VLAN ID into "PVID" field is required. Upstream: allowed untagged frames and droped tagged frames Upstream: add tag with configured VID per port Downstream: strip tag.This is the default setting for subscriber ports. g The bridge port can only be set to untagged, if the Replace VLAN tag

field is set to disabled!

"tagged" user frames

g Only frames with the configured VID are forwarded. Upstream: allowed tagged frames and droped untagged frames and

frames with unknown VIDs . Downstream: keep existing tag.

Table 16 Tagging Modes of the Bridge Port

55


Id:0900d8058025f9f0

7.8.2 Configure VLAN1. Select the icon for the SNMP NE hiX in the Network View , see Figure 25.2. In the main menu, select the menu item Configuration Equipment Configuration

and click Bridge VLAN to open the VLAN window in the Equipment Configu-ration of hiX... dialog, see Figure 38.

3. Open the Overview tab, see Figure 37. This tab contains a list of all created Virtual Local Area Networks (VLANs).

Figure 37 Overview Tab of VLAN (Example)

4. To configure a new VLAN, click the New button in the Overview tab. The VLAN Configuration window is opened, see Figure 37. Enter the parameters and confirm with OK.

5. Open the Vlan Assignment tab, see Figure 38, you can manage the VLAN assign-ment.

56

Commission

Id:0900d8058025f9f0


Figure 38 VLAN Assignment (Example)6. Open the FDB tab.

This tab contains a list of all Forwarding Databases (FDBs). Detailed information is provided by the context-sensitive online help. Confirm with Apply.

7. Close the Dialog.

7.8.3 Configure IGMP

7.8.3.1 IGMP Providerg IGMP provider are required to use proxy functionality.

The number of IGMP provider is up to now limited to 16.1. Select the icon for the SNMP NE hiX in the Network View , see Figure 25.2. In the main menu, select the menu item Configuration Equipment Configuration

and click Bridge Provider in the Equipment Configuration Window.3. Create a new IGMP provider by right-clicking the "IGMP object icon to expand the

context menu. Select the "New IGMP profile" command.Enter a unique and significant provider name (space, special characters and leading digits are not allowed).

57


Id:0900d8058025f9f0

Figure 39 IGMP Provider

4. Change or confirm preference settings.

Setting Description Default value

Proxy IP address Enter the proxy IPv4 address

Robustness Tunes IGMP to expected packet losses on the link. The default value effects that IGMP is robust to a single packet loss. If a subnet is expected to be lossy, this variable may be increased. The robustness must not be zero, and should not be one.

2

Query interval (s) Sets the interval in seconds between subscriber membership query messages are sent by the router (downstream). By varying this variable the number of IGMP messages on the network can be changed. Larger values cause IGMP queries to be sent less often.

60 s

Table 17 Set up of IGMP Provider

58

Commission

Id:0900d8058025f9f0


5. Click the "Create" button.

7.8.3.2 IGMP Multicast Groups and Packages1. Select the icon for the SNMP NE hiX in the Network View , see Figure 25.2. In the main menu, select the menu item Configuration Equipment Configuration

and click Bridge IGMP in the Equipment Configuration Window.3. Open the General tab, see Figure 40.

Query response interval (s)

Sets the interval between subscriber membership reports. By varying this variable the burstiness of IGMP messages on the subnet can be tuned. Larger values make the traffic less bursty.Range: 0...25.5 s (0.1 s steps)g The number of seconds must be less than the

"Query interval".

1 s

Startup query interval (s)

Interval between general queries sent by a router on startup.

15 s1)

Startup query count

Number of queries sent out on startup, separated by the "Startup query interval

22)

Last member query interval (s)

Used by timer to calculate group-specific and group-and-source-specific queries.A reduced value results in reduced time to detect the loss of the last member of a group or source

0.1 s

Last member query count

Number of group-specific queries sent before the router assumes there are no local members.

22)

Intermediate leave This parameter will be set by the IGMP profiles. N/A

Unsolicited report interval (s)

Time between repetitions of a subscriber initial report of membership in a group

10 s

Router timeout (s) Used only for IGMPv1 streams.Sets the groups report delay timer

400 s

Router present timeout (ms)

Used only for IGMPv1 streams.Sets the present timeout of the groups delay timer

0 ms

1) 1/4 the "Query interval 2) Equal the "Robustness

Setting Description Default value

Table 17 Set up of IGMP Provider (Cont.)

59


Id:0900d8058025f9f0

Figure 40 General Tab of IGMP(Example)

The number of "Max joined subscriber" can be changed. g This setting is valid for the whole system.Click Joined subscribers>> to open the joined suscribers overview. Click the "Update" button to make the list of the joined subscribers topical.

4. Open the Package tab of IGMP and define the needed packages as follow: Click "New>>" to expand the configuration dialog and enter a unique and

significant package name (spaces are not allowed). Detailed information is provided by the context-sensitive online help. Click "OK" to insert the new package.

5. Open the Groups tab and define the needed groups as follow, see Figure 41.To add a group, click the New >> link.

60

Commission

Id:0900d8058025f9f0


Figure 41 Groups Tab of IGMP (Example)

The required settings are provided in Table 18. Enter the data in accordance with the project-specific planning documentation. Detailed information on setting the parameters are provided by the context-sensitive online help.

To add a package, click the Package assignment linkSelect the package on the right hand-side. Then click

61


Id:0900d8058025f9f0

7.8.4 Configure UMAS1. Select the icon for the SNMP NE hiX in the Network View , see Figure 25.2. In the main menu, select the menu item Configuration Equipment Configuration .3. Click Bridge UMAS to open the UMAS window, see Figure 42.

Figure 42 UMAS Tab of Bridge (Example)

Check the Use DHCP next hop and Use PPPoE next hop checkboxes. Enter the Static MAC Address in order to prevent from the spoofing in accor-

dance with the project-specific planning documentation. Detailed information on setting the parameters are provided by the context-sensitive online help.

Confirm with Apply.

7.8.5 Configure QOS1. Select the icon for the SNMP NE hiX in the Network View , see Figure 25.2. In the main menu, select the menu item Configuration Equipment Configuration

and click Bridge QoS in the Equipment Configuration window, see Figure 43.

62

Commission

Id:0900d8058025f9f0


Figure 43 QoS Configuration (Example)

3. In the QoS window. Enter the data in accordance with the project-specific planning documentation.

Detailed information on setting the parameters are provided by the context sen-sitive online help.

Confirm with Apply.4. Close the Dialog.

7.8.6 Configure MSTP/ERP

7.8.6.1 CIST1. Select the icon for the SNMP NE hiX in the Network View , see Figure 25.2. In the main menu, select the menu item Configuration Equipment Configuration

and click Bridge MSTP/ERP.3. Open the CIST tab and choose the version of the used xSTP from the Force

version drop-down list, see Figure 44

63


Id:0900d8058025f9f0

Figure 44 CIST Tab of MSTP/ERP (Example) Enter the data for the Common Internal Spanning Tree (CIST) in accordance

with the project-specific planning documentation. Detailed information on setting the parameters is provided by the context-sensitive online help.

Confirm with Apply.4. Close the Dialog.

7.8.6.2 ERP1. Select the icon for the SNMP NE hiX in the Network View , see Figure 25.2. In the main menu, select the menu item Configuration Equipment Configuration

and click Bridge MSTP/ERP.3. Open the ERP tab.

64

Commission

Id:0900d8058025f9f0


Figure 45

Documents

Siemens Dslam user manual hiX 5625/30/35