Hix563x (M600 M1200) ACI (R1.3) OGL V4 EN PDF

Operation
ACI-E R1.2 (EM GX R1.3)

Operator Guidelines (OGL)
A50010-X3-E120-4-7619
Operator Guidelines (OGL) Operation
Important Notice on Product Safety

Elevated 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-1 / IEC 60950-1. All equipment connected has to
comply with the applicable safety standards.
The same text in German:

Wichtiger Hinweis zur Produktsicherheit
In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Spannung. Einige
Teile können auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverletzungen und
Sachschäden führen.
Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert
und wartet.
Das System entspricht den Anforderungen der EN 60950-1 / IEC 60950-1. Angeschlossene Geräte
müssen die zutreffenden Sicherheitsbestimmungen erfüllen.
Trademarks:
All designations used in this document can be trademarks, the use of which by third parties for their
own purposes could violate the rights of their owners.
Copyright (C) Siemens AG 2005.
Issued by the Communications Group

Hofmannstraße 51
D-81359 München
Technical modifications possible.

Technical specifications and features are binding only insofar as
they are specifically and expressly agreed upon in a written contract.
2 A50010-X3-E120-7619
Operation Operator Guidelines (OGL)
Reason for Update

Summary:
The forth release of EM GX R1.3
Details:
Chapter/Section Reason for Update
All Change of ACI-E version
Version History
Issue Date of issue Reason for Update

Number
1 05/2005 ACI EM GX R1.3 initial release
2 06/2005 Procedure for configuring IPoA port aaded
3 09/2005 New features added
4 11/2005 Change of ACI-E version
A50010-X3-E120-7619 3
This document consists of a total of 125 pages including cover page. All pages are issue 1.
Contents
1 Introduction ......................................................................................................... 10
1.1 Audience ............................................................................................................... 10
1.2 Document Structure .............................................................................................. 11
1.3 Related Documentation ........................................................................................ 12
1.4 Typographic Conventions ..................................................................................... 13
2 Starting the Element Manager GX R1.3 ............................................................ 14
2.1 Before Starting ...................................................................................................... 14
2.1.1 Installing the EM GX R1.3 Software ..................................................................... 14
2.1.2 Logging In ............................................................................................................. 14
2.2 Starting and Stopping the EM GX R1.3 Server Processes .................................. 15
2.2.1 Under Windows..................................................................................................... 15
2.2.2 Under Solaris ........................................................................................................ 16
2.3 Starting the ACI-E Element Manager GX R1.3 Client .......................................... 16
2.3.1 Under Windows..................................................................................................... 16
2.3.2 Under Solaris ........................................................................................................ 17
2.4 Element Manager GX R1.3 Local Craft Terminal ................................................. 17
2.5 Migration ............................................................................................................... 19
3 EM GX R1.3 Client User Interface...................................................................... 20
3.1 EM GX R1.3 Main Window ................................................................................... 20
3.1.1 File Menu .............................................................................................................. 21
3.1.2 Toolbar .................................................................................................................. 21
3.1.3 Status Bar ............................................................................................................. 22
3.2 Viewing the Access Network ................................................................................ 22
3.2.1 DCN View for SNMP Network Elements .............................................................. 22
3.2.2 Equipment View .................................................................................................... 23
3.2.3 Zooming the Display ............................................................................................. 24
3.2.4 Setting View Options............................................................................................. 24
3.3 Node Configuration ............................................................................................... 25
3.4 Working with Layout Sets ..................................................................................... 27
3.5 Access Restrictions............................................................................................... 28
3.5.1 Definitions ............................................................................................................. 28
3.5.2 Types of Access Restriction ................................................................................. 29
3.5.3 Access in the Domaining Context......................................................................... 30
3.6 LCT Access........................................................................................................... 30
3.7 Element Manager GX R1.3 Online Help............................................................... 30
4 Configuring Network Elements ......................................................................... 33
4.1 Adding a Network Element ................................................................................... 33
4.1.1 Adding a Single Network Element ........................................................................ 33
4.1.2 Mass Provisioning of SNMP NEs ......................................................................... 34
4.1.3 Autodiscovery of SNMP NEs ................................................................................ 35
4.1.4 Automatic NE Settings .......................................................................................... 37
4.2 Deleting a Network Element ................................................................................. 37
4.3 Editing SNMP Settings.......................................................................................... 37
4.4 Configuring a Network Element ............................................................................ 38
4.4.1 General Network Element Configuration .............................................................. 38
4.4.2 Displaying Equipment Data .................................................................................. 39
4 A50010-X3-E120-7619
4.4.3 Editing Inventory Data ...........................................................................................39

4.5 Setting the Date and Time .....................................................................................39
4.6 Ethernet Parameters..............................................................................................40
4.6.1 VLAN Stacking.......................................................................................................40
4.6.2 MAC Address Translation......................................................................................40
4.6.3 Class of Service Support .......................................................................................41
4.7 Network Element Alarm Configuration ..................................................................42
4.7.1 High-Temperature Warning Threshold ..................................................................43
4.8 Configuring the Outband Management Channel...................................................43
5 Configuring Subscriber Connections................................................................45
5.1 Line Profiles ...........................................................................................................45
5.1.1 Creating a Line Profile ...........................................................................................46
5.1.2 Applying a Line Profile ...........................................................................................48
5.1.3 Mass Provisioning..................................................................................................48
5.1.4 Viewing a Line Profile ............................................................................................49
5.1.5 Deleting a Line Profile............................................................................................49
5.1.6 Exporting and Importing a Profile ..........................................................................51
5.1.7 Updating a Profile ..................................................................................................51
5.2 General Instructions for Configuring Plug-in Units ................................................51
5.3 Port Permissions....................................................................................................52
6 Bridge Configuration...........................................................................................54
6.1 Bridge.....................................................................................................................54
6.1.1 Configure Bridge Parameter ..................................................................................54
6.1.2 Configure Bridge Port ............................................................................................55
6.1.3 Manage Rules........................................................................................................55
6.1.4 Manage DHCP Provider ........................................................................................56
6.1.5 Configure LAG Ports..............................................................................................57
6.1.6 Configure IPoA Ports .............................................................................................57
6.1.7 Configure IGMP Multicast Groups.........................................................................58
6.1.8 Configure Broadcast Storm Control (BCSC) .........................................................59
6.2 EREP/MSTP ..........................................................................................................60
6.2.1 Configure ERP Domain .........................................................................................60
6.2.2 Swap Port Roles of an ERP Domain .....................................................................61
6.2.3 Manage Assignment VLAN-ERP ( from ERP).......................................................61
6.2.4 Configure CIST Bridge Parameter.........................................................................62
6.2.5 Configure CIST Port Parameter ............................................................................62
6.2.6 Configure MSTP Region Parameter......................................................................63
6.2.7 Configure MSTP Instance Parameter....................................................................63
6.2.8 Configure MSTP Port Parameter...........................................................................64
6.2.9 Manage Assignment VLAN-MSTP (from MSTP) ..................................................65
6.3 VLAN......................................................................................................................65
6.3.1 Create a VLAN.......................................................................................................65
6.3.2 Configure VLAN .....................................................................................................67
6.3.3 Delete VLAN ..........................................................................................................67
6.3.4 Manage Assignment VLAN-ERP...........................................................................67
6.3.5 Manage Assignment VLAN-MSTI..........................................................................68
6.4 QoS (Quality of Service) ........................................................................................68
6.4.1 Configure Bridge Mode..........................................................................................69
6.4.2 Configure Queue Mode .........................................................................................69
6.4.3 Configure Queue Priority .......................................................................................70
6.4.4 Configure Queue Mapping.....................................................................................70
A50010-X3-E120-7619 5
7 Monitoring the hiX 563x R1.3 System.............................................................. 71

7.1 Status and State Changes .................................................................................... 71
7.1.1 Alarm State ........................................................................................................... 71
7.1.2 Synchronization State ........................................................................................... 72
7.2 Viewing NE Status in SNMP-DCN View ............................................................... 73
7.3 Viewing Plug-in Unit Status................................................................................... 74
7.4 Viewing Network Interface or Interlink Status....................................................... 75
7.5 Viewing IU Port Status .......................................................................................... 75
7.6 Inventory Data....................................................................................................... 76
7.7 Customer Information ........................................................................................... 78
8 Fault Management .............................................................................................. 80
8.1 Definitions ............................................................................................................. 80
8.2 Fault Information on the EM GX R1.3 Server ....................................................... 80
8.3 Alarm and Event Notification................................................................................. 81
8.3.1 Visible Alarm Notification ...................................................................................... 81
8.3.2 Media Interface ..................................................................................................... 82
8.4 Alarm and Event View Administration................................................................... 83
8.5 Alarm List .............................................................................................................. 83
8.5.1 Opening an Alarm List for the Entire Network ...................................................... 84
8.5.2 Opening an Alarm List for Selected NE ................................................................ 84
8.5.3 Opening the Maintenance Manual........................................................................ 85
8.6 Managing Alarm and Event Logs.......................................................................... 85
8.7 Alarm Log.............................................................................................................. 86
8.8 Alarm Log on EM Client ........................................................................................ 87
8.9 Event Log Display ................................................................................................. 88
8.10 Displaying Alarm and Event Counters .................................................................. 89
8.11 Managing Trouble Tickets .................................................................................... 89
8.11.1 Assigning a Trouble Ticket ................................................................................... 90
8.11.2 Viewing All Trouble Tickets................................................................................... 90
8.11.3 Adding a Note to a Trouble Ticket ........................................................................ 90
8.11.4 Deleting a Trouble Ticket ...................................................................................... 91
8.12 Configuring Fault Options ..................................................................................... 91
8.12.1 Setting Notepad and Trouble Ticket Options........................................................ 92
8.12.2 Setting Acknowledgement Options....................................................................... 92
8.13 Alarm Notes .......................................................................................................... 92
8.13.1 Viewing an Alarm Note ......................................................................................... 93
8.13.2 Adding an Alarm Note........................................................................................... 94
9 Performance Management ................................................................................. 95
9.1 Ethernet Statistics and Performance Monitoring .................................................. 97
9.1.1 Displaying the Ethernet Performance Counter ..................................................... 97
9.1.2 Viewing the Current and History Information........................................................ 97
9.2 ATM Performance Monitoring............................................................................... 99
9.3 IGMP Performance Monitoring ............................................................................. 99
9.3.1 Displaying all existing IGMP Multicast Groups ..................................................... 99
9.3.2 Defining the History Entry Size ........................................................................... 100
9.3.3 Viewing the Current and History Information...................................................... 100
9.4 xDSL Performance Monitoring............................................................................ 100
9.4.1 Displaying the xDSL Performance Counter........................................................ 101
9.4.2 Viewing the Current and History Information...................................................... 101
9.5 Upload Administration......................................................................................... 102
9.6 Managing Performance Data Logs ..................................................................... 102
6 A50010-X3-E120-7619
9.6.1 Opening the “Performance Log Unit Administration” Dialog ...............................103

9.6.2 Create a Performance Log Unit...........................................................................103
9.6.3 Stop and Start a Log Unit ....................................................................................104
9.6.4 Confige a Log Unit ...............................................................................................104
9.6.5 Clear a Log Unit...................................................................................................105
9.6.6 Delete a Log Unit .................................................................................................106
9.6.7 Export Log Unit Records......................................................................................106
9.6.8 Viewing Log Unit Records ...................................................................................107
9.6.9 Configuring Global Settings for Performance Log Units......................................108
9.7 Scheduled Tasks for Performance Data..............................................................108
9.8 Monitor Counters .................................................................................................109
9.9 All Port Counters..................................................................................................109
10 Troubleshooting ................................................................................................110
10.1 Starting a Consistency Check .............................................................................110
10.2 Loop Management...............................................................................................110
10.3 Remote File Administration..................................................................................111
10.4 Maintenance Manual ...........................................................................................112
10.5 Trouble Ticket Administration ..............................................................................112
10.6 Searching for NEs and NTs .................................................................................112
10.7 Failing to monitor packets....................................................................................113
11 Managing Network Elements............................................................................115
11.1 NE Maintenance ..................................................................................................115
11.1.1 Subsequent Downloads and Updates .................................................................116
11.1.2 Displaying Software Version of NE......................................................................117
11.1.3 Downloading Software to an NE..........................................................................117
11.1.4 Displaying Upgrade Status ..................................................................................118
11.1.5 Software Recovery ..............................................................................................118
11.1.6 Backing Up NE Data............................................................................................119
11.1.7 Restoring an NE Database ..................................................................................120
11.2 Audit Log..............................................................................................................121
11.3 Time Scheduled Jobs ..........................................................................................121
11.4 Configuring Log Fetch Size .................................................................................122
12 Abbreviations .....................................................................................................123
A50010-X3-E120-7619 7
Illustrations
Fig. 3.1 EM GX R1.3 Main Window ................................................................................ 20

Fig. 3.2 Views of Element Manager GX R1.3................................................................. 22
Fig. 3.3 SNMP DCN View ............................................................................................... 23
Fig. 3.4 Equipment View for Network Element (Example) ............................................. 24
Fig. 3.5 “View Options” Dialog ........................................................................................ 25
Fig. 3.6 “Node Configuration” Dialog .............................................................................. 26
Fig. 3.7 “Window Layout Set” Dialog .............................................................................. 27
Fig. 3.8 NE Representation in a View............................................................................. 29
Fig. 3.9 “Help” Menu Item in the Main Window .............................................................. 31
Fig. 3.10 Default Page of the Online Help ...................................................................... 31
Fig. 4.1 “SNMP Mass Provisioning” Dialog .................................................................... 35
Fig. 4.2 “SNMP NetScan” Dialog .................................................................................... 36
Fig. 4.3 “Add NE Type” Dialog........................................................................................ 36
Fig. 4.4 “Configuration” Tab............................................................................................ 38
Fig. 5.1 Distribution of Profiles........................................................................................ 46
Fig. 7.1 Status Display in the DCN View ........................................................................ 73
Fig. 7.2 “Node Configuration” Dialog .............................................................................. 74
Fig. 7.3 “Status” Tab of IUADSL (Example) ................................................................... 76
Fig. 7.4 Message Box for an Actice Data Retrieval ........................................................ 78
Fig. 8.1 “Alarm List” Dialog ............................................................................................. 85
Fig. 8.2 “Alarm Log” Dialog............................................................................................. 88
Fig. 8.3 “Event Log” Dialog ............................................................................................. 89
Fig. 8.4 “Create TT Note” Dialog .................................................................................... 91
Fig. 9.1 “Performance Log Unit Administration” Dialog ................................................ 103
Fig. 9.2 “Clear All Records” Dialog ............................................................................... 106
Fig. 9.3 Message Box ................................................................................................... 106
Fig. 10.1 “Find Network Elements” Dialog.................................................................... 112
8 A50010-X3-E120-7619
Tables
Tab. 1.1 Document Structure ..........................................................................................11

Tab. 1.2 Related Documentation.....................................................................................12
Tab. 1.3 Typographic Conventions..................................................................................13
Tab. 2.1 EM GX R1.3 Processes ....................................................................................15
Tab. 3.1 EM GX R1.3 File Menu .....................................................................................21
Tab. 3.2 Node Configuration Menu .................................................................................27
Tab. 4.1 User Priority and Default Queues .....................................................................42
Tab. 5.1 Plug-in Unit Configuration .................................................................................52
Tab. 8.1 Default Alarm Color ...........................................................................................81
Tab. 9.1 Export Options for Performance Data .............................................................107
Tab. 9.2 Counter Records in NE and EM GX R1.3 Database ......................................107
A50010-X3-E120-7619 9
1 Introduction
This manual describes the operation of the AccessIntegrator-Ethernet Element Manager
GX R1.3 software. This software is for the management of SURPASS hiX 563x R1.3
network elements.
This section includes the following topics:
• 1.1 Audience
• 1.2 Document Structure
• 1.3 Related Documentation
• 1.4 Typographic Conventions
1.1 Audience
This manual is intended for hiX 563x R1.3 operators and maintenance personnel. This
manual assumes that you are familiar with the following:
• DSL technology and standards
• Ethernet technology and standards
It is also assumed that you have some familiarity with the hiX 563x system. For more
information about the hiX 563x system, refer to the documents listed under Section “1.3
Related Documentation". Using this manual, you should be able to configure, operate,
and troubleshoot network elements of the hiX 563x system.
Users who are administrators of the GX R1.3 software (backup the GX R1.3 software, set
security options, install the GX R1.3 software) should refer to the ACI EM GX R1.3
Administration Manual and the Installation Manual. For more information about these
documents, see Section “1.3 Related Documentation”.
This manual also assumes that you have a basic knowledge of computer operating sys-
tems. In other words, you know how to operate a typical user interface, navigate through
a directory structure, and perform simple file management tasks. It assumes that you can
navigate to and access a remote host.
10 A50010-X3-E120-7619
1.2 Document Structure

This manual is divided into sections to enable you to find answers to your questions and
use the Element Manager GX R1.3 in the most efficient way. Refer to Tab. 1.1 for an
overview of the various sections.
Category Section Contents
Introduction 1 Introduction Describes document structure as well as related documents.

Describes the target audience and typographic conventions.
2 Starting the Element Manager GX Starting and stopping EM GX R1.3 processes. EM GX R1.3
R1.3 migration. Introduction to the Local Craft Terminal.
3 EM GX R1.3 Client User Interface Describes the user interface of the EM GX R1.3 client.
Procedures for finding NEs and subscribers.
Configuration 4 Configuring Network Elements Adding and configuring network elements. Includes Alarm
severity profiles and external alarms.
5 Configuring Subscriber Connections Configure plug-in units, including line profiles, CPEs, IUs, and
the network interface.
6 Bridge Configuration Configure bridge connections. Includes the creation,

modification, and deletion of ERP MSTP, and the configuration
of VLANs.
Monitoring 7 Monitoring the hiX 563x R1.3 Provides you procedures that enable you to determine the
System status of NEs and plug-in units, as well as ADSL line
supervision and configuring the media interface.
8 Fault Management Describes fault and event management. How to view and
manage the alarm lists and event logs.
9 Performance Management Describes how to configure and monitor performance

management.
Troubleshootin 10 Troubleshooting Provides you with procedures to help troubleshoot problems

g when they occur. It includes starting a telnet session,
consistency check, loopbacks, and remote file administration.
Managing software versions, audit logs, and time scheduled

Management 11 Managing Network Elements
jobs.
Tab. 1.1 Document Structure
A50010-X3-E120-7619 11
1.3 Related Documentation

In addition to this manual, other related documents are available, describing the
AccessIntegrator Ethernet Element Manager GX R1.3 software and the hiX 563x
system. These documents are described in Tab. 1.2.
Title Part Number Topics Covered
AccessIntegrator Ethernet Element A50010-X3-E120-*-76D1 Installation of AccessIntegrator client and server software,
Manager GX R1.3 Installation Manual installation of Versant database, installation of TAO naming
service and client software, configuration of server operating
system options.
AccessIntegrator Ethernet Element A50010-X3-E120-*-7671 Backup and restore of AccessIntegrator data, configuration
Manager GX R1.3 System of domain and permission security.
Administration Manual
hiX 563x R1.3 Technical Description A50010-X3-E130-*-7618 hiX 5630 R1.3 functions and hardware descriptions. This
manual contains references to other documents in the hiX
563x documentation set.
A50010-X3-E135-*-7618 hiX 5635 R1.3 functions and hardware descriptions. This

manual contains references to other documents in the hiX
563x documentation set.
hiX 563x Installation and Test Manual A50010-X3-E130-*-7630 Instructions for the commissioning a hiX 5630 R1.3.
A50010-X3-E135-*-7630 Instructions for the commissioning a hiX 5635 R1.3.
hiX 563x Maintenance Manual A50010-X3-E130-*-7620 Alarm troubleshooting procedures.
A50010-X3-E135-*-7620 Alarm troubleshooting procedures.
ACI Valued Added Applications A50010-T3-H311-*-7619 Value added applications available for the AccessIntegrator
product line. This includes the CORBA-CORBA Mediator,
and CORBA SNMP Mediator.
AccessIntegrator V9.1 Cross Domain A50010-T3-J100-*-7619 Cross Domain Manager operation and references to related
Manager Operation Manual documentation.
Tab. 1.2 Related Documentation
12 A50010-X3-E120-7619
1.4 Typographic Conventions

The following notational conventions are used in all the manuals:
Representation Meaning
Courier Inputs and outputs
Example : Enter LOCAL as the server name
Command not found
italic Variables
Example : name can be eight letters long.
bold Special emphasis
Example : You must not delete this name.
<Courier> Keyboard combinations
Example : <STRG> <ALT>+<ESC>
→ Menu sequences
Example : File → Exit
Additional Information
i
Warnings at critical points of the processing sequence
Tab. 1.3 Typographic Conventions
A50010-X3-E120-7619 13
2 Starting the Element Manager GX R1.3

This section includes the following sections:
• 2.1 Before Starting
• 2.2 Starting and Stopping the EM GX R1.3 Server Processes
• 2.3 Starting the ACI-E Element Manager GX R1.3 Client
• 2.4 Element Manager GX R1.3 Local Craft Terminal
• 2.5 Migration
2.1 Before Starting

Before starting the EM GX R1.3 software, you must be sure that the software is installed
and that you have access to it.
2.1.1 Installing the EM GX R1.3 Software

Before you can start the EM GX R1.3 software, the EM GX R1.3 server software must be
installed on the server host and the client software must be installed on the client host.
For more information, refer to the ACI-E EM GX R1.3 Installation Manual, see Section
“1.3 Related Documentation".
You may also be able to migrate data from a previous installation of the EM GX R1.3
software. For more information, see Section “2.5 Migration”.
2.1.2 Logging In
Access to the EM GX R1.3 is exclusively through an operating system ID. There is no
separate login procedure for the application.
In order to start and operate the Element Manager GX R1.3, you need a specific user
profile which is defined by the following:
• A Windows or Solaris authorization (user name and password)
• Membership in a user group
• Assignment to an EM GX R1.3 permission class.
The user profile is specified by the system administrator for each individual EM GX R1.3
user. Your EM GX R1.3 permission class determines the functions which you may
perform with the EM GX R1.3. For more information about permissions, refer to the ACI-E
Element Manager GX R1.3 System Administration Manual, see Section “1.3 Related
Documentation".
14 A50010-X3-E120-7619
2.2 Starting and Stopping the EM GX R1.3 Server Processes

The EM GX R1.3 server consists of a number of processes. These processes are
described in Tab. 2.1.
Process Description
BRASS The BRASS process (SNMP BRASS Management Multiplexer) is started

automatically when the server is started. The BRASS process cannot be
stopped by the Process Monitor.
SNMP server The SNMP server implements the connection to the access network via the
SNMP interface. It must always be started before the EM GX R1.3 server and
after the BRASS process.
EM GX R1.3 server The EM GX R1.3 server is the link between the SNMP Server and the
graphical user interface. It is responsible for internal communication and
administers the EM GX R1.3 database.
The server process can be started as soon as the connection to the access
network is established.
EM GX R1.3 client The client process implements the graphical user interface for the user. It
needs a connection to the EM GX R1.3 server and can therefore only be
started successfully when the server process is running.
Process monitor The process monitor process is used to start and stop the EM GX R1.3 server
processes under the Solaris operating system. Under Windows it monitors the
processes and attempts to restart them when necessary.
GUI Cut-through service The GUI Cut-through service enables a higher level management system to
open the Element Manager GX R1.3 client.
Tab. 2.1 EM GX R1.3 Processes

The server processes must be running before you can start the EM GX R1.3 client soft-
ware. The client and server can reside on the same host or different hosts. The proce-
dures to start and stop the server processes are described in the following sections.
You should only stop the server processes to upgrade the EM GX R1.3 software or to
restore the EM GX R1.3 database
2.2.1 Under Windows

The BRASS server process, the SNMP server process, and the Element Manager GX
R1.3 server process on the EM GX R1.3 server are started and stopped as Windows
services. Normally these processes are left running. They are configured by default to
start automatically when you restart your computer.
To start or stop Element Manager GX R1.3 server processes manually

1. Open the Control Panel.
Click “Start” “Settings” “Control Panel”.
2. Open Services.
Double-click “Administrative Tools” followed by “Services”.
You can manually start and stop services or enable a service to start when the
computer restarts. The EM GX R1.3 server processes are named as follows:
A50010-X3-E120-7619 15
- SNMP BRASS Management Multiplexer

- ACI SNMP DCNServer EMGXR15
- ACI-E Server EMGXR13
- Access Integrator Process Monitor EMGXR13
- ACI GUI Cut-Through Service V2
To manually start or stop a server process, right-click the service and select “Start” or
“Stop”.
Stopping these processes while a client session is still open causes an error message to
appear on the client interface.
2.2.2 Under Solaris

The BRASS server process is started automatically when you start your computer. The
SNMP server process and the Element Manager GX R1.3 server process are started and
stopped with the process monitor. Normally these processes are left running.
To start the Element Manager GX R1.3 server processes, enter the following command:
$ /opt/emgxr13server-<instance>/aci.sh start
To stop the Element Manager GX R1.3 server processes, enter the following command:
$ /opt/emgxr13server-<instance>/aci.sh stop
To check the status of the server processes, enter the following command:
$ /opt/emgxr13server-<instance>/aci.sh status
Because you can install more than one server instance on a host, the installation path
includes a server instance (1 to 8). The default installation path to the server instances
are given in the examples above. If your server host does not support multiple server
instances, the default directory does not include -<instance>.
2.3 Starting the ACI-E Element Manager GX R1.3 Client

You can only start the client process if the server processes are running, otherwise an
error message appears. It is not necessary to wait for the end of the server startup with
network elements.
2.3.1 Under Windows

To start the EM GX R1.3 client you must be logged on into the same Windows domain as
the EM GX R1.3 server.
To start the EM GX R1.3 client under Windows,
Click “Start” “Programs” “Siemens AccessIntegrator” “EM GX R1.3” “Element

Manager GX R1.3 Client (<server_name>).
16 A50010-X3-E120-7619
The default EM GX R1.3 server was designated during installation of the client software.
To connect to a non-default EM GX R1.3 server you must add the server parameter. You
must have appropriate access rights and permissions.
To connect to a non-default EM GX R1.3 server

1. Click “Start” “Run”.
2. Enter the EM GX R1.3 client executable and path with the server parameter.
The example below uses the default path:
“C:\Program Files\Siemens AG\AccessIntegrator EM GX
R1.3\bin\acic-emgxr13.exe” SERVER=<server_name or IP_address>
3. Click “OK”.
To close a client session
A client process can be ended all time. All opened dialogs or views will be closed auto-
matically. You can do this in the following way:
click “File “Exit” or
via the key combination <Alt>+<F4> or
click “Close” on right hand in the title bar.
2.3.2 Under Solaris

To start Element Manager GX R1.3 client process, first start shell file for the environment
variables, enter the following command:
# source . /opt/AccessIntegrator EMGXR13client/EMGXR13.sh.
Then start the client:
# source . /opt/AccessIntegrator EMGXR13client/acic-emgxr13-so-

laris.exe.sh
If the server host is on the same computer as the client, you can enter local for the host
name. The start command is prepared as a script for each instance you can connect to (0
to 9) and is located in the following default directory:
/<ACI_EM_client_home>/bin
You just need to provide the server host name.
You must have appropriate access rights and permissions.
To close a client session, click “File” “Exit”.
2.4 Element Manager GX R1.3 Local Craft Terminal

This manual also describes the use of the Local Craft Terminal (LCT) version of the ACI-
E Element Manager GX R1.3. The LCT differs from the ACI-E EM GX R1.3 in the basic
assumption that the local craft terminal is intended to be used on a notebook computer
connected to the outband management connection at the same location as the network
element. The ACI-E EM GX R1.3 operator, it is assumed, connects to the network ele-
A50010-X3-E120-7619 17
ment from a management center through the inband connection. This management cen-
ter may be quite remote from the network element that the operator is managing.
The EM GX R1.3 LCT functions almost identically to the ACI-E EM GX R1.3. The
differences are as follows:
• Security settings and permission classes are ignored by the LCT.
• You can only add two NEs to the SNMP port.
Because of the limit on the number of NEs, the feature ’Find NE’ is disabled.
• LCT learns cross connects for single plug-in units, not for the entire NE
You must select a plug-in unit before attempting to learn cross connects.
• If a user connects to an NE with an LCT, other users connecting with the ACI-E EM
GX R1.3 can only view the NE.
No changes can be made until the LCT user disconnects. Other users receive the
message: SNMP General Error. For more information, see Section “3.6 LCT
Access".
• LCT users can lock and unlock the inband cross connection.
ACI-E EM GX R1.3 users are denied this option because locking the inband man-
agement channel interrupts the management connection to the network element.
Once locked, the inband user has no way to unlock the interface.
• LCT users can lock and unlock the network interface.
ACI-E EM GX R1.3 users are denied this option because locking the network interface
causes an interruption of the inband management. Once locked, the inband user has
no way to unlock the interface.
18 A50010-X3-E120-7619
2.5 Migration
Migration enables you to move network connection data (IP address and SNMP
configuration) from a previous version of the ACI-E Element Manager GX R1.3 database
to another version, or from one server to another. Migration requires three steps:
1. Export the connection data.

The data is exported to file.
2. The exported data will be concatenated automatically.
Concatenate links the exported data to a single concatenation file.
3. Import the connection data.
The data is imported to the new installation of ACI-E Element Manager GX R1.3.
For more information about the migration process, refer to the context-sensitive online
help by clicking “Help” button on the corresponding dialogs.
To open the “Migration Export” dialog

Select “Utilities” “Migration” “Export” menu item. The “Migration Export” dialog
appears.
To open the “Migration Import” dialog

Select “Utilities” “Migration” “Import” menu item. The “Migration Import” dialog
appears.
A50010-X3-E120-7619 19
3 EM GX R1.3 Client User Interface

This section provides a quick overview of the EM GX R1.3 user interface. For more
information, refer to the context-sensitive online help.
The following topics are described:

• 3.1 EM GX R1.3 Main Window
• 3.2 Viewing the Access Network
• 3.3 Node Configuration
• 3.4 Working with Layout Sets
• 3.5 Access Restrictions
• 3.6 LCT Access
• 3.7 Element Manager GX R1.3 Online Help
3.1 EM GX R1.3 Main Window

Fig. 3.1 shows the main window.
File Menu
Tool bar
DCN View
General NE parameters
Equipment view Menu bar

Status bar
Fig. 3.1 EM GX R1.3 Main Window
20 A50010-X3-E120-7619
3.1.1 File Menu

Tab. 3.1 briefly describes the individual menu headings.
Menu Description
File Use to exit the Element Manager GX R1.3 client.
A print function enables you to print the active window.
View Offers access to all network views, and allows you to change and delete
time-scheduled jobs. A search function for network elements together with a
quick toggling between the different network views is also offered.
Configuration Contains all the functions for network element configuration, SNMP settings,
NE backup, for subscriber mass provisioning, and software management.
Fault Contains all fault management functions such as alarm lists, alarm
acknowledgements, alarm logging/event reports.
Measurement Contains all the functions for performance monitoring, and loopback testing.
Security Contains functions for the system administrator for administering the user
profiles (user roles, permission classes) and audit logs.
Utilities Offers functions for determining the network configuration and for
consistency checks of the EM GX R1.3 database. Under this menu item you
can also configure the media interface.
Options Allows you to define general settings for the type of representation in all the
network views.
Window Contains functions for arranging the window within the EM GX R1.3 main
window and listing the windows open at the moment.
Help Opens the online help manual and the maintenance manual with their
default pages and gives information about the element manager.
Tab. 3.1 EM GX R1.3 File Menu
3.1.2 Toolbar
The toolbar offers quick access to frequently needed functions.
To hide the toolbar
Select “View” “Toolbar” from the main menu.
For more information, refer to the context-sensitive online help.
To view the online help topic

1. Click “Help” “Operation Manual” from the main menu.
2. Click “View” menu item “Toolbar” in the navigation pane.
A50010-X3-E120-7619 21
3.1.3 Status Bar

The status bar is used for system messages and status displays.
To hide the status bar
Select “View” “Status Bar” from the main menu.

2. Click “View” menu item “Status bar” in the navigation pane.
3.2 Viewing the Access Network

The access network is presented to the user in the form of different views. The views
offer information and status about the network.
The following views are available:

• DCN view
• Equipment view.
Information for network administration task and network monitoring can be found in the
following sections:
• 3.2.1 DCN View for SNMP Network Elements
• 3.2.2 Equipment View
• 3.2.3 Zooming the Display
• 3.2.4 Setting View Options
SNMP
DCN View
Equipment
View
NE
Fig. 3.2 Views of Element Manager GX R1.3
3.2.1 DCN View for SNMP Network Elements

The DCN view for SNMP-NEs cannot be created automatically on initial startup of the EM
GX R1.3 server since the IP addresses of the network elements are not yet known. The
IP addresses are managed by the network providers and are assigned to the NEs when
they are commissioned. (Commissioning subracks is described in the accordingly ITMN,
UMN:ITMN, see Section “1.3 Related Documentation"). Providing the IP address to the
EM GX R1.3 server is part of adding an NE to the DCN network view. For more
information, see Section “4.1 Adding a Network Element".
After initial startup, only the port icon is shown in the DCN view. Each individual NE must
then be inserted and configured.
22 A50010-X3-E120-7619
All the inserted NEs are sorted by IP address.
To open the DCN view
Select “View” “SNMP DCN View” from the main menu.
Fig. 3.3 SNMP DCN View
For more information about the SNMP DCN view, refer to the context-sensitive online
help.

2. Click “Show the navigation pane” link.
3.2.2 Equipment View

The Equipment view shows the component hardware of an NE (see Fig. 3.4). Each plug-
in unit (module) is labeled with the name and slot number. A colored circle indicates the
severity of any alarms. There is a status bar which shows the NE name or the line
indexes for a particular plug-in unit.
To open the Equipment view

1. Select an NE in the SNMP-DCN view.
2. Select “View” “Equipment View” from the main menu.
A50010-X3-E120-7619 23
Fig. 3.4 Equipment View for Network Element (Example)
From the equipment view, you can configure individual plug-in units. For more informa-
tion, see Section “5.2 General Instructions for Configuring Plug-in Unitst".

2. Click “View” menu item “Equipment View” in the navigation pane.
3.2.3 Zooming the Display

For each view window, you can zoom the display in or out. You can select predefined
zoom factors or define your own.
To change the zoom factor
Click “View” “Zoom” from the main menu.
A zoom factor of 100% is the default. You can change the default value. For more infor-
mation, see Section “3.2.4 Setting View Options".

2. Click “View” menu item “Zoom” in the navigation pane.
3.2.4 Setting View Options
24 A50010-X3-E120-7619
For all views, you can define the default settings for the EM GX R1.3 display.
These include the following:

• NE designation in the DCN view
• Font style (type, variant, size, color, attributes) in the DCN view
• Zoom factor when opening the DCN or equipment view
Modified settings are associated with the user login. This means, every operator can
create his or her own settings for the screen display.
To set view options
1. Select “Options” “View Options” from the main menu.
Fig. 3.5 “View Options” Dialog

2. Determine the default options.
3. Set icon text, icon font, and zoom options for the DCN view.
4. Set zoom factor for the equipment view.
5. Click “OK”.
For more information, refer to the context-sensitive online help by clicking the “Help”
button.
3.3 Node Configuration

The “Node Configuration” dialog is divided into a menu bar and the left and the
configuration dialog options on the right. This dialog is used to make the general
configuration settings for the NE as a whole as well as for individual plug-in units and
their interfaces. Fig. 3.6 shows an example of the “Node Configuration” dialog.
A50010-X3-E120-7619 25
Module
Selector
Menu bar
Fig. 3.6 “Node Configuration” Dialog
Use the menu bar to navigate between the various subsections. Clicking on a network or
subscriber interface opens the general NE parameters for the first (lowest numbered
slot) plug-in unit with that interface type.

2. Click “Configuration” menu item “Node Configuration” in the navigation pane.
Displays the general NE parameters for the entire network element. From here
you can access the NE configuration options. For more information, see
Section “4 Configuring Network Elements".
Displays the module options for the NE plug-in units. Here you can lock and
unlock plug-in units, and change the PIU type. Use module to select the plug-in
unit you want to modify. For more information, see Section “5.2 General
Instructions for Configuring Plug-in Units".
Displays the interface configuration for Ethernet ports (except the outband
interface). Use module to select the plug-in unit with the interface you want to
configure. For more information, see Section “5.2 General Instructions for
Configuring Plug-in Units".
Displays the interface configuration for ADSL ports. Use module to select the
plug-in unit with the interface you want to configure. For more information, see
Section “5.2 General Instructions for Configuring Plug-in Units".
26 A50010-X3-E120-7619
Displays the interface configuration for SHDSL ports. Use module to select the
plug-in unit with the interface you want to configure. For more information, see
Section “5.2 General Instructions for Configuring Plug-in Units".
Tab. 3.2 Node Configuration Menu
3.4 Working with Layout Sets

You can define, save, and load layout sets for open DCN and equipment views within the
EM GX R1.3 main window. All desired views can be opened automatically upon starting
the EM GX R1.3 client. The windows are arranged exactly as defined. The window layout
set does not apply to any other windows other than the DCN view and the equipment
view.
For more information about this dialog, refer to the context-sensitive online help by click-
ing “Help” button.
To open the “Windows Layout Set” dialog
Select “Options” “Load/Save window layout set” from the main menu.
Fig. 3.7 “Window Layout Set” Dialog
You can save the current screen layout. This becomes the default layout set when you
start the EM GX R1.3 client. Stored layout sets are unaffected.
To save the current layout set

1. Open the “Windows Layout Set” dialog.
2. Enable “Save current window layout on exit”.
3. Click “OK”.
If you share the terminal and log in with a number of other operators, you may want to
save your screen layout as one of the layout sets. Or you may have different screen
configurations for different tasks.
To save a layout set
A50010-X3-E120-7619 27
1. Open all the views that you would like to include in the layout set and arrange the
windows within the EM GX R1.3 main window.
3. Select a number for the windows layout set.
4. Click “Save current layout set”.
If the number you selected is different from the current layout set, the EM GX R1.3
prompts you to confirm the selection.
- Click “Yes” to store the layout set under the new layout set number.
- Click “No” to store the layout set under the current layout set number.
5. Click “OK”.
To load a layout set

2. Select a layout set number.
3. Click “Load selected layout set”.
4. Click “Yes”.
All the views and dialogs open in the EM GX R1.3 main window close and all the
views defined in the layout set open.
3.5 Access Restrictions

Only an operator with system administration rights has unrestricted access to the NEs.
The initial startup of the EM GX R1.3 can only be carried out by an operator who has
system administration rights.
Access permission for operators who do not have administrator rights must be granted by
an operator with system administrator rights as described in the System Administration
manual, see Section “1.3 Related Documentation". Access rights may be defined at a
global level (across multiple ACI products). In this case, the system administrator may not
have the right to change access restrictions. For more information, refer to the
Administration Manual ADMN, UMN:ADMN.
3.5.1 Definitions
Domain
An EM GX R1.3 management domain is a subset of NEs with different access rights and
permissions defined in the EM GX R1.3 system. Management domains are used to
restrict the access rights of NEs for groups of EM GX R1.3 users. Different EM GX R1.3
management domains may overlap.
Global domain
There is a special EM GX R1.3 management domain called Global domain which
consists of all NEs in the access network. This domain is automatically created on initial
startup of the EM GX R1.3.
28 A50010-X3-E120-7619
Permission
Ability of the operator of the EM GX R1.3 to execute a command.
Permission class
Commands (menu items) in the EM GX R1.3 are grouped into configurable permission
classes.
System administration permission class

There is a special permission class called System Administration which is created
automatically after initial startup of the EM GX R1.3 which consists of all commands of
the EM GX R1.3.
3.5.2 Types of Access Restriction

Access permission is controlled on the EM GX R1.3 server by permission classes in
connection with domaining. Operator’s access rights are restricted by permission classes,
by domains or by combination of both:
Access restriction by permission class

Access restriction by permission class only affects which commands (menu items) you
can use. The commands which are not allowed by your permission class are disabled
(grayed out).
Access restriction by domain

Access restriction by domain means that you can only access NEs which are part of your
domain.
Fig. 3.8 shows NEs in a DCN view. Some of the NEs are in your domain and some others
are not in your domain.
NEs in your domain
NEs not in your domain
Fig. 3.8 NE Representation in a View
Different NE representations include the following:

• NEs in your domain are not faded, access is allowed.
• NEs not in your domain are faded and not selectable, access is not allowed.
A50010-X3-E120-7619 29
Modifications to domain administration are not dynamically updated in the DCN view of
the operator. The operator must close and open the view again to see the changes.
The status bar at the bottom of the EM GX R1.3 main window is not domain specific.
Thus the highest alarm severity, for example, reflects the entire SNMP port, not just your
domain.
3.5.3 Access in the Domaining Context
There are three possibilities for executing a command in the domaining context:
• The network element is not in your domain. The NE is grayed out and you cannot
select it.
• The network element is in your domain but you do not have permission to execute
certain commands in that domain. You can select NE, but menu items are disabled.
• The network element is in your domain and you have permission to execute certain
commands. The NE is selectable and some menu items are also enabled, enabling
you to execute the command.
If you select multiple NEs you may have different permissions on NEs. In this case,
the menu command is still enabled, but when executed, a message box appears with
a list of all network elements for which the operation is not permitted. The selected
operation is executed only on those network elements for which you have permission.
The NEs belong to different domains to which you have access, but different
permission classes.
3.6 LCT Access

When your OS server is defined as an LCT in the SNMP configuration file, your session
is defined as an LCT session when you connect to the network element. An LCT session
has following effects:
• No other LCT system can connect
• OS systems (TMN) have read-only access.
Any current superterminal flag is reset. Other users receive the message:
SNMP General Error.
The LCT session login remains until one of the following occurs:
• 15 minutes pass with no read or write attempts by the LCT.
Under the default settings, this time out never occurs. The ACI polls the hiX 563x with an
SNMP get request (in other words a read attempt). The default polling rate under the
SNMP settings is every 10 minutes.
3.7 Element Manager GX R1.3 Online Help

The EM GX R1.3 client online help system offers detailed information about all operation
tasks (configuration, saving and downloading data) of the SNMP NEs and the graphical
users interface. It is used to look up information relating to particular subjects and to
branch to related topics.
To search in a structured way for help

1. Select “Help” “Operation Manual” menu item (see Fig. 3.9) or the associated icon in
the toolbar.
30 A50010-X3-E120-7619
Fig. 3.9 “Help” Menu Item in the Main Window

2. The online help opens with its default page, see Fig. 3.10.
Within this dialog you can search for help in the following ways:
• Via the navigation pane on the left-hand side
Here the help text is subdivided into subject fields. The book symbols can be opened
via mouse-click to display the subordinated topics. Click any topic to open the
associated page. The content is displayed on the right-hand side.
• Via the index
Enter a term in the entry field. After confirming all assigned terms are displayed.
• Via the full text search for specific terms
Select any letter. All files with the selected letter combination are displayed on the
navigation pane.
Fig. 3.10 Default Page of the Online Help
Context-sensitive help
All important EM applications have a “Help” button with which you can open the online
help page for the opened dialog. Here you will find detailed information. For navigation
within the online help, click “Show navigation pane” link (after opening the first time) to
open the navigation pane. When the navigation pane is opened you can branch from this
A50010-X3-E120-7619 31
to all the other topics.
32 A50010-X3-E120-7619
4 Configuring Network Elements

This section provides instructions for the configuration of hiX 563x subracks. It contains
the following topics:
• 4.1 Adding a Network Element
• 4.2 Deleting a Network Element
• 4.3 Editing SNMP Settings
• 4.4 Configuring a Network Element
• 4.5 Setting the Date and Time
• 4.6 Ethernet Parameters
• 4.7 Network Ethernet Alarm Configuration
• 4.8 Configuring the Outband Management Channel
4.1 Adding a Network Element

To commission a new NE, follow the procedures outlined in the ITMN, see Section “1.3
Related Documentation". Once you have commissioned the NE and assigned an IP
address, you can make it known to the EM GX R1.3 server by adding it to the SNMP-
DCN view.
If you do not have permission to access the network element, the network element is
displayed in the SNMP-DCN view as unavailable or disconnected. You must be sure the
EM GX R1.3 server is entered in the SNMP configuration file for the NE on the FTP
server.
You can add single NEs or you can add several at the same time using autodiscovery or
mass provisioning.
4.1.1 Adding a Single Network Element

To insert an NE
1. Open the SNMP-DCN view.
2. Select the SNMP port and select “Configuration” “Insert SNMP NE” from the main
menu.
The “Insert SNMP network element” dialog appears.
3. Enter all the required information according to the planning documentation. For more
information, refer to the context-sensitive online help, by clicking the “Help” button.
If you want to change the IP address on working state of the LCT, please use the pro-
cedures described in topic “Changing the IP address on LCT" below.
4. Click the “SNMP Settings” tab.
The SNMP settings are displayed.
5. Enter all the required information according to the planning documentation. For more
information, refer to the context-sensitive online help, by clicking the “Help” button.
A50010-X3-E120-7619 33
6. Click “User settings” tab, enter the path to the FTP server(s) root directory, and the
FTP authorization.
User settings are not available until the NE type is set.
For more information, refer to the context-sensitive online help, by clicking the “Help”
button.
7. Click “Apply”.
8. Click “Close”.
The ACI searches for the NE by its IP address and downloads its status, as outlined in
Section ”7.1.2 Synchronization State". When this process is complete, the NE icon
appears in the DCN View, and the NE status is fully verified. If unsuccessful, run a
consistency check to identify the error. See Section “10.1 Starting a Consistency Check".
If the status fully verified is not achieved after synchronization, check the IP
address and the NE type. Both values cannot be corrected in the dialog box. If the
entries are incorrect, you must delete the NE and create it again.
Changing the IP address on LCT

For changing the IP address on LCT the following sequence must be done:
1. Stop all ACI-E EM GX R1.3 LCT server processes, see Section “2.2 Starting and
Stopping the EM GX R1.3 Server Processes".
2. Change the IP address, see “To insert an NE” above.
3. Restart all ACI-E EM GX R1.3 LCT server processes.
4.1.2 Mass Provisioning of SNMP NEs

Mass provisioning enables you to add multiple NEs based on the content of an ASCII file.
You must create this file before you can execute the mass provisioning command.
To create a mass provisioning file

1. Use a text editor to create a new file.
2. Create an entry for each NE you want to add.
You can enter a number of attributes for a single NE on a line. Only the first two
attributes are mandatory. For more information, refer to the context-sensitive online
help by clicking the “Help” button.
3. Save the file on your FTP server.
To add new SNMP NEs by mass provisioning

1. Select the SNMP port in the SNMP-DCN view.
2. Click “Configuration” “Mass Provisioning” from the main menu.
The “SNMP Mass Provisioning” dialog appears.
34 A50010-X3-E120-7619
Fig. 4.1 “SNMP Mass Provisioning” Dialog

3. Enter the path and filename of the file containing the mass provisioning data.
button.
4. Click “Start”.
4.1.3 Autodiscovery of SNMP NEs

Autodiscovery enables you to automatically add new SNMP NEs by means of a Net
Scan. Net Scan scans a single sub network within a given range of IP addresses and
detects any SNMP NEs of the specified types.
Net Scan only detects SNMP NEs which have MIB identifiers and the corresponding MIB
variables which are known by the EM GX R1.3 software.
To autodiscover SNMP NEs

2. Click “Configuration” “SNMP Net Scan” from the main menu.
The “SNMP NetScan” dialog appears. See Fig. 4.2.
A50010-X3-E120-7619 35
Fig. 4.2 “SNMP NetScan” Dialog
3. Enter the IP address you want to scan using zeros as variable.

4. Use the subnet mask attribute to enter the range of addresses you want to scan.
button.
5. Click “Add/Remove”.
The “Add NE Type” dialog appears.
Fig. 4.3 “Add NE Type” Dialog
6. Select the NE types for which you want to scan.

7. Click “OK”.
The NE type appears in the “SNMP NetScan” dialog.
Select the NE type and click “Configure” to preset the SNMP settings. If you want to
create or add all NEs which the scan finds, select “Auto create”. For more information,
refer to the context-sensitive online help by clicking the “Help” button.
8. Click “Scan”.
The “SNMP scan” dialog displays when it is finished scanning.
36 A50010-X3-E120-7619
4.1.4 Automatic NE Settings

You can configure the EM GX R1.3 to use the previously used SNMP and user settings
by default instead of the system default settings. The previously used settings appear as
soon as you select the NE type.
SNMP settings are used to determine when an NE is accessible. User settings determine
the path to the FTP server.
To set the default settings

2. Click “Options” “Network Options” from the main menu.
3. Enable the automatic use of the previous SNMP and user settings.
button.
4.2 Deleting a Network Element

When you delete an NE, all information about the NE is removed from the EM GX R1.3
database. All internal subrack configuration is maintained in the subrack database (con-
figurations, etc.) To reintroduce the NE, you must re-add it as described in Section “4.1
Adding a Network Element".
To remove an NE from the ACI database

1. Select the NE icon in the SNMP-DCN view.
2. Click “Configuration” “Delete SNMP NE” from the main menu.
4.3 Editing SNMP Settings

After you have added a network element, you may find the SNMP settings are no longer
appropriate, or you may want to move the FTP server to another host. For this reason,
you can change the SNMP settings of a network element.
You cannot change the IP address, or type of a network element. To do this you must
first delete then add the NE again with the new configuration. For more information, see
Chapter “4.1 Adding a Network Element".
To edit the SNMP settings

1. Select the NE in the SNMP-DCN view.
2. Select “Configuration” “SNMP Settings” from the main menu.
The “SNMP Settings” dialog appears.
3. Edit the NE name if desired.
4. Follow the instructions under Section “4.1.1 Adding a Single Network Element",
making changes as appropriate.
A50010-X3-E120-7619 37
4.4 Configuring a Network Element

The following sections describe configurations that have an impact on the entire network
element:
• 4.4.1 General Network Element Configuration

• 4.4.2 Displaying Equipment Data
• 4.4.3 Editing Inventory Data
4.4.1 General Network Element Configuration

The configuration options listed in this section affect all subscriber lines connected to the
network element. They also help determine what kinds of CPE connections are possible.
Use the procedure below to configure the NE. Refer to the following sections for an
explanation of each configuration.
To set line configuration

2. Select “Configuration” “Node Configuration” from the main menu.
The “General NE parameters” dialog appears.
3. Click “Configuration” tab (see Fig. 4.4).
Fig. 4.4 “Configuration” Tab
4. Set the following options:

- Code type
- Transmission capabilities or write NE data.
38 A50010-X3-E120-7619
button.
4.4.2 Displaying Equipment Data

You can view the inventory data for the NE (node) and the modules.
To view note data (name and version)

1. Selecting the NE in the SNMP-DCN view.
2. Select “Configuration” “Equipment Data” from the main menu.
The “Equipment Data” dialog appears.
button.
To view module data (hardware and software)

1. Select the NE in the SNMP-DCN view. Open the “Equipment View”.
2. Select the module in the “Equipment View” and choose “Configuration” “Equipment
Data” from the main menu.
button.
To view inventory data of the whole NE

2. Select “Utilities” “Show Inventory Data” from the main menu.
The “Show Inventory Data” dialog appears.
button.
4.4.3 Editing Inventory Data

You can add information to the inventory data for an NE to make it clearer to other
operators, where a particular NE is located and other identifying information.
To edit inventory data

2. Select “Configuration” “Equipment Data” from the main menu.
The “Inventory Data Configuration” dialog appears.
3. Enter any parameters.
button.
4.5 Setting the Date and Time

A manual synchronization of the date and time is required only in special cases. For
A50010-X3-E120-7619 39
example, if you have to reconfigure the time on the EM GX R1.3 server host, you may
want to manually synchronize the NE with the server host.
Synchronization between the EM GX R1.3 and the NE is normally done every 24 hours.
To set the time and date

2. Select “Configuration” “Node Configuration” from the main menu.
The “General NE parameters” dialog appears.
3. Click “Date/Time”.
4. Click “Synchronize NE”.
This forces a synchronization between the EM GX R1.3 and NE.
button.
4.6 Ethernet Parameters

The Ethernet NNI interface enables you to configure additional parameters for the net-
work element. These are available for CXU Ethernet. This section includes the following
topics:
• 4.6.1 VLAN Stacking

• 4.6.2 MAC Address Translation
• 4.6.3 Class of Service Support
4.6.1 VLAN Stacking

The hiX 563x system supports VLAN stacking. This enables you to use the outer tag as a
service identifier and the inner tag as a PVC identifier. Essentially, this enables you to
mimic the VP/VC identification of the ATM system. With the service identified, you can
route voice over IP traffic to a voice gateway, and fast Ethernet traffic to a BRAS. VLAN
tagging is only supported in multi-PVC mode.
You can configure the EtherType and user priority of the outer VLAN tag. This is known
as the SVLAN. The inner VLAN tag uses the EtherType 0x8100. It is known as the
PVLAN. If only one VLAN tag is needed, you can disable this feature by setting the PV-
LAN ID to 4095. The previous hiX 563x system versions recognize the SVLAN tag as the
only valid tag.
4.6.2 MAC Address Translation

The hiX 563x system learns the MAC address of subscribers by snooping the packets
hiX 563x system receives from them. Because subscribers switch or alter customer pre-
40 A50010-X3-E120-7619
mises equipment it is difficult for upstream equipment to identify the subscribers beyond a
certain degree of certainty. MAC address translation enables you to assign MAC
addresses to ports, creating a one-to-one correspondence between MAC address and
subscriber connection.
MAC address translation is supported on the following plug-in units:

• CXU-B
• CXU-C
Once you enable MAC address translation and set the DSLAM ID, you must restart the
hiX 563x in order for the change to take effect.
The network MAC address assigned is based on the DSLAM ID assigned at the Ethernet
interface. A specific subscriber MAC address may not always be assigned exactly the
same network MAC address. After a restart or after a subscriber times out, the sub
scriber may be assigned a new index number when the subscriber begins to send frames
upstream again.
To configure MAC address translation
1. View the Ethernet interface parameters.

For more information, see Section “5.2 General Instructions for Configuring Plug-in
Units".
2. Enable MAC address translation and configure the DSLAM ID.
3. Restart the network element.
button.
4.6.3 Class of Service Support

Historically, Ethernet has had no class of service support. All traffic is handled on a best
effort basis.
The hiX 563x system supports user priority as described in IEEE 802.1D (formerly part of
IEEE 802.1p). This adds 3 user priority bits to the Ethernet frame.
With the user priority bits, you can define the traffic types described in Tab. 4.1.
A50010-X3-E120-7619 41
User Priority Bits Traffic Type Default Description

Value Queue
0 0 0 0 Best effort (default) 1 Lowest priority
1 0 0 1 Background
2 0 1 0 Spare (reserved)
3 0 1 1 Excellent effort 2 For higher priority subscribers
4 1 0 0 Controlled load 3 For latency and throughput

sensitive applications which may be
5 1 0 1 Video
subject to admission control
6 1 1 0 Voice 4 Highest priority
7 1 1 1 Network control
Tab. 4.1 User Priority and Default Queues

The hiX 563x maintains four queues for processing the user priority bits. You can freely
assign the user priorities to different queues. The queues are handled with strict priority.
As long as a higher priority queue has frames to process, it is served first: 4 before 3, 3
before 2, and 2 before 1.
Frames without a VLAN tag and therefore without a user priority value are treated as
best-effort traffic.
You can assign user priority to the four queues in the upstream and downstream
directions of the Ethernet network interface. In the downstream direction, the mapping is
applied globally for the entire interface. In the upstream direction, you can set the traffic
priority on a VLAN basis.
To configure user priority for the downstream direction

1. View the Ethernet interface parameters.
For more information, see Section “5.2 General Instructions for Configuring Plug-in
Units".
2. For each user priority, assign a queue.
For more information, see “6.4.3 Configuring Queue Priority” and refer to the context-
sensitive online help by clicking the “Help” button.
4.7 Network Element Alarm Configuration

For each network element you can configure a number of fault management features.
These determine the alarms severity are given, the configuration of external alarms, and
the high-temperature warning threshold.
42 A50010-X3-E120-7619
Alarm severity profile

This section describes the configuration of alarm severity profiles. For more information
about alarms and alarm management, see Section “8 Fault Management".
The alarm severity profile enables you to adjust the severity of alarms for specific types of
plug-in units or other managed entities. When configuring these units or interfaces you
can assign an alarm profile in which each alarm has an adjustable severity. You can
configure a profile for each and assign them during configuration.
You can create, copy, and modify an alarm severity profile.
To open the “Alarm Severity Profiles” dialog

2. Click “Fault” “Alarm Severity Configuration” from the main menu.
The “Alarm Severity Profiles” dialog appears.
button.
4.7.1 High-Temperature Warning Threshold

If a subrack is subjected to high temperatures (perhaps due to a faulty fan), the central
microprocessor powers off modem units if the critical temperature threshold is crossed.
The network element alerts you to this problem with a ’Unit Failure’ alarm. Once a unit
powers off, you cannot restart the unit until its temperature reaches 70 degrees or lower.
To restart the unit, perform a cold start on the unit reporting the alarm.
To configure the high-temperature warning thresholds

2. Click “Configuration” “Node Configuration” menu item.
The “Node Configuration” dialog appears.
3. Click the “Temperature Alarm Thresholds” tab.
4. Configure the thresholds for the alarm.
button.
Viewing CXU/IU temperatures

To view the current CXU/IU temperatures, view the “Module” tab, see Section “5.2
General Instructions for Configuring Plug-in Units".
4.8 Configuring the Outband Management Channel

The outband management channel is configured when commissioning the network
element. This process does not involve the EM hiX 563x. However, you can assign an
43
alarm severity profile to this interface. You can access the severity index for the outband
interface from the Module window of the CXU, see Section “5.2 General Instructions for
Configuring Plug-in Units". For more information about commissioning network elements,
refer to the Installation and Test Manual ITMN, UMN:ITMN, see Section “1.3 Related
Documentation".
44 A50010-X3-E120-7619
5 Configuring Subscriber Connections

This chapter explains how to configure subscriber connections on the physical layer. Use
these procedures to configure individual plug-in units, and lines. The following topics are
discussed:
• 5.1 Line Profiles
• 5.2 General Instructions for Configuring Plug-in Units
• 5.3 Port Permissions
In order to configure a subscriber line you must configure the following:

• NNI and UNI interfaces - see Section “5.2 General Instructions for Configuring Plug-in
Units".
• Bridge - see Section “6 Bridge Configuration".
5.1 Line Profiles

Line profiles are pre-configured settings for xDSL ports. This profile is used in place of
the normal configuration process. You can use line profiles to define the settings for
different kind of subscriber connections. You can then assign a profile to an individual
port, or you can use mass provisioning to assign a profile to multiple ports on an IU. Line
profiles ensure that you maintain a level of consistency among your subscriber configu-
rations. The line profile is referred to as element manager profile, because it exists on the
element manager server host as xDSL profile.
The ADSL2+ profile is stored on the Element Manager, but refers to four profile types
stored on the network element. The ADSL2+ profile can only be assigned to network
elements with the NE Type hiX 563x R1.3 and later. The four network element profiles,
ADSL ATU profile, Alarm profile, IGMP profile, and Metering profile are used to configure
the ADSL line parameters.
45
Network
Element
Element
Profiles
Manager
Profiles
For hiX 563x R1.3
The ADSL2+ profile consists of a reference to

the ADSL ATU, Alarm, IGMP, and ADSL Exten
sions profiles.
Fig. 5.1 Distribution of Profiles
The SHDSL profile is stored on the element manager also, but refers to two profile types
sotred on the network element. The two network element profiles, SHDSL span profile
and SHDSL alarm profile are used to configure the SHDSL line parameters.
5.1.1 Creating a Line Profile

There are a number of ways to create a line profile:
• During IU configuration (EM profiles only!)
While configuring the IU port, you have the option to save the configuration as a line
profile. To do so configure the line as normal (see Section “5.2 General Instructions
for Configuring Plug-in Units") and click “Save as Profile” under the xDSL line con-
figuration.
• Use the profile configuration tool
This section addresses the profile configuration tool to create profiles. Fig. 5.2 shows
the “Profile Configuration” dialog.
46 A50010-X3-E120-7619
Fig. 5.2 Profile Configuration Tool (Example)
To create an element manager ADSL profile

1. Select the NE in the SNMP-DCN view and click “Configuration” “Profile Configu-
ration” from the main menu.
The “Profile Configuration” dialog appears.
2. Click “EM Profiles”.
3. Select the ADSL2+ line type.
4. Determine if you want to create a new profile or edit an existing profile.
- To create a new profile, click “New”.
- To edit an existing profile, click “Duplicate”.
5. Enter the name of the new profile and click “OK”.
Be sure to provide a name which is descriptive enough that other network operators
understand what kind of profile it is.
6. Configure ADSL2+ parameter.
button.
The line profile is stored in the EM GX R1.3 database.
47
To create a network element ADSL ADU profile or ADSL extensions profile

1. Select the NE in the SNMP-DCN view and click “Configuration” “Profile
Configuration” from the main menu.
2. Click “NE Profiles”.
3. Select the profile type.
4. Select the NE you want to add the profile to.
5. Determine if you want to create a new profile or edit an existing profile.
- To create a new profile, click “New”.
- To edit an existing profile, click “Duplicate”.
6. Enter the name of the new profile and click “OK.
Be sure to provide a name which is descriptive enough that other network operators
understand what kind of profile it is.
7. Configure the profile.
button.
9. Assign the new profiles to an EM ADSL2+ profile.
5.1.2 Applying a Line Profile

You can assign a profile to a port instead of manually configuring the line.
To apply a line profile

1. Select an IU and open the “Node Configuration” dialog.
To open the “Node Configuration” dialog, see Section “7.5 Viewing IU Port Status".
If necessary, select the correct IU from the module selector.
2. Select a line.
3. Double-click the profile attribute and select a profile.
The profile name appears in red text.
4. Click “Apply profile”.
The profile name appears in black text. If an error occurs during the application of the
profile, or if an operator has manually configured the line since the profile was
assigned, the profile status is set to mismatch.
To correct a profile mismatch, reassign the profile. If you reassign a mismatched profile,
all mismatched profiles of the same name on the IU are checked again.
To view the profile log to see which parameters are causing problems, click “Get Profile
Log”.
To clear the profile log, click “Clear Profile Log”.
For more information, refer to the context-sensitive online help by clicking the” Help”
button.
5.1.3 Mass Provisioning
48 A50010-X3-E120-7619
Mass provisioning enables you to apply the same line profile to multiple ports on the
same IU.
To apply a profile to multiple lines

2. Click “EM Profiles”.
3. Click “Assign”.
4. Click “Create”.
The “Create Profile Assignment Order” dialog appears.
5. Select a profile, the target ports and assign.
6. Apply the profiles.
You can select multiple ports and assign them at the same time. For more information
about creating line profiles, refer to the context-sensitive online help by clicking the “Help”
button.
5.1.4 Viewing a Line Profile

Line profiles are stored in the EM GX R1.3 database.
To view a line profile

2. Select “EM Profiles” or “NE Profiles”.
3. Select the profile type and the profile name.
4. View the configured profiles.
button.
5.1.5 Deleting a Line Profile

The only way to delete a line profile is to use the profile configuration tool.
Lines already configured with a deleted EM profile continue to use the same profile con-
figuration, but this profile no longer exists in the database and cannot be assigned to any
49
more lines. The profile status is set to profile missing.
button.
50 A50010-X3-E120-7619
5.1.6 Exporting and Importing a Profile

You can transfer EM profiles from one EM GX R1.3 server to another. You can also
transfer NE profiles from one NE to another. This can be useful if you are expanding your
network or if you want to transfer best practices from one group to another.
button.
5.1.7 Updating a Profile

After you upgrade an NE to hiX 563x R1.3, you can still use the EM profiles for xDSL you
created in the earlier versions. You must upgrade the EM xDSL basic profile to an xDSL
advanced profile.
button.
5.2 General Instructions for Configuring Plug-in Units

The configuration dialogs for all modules consist of several screens. Although the basic
configuration procedures for all PIUs are similar, the individual configurable parameters
are determined by the type of unit.
You can configure a plug-in unit, even if it is not installed in the slot. The settings are
saved in the MIB for later activation. This information is loaded when the corresponding
interfaces are unlocked. You can lock an entire line at once.
When applying any changes, the values entered in all dialogs are saved, including the
entries made on screens that are no longer visible (under the other tabs). Clicking
“Cancel”, by the same token, means that none of the changes made in any of the
screens are saved.
To open the configuration settings dialog for PIUs
1. Select a plug-in unit from the Equipment View.
2. Click “Configuration” “Node Configuation” from the main menu.
3. Select the required interface type (Ethernet, ADSL, SHDSL) and plug-in unit.
4. Select the required tab and configure the attributes.
Use the context-sensitive online help for configuring the attributes.
The contents of the “Node Configuration” dialog varies depending on the plug-in unit
selected. Refer to Tab. 5.1 to determine which sections you must configure for each plug-
in unit.
51
Modules Ethernet ADSL SHDSL
Plug-in Unit
Equipment data
ATU Physical
ATU Channel
ADSL Line
XTU/XRU
Ethernet
Bonding
General
Status
Status
Status
CXUGE:4E:E7 CXU_CGE:E X X X X
IUASDSL:48P:E X X X X X X
IUADSL:72P:IFX X X X X X X
IUADSL:72I:IFX X X X X X X
IUSHDSL:48S:E X X X X X
Tab. 5.1 Plug-in Unit Configuration
5.3 Port Permissions

This feature allows you to view currently configured domain user groups assigned to
specific port and to add domain group to port permissions for IUs.
To vew port permissions
2. Cllick “Security” “Port Permission” from the main menu.
The “Port Permission” dialog opens. The selected NE is shown in the tree.
3. Selecting a single/multiple NE/IU/port on the tree you can review current port
permissions.
4. Click “Close” to close the dialog.
butgton.
To add domain group to port permission
2. Click “Security” “Port Permission” from the main menu.
The “Port Permission” dialog opens. The selected NE is shown in the tree.
3. Selecting a single/multiple NE/IU/port on the tree you can review current port
permissions.
4. Click “Add>>” to add a domain group.
Select domain and check the group to assigned to the selection.
5. Click “OK” to confirm assignment.
52 A50010-X3-E120-7619
button.
53
6 Bridge Configuration
In order to configure a subscriber line you must configure the following:
• NNI and UNI interfaces - see Section “5.2 General Instructions for Configuring Plug-in
Units”.
• Bridge - see this section.
This section explains how to configure bridge connections. The following topics are
discussed:
• Bridge
• STP (spanning tree protocol)
• MSTP (multiple spanning tree protocol)
• VLAN assignment
• QoS (quality of services).
For more information about these topics, refer to the ACI EM GX R1.3 hiX 563x
Information Manual, see Section “1.3 Related Documentation".
6.1 Bridge
This task is used in order to choose the general configuration of the bridge. It contains
the following:
• Configure bridge parameter
• Configure bridge port
• Manage rules
• Manage DHCP provider
• Configure LAG ports
• Configure IPoA ports
• Configure IGMP multicast groups
• Configure broadcast storm control (BCSC)
6.1.1 Configure Bridge Parameter

This task serves to configure general parameter as using of mirror port, default outer
VLAN and tagging mode.
To configure general bridge parameter
54 A50010-X3-E120-7619
2. Click “Configuration” “Bridge Configuration” from the main menu.
The “Bridge Configuration” dialog appears.
3. Select the Bridge icon in the navigation pane.
The “Bridge” dialog opens with the “General” tab.
Change data according your planning documentation.
6.1.2 Configure Bridge Port

This task serves to configure physical ADSL parameter and to set VPI/VCI values.
To configure bridge port
Open the “Port Overview” tab.
This tab lists all created bridge ports and the parameters assigned with the ports.
Via “Delete” you can delete a selected port.
4. Click “Create & Configure”.
The “Bridge Port Configuration” dialog opens.
5. Select the physical ADSL port and set VPI/VCI values.
6. Click “Apply”. The bridge port and the belonging VLAN will be created automatically.
6.1.3 Manage Rules

This task serves to create or delete selected rules.
To manage rules
Open the “Rules” tab.
55
This tab lists all created rules and the parameters assigned with the rules.
Via “Delete” you can delete a selected rule.
4. Click “Create & View”.
The “Rule Configuration” dialog opens.
- Click “New Rule.
Set name, priority and select available pattern to selected action to be planned.
Set the parameter and matching type for selected pattern.
- Click “Create”. The rule will be created.
5. Or click “Expert Mode” to create a expert mode rule.
The “Expert Mode Rule Configuration” dialog opens.
- Click “New Rule”
Set parameter for available match actions, available no match action (only as
option) and available pattern as planned and add this to the “Assigned..” fields by
“Add” action.
- Click “Create”. The expert mode rule will be created.
6.1.4 Manage DHCP Provider

This task serves to configure or delete selected DHCP providers.
To manage DHCP provider
Open the “DHCP Relay” tab.
This tab lists the DHCP providers.
Via “Delete” you can delete a selected provider.
4. Select a provider and click “Create & Configure”.
The “DHCP Provider Entry Configuration” dialog opens.
Change the parameter.
5. Click “New Provider”.
Set the parameter.
56 A50010-X3-E120-7619
6.1.5 Configure LAG Ports

This task serves to configure LAG ports.
To configure LAG ports
Open the “LAG” tab.
This tab shows the LAG ports and the bridge ports tree.
Via “<<Add or Remove>>” you can add bridge port to the LAG port or remove bridge
ports from the LAG port.
4. Select a port and click “Configure LACP”.
The “Bridge Port LACP Parameter Configuration” dialog opens.
Set the parameter.
6.1.6 Configure IPoA Ports

This task serves to configure ADSL ports as IPoA ports.
To configure LAG ports
Open the “Port Overview” tab.
This tab lists all created bridge ports and the parameters assigned with the ports.
4. Select a subscriber port and click “Create & Configure”.
The “Bridge Port Configuration” dialog opens.
57
The selected bridge port will be displayed.
You also can create a new bridge port in this dialog without selecting it before.
Choose the asigned ADSL and bridge parameter. Select a PVID from the drop-down
list.
5. Select IPoA from the “Mode” drop-down list and assign a MAC address to the
selected port.
6. Confirm with “Apply” and click the “Configure VLAN” link.
The “VLAN Configuration” dialog opens.
7. The VLAN selected in step 4 is marked. Add the bridge port selected in step 4 to
the VLAN.
8. Enter the default gateway IP address for the selected VLAN and confirm with “Apply”.
6.1.7 Configure IGMP Multicast Groups

This task serves to configure mulicast groups.
To add new package to IGMP multicast group
Open the “IGMP” tab.
This tab shows the joined subscibers with assigned multicast groups.
Via “Delete” button you can delete a selected group.
4. Click “Configure Package & Groups”.
The “Package” tab opens.
Select a package group from the tree, enter a package name.
Via “Delete” button you can delete a selected package.
The new package is inserted below three node “Package”.
6. Open the “Groups” tab.
Expand the “Package assignment>>” action field, select the new package and click
“>>Add”. The new package is inserted below tree node “Groups”.
58 A50010-X3-E120-7619
Via “Delete” button you can delete a selected group.
To configue IGMP multicast groups
Open the “IGMP” tab.
Ths tab shows the joined subscribers with assigned multicast groups.
4. Select a group and click “Configure Packages & Groups”.
5. Open the “Groups” tab.
Select a group node from the tree, enter a name, multicast IP address and select a
service provider.
6. Add or remove IGMP multicast packages to or from the group.
6.1.8 Configure Broadcast Storm Control (BCSC)

This task serves to configure broadcast storm control.
To configure BCSC
Open the “BCSC” tab.
This tab shows the created broadcast storm controls.
Via “Delete” button you can delete a selected control.
4. Select a control and click “Create & Configure”.
The “Broadcast Storn Control Configuration” dialog opens.
Select the brigde port in the tree and choose the parameter.
59
6.2 EREP/MSTP
This task is used in order to configure ERP (Ethernet ring protection) domain, VLAN
assignment, CIST (common internal spanning tree) bridge parameter and MST (multiple
spanning tree) instance parameter. It contains the following:
• Configure ERP domain
• Swap port roles of an ERP domain
• Configure CIST bridge parameter
• Configure CIST port parameter
• Configure MST region parameter
• Configure MST instance parameter
• Configure MST instance port parameter
• Manage assignment VLAN to ERP domain
• Manage assignment VLAN to MSTP domain
6.2.1 Configure ERP Domain

This task serves to configure, enable and disable ERP domains and to swap roles.
To configure ERP domain
3. Select the ERP/MSTP icon in the navigation pane.
Open the “ERP” tab.
This tab lists all ERP domains.
Via “Enable”/”Disable” you can enable/disable a selected domain.
4. Click “Configure”.
The “ERP Domain Configuration” dialog opens.
Select an ERP domain and choose the editable parameter according your planning
documentation.
60 A50010-X3-E120-7619
Select an ERP domain and chose the editabl parameters according your planning
documentation.
6.2.2 Swap Port Roles of an ERP Domain

This task serves to swap roles.
This task is only enabled if the protection of the ERP domain is enabled.
To swap roles of the ERP domain
Select an ERP domain.
6.2.3 Manage Assignment VLAN-ERP ( from ERP)

This task serves to assign VLAN to ERP domain.
To assign VLAN
Select an ERP domain or continue according to step 5.
4. Click “VLAN Assignment” and continue according to step 7.
61
Select an ERP domain.
6. Click “VLAN Assignment”.
7. The “ERP - VLAN Assignment” dialog opens.
Click “Get” to verify the displaying.
6.2.4 Configure CIST Bridge Parameter

This task serves to configure CIST bridge parameter.
To configure CIST bridge parameter
Open the “CIST” tab.
Specify the CIST parameter.
Via the “Reset TC” button you can reset the topology change flag.
6.2.5 Configure CIST Port Parameter

This task serves to configure CIST port parameter.
To configure CIST port parameter
Open the “CIST” tab.
4. Click “Configure Ports”.
The “CIST Port Configuration” dialog opens.
62 A50010-X3-E120-7619
5. Select a CIST port and specify the parameters.
6.2.6 Configure MSTP Region Parameter

This task serves to configure MSTP region parameter.
To configure MSTP region parameter
Open the “General” tab.
Specify MSTP region name and revision level.
6.2.7 Configure MSTP Instance Parameter

This task serves to configure MSTP instance parameter.
To configure MSTP instance parameter
Open the “MST” tab.
This tab lists all MSTP instances.
The “MST Instance Configuration” dialog opens.
5. Select a MSTP instance and specify the bridge priority.
Via the “Reset TC” button you can reset the topology change flag.
63
6.2.8 Configure MSTP Port Parameter

This task serves to configure MSTP port parameter.
To configure MSTP port parameter
This tab lists all MST instances.
5. Select a MSTP instance.
Select a port MSTP instance and specify port priority and path cost.
64 A50010-X3-E120-7619
6.2.9 Manage Assignment VLAN-MSTP (from MSTP)

This task serves to assign VLAN to MSTP domain.
To assign VLAN
Select a MSTP instance.
5. Click “VLAN Assignment”.
6.3 VLAN
This task is used in order to create, delete, configure and manage VLAN assignment.
It contains the following:
• Create VLAN
• Configure VLAN
• Delete VLAN
• Manage VLAN assignment - ERP
• manage VLAN assignment - MSTI
6.3.1 Create a VLAN

This task serves to create a VLAN.
To create VLAN
3. Select the VLAN icon in the navigation pane.
Open the “Overview” tab.
65
This tab lists all created VLANs.
The “VLAN Configuration” dialog opens.
5. Select a VLAN, set the VLAN parameter and add ADSL ports to the VLAN to be
created.
66 A50010-X3-E120-7619
6.3.2 Configure VLAN

This task serves to configure VLAN.
To configure VLAN
Select the VLAN to be configured.
The “VLAN Configuration” dialog opens with the selection of the tree on the left side.
5. Change VLAN parameter and add/remove ADSL ports to/from the VLAN to be
changed.
6.3.3 Delete VLAN

This task serves to delete selected VLAN.
To delete selected VLAN
Select the VLAN to be deleted.
4. Click “Delete”.
6.3.4 Manage Assignment VLAN-ERP
67
This task serves to assign VLAN to ERP domain.
To assign VLAN
Select the VLAN to be assigned.
4. Click “Assign ERP”.
The “ERP - VLAN Assignment” dialog opens.
5. Change assignment and click “Apply”.
6.3.5 Manage Assignment VLAN-MSTI

This task serves to assign VLAN to MST domain.
To assign VLAN
Select the VLAN to be assigned.
4. Click “Assign MSTI”.
The “MSTI - VLAN Assignment” dialog opens.
5. Change assignment and click “Apply”.
6.4 QoS (Quality of Service)
68 A50010-X3-E120-7619
This task is used in order to configure bridge mode, queue priority and queue mapping.
It contains the following:
• Configure bridge mode
• Configure queue mode
• Configure queue priority
• Configure queue mapping.
6.4.1 Configure Bridge Mode

This task serves to configure bridge mode for ’QoS’ feature.
To configure bridge mode
3. Select the QoS icon in the navigation pane.
The “General” tab appears.
Change bridge mode according to your planning documentation.
6.4.2 Configure Queue Mode

This task serves to configure queue mode.
To configure queue mode
Select the queue mode to be changed. Double click on assigned “Mode” field opens a
drop-down list. Change the required values. The changed values will be displayed in
red color.
69
6.4.3 Configure Queue Priority

This task serves to configure queue priority.
To configure queue priority
Select the queue priority to be changed. Double click on “Uplink queue”/”Downlink

queue” field opens a drop-down list. Change the required values. The changed values
will be displayed in red color.
6.4.4 Configure Queue Mapping

This task serves to configure queue mapping.
To configure queue mapping
Select the queue to be changed. Click on “Weight”/”Watermark low”/”Watermark high”

field shows a drop-down list. Open the list and change the required values.
70 A50010-X3-E120-7619
7 Monitoring the hiX 563x R1.3 System

The Element Manager GX R1.3 user interface provides numerous ways to check the
status of the hiX 563x system and its parts.
The section includes the following topics:
• 7.1 Status and State Changes
• 7.2 Viewing NE Status in SNMP-DCN View
• 7.3 Viewing Plug-in Unit Status
• 7.4 Viewing Network Interface or Interlink Status
• 7.5 Viewing IU Port Status
• 7.6 Inventory Data
• 7.7 Customer Information
7.1 Status and State Changes

Status and state changes of network elements and their components are indicated visu-
ally in all the views and in the status bar of the EM GX R1.3 main screen. The Element
Manager GX R1.3 displays the following states:
• 7.1.1 Alarm State
• 7.1.2 Synchronization State
7.1.1 Alarm State

Alarms are spontaneous messages which are sent unsolicited by an NE to the EM GX
R1.3 server as soon as an alarm state is identified. Fault management of the EM GX
R1.3 distinguishes the following states for each alarm on, off, acknowledged.
For more information about
• Alarm management and propagation
See Section “8 Fault Management"
• Alarm severity profiles
See Section “4.7 Network Element Alarm Configuration"
• Troubleshooting alarms
See Section “10 Troubleshooting"
and the context-sensitive online help.
71
7.1.2 Synchronization State

This state display gives information about synchronization between the object in the
database (MIB) of the EM GX R1.3 and the physical NE in the network. For more
information, refer to the context-sensitive online help.
The EM GX R1.3 starts to verify the NE information as soon as you notify the EM GX
R1.3 of the NE’s IP address. When the NE is inserted (see Section “4.1 Adding a
Network Element"), the EM GX R1.3 searches for the NE and uploads NE data.
Next, the Element Manager GX R1.3 makes the following settings:
• Trap flow control to All Traps
• Sets the TMN or LCT connected flag
• Sets external time
• Sets the time zone.
The NE’s state is then set to fully verified, and it’s IP address is added to the EM
GX R1.3 polling list.
To bring up the line card and inventory informtion, approxcimatly 1 or 2 minutes are
taken.
If consistency check is doen before collecting these data, the result of consistency check
will be displayed with inconsistent. In this case, you cannot use any menus on its NE.
To ensure all necessary data are collected, use ‘show upgrade table’ command on
CLI.
The connection between the network element (NE) and the EM GX R1.3 network
operating system is automatically monitored by polling the NE on a regular basis. When
the polling fails (times out) the operational state of the NE is set to offline and the EM
GX R1.3 marks the relevant equipment with an X. The cause for this state is either a fault
in the DCN or plug-in units were removed. However, the EM GX R1.3 has no way of
distinguishing between the two. As soon as a plug-in unit has been removed, all the
alarms of this plug-in unit are deleted from the alarm list. If the NE is offline, the
alarms of all plug-in units of the NE are removed from the alarm list. When the connection
is re-established (detected by successful polling) the state of the NE returns to NE
reconnected.
A consistency check compares all persistent data of the NE in the EM GX R1.3 database.
For more information about consistency checks, see Section "10.1 Starting a Consistency
Check" and the context-sensitive online help.
After every restart of the EM GX R1.3, the NE sends a notification to the EM GX R1.3 that
it has been restarted. The EM GX R1.3 relearns the information of the NE, and the NE is
then in the EM restarted state. After every warm or cold restart or after a database
reload, the EM GX R1.3 verifies the NE automatically.
72 A50010-X3-E120-7619
In the status bar of the EM GX R1.3 main window, a counter shows the total number of
the NEs/plug-in units in the Disconnected state. For more information, refer to the
context-sensitive online help.
The Element Manager GX R1.3 does not learn the line or far end status of subscriber
connections automatically. They are only learned by viewing the status or interface dis-
play and clicking “Get” or “Update status”. This keeps the amount of status traffic to a
minimum.
7.2 Viewing NE Status in SNMP-DCN View

The SNMP-DCN view provides the general overall status of the NE.
For SNMP NEs the following status changes are indicated visually:
• Alarm state
Color display according to the alarm severity. For more information about the alarm
display, see Section “7.1.1 Alarm State".
• Disconnected state (NE)
Indicated by a red X. For more information, see Section “7.1.2 Synchronization State".
• LCT connected
LCT symbol indicates that another operator has connected with a local craft terminal.
You can only view this NE. For more information, see Section “2.4 Element Manager
GX R1.3 Local Craft Terminal".
• Domain membership
Grayed-out NEs are not in the users domain and cannot be managed.
NE is disconnected
NE Alarm state
NE is connected to an LCT
NE is not in the domain
Fig. 7.1 Status Display in the DCN View
For more information about the DCN view, see Section ”3.2.1 DCN View for SNMP
73
Network Elements".
7.3 Viewing Plug-in Unit Status

Changes in subrack equipment such as newly inserted or removed plug-in units are
automatically detected (but not identified, you must change PIU type manually) by the EM
GX R1.3 and the user interface is updated accordingly. Status changes are indicated
visually.
There are a number of ways to view the status of plug-in units (that is line cards and not
NTs or CPEs):
• Open the equipment view. For more information, refer to the online help.
• Open the node parameters for the NE.
• Open the module view. For more information, refer to the online help.
To view the NE status
2. Click “Configuration” “Node Configuration” from the main menu.
Fig. 7.2 “Node Configuration” Dialog
3. Click
- “Update Status” to update the display.
- “Convert…” to change the xDSL PIU type of a slot (only available after admin.
state was be changed to “lock”).
74 A50010-X3-E120-7619
- “Lock / Unlock” to change the Administrative state.
7.4 Viewing Network Interface or Interlink Status

You view the status of the network interface or interlink by viewing node parameters for
the CXU.
To view the link status
The “Node Configuration” dialog appears. Select the Ethernet icon.
3. Open the Status” or “Ethernet” tab and select the required port.
For more information about the available status information, see the relevant port type
under Section “5.2 General Instructions for Configuring Plug-in Units" and the context-
sensitive online help.
7.5 Viewing IU Port Status

You can get an overview of the status of all ports belonging to an IU by viewing the
“Status” tab of the IUs node configuration.
To view the IU port status
The “Node Configuration” dialog appears. Select the required interface icon.
3. Open the “Status” tab.
75
Fig. 7.3 “Status” Tab of IUADSL (Example)
4. Click “Get” or Update Status” to refresh the displayed data.
This enables the EM GX R1.3 to learn the status of unknown interfaces.
For more information about the available status information, refer to the relevant port type
under Section “5.2 General Instructions for Configuring Plug-in Units" and to the context-
sensitive online help.
7.6 Inventory Data

The configuration of a network is constantly changing, as network elements or modules
are replaced or added, and network elements are loaded with new SW versions. From
time to time, therefore, the network provider may need to retrieve current network data.
For this purpose, EM GX R1.3 provides the inventory data retrieval function. With this
function, the following data can be retrieved from each NE in the network:
• Inventory Data
Here all NE data means equipment designation, equipment type, geographical loca-
tion and loaded software version.
• Label Data (for modules)
This data give information about the HW status as well as previously made changes to
the hardware and firmware.
76 A50010-X3-E120-7619
The named NE data can be retrieved in the following ways:
- Single selection for direct display on your screen, see topic “Viewing Inventory Data"
- Multiple selection/entire network for storage in a file, see Section “7.6 Inventory Data".
Viewing Inventory Data
You can view inventory data for an individual NE. The data are shown in the “Show
Inventory Data” dialog.
To view the inventory data for an NE
2. Click “Utilities” “Show Inventory Data” from the main menu.
The “Show Inventory Data” dialog appears.
Storing inventory data in a file
Data retrieval with storage in a file can be started for a single NE.
To start the data retrieval
Only one automatic retrieval process can be active in the system at any given time!
With larger networks, the data retrieval function can require more time, in which case
the data retrieval should be started during low traffic periods.
2. Click “Utilities” “Store Inventory Data” from the main menu.
The “Select Inventory File” dialog appears.
The file stored in the <ACI-server_Installation>\idr.res\ directory and can be

read using a text editor.
Canceling the inventory data retrieval
You can cancel an active data retrieval process at any time by clicking “Cancel” in the
“Inventory Data Retrieving Progress” dialog.
If this dialog is no longer open, you can reopen it via the “Utilities” “Store Inventory
Data” menu item. A message box (see Fig. 7.4) appears indicating that a retrieval pro-
cess is already active.
77
Fig. 7.4 Message Box for an Actice Data Retrieval
Click “Yes”. The “Inventory Data Retrieving Progress” dialog reopens.
7.7 Customer Information

This feauter allows you to veiew and search for customer information for selected ports
based on given search criteria.
To vew customer information
1. Select the SNMP port or NE in the SNMP-DCN view or plug-in unit in the equipemnt
view.
2. Click “View” “Customer Information” from the main menu.
The “Customer Information” dialog appears.
3. Make sure, that “Keep search results in list” checkbox is not checked.
4. Expand the required branches of the component tree.
To search for customer information
1. Select the SNMP port or NE in the SNMP-DCN view or plug-in unit in the equipment
view.
2. Click “View” “Customer Information” from the main menu.
The “Customer Information” dialog appears.
3. Expand the required branches of the component tree.
4. Enter required search criteria in the search list or put ‘*’ in given column if you like to
search for any string.
5. Click ‘Search”.
The result will be displayted in the list.
6. Right click on a row opens a context-sensitive menu.
78 A50010-X3-E120-7619
- Node configuration: opens “Node Configuration” dialog for port related to the
currently selected customer information in the list.
- Bridge configuration: opens the “Bridge Configuration” dialog for bridge port
related to the currently selected customer information in the list.
- Find NE in tree: selects port, related to the currently selected customer

information in the list, in the component tree.
79
8 Fault Management
Fault management of the EM GX R1.3 supports alarms and event messages. Fault
management shows the operator the availability of the network. The number and the type
of alarms indicate the network availability. NEs send alarms as spontaneous events
(traps) or they can be sent on request. Event messages are either received from NEs or
generated internally due to certain state changes or problems.
This section includes the following sections:
• 8.1 Definitions
• 8.2 Fault Information on the EM GX R1.3 Server
• 8.3 Alarm and Event Notification
• 8.4 Alarm and Event View Administration
• 8.5 Alarm List
• 8.6 Managing Alarm and Event Logs
• 8.7 Alarm Log
• 8.8 Alarm Log on EM Client
• 8.9 Event Log Display
• 8.10 Displaying Alarm and Event Counters
• 8.11 Managing Trouble Tickets
• 8.12 Configuring Fault Options
• 8.13 Alarm Notes
8.1 Definitions
For terms of definitions, refer to the online help in Section “Fault Management”.
8.2 Fault Information on the EM GX R1.3 Server

The server gathers fault information (alarms and event messages) for all managed NEs.
alarms are shown in an alarm list and logged in an alarm log. Event messages are
logged in an event log. The interface to the operator are copies or filtered copies of the
alarm list or of the logs displayed on the Graphical User Interface (GUI) of the EM GX
R1.3 client.
In the further sections the terms alarm list, alarm log or event log refer to copies or
filtered copies of the alarm list, alarm log or event log.
For more alarm information, refer to the online help in Section “Fault Management”.
80 A50010-X3-E120-7619
8.3 Alarm and Event Notification

Event information is recorded as event messages in an event log. You can display a list
of events in the event log.
Alarms are indicated in the graphical user interface in the following locations:
• Color-coded icons of affected units
• Alarm indicator in the status bar
• Alarm list
• Alarm log
• Alarm history
• Alarm life cycle
You can also configure the audible notification of alarms. For more information, see
Section “8.3.2 Media Interface".
In case of NE domaining only alarms from NEs belonging to that domain(s) for which the
operator has permissions are displayed.
8.3.1 Visible Alarm Notification

Alarm severity is signaled by color-coding in the user interface. Acknowledged alarms are
also marked with a check mark. You can change the default colors.
Default alarm colors
Tab. 8.1 shows the default alarm colors in EM GX R1.3.
Alarm severity Color
Clear gray
Acknowledged yellow
Critical red
Major magenta
MInor blue
Warning turquoise
Indeterminate brown
Tab. 8.1 Default Alarm Color
81
The colors are changed in the EM GX R1.3 server and therefore apply to all EM GX R1.3
clients. It is recommended that you standardize the colors as soon as possible after
deploying the EM GX R1.3.
Alarm propagation
If several alarms are reported at the same time for a network element or a component,
the alarm with the highest severity determines the color. Within the network hierarchy, the
alarm with the highest severity is always propagated to the next higher hierarchical level.
A unit (NE, module) always shows the alarm with the highest severity for its subunits.
A colored square in the status bar of the EM GX R1.3 main window signals the alarm with
the highest severity at the moment throughout the entire network. For instance, if this
square is red (critical), this means that the EM GX R1.3 has received at least one critical
alarm. For more information about the status bar, see Section “3.1.3 Status Bar".
If you acknowledge an alarm, the relevant symbol is marked with a yellow

(acknowledged) check mark.
To change the alarm color
1. Clickt “Fault” “Alarm Color Setting” from the main menu. The “Alarm Color Setting”
dialog appears.
2. Select a severity to show the current color setting.

8.3.2 Media Interface
Using the media interface, the EM GX R1.3 operator can signal important alarms and
events audibly (internal beep or sound card).
Use this procedure to configure the basic media interface. Using this interface, you can
enable the media interface and determine what hours it should be in operation. The me-
dia interface enables your client host to play an audio file or a sound when a configured
event occurs.
The following sections describe the ways in which you can use the media interface:
• Configuring the media interface
• Selecting events for the media interface
Configuring the media interface
Click “Utilities” “Media interface...” “Media Configuration.” from the main menu. The
“Media Configuration” dialog appears.
Selecting events for the media interface
82 A50010-X3-E120-7619
You can signal the following events via the media interface:
• All fault management alarms
• The system-internal event message non-accessible NEs.
The alarms or event can be filtered in the network in accordance with NE types, i.e. you
can for example only signal the alarms of a specific NE via the media interface.
To select events
Click “Utilities” “Media interface” “Media Event Configuration” from the main menu.
The “Critical Alarm Configuration” dialog appears.
8.4 Alarm and Event View Administration

Alarms are recorded in the global alarm list and the global alarm log, event messages are
recorded in a global event log. Depending on the number of managed network elements,
these lists can be very long. You can define views for alarm lists as well as alarm and
event logs that display only the information which correspond to the elements you define.
Views are managed in the “Alarm and Event View Administration” dialog.
To open the dialog
Click “Fault” “Alarm & Event View Administration” from the main menu. The “Alarm and
Event View Administration” dialog appears. All alarm and event views are displayed.
For more information for creating, deleting and displaying, refer to the context-sensitive
online help.
8.5 Alarm List

Each alarm is displayed in an alarm list located on the EM GX R1.3 server. The alarm
lists which you open on the EM GX R1.3 clients are copies or filtered copies of the global
alarm list located on the EM GX R1.3 server. In the following sections, global alarm list
and alarm list refers to the alarm lists opened on the EM GX R1.3 client. The display of
these alarm lists is refreshed in configurable intervals.
The alarm list can be opened for
• an entity network
• a selected NE
Multiple selection is not possible.
The alarm list for the entire network is known as the global alarm list. You can only open
83
it once on each EM GX R1.3 client. Depending on the size of the network, it may be a
very long list. However, it is possible to open a subset of the alarm list for selected units
or through a predefined alarm and event view. You can open several of these sublists
simultaneously.
8.5.1 Opening an Alarm List for the Entire Network

Open the alarm list for the entire network
via the icon bar or
via the key combination <Ctrl>+<T> or
via the “Alarm list...” entry in the context menu or
via the “Fault” “Global Alarm List” from the main menu or
via the “Fault” “Alarm List” from the main menu.
8.5.2 Opening an Alarm List for Selected NE

Open the alarm list for the entire network
via the icon bar or
via the key combination <Ctrl>+<T> or
via the “Alarm list...” entry in the context menu or
via the “Fault” “Alarm List” from the main menu.
84 A50010-X3-E120-7619
Fig. 8.1 “Alarm List” Dialog
For more information about this dialog and for operating tasks inside this dialog, refer to
the context-sensitive online help.
8.5.3 Opening the Maintenance Manual

The maintenance manual provides information for alarms, including the cause, system
reaction, and procedures to clear them. You can open this manual with a web browser
from the alarm list.
You must have a web browser installed on your computer in order for this feature to
function.
To open the maintenance manual
1. Right-click an alarm in the alarm list/global alarm list.
2. Select “Maintenance Manual” from the popup menu.
The maintenance manual is also available as a separate document. For more

information, see Section “1.3 Related Documentation".
8.6 Managing Alarm and Event Logs

Alarm and event logs contain data which enable you to see the history of the faults. The
data are not discarded automatically if an alarm or event is resolved.
This dialog enables you to configure the alarm and event log on the EM GX R1.3 server.
85
To open the “Alarm and Event Log Administration” dialog, click “Fault” “Alarm & Event
Log Administration” from the main menu.
In this dialog you can modify the following data:
• log size
• properties if the log is full
• export.
The contents of the log can be deleted via the “Delete” button.
Via “Delete” all entries are removed from the log file. If necessary, export data before
deleting the entries.
Alarm and event log administration tasks should only be enabled for operators with
system administrator rights.
8.7 Alarm Log

All generated alarms are recorded in alarm log. It logs all entries and changes of the
alarms.
The alarm log is installed automatically during the commissioning of the EM GX R1.3
software. The size is set to 10.000 entries and the log full condition is set to “Wrap
around” as default.
The default settings can be changed via the “Alarm Log Administration” dialog.
86 A50010-X3-E120-7619
8.8 Alarm Log on EM Client

The data for the alarm log are located on the EM GX R1.3 server.
Alarm logs opened on EM GX R1.3 clients are copied subsets of the global alarm log.
They are not updated automatically to enable the undisturbed analysis of the alarm
situation. The update must be done manually by fetching new records. Counters must be
updated manually, too.
It can be opened for selected units in the corresponding views or by means of predefined
views.
To open the alarm log for selected NE or plug-in units
Select the desired unit (NE/plug-in unit) and open the alarm log via
• the “Fault” “Alarm Log Display...” entry in the context menu or
• the “Fault” “Alarm Log Display...” from the main menu.
If no unit is selected, the menu is disabled.
To open the alarm log for predefined alarm view
Alarm logs are opened via the “Alarm and Event View Administration” dialog.
• Select “Fault” “Alarm & Event View Administration” from the main menu.
The “Alarm and Event View Administration” dialog appears. All existing views are
listed.
• Select a view and click “Alarm Log”. The alarm log is opened for all elements con-
tained in the alarm view.
Fig. 8.2 shows an example for an “Alarm Log” dialog. The table contains all log entries for
the selected unit or for the elements of the predefined alarm view. The displaying can be
limited via filter options.
The table contains uncolored icon for alarm severity. But it contains a column for a log
date and time.
87
Fig. 8.2 “Alarm Log” Dialog
8.9 Event Log Display
The data for the event log are located on the EM GX R1.3 server. The “Event Log“ dialog
on the EM GX R1.3 client represents only a copy or filtered copy of the event log located
on the EM GX R1.3 server.
Event logs opened on EM GX R1.3 clients are copied subsets of the global event log.
They are not updated automatically. The update must be done manually by fetching new
records. Counters must be updated manually, too.
It can be opened for selected units in the corresponding views or by means of predefined
views.
To open the event log for selected NEs/plug-in units
Select the desired unit (NE/plug-in unit) and open the event log.
• via the “Fault” “Event Log Display...” from the main menu.
If no unit is selected, the menu is disabled.
To open the event log for predefined event view
Event logs are opened via the “Alarm and Event View Administration” dialog.
• Select “Fault” “Alarm & Event View Administration” from the main menu.
The “Alarm and Event View Administration” dialog appears. All existing views are
listed.
88 A50010-X3-E120-7619
• Select a view and click “Event Log”.
Fig. 8.3 “Event Log” Dialog
8.10 Displaying Alarm and Event Counters

Use the “Alarm And Event Counter” dialog to display a summary of the alarms and events
present in the system.
To display the alarm and event counters
1. Click “Fault” “Alarm & Event Counter” from the main menu.
2. The “Alarm and Event Counter” dialog appears.
8.11 Managing Trouble Tickets

Trouble tickets enable you to assign alarms to individual operators. You can then track
these problems, add comments, and prioritize them.
This section includes the following topics:
• 8.11.1 Assigning a Trouble Tickets
• 8.11.2 Viewing All Trouble Tickets
89
• 8.11.3 Adding a Note to a Trouble Ticke
• 8.11.4 Deleting a Trouble Ticket
8.11.1 Assigning a Trouble Ticket

To assign a trouble ticket
2. Click “Fault” “Trouble Ticket Administration” from the main menu. The “Trouble
Ticket Administration” dialog appears. Click “Create...”.
3. The “Trouble Ticket” dialog are opened.
If the alarm already has a trouble ticket assigned to it, the trouble ticket opens. Confirm
with “Yes”. The “Trouble Ticket” dialog keeps open. Then you only can change the ticket.
8.11.2 Viewing All Trouble Tickets

To view a trouble ticket
2. Click “Fault” “Trouble Ticket Administration” from the main menu.
3. The “Trouble Ticket Administration” dialog appears.
All tickets are displayed in the list. The list can be exported or printed.Click “Export” to
export the list of trouble tickets to a comma separated file.
8.11.3 Adding a Note to a Trouble Ticket

You can add notes to a trouble ticket. Some possible uses might be information needed
by the network operator or a list of actions taken to clear the alarm.
You can configure the EM GX R1.3 to add trouble ticket notes automatically. For more
information, see Section “8.12.1 Setting Notepad and Trouble Ticket Options".
Trouble ticket notes do not appear in the alarm log or alarm list dialogs. Only alarm notes
appear there. Trouble ticket notes only appear when viewing a trouble ticket.
To add a note to a trouble ticket
1. Open the “Trouble Ticket” dialog.
For detailed instructions, see Section “8.11.1 Assigning a Trouble Ticket".
90 A50010-X3-E120-7619
2. Click “Add Note”. The “Create TT Node” dialog opens.
Fig. 8.4 “Create TT Note” Dialog
3. Enter the note text and set the priority.
You can import a plain text file instead of typing a note by clicking “Copy from file...”.
Once created, you cannot edit the note text
4. Click “OK”.
8.11.4 Deleting a Trouble Ticket

To delete a trouble ticket
1. Open the “Trouble Ticket” dialog.
For detailed instructions, see Section “8.11.1 Assigning a Trouble Ticket".
2. Select a trouble ticket. You can only delete a trouble ticket which is closed or
close/Ack.
3. Click “Delete”. Confirm the message box with “Yes”.
4. The ticket is deleted from the list.
8.12 Configuring Fault Options

Fault options refer to notepad, trouble ticket and acknowledgement options. It is recom-
mended that these options can only be changed with the permission of the system
administrator.
91
The fault options apply to all EM GX R1.3 clients and to all operators.
This section describes the following topics:
• 8.12.1 Setting Notepad and Trouble Ticket Options
• 8.12.2 Setting Acknowledgement Options
8.12.1 Setting Notepad and Trouble Ticket Options

To set notepad and trouble ticket options
1. Click “Options” ”Fault Options” from the main menu. The “Fault Options” dialog
appears with the “Notepad and Trouble Ticket” tab.
2. Determine the default priority to be used when creating an alarm note.
3. Determine which alarm notepad and trouble ticket options you want to enable.
8.12.2 Setting Acknowledgement Options

To change the acknowledgement options
1. Click “Options” ”Fault Options” from the main menu. The “Fault Options” dialog
appears. Open the “Acknowledgement” tab.
2. Select an alarm list mode.
You must restart the computer before this setting can take effect.
3. Determine if you want to enable operator registration.
Enable this option to display the operator which acknowledged an alarm in the alarm
list or the alarm log.
8.13 Alarm Notes

The alarm notes enable you to record important information associated with an alarm.
Examples include:
• Steps taken to clear alarms
• Test results
92 A50010-X3-E120-7619
• Explanation of operator responsibility assignment
• Explanation of extenuating circumstances needed by other operators.
Notes attached to an alarm are indicated by a symbol in the alarm list, the alarm log, and
trouble ticket view. When alarms are cleared notes are deleted.
Once created, you cannot edit or delete a note.
Each note may contain up to 3200 characters. Up to 20 notes can be attached to one
alarm.
Some notes are created automatically. Automatically created notes can exceed the limit
of 20 notes per alarm. To enable or disable this feature, see Section “8.12.1 Setting
Notepad and Trouble Ticket Optiona".
Notes are created automatically for alarms in the following cases:
- NE name is changed and it has alarms currently associated
- NE is deleted from the database and it has alarms currently associated
- Alarm time is not identically with the time when an alarm was detected
- A cleared alarm is detected again after refreshing an alarm log or list view
- An alarm is detected as cleared twice
- An alarm is determined to be an alternating alarm
- Life cycle of a cleared alarm is terminated due to EM GX R1.3 server restart
- Alarm status changes are detected after list synchronization after a server restart or
the re-establishment of communication with an NE
- An alarm present or present and acknowledged is cleared after refreshing an alarm

log or list view.
8.13.1 Viewing an Alarm Note

You can also view notes from the alarm trouble ticket, if one is assigned. For more in-
formation, see “8.11.2 Viewing All Trouble Tickets”.
To view an alarm note
1. Click on the note symbol in the alarm list or alarm log.
All the notes associated with the life cycle of a selected alarm record are displayed.
The list is sorted in chronological order. At the top of the list is the newest note.
2. Click on one of the note entries and view the contents in the gray display area at the
bottom of the dialog.
To print alarm notes, click Print.
93
You cannot edit an alarm once it is create, but you can change the alarm priority by right-
clicking the note entry and selecting the new priority.
8.13.2 Adding an Alarm Note

You can create alarm notes for all alarms displayed in the Alarm List. For cleared alarms,
you can create notes from the Alarm Log. You can also create notes from trouble tickets,
see 8.11.3 Adding a Note to a Trouble Ticket.
If you are using mode 3 for the alarm list, you cannot create notes for cleared alarms in
acknowledgement mode which were acknowledged again.
To add an alarm note
1. Open the “Alarm Notepad” dialog.
For details, see Section “8.13.1 Viewing an Alarm Note".
2. Click “New”.
3. Enter the note text and set the priority.
4. Click “OK”.
94 A50010-X3-E120-7619
9 Performance Management
With the performance management functions of AccessIntegrator Ethernet, you can
configure and view the following performance management of hiX 563x R1.3 lines:
• Ethernet statistics and performance monitoring
• ATM performance monitoring
• IGMP peformance monitoring
• xDSL (ADSL and SHDSL) performance monitoring
• Upload administration.
For more information about the different types of performance management, see the fol-
lowing:
• 9.1 Ethernet Statistics and Performance Monitoring
• 9.2 ATM Performance Monitoring
• 9.3 IGMP Performance Monitoring
• 9.4 xDSL Performance Monitoring
• 9.5 Upload Administration
Within the hiX 563x for numerous interfaces of the hiX 563x network element there are
performance management counters. These counters tally a variety of measurements, for
example, misinserted cells or errored seconds at the measurement point. For each
measurement point there are two counters:
• 15-minute
• 24-hour
The 15-minute counter totals all occurrences of each measurement at the measurement
point over a 15-minute periods. At the end of every fifteen minutes, the 15-minute counter
values are added to the 24-hour counter if it is enabled.
The counter data is stored in the network element. You can configure the history to
determine how many counter records are stored for each counter. You can retrieve the
counter records from the NE and store them in the hiX 563x R1.3 database for long-term
storage by creating log units. You can then export these to file. For more information
about log units and the administration of log units, see Section “9.6 Managing
Performane Data Logs".
Every PM reporting object in the node, is regularly queried for its counter values. These
values are logged into the hiX 563x R1.3 database. A schedule to query these counter
values automatically may also be configured by the operator. All performance data re-
95
trieved by the logs can be exported to a file. This export function can be configured to
take place automatically as a scheduled job and/or manually on request. For more infor-
mation about schedules, see Section “9.7 Scheduled Tasks for Performance Data".
There is an addition ATM counter type, which is managed independently from the ATM
layer performance counters.
Finally, there are IGMP counters. These counters provide statistics about IGMP host and
router instances.
Additionally, you can monitor port specific PM data in real time. Therefore the following
two types of displays are provided:
• 9.8 Monitoring Counters
• 9.9 All Port Counters
96 A50010-X3-E120-7619
9.1 Ethernet Statistics and Performance Monitoring

This performance management can be divided into two parts:
• Counters for Ethernet uplink interface at CXU module
• Counters for bridge ports at IUxDSL modules.
The hiX 563x system enables you to use Ethernet network interface performance man-
agement counters for the standard 15-minute and 24-hour periods or free-running
counters which you can start and stop at will.
Since performance and protocol monitoring are handled in the same way by Element
Manager GX R1.3 , they are referred to as performance management (PM).
The following aspects of performance management are described:
• 9.1.1 Displaying the Ethernet Performance Counter
• 9.1.2 Viewing the Current and History Information
9.1.1 Displaying the Ethernet Performance Counter

Open the “Performance Management” dialog to view which counters are available for
which ports as well as the history settings.
To open the “Ethernet” dialog
1. From the “Equipment View”, select a plug-in unit.
2. Click “Measurement” “Performance Management” “Performance Management...”

from the main menu.
The “Performance Management” dialog appears.
3. Select the Ethernet icon in the navigation pane.
The “Ethernet” dialog opens.
The dialog contains tabs with counters for specific interface
4. Click “Get” to verify the displaying.
9.1.2 Viewing the Current and History Information
97
Use this procedure to read the data records for a counter from the NE. You can view the
current record that is being collected by the counter or you can read records stored by
the counter on the NE. To save records from a longer period create a log for the counter
to store them in the EM GX R1.3 database and even export them to files. For more in-
formation about logs, see Section “9.6 Managing Performane Data Logs".
To view current or history information
1. Open the “Ethernet” dialog.
For more information, see Section “9.1.1 Displaying the Ethernet Performance
Counter".
2. To view the history data, select “History” and click “Get”.
To view the current data, select “Current” and click “Get”.
The NE does not support the ’free running counter’ feature in current mode. Thereforethis
field will be empty. In “History” mode , free runnig counters are only displayed if they was
be created (via “Free Running Counters Sample” tab before.
98 A50010-X3-E120-7619
9.2 ATM Performance Monitoring

This performance management contains ATM counters for ADSL ports at IUADSL
modules.
The ATM Performance Monitoring (PM) function reports lost or misinserted cells and also
transmitted cells. ATM PM is not supported towards the line interfaces of the NT / CPE.
The hiX 563x either receives from or sends cells to the core network over the network
interface. If you have an interlink, you can send or receive ATM PM cells over the
interlink.
To display ATM cell counter
1. From the “Equipment View”, select an IUADSL plug-in unit.

from the main menu.
3. Select the ATM icon in the navigation pane.
The “ATM Cell Counters” tab opens.
The tab contains a list with specific counters.
9.3 IGMP Performance Monitoring

For every IGMP multicast group two PM objects can be created (with 15 min. and day
interval type) or deleted. additionally history entry size can be defined. It is possible to
modify history entry size in existing PM object. Counting of performance monitoring object
can be enabled or disabled.
9.3.1 Displaying all existing IGMP Multicast Groups

To open the “IGMP” dialog

from the main menu.
3. Select the IGMP icon in the navigation pane.
The “IGMP” dialog opens.
99
The dialog contains two tabs.
4. Open the “Overview” tab und select the multicast group you want to display.
In this tab you can enable, disable, or delete the selected multicast group counters.
9.3.2 Defining the History Entry Size

To define the history entry size
1. Open the “IGMP” dialog.
For more information, see Section “9.3.1 Displaying all existing IGMP Multicast
Groups".
2. Disable a selected 15 min. counter.
3. Double click the “history entry size” column of this counter and enter the number used
for history data collection.
4. Open the “Overview” tab und select the multicast group you want to display.
5. Confirm with “Apply”.

1. Open the “IGMP” dialog.
For more information, see Section “9.3.1 Displaying all existing IGMP Multicast
Groups".
2. Open the “IGMP Counters” tab.
This tab list all 15 min or 24 hrs conters.
Select the interval type.
To view the current data, select “Current” and click “Get”.
9.4 xDSL Performance Monitoring
100 A50010-X3-E120-7619
This performance management contains xDSL specific counters for each ports at IUxDSL
modules.
9.4.1 Displaying the xDSL Performance Counter

Open the “Performance Management” dialog to view which counters are available for
which ports as well as the history settings.
To open the “xDSL” dialog
1. From the “Equipment View”, select a plug-in unit.

from the main menu.
3. Select the ADSL or SHDSL icon in the navigation pane.
The “sDSL” dialog opens.
The dialog contains tabs with specific counters.

Use this procedure to read the data records for a counter from the NE. You can view the
current record that is being collected by the counter or you can read records stored by
the counter on the NE. To save records from a longer period create a log for the counter
to store them in the EM GX R1.3 database and even export them to files. For more in-
formation about logs, see Section “9.6 Managing Performance Data Logs".
1. Open the “xDSL” dialog.
For more information, see Section “9.4.1 Displaying the xDSL Performance Counter".
2. Open the required “ATU...” or “SHDSL counters” tab.
(For interface counters, only current counters are available.)
To view the current data, select “Current” and click “Get”
101
9.5 Upload Administration

Upload functionality allows to store performance data in file on the FTP server in
specified folder and specified file name.
To enable counter data upload
1. Select an NE in the DCN view.

from the main menu.
3. Select the Upload icon in the navigation pane.
The “Upload Administration” tab opens.
Enter the parameter needed for uploading the data and confirm with “upload”.
9.6 Managing Performance Data Logs

The NE is generally capable of storing performance data for up to 96 hours, depending
on the history counter you have configured for the counter. Logs enable you to keep per-
formance data for a longer period of time. The logs are created by periodically reading
the data from the NE and storing the records in the EM GX R1.3 database. You can
manually or automatically export logged records from the database to file for trouble-
shooting or statical analysis purposes.
You can only log one measurement point at a time. In order to record all the measure-
ment points of an NE, you must create a log for each individual measurement point.
• 9.5.1 Opening the “Performane Log Unit Administration” Dialog
• 9.5.2 Create a Performance Log Unit
• 9.5.3 Stop and Start a Log Unit
• 9.5.4 Configure a Log Unit
• 9.5.5 Clear a Log Unit
• 9.5.6 Delete a Log Unit
• 9.5.7 Export Log Unit Records
• 9.5.8 Viewing Log Unit Records
102 A50010-X3-E120-7619
• 9.5.9 Configuring Global Settings for Performance Log Units
9.6.1 Opening the “Performance Log Unit Administration” Dialog

To open the “Performance Log Unit Administration” dialog
Click “Measurement” “Performance Management” “Log Unit Administration”.
The “Performance Log Unit Administration” dialog appears.
Fig. 9.1 “Performance Log Unit Administration” Dialog
In this dialog, you can:
• Creating a Performance Log Unit (“New”)
• Stop and Start a Log Unit (“Stop”, “Start”)
• Configure a Log Unit (“Configure”)
• Export Log Unit Records (“Export”)
• Clear a Log Unit (“Clear”)
• Delete a Log Unit (“Delete”)
• Viewing Log Unit Records (“View”)
9.6.2 Create a Performance Log Unit
103
Each log is stored in the EM GX R1.3 database. Note the following:
• An entry in the alarm log occupies about 180 bytes. For the default size of 1000
entries, a maximum of 180 kBytes are required for a log in the database.
• Create only as many logs as required.
Delete unneeded logs to free memory in the database. If required, use the export
function to write the log contents to a file and to save it to an external medium.
To create a performance data log
1. Select in the SNMP-DCN view a unit based on the type of PM you want to log.
2. Open the “Performance Log Unit Administration” dialog.
For detailed instructions, see 9.5.1 Opening the “Performance Log Unit
Administration” Dialog.
3. Click “New”.
The “Create Log Unit” dialog appears.
The EM GX R1.3 checks the entered name for the log. If the name is clearly, that means,
a log with the equal name exists already, an error message appears on screen. The di-
alog is opened to correct the name.
9.6.3 Stop and Start a Log Unit

When you create a new performance data log, logging starts automatically by default.
Logging can be stopped or started at any time.
To stop or start a log unit
For detailed instructions, see Section 9.5.1 Opening the “Performance Log Unit
2. Select a log.
3. Click “Stop” or “Start”.
A log in the Full state stops automatically.
9.6.4 Confige a Log Unit
104 A50010-X3-E120-7619
You can edit the attributes of a log unit after it has been created.
You can edit the following attributes:
- Logging state
- Lock state
- Description
- Schedules
To configure a log unit
2. Select a log.
The “Configure Log Unit” dialog appears.
9.6.5 Clear a Log Unit

You can manually delete log unit records from the EM GX R1.3 database. This creates
more room in the EM GX R1.3 database. The log unit must be unlocked before you can
clear it. To unlock a log unit, see Section “9.5.4 Config a Log Unit" and the context-sen-
sitive online help.
To clear a log unit
For detailed instructions, see Section 9.5.1 Opening the “Performance Unit
Administration" Dialog.
2. Select a log.
3. Click “Clear”.
The “Clear all records” message box appears.
105
Fig. 9.2 “Clear All Records” Dialog
4. Determine which records you want to delete.
- To delete all records, click “Clear All”.
- To delete only records which have been previously exported, click “Clear
Exported”.
9.6.6 Delete a Log Unit

When a log unit is no longer needed, you should delete it. Before you can delete a log, it
must be unlocked. To unlock a log unit, see Section “9.6.4 Config a Log Unit" and the
context-sensitive online help.
To delete a log unit
2. Select a log.
3. Click “Delete”.
A message box appears.
Fig. 9.3 Message Box
4. Click “Yes” to delete the log unit.
9.6.7 Export Log Unit Records

You can manually export or schedule the automatic export of log records from a log unit.
The data is exported to an ASCII file (.csv) which you can analyze, use for troubleshoot-
ing.
Tab. 9.1 summarizes the different options.
Export Manual Time-scheduled
106 A50010-X3-E120-7619
Complete Log Filtered Log Complete Log
Where? “Performance Log Unit Administration” “Performance Records of Log “Scheduled Time Jobs” dialog, see
dialog, see Secction mark-var- Unit” dialog, see Section Section mark-var-crossparanum
crossparanum mark-var-crossparanum
How? Select log and click “Export”. Click “Details >>”, then click Schedule an export job during log unit cre-
“Save As” ation, log unit configuration, or global ex-
port schedule creation.
Where to? In the EM GX R1.3 installation directo- In the EM GX R1.3 installation directory:
ry: \Export\Performance\Automatic
Destination directory \Export\Performance\Manual User defined <logtitle><date>@<time>.csv
File name <logtitle><date>@<time>.csv User defined
Tab. 9.1 Export Options for Performance Data
9.6.8 Viewing Log Unit Records

You can view the log unit records in the EM GX R1.3 database. Do not confuse these
records with the records kept on the NE, though they can overlap.
Counter Records in NE Counter Records in EM GX R1.3 Database
Current record is viewable (even though counting Cannot view current record.
period may not be complete).
Can save a number of records up to the history setting. Can save records until the configured maximum num-
When this number is reached, the records wrap around. ber of records for performance log is reached. Full logs
can be configured to wrap around or stop.
Records are saved according to the counter interval, Records are saved (retrieved from the NE) according
once every 15 minutes or once every 24 hours. to retrieval schedule. The default is once every 15 min-
utes and once every 24 hours. However, you can con-
figure schedules globally or individually for logs. For
example, if you set the 15-minute schedule to every 30
minutes, and the history setting for the counter is set to
1, only every second record is retrieved.
Separate views for 15-minute and 24-hour counter. Both counters are logged for the same measuring
point.
Tab. 9.2 Counter Records in NE and EM GX R1.3 Database

There is a limit to the number of records you can view from the EM GX R1.3 server as
defined by the log fetch size (default is 1000). If there are too many records the EM GX
R1.3 warns you that not all records could be displayed. Export your records to file, see
Section “9.6.7 Export Log Unit Records", filter the log view, or configure the log fetch size,
see Section “11.4 Configuring Log Fetch Size".
To view log unit records
107
2. Select a log.
3. Click “View”.
The “Performance Records of Log Unit <title>” dialog appears.
4. To filter the records displayed, click “Details>>”. Check the “Use Fetch Criteria”
checkbox and select the fetch criteria.
5. Click “Fetch Records”.
9.6.9 Configuring Global Settings for Performance Log Units

There are a number of settings that apply to all performance log units.
Settings made for individual log units override these global settings.
To configure the global settings
Click “Measurement” “Performance Management” “Log Administration”.
The “Performance Log Administration” dialog appears.
9.7 Scheduled Tasks for Performance Data

With the Scheduled Services function, the following actions can be carried out:
• Export all logs units at scheduled times
• Change the time interval for retrieving data records from the NE.
You can set these schedules during the following actions
• Creating a log unit
For more information, see Section “9.6.2 Create a Performance Log Unit".
• Configuring a log unit
For more information, see Section “9.6.4 Config a Log Unit".
• Setting global options
For more information, see Section “9.6.9 Configuring Global Settings for
Performancee Log Units".
108 A50010-X3-E120-7619
9.8 Monitor Counters

The “Monitor Counters” dialog displays statistic data for selected Ethernet port. The data
are displayed in a line diaram over a time period.
To monitor packets, JAVA J2SDK must be installed on server computer before using this
menu. For detail information, see 10.7 Failing to monitor packets.
To open the dialog
2. Click “Measurement” “Performance Management” “Monitor Counters...” from the

main menu.
The “Monitor Counters” dialog appears.
3. Select the port you want to monitor.
4. Ckeck the parameter and configure the period time and the update interval.
5. Click “Start” to start the monitoring..

9.9 All Port Counters
The “All Port Monitor” dialog gives an overview about onechannel parameter for all ports.
To monitor packets, JAVA J2SDK must be installed on server computer before using this
menu. For detail information, see 10.7 Failing to monitor packets.
To open the dialog
2. Click “Measurement” “Performance Management” “All Port Monitor...” from the

main menu.
The “All Port Monitor” dialog appears.
3. Select the channel parameter you want to monitor.
4. Ckeck the ports and configure the update interval.
5. Click “Start” to start the monitoring.
109
10 Troubleshooting
The Element Manager GX R1.3 (EM GX R1.3) has a number of means for detecting and
troubleshooting problems.
• 10.1 Starting a Consistency Check
• 10.2 Loop Management
• 10.3 Remote File Administration
• 10.4 Maintenancne Manual
• 10.5 Trouble Ticket Administration
• 10.6 Searching for NEs and NTs
10.1 Starting a Consistency Check

A consistency check ensures that the data you have in the EM GX R1.3 database is
consistent with the data in the NE database. Consistency check runs on NE automatically
after an NE starts up or is added to the SNMP-DCN view. For more information, see
Section “7.1.2 Synchronization State". You can start a manual consistency check.
A manual consistency check also enables an LCT to reconnect to a network element.
To manually start a consistency check
2. Click “Utilities” “Consistency Check” from the main menu. The “Consistency Check”
dialog appears.
For more information, refer to the context-/sensitive online help.
10.2 Loop Management

This section describes loop management.
The hiX 563x R1.3 can test on the ATM layer. The test is a transient test. These tests
run only long enough to check the loop. After they return a result, they have no further
impact on the system
Performing a Transient ATM Layer Loop Test
An ATM layer loopback test is conducted between link termination points. A link termi-
nation point can be either a segment end point or a connecting point. The test can be
110 A50010-X3-E120-7619
configured between two end to end points.
This procedure describes how to start a loopback test from a hiX 563x R1.3. To return
cells you must have the loopback location ID and the appropriate cross connection
To start a loopback test
2. Click “Measurement” “Loop Management” .
The “Loop Management” dialog appears.
3. Select ATM icon in the navigation pane.
The “ATM Layer Loopback Test” dialog appears.
4. Enter the required parameters.
5. Click “Start”.
After the test has been initiated, the status bar displays that the test is Processing.
The test result can be observed in the status bar.
If multiple loopback points return the test cells, the connecting points which looped it
back are displayed in the Multiple Loopback Result list.
If another ATM Layer loopback test or a physical layer test has been initiated in the
hiX 56x R1.3, you receive the following error message:
Unable to start the test as another Loopback test already
running on the selected DSLAM.
If the input parameters are invalid then appropriate error message appears.
10.3 Remote File Administration

This command is used to upload/download remote files from/to NE.
To download/upload remote files with remote file administration
1. Select the NE in the SNMP-DCN view or plug-in unit from the “Equipment View”.
2. Clickt “Utilities” “Remote File Administration” from the main menu.
The “Remote File Management” dialog appears.
3. Select the file you want to upload/download.
Remote inventory file (only upload)
SNMP configuration file (only download)
111
Error log file (only upload)
4. Choose destination/source path and file name.
5. Click “Get” to upload/download the file.
10.4 Maintenance Manual

The Maintenance Manual for the hiX 563x system provides step-by-step procedures for
clearing alarm. You can access this manual in HTML format from the alarm list. For more
information, see Section “8.5.3 Opening the Maintenance Manual". The document is also
separate from the Element Manager GX R1.3 software. For more information, see
Section “1.3 Related Documentation".
10.5 Trouble Ticket Administration

You can use trouble ticket administration to enhance the management of alarms. For
more information, see Section “8.11 Managing Trouble Tickets".
10.6 Searching for NEs and NTs

The EM GX R1.3 has a search function which enables you to find network elements or
NTs within the entire access network. This feature is disabled for the LCT.
The search is started via the “Find Network Elements” dialog in which you can specify the
search criteria and view the search result.
Opening the “Find Network Elements” dialog
• Via the “View” “Find NE” from the main menu
• Via the context menu in the SNMP-DCN View (no NE has been selected)
Fig. 10.1 “Find Network Elements” Dialog
For more information about this dialog, refer to the context-sensitive online help.
112 A50010-X3-E120-7619
To start a search
1. Selecting the search criteria.
2. Click Start”.
To stop a search in progress
click “Stop”.
To print the search result
click “Print”.
To open a view for an NE
1. Right-click an entry from the search result.
2. Select the view type:
- NE in DCN View. This opens the DCN view with the NE selected.
- Equipment View. The appropriate equipment view is opened for the NE. This
option is disabled if the SNMP-DCN View is closed.
10.7 Failing to monitor packets

If you fail to monitor packets using ‘Monitor Counter’ and ‘All Port Monitor’ menu, check
Java was installed in server host.
If not, install java now.
Follow the install procedures below.
1. Stop ACI EMGX Server on Services.
2. Run ACI_Core.
3. Select Custom installation.
4. Uncheck all except Java 2 SDK1.4.2.
5. Continue Installing Java.
6. After finish installing Java, open mpjavaclient.dsf using notepad or something on

C:\Programe Files\Siemens AG\AccessIntegrator EM GX R1.3
Client\conf\mpjavaclient.dsf.
7. Change path as below picture.
113
8. start ACI EMGX Server on Services.
9. Start ACI EMGX client.
114 A50010-X3-E120-7619
11 Managing Network Elements

This chapter describes functions and concepts you need to attend to from time to time as
part of managing network elements.
The following topics are presented:
• 11.1 NE Maintenance
• 11.2 Audit Log
• 11.3 Time Scheduled Jobs
• 11.4 Configuring Log Fetch Size
11.1 NE Maintenance
The operator can request to see the software versions (SAPS versions) of the NE. There
are two software versions that are associated with the EM GX R1.3. One is the active
software version, i.e., the currently running software version and the other is the stand- by
software version.
The term Application Program Software (APS) covers all software required for a particular
version of an Access Network. The software FTP server contains all the files of one or
more APS versions in the SAPS directory. There may be more than one active S-APS
version at any time for different network elements. There may even be more than one
active SAPS directory. After installation and start-up, each NE and its modules are loaded
with the appropriate software version. You can download new APS versions or software
updates from the software FTP server to individual NEs, plug-in units, or NTs.
For information about types of software and requirements for an initial software
download, refer to the context-sensitive online help under the topic “Software
Management”.
NE maintenance includes the following topics:
• 11.1.1 Subsequent Downloads and Updates
• 11.1.2 Displaying Software Version of NE
• 11.1.3 Downloading Software to an NE
• 11.1.4 Displaying Upgrade Status
• 11.1.5 Software Recovery
• 11.1.6 Backing Up NE Data
• 11.1.7 Restoring an NE Database
115
11.1.1 Subsequent Downloads and Updates

In the case of a software update, the existing software version continues working in RAM.
The new version is loaded into the RAM overwriting the current version. If there is a
disturbance during loading process, the existing software version in the FEPROM will no
longer be available and the plug-in unit cannot be booted. The entire software package
must then be reloaded.
When a new software version has been loaded it must be activated so that the plug-in
unit can reboot with the new software.
If the software upgrade results in a new NE version, the change is noted automatically in
the SNMP-DCN view, but only if you enable the “System Upgrade” check option during
the software update. If you do not, you must delete and reinsert the NE. For more
information, see Section “11.1.3 Downloading Software to an NE".
116 A50010-X3-E120-7619
11.1.2 Displaying Software Version of NE

1. Select one or more NEs.
2. Click “Configuration” “NE Maintenance” from the main menu.
The “NE Maintenance” dialog appears.
3. Select the Software Download icon in the navigation pane.
The “Software download” tab opens.
The list shows affected NEs or plug-in units, current SW version, and stored SW
version. An “Available Load” drop-down list displays all the software version available
on FTP server for the NE.
11.1.3 Downloading Software to an NE

A single NE or a group of NEs must have been selected for the download.
If an upgrade operation is already in progress, an attempt to start a similar operation will

not succeed.
1. Select one or more NEs, or the SNMP port.
4. Select the NE(s) in the table and adapt the download options.
5. Select any download options.
- Click “Download” to start the download immediately
- Click “Schedule” to enter details for scheduling the download to take place
automatically at a later date and time, or
- Enable “Activate after download” to reset the unit as soon as the download is
complete or disable it to reset the unit later. When you are ready to reset the unit
open the “Upgrade Status” tab.
- Enable “All of Type” to update all PIUs of the same type on the NE to the selected
software.
Enable “System upgrade” when you upgrade NE software from one version to another,
for example. This forces the ACI-E EM GX R1.3 to update the NE icon in the SNMP-
DCN view to the new version. This option is only available for automatic update.
117
If you forget to enable the system upgrade option, the NE remains inconsistent, even if
you perform a consistency check. Your only option is to delete the NE from the DCN view
and reinsert the network element.
6. Choose from one the of the following options:
- Click Proceed to start the download immediately
- Click Schedule to enter details for scheduling the download to take place auto-
matically at a later date and time
If you clicked “Proceed”, the “Download Progress View” dialog.
When the software download is complete, the label on the “Cancel” button changes to
“Close”.
11.1.4 Displaying Upgrade Status

With this management function of the EM GX R1.3, the current active or failed software
upgrade tasks for the selected NE can be viewed in a table form. Successful and acti-
vated upgrade tasks are not listed. The table is normally used to display the upgrade
status for PIUs and it is continually refreshed.
1. Select a single NE in the SNMP-DCN view.
This dialog displays the current active or failed tasks of software upgrade of the se-
lected NE. Each row of the table is numbered sequentially and contains the details of
an upgrade event.
4. Choose from one of the following actions:
To filter the table, select an NE type from the drop-down list “NE”. The table is
immediately refreshed to reflect the application of any filters.
To close the dialog, click “Close”.
11.1.5 Software Recovery
118 A50010-X3-E120-7619
Use software recovery to reset NE plug-in units.
There are four levels of software recovery:
• Reset system
Restarts the system software.
• Reset system with default
Restarts the system software with deault values.
• Reset module
Restarts the software of the selected module.
• Reset module of all type
Restarts the software of all types as the selected module.
To execute a recovery procedure
1. Select a single PIU or a set of PIUs of the same type in the “Equipment View”.
2. Click “Configuration” “Node Configuration”.
3. Select the Modules icon in the navigation pane.
The “Modules dialog with the “General” tab appears
4. Select the plug-in unit, one of the recovery levels and click “Start”.
The selected recovery level is initiated and a warning message appears to indicate
that recovery is a long operation.
The results of the recovery operations is logged in the Event Log. If an error in the
recovery download occurred, the PIU continues running its previous software.
11.1.6 Backing Up NE Data

The database of the NE stores various kinds of information locally, such as the software
version that is being used. This database should be backed-up regularly. The database
backups can be done at any time manually, or it can be configured as a time-scheduled
job. During this process the current database is transferred from the NE to the FTP
server.
There are two types of backups:
- Local backup stores the information in the FEPROM of the NE
- Remote backup stores the information on the FTP server machine
119
Because of the time required to back up an entire element, it is recommended that the
backup procedures for large networks should be carried out in steps, limiting the number
of NE that are backing up at the same time.
The active database is backed up automatically by default every 24 hours. By default this
occurs at 2:00 am. If there are no changes in the database, no backup takes place.
Perform a manual backup after a software upgrade or a change of PIU type.
To back up NE data manually
If you do not select anything, all the NEs in the subnetwork are included in the backup.
3. Select the Backup icon in the navigation pane.
The “Backup” dialog opens.
This dialog displays the selected NEs, current software version loaded to the network
element, status of backup, start time and periodicity for scheduled backup.
4. Set the start time and the periodicity for backup and confirm with “Apply”.
5. For spontaneously backup, click “Backup” button.
11.1.7 Restoring an NE Database

The ’restore’ function is reserved for a download of the previously backed up database to
the NE. During this process the latest backed up database is transferred from the data
FTP server to the selected NE.
A restore of the hiX 563x database transfers the remotely stored backup file from the FTP
server to the subrack. The FTP server must be available to the NE and there must be a
recent backup of the database.
To restore NE data
1. Select an NE in the SNMP_DCN view.
3. Select the Restore icon in the navigation pane.
The “Restore” dialog opens.
120 A50010-X3-E120-7619
4. Select an accessible backup file which must be restored to NE and click “Restore”
button.
11.2 Audit Log

The audit log is intended to keep a record of who did what. It shows which operators
performed which tasks.
To view the audit log
1. Click “Security” “Audit Log Display...” from the main menu.
The “Audit Log: Global” dialog appears.
2. Set the desired options.
To configure audit log administration
1. Click “Security” “Audit Log Admin...” from the main menu.
The “Audit Log Administration” dialog appears.
2. Set the desired options.
11.3 Time Scheduled Jobs

The EM GX R1.3 has central time planning available to it, allowing it to issue time-sched-
uled jobs.
The following EM GX R1.3 functions can be scheduled for execution:
• SW download
• Backup NE data (see Administration Manual ADMN; UMN:ADMN)
• Exporting log data
- Alarm logs
- Event logs
- Performance logs.
A time-scheduled job is scheduled in the dialog of the relevant EM GX R1.3 function.
To open the dialog, click “View” “Time Scheduled Jobs” from the main menu.
A list of all the active time-scheduled jobs is displayed. The list columns describe the start
point of the order, the EM GX R1.3 function to be executed and also the periodicity, if the
121
job is to be executed more than once.
11.4 Configuring Log Fetch Size

There is a limit to the amount of log data you can fetch to your terminal. You may want to
adjust this limit based on the performance of your network and your host.
To configure the fetch size for logs
1. Click “Options” “Configure Log Fetch Size” from the main menu.
The “Log Fetch Size” dialog appears.
Set the parameter.
2. Click “OK”.
122 A50010-X3-E120-7619
12 Abbreviations
ACI AccessIntegrator
ACT Activation
ADMN System Administration Manual
ADSL Asymmetric Digital Subscriber Line
AIS Alarm Indication Signal
ANSI American National Standards Institute
APS Application Program Software
ATM Asynchronous Transfer Mode
BOOTP Bootstrap Protocol
BR Backward Reporting
CAPS Customer Application Program Software
CBR Constant Bitrate
CC Cross Connection
CDVT cell delay variation tolerance
CI Central Processor
CLU Central processor and Line Unit
CoC Continuity Check
CORBA Common Object Request Broker Architecture
CPE Customer Premises Equipment
CRC Cyclic Redundancy Check
CSV Comma Separated Value
DB Database
DCN Data Communications Network
DHCP Dynamic Host Configuration Protocol
DSL Digital Subscriber Line
DSLAM Digital Subscriber Line Access Multiplexer
EBER Excessive Bit Error Rate
EM Element Manager
123
FCU Fan Control Unit
FM Forward Monitoring
FTP File Transfer Protocol
FU Functional Unit
HPEBER High-Order Path Excessive Bit Error Rate
HW Hardware
HWM Hardware Management
IDR Inventory Data Retrieval
IMA Inverse Multiplexing over ATM
IMN Installation Manual
IP Internet Protocol
ISP Internet Service Provider
ITU-T International Telecommunications Union - Telecommunications

Standardization Sector
LAN Local Area Network
LCT Local Craft Terminal
LI Line Interface
LLID Loopback Location ID
LOC Loss of Continuity
LOS Loss of Signal
LU Line Unit
MBS Minimum Burst Size
MCR Minimum Cell Rate
MIB Management Information Base
MSEBER Multiplexer Section Excessive Bit Error Rate
MTA Metallic Test Access
NE Network Element
NNI Network-Network Interface
nrt-VBR Non-Realtime Variable Bitrate
NT Network Termination
124 A50010-X3-E120-7619
OAM Operations and Maintenance
OMN Operations Manual
PAPS Partial Application Program Software
PCR Peak Cell Rate
PDF Portable Document Format
PIU Plug-In Unit
PM Performance Management
PPTP Physical Path Termination Point
RAM Random Access Memory
RDI Remote Defect Indication
RSEBER Regeneration Section Excessive Bit Error Rate
rt-VBR Realtime Variable Bitrate
SAPS System Application Program Software
SCR Sustainable Cell Rate
SD Signal Degradation
SDSL Symmetric Digital Subscriber Line
SMS Short Message Service
SNMP Simple Network Management Protocol
SNR Signal-to-Noise Ratio
SU Subscriber Unit
SW Software
TCA Transmission Convergence Adapter
TMN Telecommunications Management Network
TP Termination Point
UBR Unspecified Bitrate
UNC Universal Naming Convention
UNI User-Network Interface
UTP Unshielded Twisted Pair
VBR Variable Bitrate
VC Virtual Channel
125
VCCC Virtual Channel Cross Connection
VCI Virtual Channel Index
VP Virtual Path
VPCC Virtual Path Cross Connection
VPI Virtual Path Index
VPL Virtual Path Link
VPTP Virtual Path Termination Point
XL XpressLink
126 A50010-X3-E120-7619

Hix563x (M600 M1200) ACI (R1.3) OGL V4 EN PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hix563x (M600 M1200) ACI (R1.3) OGL V4 EN PDF

Uploaded by

Copyright:

Available Formats

Operation

ACI-E R1.2 (EM GX R1.3)

Important Notice on Product Safety

The same text in German:

Copyright (C) Siemens AG 2005.

Issued by the Communications Group

Technical modifications possible.

Reason for Update

Chapter/Section Reason for Update

All Change of ACI-E version

Issue Date of issue Reason for Update

1 05/2005 ACI EM GX R1.3 initial release

2 06/2005 Procedure for configuring IPoA port aaded

3 09/2005 New features added

4 11/2005 Change of ACI-E version

4.4.3 Editing Inventory Data ...........................................................................................39

7 Monitoring the hiX 563x R1.3 System.............................................................. 71

9.6.1 Opening the “Performance Log Unit Administration” Dialog ...............................103

Fig. 3.1 EM GX R1.3 Main Window ................................................................................ 20

Tab. 1.1 Document Structure ..........................................................................................11

1.2 Document Structure

Category Section Contents

Introduction 1 Introduction Describes document structure as well as related documents.

6 Bridge Configuration Configure bridge connections. Includes the creation,

9 Performance Management Describes how to configure and monitor performance

Troubleshootin 10 Troubleshooting Provides you with procedures to help troubleshoot problems

Managing software versions, audit logs, and time scheduled

Tab. 1.1 Document Structure

1.3 Related Documentation

Title Part Number Topics Covered

A50010-X3-E135-*-7618 hiX 5635 R1.3 functions and hardware descriptions. This

A50010-X3-E135-*-7630 Instructions for the commissioning a hiX 5635 R1.3.

hiX 563x Maintenance Manual A50010-X3-E130-*-7620 Alarm troubleshooting procedures.

A50010-X3-E135-*-7620 Alarm troubleshooting procedures.

Tab. 1.2 Related Documentation

1.4 Typographic Conventions

Courier Inputs and outputs

Example : Enter LOCAL as the server name

Command not found

Example : name can be eight letters long.

bold Special emphasis

Example : You must not delete this name.

<Courier> Keyboard combinations

Example : <STRG> <ALT>+<ESC>

Example : File → Exit

Tab. 1.3 Typographic Conventions

2 Starting the Element Manager GX R1.3

2.1 Before Starting

2.1.1 Installing the EM GX R1.3 Software

2.2 Starting and Stopping the EM GX R1.3 Server Processes

BRASS The BRASS process (SNMP BRASS Management Multiplexer) is started

Tab. 2.1 EM GX R1.3 Processes

2.2.1 Under Windows

To start or stop Element Manager GX R1.3 server processes manually

- SNMP BRASS Management Multiplexer

2.2.2 Under Solaris

2.3 Starting the ACI-E Element Manager GX R1.3 Client

2.3.1 Under Windows

To start the EM GX R1.3 client under Windows,

Click “Start”  “Programs”  “Siemens AccessIntegrator”  “EM GX R1.3”  “Element

To connect to a non-default EM GX R1.3 server

click “File  “Exit” or

via the key combination <Alt>+<F4> or

Click “Start” “Programs” “Siemens AccessIntegrator” “EM GX R1.3” “Element

click “File “Exit” or

To close a client session, click “File” “Exit”.

Select “View” “Toolbar” from the main menu.

Select “View” “Status Bar” from the main menu.

Select “View” “SNMP DCN View” from the main menu.

Click “View” “Zoom” from the main menu.

1. Select “Options” “View Options” from the main menu.