Administration Maintenance

s
HiPath
Gateway 1500
HiPath HG 1500 V3.0
Administration and Maintenance
*1PA31003-H3540-A800-1-7619*
1P A31003-H3540-A800-1-7619
The device meets the requirements contained in the EU Directive 1999/5/

EU and carries the CE symbol.
This device has been manufactured in accordance with our certied environmental management system (ISO 14001). This process ensures that energy consumption and the use of primary raw materials are kept to a minimum, thus reducing waste production.
The information in this document contains general descriptions of the technical options available, which do not
always have to be present in individual cases. The required features should therefore be specied in each individual
case at the time of closing the contract.
Siemens AG 2003 Information and Communication Networks, Hofmannstrae 51, D-81359 Munich
Reference No.: A31003-H3540-A800-1-7619
Printed in the Federal Republic of Germany.
Subject to availability. Right of modication reserved.
HiPath is a registered trademark of Siemens AG.
bkTOC.fm
For internal use only
Contents
Contents
List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0-7

List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0-9
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Documentation Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Target Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Contents of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Conventions Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-1
1-1
1-1
1-2
1-3
2 Management Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.1 Overview of Management Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.2 Web-Based Management (WBM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2.3 WBM Window Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.3.1 WBM Module Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
2.3.2 Menu Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
2.3.3 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
2.3.4 Differences Between Wizards, Maintenance and Explorer modules . . . . . . . . . . 2-8
2.4 Command Line (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
2.4.1 Overview of Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
2.4.2 General Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
2.4.3 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
2.4.4 Configuring the Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
2.4.5 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
2.5 SNMP Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
2.6 HiPath 3000 Manager E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
3 Web-Based Management (WBM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.1 WBM Window Control Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.1.1 Control Icon Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.1.2 Control Icon Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.2 Tree Representation in the WBM Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.3 Starting a WBM Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.4 Using WBM Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.4.1 Wizards Module Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3.4.2 Navigating in a Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3.4.3 Wizard Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
3.5 Using WBM Maintenance Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.5.1 Maintenance View Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.5.2 Navigating in Maintenance View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.5.3 Maintenance Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.6 Using WBM Explorers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
A31003-H3540-A800-1-7619, 2003-05-02
HG 1500 V3.0, Administration and Maintenance
0-1
bkTOC.fm
Contents
3.6.1 Explorer View Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

3.6.2 Navigating in the Explorer View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
3.6.3 Explorer functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
4 Administration Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.1 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.1.1 Logging In and Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.1.2 Access Rights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2 Sequence of a WBM Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.2.1 Starting WBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.2.2 Selecting a Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.2.3 Using a Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.2.4 Terminating a Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
4.3 Configuring Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4.3.1 Configuring Telnet Access via the Command Line. . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4.3.2 Configuring WBM Clients via the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4.3.3 Configuring WBM Clients and Telnet Clients in WBM . . . . . . . . . . . . . . . . . . . . . . 4-6
4.3.4 Using Telnet Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
4.4 Backing up System Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4.5 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4.5.1 Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
4.6 Traces (Procedure Recording) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
4.6.1 Displaying a Trace Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
4.6.2 Editing a Trace Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
4.6.3 Loading Trace Log File to the Server or PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
4.6.4 Deleting the Gateway Trace Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
4.6.5 Displaying the H.323 Stack Trace Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
4.6.6 Editing the H.323 Stack Trace Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
4.6.7 Trace Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
4.6.8 Trace Probes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
4.7 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
4.7.1 Event Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
4.7.2 Transferring an Event File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
4.7.3 Deleting the Gateway Event Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
4.7.4 Displaying E-Mail Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
4.7.5 Editing E-Mail Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
4.7.6 Displaying the Reaction Settings for All Events . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
4.7.7 Setting Reactions to Individual Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
4.8 Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
4.8.1 Displaying a List of All Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
4.8.2 Displaying a List of All Critical Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
4.8.3 Displaying Individual Traps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
4.8.4 Displaying a List of All SNMP Communities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42
4.8.5 SNMP Read Communities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43
4.8.6 SNMP Write Communities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
0-2
A31003-H3540-A800-1-7619, 2003-05-02
bkTOC.fm
Contents
4.8.7 Trap Communities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.9 System Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.9.1 Manual Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.9.2 Automatic Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-50
4-54
4-54
4-56
5 Maintenance Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.1 Safety Information for Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.1.1 Safety Information: Danger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5.1.2 Safety Information: Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
5.1.3 Safety Information: Caution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
5.1.4 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
5.1.5 What To Do in an Emergency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
5.1.6 Reporting Accidents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.1.7 Disposal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.2 Replacing HXG3 boards in the HiPath HG 1500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.2.1 Preparing the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.2.2 Preparing Boards for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.2.3 Preparing HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.2.4 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.3 Expanding HiPath HG 1500 with HXG3 boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
5.3.1 Preparing the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
5.3.2 Preparing Boards for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
5.3.3 Preparing HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
5.3.4 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
5.4 Inserting an Extension Module in an HXG3 Board . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
5.4.1 Preparing the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
5.4.2 Removing HXG3 Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
5.4.3 Exchanging or Inserting Extension Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
5.4.4 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
5.5 Software Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
5.5.1 Rebooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
5.5.2 Changing the Software Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
5.5.3 Loading Configuration Data from Server or PC . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
5.5.4 Saving Configuration Data on a Server or PC . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
5.6 Multigateway Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
5.6.1 Displaying the List of Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
5.6.2 Adding a New Gateway to a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
5.6.3 Removing All Gateways from Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
5.6.4 Selecting and Deselecting Gateways for Distribution . . . . . . . . . . . . . . . . . . . . . 5-26
5.6.5 Displaying Gateway Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
5.6.6 Displaying Gateway Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
5.6.7 Editing Gateway Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
5.6.8 Deleting a Gateway from a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
5.6.9 Editing the List of Configuration Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
5.6.10 Distributing Configuration Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
A31003-H3540-A800-1-7619, 2003-05-02
0-3
bkTOC.fm
Contents
5.6.11 Checking the Processing Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.7 Administration Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.1 Administration Log File Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.2 Loading the Administration Log File to a Server or PC . . . . . . . . . . . . . . . . . . . .
5.7.3 Deleting Administration Log Files from the Gateway . . . . . . . . . . . . . . . . . . . . . .
5.8 Job Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-31
5-32
5-32
5-33
5-34
5-35
6 Error Correction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1 Errors During Installation or Starting the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 Errors during System Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.1 Software Image Exchange Fails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.2 Downloading Configuration Data Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3 Error Detection during Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.1 Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.2 Traces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.3 Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3.4 Event Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4 Problems with the WBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5 Abnormal Board Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-1
6-1
6-2
6-2
6-3
6-4
6-4
6-5
6-6
6-6
6-8
6-9
A Command Line (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A.1 General Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.1.1 Shell Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.1.2 Interrupting the Boot Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.1.3 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.2.1 Installation Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.2.2 Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.3 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.3.1 Inspection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.3.2 Resetting the Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.4 List of All CLI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-1
A-2
A-2
A-3
A-3
A-4
A-4
A-4
A-7
A-7
A-8
A-9
B Boot Command Line (Boot CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B.1 Rebooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.1.1 Initiating Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.1.2 Boot Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.1.3 Interrupting the Boot Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.2 Controlling the Boot Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.2.1 Boot Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.2.2 Start Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.2.3 Editing Start Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.3 Software Installation using the Boot CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.3.1 Preparations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.3.2 Loading the Software to the Flash Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B-1
B-1
B-1
B-1
B-2
B-2
B-2
B-3
B-4
B-5
B-5
B-5
C Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
0-4
A31003-H3540-A800-1-7619, 2003-05-02
bkTOC.fm
Contents
C.1 Trace Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

C.1.1 System Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
C.1.2 OAM / WBM Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
C.1.3 Licence Management Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-8
C.1.4 IP Accounting Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9
C.1.5 GSA Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10
C.1.6 CP Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-11
C.1.7 SCN Protocol Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15
C.1.8 IP Networking Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-16
C.1.9 H.323 Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-19
C.1.10 Device Manager Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-21
C.1.11 HIP Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-22
C.1.12 SW Platform Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-23
C.2 Event Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-30
C.2.1 Status Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-30
C.2.2 Reboot Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-31
C.2.3 Resource Observation Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-35
C.2.4 Routing Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-41
C.2.5 Call Control and Feature Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-43
C.2.6 SCN Protocol Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-47
C.2.7 H.323 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-55
C.2.8 H.235 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-58
C.2.9 RTPQM Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-59
C.2.10 GSA Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-60
C.2.11 DGW Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-60
C.2.12 CAR Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-72
C.2.13 REG Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-74
C.2.14 NU Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-75
C.2.15 NU Leg Control Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-78
C.2.16 HFA Manager Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-79
C.2.17 HFA Adapter Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-84
C.2.18 PPP Call Control Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-85
C.2.19 PPP Manager Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-88
C.2.20 PPP Stack Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-89
C.2.21 VCAPI Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-90
C.2.22 VCAPI Application Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-99
C.2.23 H.323 Client Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-104
C.2.24 IPNC Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-105
C.2.25 IPNCA Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-107
C.2.26 MPH Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-107
C.2.27 OAM Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-108
C.2.28 WBM Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-112
C.2.29 CLI Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-113
C.2.30 Licence Management Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-114
A31003-H3540-A800-1-7619, 2003-05-02
0-5
bkTOC.fm
Contents
C.2.31
C.2.32
C.2.33
C.2.34
C.2.35
C.2.36
C.2.37
C.2.38
C.2.39
C.2.40
C.2.41
C.2.42
C.2.43
C.2.44
C.2.45
HIP Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SI Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MAGIC / Device Manager Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Important Platform SW Status Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Major ASC Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Major ASP Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ASC Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Minor ASP Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IP Filter Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MAC Filter Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IP Stack Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DELIC Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Test Loadware Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fax Converter, HDLC, X.25 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IP Accounting Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C-116
C-119
C-129
C-137
C-137
C-138
C-139
C-141
C-141
C-142
C-143
C-144
C-144
C-145
C-147
D Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
D.1 Suggested LAN Solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
D.1.1 BNC Network at a Twisted Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
D.1.2 3COM Dual Speed hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
D.1.3 Solution with a Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
D.1.4 HiPath HG 1500 in Token Ring Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4
D.2 Utility Programs for TCP/IP Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4
D.2.1 ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4
D.2.2 ipconfig. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7
D.2.3 nslookup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-9
D.2.4 hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-11
D.2.5 netstat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-12
D.2.6 nbtstat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-16
D.2.7 route. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-17
D.2.8 tracert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-19
D.2.9 arp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-20
D.2.10 telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-21
D.3 IP Addressing: Sub-Networks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-22
D.4 Port Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-30
D.4.1 Port numbers on HG 1500 V3.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-30
D.4.2 Port Numbers on the HiPath 3000/5000 Server . . . . . . . . . . . . . . . . . . . . . . . . . D-31
D.4.3 Port Numbers on HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-32
D.5 Unwanted Internet connections (DNS queries) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-33
D.6 PC sound settings for Voice over IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-33
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Y-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Z-1
0-6
A31003-H3540-A800-1-7619, 2003-05-02
bkLOF.fm
List of Figures
Figure 2-1
Figure 3-1
Figure D-1
Figure D-2
Figure D-3
Figure D-4
Figure D-5
List of Figures
WBM Window Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Wizard Module Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Connection of BNC Network at Twisted Pair to HiPath HG 1500 . . . . . . . D-1
Example: 3COM SuperStack II Dual Speed . . . . . . . . . . . . . . . . . . . . . . . D-2
Switch with 100 MB and 10 MB Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
HiPath HG 1500 in Token Ring Networks . . . . . . . . . . . . . . . . . . . . . . . . . D-4
Connection of BNC Network at Twisted Pair to HiPath HG 1500 . . . . . . D-28
A31003-H3540-A800-1-7619, 2003-05-02
0-7
bkLOF.fm
List of Figures
0-8
A31003-H3540-A800-1-7619, 2003-05-02
bkLOT.fm
List of Tables
Table 1-1
Table 1-2
Table 4-1
Table 4-2
Table 5-1
Table 6-1
Table 6-2
Table 6-3
Table 6-4
Table 6-5
Table 6-6
Table 6-7
Table 6-8
Table 6-9
Table A-1
Table A-2
Table A-3
Table B-1
Table B-2
Table B-3
Table B-4
Table B-5
Table D-1
Table D-2
Table D-3
Table D-4
Table D-5
Table D-6
Table D-7
Table D-8
Table D-9
Table D-10
Table D-11
Table D-12
List of Tables
Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Typographic Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Trap Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
Effect Classes for Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
LED indicators when booting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Errors when switching on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Error correction: updating the software image . . . . . . . . . . . . . . . . . . . . . 6-3
Error correction: downloading the configuration data . . . . . . . . . . . . . . . . 6-3
System traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Performance traps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Trace functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Meanings of entries in event log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Problems with the WBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Abnormal Gateway Behavior. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Command Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Reset commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
Overview of CLI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
LED indicators when booting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Boot Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Start Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
Commands for Editing Start Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . B-5
Start Parameters for Software Installation via Boot CLI . . . . . . . . . . . . . . B-5
Network Classes and Standard Network Masks . . . . . . . . . . . . . . . . . . . D-22
Example of a Class C Standard Network Mask . . . . . . . . . . . . . . . . . . . D-22
Bit Number Depending on Number of Networks . . . . . . . . . . . . . . . . . . . D-23
Example of a Subnet Mask Binary Format . . . . . . . . . . . . . . . . . . . . . . . D-24
Calculating New Subnets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-24
Host Segment in a Network Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . D-25
Network Addresses Depending on Last Two Bit Digits . . . . . . . . . . . . . . D-25
Allocating IP Addresses to Class C Networks. . . . . . . . . . . . . . . . . . . . . D-25
Overview of the Most Commonly-Used Class C Masks . . . . . . . . . . . . . D-27
Port numbers on HG 1500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-30
Port Numbers on the HiPath 3000/5000 Server . . . . . . . . . . . . . . . . . . . D-31
Port Numbers on HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-32
A31003-H3540-A800-1-7619, 2003-05-02
0-9
bkLOT.fm
List of Tables
0-10
A31003-H3540-A800-1-7619, 2003-05-02
Admain1.fm
Introduction
Documentation Structure
Introduction
The integrated HiPath HG 1500 gateway board is a VoIP gateway (Voice over IP) of the new
generation. This Administration and Maintenance manual describes HiPath HG 1500 management.
This chapter describes the structure of the documentation, denes the target audience and provides an overview of the contents. It describes:
the layout of the documentation (see Section 1.1, Documentation Structure),
this manuals target audience (see Section 1.2, Target Audience),
the contents of each chapter in this manual (see Section 1.3, Contents of this Manual),
the typographical conventions used (see Section 1.4, Conventions Used).
1.1
Documentation Structure
The HiPath HG 1500 documentation consists of the following manuals:
Technical Description
Installation Instructions
Administration and Maintenance (this document)
Conguration
1.2
Target Audience
This manual is designed for technicians and administrators who will monitor HiPath HG 1500
operation, resolve problems and deal with the maintenance of hardware and software.
Technicians must have in-depth knowledge of the following:
Data communications hardware
WAN (Wide Area Network) concepts and terms
LAN (Local Area Network) concepts and terms
Internet concepts and terms
A31003-H3540-A800-1-7619, 2003-05-02
1-1
Admain1.fm
Introduction
Contents of this Manual
1.3
Contents of this Manual
This Administration and Maintenance manual contains an overview of the management tools,
the basic explanation of Web-Based Management (WBM), a description of the administrative
activities and maintenance tasks as well as instructions and information on troubleshooting.
This manual contains the following chapters:
No. Chapter
Contents
Introduction
Describes the use of the manual, shows how the documentation is structured and denes the target audience.
Management Tools
Contains information on the various HiPath HG 1500

management tools.
Web-Based Management
(WBM)
Describes the basic layout of Web-Based Management

and its functions and use for HiPath HG 1500 administration and maintenance.
Administration Tasks
Describes the ongoing gateway observation and administration and contains an overview of events and messages.
Maintenance Tasks
Describes how to handle traps, exchange certain hardware modules, restart the system, restore data and update software.
Error Correction
Contains information and guidelines for handling problems and errors.
Command Line (CLI)
Contains all the CLI commands including a brief description.
Boot Command Line (Boot

CLI)
Contains a brief description of the Boot CLI commands.
Tables
Contains a collection of trace and event templates.
10
Appendix
Contains additional information which may be helpful

when operating HiPath HG 1500.
11
Glossary
Describes important terms used in this manual.
12
Abbreviations
Lists the abbreviations used in this manual in alphabetical

order.
13
Index
An alphabetic list of key words.
Table 1-1
1-2
Chapter overview
A31003-H3540-A800-1-7619, 2003-05-02
Admain1.fm
Introduction
Conventions Used
1.4
Conventions Used
The following display conventions are used in this manual:

Convention
Example
Courier
Input and output

Example: Enter LOCAL as the le name.
Command not found
Italics
Variable
Example: Name can contain up to eight characters.
Bold
Special emphasis
Example: This Name must not be deleted.
Quotation marks
Indicates user interface elements

Example: Click OK.
Select Exit from the File menu.
<Courier>
Keyboard shortcuts
Example: <CTRL>+<ALT>+<ESC>
>
Menu sequence
Example: File > Exit
>
Additional information
Warning of critical points in a procedure.
Table 1-2
Typographic Conventions
A31003-H3540-A800-1-7619, 2003-05-02
1-3
Admain1.fm
Introduction
Conventions Used
1-4
A31003-H3540-A800-1-7619, 2003-05-02
Admain2.fm
Management Tools
Overview of Management Tools
Management Tools
Various tools support administrators in performing their tasks. These will be explained in this
chapter.
2.1
Overview of Management Tools
The following four tools are available in HiPath HG 1500 for administrators:
Web-Based Management (WBM) via an integrated HTTP server

Provides a step-by-step conguration and easy access to all management functions. WBM
is the primary management tool.
Command line (CLI) via Telnet or the serial V.24 interface

The command line is designed as the secondary management tool and provides a limited
function scope. It can be used to modify certain conguration data, update and restart the
system and to diagnose the system conguration.
SNMP-supported management via an SNMP agent

SNMP-supported management enables gateway integration in network management systems. Systems like this can manage devices from other manufacturers.
HiPath HG 1500 supports SNMP version 1. Information such as statistics can be read and
some important settings can be modied using SNMP. The gateway can also report important events by means of traps.
HTTP applications via a command interface

HiPath HG 1500 conguration data can be read out and modied and commands can be
executed via an HTTP port.
The Universal Resource Identier (URI) in the HTTP sequence is recognized by the gateway as an administration command. The HTTP header contains information required for
authentication.
In addition to the HiPath HG 1500 management tools, HiPath 3000 Manager E is available for
administrating HiPath 3000.
HiPath 3000 Manager E via a HiPath 5000 RSM server PC

HiPath 3000 Manager E is an independent tool installed on an HiPath 5000 RSM server
PC. It displays the relevant parts of the HiPath 5000 network as a virtual HiPath system.
Depending on the HiPath HG 1500 version, some settings can be congured using HiPath
3000 Manager E or WBM. All parameters that can be set are explained in the Conguration
manual.
A31003-H3540-A800-1-7619, 2003-05-02
2-1
Admain2.fm
Management Tools
Web-Based Management (WBM)
2.2
Each computer with a TCP/IP-supported network connection on which a compatible Web

browser runs can access HiPath HG 1500 via a password. The WBM interface is available in
German and English. The language can be set via the Web browsers language setting.
>
WBM is composed of HTML/XSL pages with frames. The following must be installed:
Windows 98SE, NT 4.0, 2000 or XP
Java plug-in JRE 1.3.1
Microsoft Internet Explorer 5.5 or 6.0
XML Extension DLL V3.0 SP2
Explorer settings must permit the use of ActiveX and Java.
Information on the software requirements and links for a software download are also available
on the WBM homepage (login page).
>
2-2
A mouse with at least two keys is required for WBM.
A31003-H3540-A800-1-7619, 2003-05-02
Admain2.fm
Management Tools
WBM Window Layout
2.3
WBM Window Layout
The WBM window is divided into the following ve frames:

Banner area
Module area
Contents area
Menu
area
Control area
Figure 2-1
WBM Window Layout
Banner area
The top area contains the Siemens logo and product name. You can open the relevant Web
pages by clicking the logo or the product name.
Module area
The area under the banner displays the modules available. You can select the required
module by clicking its name.
Menu area
The area at the left is used for navigating within a module. The selected management tool
determines the menu that is displayed there.
Control area
The icons for controlling WBM and the status information that is constantly displayed are
located at the bottom.
A31003-H3540-A800-1-7619, 2003-05-02
2-3
Admain2.fm
Management Tools
WBM Window Layout
Contents area
All messages and dialogs are displayed in the central area. The Explorer mode displays
conguration items as a tree structure with the respective pop-up menus. The pop-up
menus enable conguration data to be displayed and conguration functions to be activated.
The contents area contains HTML pages which, depending on the task, may comprise a
simple text, an applet, generated texts (XSL or XML) or a combination of these.
HTML text les are used for explanations.
Applets display an overview of the system or parts of it.
Generated text pages display system details.
The following gure illustrates a sample WBM window:
All activities are controlled via the control icons in the control area or via buttons in the contents
area. You can change to other WBM windows via the module names in the module area of the
WBM window.
2-4
A31003-H3540-A800-1-7619, 2003-05-02
Admain2.fm
2.3.1
Management Tools
WBM Window Layout
WBM Module Area
All available modules are displayed in the area under the banner. You can select a module by
clicking its name.
The modules name is displayed in red italics when activated (see diagram below) and modulespecic options appear in the module area.
Logoff
Clicking this module terminates the connection to the gateway and closes the WBM session.
Wizards
Clicking this module will open a menu containing various wizards to support you when conguring HG 1500:
Initial Setup
PBX Routing
IP Mapping
IP Filter
NAT
MAC Filter
Maintenance
A list of the available Maintenance functions is displayed in the menu area when this module is clicked. If you select a Maintenance function, a hierarchical tree structure containing
expanding and collapsing subfolders appears in the left part of the contents area (similar
to Windows Explorer). You can open a pop-up menu for each tree element by right-clicking
it. Each pop-up menu contains additional functions and provides access to elements of the
MIB (Management Information Base). If you select an entry from the pop-up menu, the corresponding function is displayed in the contents area. The menu area contains:
Conguration
Software Image
Multigateway Admin
Joblist
Traces
Events
A31003-H3540-A800-1-7619, 2003-05-02
2-5
Admain2.fm
Management Tools
WBM Window Layout
SNMP
Admin Log
Actions
Conversion
Explorer
An Explorer window opens when this module is clicked. A list of the available Explorers is
displayed in the menu area. After an Explorer function has been selected, a hierarchical
tree structure with expanding and collapsing subfolders appears in the left part of the Explorer window (similar to Windows Explorer). Pop-up menus can be opened by right-clicking a tree element. Each pop-up menu contains additional functions and provides access
to elements of the MIB (Management Information Base). If you select an entry from the
pop-up menu, the corresponding function is opened. The following Explorers are available:
Basic settings
Security
Network Interfaces
Routing
Voice Gateway
VCAPI
Payload
Statistics
Help
Clicking this module displays a list of functions via which you can:
show information on how to use WBM,
display HiPath HG 1500 documentation or
open HiPath Web pages.
2.3.2
Menu Area
The menu area contains all the options available to a module, for example, various Explorers.
If you click Explorer in the module area, a list of available Explorers appears in the menu
area and you can select the required Explorer.
If you click an object in the menu list, this will start the respective process in the contents area.
2-6
A31003-H3540-A800-1-7619, 2003-05-02
Admain2.fm
Management Tools
WBM Window Layout
The following gure is an example of a menu area:
2.3.3
Authentication
When administrators log into WBM from their computer for the rst time, they will see a login
window in which the user name and password must be entered.
As soon as the administrator has been successfully authenticated, a cookie containing the user
name and expiration date will be saved on the computer. The cookie is used for performing authentication whenever WBM is accessed from now until the expiration date. If no valid cookie
is found, the login window will be displayed.
>
You do not have to log off. If you do not perform any action on the gateway for an
hour the session will be terminated automatically. If you have write access for the
gateway, this will also remain active for one hour and prevent other administrators
from modifying gateway data during this time. For security reasons, sessions will always be automatically terminated eight hours after login, even if you are currently
performing actions. You will need to log in again. Terminating a session in this way
will produce an invalid cookie and the login page will be displayed again.
Using this procedure means that the administrator does not have to enter the password for
each access.
A31003-H3540-A800-1-7619, 2003-05-02
2-7
Admain2.fm
Management Tools
Command Line (CLI)
2.3.4
Differences Between Wizards, Maintenance and Explorer

modules
The objective of the Wizards, Maintenance and Explorer modules is the same, namely to display and modify data. The difference lies in the operation and task.
Wizards
The Wizards module for the initial setup combines all operations required for initial gateway
conguration. It guides the administrator through the procedure step by step so that all the
required settings are performed. The other Wizards enable data to be entered and modied using a table editor.
Maintenance
Maintenance functions are displayed as hierarchical tree structures. This module contains
all the functions necessary for HiPath HG 1500 maintenance and administration (see also
Chapter 5 in the Administration and Maintenance manual).
Explorer
Explorer functions are displayed as hierarchical tree structures. This module contains all
the functions necessary for HiPath HG 1500 conguration (see also the Conguration
manual).
2.4
Command Line (CLI)
The command line (CLI) is available on a normal terminal (for example, VTI100) that is connected to the HiPath HG 1500 V.24 serial interface. It is also available via a Telnet client when
in insecure mode. Telnet access is only possible by clients whose IP addresses are released
for this in HiPath HG 1500.
The HiPath HG 1500 command line only supports a selection of basic commands with which
the following tasks can be performed.
Authentication (setting up access, modifying write privilege, conguring Telnet and WBM
clients)
Conguration (conguring gateways, transferring data, rebooting)
System maintenance (diagnosis, controlling gateways and interfaces)
2-8
A31003-H3540-A800-1-7619, 2003-05-02
Admain2.fm
2.4.1
Management Tools
Command Line (CLI)
Overview of Functions
The command line provides a text-only interface for conguring HiPath HG 1500. It permits editing of entered commands and listing of dened commands. The command line is available as
a character stream at the V.24 interface. Remote access to the management interface is also
possible if a modem is connected at the V.24 interface. There is no difference between accessing via a directly connected terminal and accessing via a modem.
The command line is also available at every interface via a Telnet connection over IP.
The management program monitors the number of active management sessions and the administrators who are logged in.
The set of commands for the command line is limited to those required for initialization and basic conguration of the system.
The commands available are described in Appendix A.
2.4.2
General Commands
Commands are available for the following tasks:
displaying a list of all the commands available
jumping to previously dened commands
editing command lines
logging off
activating and deactivating the Telnet function
2.4.3
Authentication
Commands are available for the following authentication tasks:
checking and reserving write access
conguring Telnet clients
conguring WBM clients
2.4.4
Conguring the Gateway
Commands are available for the following conguration tasks:
displaying and setting the IP address and default router
conguring TFTP
A31003-H3540-A800-1-7619, 2003-05-02
2-9
Admain2.fm
Management Tools
SNMP Administration
loading software into the gateway
saving or activating a conguration, loading a conguration into the gateway or loading

a conguration from the gateway onto a server
direct access to the TFTP server
2.4.5
Maintenance
Commands are available for the following Maintenance tasks:
displaying version, date and time
displaying gateway conguration
displaying gateway and interface status reports
displaying the ARP cache
displaying and modifying IP addresses, gateway names and subnet masks
displaying static routes
sending ping and restarting the gateway
2.5
SNMP Administration
SNMP (Simple Network Management Protocol) is designed to be used in conjunction with Network Management Systems (NMS). NMS uses SNMP to integrate the management of network
elements from different manufacturers.
HiPath HG 1500 contains an SNMP agent which accesses a standard MIB 2 as well as a private MIB specic to HiPath HG 1500. Authorized administrators can read out administration
and conguration data via SNMP. Some settings in HiPath HG 1500 can be modied via SNMP.
Both MIBs are available to administrators if a standard operating environment (for example, HP
OpenView) is used.
HiPath HG 1500 can limit SNMP access to certain IP addresses, enabling data to be read out
or modied via the NMS by authorized administrators only.
Read-only access
MIB II (Management Interface Base); RFC 1213
HG 1500MIB (HLB2 conguration and statistics)
RG2599MIB (MIB for some routing functions)
HiPathCommonMonitoringMIB (commonNoticationGroup only)
2-10
A31003-H3540-A800-1-7619, 2003-05-02
Admain2.fm
Management Tools
HiPath 3000 Manager E
Write access
MIB II (system group, TrapDestTable)
HG1500MIB (Control group)
HiPathCommonMonitoringMIB (IPConnControlTable)
SNMP Traps
SNMP can be used to generate traps. Changes to the existing conditions or gateway status are
transferred by the trap in real time. If a trap is generated, HiPath HG 1500 sends a PDU (Protocol Data Unit) trap to the SNMP agent which then forwards it to the NMS.
2.6
HiPath 3000 Manager E is an administration tool for managing a HiPath 5000 RSM database
and the HiPath 5000 nodes. The relevant parts of the HiPath 5000 network are displayed as a
virtual HiPath system.
The program is a 32-bit application and can run under Windows 95, 98, ME, NT4.0 and 2000
operating systems.
The HiPath 5000 system can only be managed by one HiPath 3000 Manager E at any given
time. The IP address of Manager E and the beginning and end of the session is logged at each
session. The log can be read out via the operating systems event le. The modied data continues to be logged in the HiPath 5000 nodes.
HiPath 3000 Manager E takes priority over the applications running in the HiPath system. This
means that the modied data is stored in the HiPath 5000 database and the application is alerted of the change.
A description of HiPath 3000 Manager E will be found in the HiPath 5000 system documentation.
A31003-H3540-A800-1-7619, 2003-05-02
2-11
Admain2.fm
Management Tools
2-12
A31003-H3540-A800-1-7619, 2003-05-02
Admain3.fm
WBM Window Control Icons
WBM is the primary management tool.
3.1
The control area is an applet that constantly provides control and status information. The gure
below shows an example:
The following control icons are available:
Padlock icon (1)
Save icon (2)
Reset icon (3)
Action icon (4)
The following status information is also displayed:
Status of the SSL and IPsec security functions (5)
Access category of the user and system version (6)
System name and location (7)
System date and time, and how long since the last restart (8)
3.1.1
Control Icon Concept
Not all the control icons are always active. Inactive icons are grayed out.
Before an administrator can modify data, the padlock must be unlocked. This reserves write access for a particular administrator, preventing the same data from being modied from another
computer. Data can only be modied from the computer at which write access has been reserved. From all other computers the data can only be read. The save and reset icons are only
available if write access has been reserved. They indicate whether data must be saved, the
gateway must be restarted or whether both are required to end a procedure.
A31003-H3540-A800-1-7619, 2003-05-02
3-1
Admain3.fm

3.1.2
Control Icon Functions
Padlock icon
This icon indicates the current write access status for the administered gateway. The following two statuses are possible:
Data input is blocked. You can read data but you cannot enter or modify it.
Data can be entered. You have read and write access.
The gateway status changes when the padlock icon is clicked.
If data input is blocked, clicking the icon will activate write access from this computer
immediately provided that no other administrator currently has write access.
If data input is blocked and write access is currently activated at another computer, a
warning message will be displayed when you click the padlock icon. The program queries whether write access should be transferred to this administrator. If Yes is clicked,
write access will be transferred from another computer to this administrators computer.
The warning message is shown below:
3-2
If you click the padlock icon while write access is still active on the current computer,
write access will be released even if the data is not yet saved. If data has yet to be
saved and/or a restart is required but has not yet been performed, the relevant control
icons will indicate the present status when write access is next activated.
A31003-H3540-A800-1-7619, 2003-05-02
Admain3.fm

Save icon
This icon saves modied data. It can assume three statuses:
Data input is blocked. The user can read but not write.
Data can be entered but no changes have yet been made. (Data in the RAM
is identical to that in the ash memory.)
Data can be entered. Data has been modied but not saved. (Data in the RAM
differs from that in the ash memory.)
Changes are always made to the conguration that was active at the start of the session
or to the last conguration saved during the session. The modied conguration in the RAM
is saved as a new conguration in the ash memory. The function of the save icon is identical to that of the CLI save configuration command.
Reset icon
This icon triggers a gateway restart. It can assume three statuses:
Data input is blocked. The user can read but not write.
Data input is active but no restart is required.
Data input is active. Data has been modied. The gateway must be restarted
to activate the modied conguration.
Clicking the reset icon will delete any unsaved changes which were made since the start
of the session or since the last time the conguration was saved. The following warning is
displayed before unsaved data is deleted:
If you click Yes, the gateway will restart and the conguration from the ash memory will
overwrite the conguration in the RAM.
The function of the reset icon is identical to that of the CLI reset command.
A31003-H3540-A800-1-7619, 2003-05-02
3-3
Admain3.fm

Tree Representation in the WBM Window
3.2
Tree Representation in the WBM Window
The functions available in the Maintenance and Explorer modules are displayed in the contents area in a tree representation similar to Windows Explorer. This tree representation has
the following icons:
Directories
Main directory closed. The name of the activated function appears next to the main directory.
Main directory open. The usable functions and/or additional directories are displayed under the main directory.
Any directory that contains hidden functions is characterized by
a plus sign (+). A double-click will display these functions.
The functions in this open directory are displayed. A doubleclick will hide these functions.
Bullet points
This function can be activated but does not have status information (color: gray).
This symbol denotes settings which can be reset to factory defaults (color: blue).
This function is active and can be deactivated via a pop-up
menu (color: green).
This function is inactive and can be activated via a pop-up
menu (color: red).
Pop-up menus
A pop-up window opens when you right-click a directory or bullet point. If a display function
is included in the pop-up menu, you can open this directly by a simple click on the directory
or bullet point.
3-4
A31003-H3540-A800-1-7619, 2003-05-02
Admain3.fm
3.3

Starting a WBM Session
Starting a WBM Session
Proceed as follows to start a WBM session:

1.
Start the Web browser.
2.
Enter the gateway IP address as the URL in the browsers address field.
(http://num.num.num.num:8085, where num is a number between 0 and 255).
3.
Press the return key.
4.
Enter your user name and password in the login page and click the login button.
You will see the gateway homepage, in which you can view the available management modules,
a graphic display of the gateway and information on the active software version. Other pages
can be displayed via the existing modules.
The following gure shows a sample WBM homepage:
3.4
Using WBM Wizards
Wizards are basically made up of a series of dialogs. The type and composition of these dialogs
depends on the wizard selected.
A31003-H3540-A800-1-7619, 2003-05-02
3-5
Admain3.fm

Using WBM Wizards
3.4.1
Wizards Module Layout
Wizard dialogs are divided into two areas:
Menu area
with all the functions available in the wizard. You can select a function by clicking it.
Dialog area
in which the dialogs are displayed. You can make entries by selecting or entering the required values.
Refer to Section 2.3, WBM Window Layout for an explanation of the general WBM areas.
Banner area
Module area
Menu
area
Dialog area
Control area
Figure 3-1
3.4.2
Wizard Module Layout
Navigating in a Wizard
You should use the Wizard buttons to navigate and not the forwards and backwards buttons in
the browser.
Your input is sent to HiPath HG 1500 when the Apply button is clicked. If you make changes
to a page which has an Apply button but click Next Page instead of clicking Apply to save
the changes, these changes will be lost.
3-6
A31003-H3540-A800-1-7619, 2003-05-02
Admain3.fm

Using WBM Wizards
You must always click the save button in the control area to save changes to the gateway (before a restart if necessary).
A wizard can be closed at any time by activating the same wizard or by selecting another WBM
module. Any changes will be sent to the gateway or rejected as described above.
3.4.3
Wizard Functions
All wizards are selected via a menu. The following wizards are available:
Initial Setup
PBX Routing
IP Mapping
IP Filter
NAT
MAC Filter
Initial Setup
The following dialogs appear in succession:
Congure gateway properties:
Congure licenses:
specify the number of licensed B channels, licensed functions and license keys
Congure the second LAN interface
specify the gateway name, location and a contact address
specify and congure the required operating mode or deactivate the second LAN interface
Congure logical interfaces
specify the H.323 stack parameters
PBX Routing
PBX routing data can be read out and edited in a table editor. This comprises:
Call Number
Node Number
Service (fax, modem, voice)
A31003-H3540-A800-1-7619, 2003-05-02
3-7
Admain3.fm

Using WBM Wizards
IP Mapping
Data for IP mapping can be read out and edited in a table editor. This comprises:
External IP Address
Internal IP Address
IP Filter
IP lter settings can be read out and dened in a table editor. This comprises:
On (enable or disable lter)
Lower IP Limit (beginning of address space)
Upper IP Limit (end of address space)
Destination IP address
IP Protocol (TCP, UDP, ICMP or all)
NAT
Network Address Translation (NAT) settings can be read out and dened in a table editor. This
comprises:
Destination IP address
Local Port
Global Port
Protocol (TCP or UDP)
MAC Filter
MAC lter settings can be read out and dened in a table editor. This comprises:
On (enable or disable lter)
IP Address
MAC Address
>
3-8
The table editor is described in Chapter 10 of the Conguration manual.
A31003-H3540-A800-1-7619, 2003-05-02
Admain3.fm
3.5

Using WBM Maintenance Functions
Using WBM Maintenance Functions
The Maintenance function dialog provides maintenance-oriented menus combining all the MIB
entries that can be modied. The available functions can be selected from the list in the menu
area.
3.5.1
Maintenance View Layout
Maintenance windows have the following areas:
Menu area
with all the available Maintenance functions. You can select a function by clicking it.
Contents area
The contents area is divided into two sections:
an overview on the left and
a detail view on the right.
The overview is displayed as a tree view.

The detail view shows input elds and command buttons. You can make entries by entering
or selecting values.
The Apply button activates all the changes made.
The Undo button rejects all changes.
The following gure shows a sample Maintenance window:
A31003-H3540-A800-1-7619, 2003-05-02
3-9
Admain3.fm

Using WBM Explorers
3.5.2
Navigating in Maintenance View
Open the Maintenance window by clicking Maintenance in the menu bar and navigate by double-clicking the directory icons. A directory icon may contain a pop-up menu that can be opened
with the right mouse button. Each list entry in the directory has a pop-up menu that can be
opened with the right mouse button. Clicking the function listed in this menu will open a display
or input window or will activate or deactivate a function.
3.5.3
Maintenance Functions
Conguration (conguring gateway on the server or loading from server into the gateway)
Software Image (loading software image from the server to the gateway)
Multigateway Admin (list of gateways, list of conguration tables, job administration)
Joblist (checking the processing of initiated jobs)
Traces (dening the monitoring function and activating or deactivating the monitoring
of individual trace components)
Events (setting the reactions to events, setting e-mail recipients and displaying event
data)
SNMP (setting the alert messages using SNMP traps)
Admin Log (conguring the administration protocol and displaying protocol data)
Actions (setting manual and automatic actions, for example, Garbage Collection)
Conversion (transferring data from HXG cards of the predecessor version to HXG3
cards)
>
3.6
The Conversion maintenance function is described in Chapter 5, Initial Startup of

the Installation manual. All other Maintenance functions are covered by Chapter 5,
Maintenance Tasks of this manual.
Using WBM Explorers
Explorers provide access to all entries in the MIB (Management Information Base) using a tree
representation similar to Windows Explorer. Directories of the required functions can be selected from a list in the menu area.
3-10
A31003-H3540-A800-1-7619, 2003-05-02
Admain3.fm
3.6.1

Using WBM Explorers
Explorer View Layout
Explorer windows have the following areas:
Menu area
with all the available Explorers. You can select an Explorer by clicking it.
Contents area
in which the directories, functions, pop-up menus and data for the respective Explorer are
displayed. Depending on the function selected, data can be displayed, edited or modied.
The contents area is divided into two sections:
an overview on the left and
a detail view on the right.
The overview is displayed as a tree view.

The detail view of the contents area contains buttons for accepting and rejecting changes:
The Apply button activates all the changes made.
The Undo button rejects all changes.
The following gure shows a sample Explorer window:
3.6.2
Navigating in the Explorer View
Open the Explorer view by clicking Explorer in the menu bar and navigate by double-clicking
the directory icon. A directory icon may contain a pop-up menu that can be activated with the
right mouse button. Each list entry in the directory has a pop-up menu that can be opened with
the right mouse button. Clicking the function listed in this menu will open a display or input window.
A31003-H3540-A800-1-7619, 2003-05-02
3-11
Admain3.fm

Using WBM Explorers
3.6.3
Explorer functions
The following Explorers are available in the menu area:
Basic settings
Security
Network Interfaces
Routing (router settings)
Voice Gateway
VCAPI
Payload
Statistics
3-12
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
Security
This chapter describes the regular administration tasks and other tasks which administrators
must normally perform.
>
4.1
All gateway conguration tasks are described in the Conguration manual.
Security
Access and the allocation of access rights are performed via a login window.
4.1.1
Logging In and Passwords
Management access to HiPath HG 1500 is password-protected.
>
Several sessions can be simultaneously active. The local management application

displays a warning message when other sessions are active, but does not limit the
administrators options even in this case. We therefore urge you to take organizational measures to ensure that no two administrators attempt to process the same object
simultaneously.
When users log in from their computer for the rst time, they will see a login window in which
they must enter the user name and password. The password is veried by the gateway.
As soon as the user has been successfully authenticated, a cookie containing the user name
and expiration date will be saved on the computer. From then on, the cookie is used for WBM
access authentication. If no valid cookie is found, the login window will be displayed.
Using this procedure means that the administrator does not have to enter the password for
each access.
4.1.2
Access Rights
Depending on the intended role, predened read and write rights are available to users after
they have entered their password.
You can use HiPath 3000 Manager E to set up user accounts (see documentation for HiPath
3000 Manager E). Access rights and user accounts cannot be managed via WBM.
A31003-H3540-A800-1-7619, 2003-05-02
4-1
Admain4.fm
Sequence of a WBM Session
4.2
Some steps of a WBM session are always the same, irrespective of the concrete tasks. This
subsection describes these typical steps.
4.2.1
Starting WBM
Perform the following steps to start a WBM session:

1.
Start the Web browser.
2.
Enter the gateway IP address as the URL in the browsers address field.
(http://num.num.num.num:8085, where num is a number between 0 and 255). Note that
the port number 8085 must be specied.
3.
Press the return key.
The rst time WBM is started from this computer, a login window is displayed in which the user
name and password must be entered. If WBM has previously been successfully started from
this computer, the Web server checks the authentication cookie and grants the relevant access.
After successful authentication, the gateway start page is displayed and all modules are available to you.
4.2.2
Selecting a Module
Five different modules are available:
Chapter 2 provides overview descriptions of the modules.

The various modules are intended for the following purposes:
Logoff
This module terminates a session.
Wizard
The Wizard module for the initial setup combines all operations required for initial gateway
conguration. It guides the administrator through the procedure step by step so that all the
required settings are performed. The other Wizards enable data to be entered and modied using a table editor.
4-2
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
Maintenance
Maintenance functions are displayed as hierarchical tree structures. This module contains
all the functions necessary for HiPath HG 1500 maintenance and administration (see also
Chapter 5 in the Administration and Maintenance manual).
Explorer
Explorer functions are displayed as hierarchical tree structures. This module contains all
the functions necessary for HiPath HG 1500 conguration (see also the Conguration
manual).
Help
In addition to the online documentation, there is access to further help information (about
links, versions, etc.).
4.2.3
Using a Module
When the administrator selects a module, the function window for that module opens
You can navigate within a module via a xed dialog sequence (for Wizards) or using the menu
area at the left of the WBM window (for Maintenance and Explorers).
The following icons are available to control how modications are handled:
Clicking the padlock icon enables write access from this terminal. You must activate
write access before modifying data. Write access remains active for the entire session.
Your write access is disabled by logging off, by clicking the padlock icon again, or when
write access is enabled for another administrator.
Clicking the save icon saves changes and updates the display accordingly. Click this
icon to apply your changes.
Clicking the reset icon rejects all changes made since the beginning of the session or
since the last time changes were saved. The gateway restarts and the conguration in
the ash memory replaces that in the RAM. The conguration from the beginning of
the session or the last saved conguration is restored. Click this icon if you want to reject all unsaved changes.
>
Maintenance functions, Wizards and Explorer editing options are only available if
you enable write access using the padlock icon. The Explorer display functions are
available at any time.
A31003-H3540-A800-1-7619, 2003-05-02
4-3
Admain4.fm
Example
To modify a value:
1.
Click the padlock icon to ensure that no other administrator can modify this information at
the same time.
2.
Navigate to the required input mask.
3.
Edit the information.
4.
Click the reset icon if you need to restore the original conguration valid before the change.
5.
Click the save icon to save changes in HiPath HG 1500.
4.2.4
Terminating a Session
Once you have performed all the tasks or when the gateway monitoring has ended, you should
terminate the session.
1.
If you have activated write access, disable it by clicking the padlock icon again.
2.
Click the Logoff module to log off. If you wish to remain logged in, simply close the browser window without terminating the browser.
>
Do not terminate a WBW session by closing the browser as this may lead to
problems when restarting WBM.
If conguration changes have not been saved when logging off, or if a necessary board reset has not yet been performed (the respective icons in the control area are red), the following warning will appear:
Click Cancel. To save changes: Click the save icon in the control area. If a reset is necessary: Click the reset icon in the control area.
If you click OK, the browser will be closed and you will be logged off. Unsaved changes
will be lost.
4-4
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
>
4.3
Configuring Access
You do not have to log off. If you do not perform any action on the gateway for an
hour the session will be terminated automatically. If you have write access for the
gateway, this will also remain active for one hour and prevent other administrators
from modifying gateway data during this time. For security reasons, sessions will always be automatically terminated eight hours after login, even if you are currently
performing actions. You will need to log in again. Terminating a session in this way
will produce an invalid cookie and the login page will be displayed again.
Conguring Access
Telnet access is congured and WBM clients are administrated via the CLI command line or via
WBM.
4.3.1
Conguring Telnet Access via the Command Line
To allow Telnet clients access to the gateway, enter the IP addresses from which Telnet access
to the gateway should be permitted.
To grant Telnet access from another IP address, enter:
add telnet client <ip address>
To prevent Telnet access from a previously released IP address, enter:
delete telnet client <ip address>
To view a list of the released IP addresses, enter:
show telnet clients
4.3.2
Conguring WBM Clients via the Command Line
To allow WBM clients access to the gateway, enter the IP addresses from which WBM access
to the gateway should be permitted.
To enter a new WBM client, enter:
add wbm client <ip address>
To delete an existing WBM client, enter:
delete wbm client <ip address>
To view a list of existing WBM clients, enter:
show wbm clients
A31003-H3540-A800-1-7619, 2003-05-02
4-5
Admain4.fm
Configuring Access
4.3.3
Conguring WBM Clients and Telnet Clients in WBM
1.
Open the WBM window.
2.
Click the padlock icon to activate write access (if you do not already have it).
3.
Click the Explorer module.
4.
Click Security in the menu at the left of the window.
5.
Right-click IP Administration Access and select Add Permitted IP Address for Administration from the pop-up menu.
The following dialog is displayed in the contents area:
6.
Make the following entries:
Permitted IP Address: Enter the IP address for which Telnet and WBM are to have
access rights.
Telnet Access: Select this option if Telnet access should be permitted.
WBM Access: Select this option if administration via WBM is to be enabled.
7.
Click Apply. The conguration is modied and the dialog title changes from add to edit.
8.
Click the save icon in the control area.
4.3.4
Using Telnet Access
To use Telnet access for administration:

1.
Enter the command telnet <gateway name> in a Telnet terminal.
2.
When a corresponding prompt appears, enter your user name and password.
After entering your name and correct password you can enter all the commands of the command line (CLI) in the Telnet terminal.
4-6
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
>
4.4
Backing up System Files
Telnet access privileges are administrated via WBM (see the description for IP administration access in Chapter 4 of the Conguration manual).
Backing up System Files
For security reasons, you should create a backup copy of conguration les so that you can
replace damaged les without any problems. HiPath HG 1500 can save les to a server (via
TFTP) or to a connected PC (via HTTP).
The corresponding procedure is described in Section 5.5.4, Saving Conguration Data on a
Server or PC.
Reverting to backup les
Section 5.5.3, Loading Conguration Data from Server or PC describes how to download
backup copies to the gateway.
4.5
Monitoring
The gateway performance and status can be monitored by the administrator. This information
is available as:
Performance statistics
LEDs
Traces (procedure recording), see Section 4.6, Traces (Procedure Recording)
Events, see Section 4.7, Events
Traps, see Section 4.8, Traps
A31003-H3540-A800-1-7619, 2003-05-02
4-7
Admain4.fm
Monitoring
4.5.1
Performance Statistics
These statistics enable managers to evaluate gateway performance and to pinpoint bottlenecks. All performance data is read-only.
To activate the statistical functions:
1.
2.
Click the Explorer module.
3.
Click Statistics at the left of the Explorer menu.
4.
To view the respective statistics:

LAN statistics
Double-click Device-Statistics
Right-click LAN Statistics
SCN statistics
Double-click Device-Statistics
Right-click SCN Statistics
MSC statistics
Double-click MSC Statistics
Right-click Overall Statistics

or Per-Call Statistics
Call statistics
Double-click Call Statistics
Right-click the required statistics
The following statistics window is displayed:

LAN Statistics
displays the congured and used channels of individual LAN devices:
4-8
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
Monitoring
SCN Statistics
displays the congured and used channels of individual SCN devices:
MSC Statistics
The following statistics are available via Media Stream Control (MSC):
Overall Statistics (an overview of statistics for all calls)
Per-Call Statistics (individual statistics for each active call)
The following gure shows a sample window with individual call data.
Call Statistics
The following call statistics are available:
Call Statistics 1h displays the LAN, PBX and data call statistics for the last hour
Call Statistics 24h displays the LAN, PBX and data call statistics for the last 24 hours
LAN Call Statistics displays the statistics of the voice and fax calls received via LAN in
the last hour and the last 24 hours
A31003-H3540-A800-1-7619, 2003-05-02
4-9
Admain4.fm
Traces (Procedure Recording)
PBX Call Statistics displays the statistics of the voice and fax calls received via PBX in
Data Call Statistics displays the statistics of the data calls received via LAN and PBX in
The following gure shows a sample window with LAN call statistics.
4.6
A trace logs the execution of a software component. A technician can use these process
records to nd the cause of an error.
>
To improve legibility and statement value, the additional Trace Monitoring Tool
(TMT) program which is available to Siemens technicians can be used to analyze
trace logs.
Trace results can be:
displayed on a console that is connected to a V.24 interface

(console trace) and/or,
saved in a log le and/or
saved on a PC via a LAN connection.
4-10
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
4.6.1
Displaying a Trace Conguration
To display the current trace conguration:

1.
2.
Click the Maintenance module.
3.
Click Traces at the left of the Maintenance menu.
4.
Right-click Trace Conguration and select Display Trace Conguration.

The current trace conguration is displayed:
4.6.2
Editing a Trace Conguration
To edit the current trace conguration:

1.
2.
3.
4.
5.
Right-click Trace Conguration and select Edit Trace Conguration. The following dialog
appears:
A31003-H3540-A800-1-7619, 2003-05-02
4-11
Admain4.fm
Select Switch Console Trace On to output trace data to the console at the V.24 connector.
Select Switch File Trace On to write trace data to a log le.
Select Switch Trace via LAN On to transfer trace data via the LAN interface.
6.
Click Apply. The conguration is modied.
4.6.3
Loading Trace Log File to the Server or PC
You can use WBM to copy the log le from the ash memory to a TFTP server or to a PC. It
can then be opened, edited and printed using any text editor.
1.
2.
3.
4.
5.
Right-click Trace Log and select Load via HTTP or Load via TFTP from the pop-up
menu.
The following dialog appears when Load via TFTP is selected:
4-12
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
Select the TFTP server and enter the name which should be assigned to the log le on the
server in the Remote Filename eld. The gateway automatically enters the IP addresses
last entered for the default and alternative TFTP servers. You only need to edit these if the
addresses have been changed. Click Load.
6.
The following dialog is displayed:
7.
Click OK.
A dialog for saving data is displayed. Specify the le name for the log le and the storage
location.
4.6.4
Deleting the Gateway Trace Log File
The log le can be deleted from the gateway ash memory.

1.
2.
3.
4.
5.
Right-click Trace Log and select Clear Trace Log from the pop-up menu.
A31003-H3540-A800-1-7619, 2003-05-02
4-13
Admain4.fm
The following warning appears:
6.
Click Clear Log. The gateway log le is deleted.
4.6.5
Displaying the H.323 Stack Trace Conguration
To display the current stack trace conguration for H.323 monitoring:

1.
2.
3.
4.
Right-click H.323 Stack Trace and select Display H.323 Stack Trace. The current conguration is displayed:
4.6.6
Editing the H.323 Stack Trace Conguration
To edit the current stack trace conguration for H.323 monitoring:

1.
2.
4-14
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
3.
4.
5.
Right-click H.323 Stack Trace and select Edit H.323 Stack Trace.
The following dialog appears:
6.
Edit the following settings:
Debug Level: Debug levels have a value range from 0 to 9. 0 stands for the least
amount and 9 for the greatest amount of detail, thus the higher the number the greater
the quantity of trace information.
Clear All Debug Switches: No module is monitored when this option is selected.
Debug Modules: You can select for each module whether or not it should be monitored. The module is monitored when the option is selected.
7.
8.
A31003-H3540-A800-1-7619, 2003-05-02
4-15
Admain4.fm
4.6.7
Trace Proles
You can create your own proles where you combine the monitoring of individual components,
or you can use the predened trace proles. Customized proles can be newly created, modied or deleted.
To display all trace proles:
1.
2.
3.
4.
Right-click Trace Proles and select Display All Trace Proles.

All trace proles (including those you created) are displayed:
The entries can be sorted. A triangle after a column name (for example, Prole Name)
indicates the column by which data was sorted. If you wish to sort the table by another
column, click the respective column name. The trace proles started are displayed in bold
type.
To add an empty trace prole:
1.
2.
3.
4.
5.
Right-click Trace Proles and select Add Trace Prole (Empty Prole).
4-16
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
6.
Enter a name for the prole in the Prole Name eld and click Apply. An empty trace
prole is created in the Trace Proles folder.
To add a trace prole with the current setting:

1.
2.
3.
4.
5.
Right-click Trace Proles and select Add Trace Prole (with Current Trace Settings). The
following dialog appears:
6.
Enter a name for the prole in the Prole Name eld. You can deselect the current trace
component settings individually or together. You can also modify the trace level individually
or set it to 0 for all components.
7.
Click Apply. A new trace prole is created in the Trace Prole folder containing the selected trace component settings.
8.
A31003-H3540-A800-1-7619, 2003-05-02
4-17
Admain4.fm
To view a trace prole:

1.
2.
3.
4.
Right-click a required trace prole and select Display Trace Prole.

To modify a trace prole which you added yourself:
>
You cannot modify or delete any trace profiles defined by the manufacturer.
1.
2.
3.
4.
5.
Right-click a required trace prole and select Display Trace Prole.
4-18
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
6.
If necessary, change the prole name in the Prole Name eld. You can deselect the current trace component settings individually or together. You can also modify the trace level
individually or set it to 0 for all components.
7.
8.
To start a trace prole:

1.
2.
3.
4.
A31003-H3540-A800-1-7619, 2003-05-02
4-19
Admain4.fm
5.
Right-click the required trace prole and select Start Trace Prole from the pop-up menu.
The icon next to the trace prole name changes from red to green.
6.
To stop a trace prole:

1.
2.
3.
4.
5.
Right-click the required trace prole and select Stop Trace Prole from the pop-up menu.
The icon next to the trace prole name changes from green to red.
6.
To delete a trace prole which you added yourself:
>
You cannot modify or delete any trace profiles defined by the manufacturer.
1.
2.
3.
4.
5.
Right-click the required trace prole and select Delete Trace Prole from the pop-up
menu.
6.
Click Delete. The trace prole is deleted.
7.
4-20
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
To view the setting for a trace component:

1.
2.
3.
4.
Double-click Trace Components in the tree representation.
5.
Right-click a required trace component and select Display Trace Component from the
pop-up menu.
To edit the setting for a trace component:

1.
2.
3.
4.
5.
6.
Right-click a required trace component and select Edit Trace Component from the popup menu.
A31003-H3540-A800-1-7619, 2003-05-02
4-21
Admain4.fm
You can make the following entries:
Trace Level: Trace levels have a value range from 0 to 9. 0 stands for the least amount
and 9 for the greatest amount of detail, thus the higher the number the greater the
quantity of trace information.
Trace On: Select this option to monitor this component.
Data Included in the Trace Output: You can select for each parameter whether or not
it should be recorded in the log le. Each selected parameter is logged in the le.
>
There are trace components which cannot be modied and some that can only be
modied to a limited extent. Trace component elements which cannot be modied
are grayed out.
7.
8.
To start monitoring a trace element

1.
2.
3.
4.
4-22
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
5.
6.
Right-click a required trace component and select Start Trace Component from the popup menu. The icon next to the trace component name changes from red to green.
To stop monitoring by a trace component:

1.
2.
3.
4.
5.
6.
Right-click a required trace component and select Stop Trace Component from the popup menu. The icon next to the trace component name changes from green to red.
To view all trace components:

1.
2.
3.
4.
Right-click Trace Components and select Display All Trace Components. The following
dialog appears:
A31003-H3540-A800-1-7619, 2003-05-02
4-23
Admain4.fm
To view all started trace components:

1.
2.
3.
4.
Right-click Trace Components and select Display Started Trace Components. The following dialog appears:
To view all stopped trace components:

1.
2.
3.
4.
Right-click Trace Components and select Display Stopped Trace Components.

4-24
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
To make changes to several trace components:

1.
2.
3.
4.
5.
Right-click Trace Components and select Edit Trace Components.

Trace Level: Trace levels have a value range from 0 to 9. 0 stands for the least amount
Trace On: Select this option to monitor this component.
>
6.
There are trace components which cannot be modied and some that can only be
modied to a limited extent. Trace component elements which cannot be modied
are grayed out.
A31003-H3540-A800-1-7619, 2003-05-02
4-25
Admain4.fm
7.
To stop all trace components:

1.
2.
3.
4.
5.
Right-click Trace Components and select Stop All Trace Components.
6.
4.6.8
Trace Probes
A list of events can be logged and saved to enable gateway problems to be analyzed with the
WindView software.
Analysis after a system crash
in the event of a system crash, log data is saved to the ash le system. This data can be transferred to a host computer and can be read there with WindView.
Online analysis
Selected events are logged with the WindView software running. The saving of data can be
started and terminated via the WBM.
Displaying all Probes components
To display the status of all Probes components:
1.
2.
3.
4.
Right-click Probes and select Display All Probes Components.
4-26
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
This shows whether global event generation is activated and which trace component is
activated at which level.
The entries can be sorted. A triangle after a column name (for example Component) indicates the column by which data was sorted. If you wish to sort the table by another column, click the respective column name.
Editing all Probes components
To edit the settings for all Probes components:
1.
2.
3.
4.
5.
Right-click Probes and select Edit All Probes Components.
A31003-H3540-A800-1-7619, 2003-05-02
4-27
Admain4.fm
Event Level: Event levels have a value range from 0 to 9. 0 stands for the least amount
Active: Select this option to monitor this component.
Set All to 0: Set the event level of all components to zero.
None: Deactivates all components.
6.
7.
Starting and stopping global event generation

To start and stop global event generation:
4-28
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
1.
2.
3.
4.
5.
Right-click Probes and select Start Global Event Generation or Stop Global Event Generation.
6.
Displaying properties of a component:

To display the Probe settings of a component:
1.
2.
3.
4.
Double-click Probes.
5.
Right-click the required component and select Display Probe Settings.

Editing a Probe component

To edit settings for a Probe component:
1.
2.
3.
4.
A31003-H3540-A800-1-7619, 2003-05-02
4-29
Admain4.fm
5.
6.
Right-click the required component and select Edit Probe Settings.

Event Level: Event levels have a value range from 0 to 9. 0 stands for the least amount
Switch Component Event Generation on: Select this option to monitor this component.
Switch Global Event Generation on: Select this option if the component is to be
monitored during global event generation.
7.
8.
Starting and stopping component monitoring

To start and stop monitoring a selected component:
1.
2.
3.
4.
5.
4-30
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
Events
6.
Right-click the required component and Start Global Event Generation or Stop Global
Event Generation.
7.
4.7
Events
Events report problems in the system. The administrator should check the network or gateway
conguration to correct the irregularity.
>
Refer to Section 6.3.3, Events for a description of the event log le.
You can use the Maintenance function to:
save the event data written to a le to an external system.
dene an e-mail address to be informed of certain events, and
dene which actions are to be executed on certain events.
4.7.1
Event Conguration
You can view the event conguration settings and specify whether the event log should be
transferred via a LAN.
Displaying an event conguration
To view the event conguration setting:
1.
2.
3.
Click Events at the left of the Maintenance menu.
4.
Right-click Event Conguration and select Display Event Conguration.
A31003-H3540-A800-1-7619, 2003-05-02
4-31
Admain4.fm
Events
Enabling and Disabling logging via the LAN

To activate and deactivate event logging via LAN:
1.
2.
3.
4.
5.
Right-click Event Conguration and select Edit Event Conguration from the pop-up
menu.
6.
You can enable and disable the following functions:
4-32
Switch Event Logging via LAN On: Select this function to activate event logging via
the LAN.
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
7.
8.
4.7.2
Events
Transferring an Event File
You can save an event le to an external system, It can then be opened, edited and printed using any text editor.
To save an event le to an external system:
1.
2.
3.
4.
5.
Right-click Event Log and select Load via HTTP or Load via TFTP from the pop-up
menu.
Select the TFTP server and enter the name which should be assigned to the log le on the
server in the Remote Filename eld. The gateway automatically enters the IP addresses
last entered for the default and alternative TFTP servers. You only need to edit these if the
addresses have been changed. Click Load.
A31003-H3540-A800-1-7619, 2003-05-02
4-33
Admain4.fm
Events
6.
7.
Click OK.
location.
4.7.3
Deleting the Gateway Event Log File
The log le can be deleted from the gateway ash memory.

1.
2.
3.
4.
5.
Right-click Event Log and select Clear Event Log from the pop-up menu.
6.
Click Clear Log. The gateway event log le is deleted.
4.7.4
Displaying E-Mail Settings
You can set to which e-mail address a warning is sent when an event occurs. To view the current settings:
1.
2.
4-34
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
3.
4.
Right-click E-mail and select Display E-mail Settings.
Events
4.7.5
Editing E-Mail Settings
You can set to which e-mail address a warning is sent when an event occurs. To edit the setting:
1.
2.
3.
4.
5.
Right-click E-mail and select Edit E-mail Settings from the pop-up menu.
A31003-H3540-A800-1-7619, 2003-05-02
4-35
Admain4.fm
Events
6.
SMTP Server Settings: Enter the IP address, port and SMTP server domain. Comply
with the conventions of standard protocols RFC 821 and RFC 822.
>
SMTP server settings are required because HiPath HG 1500 only supports the
Relay Agent function and cannot itself be used as the SMTP server.
Select an SMTP server without authentication because HiPath HG 1500 does not support any authentication mechanisms as regards SMTP.
The SMTP domain designates the HiPath HG 1500 and it should be unique because
it is used as the sender of the e-mail.
The port for the SMTP server is preset to 25.
E-mail Settings: Enter the sender and a text which clearly identies the incoming email as indicating an event.
E-mail Address (Recipients): The e-mail warning can be sent to up to ve addresses. Enter at least one e-mail address in the top address eld.
4-36
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
7.
8.
4.7.6
Events
Displaying the Reaction Settings for All Events
You can display the reaction settings for all events:

1.
2.
3.
4.
Right-click Reaction Table and select Display All Events from the pop-up menu.
4.7.7
Setting Reactions to Individual Events
For each event type, you can set how the system should react to this event.
To view the current setting:
1.
2.
3.
4.
Double-click Reaction Table.
5.
Right-click an event and select Display Event from the pop-up menu.
A31003-H3540-A800-1-7619, 2003-05-02
4-37
Admain4.fm
Events
To edit the reaction to an event type:

1.
2.
3.
4.
5.
Double-click Reaction Table.
6.
Right-click an event and select Edit Event from the pop-up menu.
4-38
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
Traps
Send an E-mail: If this option is selected an e-mail is sent when this event occurs.
Associated Trace Prole: You can allocate one of your dened trace proles to this
event.
Start / Stop Trace Prole: You can specify whether the selected trace prole should
be started or stopped by this event.
7.
8.
4.8
Traps
If gateway problems occur, traps are generated to inform administrators of errors and failures.
There are two types of traps:
System traps
Performance traps
Trap Types
Description
System trap
Indicates a system error and calls for immediate

corrective action.
Performance trap
Indicates performance problems but does not call

for any corrective action. Traps are only used to
provide information.
Table 4-1
>
Trap Types
Details of traps and the recommended actions for error correction are described in
Section 6.3.1, Traps.
Traps are classied according to their effect and are colored accordingly in the tree representation.
Effect Classes
Bullet Point Colors
Critical
Red
Major
Red
Minor
Orange
Warning
Yellow
Table 4-2
Effect Classes for Traps
A31003-H3540-A800-1-7619, 2003-05-02
4-39
Admain4.fm
Traps
Effect Classes
Bullet Point Colors
Deleted
Green
Informative
Gray
Intermediate status
Gray
Other traps
Gray
Table 4-2
Effect Classes for Traps
Traps are sorted in the tree representation and in the table (see Section 4.8.2, Displaying a List
of All Critical Traps) in the order they occur in the system.
4.8.1
Displaying a List of All Traps
You can display a list of all traps.

1.
2.
3.
Click SNMP at the left of the Maintenance menu.
4.
Right-click Traps and select Display All Traps from the pop-up menu.
The display is automatically updated every 30 seconds. The time until the next update is
displayed. Click Refresh if you wish to update the window sooner.
4-40
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
4.8.2
Traps
Displaying a List of All Critical Traps
You can display a list of all critical traps.

1.
2.
3.
4.
Right-click Traps and select Display All Critical Traps from the pop-up menu.
The display is automatically updated every 30 seconds. The time until the next update is
displayed. Click Refresh if you wish to update the window sooner.
4.8.3
Displaying Individual Traps
You can display information on the individual traps.

1.
2.
3.
4.
Double-click Traps.
5.
Right-click a trap and select Display Trap from the pop-up menu.
A31003-H3540-A800-1-7619, 2003-05-02
4-41
Admain4.fm
Traps
The following list appears:
The rst four entries have the following meaning:
Trap severity (for example, Information)
Trap name
Explanation of this trap
Trap type (1 = software, 2 = hardware)
4.8.4
Displaying a List of All SNMP Communities
You can display a list of all SNMP communities.

1.
2.
3.
4.
Right-click Communities and select Display Communities from the pop-up menu.
4-42
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
Traps
The following table appears:
Each SNMP subscriber is displayed in the table with its IP address. The SNMP access
rights (community) and SNMP type are also displayed.
4.8.5
SNMP Read Communities
To display a list of all the SNMP read communities:

1.
2.
3.
4.
Double-click Communities.
5.
Right-click Read Communities and select Display Read Communities from the pop-up
menu.
Each SNMP read community is displayed in the table with its IP address.
To display information on an SNMP read community:
1.
2.
3.
4.
A31003-H3540-A800-1-7619, 2003-05-02
4-43
Admain4.fm
Traps
5.
Double-click Read Communities.
6.
Right-click an SNMP subscriber and select Display Community from the pop-up menu.
The IP address and SNMP access rights (community) are displayed for the selected SNMP
community.
To create an SNMP read community:
1.
2.
3.
4.
5.
6.
Right-click Read Communities and select Add Read Community from the pop-up menu.
Enter the recipient information in the input elds:
IP Address: Enter the IP address of the new trap recipient in this eld.
Community: This eld denes the SNMP access rights. Enter the community as a
character string.
4-44
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
Traps
7.
Click Apply. The read community is set up and the dialog title changes from add to
edit.
8.
To edit an SNMP read community:

1.
2.
3.
4.
5.
6.
7.
Right-click the required community and select Edit Community from the pop-up menu.
character string.
8.
Click Apply. The read community is modied.
9.
To delete an SNMP read community:

1.
2.
3.
A31003-H3540-A800-1-7619, 2003-05-02
4-45
Admain4.fm
Traps
4.
5.
6.
7.
Right-click the required community and select Delete Community from the pop-up menu.
8.
Click Delete. The read community is deleted.
9.
4-46
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
4.8.6
Traps
SNMP Write Communities
To display a list of all the SNMP write communities:

1.
2.
3.
4.
5.
Right-click Write Communities and select Display Write Communities from the pop-up
menu.
Each SNMP write community is displayed in the table with its IP address.
To create an SNMP write community:
1.
2.
3.
4.
5.
6.
Right-click Write Communities and select Add Write Community from the pop-up menu.
A31003-H3540-A800-1-7619, 2003-05-02
4-47
Admain4.fm
Traps
character string.
7.
Click Apply. The write community is set up and the dialog title changes from add to
edit.
8.
To display information on an SNMP write community:

1.
2.
3.
4.
5.
Double-click Write Communities.
6.
Right-click an SNMP subscriber and select Display Community from the pop-up menu.
The IP address and SNMP access rights (community) are displayed for the selected SNMP
community.
To edit an SNMP write community:
1.
2.
3.
4.
5.
6.
7.
Right-click the required community and select Edit Community from the pop-up menu.
4-48
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
Traps
character string.
8.
Click Apply. The write community is modied.
9.
A31003-H3540-A800-1-7619, 2003-05-02
4-49
Admain4.fm
Traps
To delete an SNMP write community:

1.
2.
3.
4.
5.
6.
7.
Right-click the required community and select Delete Community from the pop-up menu.
8.
Click Delete. The write community is deleted.
9.
4.8.7
Trap Communities
To display a list of all the trap communities:

1.
2.
3.
4.
5.
Right-click Trap Communities and select Display Trap Communities from the pop-up
menu.
4-50
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
Traps
The IP address and the SNMP access rights (community) are displayed for all trap recipients.
To add a new trap community:
1.
2.
3.
4.
5.
6.
Right-click Trap Communities and select Add Trap Community from the pop-up menu.
character string.
7.
Click Apply. The new trap community is set up and the dialog title changes from add to
edit.
8.
A31003-H3540-A800-1-7619, 2003-05-02
4-51
Admain4.fm
Traps
To display information on a selected trap community:

1.
2.
3.
4.
5.
Double-click Trap Communities.
6.
Right-click the required trap recipient and select Display Trap Community from the popup menu.
The IP address and the SNMP access rights (community) are displayed for this trap recipient.
To edit the attributes of a selected trap community:
1.
2.
3.
4.
5.
6.
7.
Right-click the required trap recipient and select Edit Trap Community from the pop-up
menu.
4-52
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
Traps
8.
character string.
Click Apply. The trap community is modied.
To delete a trap community:

1.
2.
3.
4.
5.
6.
7.
Right-click the required trap recipient and select Delete Trap Community from the pop-up
menu.
8.
Click Delete. The trap community is deleted.
A31003-H3540-A800-1-7619, 2003-05-02
4-53
Admain4.fm
System Actions
9.
4.9
System Actions
The Actions Maintenance function supports frequently recurring administrative tasks. Some
actions must be performed manually; others are performed automatically.
The following administration tasks can be performed manually:
delete trace logs
delete event logs
delete administration logs
The following administration tasks can be performed automatically:
Garbage collection
Software activation
4.9.1
Manual Actions
You can manually:
delete trace logs
delete event logs
delete administration logs
delete trace logs

You can delete trace les manually using this function:
1.
2.
3.
4.
Click Actions in the menu at the left of the window.
5.
Double-click Manual Actions.
6.
Right-click Trace Log and select Clear Files from the pop-up menu.
4-54
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
System Actions
7.
Select the required action:
Clear Log: deletes the log le
Dont Clear: cancels the procedure; data is not deleted.
Deleting event logs

You can delete event logs manually using this function:
1.
2.
3.
4.
Click Actions at the left of the Maintenance menu.
5.
6.
Right-click Event Log and select Clear Files from the pop-up menu.
7.
A31003-H3540-A800-1-7619, 2003-05-02
4-55
Admain4.fm
System Actions
Deleting administration logs

You can delete event logs manually using this function:
1.
2.
3.
4.
5.
6.
Right-click Admin Log and select Clear Files from the pop-up menu.
7.
4.9.2
Automatic Actions
For the following functions:
Garbage Collection
Software Activation
you can perform automatic settings, enable and disable the function and view the status.
Software Activation
To set the time for activating a new software image:
1.
2.
3.
4-56
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
System Actions
4.
5.
Double-click Automatic Actions.
6.
Right-click Software Activation and select Edit Action from the pop-up menu.
The following is displayed in the contents area:
Action Activated: The new software image is automatically loaded when this option
is selected.
Start Action in: The time in days, hours and minutes until the action is started.
Start Action on: The date and time when the action should begin.
The version of the inactive software image which has been loaded is displayed. The Apply
button is only active when a software image is available.
Click Use Calendar to select the date from a calendar.
A31003-H3540-A800-1-7619, 2003-05-02
4-57
Admain4.fm
System Actions
The display is extended to include the following eld:
You can scroll between years and months using the arrow keys. Click the required day to
apply the date in the start eld.
7.
8.
Setting the garbage collection

To perform the settings for the garbage collection:
1.
2.
3.
4.
5.
6.
Right-click Garbage Collection and select Edit Action from the pop-up menu.
4-58
A31003-H3540-A800-1-7619, 2003-05-02
Admain4.fm
System Actions
The following is displayed in the contents area:
Action Activated: The automatic garbage collection is activated when this option is
selected.
Start Time (after midnight): The time at which the garbage collection is performed.
Days on which to Perform Action: The week days on which the garbage collection
is performed.
7.
8.
Enabling or disabling an automatic action

To enable or disable the automatic action:
1.
2.
3.
4.
A31003-H3540-A800-1-7619, 2003-05-02
4-59
Admain4.fm
System Actions
5.
6.
Right-click Garbage Collection or Software Activation and select Stop Action from the
pop-up menu to disable the function or select Start Action to enable the function.
7.
Viewing the status of the automatic action

To view the status of the automatic action:
1.
2.
3.
4.
5.
Right-click Garbage Collection or Software Activation and select Display Action from
the pop-up menu.
The following dialog appears for Garbage Collection:
The following dialog appears for Software Activation:
4-60
A31003-H3540-A800-1-7619, 2003-05-02
Admain5.fm
Maintenance Tasks
Safety Information for Maintenance
Maintenance Tasks
The architecture of the HiPath HG 1500 is designed to enable updates to the hardware (e.g.
via new DSP modules) and software. Standardized HGA slots make it possible to add or exchange modules.
5.1
The following information is aimed at service personnel and authorized specialists.

Read through all information on the equipment carefully, and follow all safety instructions. Make
sure you know the emergency numbers.
Always contact your supervisor before starting work if the necessary safety measures do not
appear to be in place (e. g. risk of gas explosion, humidity).
Safety symbols
This chapter uses the following symbols to indicate potential hazards:
Danger
This symbol warns that a situation may cause death or serious injury.
Warning
This symbol indicates hazards which may lead to serious injury.
Caution
This symbol indicates a risk of damage to hardware or software.
>
This symbol denotes useful information.
Further symbols for identifying sources of danger in greater detail

The following symbols may appear on equipment:
Electricity
Weight
Heat
Fire
Chemicals
ESD*
Laser
* Electrostatically Sensitive Devices
A31003-H3540-A800-1-7619, 2003-05-02
5-1
Admain5.fm
Maintenance Tasks
5.1.1
Safety Information: Danger
HiPath 3500 and HiPath 3300

Potentially hazardous circuits are accessible in HiPath 3500 and HiPath 3300 19 systems.
These systems should therefore only be operated with closed housing.
Dangerous voltages
Voltages above 30 V AC (alternating current) or 60 V DC (direct current) are dangerous.
Damage
If the power cable appears to be damaged, replace it immediately.
Immediately replace any damaged safety equipment (covers, labels and protective cables).
Accessories
Use only original accessories or components permitted specically for the system. Failure to
comply with these safety instructions may cause irreversible damage to the installation or violate safety and EMC regulations.
Working on electrical circuits
Work on the low voltage network (100240 V AC) may only be carried out by those with
appropriate qualications or by an authorized technician.
If you are handling circuits with dangerous voltages, always work with a partner who knows
the location of the power supply switches.
Always ensure adequate insulation when touching powered circuits.
Ensure that the installation is not powered by an additional power supply, or protected via
an additional fuse or additional main switch.
Before starting any work, check whether the corresponding circuits are still on power. Never take it for granted that all circuits have reliably been disconnected from the power supply
when a fuse or a main switch has been switched off.
During a thunderstorm, you should not connect or remove telephone lines or boards.
Expect to encounter leakage current from the telecommunications network.
Ensure that, whenever work is carried out on an open installation, the installation is never
left unsupervised.
5-2
A31003-H3540-A800-1-7619, 2003-05-02
Admain5.fm
5.1.2
Maintenance Tasks
Safety Information: Warning
Protective clothing and equipment
When working on the installations, never wear loose clothing and always tie back long hair.
Never wear jewelry, metal watch straps or items such as metal ttings or metal rivets on
items of clothing. These could cause injury and short circuits.
General safety
The surface of a mirror is conductive. Never touch powered components with a mirror; you
may injure yourself and/or at least cause short-circuit damage.
Always disconnect the power supply when working in the immediate vicinity of a power
supply unit or direct current converter, unless the work instructions expressly permit you to
work without shutting off the power.
5.1.3
Safety Information: Caution
Damage
Only use tools and utilities that are in awless condition. It is not permitted to use visibly damaged tools.
Protecting electrostatically sensitive devices (ESD)
To protect electrostatically sensitive devices:
Always put on the ESD wristband before touching any of the boards or modules.
Only transport PC boards in suitable protective packaging.
Always place PC boards on a grounded conducting base, and do not work on the PC
boards anywhere else.
Only use grounded soldering irons.
Laying cables
Cables should be installed so that they do not pose an accident risk (i.e. will not trip anybody
up) and cannot be damaged.
A31003-H3540-A800-1-7619, 2003-05-02
5-3
Admain5.fm
Maintenance Tasks
5.1.4
General Information
Connecting lines
All cables and lines which leave a system cabinet must be screened at least between the
connection point in the cabinet and the point at which the cable leaves the cabinet.
Use a clip and pressure screw to contact all shield fabric to the cabinet outlet. This also
applies to permanently connected service equipment.
Cables should only be connected to the specied connection points.
Location of safety equipment

When the installation or maintenance is completed, replace all safety equipment in the correct
location.
Checking tools
Check your tools regularly. Only use intact tools.
Closing the housing
Close all housing covers once work has been completed.
Module condensation
If modules are brought into the operating site from a cold environment, condensation may occur. Wait until the temperature of the installation has adjusted to the ambient temperature and
until the installation is absolutely dry before you start it up.
Fire protection and EMC requirements
To ensure compliance with the statutory re protection and EMC requirements, HiPath systems
must only be operated when closed. The housing may only be opened briey for installation
and maintenance purposes.
Flammable materials
Do not allow ammable materials to be stored near the installation or in the installation
room.
Documents, descriptions, operating manuals or other combustible material must not be left
on top of the equipment.
5-4
A31003-H3540-A800-1-7619, 2003-05-02
Admain5.fm
Maintenance Tasks
Workplace hazards
Ensure good lighting at the workplace.
Untidiness at the workplace involves the risk of injuries.
5.1.5
What To Do in an Emergency
Actions in emergencies
In the event of accidents, remain calm and controlled.
Always switch off the power supply before you touch an accident victim.
If you are not able to switch off the power supply immediately, only touch the victim with
non-conducting materials (e. g. a wooden broom handle), and rst of all try to isolate the
victim from the power supply.
First aid
You must be familiar with rst-aid practices in the event of electricity injuries. A fundamental
knowledge of the various resuscitation methods if the victim has stopped breathing or if the
victims heart is no longer beating, as well as rst aid for treating burns, is absolutely essential in such emergencies.
If the victim is not breathing, immediately perform mouth-to-mouth or mouth-to-nose resuscitation.
If you have appropriate training, immediately perform heart massage if the victims heart is
not beating.
Calling for help

Immediately call an ambulance or the emergency doctor. Give details of the accident in the following order:
Where did the accident happen?
What happened?
How many people were injured?
What type of injuries?
Wait for questions.
A31003-H3540-A800-1-7619, 2003-05-02
5-5
Admain5.fm
Maintenance Tasks
Replacing HXG3 boards in the HiPath HG 1500
5.1.6
Reporting Accidents
Immediately report all accidents, near accidents and potential sources of danger to your
manager.
Report all electrical shocks, no matter how small.
5.1.7
Disposal
HiPath HG 1500 is an electrical device containing environmentally damaging, non-biodegradable substances. For this reason, it cannot be disposed of with general ofce refuse.
HiPath HG 1500 systems must be properly disposed of. The relevant laws and regulations
must be observed. For further information on this topic, please consult your local Siemens representative.
5.2
Only Siemens service technicians who are authorized to work on HiPath devices may install
and maintain the system.
Danger
Before you start any work on the hardware, ensure that the board is powered off (i.e.
that it has been removed from that slot).
Warning
Protection for electrostatically sensitive devices.
Wear a suitably grounded antistatic wristband before commencing work. Attach the
alligator clip at the end of the electrostatic wristband to a grounded object.
5.2.1
Preparing the System
1.
If necessary, use the Maintenance function Conguration > Load from Gateway to save
the conguration of the board to be replaced (see Section 5.5.4, Saving Conguration
Data on a Server or PC).
2.
Perform a controlled shutdown of the system.
3.
Disconnect the system from the power supply.
4.
Check that there is no voltage.
5-6
A31003-H3540-A800-1-7619, 2003-05-02
Admain5.fm
5.2.2
Maintenance Tasks
Preparing Boards for Installation

Warning
1.
Put on an antistatic wristband.
2.
Unpack the new HXG3 board and all extension modules.
3.
Place the extension modules (if any) on the HGA interfaces. Apply the shielding to HXGS3
and HXGR3.
5.2.3
Warning
The module and the slot connection may be damaged if a module is pushed too hard
into a slot.
Do not force the extension module into the slot.
Preparing HiPath 3000

Caution
HXGR3 and HXGS3 boards are not hot-pluggable.
Proceed as follows to prepare the device:

1.
Open the system as specied in the description accompanying the device.
2.
Carefully remove the board you want to replace from the slot.
5.2.4
Installation Procedure
Insert the board in the unassigned slot as described below.
Caution
Warning
The board and the slot connection may be damaged if a board is pushed too hard
into a slot.
Do not force the board into the slot.
A31003-H3540-A800-1-7619, 2003-05-02
5-7
Admain5.fm
Maintenance Tasks
Expanding HiPath HG 1500 with HXG3 boards
1.
Ensure that HiPath 3000 is disconnected from all network power supply units. Make sure
that you are wearing an antistatic wristband which is attached to a suitable grounded object.
2.
Hold the board with the cable connector pointing towards the slot or backplane.
3.
Carefully insert the board along the card slot guide into the slot or backplane until it is rmly
engaged.
The front panel or dummy panel should make contact with the front panel of HiPath 3000.
4.
Hand-tighten the screws on both sides of the board.
5.
Close HiPath 3000 (if necessary) and turn the power back on. Restart the board (see also
Section 5.5.1, Rebooting).
6.
If necessary, use the Maintenance function Conguration > Load to Gateway to load the
saved conguration data to the new board (see Section 5.5.3, Loading Conguration Data
from Server or PC).
7.
Dispose of the old board (see also Section 5.1.7, Disposal).
5.3
Danger
that it has been removed from the slot).
Warning
Protection for electrostatically sensitive devices (ESD).
Wear a protective wristband before commencing work on modules. Attach the alligator clip at the end of the electrostatic wristband to a grounded object or the device
chassis.
5.3.1
1.
2.
3.
5-8
A31003-H3540-A800-1-7619, 2003-05-02
Admain5.fm
5.3.2
Maintenance Tasks
Preparing Boards for Installation

Warning
1.
2.
Unpack the new HXG3 board and all extension modules.
3.
Place the extension module (s) (if available) on the HGA interfaces. Apply the shielding to
HXGS3 and HXGR.
5.3.3
Warning
The board and the slot connection may be damaged if a module is pushed too hard
into a slot.
Do not force the extension module into the slot.
Preparing HiPath 3000
Proceed as follows to prepare the device:

1.
2.
Check that the required slot is free and that the maximum number of HXG3 boards permitted has not already been reached (see also Chapter 4 of the Installation manual for
HiPath HG 1500 boards).
5.3.4
Warning
The board and the slot connection may be damaged if a board is pushed too hard
into a slot.
Caution
A31003-H3540-A800-1-7619, 2003-05-02
5-9
Admain5.fm
Maintenance Tasks
Inserting an Extension Module in an HXG3 Board
1.
2.
3.
engaged.
The front panel or dummy panel should make contact with the front panel of the HiPath
3000.
4.
5.
6.
Congure the new board (see the Conguration manual).
5.4
Danger
that it has been removed from the slot).
Warning
Protection for electrostatically sensitive devices (ESD).
Wear a protective wristband before commencing work on modules. Attach the alligator clip at the end of the electrostatic wristband to a grounded object or the device
chassis.
5.4.1
1.
2.
3.
5-10
A31003-H3540-A800-1-7619, 2003-05-02
Admain5.fm
5.4.2
Maintenance Tasks
Removing HXG3 Boards
Caution
Warning
Remove the HXG3 board that will have a PEM or PMD module replaced or added:
1.
1.
2.
Carefully remove the HXG3 board from the slot.
5.4.3
Exchanging or Inserting Extension Modules
1.
Unpack the new extension module.
2.
Remove the shielding (only for HXGS3 and HXGR3).
3.
If exchanging modules, carefully remove the old extension module from the HGA slot.
4.
Place the extension module(s) on the HGA interface(s).
5.
Replace the shielding (only for HXGS3 and HXGR3).
5.4.4
Warning
The module and the slot connection may be damaged if a module is pushed too hard
into a slot.
Do not force the extension module into the slot!
Caution
WARNING: The board and the slot connection may be damaged if a board is pushed
too hard into a slot.
A31003-H3540-A800-1-7619, 2003-05-02
5-11
Admain5.fm
Maintenance Tasks
Software Maintenance
1.
2.
3.
engaged.
The front panel or dummy panel should make contact with the front panel of HiPath 3000.
4.
5.
5.5
The HiPath HG 1500 needs only limited software maintenance. In general, it is limited to:
Restarting the system
Restoring system and conguration les
Refreshing system software
>
System software and conguration les should be loaded during low trafc times.
Otherwise, faults in gateway operation and in the maintenance activity itself could result.
>
Save the current conguration data (see Section 5.5.4, Saving Conguration Data
on a Server or PC) before loading a new software image or other conguration data.
If for some reason the newly loaded conguration data or the new software image is
not usable, you can at least fall back on the last conguration status.
5.5.1
Rebooting
The HiPath HG 1500 V3.0 board is rebooted in the same way as other boards in HiPath 3000.
The boot procedure can be interrupted by pressing any key on the keyboard of a terminal connected to the V.24 interface.
Initiating Reboot
To reboot an already operating HiPath HG 1500:
Key combination
Press CTRL- X simultaneously on the terminals keyboard.
5-12
A31003-H3540-A800-1-7619, 2003-05-02
Admain5.fm
Maintenance Tasks
Command line
Enter the Reset command on a terminal connected to the V.24 interface or alternatively
on a Telnet terminal.
In both cases, the gateway will reboot with the current conguration.
Boot sequence
The rmware performs the following tasks during startup:
1.
It initializes the hardware components of the board.
2.
It tests the hardware components (module test). The Boot ROM displays the results of the
integrated self-test as well as information on the boards and the current start parameter
(Boot Line). A three-second countdown is subsequently performed and displayed on the
screen. The boot procedure can be interrupted during the countdown by pressing any key
on the terminal connected to the V.24 interface.
3.
Creates the le system in the ash memory when the countdown is nished.
4.
Activates the Command Line Interface (CLI) handler.
5.
Loads the software image from the ash memory into RAM and starts it.
6.
Starting the software image activates all hardware components, initializes the kernel, congures the TCP/IP stack (using the IP address given in the start parameters) and links the
driver to the kernel.
7.
The Boot ROM starts a checking process to observe the gateway. If this process determines that the gateway is hanging, it will reboot automatically with the current conguration.
LED indicators when booting

LED status
LED Fail ashes
red
Meaning
Flashing LED indicates that software is being reloaded.
LED Fail is off, LED The boot procedure is nished and the board is operational.
Run is lit
Table 5-1
Interrupting the boot procedure

The message Press any key to stop auto-boot appears on the terminal during the boot procedure. The boot procedure can be interrupted within three seconds by pressing any key on a
keyboard connected to the V.24 interface.
A31003-H3540-A800-1-7619, 2003-05-02
5-13
Admain5.fm
Maintenance Tasks
If the boot procedure is interrupted in this way, the device switches to a special mode. To repeat
the standard boot procedure, press <CTRL>-X.
5.5.2
Changing the Software Image
The software image in ash memory can be changed via the WBM or the command line.
>
Using WBM maintenance functionality:

1.
2.
3.
4.
Click Software Image in the maintenance menu.
5.
Right click Load to Gateway and select Load via HTTP or Load via TFTP from the popup menu.
The following dialog appears when Load via HTTP is selected:
5-14
A31003-H3540-A800-1-7619, 2003-05-02
Admain5.fm
6.
Maintenance Tasks
Load via TFTP:

Select the TFTP server and enter the name of the software image on the server in the relevant eld. The gateway automatically enters the IP addresses last entered for the default
and alternative TFTP servers. You only need to edit these if the addresses have been
changed.
Load via HTTP:
Enter the name of the le on the PC into the input eld. If you do not know the exact le
name, you can nd the le using the Browse button. Clicking the Browse button opens
a window showing the les on the PC.
7.
Click Load to load the le with the new software image onto the gateway. You will be
asked to wait for the loading procedure to nish.
A dialog appears in which you can chose whether the software should be activated immediately or later:
8.
Click Activate Now to activate the software image immediately. The gateway performs a
cold start to load the new software in the RAM.
Click Dont Activate to activate the software image later. You can then activate the loaded
software image at a later time (see Section 4.9.2, Automatic Actions).
Click Schedule Activation ... to choose when the software image should be activated.
After clicking on Schedule Activation ... the following appears in the contents area:
A31003-H3540-A800-1-7619, 2003-05-02
5-15
Admain5.fm
Maintenance Tasks
is selected.
Click Use Calendar to select the date from a calendar.

The display is extended to include the following eld:
5-16
A31003-H3540-A800-1-7619, 2003-05-02
Admain5.fm
>
9.
Maintenance Tasks
Click Refresh to update the display.
10. Click the save icon in the control area.

Using the command line:
1.
Enter the TFTP server:

set tftp <ip address [:port]
or
set alternate tftp <ip address [:port]
2.
Copy the conguration les to the gateway using the following command:
download software <remote filename>
3.
Activate the newly loaded software as follows:

activate software
Example
set tftp 139.1.1.30
download software x_hg15_002.001
activate software
When you load a software image to the board and use the command line to reboot, a self-extracting le will rst be executed. You need to decide if you want to reinstall the entire software
(after deletion of ash memory) or just update it (replacement of existing les, but no change
to conguration)
>
Updating is possible during a Telnet session but a complete reinstallation is not.
A full reinstallation results in an empty database and only a software image on the gateway. All
previous conguration data is deleted.
An update replaces the old software version with a new one.
An additional restart is automatically begun that utilizes the new software image and removes
the self-extracting le from the ash memory.
A31003-H3540-A800-1-7619, 2003-05-02
5-17
Admain5.fm
Maintenance Tasks
If this second reboot is not successful, the board will reboot again automatically with the old
software image. In this case, no backup copy of the code in the gateway will be available.
5.5.3
Loading Conguration Data from Server or PC
The conguration le in ash memory can be changed via the WBM or the command line.
>
Always save the current conguration data (see Section 5.5.4, Saving Conguration
Data on a Server or PC) before loading a new software image or other conguration
data. If for some reason the newly loaded conguration data or the new software image is not usable, you can at least fall back on the last conguration status.
>
Login passwords are saved in the conguration le. Make sure you know the passwords in the le that will overwrite the current conguration. Otherwise, you will no
longer have access to the system.
Using WBM maintenance functionality

1.
2.
3.
4.
Click Conguration at the left of the Maintenance menu.
5.
Right click Load to Gateway and select Load via HTTP or Load via TFTP from the popup menu.
The following dialog appears when Load via HTTP is selected:
5-18
A31003-H3540-A800-1-7619, 2003-05-02
Admain5.fm
6.
Maintenance Tasks
Load via TFTP:

Select the TFTP server and enter the name of the conguration le on the server in the
relevant eld. The gateway automatically enters the IP addresses last entered for the default and alternative TFTP servers. You only need to edit these if the addresses have been
changed.
Load via HTTP:
Enter the name of the le on the PC into the input eld. If you do not know the exact le
name, you can nd the le using the Browse button. Clicking the Browse button opens
a window showing the les on the PC.
7.
Click Load.
8.
Click OK. The conguration le will be copied from the given location to the ash memory.
A31003-H3540-A800-1-7619, 2003-05-02
5-19
Admain5.fm
Maintenance Tasks
Select the tables to be activated. Choose Select all tables to select all tables for activation.
Choose Deselect all tables to deselect each table. You can select or deselect each table
individually.
9.
Click Activate Now to activate the newly loaded conguration data. The gateway performs
a cold start.
>
5-20
If you want to activate the loaded conguration le later, click Dont Activate. To activate the conguration data later, click Job Administration in the maintenance
menu and activate the job.
A31003-H3540-A800-1-7619, 2003-05-02
Admain5.fm
Maintenance Tasks
Using the command line
>
1.
The command line can only be used for loading les from a TFTP server, not from a
PC.

or
2.
Copy the conguration les from the server using the following command:
download configuration <remote filename>
3.
Activate the new conguration les as follows:

activate configuration
Example
set tftp 139.1.1.30
download configuration lucia161_34_001
5.5.4
Saving Conguration Data on a Server or PC
Conguration data can be copied from the ash memory to a TFTP server or a PC using WBM
or the command line. It can then be opened, edited and printed using any text editor.
Using WBM maintenance functionality
1.
2.
3.
4.
Click Conguration at the left of the Maintenance menu.
5.
Right click Load from Gateway and select Load via HTTP or Load via TFTP from the
pop-up menu.
A31003-H3540-A800-1-7619, 2003-05-02
5-21
Admain5.fm
Maintenance Tasks
The following dialog appears when Load via TFTP is selected. When Load via HTTP is
selected, this dialog displays only the table selection area.
6.
When loading via TFTP:

Select the TFTP server and enter the name of the conguration le on the server in the
relevant eld. The gateway automatically enters the IP addresses last entered for the default and alternative TFTP servers. You only need to edit these if the addresses have been
changed.
Select the tables to be saved to the conguration le. Choose Select all tables to select
all tables to be saved. Choose Deselect all tables to deselect all tables. You can select or
deselect each table individually.
7.
Click Load.
5-22
A31003-H3540-A800-1-7619, 2003-05-02
Admain5.fm
Maintenance Tasks
Multigateway Administration
When loading via HTTP, a dialog for entering the directory and le name will appear. Enter
the necessary information.
The conguration le will be copied from the ash memory to the given location.
Using the command line
>
1.
The command line can only be used for saving les to a TFTP server, not to a PC.

or
2.
Copy the conguration les to the server using the following command:
upload configuration <remote filename>
Example
set tftp 139.1.1.30
upload configuration lucia161_34_001
5.6
The Web-based Management allows you to administer multiple gateways.

The following functions are available:
List of Gateways
In the pop-up menu, you can choose to display all entered gateways, all selected gateways
or all unselected gateways. You can also open a list of all entered gateways with additional
information. Gateways can be added to or removed from the lists.
List of Conguration Tables

You can open a list of all conguration tables. In this list you can determine which tables
from the current conguration should be distributed to the selected gateways. You can select individual tables or all tables.
A31003-H3540-A800-1-7619, 2003-05-02
5-23
Admain5.fm
Maintenance Tasks
Distribution
This function distributes the chosen conguration tables to selected gateways.

Job Administration
This function opens a list that displays the processing status of conguration distribution.
>
5.6.1
The list of gateways to which conguration data should be distributed should not be
too long. Otherwise, it will take quite a while for the WBM to be available again for
other functions.
Displaying the List of Gateways
1.
2.
3.
Click Multigateway Admin at the left of the Maintenance menu.
4.
Right click List of Gateways and select a display option from the pop-up menu.
Depending on your selection, the following tables will be opened:
Display All Gateways
Display Selected Gateways
Display Unselected Gateways
5-24
A31003-H3540-A800-1-7619, 2003-05-02
Admain5.fm
Maintenance Tasks
Display All Gateways with Status Information
The tables can be sorted by the criteria Gateway Name and Gateway IP Address. An
arrow after a column name (e.g Gateway Name) indicates by which criteria the entries
were sorted. If you wish to sort the table by another column, click the respective column
name.
5.6.2
Adding a New Gateway to a List
1.
2.
3.
4.
5.
Right click List of Gateways and select Add Gateway from the pop-up menu.
Enter the gateway name and IP address in the input elds. Indicate whether or not this
gateway should be selected for distribution of conguration data.
6.
Click Apply. The conguration is modied and the dialog title changes from add to edit.
7.
A31003-H3540-A800-1-7619, 2003-05-02
5-25
Admain5.fm
Maintenance Tasks
8.
5.6.3
Removing All Gateways from Lists
1.
2.
3.
4.
5.
Right click List of Gateways and select Delete All Gateways from the pop-up menu.
6.
Click Delete to remove all gateways from the list.
7.
5.6.4
Selecting and Deselecting Gateways for Distribution
A folder icon appears as soon as a gateway has been added to a list. This folder contains all
added gateways.
A dot in front of the gateway shows whether it has been selected for distribution or not:
Icon
Status
This gateway is not selected for distribution of conguration tables (color: red).
This gateway is selected for distribution of conguration tables (color: green).
Select or deselect gateways for distribution as follows:

1.
2.
3.
5-26
A31003-H3540-A800-1-7619, 2003-05-02
Admain5.fm
Maintenance Tasks
4.
5.
Double click the List of Gateways folder.
6.
Right click the required gateway and choose Deselect Gateway for Distribution or Select
Gateway for Distribution from the pop-up menu.
The dot in front of the gateway name in the list changes color.
7.
5.6.5
Displaying Gateway Properties
Display the properties of a gateway in the list as follows:

1.
2.
3.
4.
5.
Right click the required gateway and choose Display Gateway Properties from the popup menu.
5.6.6
Displaying Gateway Status Information
Display the properties, including the dynamically gained status info, of a gateway in the list as
follows:
1.
2.
3.
4.
5.
Right click the required gateway and choose Display Gateway Status Information from the
pop-up menu.
A31003-H3540-A800-1-7619, 2003-05-02
5-27
Admain5.fm
Maintenance Tasks
5.6.7
Editing Gateway Properties
1.
2.
3.
4.
5.
Double click List of Gateways.
6.
Right click the gateway you want to edit and select Edit Gateway Properties from the popup menu.
Enter the gateway name and IP address in the input elds. Indicate whether or not this
gateway should be selected for distribution of conguration data.
7.
8.
5-28
A31003-H3540-A800-1-7619, 2003-05-02
Admain5.fm
5.6.8
Maintenance Tasks
Deleting a Gateway from a List
Delete a gateway from the administration list as follows:

1.
2.
3.
4.
5.
Double click List of Gateways.
6.
Right click the required gateway and select Delete Gateway from the pop-up menu.
7.
Click Delete to remove the displayed gateway from the list.
8.
5.6.9
Editing the List of Conguration Tables
1.
2.
3.
4.
5.
Right click List of Conguration Tables.
6.
Select Display List of Conguration Tables from the pop-up menu.
A31003-H3540-A800-1-7619, 2003-05-02
5-29
Admain5.fm
Maintenance Tasks
Select the conguration tables which should be distributed to the selected gateways.
Choose Select all tables to select all tables for distribution. Choose Deselect all tables
to deselect all tables. You can select or deselect each table individually.
7.
Click Apply. The conguration tables are ready to be distributed (for information on distribution, see Section 5.6.10, Distributing Conguration Tables).
8.
5-30
A31003-H3540-A800-1-7619, 2003-05-02
Admain5.fm
5.6.10
Maintenance Tasks
Distributing Conguration Tables
>
Before distributing, you need to select which conguration tables should be distributed (see Section 5.6.9, Editing the List of Conguration Tables).
>
1.
2.
3.
4.
5.
Right click Distribution and select Distribute Conguration from the pop-up menu.
6.
7.
Click Distribute to distribute the conguration tables or Dont Distribute if the tables
should not be distributed.
5.6.11
Checking the Processing Status
1.
2.
3.
4.
5.
Right click Job Administration and select Display List of Jobs from the pop-up menu.
A31003-H3540-A800-1-7619, 2003-05-02
5-31
Admain5.fm
Maintenance Tasks
Administration Monitoring
The status of the jobs that are already processed and those that are not yet processed is
displayed.
6.
Click Abort and Clear Job to abort a job or to delete it from the list. Click Clear All Jobs
to abort all jobs or to delete them from the list.
>
5.7
All changes made by administrators are saved in a log le in the gateway. This log le will be in
English or German, depending on the setting. The log le can be loaded to a TFTP server or a
connected PC.
5.7.1
Administration Log File Language
Displaying Settings
1.
2.
3.
Click Admin Log at the left of the Maintenance menu.
4.
Right click Conguration and select Display Conguration from the pop-up menu.
The following dialog shows the current settings:
5-32
A31003-H3540-A800-1-7619, 2003-05-02
Admain5.fm
Maintenance Tasks
Changing Settings
1.
2.
3.
4.
5.
Right click Conguration and select Edit Conguration from the pop-up menu.
Choose one of the two languages available.

6.
7.
5.7.2
Loading the Administration Log File to a Server or PC
You can load log les saved in the gateway to a TFTP server or connected PC and open them
there.
1.
2.
3.
4.
5.
Right click Admin Log Data and select Load via HTTP or Load via TFTP from the popup menu.
A31003-H3540-A800-1-7619, 2003-05-02
5-33
Admain5.fm
Maintenance Tasks
Select the TFTP server and enter the name of the log le on the server in the Remote Filename eld. The gateway automatically enters the IP addresses last entered for the default
and alternative TFTP servers. You only need to edit these if the addresses have been
changed. Click Load.
6.
7.
Click OK.
location.
5.7.3
Deleting Administration Log Files from the Gateway
Delete administration log les from the gateway as follows:

1.
2.
3.
4.
5.
Right click Admin Log Data and select Clear Log File from the pop-up menu.
5-34
A31003-H3540-A800-1-7619, 2003-05-02
Admain5.fm
Maintenance Tasks
Job Monitoring
6.
Click Clear Log to remove the administration log le from the gateway.
7.
5.8
Job Monitoring
Software conguration jobs initiated by the administrator can be displayed in a list of jobs
1.
2.
3.
4.
Click Joblist at the left of the Maintenance menu.

The following dialog is an example of a joblist (loading a software image):
The status of the jobs that are already processed and those that are not yet processed is
displayed.
5.
Click Abort and Clear Job to abort a job or to delete it from the list. Click Clear All Jobs
to abort all jobs or to delete them from the list.
6.
Click Activate Software to activate the downloaded software immediately. Click Schedule
Activation ... to activate the downloaded software at a later time.
After you click Activate Software the following appears in the contents area:
A31003-H3540-A800-1-7619, 2003-05-02
5-35
Admain5.fm
Maintenance Tasks
Job Monitoring
Click OK to activate the software image or click Cancel if you do not wish to activate the
software image.
After you click Schedule Activation... the following dialog appears in the contents area:
is selected.
Click Use Calendar to select the date from a calendar. The display is extended to include
the following eld:
5-36
A31003-H3540-A800-1-7619, 2003-05-02
Admain5.fm
Maintenance Tasks
Job Monitoring
>
7.
8.
A31003-H3540-A800-1-7619, 2003-05-02
5-37
Admain5.fm
Maintenance Tasks
Job Monitoring
5-38
A31003-H3540-A800-1-7619, 2003-05-02
Admain6.fm
Error Correction
Errors During Installation or Starting the System
Error Correction
The following information could be helpful in nding the causes and solutions for problems arising with operational performance of the HiPath HG 1500.
This chapter is divided into the following sections:

Describes problems during installation and connection setup as well as problems due to
incorrect or incomplete conguration.
Errors during System Changes

Describes problems that can arise when downloading conguration data or exchanging the
software image.
Error Detection during Operation

Describes the meanings of messages, alarms (traps) and warnings that can arise during
operation and gives information about troubleshooting.
Problems with the WBM

Explains how to correct specic problems with Web-based Management.
Abnormal Board Behavior

Explains reasons for specic board behaviors and describes steps to correct them.
You must be familiar with the system, its environment and the software image to undertake
diagnosis and problem correction.
When correcting problems, only try one solution at a time. After each attempt to solve the problem, you should check if the problem still exists. This strict sequential processing prevents making the problem worse.
6.1
The HiPath HG 1500 is usually operational when switched on. If not, check the following:
Is the TFTP server set up correctly?

Set up the server as described in the conguration manual.
Was the initial conguration completed? Has all necessary data been entered?
Check all data necessary for initial conguration. We strongly recommend using the
Initial Setup wizard for this.
Has the system conguration been changed?
A31003-H3540-A800-1-7619, 2003-05-02
6-1
Admain6.fm
Error Correction
Make sure that the conguration changes were fully completed, the new conguration
was saved in the ash memory and the board was successfully restarted.
Is the IP address of the gateway correct?

Check the IP address and verify by sending a ping.
Has the application software image been loaded?

Check that the ash memory has the correct software image for the board. The conguration data must be saved in the ash memory.
Did all LEDs show expected behavior when starting?
Error messages when switching on

When switching on the system, messages regarding the boot procedure are displayed on the
console. Error messages appear when there are problems.
Message
PersService Init Failed
Table 6-1
6.2
Recommended action
If this message appears after Loading Cong Table is
shown, the system does not have a valid conguration
le.
Reinstall the software image using the download
software command. Then enter activate software in the command line (CLI).
Errors when switching on
Errors can arise when exchanging the software image or when downloading conguration data.
6.2.1
Software Image Exchange Fails
The following errors may occur when updating the software image:
The download software command is not executed successfully.
An administrator initiates a reboot during a download.
A system error or power loss initiates a reboot.
An event initiates a reboot.
The self-extracting le does not open properly.
A reboot is initiated while the self-extracting le is opening.
6-2
A31003-H3540-A800-1-7619, 2003-05-02
Admain6.fm
Error Correction
Error correction
The following actions are recommended for troubleshooting:
Error
download software failed
Action
Execute download software again
Reboot caused by administrator, error, power Execute download software again

loss or event
The self-extracting file does not open properly Execute download software again and then
activate software
Reboot initiated when self-extracting file is
opening
Table 6-2
6.2.2
Execute download software again;

if the self-extracting le seems to be defective,
execute download software again
Error correction: updating the software image
Downloading Conguration Data Fails
The following errors may occur when downloading conguration data:
The download conguration command is not executed successfully.
A reboot is initiated during the download of the conguration le.
A reboot is initiated while the save conguration command is being executed.
Error correction
The following actions are recommended for troubleshooting:
Error
Action
download conguration fails
Execute download conguration again
Reboot during download
Reboot during save conguration
Table 6-3
Error correction: downloading the conguration data
A31003-H3540-A800-1-7619, 2003-05-02
6-3
Admain6.fm
Error Correction
6.3
There are several ways to recognize and trace errors in the board:
Traps
indicate irregular states, critical errors or important system information.
Traces
log the execution of a software component.
Events
report system problems or system information.
Traces and events are written to their own event log les (see Section 6.3.4, Event Log Files).
6.3.1
Traps
When board problems occur, traps are generated to inform the administrator of errors. There
are two types of traps:
System traps
Performance traps
WBM displays traps dynamically. The list of traps is refreshed every 30 seconds. You can also
manually refresh the display.
System traps
These traps:
indicate system errors and require the administrator to take immediate countermeasures,
or they signal important system information.

Trap
Board started successfully
Recommended action
Information only, no action required
Reboot initiated by administrator, garbage col- The reboot will be executed,

lection, VxWorks, H.323 or H.323 Stack
no action required
Adapter (HSA)
Memory problems
Reboot will be executed automatically,
(memory full, memory allocation failed, mem- no action required
ory is inconsistent)
Table 6-4
6-4
System traps
A31003-H3540-A800-1-7619, 2003-05-02
Admain6.fm
Error Correction
Trap
Recommended action
Internal software problem

(Check failed, exit event, problem with conguring pool size, session setup)
Reboot will be executed automatically,

no action required
IP connection error
Check the network plug and cable
Flash memory capacity has been reached
Remove any unnecessary les from ash

memory
IP network stack resources are exhausted
Check the IP conguration of the gateway and

routers
SCN connection error
Information only, no action required
Table 6-4
System traps
Performance traps
These traps indicate performance problems but require no countermeasures. They only provide information.
Trap
Recommended action
System memory is full
None
DMA memory is full
None
Table 6-5
6.3.2
Performance traps
Traces
A trace logs the execution of a software component. A technician can use these process
records to nd the cause of an error.
Trace results can be:
displayed on a console that is connected to a V.24 interface

(console trace) and/or,
saved in a log le and/or
saved on a PC via a LAN connection.
A31003-H3540-A800-1-7619, 2003-05-02
6-5
Admain6.fm
Error Correction
The following trace functions are available:

Trace function
Description
Trace Conguration
Displays the current trace function setting and enables trace functions to be turned on and off.
Trace Log
Loads trace results as a log le from the board to a destination computer via TFTP or HTTP and enables trace data to be deleted from
the board.
H.323 Stack Trace
Displays the current debug switch settings for the H.323 Stack Trace.
Each debug switch can be separately enabled or disabled.
Trace Proles
Groups the monitoring of individual components into customized

proles. Proles can be created, changed, started or deleted.
Trace Components
Monitoring can be started or enabled and disabled for each component individually. In addition, the data to be entered for each component can be specied.
Service Traces
Trace functions for Siemens technicians only; not yet activated.
Probes
For analyzing board problems with WindView software
Table 6-6
Trace functions
The possible settings are described in Section 4.6, Traces (Procedure Recording).
6.3.3
Events
Events notify you of system faults. Check the network conguration and/or gateway conguration to clear up any abnormalities.
Depending on the setting and the class of problem, events can generate an SNMP trap, send
a message to the HiPath system, send an E-mail, initiate a trace observation and reboot the
board.
Events are always written to a log le (see Section 6.3.4, Event Log Files).
6.3.4
Event Log Files
All events are written to a log le with a limited size. When the maximum le size is exceeded,
new messages overwrite the oldest entries.
The event log le name is:
evtlog.txt
It is saved in the HiPath HG 1500 ash memory in the following directory:
\tffs\evtlog
6-6
A31003-H3540-A800-1-7619, 2003-05-02
Admain6.fm
Error Correction
The event log le can be transferred to a PC. Use the WBM maintenance function Events >
Events Log > Load via HTTP or Load via TFTP.
Event messages can also be forwarded to the V.24 or telnet terminal. For this, the trace component EVTLOG must be activated with trace level 6 (Explorer function Traces > Service Traces > Trace Component EVTLOG).
The following example shows a typical event entry:
EventLogEntry from IFTABLE (tH323-CLP "03/17/2000 08:13:56.828020"
ciftable01.cpp 433):
EventType: csevWarning
EventCode: MSG_DVMGR_INTERROR_DEVID
EventText: DeviceID(0XFFFFFFFF): ClIfTable::fCheckConsistency: Persistency
files and hw_specification inconsistent!
The meanings of these entries are as follows:
Entry in Log File
Meaning
IFTABLE
Name of component that initiated the event
tH323-CLP
Name of task that initiated the event
03/17/2000
Date of event
08:13:56.828020
Time of event in
hh:mm:ss (seconds with six places after decimal point)
ciftable01.cpp 433
Name of source le with line number where

event occurred
csevWarning
Event class
MSG_DVMGR_INTERROR_DEVID
Internal event code
DeviceID(0XFFFFFFFF): ClIfTable::
fCheckConsistency Persistency les and
hw_specication inconsistent!
Text in event le
Table 6-7
Meanings of entries in event log les
A31003-H3540-A800-1-7619, 2003-05-02
6-7
Admain6.fm
Error Correction
6.4
The following problems can arise when using the WBM:

Behavior
After the Internet Explorer
language settings are
changed, WBM does not
support the new language.
Recommended action
Delete all les in the Windows > Temporary Internet Files directory. Exit and then restart Internet Explorer.
Access to WBM is no longer Close all browser windows and start a new WBM session.
possible
The cookie may expire if a WBM session is no longer active. In
this case, access permission is withdrawn and no further access to the WBM is possible during that session. Make sure
that all users close WBM sessions when they log off by exiting
the browser.
Full access to WBM is not
possible even after logging
off and back on
Exit the browser and start a new WBM session.

It is possible that you ended a session by logging off, but did not
exit the browser.
WBM screen is not displayed If an administrator starts another application while a WBM sescompletely
sion is being started (the control applet is loading), it is possible
that the screen will not be displayed completely. The same effect can be observed when too many activities are begun one
after another.
Wait until all information is displayed or use the relevant browser command to refresh the display. Do not start too many actions within a short time period.
The administrator cannot re- Make sure the write lockout was set in the active WBM session.
move a write lockout.
Use the browser command to refresh the screen to make certain that the display is correct.
The administrator cannot set Make sure that the WBM session was correctly closed with the
a write lockout
Logoff module.
Start a WBM session, close it with the Logoff module and exit
the browser. Then start a new WBM session.
WBM access is interrupted
(displays no data or only
default data)
Check the proxy settings for Internet Explorer. The gateway IP

address must always be entered in full and without wildcards.
Internet Explorer reports errors or indicates problems

(e.g. ActiveX controls)
In Internet Explorer, click Tools > Internet Options > Security >
Local Intranet. Click Custom Level. Under Initialize & script
ActiveX controls not marked as safe and Run ActiveX controls
& plug-ins select Prompt or Enable.
Table 6-8
6-8

A31003-H3540-A800-1-7619, 2003-05-02
Admain6.fm
Error Correction
Behavior
Other problems with the
WBM
Recommended action
Make sure the browser you are using is compatible with the
WBM. Further details can be found in Section 2.2.
The maximum number of us- If you call up HXG3 boards via your browser favorites, the URL
ers who can work simultamust include the Port 8085 used (e.g. <IP address>:8085).
neously is reached quickly
The URL should never lead to the login page because repeated
logins will quickly reach the maximum number of users who
can work simultaneously and will block the system.
Access to WBM blocked due WBM access is blocked if the IP address is congured incorto incorrectly entered IP ad- rectly (e.g. mistyped). Start the board using the CLI command
dress
reset. Since the incorrectly entered IP address had not yet
been saved, WBM access is possible again.
Table 6-8
6.5
Incorrect or incomplete conguration can lead to unexpected board behavior. The following table summarizes some typical problems.
Behavior
Recommended action
WBM reactions appear to be Make sure the board IP address is entered in the DNS server.
too slow
If that is not possible, enter the board IP address in the ETC/
host tables on all administration terminals.
Problem during administration of multiple boards
If multiple HXG3 boards are administered from one PC they

must have the same revision status. Otherwise, problems may
arise during administration of the boards.
Software cannot be downloaded via the WBM
Open a HiPath HG 1500 telnet session or a V.24 terminal. Enter the command show flash and check that the les
SW_Image.001 and/or SW_Image.002 are in the directory
\tffs.
Entering show boot displays the currently active image.
Make sure that the le X_CG25_X is not there. If found, it
must be deleted from the ash memory. In this case, restart the
board and interrupt the boot procedure on the V.24 terminal.
The boot command line is now active.
Enter the command D to delete a le from the ash memory.
After deleting the le X_CG25_X, press @ to continue the
boot procedure.
Download the new software with WBM and activate it.
Table 6-9
Abnormal Gateway Behavior
A31003-H3540-A800-1-7619, 2003-05-02
6-9
Admain6.fm
Error Correction
6-10
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_A.fm
Command Line (CLI)
Command Line (CLI)
We recommend administrating HiPath HG 1500 via WBM (Web-Based Management). However, this does require that the gateway already has an IP address.
You can use the command line to enter various commands at a terminal connected directly to
HiPath HG 1500 without the need for an IP address. Commands can be used for the initial startup and basic conguration and for monitoring certain counters and statistics.
There are two access options for using CLI commands:
a terminal connected directly to the V.24 interface or a suitable terminal emulation program
(for example, HyperTerminal, Linux computer with Minicom application)
Telnet applications.
Before using a Telnet connection, Telnet clients must be congured. Telnet is always enabled
by default.
CLI commands are explained below. To provide a better overview, the commands are grouped
according to their eld of application.
Command Types
Description
General Commands
Commands for logging off, editing command lines, listing

available commands, displaying previously dened commands and for enabling and disabling the Telnet function.
Authentication
Commands for the write privilege and for conguring Telnet

clients and WBM clients.
Conguration
Commands for conguring the gateway, transferring les

and restarting.
Maintenance
Commands for diagnostics and for controlling the gateway

and interfaces.
Table A-1
Command Types
When entering a command you only need to enter the number of characters required for the
command to be clearly identied. Commands can be entered in upper and lower case.
>
The input for the <ip address> and <ip subnet mask> parameters must follow
the convention xxx.xxx.xxx.xxx, where xxx is a whole number between 0 and 255.
A31003-H3540-A800-1-7619, 2003-05-02
A-1
Admain_anhang_A.fm
Command Line (CLI)

General Commands
A.1
General Commands
A.1.1
Shell Commands
Every command entered in the command line is retained in a command protocol that can be
called up again. The following commands are available for scrolling through and reusing this
protocol:
Help
To display a list of all the commands available, enter:
help
Last command
The last command executed can be displayed again by pressing the
<Up arrow>
You can scroll through the command protocol by pressing this key and entering the following
command:
Next command
The next command in the protocol can be displayed with the
<Down arrow>
Editing a command
You can edit a command with the
<Backspace key>
This deletes the character at the left of the insertion mark.
Logging off
You must log in to start a session. No special command is required for this; authentication is
performed automatically when you enter a name and password.
A-2
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_A.fm
Command Line (CLI)

General Commands
To terminate a session, enter:

logout
A.1.2
Interrupting the Boot Procedure
The start sequence can be interrupted within three seconds after activation by pressing any key
on the terminal connected to the V.24 interface. The session starts once the start password and
root access rights are entered (Root Administrator).
After authentication, the boot command line is available. This has other commands than the
conventional command line.
A.1.3
Authentication
Write access
You must reserve write access for yourself before saving data, loading it onto the server or
downloading it from the server. To do this, you must check that no one else has already reserved write access, then reserve it and release it after the task is completed.
who has write access
get write access
release write access
Conguring Telnet clients
The following commands are available for conguring access via Telnet and for using a restricted CLI command set:
add telnet client <ip address>
delete telnet client <ip address>
show telnet clients
Conguring WBM clients
The following CLI commands are available for adding or deleting WBM clients or displaying existing WBM clients:
add wbm client <ip address>
delete wbm client <ip address>
show wbm clients
A31003-H3540-A800-1-7619, 2003-05-02
A-3
Admain_anhang_A.fm
Command Line (CLI)

Configuration
A.2
Conguration
A.2.1
Installation Commands
To perform the initial conguration you must connect a terminal to the V.24 interface of the gateway. You can enter the IP address and load the software image from a TFTP server via this
terminal.
Assigning an IP address to the gateway
You must assign a name, an IP address and a subnet mask for the Ethernet interface to the
gateway.
Once it has been entered, the gateway name will be the rst element in every command
prompt. Any changes to the IP address or subnet mask will only become effective after the
gateway is restarted.
To change this information, enter:
set hostname <hostname>
set ip address <ip address>
set ip subnet <ip subnet mask>
Assigning a default router
You must assign a default router to the gateway.
To assign a default router, enter:
set default gateway <ip address>
A.2.2
Conguration Commands
The gateway has a TFTP client for le transfer purposes. A corresponding TFTP server must
be available in the network. The software image and conguration data are downloaded directly
to the ash memory. Conguration data, trace les and event logs can be loaded from the gateway onto the server.
Specifying the primary TFTP server
Before you can load les to the gateway or on the server via TFTP, you must select a TFTP
server using the following command:
set tftp <ip address[:port]>
A-4
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_A.fm
Command Line (CLI)

Configuration
Specifying the alternative TFTP server

In addition to the primary TFTP server, you can specify an alternative TFTP server with the following command:
set alternate tftp <ip address[:port]>
Switching from the alternative to the primary TFTP server
If the alternative TFTP server has been active and you want to switch back to the primary TFTP
server, use the following command to change TFTP servers:
activate tftp
Switching from the primary to the alternative TFTP server
If the primary TFTP server has been active and you want to switch back to the alternative TFTP
server, use the following command to change TFTP servers:
activate alternate tftp
Downloading software images
You can download a software image from a TFTP server to the gateway by entering:
download software <remote filename>
Enter the following command to conclude the software image switchover:
activate software
During this restart you will be asked if the gateway should be completely reinstalled (deleting
the ash memory and reinitializing it) or if an update should be performed (replacing the existing les without modifying the conguration).
>
This choice is only available if the software was downloaded from a V.24 terminal.
A complete reinstallation results in an empty database with only one software image in the
gateway. All previous conguration data is lost.
If an update is performed, the currently active software image is replaced by the new image
which is then used at the next reboot.
Loading a conguration onto the server
The following command copies the current conguration le to the TFTP server:
upload configuration <remote filename>
A31003-H3540-A800-1-7619, 2003-05-02
A-5
Admain_anhang_A.fm
Command Line (CLI)

Configuration
Downloading, activating and saving a conguration from the server

This command copies a conguration le from the TFTP server to the gateways ash memory:
download configuration <remote filename>
Execute the following command to activate the new conguration le:
The downloaded conguration le replaces the conguration le in the ash memory. Once the
command activate configuration has been executed, the new conguration is active.
Execute the following command to save the new conguration after a successful restart:
save configuration
This transfers the new conguration from the RAM to the ash le system.
TFTP
In addition to the special commands described above, you can also access the TFTP server
directly. This is particularly useful for reading trace and event logs. Binary data transfers are
supported.
>
For security reasons, HiPath HG 1500 can only operate as a TFTP client. The TFTP
server must be set up on the partner device.
The put tftp command transfers les from the gateway to the server; get TFTP transfers
les from the server to the gateway:
get tftp <remote filename> [<local filename>]
put tftp <remote filename> [<local filename>]
To load trace or event logs on the server, enter:
upload trclog <remote filename>
upload evtlog <remote filename>
The protocols are also available on the server as:
/trace/trace.txt
/trace/trace.bak
/evtlog/evtlog.txt
/evtlog/evtlog.bak
A-6
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_A.fm
A.3
Command Line (CLI)

Maintenance
Maintenance
The maintenance commands enable you to determine the current administrative status of the
gateway, to use tools for diagnosing and controlling the gateway and to restart the gateway.
A.3.1
Inspection
Gateway conguration
These commands display information on the various aspects of the gateway conguration and
the gateway time:
show versions
show uptime
show time
Gateway start conguration
This command displays information on the current start conguration of the gateway:
show boot
Gateway status
The following commands display information on the use of the RAM and ash memory:
show memory
show flash
Viewing APR cache
To view the current contents of the APR cache, enter:
show arp cache
Interface statuses
The following commands display information on status of the interfaces:
show if counters
show if states
A31003-H3540-A800-1-7619, 2003-05-02
A-7
Admain_anhang_A.fm
Command Line (CLI)

Maintenance
Displaying the IP address, name or subnet mask of the gateway

To view the gateway name, IP address or subnet mask, enter:
show hostname
show ip address
show ip subnet
Information on the active TFTP server addresses
To display the IP addresses of the primary and alternative TFTP server and to check which
server is currently active, enter:
show tftp
Default router information
A default router must be assigned to the gateway.
To view the IP address of the current default router:
show default gateway
Viewing static route entries
To view the entries for static routes, enter:
show route
Ping
This command sends an ICMP ECHO_REQUEST packet to another device in the network.
ping <ip address>
A.3.2
Resetting the Gateway
There are various commands available for resetting the gateway:

Command
Description
reset
Restarts the gateway with the current conguration.
reset factory
Resets the conguration data to the factory default and

starts the gateway with this conguration.
Table A-2
A-8
Reset commands
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_A.fm
Command Line (CLI)

List of All CLI Commands
>
Administrators must ensure that they arrange a gateway restart to suit other users
(if any).
Normal reset
To restart the gateway with the current conguration data, enter:
reset
Resetting using the preset conguration
To restart the gateway with the factory default conguration, enter:
reset factory
A.4
The following table contains all the CLI commands. In addition to a brief description, the table
also indicates whether a write privilege is required for using the command.
Command
Description
Write
Access
activate configuration Activates a newly loaded conguration le.
No
activate software
Loads the contents of a self-extracting le.
Yes
activate alternate
tftp
Switches from the primary to the alternative TFTP

server.
Yes
activate tftp
Switches from the alternative to the primary TFTP

server.
Yes
add telnet client
Adds a Telnet client.
Yes
add wbm client
Adds a WBM client.
Yes
delete telnet client
Deletes a Telnet client.
Yes
delete wbm client
Deletes a WBM client.
Yes
download configuration Copies a conguration le from the TFTP server to

the ash le system.
Yes
download software
Loads a software image from the TFTP server.
Yes
get tftp
Transfers les from the TFTP server to the gateway.
Yes
get write access
Reserves write access.
No
Table A-3
Overview of CLI Commands
A31003-H3540-A800-1-7619, 2003-05-02
A-9
Admain_anhang_A.fm
Command Line (CLI)

Command
Description
Write
Access
help
Displays the list of all available commands.
No
logout
Terminates a session.
No
ping
Dispatches a data packet.
No
put tftp
Transfers les from the gateway to the TFTP server.
Yes
release write access
Releases write access.
Yes
reset
Restarts the gateway with the current conguration.
No
reset factory
Resets the conguration data to the factory default

and starts the gateway.
Yes
save configuration
Saves a conguration after the restart.
Yes
set alternate tftp
Selects the alternative TFTP server.
Yes
set default gateway
Assigns the default router.
Yes
set hostname
Denes the gateway name.
Yes
set ip address
Assigns an IP address.
Yes
set ip subnet
Assigns a subnet mask.
Yes
set tftp
Selects the primary TFTP server.
Yes
show arp cache
Displays the current contents of the ARP cache.
No
show boot
Displays the start conguration.
No
show default gateway
Displays the IP address of the default router.
No
show flash
Displays the utilization ratio of the ash memory.
No
show hostname
Displays the gateway name.
No
show if counters
Displays the interface counter.
No
show if states
Displays the interface status.
No
show ip address
Displays the IP address.
No
show ip subnet
Displays the subnet mask.
No
show memory
Displays the utilization ration of the RAM.
No
show routes
Displays the entries for static routes.
No
show telnet clients
Displays the available Telnet clients.
No
show tftp
Displays which TFTP server is active.
No
Table A-3
A-10
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_A.fm
Command Line (CLI)

Command
Description
Write
Access
show time
Displays the gateway time.
No
show uptime
Displays how long the gateway is enabled.
No
show versions
Displays the software versions available.
No
show wbm clients
Displays the existing WBM clients.
No
upload configuration
Copies the current conguration le to the TFTP

server.
Yes
upload evtlog
Loads the event log le to the TFTP server.
Yes
upload trclog
Loads the trace log le to the TFTP server.
Yes
who has write access
Displays who has write access.
No
Table A-3
A31003-H3540-A800-1-7619, 2003-05-02
A-11
Admain_anhang_A.fm
Command Line (CLI)

A-12
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_B.fm
Boot Command Line (Boot CLI)
Rebooting
The boot command line has a command set with which you can control and inuence the startup of HiPath HG 1500.
B.1
Rebooting
HiPath HG 1500 can be rebooted via the standard Reset command line or via the WBM Reset
button. The startup procedure can be interrupted by pressing any key on the keyboard of a terminal connected to the V.24 interface.
B.1.1
Initiating Startup
To reboot an already operating HiPath HG 1500:
Key combination
Press <CTRL>-X at the same time.
WBM input
Click the Reset icon.
Command line
Enter the Reset command on a terminal connected to the V.24 interface or alternatively
on a Telnet terminal.
In all of these cases, the gateway will restart with the current conguration.
B.1.2
Boot Sequence
The rmware performs the following tasks during startup:

1.
It initializes the hardware components of the board.
2.
It tests the hardware components (module test). The Boot ROM displays the results of the
integrated self-test as well as information on the boards and the current start parameter
(Boot Line). A three-second countdown is subsequently performed and displayed on the
screen. The boot procedure can be interrupted during the countdown by pressing any key
on the terminal connected to the V.24 interface.
3.
Once the count down has ended, the system loads the software image from the ash memory into RAM and starts it.
A31003-H3540-A800-1-7619, 2003-05-02
B-1
Admain_anhang_B.fm

Controlling the Boot Procedure
4.
Starting the software image activates all hardware components, initializes the kernel, congures the TCP/IP stack (using the IP address given in the start parameters) and links the
driver to the kernel.
5.
The Boot ROM starts a checking process to observe the gateway. If this process determines that the gateway is hanging, it will reboot automatically with the current conguration.

LED status
Meaning
LED Fail ashes

red
Flashing LED indicates that software is being reloaded.
LED Fail is off, LED The boot procedure is nished and the board is operational.
Run is lit
Table B-1
B.1.3
Interrupting the Boot Procedure
The message Press any key to stop auto-boot appears on the terminal during the boot procedure. The boot procedure can be interrupted within three seconds by pressing any key on a
keyboard connected to the V.24 interface. The session then starts as for the root administrator
and requests a password.
You can manually control the boot procedure by specifying boot commands and changing the
start parameters. The Fail LED ashes for as long as the boot procedure is interrupted.
B.2
B.2.1
Boot Commands
The following commands are available for controlling the boot procedure:
Command
Description
Reads the TFFS start parameters (True Flash File System) from the ash
memory.
Reads the default start parameters.
Formats TFFS. You are requested to specify if Low Level formatting should
be performed (recommended if there are serious problems. Low Level formatting takes longer than standard formatting)
Table B-2
B-2
Boot Commands
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_B.fm

Command
Description
Writes the start parameters to TFFS.
Loads a software image and copies it to TFFS (per TFTP).
Loads a le and copies it to TFFS (per TFTP).
Lists the contents of the current TFFS directory.
Modies the directory.
Displays the path for the current directory.
Creates a new TFFS directory.
Deletes a directory.
Creates a le with any desired name (0 bytes in length) in the TFFS, enabling
specic switch les to be created for more thorough error detection by the
developer.
#
*
These commands can be used to correct a faulty RAM disk during a restart.
The gateway behaves in the same way as when disconnecting and reconnecting (for debugging only).
Deletes a le from the TFFS.
Displays this list.
Starts the system (loads and executes software).
Displays the start parameters.
Changes the start parameters (see also Table 4).
Small L prints the Boot logo.
Table B-2
Boot Commands
Boot commands can only be specied via a terminal that is connected to the V.24 interface.
They are not available in Telnet sessions.
B.2.2
Start Parameters
The following parameters can be modied using the c boot command:

Parameters
boot device
Description
Start unit; available units: emac0 or tffs/
processor number Always zero.
Sample value
emac0
0
host name
Name of the host from which the system is being started. host1
le name
Complete path of the module to be started.
Table B-3
X_CG25_C.001
Start Parameters
A31003-H3540-A800-1-7619, 2003-05-02
B-3
Admain_anhang_B.fm

Parameters
Description
Sample value
inet on ethernet
(e)
IP address of HiPath HG 1500

including the subnet mask.
139.1.24.88
255.255.255.0
inet on
backplane (b)
Not used, stays empty.
host inet (h)
IP address of the BootP server from which the system

should be started.
gateway inet (g)
IP address of a gateway node if the BootP server is not 139.1.21.13

in the same network as the target device.
user (u)
Access name of the administrator for FTP.
139.1.1.30
ftp password (pw) Password for the FTP administrator name.

ags (f)
Conguration options that are specied as numerical

values:
0x00 Load the start conguration via FTP (default)
0x02 Load icon for local system
0x04 Deactivate automatic startup
0x08 Quicker automatic start (no countdown)
0x20 Deactivate logon protection
0x80 Load start conguration via TFTP
target name (tn)
Name of the target system that is to be added to the host

table (necessary).
other (o)
Must always be set to emac.
Table B-3
B.2.3
0x00
Start Parameters
Editing Start Parameters
If c is specied in the command line, the rst current start parameter is displayed (for example:
boot device emac0). To modify this value, specify the new value after the value displayed.
Press z to save the new value.
>
B-4
If the start parameters were modied with the c command but not saved, only the
RAM data is changed. The modied data is only used for the next boot procedure.
The changes are only saved to the ash memory after successful startup using the
modied parameters.
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_B.fm

Software Installation using the Boot CLI
The following commands are available for navigating within the command line and for editing
entries.
Command
Description
Entering a point deletes the content of the line.
Input key
Pressing the input key displays the next parameter line.
Entering a minus sign displays the contents of the previous parameter line.
CTRL-d
Inputting <CTRL>-D terminates the editing process for start parameters.
Table B-4
B.3
Commands for Editing Start Parameters
Proceed as follows to correctly install the software using the Boot CLI:
B.3.1
Preparations
The TFTP server is available. A self-extracting le (*.inst) containing the software image is available on the server in a known directory. This le automatically installs the
software during system startup.
A console is connected to the V.24 interface.
B.3.2
Loading the Software to the Flash Memory
1.
Press any key on the connected console keyboard if the message Press any key to stop
auto-boot... is displayed on the terminal. The session then starts as for the root administrator and requests a password.
2.
Enter a valid password.
3.
Press c and change the start parameters to the following values:

Parameters
Value
boot device
emac0
processor number
host name
Name of the TFTP or FTP server.
le name
Name of the le containing the software image (e.g. X_CG25_C.001).
inet on ethernet (e)
IP address of the HG 1500 including the subnetwork mask.
inet on backplane (b) No changes required.

Table B-5
Start Parameters for Software Installation via Boot CLI
A31003-H3540-A800-1-7619, 2003-05-02
B-5
Admain_anhang_B.fm

Parameters
Value
host inet (h)
IP address of the TFTP or FTP server.
gateway inet (g)
Gateway IP address, via which the TFTP or FTP server can be

reached (optional).
user (u)
FTP access name.
ftp password (pw)
FTP password.
ags (f)
In the case of FTP: 0x00, in the case of TFTP: 0x80
target name (tn)
Name of the HiPath HG 1500.
other (o)
emac
Table B-5
Start Parameters for Software Installation via Boot CLI
4.
Once you have changed the start parameters, enter the w command.
5.
Enter the extension 001 at the prompt. The le name is now SW_IMAGE.001.
6.
Wait until the data transfer is complete. If errors occur, check the values of the start parameters and the LAN cable connection and make sure that the FTP or TFTP server is operational.
7.
Once the data has been transferred you will be asked if the changes made to the start parameters are to be saved. Press y to save your changes.
8.
Now run the self-extracting le (*.INST) and wait for the system to restart.
The new software is now installed on the board. All user-dened congurations are deleted and
the boards database is empty.
B-6
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_C.fm
Tables
Tables
This chapter contains
trace templates and
event templates.
To provide a clear overview, these tables are displayed horizontally.
A31003-H3540-A800-1-7619, 2003-05-02
C-1
C-2
Trace Templates
EVTLOG
EVTLOGTRAP
SENDTMT
SYSTEM: 3
EVTLOG: 3
Standard trace prole to observe system relevant data, like important status messages and event information
Tables
Trace Templates
disabled
SystemInfo
Description
Reports when a call is rejected due to overload handling
INTRA (6)
Prole contains the following

Trace Components and Levels
(per Component)
Shows whether overload handling by the SSM is enabled or not
receiving a message (extra info for TMT)
error while sending or posting a message (extra info for TMT)
INTER (3)
Activation/Deactivation of an Trace Prole for an occurred event
Mutex blocking situations
6
3
Ensure that events are also visualized via trace on console/in trace log/via lan trace
Always on, global system information (do not change this)
Description
Trace Prole Name Prole per Default

Enabled/Disabled
Proles
SYSTEM
SERVICE_TRACE
Congured
Default Trace
Level
Component
Level (0-9)
STATUS == Level 0
INTER == Level 3
INTRA == Level 6
DETAIL == Level 9
System Traces
Components
C.1.1
The following tables contain the original trace templates. The tables are sorted according to trace components and factory default trace proles.
C.1
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
Congured
Default Trace
Level
Component
TOOLS
DISPATCH
MANAGER
A31003-H3540-A800-1-7619, 2003-05-02
ADMIN
problems with logical msg queue (see remarks above)

wrong coded component message handling, internal SW problems
- Message not unregistered (wrong RecvListType)
- Message not registered (wrong RecvListType)
- Post Message not successful (wrong RecvListType)
- Send Message not successful (wrong RecvListType)
- Unregistered Post Message
- Unregistered Send Message
(see remarks for trc level 6)
6 / 9
incoming and outgoing admin messages with all details

This has an impact to the system performance.
incoming and outgoing admin messages with all details;
also internal admin messages, like polling information.
This has a big impact to the system performance.
3
9
problems with deleting, adding, changing objects of managers
This has a big impact to the system performance.

This setting should only be used for getting message details
listing of the msg header of all messages sent via dispatcher

This has an impact to the system performance.
This setting must be preferred for getting an overview
detailed listing of all messages sent via dispatcher
nishing of class OSThread threads
Description
Level (0-9)
STATUS == Level 0
INTER == Level 3
INTRA == Level 6
DETAIL == Level 9
OAM / WBM Traces
Components
C.1.2
Admain_anhang_C.fm
Tables
Trace Templates
C-3
C-4
RIPCONF
SWCONF
EMAIL_MANAGER
TIME_SYNC
OAM
MGAF_TBL
Congured
Default Trace
Level
Component
stack overow information for all tasks

stack usage information for all tasks
execution of OAM Threshold Timer
OAM Task Queue Problems like queue full, ...
problems when conguring SNTP/Time Synchronization (not relevant for HXG3, moved to
TIME_SYNC)
4
5
5
6
6
RIP not initialized,

Loopback Entry not initialized
own RIP Entry not initialized
(This Trace Component is not relevant for HXG3)
Information about sending E-Mails and connections to mail server
detailed socket information
6
3
login/logout/connection status information
detailed information about job interna of any kind of jobs, e.g. HTTP le transfer, MGAF etc.
fatal errors, e.g. missing parameters, invalid session ID
status information about job handling and process
fatal errors, e.g. missing parameter, unknown commands etc.
problems when conguring SNTP/Time Synchronization (not relevant for HXG3)
data ow of routing wizard actions - create default routes, delete routes, ... (not relevant for
HXG3)
data ow of uploads and backup/exports/upgrades (requires to execute the admin action)
Description
Level (0-9)
STATUS == Level 0
INTER == Level 3
INTRA == Level 6
DETAIL == Level 9
Admain_anhang_C.fm
Tables
Trace Templates
A31003-H3540-A800-1-7619, 2003-05-02
Congured
Default Trace
Level
Component
SESSION_MGMT
OAM_ACTIONLIST
COMMUNITIES
Trap
SNMP
CMGMT
write admin session data to persistency w/wo synching
A31003-H3540-A800-1-7619, 2003-05-02
Detailed Trap Information
0-9
status, ..., detailed information about CLI actions.

Only use this trace after discussion with development
status, ..., detailed information about the congured data (via SNMP) and internal SNMP informations and problems.
Only use this trace after discussion with development
Status Information like:

- trap receive ok
- trap received from local host or from anywhere
- error information
Add/remove Trap to/from Trap Buffer
0-9
Important status information (trap from IP and port, SNMP Trap Version)
Fatal errors when receiving traps
Add/delete/change SNMP read/write/trap communities

Receive SNMP Trap Destination via Autodiscovery
execution of automatic scheduled actions (garbage collection, gatekeeper switchback, ...)
admin session creation or verication

(only >= 2.1)
admin session update
removal of expired admin session
closing admin sessions
write token/access handling (get/release)
info about: GetUserInfo, SessionUpdate, SessionIDVerication
Description
Level (0-9)
STATUS == Level 0
INTER == Level 3
INTRA == Level 6
DETAIL == Level 9
Admain_anhang_C.fm
Tables
Trace Templates
C-5
C-6
Congured
Default Trace
Level
WEBAPPL
SECURITY_SVC
WEBSERVER
WEBSRV_SYS_IF
WEBSRV_CLIENT_ 0
IF
Component
fatal errors, e.g. missing parameter, unknown commands etc

status information and handling
detailed information, method calls
3
6
entry/exit of important webApplication functions/methods only for developers
entry/exit of important webSever functions/methods (for developers)
3/6
Login data send to admin Interface, Response send to client, internal param table information
user/password information
6
9
admin interface trace

data send to the admin interface, xml data got from the admin interface
http socket trace

the http data, including the http stack coming form the browser are printed
the http data, including the http stack of dynamic pages (xml) and generated/static pages
(htm,html) () send to the browser are printed
same as 3, additionally with traces for polling requests.
note: the WEBSRV_SYS_IF trace includes no trace information for polling requests
data send to and coming from gatekeeper (gateway detection, autodiscovery)
http socket trace (without tracing polling requests)

the http data, including the http stack coming form the browser are printed
the http data, including the http stack of dynamic pages (xml) send to the browser are printed
trace all requested (URI/URL) coming from a http-client (normally a browser)

only the name of the URI is printed
Description
Level (0-9)
STATUS == Level 0
INTER == Level 3
INTRA == Level 6
DETAIL == Level 9
Admain_anhang_C.fm
Tables
Trace Templates
A31003-H3540-A800-1-7619, 2003-05-02
ADMIN: 3
WEBSRV_CLIENT_IF: 1
WEBSRV_SYS_IF: 2
disabled
disabled
AdminOverview
AdminDetails
ADMIN: 9
WEBSRV_CLIENT_IF: 1
WEBSRV_SYS_IF: 2
WEBSERVER: 6
WEBAPPL: 6

(per Component)

Enabled/Disabled
Proles
Details for the Admin Data Flow.

Details are shown at all interfaces (WBM/AdminReceiver)
(This Prole has a big impact to the system performance)
Overview for the Admin Data Flow.

Important Information at WebServer IF is shown.
Admin messages are shown in detail at the Admin Receiver IF.
(This Prole has an impact to the system performance)
Description
Admain_anhang_C.fm
Tables
Trace Templates
A31003-H3540-A800-1-7619, 2003-05-02
C-7
C-8
SUSY_LICMGMT
disabled
License_
Management_1.3
LICMGMT: 6
DEVMGR: 3
SCN: 3
HFA_Manager: 3
LICMGMT: 6
DEVMGR: 3
SCN: 3
disabled
More details
License_
Management_1.2
Function exits and results
Trace for analysis of License Management, HiPath 3.0
Trace for analysis of License Management, Hicom 1.2
Description
Received and sent messages via AdminIF

(per Component)
not used
Description

Enabled/Disabled
Proles
Congured
Default Trace
Level
Component
Level (0-9)
STATUS == Level 0
INTER == Level 3
INTRA == Level 6
DETAIL == Level 9
Licence Management Trace
Components
C.1.3
Admain_anhang_C.fm
Tables
Trace Templates
A31003-H3540-A800-1-7619, 2003-05-02
SUSY_IPACCSRV
A31003-H3540-A800-1-7619, 2003-05-02
disabled
IP_Accounting_
Results
IPACCSRV: 6
PPTP_PROC: 3
PPPOE_PROC: 3
PPP_STACK_PROC: 3
IPACCSRV: 6
disabled
More details
IP_Accounting_
Client
Function entries and exits
Trace for analysis of IP Accounting
Trace for problems with the IP Accounting Client
Description
Received and sent messages (from/to message queue, socket), IP client status

(per Component)
Logon, Logoff
Description

Enabled/Disabled
Proles
Congured
Default Trace
Level
Component
Level (0-9)
STATUS == Level 0
INTER == Level 3
INTRA == Level 6
DETAIL == Level 9
IP Accounting Trace
Components
C.1.4
Admain_anhang_C.fm
Tables
Trace Templates
C-9
C-10
GSA Trace
SUSY_GSA
SUSY_GSA_DISP
SUSY_GSA
SUSY_GSA_DISP
Disabled
GSA
Gatekeeper Supervisory Application

GSA dispatcher
Description
Trace for low importance and very detailed message tracing

(per Component)
Trace for semi important and more detailed tracing
Trace for low importance and very detailed message tracing
9
Trace for very important message tracing for GSA dispatcher
Trace for semi important message tracing (semi detailed)
Gatekeeper Supervisory Application trace for very important message tracing
Description
Level (0-9)
STATUS == Level 0
INTER == Level 3
INTRA == Level 6
DETAIL == Level 9

Enabled/Disabled
Proles
Congured
Default
Trace Level
Component
Components
C.1.5
Admain_anhang_C.fm
Tables
Trace Templates
A31003-H3540-A800-1-7619, 2003-05-02
CP Trace
Congured
Default Trace
Level
Component
H323Client
IPNC
NU_LEGCTRL
HFA_ADAPTER
Components
C.1.6
A31003-H3540-A800-1-7619, 2003-05-02
Incoming and outgoing messages, object creating/destroying
Methods calling
More details
3
6
9
Checking variables and pointers
9
Startup/Shutdown
Function entries and exits, states of call objects
Received and sent messages, parameters printing
Level6 + details of the processing within individual methods/functions
9
Startup, shutdown
Level3 + interface between sub-components: IPNCC, IPNCA
Level0 + Messages received from other components: SI, HFAM, NU, H323, SSM
Level6 + details of the processing within individual methods/functions and messages sent to
other components: NWRS, System Interface
No sub-components exist: same as Level3
only trace error and status conditions
Messages received from other components: OAM
Not used
Description
Level (0-9)
STATUS == Level 0
INTER == Level 3
INTRA == Level 6
DETAIL == Level 9
Admain_anhang_C.fm
Tables
Trace Templates
C-11
C-12
SSM
SCNPAY
PPP_CC
HFA_Manager
NWRS
Congured
Default Trace
Level
Component
External interfaces of SCN Payload Manager. Maintains B-Channels and de-multiplexes messages into signaling relevant information and payload relevant information.
External and internal interfaces of SCN Payload Manager.
External and internal Interfaces and details of the processing within SCN Payload Manager.
6
9
External and internal Interfaces and details of the processing within Network Routing Service.
External and internal interfaces of Network Routing Service.
Not used
External interfaces of Network Routing Service. Determines protocols and resources for incoming calls, manages out dial rules.
Tables
Trace Templates
Not used
External and internal Interfaces and details of the processing within Session Signaling Manager.
External and internal interfaces of Session Signaling Manager.
6
9
External interfaces of Session Signaling Manager. Manages the session/call signaling objects). Used to trace Call Message Handling.
External and internal Interfaces and details of the processing within PPP Call Control
9
Not used
External and internal interfaces of PPP Call Control
External interfaces of PPP Call Control to other components, z.B. PPP-Manager
More details
Methods calling
Not used
Incoming and outgoing messages, object creating/destroying
Startup/Shutdown
Description
Level (0-9)
STATUS == Level 0
INTER == Level 3
INTRA == Level 6
DETAIL == Level 9
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
SPL
CPMSG
SDR
SS
H323Client: 9
NWRS: 9
SSM: 3
DSS1: 3
IPNC: 3, SI: 3, SSM: 3, NU: 3,
HFAM: 3 SPL: 3
H323_Client_Admin disabled
IPNC-Std
Standard trace prole for problems with establishment/termination of PPP

connections
Standard trace prole to observe the conguration of H323 clients
Description
disabled

(per Component)
Trace conversion of party numbers.
External and internal Interfaces and details of the processing within Statistical Data Recording.
External and internal interfaces of Statistical Data Recording.
Not used
External interfaces of Statistical Data Recording. SDR collects call related data by monitoring
the interfaces.
Not used
Detailed trace for call relevant internal messages.
9
0
Trace call relevant internal messages.
External and internal Interfaces and details of the processing within Session Payload Manager.
External and internal interfaces of Session Payload Manager.
Not used
External interfaces of Session Payload Manager. Manages the session/call payload objects.
Not used
Description
Level (0-9)
STATUS == Level 0
INTER == Level 3
INTRA == Level 6
DETAIL == Level 9

Enabled/Disabled
Proles
Congured
Default Trace
Level
Component
Admain_anhang_C.fm
Tables
Trace Templates
C-13
disabled
disabled
disabled
disabled
disabled
disabled
IPNC-Error
IPNC-Internal
IPNC-Detailed
C-14
PPP_CC-Std
PPP_CC-Features
PPP_CC-Detail

connections
Trace prole for detailed analysis of IPNC
Trace prole for internal analysis of IPNC
Trace prole for only tracing error and status conditions
PPP_CC: 9, PPPM_TBAS: 3,
Detailed trace prole for problems with establishment/termination of PPP
PPPM_TSTD: 3, SSM: 3, GWSI: 3 connections
Trace prole for problems with PPP features. callback, retry and short hold
PPPM_TSTD: 6, SSM: 6, GWSI: 3 mode
PPPM_TSTD: 3, SSM: 3, SPL: 3
IPNC: 9, SI: 3, NU: 3, HFAM: 3,

SSM: 3, SPL: 3
IPNC: 6
IPNC: 0
Admain_anhang_C.fm
Tables
Trace Templates
A31003-H3540-A800-1-7619, 2003-05-02
Congured
Default Trace
Level
Component
CN
CNQ
DSS1
A31003-H3540-A800-1-7619, 2003-05-02
CNIWK
CNQIWK
Q931
Traces about encoding/decoding of IEs.

Trace all information available.
3/6
9
Normal operation traces.
3/6
9
0
3/6
9
Long description of messages.
3/6
Short description of messages, normal operation traces.
9
0
3/6
9
3/6
Description
Level (0-9)
STATUS == Level 0
INTER == Level 3
INTRA == Level 6
DETAIL == Level 9
SCN Protocol Trace
Components
C.1.7
Admain_anhang_C.fm
Tables
Trace Templates
C-15
C-16
CAR
NU
REG
Congured
Default Trace
Level
Component
Not used
Trace level to see messages received from other components
To be used when there are problems with IP Networking Call Setup in an AllServe conguration (with Allserve Server)
Trace level to see the ow within the functional blocks of the REG component
To be used when there are problems in case of IP Networking Call Address Resolution in an
Allserve Conguration (with Allserve Server)
Trace level to see the details of the processing between and within individual functional blocks
To be used when there are major problems within REG or on the interface with REG
of CAR
To be used when there are major problems within CAR or on the interface with CAR
Trace level to see the ow within the functional blocks of the CAR component
To be used when there are problems in case of IP Networking Call Address Resolution

To be used when there are problems in case of IP Networking Call Setup
of NU
To be used when there are major problems within NU or on the interface with NU
Trace level to see the ow within the functional blocks of the NU component
To be used when there are signaling problems in case of IP Networking
Not used

To be used generally when there are problems in case of IP Networking
Not used
Description
Level (0-9)
STATUS == Level 0
INTER == Level 3
INTRA == Level 6
DETAIL == Level 9
IP Networking Trace
Components
C.1.8
Admain_anhang_C.fm
Tables
Trace Templates
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
NS
GWSI: 3, DEVMGR: 3, NU: 3,

CAR: 3, REG: 3, NS: 3, SOH: 9,
DELIC_DRIVER: 6, MSC_TMT: 6
GWSI: 3, DEVMGR: 3,
DISPATCH: 3, CN:6, SSM: 6,
NU: 6, NU_LEGCTRL: 6, CAR: 6,
SOH: 9
GWSI: 3, DEVMGR: 6,
DISPATCH: 3, CN: 6, SSM: 6,
NU: 3, NU_LEGCTRL: 3, H323: 6,
HSA_H225_CS: 6, HSA_H245: 6,
SCN: 6, LAN: 6, MSC: 6,
DELIC_DRIVER: 6
disabled
IPTRKVoice1.2-Sig- disabled
nalling
IPTRKVoice1.2-Pay- disabled
load
of NS
To be used when there are problems within NS or on the interface with NS
IPTRKVoice1.2Cong
Trace level to see the ow within the functional blocks of the NS component
To be used when there are problems in case of IP Networking connection failure within a conguration with Alive Check activated
Trace Prole for IP Networking Voice V1.2 when there are problems with
the payload
Standard Trace Prole for IP Networking Voice V1.2
Trace Prole to analyze the IP Networking V1.2 conguration settings during startup time
Description

To be used generally when there are problems in case of IP Networking connection failure
within a conguration with Alive Check activated

(per Component)
Not used
Description
Level (0-9)
STATUS == Level 0
INTER == Level 3
INTRA == Level 6
DETAIL == Level 9

Enabled/Disabled
Proles
Congured
Default Trace
Level
Component
Admain_anhang_C.fm
Tables
Trace Templates
C-17
C-18
GWSI: 3, DEVMGR: 6,
NU: 3, IPNC: 6, H323: 6,
HSA_H225_CS: 6, HSA_H245: 6,
SCN: 6, LAN: 6, MSC: 6,
DELIC_DRIVER: 6
IPTRKVoice1.3-Pay- disabled
load
GWSI: 3, DEVMGR: 3, NU: 3,

CAR: 3, REG: 3, NS: 3, SOH: 9,
DELIC_DRIVER: 6, MSC_TMT: 6,
IPNC: 6
GWSI: 3, DEVMGR: 3,
NU: 6, IPNC: 6, CAR: 6, SOH: 9
disabled
IPTRKVoice1.3-Sig- disabled
nalling
IPTRKVoice1.3Cong
Trace Prole for IP Networking Voice V1.3 when there are problems with
the payload
Standard Trace Prole for IP Networking Voice V1.3
Trace Prole to analyze the IP Networking V1.3 conguration settings during startup time
Admain_anhang_C.fm
Tables
Trace Templates
A31003-H3540-A800-1-7619, 2003-05-02
H.323 Trace
DETAIL
INTER
STATUS
STATUS
STATUS
STATUS
DETAIL
SUSY_HSA_H225_
CS
SUSY_HSA_H225_
RAS
A31003-H3540-A800-1-7619, 2003-05-02
SUSY_HSA_H245
SUSY_HSA_
SYSTEM
SUSY_HSA_RV_
LOG
SUSY_PERFM_SIG STATUS
Performance trace for signalling part. Trace of SETUP, CONNECT and RELEASECOMPLETE
Logging of RADVision stack traces
Information traces
Receipt of dispatcher messages, admin receiver, initialization/destruction HSA, HSA thread
handling
Post message to H.323 protocol manager, call handle counter
Function trace, conguration parameter trace
Information traces
Callbacks that lead to a message towards H.323 protocol manager, stack API functions that
lead to a LAN message
Callbacks that just collect parameter information
Function/parameter trace
Information traces
only used in specic situations
Information traces, H.323-stack API errors

PVT usage of H.323 stack
Information traces
Receipt of dispatcher messages, admin receiver
Post/Send message to other components
Description
INTRA
DETAIL
STATUS
INTER
INTRA
DETAIL
STATUS
INTER
INTRA
DETAIL
STATUS
INTER
INTRA
DETAIL
STATUS
INTER
STATUS
INTER
INTRA
DETAIL
STATUS
SUSY_H323
Level (0-9)
STATUS == Level 0
INTER == Level 3
INTRA == Level 6
DETAIL == Level 9
Congured
Default Trace
Level
Component
Components
C.1.9
Admain_anhang_C.fm
Tables
Trace Templates
C-19
C-20
disabled
H323_ANALYSIS_
CALL
disabled
H323_CLIENT_
PAYLOAD
disabled
disabled
H323_CLIENT_
DETAIL_SIG
H323_ANALYSIS_
STARTUP
EVTLOG: 3
H323:3
HSA_SYSTEM: 3
SSM: 3
DSS1: 3
disabled
H323_CLIENT_SIG
NALLING
EVTLOG: 3
HSA_SYSTEM: 9
HSA_H225_CS: 9
HSA_H245: 9
H323: 9
EVTLOG: 3
HSA_SYSTEM: 9
H323: 9
EVTLOG: 3
H323: 9
SCNPAY: 3
DSS1: 3
SPL: 9
DEVMGR: 3
LAN: 6
MSC: 0
EVTLOG: 3
HSA_H225_CS: 6
HSA_H245: 6
HSA_SYSTEM: 6
H323: 3
SSM: 3
SCNPAY: 3
DSS1: 3
SPL: 3

(per Component)

Enabled/Disabled
Proles
This prole should be activated when call related events are logged for the
H323 protocol components.It should be used for single call analysis only
This prole should be activated when events are logged for the subsystem
HSA_SYSTEM or when there are indications for a wrong conguration/
startup of H323.
Prole should be used to trace payload problems of a H323 client call. It

should be used for single call analysis only
Prole used to get a more detailed trace for signaling problems of a H323
client call.
It should be used for single call analysis only
Prole used to trace signaling problems of a H323 client call. First analysis
trace
Description
Admain_anhang_C.fm
Tables
Trace Templates
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
DEVMGR
LAN
SCN
IFTABLE
SUSY_DEVMGR: 6
SUSY_IFTABLE: 6
SUSY_DEVMGR: 3
SUSY_ DEVMGR: 3
SUSY_LAN : 6
SUSY_SCN : 6
Disabled
Disabled
DEVMGR-Startup
DEVMGR-CP
DEVMGR-Overview Disabled
Not used
Shows interface functions with important parameters
Shows the Callprocessing interface functions for Call-Setup/-Release
Shows the Startup of Device Manager and IF-table conguration
Description
Shows function calls with important parameters

(per Component)
Shows errors
Shows detailed informations
9
3
Shows detailed informations
9
Shows some normal operation cases and errors
Shows some normal operation cases and errors
Shows CP interface functions for call setup and errors
Description

Enabled/Disabled
Proles
Congured
Default Trace
Level
Component
Level (0-9)
STATUS == Level 0
INTER == Level 3
INTRA == Level 6
DETAIL == Level 9
Device Manager Trace
Components
C.1.10
Admain_anhang_C.fm
Tables
Trace Templates
C-21
C-22
HIP Trace
GWHIP
SUSY_IPSTACK_
HIP_IF
GWSI:3, GWHIP:3
disabled
HIP-Standard
Not used
Standard Trace Prole for HIP (Proxy IP Access for HiPath 3000)
Description
Not used

(per Component)
Standard trace level to see the conguration of the HIP I/F to the IP-Stack
Not used
Not used
Not used
Standard trace level to see the ow within and between functional blocks of HIP
Not used
Description
Level (0-9)
STATUS == Level 0
INTER == Level 3
INTRA == Level 6
DETAIL == Level 9

Enabled/Disabled
Proles
Congured
Default Trace
Level
Component
Components
C.1.11
Admain_anhang_C.fm
Tables
Trace Templates
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
SUSY_IPSTACK_
NAT
SUSY_SOH
SUSY_IPSTACK
SUSY_IPSTACK_
GLOBAL
SUSY_IPSTACK_
ROUTE
SUSY_IPSTACK_
1LAN_IF
SUSY_IPSTACK_
2LAN_IF
TESTLW
MAC_FILTER
IP_FILTER
Component
Congured
Default Trace
Level
0-9
status, ..., detailed information about TESTLW actions.

Only for developers.
Handling of cong data
Error situation of routing data
Error situation in IP-accounting hash functions.

Only for developers
Status, , detailed information about SOH internal.

Only for developers
Initialization
Detailed information about NAT Processing
Translated data
Show rule, that led to the decision
9
3
6
9
Decision: pass/delete
Show rule, that led to the decision
9
Packet
Decision: pass/delete
Packet/direction
Description
Level (0-9)
STATUS == Level 0
INTER == Level 3
INTRA == Level 6
DETAIL == Level 9
SW Platform Trace
Components
C.1.12
Admain_anhang_C.fm
Tables
Trace Templates
C-23
C-24
SUSY_MSP_HDLC
ASP
ASP_DSP_IOCTL
SUSY_FAXCONV_
LOGT
SUSY_DELIC_
DRIVER
SUSY_FAXCONV_
OS
SUSY_FAXCONV_
IF
SUSY_X25
SUSY_FAXCONV_
T30INT
SUSY_FAXCONV_
T30DOWN
SUSY_X75
SUSY_FAXCONV_
T30UP
SUSY_
FAXCONVERTER
SUSY_T90
Congured
Default Trace
Level
Component
more detailed information about call setup / call release (includes all parameters)
Information about call setup / release
3
9
Detailed information about call setup / release of MSP (except DSP-DD)
status, ..., detailed information about HDLC-Driver actions.

status, ..., detailed information about DELIC driver (SWC).

status, ..., detailed information about X.25 Protocol actions.

status, ..., detailed information about X.75 Protocol actions.

status, ..., detailed information about T.90 Protocol actions.

Customer trace, show if bad fax transmission occurred!
status, ..., detailed information about FaxConverter OS Interface Module actions.

status, ..., detailed information about FaxConverter CAPI Interface Module actions.
status, ..., detailed information about FaxConverter T.30 Module actions.

status, ..., detailed information about FaxConverter T.30 Module downstream interface actions.
status, ..., detailed information about FaxConverter T.30 Module upstream interface actions.
status, ..., detailed information about FaxConverter routines and Fax Converter Streamsinterface actions.
Description
Tables
Trace Templates
0-9
0-9
0-9
0-9
0-9
0-9
0-9
0-9
0-9
0-9
0-9
Level (0-9)
STATUS == Level 0
INTER == Level 3
INTRA == Level 6
DETAIL == Level 9
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
ASP_DSP_EVENT
ASP_DSP_STAT
MSC
MSC_TMT
MSC_RTCP
MSC_QM
SUSY_DSP
SUSY_MSP_RTP_
MOD
internal functions called during RTCP session

detailed information to all MSC functions (only RTCP context)
6
9
not used
internal messages from RTP module
3-9
internal messages from PPP interface driver
3-9
0
not used
internal messages from CAPI interface driver
3-9
0
not used
messages issued by DSP and displayed by DSP driver
3-9
0
not used
Information about quality monitoring
callback function from MSP concerning RTCP events
General information about RTCP session, timer,
all I/O controls (interface to MSP) will be traced
setting of the cong params (MSC, MSP/DSP) will be traced + detailed information to all MSC
functions
tracing of the MSC internal functions + handles/ledescriptors
MSC functions called by Magic will be traced
also the I/O controls to MSP will be traced
API to Magic (function calls with parameters)
Information about Data Channel Conguration after call setup (FAX, Modem, V.110)
Information about detected DTMF- , Fax- or Modem
Description
Level (0-9)
STATUS == Level 0
INTER == Level 3
INTRA == Level 6
DETAIL == Level 9
SUSY_MSP_PPP_
IF
SUSY_MSP_CAPI_ 0
IF
Congured
Default Trace
Level
Component
Admain_anhang_C.fm
Tables
Trace Templates
C-25
C-26
SUSY_MAT_
STREAM
SUSY _STREAMS
PPTP_PROC
PPTP_DBG_IF
PPPOE_PROC
PPPOE_DBG_IF
PPPM_TBAS
PPPM_TSTD
PPPM_TEXT
PPP_STACK_PROC 0
PPP_STACK_DBG_ 0
IF
Congured
Default Trace
Level
Component
information about setup and release of PPP connections
3-9
3-9
extended information about internal proceedings of PPP-Manager
internal message ow of PPP-Manager
PPP-Manager: basic conguration and status messages, abnormal conditions
Tables
Trace Templates
3-9
PPP negotiation phase
Status of PPP connection setup / release
3
6-9
PPP Stack internal program ow
PPP Stack internal error message
3
6-9
more detailed information about call setup / call release
internal error messages of PPPoE step machine for debugging
3-9
6-9
not used
Information about call setup / release at PPP Manager Interface
3
0
more detailed information about call setup / call release
internal error messages of PPTP for debugging
3-9
6-9
not used
Information about call setup / release at PPP Manager Interface
3
0
detailed information about MSC specic quality data
internal messages from Streams memory management
3-9
9
not used
internal messages from materna memory management
3-9
0
not used
Description
Level (0-9)
STATUS == Level 0
INTER == Level 3
INTRA == Level 6
DETAIL == Level 9
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
PPPCC: 3, PPPM_TBAS: 3,
SSM: 3, SPL: 3, MSC: 6,
PPP_STACK_PROC: 6,
PPP_DBG_IF: 3
disabled
disabled
disabled
disabled
disabled
disabled
disabled
disabled
disabled
disabled
PPPISDNCall
PPPModemCall
ISPAccessISDN
ISPAccessModem
A31003-H3540-A800-1-7619, 2003-05-02
ISPAccessPPPoE
ISPAccessPPTP
H323VoiceCall
HFAVoiceCall
IPTrunkVoiceCall
ToneProcessing
SSM: 3, DSS1: 3, MSC: 6,

ASP_DSP_EVENT: 3
Trace prole for problems with tone processing handling (e.g. DTMF)
Trace prole for problems with IPTRK call setup / release within MSC /
MSP
Trace prole for problems with HFA call setup / release within MSC / MSP
Trace prole for problems with H.323 call setup / release within MSC / MSP
Trace prole for problems with establishment/termination of PPP connection to ISP via PPTP incl. PPP stack negotiation
Trace prole for problems with establishment/termination of PPP connection to ISP via PPPoE incl. PPP stack negotiation
Trace prole for problems with establishment/termination of PPP connection to ISP via Modem incl. PPP stack negotiation
Trace prole for problems with establishment/termination of PPP connection to ISP via ISDN incl. PPP stack negotiation

connection via Modem incl. PPP stack negotiation

connection via ISDN incl. PPP stack negotiation
Description
IPNC: 3, SI: 3, SSM: 3, NU:3,

SPL: 3, MSC: 6
IPNC: 3, HFAM: 3, SSM: 3,

DSS1: 3, SI: 3, MSC: 6
H323: 3, SSM: 3, DSS1: 3, SI: 3,

MSC: 6
PPPM_TBAS: 3, PPTP_PROC: 3,
PPP_STACK_PROC: 6,
PPP_DBG_IF: 3
PPPM_TBAS: 3,
PPPOE_PROC: 3,
PPP_STACK_PROC: 6,
PPP_DBG_IF: 3
SSM: 3, SPL: 3, MSC: 6,
PPP_STACK_PROC: 6,
PPP_DBG_IF: 3
SSM: 3, SPL: 3, MSC: 6,
PPP_STACK_PROC: 6,
PPP_DBG_IF: 3
SSM: 3, SPL: 3, MSC: 6,
PPP_STACK_PROC: 6,
PPP_DBG_IF: 3

(per Component)

Enabled/Disabled
Proles
Admain_anhang_C.fm
Tables
Trace Templates
C-27
C-28
ASP_DSP_EVENT: 6,
Trace prole for problems with the transfer of a FAX document within the BASP_DSP_IOCTL: 3,
channel.
BSD44_PROC: 3, VCAPI_DISP: 3,
VCAPI: 3, CAPIMGR: 3,
SUSY_FAXCONVERTER: 9,
SUSY_FAXCONV_T30UP: 5,
SUSY_FAXCONV_T30INT: 9,
SUSY_FAXCONV_T30DOWN : 5,
SUSY_FAXCONV_IF: 5,
SUSY_FAXCONV_OS: 8,
SUSY_FAXCONV_LOGT: 0
DELIC_DRIVER: 6,
Trace prole for problems with the setup and cleardown of the FAX connecMSP_HDLC: 6,
tion within the B- channel.
SUSY_X75: 3, SUSY_T90: 6
T30_38_FAX_XFER Disabled
Disabled
Disabled
Disabled
T90_CON
T90_XFER
X25_CON
Tables
Trace Templates
DELIC_DRIVER: 6,
Trace prole for problems with the setup and cleardown of an X.25 connecMSP_HDLC: 6,
SUSY_X75: 3, SUSY_X25: 6
DELIC_DRIVER: 6,
Trace prole for problems with the data transfer of an T.90 connection withMSP_HDLC: 6,
in the B- channel.
SUSY_X75: 3, SUSY_T90: 9
DELIC_DRIVER: 6, MSC: 6,
Trace prole for problems with the setup and cleardown of the FAX connecASP_DSP_EVENT: 3,
ASP_DSP_IOCTL: 3,
SUSY_FAXCONVERTER: 6,
SUSY_FAXCONV_T30UP: 9,
SUSY_FAXCONV_T30INT: 6,
SUSY_FAXCONV_T30DOWN : 9,
SUSY_FAXCONV_IF: 6,
SUSY_FAXCONV_LOGT: 0
disabled
T30_38_FAX_CON
Description

(per Component)

Enabled/Disabled
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
Disabled
Disabled
X75-CON
X75_XFER
DELIC_DRIVER: 6,
Trace prole for problems with the data transfer of an X.75 connection withMSP_HDLC: 6,
in the B- channel.
SUSY_X75: 9
DELIC_DRIVER: 6,
Trace prole for problems with the setup and cleardown of an X.75 connecMSP_HDLC: 6,
SUSY_X75: 6
DELIC_DRIVER: 6,
Trace prole for problems with the data transfer of an X.25 connection withMSP_HDLC: 6,
in the B- channel.
SUSY_X75: 3, SUSY_X25: 9
Disabled
X25_XFER
Description

(per Component)

Enabled/Disabled
Admain_anhang_C.fm
Tables
Trace Templates
A31003-H3540-A800-1-7619, 2003-05-02
C-29
Event Templates
C-30
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Status Events
MSG_GW_
Information
SUCCESSFULLY_
STARTED
EventCode
C.2.1
Description
Automatic
Remedy Actions
Actions,
performed by
the Gateway
EventLogEntry from
Gateway was started successfully SNMP Trap
EventType: csevInformation
at given time
EventCode:
MSG_GW_SUCCESSFULLY_STARTED
EventText: 11/21/2001 20:46:52
Complete Log for the Event
The following tables contain the original event templates. The tables are sorted according to event types.
C.2
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
EventLogEntry from
EventCode:
MSG_SYSTEM_REBOOT
EventText: Reboot initiated by Garbage
Collection
Available memory: xxxx
EventLogEntry from
EventCode:
MSG_ADMIN_REBOOT
EventText: Reboot initiated by Admin
(SW Upgrade)
Information
Information
EventLogEntry from
EventCode:
MSG_ADMIN_REBOOT
EventText: Reboot initiated by
Admin (SW Image Activation)
Information
MSG_SYSTEM_
REBOOT
EventLogEntry from
EventCode:
MSG_ADMIN_REBOOT
EventText: Reboot initiated by Admin
Information
MSG_ADMIN_
REBOOT
Event Text
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Reboot Events
EventCode
C.2.2
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Not necessary
Not necessary
A reboot, necessary after perform- Requested re- Not necessary

ing internal garbage collection, is boot is executperformed
ed;
SNMP Trap;
For HG3550:
Hicom is informed
A reboot, necessary after performing a data upgrade by an administrator, is performed
A reboot, necessary after activation of a new image by an administrator, is performed
For HG3550:
Hicom is informed
SNMP Trap;
A reboot, requested by an admin- Requested re- Not necessary

istrator, is performed
boot is executed;
Description
Admain_anhang_C.fm
Tables
Event Templates
C-31
C-32
Critical
Critical
MSG_CAT_HSA_
REBOOT
MSG_GW_OBJ_
MEMORY_
EXHAUSTED
Critical
Information
MSG_
EXCEPTION_
REBOOT
MSG_GW_OBJ_
ALLOC_FAILED
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
EventLogEntry from
EventType: csevCritical
EventCode:
MSG_GW_OBJ_ALLOC_FAILED
EventText: Memory allocation in partion
xxx failed. XXX Error.
Last allocation size: xxxx
Rebooting ...
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Possible Memory Problems:

1. allocation size is to big or
2. there is no more memory
Requested re- No action, reboot is

boot is executperformed autoed;
matically.
SNMP Trap;
For HG3550:
Hicom is informed

matically.
SNMP Trap;
For HG3550:
Hicom is informed
H.323 Stack adapter runs out of in- Requested re- Attach event log to
ternal resources and initiates a reboot is execut- error report.
boot
ed;
SNMP Trap;
A reboot after a VxWorks Task Ex- Requested re- Not necessary

ception is performed
boot is executed;
SNMP Trap;
For HG3550:
Hicom is informed
Description
EventLogEntry from
1. allocation size is to big or
EventCode:
2. there is no more memory
MSG_GW_OBJ_MEMORY_
EXHAUSTED
EventText: Object memory has been exhausted. Last allocation size: xxxx. Using
failsafe areas to attempt a graceful shutdown."
EventLogEntry from
EventCode:
MSG_CAT_HSA_REBOOT
EventText: HSA (Reboot)
Q931 cmCallNew() failed:reaching vtNodeCount limit
EventLogEntry from
EventCode:
MSG_EXCEPTION_REBOOT
EventText: Reboot initiated by VxWorks
Task Exception
Event Text
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Critical
Information
Information
Information
Information
EventCode
MSG_GW_OBJ_
MEMORY_
INCONSISTENT
ASSERTION_
FAILED_EVENT
EXIT_REBOOT_
EVENT
A31003-H3540-A800-1-7619, 2003-05-02
EXIT_REBOOT_
EVENT
EXIT_REBOOT_
EVENT
memory allocation failed
task spawn of V24CLI failed
reboot
reboot
Requested reboot is executed;

SNMP Trap;
For HG3550:
Hicom is informed
Internal Software Coding Problem Requested reboot is executed;

SNMP Trap;
For HG3550:
Hicom is informed
Create TR/MR
No action, reboot is
performed automatically.
Create TR/MR
EventLogEntry from
EventCode: EXIT_REBOOT_EVENT
EventText: internal error: not enough
memory.
.
EventLogEntry from
EventText: cannot create task tV24CliI.
.
Automatic
Remedy Actions
Actions,
performed by
the Gateway

1. memory overwritten
boot is executperformed auto2. freeing of already freed memory ed;
matically.
SNMP Trap;
For HG3550:
Hicom is informed
Description
EventLogEntry from
Internal Software Coding Problem
EventCode:
EXIT_REBOOT_EVENT
EventText: Rebooting due to Exit Event
EventLogEntry from
EventCode:
ASSERTION_FAILED_EVENT
EventText: Assertion failed
EventLogEntry from
EventCode:
MSG_GW_OBJ_ALLOC_FAILED
EventText: Memory corruption in partion
xxx
XXX Error.
nInvalid block address: xxxx
Rebooting ...
Event Text
Admain_anhang_C.fm
Tables
Event Templates
C-33
C-34
EventCode: MSG_ASP_REBOOT
EventText: ASP: DSP DISTURBED
<module nr>
MSG_ASP_
REBOOT
Critical
EventLogEntry from
EventType: csevMajor
EventCode:
MSG_SSM_SESSION_CREATION_
FAILED
EventText: Session creation failed.
MSG_SSM_
SESSION_
CREATION_
FAILED
MSG_SSM_NUM_OF_CALL_LEGS_2BI
G
EventText: More than 2 call legs: not supported! CSID: xxxx
Create TR/MR
Gateway reboots
Internal DSP error,

no specic reason

matically.
SNMP Trap;

matically.
SNMP Trap;
Requested reboot is executed;

SNMP Trap;
For HG3550:
Hicom is informed
reboot
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Tables
Event Templates
DSP works no longer
?????
?????
EventLogEntry from
EventCode:
corrupted stdio
MSG_SSM_NUM_ Major
OF_CALL_LEGS_
2BIG
EventLogEntry from
EventText:
CLI: read operation from STD_IN has
failed
.
Description
EventLogEntry from
Internal Pool Size conguration
problem
EventCode:
MSG_TLS_POOL_SIZE_EXCEEDED
EventText: maximal number of elements
exceeded
Information
EXIT_REBOOT_
EVENT
Event Text
MSG_TLS_POOL_ Major
SIZE_EXCEEDED
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
EventLogEntry from
EventCode: MSG_IP_LINK_FAILURE
EventText: IP Link still out of order
EventLogEntry from
Network ip is available again.
EventType: csevCleared
Problem is solved.
EventText: IP Link no longer out of order
Warning
Cleared
SNMP Trap;
There is still no network ip connec- SNMP Trap;

tion.
Verify the network

connector or cable
Verify the network

connector or cable
Automatic
Remedy Actions
Actions,
performed by
the Gateway
There is no network ip connection. SNMP Trap;
EventLogEntry from
EventText: IP Link out of order
Warning
Description
MSG_IP_LINK_
FAILURE
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Resource Observation Events
EventCode
C.2.3
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
C-35
C-36
EventLogEntry from
EventCode:
MSG_OAM_RAM_THRESHOLD_
REACHED
EventText: High WaterMark XXX still
reached: Congured: xxx Current: xxx
EventLogEntry from
EventCode:
REACHED
EventText: High WaterMark XXX no
longer reached: Congured: xxx Current: xxx
Warning
Cleared
EventLogEntry from
EventCode:
REACHED
EventText: High WaterMark XXX
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
MSG_OAM_RAM_ Warning
THRESHOLD_
REACHED
EventCode
Maybe call load is now decreased.
Problem solved.
SNMP Trap;
System Memory Threshold

SNMP Trap;
reached
Details are listed in the event message.
Threshold value, current value,
and usage in percent.
High call load can be the reason.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
System Memory Threshold

SNMP Trap;
reached
Description
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
EventLogEntry from
Problem solved.
SNMP Trap;
EventCode:
Maybe call load is now decreased.
MSG_OAM_DMA_RAM_THRESHOLD_
REACHED
EventText: High WaterMark XXX no
longer reached: Congured: xxx Current: xxx
Cleared
DMA Memory Threshold reached SNMP Trap;

EventLogEntry from
EventCode:
REACHED
EventText: High WaterMark XXX still
A31003-H3540-A800-1-7619, 2003-05-02
-
Automatic
Remedy Actions
Actions,
performed by
the Gateway
DMA Memory Threshold reached SNMP Trap;

Description
Warning
EventLogEntry from
EventCode:
REACHED
EventText: High WaterMark XXX
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
MSG_OAM_DMA_ Warning
RAM_
THRESHOLD_
REACHED
EventCode
Admain_anhang_C.fm
Tables
Event Templates
C-37
EventLogEntry from
EventCode:
MSG_OAM_THRESHOLD_REACHED
EventText: High/Low WaterMark XXX
EventLogEntry from
EventCode:
still reached: Congured: xxx Current:
xxx
EventLogEntry from
EventCode:
no longer reached: Congured: xxx
Current: xxx
Warning
Warning
Cleared
MSG_OAM_
THRESHOLD_
REACHED
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
C-38
Problem solved.
Flash File System Free Size

Netstack IP Resources
SNMP Trap;
Threshold reached
SNMP Trap;
and optionally usage in percent.
Flash File System Free Size

Netstack IP Resources
Netstack Resources: Verify IP Conguration of gateway/routers
Flash: Remove unnecessary les

from ash le system.
Flash: Remove unnecessary les

from ash le system.
Netstack Resources: Verify IP Conguration of gateway/routers
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Threshold reached
SNMP Trap;
and optionally usage in percent.
Description
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
EventLogEntry from
EventCode:
MSG_OAM_PSU_OR_RPS_OUT_OF_
SERVICE
EventText: PSU or RPS out of Service
EventLogEntry from
EventCode:
SERVICE
EventText: PSU or RPS still out of Service
EventLogEntry from
EventCode:
SERVICE
EventText: PSU or RPS no longer out of
Service
Warning
Warning
Cleared
MSG_OAM_PSU_
OR_RPS_OUT_
OF_SERVICE
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
A31003-H3540-A800-1-7619, 2003-05-02
Problem is solved.
There is still a problem with the

PSU or RPS.
SNMP Trap;
SNMP Trap;
Verify/Exchange
PSU or RPS
Verify/Exchange
PSU or RPS
Automatic
Remedy Actions
Actions,
performed by
the Gateway
There is a problem with the PSU or SNMP Trap;

RPS.
Description
Admain_anhang_C.fm
Tables
Event Templates
C-39
C-40
EventLogEntry from
EventCode:
MSG_OAM_FAN_OUT_OF_SERVICE
EventText: Fan still out of Service
EventLogEntry from
Problem is solved.
EventCode:
EventText: Fan no longer out of Service
Warning
Cleared
There is still a problem with the

Fan.
There is a problem with the Fan.
EventLogEntry from
EventCode:
EventText: Fan out of Service
Warning
Description
MSG_OAM_FAN_
OUT_OF_
SERVICE
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
SNMP Trap;
SNMP Trap;
SNMP Trap;
Verify/Exchange
Fan
Verify/Exchange
Fan
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
A31003-H3540-A800-1-7619, 2003-05-02
-
Minor
MSG_NWRS_
UNKNOWN_
FIELD_ECHOED
same as described
for
...EMPTY_FIELD_
ECHOED.
Check the digit

string of the DialPlanMember in
conjunction with
the EchoCommands of the OutDialRule.
Assign Port to a DialPlan, if necessary create a new

DialPlan rst.
Use only allowed

digits and use separators not in sequence and not at
the beginning or at
the end.
Unknown eld # echoed by Out Dial Rule same as described for

#
...EMPTY_FIELD_ECHOED.
Empty eld # echoed by Out Dial Rule # A EchoCommand of an OutDial- Rule results in an empty or unplausible substring.
Warning
MSG_NWRS_
EMPTY_FIELD_
ECHOED
Port is not attached to any DialPlanMember.
Dial Plan Entry invalid: Dpln=#, DplnEn- Syntax error in DialPlan: digits oth- try=#member
er than 0123456789*#ANXZ-
used or separator - misplaced.
Dial Plan not found for Device #port
Minor
Check ODR commands: NPITYPE,

TONTYPE (and
CGNPITYPE, CGTONTYPE) for
plausible values.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Invalid data for NPI or TON value within ODR command; Command
ignored. (May also appear if admin
changes ODR during use).
Description
MSG_NWRS_NO_ Major
DPLN_FOUND_
FOR_DEVICE
MSG_NWRS_
DPLN_ENTRY_
INVALID
Major
Routing Events
MSG_CAT_NWRS Warning
EventCode
C.2.4
Admain_anhang_C.fm
Tables
Event Templates
C-41
C-42
Major
MSG_NWRS_
DPLN_NOT_
FOUND
MSG_NWRS_
Major
UNSPEC_ERROR
Major
MSG_NWRS_
ROUTE_NOT_
FOUND
Major
MSG_NWRS_
DEVICE_TABLE_
NOT_FOUND
"%p"
"Dial Plan not found: Dpln = %i"
Route # not found
Device Table not found
Device #port not found
Major
MSG_NWRS_
DEVICE_NOT_
FOUND
inconsistent state of the software, e.g. invalid data
a dial plan with the given ID could not be found.
A DialPlanMember contains an
unresolved Route Number.
Port not available.
No valid Port assigned to RouteMember.
A RouteMember contains an unresolved OutDialRule Index.
Out Dial Rule # not found
Use a already congured Route or

create a new one.
Try HW recovery.
Set a valid DestinationPort for the RouteMember.
Use an already
congured OutDialRule or create a
new one.
Check the syntax

of the OutDialRule
for keywords and
for separators (:
and ;) as well as
for data constants
or value range limits.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Warning
Description
MSG_NWRS_
ODR_NOT_FOUN
D
Unknown Command string in Out Dial OutDialRule contains an unrecog- Rule #

nizable Command or a value out of
range.
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
MSG_NWRS_
Minor
ODR_COMMAND_
UNKNOWN
EventCode
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
Major
Major
MSG_SCNP_
CHANNEL_ID_
MISSING
MSG_SCNP_NO_
RESOURCE_ID
"SCN Payload: Could not delete SCN
Payload Object - EXCEP: %n%e"
"SCN Payload: Could not create SCN
Payload Object - EXCEP: %n%e"
MSG_SCNP_
Major
COULD_NOT_
DELETE_OBJECT
MSG_SCNP_
Major
COULD_NOT_
CREATE_OBJECT
"SCN Payload: No resource ID available

in message 0x%X - EXCEP: %n%e"
"SCN Payload: Mandatory eld channel

ID missing in message 0x%X - EXCEP:
%n%e"
"SCN Payload: Mandatory eld device ID in the specied message the man- missing in message 0x%X - EXCEP:
datory eld DeviceID is missing,
%n%e"
which is needed to construct the
Resource ID
Major
SCN Payload Object could not be created
SCN Payload Object could not be deleted
no ResourceID available in the

specied message
in the specied message the mandatory eld ChannelId is missing,

which is needed to construct the
Resource ID
MSG_SCNP_
DEVICE_ID_
MISSING
unknown message received
Not used for HXG3
unexpected or unregistered message?
"SCN Payload: Unanticipated Message

%s in state %s - EXCEP: %n%e"
"SDR: Unexpected event %n%M%n in

state %s%n from %s - EXCEP: %n%e"
SDR init failed (no les) something went wrong during initialization of SDR
Automatic
Remedy Actions
Actions,
performed by
the Gateway
MSG_SCNP_
Warning
UNANTICIPATED_
MESSAGE
Warning
MSG_SDR_
UNEXPECTED_
EVENT
"SDR init %p"
Description
Major
MSG_SDR_INIT
MSG_SDR_
LOGICAL_ERROR
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Call Control and Feature Events
EventCode
C.2.5
Admain_anhang_C.fm
Tables
Event Templates
C-43
C-44
Description
no session object found
object could not be added
"Msg doesn't contain a CSID !"
Major
Major
MSG_SSM_NO_
CSID
MSG_SSM_
INVALID_PARAM
Parameter with invalid value
missing Call and Session ID
unanticipated Message
Tables
Event Templates
Invalid parameter %s, value %x"
"Session Payload: Unanticipated Message %s in state %s - EXCEP: %n%e"
"Session Payload: Missing Call and Ses- missing Call and Session ID
sion ID - EXCEP: %n%e"
"Session Payload: Object could not be

added - EXCEP: %n%e"
Automatic
Remedy Actions
Actions,
performed by
the Gateway
SCNPayloadObj could not be added
"Session Payload: Object could not be in- no memory left to instantiate a

stantiated - EXCEP: %n%e"
session payload object
"No session for Session Payload Object

found using CSID: %u - EXCEP: %n%e"
SCN Payload: Could not add SCN Payload Object - EXCEP: %n%e"
SCN Payload: Neither encoding could be neither encoding could be set

set for CSID: (%s) and ResID: (%u) - EXCEP: %n%e"
"SCN Payload: Could not set reverse en- could not set reverse encoding
coding to %i for CSID: (%s) and ResID:
(%u) - EXCEP: %n%e"
"SCN Payload: Could not set forward en- could not set forward encoding
coding to %i for CSID: (%s) and ResID:
(%u) - EXCEP: %n%e"
MSG_SPL_
Warning
UNANTICIPATED_
MESSAGE
Major
Major
MSG_SPL_
SESSION_NOT_
FOUND
MSG_SPL_
MISSING_CS_ID
Major
MSG_SCNP_
ADD_OBJECT_
FAILED
Major
Major
MSG_SCNP_
NEITHER_ENC_
COULD_BE_SET
MSG_SPL_ADD_
OBJECT_FAILED
Major
MSG_SCNP_
COULD_NOT_
SET_REV_ENC
Major
Major
MSG_SCNP_
COULD_NOT_
SET_FORW_ENC
MSG_SPL_NEW_
OBJECT_FAILED
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
Major
Information
MSG_MAND_
PARAM_MISSING
MSG_GF_GFT_
EVT_INIT_
SUCCESS
A31003-H3540-A800-1-7619, 2003-05-02
"GF: System startup message received"
Information
Critical
Critical
Critical
Cleared
MSG_GF_GFT_
EVT_STARTUP
MSG_GF_GFT_
EVT_NO_ASSOC
_SESOBJ
MSG_GF_GFT_
EVT_GFTOBJ_
NO_PARTNER
MSG_GF_GFT_
EVT_GFTOBJ_
NO_LINK
MSG_GF_GFT_
EVT_INCOMP_
TRANSP_STATE
not relevant for HXG3 - code will

be removed
Reboot the gateway.
Check route conguration of signalling source to destination.
"GF: Event %s incompatble with transport not relevant for HXG3 - code will
state %s"
be removed
"GF: Transport could not be linked to Ses- not relevant for HXG3 - code will
sion"
be removed
"GF: Partner Transport could not be instantiated"

be removed

be removed
GF: H.450-interworking platform unavail- Initialization of GenericFunctions

able! :(
failed; Probably Loadware error.
Not relevant for HXG3
MSG_GF_GFT_
Critical
EVT_INIT_FAILED
GF: No associated Session for new

Transport found
a CCP message could not be build from a message base, because a

mandatory parameter was missing
Probably a protocol loop was detected.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
inconsistent state of the software, e.g. invalid data
Description
"GF: H.450-interworking platform started not relevant for HXG3 - code will
:)"
be removed
"Mandatory parameter %s for construction of message missing"
Bad result from NWRS
Major
MSG_SSM_BAD_
NWRS_RESULT
"%p"
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
MSG_SSM_
Major
UNSPEC_ERROR
EventCode
Admain_anhang_C.fm
Tables
Event Templates
C-45
C-46
Information
Major
MSG_GF_GFT_
EVT_DISPOSE_
OF
MSG_GF_PROT_
ERROR
"MSG_GF_INT_ERROR"
MSG_GF_INT_
ERROR
Major
"GF Error: %p"
GF Protocol Error: protocol
"GF: H.450-interworking platform shutdown :|"
MSG_GF_ERROR Warning
Warning
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode

be removed

be removed
Incompatible ASN1 coded message received from LAN or SCN

port.
Not relevant for HXG3

be removed
Description
Replace incompatible components:

client, PBX, gateway.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Description
A31003-H3540-A800-1-7619, 2003-05-02
Warning
Information
MSG_ISDN_
CMR_
UNIMPLEMENTED
MSG_ISDN_
CMR_TIMER_
EXPIRED
A timer was expired.
EventLogEntry from
EventCode:
MSG_ISDN_CMR_TIMER_EXPIRED
EventText: %pTimer %s expired in state
%s
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Call leg object for session was not found.
EventLogEntry from
The requested feature is not imEventType: csevWarning
plemented.
EventCode:
MSG_ISDN_CMR_UNIMPLEMENTED
EventText: %pUnimplemented feature%s
EventLogEntry from
EventCode:
MSG_ISDN_CMR_OBJECT_NOT_
FOUND
EventText: %pThe object for Call and
Session ID %s could not be found
Critical
MSG_ISDN_
CMR_OBJECT_
NOT_FOUND
Mandatory elds are missing in

the message.
EventLogEntry from
Initialization of protocol manager
failed.
EventCode:
MSG_ISDN_CMR_INIT_FAILED
EventText: Initialization for protocol manager failed. %p
EventLogEntry from
EventCode:
MSG_ISDN_CMR_MAND_FIELDS_
MISSING
EventText: %pMandatory elds missing
(ID %s)
Warning
MSG_ISDN_
CMR_INIT_
FAILED
MSG_ISDN_
Warning
CMR_MAND_
FIELDS_MISSING
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
SCN Protocol Events
EventCode
C.2.6
Admain_anhang_C.fm
Tables
Event Templates
C-47
C-48
Warning
Critical
MSG_ISDN_
CMR_MSG_
DECODE_FAILED
MSG_ISDN_
CMR_NEW_
OBJECT_FAILED
Critical
Warning
MSG_ISDN_
CMR_WRONG_
DEVICE_TYPE
MSG_ISDN_
CMR_ADD_
OBJECT_FAILED
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Description
EventLogEntry from
Call leg object could not be linked EventType: csevCritical
to the protocol manager.
EventCode:
MSG_ISDN_CMR_ADD_OBJECT_
FAILED
EventText: %pThe object created for this
Call and Session ID could not be added to
the manager
Automatic
Remedy Actions
Actions,
performed by
the Gateway
EventLogEntry from
Creating call leg object for session EventType: csevCritical
failed.
EventCode:
MSG_ISDN_CMR_NEW_OBJECT_
FAILED
EventText: %pThe object for this Call and
Session ID could not be created
EventLogEntry from
Decoding of the message failed.
EventCode:
MSG_ISDN_CMR_MSG_DECODE_
FAILED
EventText: %pEvent decoding failed. %s
%s %nEvent data: %b
EventLogEntry from
Device type is invalid.
EventCode:
MSG_ISDN_CMR_WRONG_DEVICE_
TYPE
EventText: %p%Device Id %i is not a valid device type
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Information
Critical
Information
Critical
Information
EventCode
MSG_ISDN_
CMR_
UNEXPECTED_
EVENT
MSG_ISDN_
CMR_SESSION_
NOT_FOUND
MSG_ISDN_
CMR_STATUS_
MSG_RCVD
MSG_ISDN_
CMR_WRONG_
PROTVAR
MSG_ISDN_
CMR_GENRIC_
EVENT
Unexpected event was received.
Description
A31003-H3540-A800-1-7619, 2003-05-02
Generic event.
Protocol variant is invalid.
A STATUS message was received. -
Automatic
Remedy Actions
Actions,
performed by
the Gateway
EventLogEntry from
EventCode:
MSG_ISDN_CMR_GENRIC_EVENT
EventText: %p
EventLogEntry from
EventCode:
MSG_ISDN_CMR_WRONG_PROTVAR
EventText: %pProtocol Variant %i, Key
%x is not valid. Using default Timer Values !
EventLogEntry from
EventCode:
MSG_ISDN_CMR_STATUS_MSG_
RCVD
EventText: %pL3 Status message received in state %s
EventLogEntry from
Session object to call leg was not
found.
EventCode:
MSG_ISDN_CMR_SESSION_NOT_
FOUND
EventText: %pThe session object for this
Call and Session ID could not be found by
the manager
EventLogEntry from
EventCode:
MSG_ISDN_CMR_UNEXPECTED_
EVENT
EventText: %pReceived unexpected
event Message ID: %s
Admain_anhang_C.fm
Tables
Event Templates
C-49
C-50
EventLogEntry from
EventCode:
MSG_ISDN_RESOURCE_NOT_
AVAILABLE
EventText: %pResource not available,
Resource State %s
MSG_ISDN_
Critical
CMR_DEVICE_PT
R_BAD
Pointer to device object is null.
Tables
Event Templates
EventLogEntry from
EventCode:
MSG_ISDN_CMR_DEVICE_PTR_BAD
EventText: %pNull device pointer
EventLogEntry from
Device object could not be found.
EventCode:
MSG_ISDN_DEVICE_PTR_NOT_
FOUND
EventText: %pThe device ID could not be
found
MSG_ISDN_
DEVICE_PTR_
NOT_FOUND
Warning
EventLogEntry from
Resource is reserved by an other
call. (Call collision)
EventCode:
MSG_ISDN_RESOURCE_IN_USE_BY_
O_CALL
EventText: %pResource in use by other
call. Resource not released, Resource
State %s
Resource is not available.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Wrong resource state: resource is not in service.
Description
MSG_ISDN_
Information
RESOURCE_IN_
USE_BY_O_CALL
Information
MSG_ISDN_
RESOURCE_
NOT_AVAILABLE
EventLogEntry from
EventCode:
MSG_ISDN_RESOURCE_NOT_IN_
SERVICE
EventText: %pResource not in service,
Resource State %s
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
MSG_ISDN_
Information
RESOURCE_
NOT_IN_SERVICE
EventCode
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
EventLogEntry from
EventCode:
VALUE
EventText: %pUnexpected value for this
Device ID
Warning
MSG_ISDN_
CMR_
UNEXPECTED_
VALUE
Unexpected value for device id.
Unexpected error occurred.
EventLogEntry from
EventType: csevMinor
EventCode:
ERROR
EventText: %pUnexpected error
Minor
EventLogEntry from
Sending of message failed.
EventCode:
MSG_ISDN_CMR_MSG_SEND_FAILED
EventText: %pL3 Message sending failed
MSG_ISDN_
CMR_
UNEXPECTED_
ERROR
Critical
MSG_ISDN_
CMR_MSG_
SEND_FAILED
EventLogEntry from
Encoding of message failed.
EventCode:
MSG_ISDN_CMR_MSG_ENCODE_
FAILED
EventText: %pEvent encoding failed. %s
%s %nEvent data: %b
Description
EventLogEntry from
Segmented message error.
EventCode:
MSG_ISDN_CMR_SEG_MSG_ERROR
EventText: %pSegmented message error
Warning
MSG_ISDN_
CMR_MSG_
ENCODE_FAILED
MSG_ISDN_
Minor
CMR_SEG_MSG_
ERROR
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
C-51
C-52
Critical
Critical
MSG_ISDN_
CMR_WRONG_
INTERFACE
MSG_ISDN_
NULL_PTR
Critical
MSG_ISDN_
CMR_GEN_
CALL_REF_
FAILED
Warning
Warning
MSG_ISDN_
CMR_MSG_
UNEXPECTED
MSG_ISDN_
CMR_UNH_
STATE_EVENT
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
EventLogEntry from
EventCode:
MSG_ISDN_NULL_PTR
EventText: %p%p
Wrong interface type.
Null pointer was intended to use.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Generating of call reference failed. -
Message was unexpected in the

actual call state.
Description
EventLogEntry from
Event was not handled in the apEventType: csevWarning
propriate call state.
EventCode:
MSG_ISDN_CMR_UNH_STATE_EVENT
EventText: %pUnhandled event
EventLogEntry from
EventCode:
MSG_ISDN_CMR_WRONG_
INTERFACE
EventText: %pWrong interface type %s
EventLogEntry from
EventCode:
MSG_ISDN_CMR_GEN_CALL_REF_
FAILED
EventText: %pCould not generate a Call
Reference
EventLogEntry from
EventCode:
MSG_ISDN_CMR_MSG_
UNEXPECTED
EventText: %pUnexpected event
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
EventLogEntry from
EventCode:
MSG_ISDN_START_UP_ERROR
EventText: %s: Start up error. %p
Critical
Information
MSG_ISDN_
START_UP_
ERROR
MSG_ISDN_
START_UP
Start up done.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Error during start-up of ISDN protocols.
Message is erroneous.
Message was not conform to the

actual protocol.
No ISDN error.
ISDN error.
Description
EventLogEntry from
EventCode:
MSG_ISDN_START_UP
EventText: %s: Start up OK. %p
EventLogEntry from
EventCode:
MSG_ISDN_CMR_MESSAGE_ERROR
EventText: Message Error 0x%X
EventLogEntry from
EventCode:
MSG_ISDN_NO_ERROR
EventText: %pNo Error
MSG_ISDN_
Minor
CMR_MESSAGE_
ERROR
Information
MSG_ISDN_NO_
ERROR
EventLogEntry from
EventCode:
MSG_ISDN_ERROR
EventText: %pError: %p
EventLogEntry from
EventCode:
MSG_ISDN_CMR_PROTOCOL_
ERROR
EventText: Protocol Error: Device ID %d
Minor
MSG_ISDN_
ERROR
MSG_ISDN_
Warning
CMR_PROTOCOL
_ERROR
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Admain_anhang_C.fm
Tables
Event Templates
C-53
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Information
EventCode
MSG_ISDN_
OVERLOAD_
CONDITION
C-54
EventLogEntry from
EventCode:
MSG_ISDN_OVERLOAD_CONDITION
EventText: %pOverload Condition. SETUP received, RELEASE COMPLETE
sent
Overload condition: call cleared.
Description
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
Major,
Minor,
Warning,
Information
H323_INVALID_
POINTER
none
This pointers has got an invalid

value.
The current function call returns

an unexpected result.
The conguration for H.323 is

wrong.
none
none
none
Activate proper
H.323 analysis
trace prole and attach trace and
event log to error
report.
Activate proper
H.323 analysis
event log to error
report.
Activate proper
H.323 analysis
trace prole and attach trace, event
log and gateway
cong data to error
report.
Activate proper
H.323 analysis
event log to error
report.
Activate proper
H.323 analysis
event log to error
report.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
There is a parameter that exceeds none

the specied value range.
A parameter within a message

sent to the component H.323 is
missing.
Description
EventLogEntry from <Subsystem>

EventType: <Severity>
EventCode: H323_INVALID_POINTER
EventText:

EventCode:
H323_UNEXPECTED_RETURN_
VALUE
EventText:
Major,
Minor,
Warning

EventCode:
H323_INVALID_PARAMETER_VALUE
EventText:
H323_
UNEXPECTED_
RETURN_VALUE
Major,
Minor,
Warning
H323_INVALID_
PARAMETER_
VALUE

EventCode:
H323_MISSING_PARAMETER
EventText:

EventCode:
H323_INVALID_CONFIGURATION
EventText:
Major,
Minor,
Warning,
Information
H323_MISSING_
PARAMETER
H323_INVALID_
Major,
CONFIGURATION Warning
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
H.323 Events
EventCode
C.2.7
Admain_anhang_C.fm
Tables
Event Templates
C-55
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Information
Major,
Minor,
Warning
Major,
Warning,
Information
Major,
Minor,
Warning,
Information
Major,
Minor,
Warning,
Information
EventCode
H323_
INFORMATION
C-56
H323_
UNEXPECTED_
MESSAGE
H323_LOGIC_
ERROR
H323_STACK_
ERROR
H323_
PROTOCOL_
ERROR
none
none
An error occurred during a H.323

stack operation.
none
Activate proper
H.323 analysis
event log to error
report.
Activate proper
H.323 analysis
event log to error
report.
Activate proper
H.323 analysis
event log to error
report.
Activate proper
H.323 analysis
event log to error
report.
none
Automatic
Remedy Actions
Actions,
performed by
the Gateway
A logical error was detected during none

message processing.
H.323 received an unexpected

message.
This is for information purpose

only.
Description

A protocol information is missing / none
wrong.
EventCode: H323_PROTOCOL_ERROR
EventText:

EventCode: H323_STACK_ERROR
EventText:

EventCode: H323_LOGIC_ERROR
EventText:

EventCode:
H323_UNEXPECTED_MESSAGE
EventText:
EventLogEntry from
EventCode: H323_INFORMATION
EventText:
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Major
EventCode
H323_OSCAR_
NSD_ERROR

EventCode:
H323_OSCAR_NSD_ERROR
EventText:
This is an error related to the non

standard data.
Description
none
Activate proper
H.323 analysis
event log to error
report.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
Tables
Event Templates
C-57
C-58
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Major,
Warning,
Information
MSG_CAT_H235
H.235 Events
EventCode
C.2.8
EventLogEntry from
EventType: csev Information
EventCode: MSG_CAT_H235
EventText: H.235
.
Not relevant for HXG3.
H235 Security related events
Description
none
Verication of
H235 conguration in Gateway,
GK, clients
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Major
Cleared
Warning
MSG_IP_RTP_
QUALITY_
FAILURE
MSG_IP_RTP_
QUALITY_
FAILURE
MSG_IP_RTP_
QUALITY_
WARNING
RTPQM Events
EventCode
C.2.9
A31003-H3540-A800-1-7619, 2003-05-02
EventLogEntry from
EventCode:
MSG_IP_RTP_QUALITY_WARNING
EventText:
EventLogEntry from
EventCode:
MSG_IP_RTP_QUALITY_FAILURE
EventText:
EventLogEntry from
EventCode:
MSG_IP_RTP_QUALITY_FAILURE
EventText:
Call requests
for this destination will be
rejected. The
call is routed
over the SCN
network.
Check the packet

loss ratio for IP trafc to this destination.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
This is a warning that the LAN

quality gets worse. It is possible
that the route to that destination
will be blocked shortly.
Check the packet

loss ratio for IP trafc to this destination.
The blocking time for the specied Unblock IP ad- destination IP address is elapsed. dress for LAN
LAN calls to this destination can
calls.
be established again.
The LAN quality to the specied

destination IP address is classied
as too bad for voice calls. So all
further calls to that destination will
be routed over the SCN network.
Description
Admain_anhang_C.fm
Tables
Event Templates
C-59
C-60
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
GSA Events
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Major
Major
Major
MSG_BSD44_
VCAPI_NO_LIST
MSG_BSD44_
DGW_NO_LIST
MSG_BSD44_
ACCEPT_DGW_
ERR
DGW Events
EventCode
C.2.11
MSG_GSA_SNMP Critical
EventCode
C.2.10
Description
Critical error for GSA, generate

SNMP Trap msg.
Description
Not possible to create a listening

socket for DATAGWI.
LAN trafc not possible.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Trap
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Tables
Event Templates
EventLogEntry from
Not possible to set up a new conEventType: : csevMajor
nection for DATAGW
EventCode:
MSG_BSD44_ACCEPT_DGW_ERR
EventText: accept error for DATAGW Dispatcher
EventLogEntry from
EventCode:
MSG_BSD44_DGW_NO_LIST
EventText: No listening socket for DATAGW
EventLogEntry from
Not possible to create a listening
socket for VCAPI.
EventCode:
LAN trafc not possible.
MSG_BSD44_VCAPI_NO_LIST
EventText: No listening socket for VCAPI
EventLogEntry from
EventType: csev information
EventCode: MSG_GSA_SNMP
EventText: %p
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
Minor
Minor
MSG_DGW_
WRONG_STATE
MSG_DGW_
MSG_IGNORED
Message ignored because DGWDispatcher in wrong state.
Wrong state for DATAGW Dispatcher
Connection ID exceeds the max

allowed channels
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Client can not connect to the server
Client can not bind a socket
Client can not retrieve a socket.
Description
EventLogEntry from
EventType: : csevMinor
EventCode:
MSG_DGW_MSG_IGNORED
EventText: %s from CAPI_PAYLOAD_IF
ignored!
EventLogEntry from
EventCode:
MSG_DGW_WRONG_STATE
EventText: dg_capi_HandleCapi20Msg:
id=%d wrong state!
EventLogEntry from
EventCode:
MSG_DGW_CONN_OUT_OF_RANGE
EventText: dg_capi_HandleCapi20Msg:
connection_id=%d out of range!
Major
EventLogEntry from
EventCode:
MSG_BSD44_DGW_BIND_FAIL
EventText: DGW bind() failed
MSG_DGW_C
ONN_OUT_OF_
RANGE
Minor
MSG_BSD44_
DGW_BIND_FAIL
EventLogEntry from
EventType: : csevMinor
EventCode:
MSG_BSD44_DGW_SOCKET_FAIL
EventText: DGW socket() failed
EventLogEntry from
EventCode:
MSG_BSD44_DGW_CONNECT_FAIL
EventText: DGW connect() failed
Minor
MSG_BSD44_
DGW_SOCKET_
FAIL
MSG_BSD44_
Minor
DGW_CONNECT_
FAIL
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Admain_anhang_C.fm
Tables
Event Templates
C-61
C-62
Major
Major
MSG_DGW_
DISC_B3_IND
MSG_DGW_
ALLOC_DISC_B3
MSG_DGW_
Major
DATA_B3_ALLOC_
ERR
Minor
Major
MSG_DGW_
CONN_B3_ACT_
IND
MSG_DGW_
UNHANDLED_
MSG
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Description
EventLogEntry from
EventCode:
MSG_DGW_DATA_B3_ALLOC_ERR
EventText:DATAB3_REQ:ALLOC ERROR: returncode %x
Can not allocate a buffer to send

CMT_DATA_REQ to
CAPI_PAYLOAD_IF
EventLogEntry from
Unknown message from
CAPI_PAYLOAD_IF to DGW-DisEventCode:
patcher
MSG_DGW_UNHANDLED_MSG
EventText: unhandled %s msg=%d from
CAPI_PAYLOAD_IF
EventLogEntry from
DGW_FREE_REQ
EventCode:
MSG_DGW_ALLOC_DISC_B3
EventText:
CAPI2_DISCONNECTB3_IND(2) dreadful!: no more buffers
EventLogEntry from
DGW_CLOSE_REQ
EventCode: MSG_DGW_DISC_B3_IND
EventText:
CAPI2_DISCONNECTB3_IND dreadful!:
no more buffers
EventLogEntry from
CONNECT_B3_ACTIVE_
EventCode:
RESPONSE
MSG_DGW_CONN_B3_ACT_IND
EventText: ALLOC error: no more buffers
reboot
reboot
reboot
reboot
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Minor
Minor
Major
Major
Minor
EventCode
MSG_DGW_
ALLOC_REQ_
ERR
MSG_DGW_
ALLOC_CONF_
ERR
MSG_DGW_
FREE_ALLOC_
ERR
MSG_DGW_
UNKNOWN_
PRIMITIVE
MSG_DGW_
RECEIVE_ERR
Description
A31003-H3540-A800-1-7619, 2003-05-02
-
Unknown message from

CAPI_PAYLOAD_IF to DGW-Dispatcher
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Not possible to allocate a buffer to reboot

send DISCONNECT_B3_REQ
DGW-Dispatcher in wrong state

when receiving
DGW_ALLOC_CONF
EventLogEntry from
Receive error
EventCode:
MSG_DGW_RECEIVE_ERR
EventText: Error while receiving message
for DATAGW-Dispatcher:Returncode %x
EventLogEntry from
EventCode:
MSG_DGW_UNKNOWN_PRIMITIVE
EventText: DG: unknown capi primitive:
%x
EventLogEntry from
EventCode:
MSG_DGW_FREE_ALLOC_ERR
EventText: DGW_FREE_REQ: allocb
failed!
EventLogEntry from
EventCode:
MSG_DGW_ALLOC_CONF_ERR
EventText: DGW_ALLOC_CONF id=%d
received in wrong state!
EventLogEntry from
DGW-Dispatcher in wrong state
when receiving
EventCode:
DGW_ALLOC_REQ
MSG_DGW_ALLOC_REQ_ERR
EventText: DGW_ALLOC_REQ received
in wrong state!
Admain_anhang_C.fm
Tables
Event Templates
C-63
C-64
Major
Major
MSG_DGW_IND_
ALLOC_ERR
MSG_DGW_
CONF_ALLOC_
ERR
EventLogEntry from
Not possible to allocate a buffer for reboot
CMT_DATA_CONF
EventCode:
MSG_DGW_CONF_ALLOC_ERR
EventText: Not possible to allocate a buffer for CMT_DATA_CONF
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Not possible to nd connection ID because of wrong PLCI
Unhandled event received by

DGW-Dispatcher
Description
EventLogEntry from
CMT_DATA_IND
EventCode:
MSG_DGW_IND_ALLOC_ERR
EventText: Not possible to allocate a buffer for CMT_DATA_IND
EventLogEntry from
EventCode: MSG_DGW_NO_PLCI
EventText: Find connection ID by PLCI:PLCI %d not found
Warning
MSG_DGW_NO_
PLCI
EventLogEntry from
EventCode:
MSG_DGW_UNHANDLED_EVENT
EventText: Unhandled event for DGWDispatcher,received event:%d
EventLogEntry from
EventCode:
MSG_DGW_WRONG_EVENT_CAPI20
EventText: wrong eventcode from
CAPI20-Mgr
Warning
MSG_DGW_
UNHANDLED_
EVENT
MSG_DGW_
Warning
WRONG_EVENT_
CAPI20
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
Major
Minor
Minor
MSG_DGW_
ALLOC_CHN_
CONN_FAIL
MSG_DGW_
OPEN_CHN_
UNKNOWN_ID
MSG_DGW_
OPEN_CHN_
WRONG
Too many connections
wrong eventcode from

CAPI_PAYLOAD_INTERFACE
Description
EventLogEntry from
EventCode:
MSG_DGW_OPEN_CHN_WRONG
EventText:
OPEN_CHANNEL_REQ:dreadful!:
wrong state
Wrong state for message

OPEN_CHANNEL_REQ
EventLogEntry from
Connection ID not found by using
channel_id
EventCode: MSG_DGW_OPEN_CHN_
UNKNOWN_ID
EventText: OPEN_CHANNEL_REQ: unknown id
EventLogEntry from
Not possible to set up a new conEventType: csevMajor
nection to the server
EventCode:
MSG_DGW_ALLOC_CHN_CONN_FAIL
EventText:
ALLOC_CHANNEL_REQ:connect failed
EventLogEntry from
EventCode:
MSG_DGW_ALLOC_CHN_RUN_OUT
EventText: ALLOC_CHANNEL_REQ:
run out of connection handles
Minor
MSG_DGW_
ALLOC_CHN_
RUN_OUT
EventLogEntry from
EventCode:
MSG_DGW_WRONG_EVENT_CAPI
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
MSG_DGW_
Warning
WRONG_EVENT_
CAPI
EventCode
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
C-65
C-66
EventLogEntry from
EventCode:
MSG_DGW_FREE_CHN_ALLOC_FAIL
EventText: FREE_CHANNEL_REQ : Alloc failed
Second ALLOC for
FREE_CHANNEL_REQ
failed.Not possible to send
DGW_FREE_REQ
ALLOC for
FREE_CHANNEL_REQ
failed.Not possible to send
DISCONNECT_B3_REQ
reboot
reboot
EventLogEntry from
Unknown message from CAPI20- EventType: csevWarning
Mgr
EventCode:
MSG_DGW_UNH_MSG_CAPI20_MGR
EventText: unhandled message %d from
CAPI20-Mgr
Major
MSG_DGW_
FREE_CHN_
ALLOC_FAIL
EventLogEntry from
FREE_CHANNEL_REQ with unEventType: csevMajor
known ID
EventCode:
MSG_DGW_FREE_UNKNOWN_ID
EventText: FREE_CHANNEL_REQ : unknown connection_id

DGW_OPEN_CONFIRM
Automatic
Remedy Actions
Actions,
performed by
the Gateway
MSG_DGW_UNH_ Warning
MSG_CAPI20_
MGR
Major
MSG_DGW_
FREE_
UNKNOWN_ID
EventLogEntry from
EventCode:
MSG_DGW_OPEN_CHN_ALLOC_FAIL
EventText: OPEN_CHANNEL_REQ:Alloc failed
Description
EventLogEntry from
EventCode:
MSG_DGW_SEC_ALLOC_FAIL
EventText: FREE_CHANNEL_REQ :
second Alloc failed
Major
MSG_DGW_
OPEN_CHN_
ALLOC_FAIL
MSG_DGW_SEC_ Major
ALLOC_FAIL
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Minor
Major
Major
Minor
Major
EventCode
MSG_DGW_
UNKNOWN_ID_
CHANNEL
MSG_DGW_
FREE_NOT_
SEND
MSG_DGW_
DISC_B3_NOT_
SEND
MSG_DGW_
SOCKET_
UNKNOWN
MSG_DGW_
CONNECT_
FAILED
Description
A31003-H3540-A800-1-7619, 2003-05-02
SO_NTFY_CONN_
COMPLETE:
error! ret= %d!
Connection error
Alloc error: reboot
SO_NTFY_CONN_
COMPLETE:
unknown socket!
Connection will be closed
DISCONNECT_B3_
REQUEST not sent
Alloc error:
reboot
DGW_FREE_REQUEST not sent
Automatic
Remedy Actions
Actions,
performed by
the Gateway
EventLogEntry from
EventCode:
MSG_DGW_CONNECT_FAILED
EventText:
SO_NTFY_CONN_COMPLETE: error!
ret= %d!
EventLogEntry from
EventCode:
MSG_DGW_SOCKET_UNKNOWN
EventText:
SO_NTFY_CONN_COMPLETE: unknown socket!
EventLogEntry from
EventCode:
MSG_DGW_DISC_B3_NOT_SEND
EventText: Alloc error:
DISCONNECT_B3_REQUEST not
sent
EventLogEntry from
EventCode:
MSG_DGW_FREE_NOT_SEND
EventText:
Alloc error: DGW_FREE_REQUEST not
sent
EventLogEntry from
Connection ID can not be found
using channel_ID
EventCode:
MSG_DGW_UNKNOWN_ID_CHANNEL
EventText:
nd_conn_id_by_chn_id: unknown id %d
Admain_anhang_C.fm
Tables
Event Templates
C-67
C-68
EventLogEntry from
EventCode:
MSG_DGW_MGR_NOT_READY
EventText:SO_NTFY_CONNECTION:
CAPI20Mgr not
ready:DGW_Disp_State=0x%x
EventLogEntry from
Data can not be received because EventType: csevMinor
of unknown socket
EventCode:
MSG_DGW_RCV_SOCK_UNKN
EventText: SO_NTFY_RCV_SDATA: unknown socket
MSG_DGW_RCV_ Minor
SOCK_UNKN
Send not possible because of

socket unknown
reboot
Tables
Event Templates
Automatic
Remedy Actions
Actions,
performed by
the Gateway
EventLogEntry from
EventCode:
MSG_DGW_BUFAVAIL_SOCK_UNKN
EventText: SO_NTFY_BUFAVAIL: unknown socket
SO_NTFY_CONNECTION:
CAPI20Mgr not
ready:DGW_Disp_State=0x%x
Start Operation message from
CAPI20-Mgr not received
Too much connections
SO_NTFY_CONN_
COMPLETE:
Alloc failed
No DGW_ALLOC_REQUEST to
remote
Description
MSG_DGW_
Minor
BUFAVAIL_SOCK_
UNKN
Warning
MSG_DGW_
MGR_NOT_
READY
EventLogEntry from
EventCode:
MSG_DGW_CONN_COMPL_ALLOC
EventText:
SO_NTFY_CONN_COMPLETE:
Alloc failed
EventLogEntry from
EventCode:
MSG_DGW_CONN_RUN_OUT
EventText: SO_NTFY_CONNECTION:
run out of connection handles:cnt=%d
Major
MSG_DGW_
CONN_COMPL_
ALLOC
MSG_DGW_
Warning
CONN_RUN_OUT
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
EventLogEntry from
EventCode: MSG_DGW_RCV_FAILED
EventText: recv() failed, id=%d
EventLogEntry from
Message with wrong length reEventType: csevMinor
ceived from remote
EventCode: MSG_DGW_INV_MSG_LEN
EventText: invalid message lenght: %d
MSG_DGW_RCV_ Minor
FAILED
MSG_DGW_INV_
MSG_LEN
EventLogEntry from
EventCode:
MSG_DGW_MSG_RCV_FAIL
EventText: recv() failed, id=%d
MSG_DGW_
MSG_RCV_FAIL
Minor
EventLogEntry from
EventCode:
MSG_DGW_RCV_ALLOC_FAIL
EventText: FATAL: allocb() failed, id=%d
MSG_DGW_RCV_ Major
ALLOC_FAIL
Minor
EventLogEntry from
EventCode:
MSG_DGW_UNKNOWN_NOTIFIC
EventText: Unknown notication 0x%x
Minor
MSG_DGW_
UNKNOWN_
NOTIFIC
Not possible to receive a message -
Not possible to allocate a receive- reboot

buffer
Data are not received properly
Unknown notication
Automatic
Remedy Actions
Actions,
performed by
the Gateway
EventLogEntry from
Connection can not be closed be- EventType: csevMinor
cause of unknown socket
EventCode:
MSG_DGW_ABORT_SOCK_UNKN
EventText: SO_NTFY_ABORT: unknown
socket
Minor
Description
MSG_DGW_
ABORT_SOCK_
UNKN
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Admain_anhang_C.fm
Tables
Event Templates
C-69
C-70
Minor
MSG_DGW_
SEND_FAILED
wrong data length received from

remote
Wrong length received from remote
Description
EventLogEntry from
EventCode:
MSG_DGW_SOCKET_NOT_OPEN
EventText: DGW-Socket not opened
Major
Major
MSG_DGW_
SOCKET_NOT_
OPEN
MSG_DGW_
SOCKET_BIND_
ERR
EventLogEntry from
EventCode:
MSG_DGW_SOCKET_BIND_ERR
EventText: bind error for DGW
socket %d
EventLogEntry from
EventCode:
MSG_DGW_SEND_DATA_ERR
EventText: send() data failed, id=%d
MSG_DGW_
Minor
SEND_DATA_ERR
bind error for DGW socket

no connections possible
DGW-Socket not opened

Not possible to send data to remote
EventLogEntry from
Not possible to send message to
remote
EventCode: MSG_DGW_SEND_FAILED
EventText: send() failed, id=%d
EventLogEntry from
EventCode:
MSG_DGW_INV_DATA_LEN
EventText: invalid data lenght:%d
Minor
MSG_DGW_INV_
DATA_LEN
EventLogEntry from
EventCode:
MSG_DGW_INVALID_LENGTH
EventText: invalid lenght:%d %s
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
MSG_DGW_
Minor
INVALID_LENGTH
EventCode
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Major
Minor
EventCode
MSG_DGW_
LISTENING_ERR
MSG_DGW_
ACCEPT_FAILED
Description
EventLogEntry from
EventCode:
MSG_DGW_ACCEPT_FAILED
EventText: so_accept() failed
No new connection accepted
EventLogEntry from
listening error for DGW socket
EventCode:
MSG_DGW_LISTENING_ERR
EventText: listening error for DGW socket
%d
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
C-71
C-72
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Minor
Minor
Minor
Critical
Critical
Minor
MSG_CAR_
GENERAL_
ERROR
MSG_CAR_NO_
MEMORY
MSG_CAR_FKT_
GET_IPADR_
FAILED
MSG_CAR_
START_TCP_
LISTENER_
FAILED
MSG_CAR_
SENDING_
UPDATE_
REQUEST_
FAILED_SOH_
ERROR
MSG_CAR_
SENDING_
UPDATE_
REQUEST_
FAILED_NO_
MEMORY
CAR Events
EventCode
C.2.12
Car_fkt_get_ipadr returns an unsuccessful result due to the fact

that mat_allocb cannot reserve
any memory anymore
CAR : there is no more memory

available.
A general error occurred in the

subsystem CAR.
Description
None
None
None
CAR : SOH : start update failed due to

lack of memory
CAR : SOH : sending update request

failed : returncode
soh_api_send_tcp_data = %d
CAR : SOH : start update failed

due to lack of memory
None
soh_api_send_tcp_data returns
None
an incorrect value. The sending of
the update request failed.
None
None
None
None
None
None
Automatic
Remedy Actions
Actions,
performed by
the Gateway
CAR : SOH : start of TCP listener failed : soh_api_start_tcp_listener returns None

returncode soh_api_start_tcp_listener = an incorrect value. The start of the
%d
TCP listener failed.
CAR : car_fkt_get_ipadr result unsuccessful due to lack of memory

(mat_allocb)
CAR : no more memory available
CAR : General error : %s
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
Minor
Major
Minor
Major
Information
MSG_CAR_
UPDATE_
NUMBER OF
ENTRIES_
CALLADDRTAB_
TOO_BIG
MSG_CAR_SOH_
MESSAGE_NOT_
FROM_VENUS
MSG_CAR_DB_
READ_NODE_
TABLE_ERROR
MSG_CAR_
ALIVE_IP_
CONNECTION_
LOST
MSG_CAR_
ALIVE_IP_
CONNECTION_
OK_AGAIN
MSG_CAR_
Minor
ERROR_WITH_
OAM_INTERFACE
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
CAR: Alive : ip connection ok

again
CAR : Alive : ip connection lost
CAR : An error occurred with the OAM in- CAR : An error occurred with the
terface RC = %d
OAM interface
CAR: Alive : ip connection

%d.%d.%d.%d ok again
CAR : Alive : ip connection

%d.%d.%d.%d lost
None
None
None
None
CAR : SOH : received message is None

not from the Venus server.
None
None
None
None
None
None
Automatic
Remedy Actions
Actions,
performed by
the Gateway
CAR : SOH : the number of entries None

received by the update is too big.
Possible SOH error.
Description
CAR : DB : Read of Node Table failed : ta- CAR : DB : Read of Node Table
ble index = %d
failed
CAR : SOH : received message is not

from the Venus server. Received IP address = 0x%x
CAR : SOH : update data : number of

CallAddressEntries = %d too big
Admain_anhang_C.fm
Tables
Event Templates
C-73
C-74
"REG : No registration possible (no response)"
Major
MSG_REG_NO_
REGISTRATION_
POSSIBLE
None
None
REG : NIL pointer received from

SOH
REG : REG request within registration
"REG : No registration possible

(no response)"
None
REG : SOH : Unknown event from None

SOH
None
None
None
None
None
None
None
None
None
None
None
Automatic
Remedy Actions
Actions,
performed by
the Gateway
REG : SOH : send data failed : the None

routine soh_api_send_tcp_data
returned an incorrect returncode.
REG : no more memory
REG : global error
Description
REG : SOH : Error from SOH : errorcode REG : SOH : Error from SOH
= 0x%x
REG : SOH : Unknown event from SOH
0x%x
Critical
MSG_REG_SOH_ Minor
UNKNOWN_
EVENT_FROM_
SOH
MSG_REG_
ERROR_FROM_
SOH
Critical
MSG_REG_NIL_
PTR_FROM_SOH
REG : NIL pointer received from SOH :

Pointer = 0x%x
REG : REG request within registration "
Minor
REG : No more memory available
MSG_REG_
REQUEST_
WITHIN_
REGISTRATION
Minor
MSG_REG_NO_
MEMORY
REG : Global error : %s
REG : SOH : send data failed : returncode soh_api_send_tcp_data = %d
Minor
MSG_REG_
GLOBAL_ERROR
MSG_REG_SOH_ Critical
SEND_DATA_
FAILED
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
REG Events
EventCode
C.2.13
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Warning
Major
Warning
Major
Major
Major
Major
Minor
Major
MSG_NU_
GENERAL_
ERROR
MSG_NU_
TRANSPCONT_
MISSING
MSG_NU_NO_
FREE_
TRANSACTION
MSG_NU_
INVALID_CIDL
A31003-H3540-A800-1-7619, 2003-05-02
MSG_NU_CAR_
FAILED
MSG_NU_
CAR_RESP_
INVALID
MSG_NU_
UNEXPECTED_
MSG
MSG_NU_
UNEXPECTED_
TIMER
MSG_NU_FREE_
CHN_
UNEXPECTED
None
None
None
None
Free channel unexpected in certain NU state
Unexpected timer event in a certain NU state
None
None
Unexpected message in certain

None
NU state with event and message
type
Invalid Response from CAR: value None

shown
None
None
None
None
None
None
None
None
None
None
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Call to CAR function failed. Wrong None

return code came back.
The CIDL send along in the message is invalid.
No free transaction store found in

a function
Transport container missing
Only as a temporary dummy.
Description
Free channel conrmation too late State: Free channel conrmation from
None
%d
the NU Leg Control too late in certain NU state
Free channel unexpected: State: %d
Timer unexpected: State: %d, Subind:0x%x
Unexpected message: State:%d,

Event:0x%x, Msgtype:0x%x
Invalid Response from CAR: 0x%x "
Call to CAR function failed
CIDL invalid
No free transaction store found in %s
Transport container missing
General error %s
MSG_NU_
Major
FREE_CHN_
CONF_TOO_LATE
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
NU Events
EventCode
C.2.14
Admain_anhang_C.fm
Tables
Event Templates
C-75
C-76
Warning
Minor
Critical
Minor
MSG_NU_TOO_
MUCH_DIGITS
MSG_NU_TCP_
LISTENER_FAILE
D
MSG_NU_SOH_
RESP_INVALID
Minor
MSG_NU_
SUPERFLUOUS_
MSG
MSG_NU_
INTERNAL_
ERROR
Major
MSG_NU_NO_
PORT_DATA
Minor
Warning
MSG_NU_
UNEXPECTED_
SETUP
MSG_NU_
UNKNOWN_MSG
Major
MSG_NU_
WRONG_CALL_
REF
Minor
Minor
MSG_NU_
EVENT_
EXCEPTION
MSG_NU_IP_
ERROR
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Description
No data for a port found in a certain function.
Unexpected SETUP on active

transaction in certain NU state.
Might be caused by glare situations
None
None
Wrong call reference from system None

or LAN.
None
SOH call back response invalid.

Event:0x%x, Reason:%s
None
None
None
None
Parameters returned in the Socket None

Handler call back function invalid
or SOH error
The Socket Handler couldnt start None

a listener function
Too much digits send at a time
NU Internal software error
Unknown message sent to NU
IP error
None
None
None
None
None
None
Tables
Event Templates
Start_tcp_listener failed
Too much digits send at a time
NU internal error: %s
Unknown message: Event:0x%x, Channel:%d
IP Error: IPAddress:0x%x, Error: 0x%x
None
None
None
None
None
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Superuous message: Event:0x%x, Lw- Superuous message send to NU. None

port:%d, Channel:%d, Data:0x%x
Might be caused by asynchronous
behaviour of the two nodes
No data for port_%d found in %s
Unexpected SETUP: State:%d, Lwport/

IPAddr:0x%x, CR:%d, Direction:%d
Wrong Call Reference. Event: 0x%x
Event exception: State: %d, Event:0x%x, Event exception in a certain NU

Data:0x%x
state
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
MSG_NU_DEV_
Major
TAB_NOT_FOUND
EventCode
Device table not found
None
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Access to the device table not OK. None
Description
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
Tables
Event Templates
C-77
C-78
EventlogEntry from
EventText: %s
Successful startup or shutdown of display

application
display
Information
Internal error in NU Leg Control
MSG_NULC_
INTERNAL_
EVENT
display
EventlogEntry from
EventText: %s
Mandatory parameter missing or

having not a valid value
Major
EventlogEntry from
EventText: Missing/not valid parameter
%s in message %s
%s = name of either parameter or message
Received unexpected or unknown display

message
Automatic
Remedy Actions
Actions,
performed by
the Gateway
MSG_NULC_
INTERNAL_
ERROR
Major
MSG_NULC_
PARAM_ERROR
EventlogEntry from
EventText: Unexpected message ID or
eventcode (%x)
%x = message type
Description
EventlogEntry from
Application doesnt get requested display
memory or any other operation reEventText: Can't access to/allocate mem- turns null pointer
ory
Warning
MSG_NULC_
MESSAGE_
ERROR
MSG_NULC_
Major
MEMORY_ERROR
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
NU Leg Control Events
EventCode
C.2.15
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Major
Major
Major
Major
Major
Major
MSG_HFAM_
HAH_ALLOC_
CHAN_ERR
MSG_HFAM_
HAH_ALLOC_
CONF_ERR
MSG_HFAM_
HAH_OPEN_
CHAN_ERR
A31003-H3540-A800-1-7619, 2003-05-02
MSG_HFAM_
HAH_OPEN_
CONF_ERR
MSG_HFAM_
MAIN_UNEXP_
LWEVENT_ERR
MSG_HFAM_
MAIN_ILLEG_
PORTNO_ERR
Illegal port no with event code
unknown/unexpected event code

received: lw_event
display
display
HFAM_OPEN_CHANNEL_CONF display
received from client that is not in
opening state
Check system
System side error

DH / CP
HFAA error
HFAM internal
HFAA error
EventlogEntry from
EventText: "Illegal port no with event
code"
EventlogEntry from
EventText: "unknown/unexpected event
code received: lw_event"
EventlogEntry from
EventText:
"HFAM_OPEN_CHANNEL_CONF received from client that is not in opening
state"
display
HFAM_ALLOCATE_CHANNEL_C display
ONF received from client that is
not in allocating or opening state
HFAM internal
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Tried to allocate channel for client display

that is not in idle state
Description
EventlogEntry from
Tried to open connection to client
which was not allocating_in, alloEventText: "Tried to open connection to
cated or open state
client which was not allocating_in, allocated or open state"
EventlogEntry from
EventText:
"HFAM_ALLOCATE_CHANNEL_CONF
received from client that is not in allocating or opening state"
EventlogEntry from
EventType: csev Major
EventText: "Tried to allocate channel for
client that is not in idle state"
HFA Manager Events
EventCode
C.2.16
Admain_anhang_C.fm
Tables
Event Templates
C-79
C-80
Major
MSG_HFAM_LIH_
ACCEPT_
CLIENT_CON_
ERR
Critical
MSG_HFAM_LIH_
BIND_
REGISOCK_ERR
Critical
Critical
MSG_HFAM_LIH_
SOCK_REUSE_
ADR_ERR
MSG_HFAM_LIH_
ACCEPT_TCPIP_
CON_ERR
Critical
MSG_HFAM_LIH_
CREATE_
REGISOCK_ERR
Critical
Major
MSG_HFAM_
MAIN_NO_
LOGONTIMER_
ERR
MSG_HFAM_LIH_
LISTEN_
REGISOCK_ERR
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Description
EventlogEntry from
Connection from client not accept- display
ed
EventText: "connection from client not accepted"
EventlogEntry from
Could not accept TCP/IP connec- display
tion from client
EventText: "Could not accept TCP/IP connection from client"
display
Could not bind registration socket display
Could not set socket option reuse display

address'
Could not create registration sock- display

et
EventlogEntry from
Could not listen at registration
socket
EventText: "Could not listen at registration
socket"
EventlogEntry from
EventText: "Could not bind registration
socket"
EventlogEntry from
EventText: "Could not set socket option
reuse address'"
EventlogEntry from
EventText: "Could not create registration
socket"
LAN side error

Check client setup
LAN side error

Check client setup
LAN side error
LAN side error
LAN side error
LAN side error
HFAM intern
Automatic
Remedy Actions
Actions,
performed by
the Gateway
EventlogEntry from
No logon timer started for that cli- display
ent
EventText: "No logon timer started for that
client
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Critical
Major
Minor
Minor
Minor
Major
Major
Major
EventCode
MSG_HFAM_LIH_
MAX_CON_
EXCEED_ERR
MSG_HFAM_LIH_
ACCEPT_
INETOA_CON_
ERR
MSG_HFAM_LIH_
SOCK_
WOULDBLOCK_
ERR
MSG_HFAM_LIH_
TCDATAGRAM_
RCV_ERR
A31003-H3540-A800-1-7619, 2003-05-02
MSG_HFAM_LIH_
UNEXP_
CORNET_ERR
MSG_HFAM_LIH_
IPADR_TOO_
LONG_ERR
MSG_HFAM_LIH_
SUBNO_TOO_
LONG_ERR
MSG_HFAM_LIH_
ALGORITM_
OBJID_ERR
display
display
EventlogEntry from
Algorithm Object-ID too long, cut ! display
EventText: "Algorithm Object-ID too long,
cut !"
Subscriber number too long, cut !
IP-address too long, cut !
display
TC_DATAGRAM received from cli- display

ent->subscriber_no while not in
logged_in state, discarded
Check client setup
Check client setup
Check client setup
Check client
LAN side error

Check Client setup
LAN side error
LAN side error

Check client setup
HFAM internal
EventlogEntry from
EventText: "SubNo too long, cut !"
EventlogEntry from
EventText: "IP-address too long, cut !"
display
display
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Socket would block: keine Daten - display

> ignorieren
Cannot accept connection from

client
max no
(HFAM_MAX_CONNECTIONS)
of TCP/IP connections exceeded
Description
EventlogEntry from
unknown/unexpected Cornet-TS
message received from client
EventText: "unknown/unexpected CornetTS message received from client"
EventlogEntry from
EventText: "TC_DATAGRAM received
from client->subscriber_no while not in
logged_in state, discarded"
EventlogEntry from
EventText: "Socket would block: keine
Daten -> ignorieren"
EventlogEntry from
EventText: " Cannot accept connection
from client
EventlogEntry from
EventText: "max
no.(HFAM_MAX_CONNECTIONS) of
TCP/IP connections exceeded"
Admain_anhang_C.fm
Tables
Event Templates
C-81
C-82
EventlogEntry from
EventText: "No monitor timer !"
Minor
Minor
Major
MSG_HFAM_
MON_NO_MON_
TIMER_ERR
MSG_HFAM_
REG_LOGIN_
NOTREG_ERR
MSG_HFAM_
REG_SUBNO_
TOO_LONG_ERR
display
display
DL_LOGON_IN received for client display

not in not_registered state
No monitor timer !
display
display
display
display
Check client setup

in system
HFAM internal
HFAM init
System side error
System side error
HFAM init
LAN side error
Tables
Event Templates
EventlogEntry from
SubNo in DL_LOGON_IN too
long, cut:
EventText: " DL_LOGON_IN received for
client not in not_registered state "
EventlogEntry from
EventText: "DL_LOGON_IN received for
client not in not_registered state, subno"
EventlogEntry from
cannot synthesize CorNet-TS
message longer than 28 bytes
EventText: "cannot synthesize CorNet-TS
message longer than 28 bytes"
MSG_HFAM_SIH_ Major
CORNET_
LONGER_28_ERR
Input parameter for

hfam_sih_send_ts invalid
Login timer for client could not be

started!
returned socket error
EventlogEntry from
EventText: "Input parameter for
hfam_sih_send_ts invalid"
EventlogEntry from
EventText: "returned socket error"
MSG_HFAM_SIH_ Major
INVAL_TSLOT_
PARAM_ERR
Major
MSG_HFAM_LIH_
RETURNED_
SOCKET_ERR
Check client setup
Automatic
Remedy Actions
Actions,
performed by
the Gateway
EventlogEntry from
too many elements in protocol list display
EventText: "too many elements in protocol
list"
Description
EventlogEntry from
EventText: "timeslot is valid"
Major
MSG_HFAM_LIH_
PROTOCOL_
LIST_ERR
MSG_HFAM_SIH_ Major
NO_LOGIN_
TIMER_ERR
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Minor
Minor
Minor
Minor
Information
Minor
EventCode
MSG_HFAM_
REG_SUBNO_
NOTCONFIG_
ERR
MSG_HFAM_
REG_ESTAB_
NOTREG_ERR
MSG_HFAM_
REG_RELIN_
NOTREG_ERR
MSG_HFAM_
REG_MISSING_
L2INFO_ERR
A31003-H3540-A800-1-7619, 2003-05-02
MSG_HFAM_
REG_LOGON_
REJECT_ERR
MSG_HFAM_
REG_INVAL_
PWD_LEN_ERR
EventlogEntry from
EventText: "invalid password length of
<sub_number>, no hash"
EventlogEntry from
EventText: "logon of client>subscriber_no rejected"
EventlogEntry from
EventText: "missing L2addr-InfoElem, no
IP address"
EventlogEntry from
EventText: "DL_REL_IN arrived for client
not in registered state"
EventlogEntry from
EventText: "DL_EST_IN arrived for client
not in registered state"
EventlogEntry from
EventText: " SubNo from System I/F not
found in cong data "
display
invalid password length of

<sub_number>, no hash
display
logon of client->subscriber_no re- display

jected
missing L2addr-InfoElem, no IP
address
DL_REL_IN arrived for client not in display

registered state
DL_EST_IN arrived for client not in display

registered state
Invalid client setup

in system or WBM
Check client setup
Check client setup
Check system setup or WBM
Check system setup or WBM
Check client setup

in system
Automatic
Remedy Actions
Actions,
performed by
the Gateway
SubNo from System I/F not found display

in cong data
Description
Admain_anhang_C.fm
Tables
Event Templates
C-83
C-84
Mandatory parameter missing or
having not a valid value
display
MSG_HFAA_
INTERNAL_
EVENT
Information
Major
EventlogEntry from
EventText: %s
Successful startup or shutdown of display

application
Other internal error in HFA Adapt- display

er
EventlogEntry from
EventText: %s
EventlogEntry from
EventText: Missing/not valid parameter
%s in message %s
Received unexpected or unknown display

message
Automatic
Remedy Actions
Actions,
performed by
the Gateway
MSG_HFAA_
INTERNAL_
ERROR
Major
MSG_HFAA_
PARAM_ERROR
EventlogEntry from
EventText: Unexpected message ID or
eventcode (%x)
Description
EventlogEntry from
Application doesnt get requested display
memory or constructor returns null
EventText: Can't access to/allocate mem- pointer
ory
Warning
MSG_HFAA_
MESSAGE_
ERROR
MSG_HFAA_
Major
MEMORY_ERROR
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
HFA Adapter Events
EventCode
C.2.17
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Major
Warning
Minor
Warning
MSG_PPP_CC_
STARTUP_
FAILURE
MSG_PPP_CC_
UNHANDLED_
MSG_ID
MSG_PPP_CC_
INVALID_PARAM
MSG_PPP_CC_
STATE_
PROCESSING_
ERROR
Software error during startup of

PPP
Description
A31003-H3540-A800-1-7619, 2003-05-02
Software error: invalid internal
data detected
Stop Trace
Prole:
PPP_CC-STD
EventText: inconsistent internal state:

%n%s
MSG_PPP_CC_INCONSISTANT_INTERNAL_STAT
EventLogEntry from
EventCode:
Software error: internal data beStop Trace

came inconsistent during process- Prole:
ing
PPP_CC-STD
EventLogEntry from
Software error : Received mesStop Trace
sage not expected in current state Prole:
EventCode:
will be ignored
PPP_CC-STD
MSG_PPP_CC_
STATE_PROCESSING_ERROR
EventText: received message %s not expected in current state %s
EventLogEntry from
EventCode:
MSG_PPP_CC_ INVALID_PARAM
EventText: invalid parameter %s, value
%i
Stop Trace
Prole:
PPP_CC-STD
Automatic
Remedy Actions
Actions,
performed by
the Gateway
EventLogEntry from
Software error : Unexpected mes- Stop Trace
sage received will be ignored
Prole:PPPEventCode:
Std
MSG_PPP_CC_UNHANDLED_MSG_ID
EventText: unexpected message received, id:%x
EventLogEntry from
EventCode:
MSG_PPP_CC_ STARTUP_FAILURE
EventText: startup of PPP call control
failed:%n%s
MSG_PPP_CC_
Minor
INCONSISTANT_
INTERNAL_STATE
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
PPP Call Control Events
EventCode
C.2.18
Admain_anhang_C.fm
Tables
Event Templates
C-85
C-86
Warning
Major
MSG_PPP_CC_
MANDATORY_
PARAM_MISSING
MSG_PPP_CC_
INCONSISTENT_
DYNAMIC_DATA
Major
MSG_PPP_CC_
INCONSISTENT_
MAP
Major
Major
MSG_PPP_CC_
INVALID_PEERID
MSG_PPP_CC_
INCONSISTENT_
CONFIG
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Software error: inconsistent map
EventLogEntry from
Inconsistence of dynamic peer
data
EventCode:
MSG_PPP_CC_INCONSISTENT_DYNA
MIC_DATA
EventText: dynamic data of peer %i inconsistant
EventLogEntry from
Inconsistence in conguration
data found
EventCode:
MSG_PPP_CC_INCONSISTENT_CONF
IG
EventText: peer %i inconsistant
Stop Trace
Prole:
PPP_CC-STD
Stop Trace
Prole:
PPP_CC-STD
Stop Trace
Prole:
PPP_CC-STD
Stop Trace
Prole:
PPP_CC-STD
Software error: index of ISDN peer Stop Trace

table incorrect
Prole:
PPP_CC-STD
Description
EventLogEntry from
Mandatory parameter missing
EventCode:
MSG_PPP_CC_MANDATORY_PARAM_
MISSING
EventText: mandatory parameter %s
missing (ID: %i)
EventLogEntry from
EventCode:
MSG_PPP_CC_INCONSISTENT_MAP
EventText: map of %s inconsistant
EventLogEntry from
EventCode:
MSG_PPP_CC_INVALID_PEERID
EventText: invalid Peer ID: %d
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Minor
Minor
Mayor
EventCode
MSG_PPP_CC_
INVALID_ADMIN_
MSG
MSG_PPP_CC_
INITIALIZATION_
ERROR
MSG_PPP_CC_
INTERNAL_
ERROR
Description
Automatic
Remedy Actions
Actions,
performed by
the Gateway
A31003-H3540-A800-1-7619, 2003-05-02
EventLogEntry from
EventCode:
MSG_PPP_CC_ INTERNAL_ERROR
EventText: %s
Software error: internal inconsistency
EventLogEntry from
Software Error: double initializaEventType: csevMinor
tion sequence - ignored
EventCode:
MSG_PPP_CC_INITIALIZATION_ERRO
R
EventText: re-initialization of PPP-CC not
allowed
Stop Trace
Prole:
PPP_CC-STD
Stop Trace
Prole:
PPP_CC-STD
EventLogEntry from
Error received while reading/ writ- Stop Trace
ing conguration les
Prole:
EventCode:
PPP_CC-STD
MSG_PPP_CC_INVALID_ADMIN_MSG
EventText: invalid admin message for le
%s received
Admain_anhang_C.fm
Tables
Event Templates
C-87
C-88
%p
MSG_PPPM_
Critical
ERR_OPERATION Major
Minor
Unexpected Condition during operation
None
*1
Examine the Conguration Data for

PPP
*1
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Inconsistency in the Conguration None

Data;
Failure at the Admin-Receiver;
Description
*1 Inform SW-Development, make Trace-Files (SUSY_PPPM_TBAS, SUSY_PPPM_TSTD, SUSY_PPPM_TEXT Lvl 9) available containing this incorrect behaviour.
%p
Critical
Major
Minor
MSG_PPPM_
ERR_CONFIG
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
PPP Manager Events
EventCode
C.2.19
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
Critical
Major
Minor
Warning
Critical
Major
Minor
Warning
Critical
Major
Minor
Warning
MSG_PPP_
STACK_REBOOT
MSG_PPP_
STACK_PROC
MSG_PPPOE_
STACK_REBOOT
MSG_PPPOE_
STACK_PROC
MSG_PPTP_
STACK_REBOOT
MSG_PPTP_
STACK_PROC
%p
Reboot forced by PPTP Stack, reason =

%d
%p
Reboot
PPTP stack processing error
PPTP Stack damaged
PPPOE stack processing error
None
Reboot
None
Reboot
*3
*3
*2
*2
*1
*1
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Internal PPP stack processing er- None

ror
PPP Stack damaged
Description
Reboot forced by PPPOE Stack, reason = PPPOE Stack damaged

%d
%p
Reboot forced by PPP Stack, reason =

%d
*3 Inform SW-Development, make Trace-Files (SUSY_PPTP_STACK_PROC Lvl 6 and SUSY_PPTP_STACK_DBG_IF Lvl 9) available containing this incorrect
behaviour.
*2 Inform SW-Development, make Trace-Files (SUSY_PPPOE_STACK_PROC Lvl 6 and SUSY_PPOE_STACK_DBG_IF Lvl 9) available containing this incorrect behaviour.
*1 Inform SW-Development, make Trace-Files (SUSY_PPP_STACK_PROC Lvl 6 and SUSY_PPP_STACK_DBG_IF Lvl 9) available containing this incorrect
behaviour.
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
PPP Stack Events
EventCode
C.2.20
Admain_anhang_C.fm
Tables
Event Templates
C-89
C-90
EventLogEntry from
PLCI not found in VS_Plci_Link ta- EventType: csevMinor
ble (needed to nd message_nbr)
EventCode: VCAPI_NO_PLCI
EventText: PLCI not found in
VS_Plci_Link table (to nd message_nbr)
Tables
Event Templates
MSG_VCAPI_NO_ Minor
PLCI
EventLogEntry from
Too many physical link connecEventType: csevMajor
tions or connections are not reEventCode: VCAPI_LINK_TABLE_FULL leased properly.
EventText: No free element found in
VS_Plci_Link table
Major
MSG_VCAPI_
LINK_TABLE_
FULL
EventLogEntry from
Wrong linknumber in the message EventType: csevMinor
received from VCAPI-Server oder
EventCode: VCAPI_WRONG_LINKNUM CAPI_PAYLOAD_INT
EventText: Wrong link number %d in
message %s
Not possible to set up a new connection for VCAPI
Minor
EventLogEntry from
EventCode: BSD44_ACCEPT_ERROR
EventText: Accept error for VCAPI
Dispatcher
Sockets for VCAPI and DATAGW

clients doesnt work anymore
Automatic
Remedy Actions
Actions,
performed by
the Gateway
MSG_VCAPI_
WRONG_
LINKNUM
Major
MSG_BSD44_
ACCEPT_ERROR
EventLogEntry from
EventCode: BSD44_SELECT_ERROR
EventText: Select error for VCAPI &
DATAGW Dispatcher
Description
EventLogEntry from
No data available in the message EventType: csevMinor
received from VCAPI-Server oder
EventCode: VCAPI_NO_CAPI_DATA
CAPI_PAYLOAD_INT
EventText: No CAPI data in message with
event 0x%x
Major
MSG_BSD44_
SELECT_ERROR
MSG_VCAPI_NO_ Minor
CAPI_DATA
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
VCAPI Events
EventCode
C.2.21
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Minor
Minor
Minor
Minor
Minor
Minor
EventCode
MSG_VCAPI_
CONV_H2N_
ERROR
MSG_VCAPI_
CONV_H2N_
FAILED
MSG_VCAPI_
WRONG_CONV_
H2N
A31003-H3540-A800-1-7619, 2003-05-02
MSG_VCAPI_
UNKNOWN_
MSG_H2N
MSG_VCAPI_
WRONG_MSG_
LENGTH
MSG_VCAPI_
CONV_N2H_
FAILED
Conversion returns wrong value
Wrong total_length in CAPI-Message
Wrong subcommand in message
Message not converted (wrong

message)
Conversion returns wrong value
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Message to client is not converted correctly
Description
EventLogEntry from
EventCode:
VCAPI_CONV_N2H_FAILED
EventText: Conversion for %s returns
%d,expected %d)
EventLogEntry from
EventCode:
VCAPI_ WRONG_MSG_LENGTH
EventText: Wrong message length %d
EventLogEntry from
EventCode:
VCAPI_ UNKNOWN_MSG_H2N
EventText: Unknown message %s
EventLogEntry from
EventCode:
VCAPI_WRONG_CONV_H2N
EventText: Wrong conversion for %s
EventLogEntry from
EventCode:
VCAPI_CONV_H2N_FAILED
EventText: Conversion for %s returns
%d,expected %d
EventLogEntry from
EventCode:
VCAPI_CONV_H2N_ERROR
EventText: Conversion error:%d
Admain_anhang_C.fm
Tables
Event Templates
C-91
C-92
Minor
Warning
Major
MSG_VCAPI_
UNKNOWN_
MSG_N2H
MSG_VCAPI_
TOO_MANY_
CLIENTS
MSG_VCAPI_
ACCEPT_ERROR
MSG_VCAPI_NO_ Minor
CLIENT
Warning
Minor
MSG_VCAPI_
WRONG_CONV_
N2H
MSG_VCAPI_
DISP_NOT_
READY
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
EventLogEntry from
EventCode: VCAPI_NO_CLIENT
EventText: no client address
EventLogEntry from
EventCode:
VCAPI_DISP_NOT_READY
EventText: VCAPI-Dispatcher not ready
EventLogEntry from
EventCode: VCAPI_ACCEPT_ERROR
EventText: Accept error for VCAPI
Dispatcher
EventLogEntry from
EventCode:
VCAPI_TOO_MANY_CLIENTS
EventText: Too many clients connected
EventLogEntry from
EventCode:
VCAPI_ UNKNOWN_MSG_N2H
EventText: unknown msg %s
EventLogEntry from
EventCode:
VCAPI_WRONG_CONV_N2H
EventText: Wrong conversion for %s
no client address
VCAPI-Server has not send the

VCAPI_EVENT_START_
OPERATION_REQ to the dispatcher
Not possible to set up a new connection for VCAPI
Automatic
Remedy Actions
Actions,
performed by
the Gateway
No free element found in connection table

Close connection.
Wrong subcommand in message
Message not converted (wrong

message)
Description
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
EventLogEntry from
EventCode:
VCAPI_ NO_NEW_BUF
EventText: Not possible to create buffer
with size:%d
MSG_VCAPI_
BUF_NOT_
CREATED
Not possible to create a buffer with the expected length
EventLogEntry from
Not possible to get an extended re- reboot
ceive buffer
EventCode:
(Alloc error)
VCAPI_ NO_ALLOC_EXTENDED
EventText: Not possible to allocate an extended buffer
MSG_VCAPI_NO_ Major
ALLOC_
EXTENDED
Major
EventLogEntry from
Not possible to get a single receive reboot
buffer
EventCode:
(Alloc error)
VCAPI_ NO_ALLOC_SINGLE
EventText: Not possible to allocate a single buffer
Major
Receive buffer either already

cleared or not possible to get one
Buffer length not within the message limits
Automatic
Remedy Actions
Actions,
performed by
the Gateway
MSG_VCAPI_
NO_ALLOC_
SINGLE
EventLogEntry from
EventCode:
VCAPI_ WRONG_BUF_LEN
EventText: Wrong buffer length %d
Description
EventLogEntry from
EventCode:
VCAPI_ NO_RCV_BUFFER
EventText: rcvBufPP=0x%x null
Minor
MSG_VCAPI_
WRONG_BUF_
LEN
MSG_VCAPI_NO_ Minor
RCV_BUFFER
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Admain_anhang_C.fm
Tables
Event Templates
C-93
C-94
Major
Major
Minor
MSG_VCAPI_
SOCKET_BIND_
ERR
MSG_VCAPI_
LISTENING_ERR
MSG_VCAPI_
RECEIVE_ERR
Major
MSG_VCAPI_
SOCKET_NOT_
OPEN
Not possible to create a listening VCAPI-socket

(Connections with clients not possible)
Bind error for VCAPI-socket

Socket couldnt be opened.

Received data not stored because reboot

of no new buffer allocated
(Alloc error)
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Not possible to create a new buffer reboot

to store the received data
(Alloc error)
Description
Tables
Event Templates
EventLogEntry from
Error while receiving message for EventType: csevMinor
VCAPI-Dispatcher
EventCode:
VCAPI_ RECEIVE_ERR
EventText: Error while receiving message
for VCAPI-Dispatcher:Returncode %x
EventLogEntry from
EventCode:
VCAPI_ LISTENING_ERR
EventText: listening error for socket %d
EventLogEntry from
EventCode:
VCAPI_ SOCKET_ BIND_ERR
EventText: bind error for socket %d
EventLogEntry from
EventCode:
VCAPI_ SOCKET_NOT_OPEN
EventText: VCAPI-Socket not opened
EventLogEntry from
EventCode:
VCAPI_ DATA_NOT_STORED
EventText: Not possible to get a receive
buffer,data not stored
Major
MSG_VCAPI_
DATA_NOT_
STORED
EventLogEntry from
EventCode:
VCAPI_ NO_NEW_BUF
EventText: No new buffer created by
vs_bputd
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
MSG_VCAPI_NO_ Major
NEW_BUF
EventCode
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
EventLogEntry from
EventCode:
VCAPI_ PLCI_NOT_FOUND
VS_Plci_Link table
Minor
Major
Major
MSG_VCAPI_
PLCI_NOT_
FOUND
MSG_VCAPI_
IND_ALLOC_ERR
MSG_VCAPI_
CONF_ALLOC_
ERR
EventLogEntry from
EventCode:
VCAPI_ CONF_ALLOC_ERR
EventText: Not possible to allocate a buffer for CMT_DATA_CONF
EventLogEntry from
EventCode:
VCAPI_ IND_ALLOC_ERR
EventText: Not possible to allocate a buffer for CMT_DATA_IND
EventLogEntry from
EventCode:
VCAPI_ WRONG_EVENT_SRV
VCAPI_SERVER
MSG_VCAPI_
Warning
WRONG_EVENT_
SRV
EventLogEntry from
EventCode:
VCAPI_ NO_ALLOC_MSG
EventText: Not possible to allocate a buffer
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
MSG_VCAPI_NO_ Major
ALLOC_MSG
EventCode

CMT_DATA_CONF
(message can not be sent to client)

CMT_DATA_IND
(message can not be sent to client)
PLCI not found in VS_Plci_Link table when receiving a message

from CAPI_PAYLOAD_IF
VCAPI-Dispatcher has received

wrong event from VCAPI-Server
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Not possible to send a message to reboot

VCAPI-Dispatcher because no
buffer could be allocated
(Alloc error)
Description
Admain_anhang_C.fm
Tables
Event Templates
C-95
C-96
EventLogEntry from
EventCode:
VCAPI_ DATA_B3_ALLOC_ERR
EventText: ALLOC ERROR: returncode
%x
EventLogEntry from
EventCode:
VCAPI_ NO_PLCI_DISCONNECT
EventText: PLCI Element not found in
VS_Plci_Link table for
DISCONNECT_RESPONSE
MSG_VCAPI_
Major
DATA_B3_ALLOC_
ERR
MSG_VCAPI_NO_ Minor
PLCI_
DISCONNECT
MSG_VCAPI_NO_ Minor
PLCI_DATA_B3
EventLogEntry from
EventCode:
VCAPI_ NO_PLCI_DATA_B3
VS_Plci_Link table (for DATA_B3_REQ)
EventLogEntry from
EventCode:
VCAPI_ WRONG_ LENGTH_MSG
EventText: Wrong message length %d
Warning
MSG_VCAPI_
WRONG_
LENGTH_MSG
EventLogEntry from
EventCode:
VCAPI_ WRONG_EVENT_CAPI
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
MSG_VCAPI_
Warning
WRONG_EVENT_
CAPI
EventCode
PLCI Element not found in

VS_Plci_Link table for
DISCONNECT_RESPONSE
message
Not possible to get a buffer to send reboot

the DATA_B3_REQ message to
CAPI_PAYLOAD_IF
(Alloc error)
Automatic
Remedy Actions
Actions,
performed by
the Gateway
PLCI not found in VS_Plci_Link table (for DATA_B3_REQ)

(message can not be sent to
CAPI_PAYLOAD_IF)
Message from client to VCAPIServer/CAPI_PAYLOAD_IF has

an incorrect length
VCAPI-Dispatcher has received

wrong event from
CAPI_PAYLOAD_IF
Description
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
Warning
Minor
MSG_VCAPI_
SOCKET_RCV_
ERR
MSG_VCAPI_
SOCK_NOT_
AVAIL
EventLogEntry from
EventCode:
VCAPI_ SOCK_NOT_AVAIL
EventText: connected socket not stored
in connection table
EventLogEntry from
EventCode:
VCAPI_ SOCKET_RCV_ERR
EventText: Error on receiving data from
the socket (connection interrupted)
EventLogEntry from
EventCode:
VCAPI_ RCV_LEN_ERR
EventText: Wrong message length at receive data from client
Warning
MSG_VCAPI_
RCV_LEN_ERR
EventLogEntry from
EventCode:
VCAPI_ MSG_NOT_SEND
EventText: Not possible to send message
EventLogEntry from
EventCode:
VCAPI_ NO_LIST_SOCKET
EventText: no listening socket stored in
connection table
Warning
MSG_VCAPI_
MSG_NOT_SEND
MSG_VCAPI_NO_ Major
LIST_SOCKET
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Connected socket not stored in

connection table.No data can be
received.
Connection has been interrupted.Causes an error on receiving

data.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Wrong message length at receive data from client

(close connection,message is not
sent to VCAPI-Server)
No listening socket stored in connection table

(a new connection can not be
opened)
Not possible to send message

(interface to CAPI_PAYLOAD returns
1)
Description
Admain_anhang_C.fm
Tables
Event Templates
C-97
C-98
-
Automatic
Remedy Actions
Actions,
performed by
the Gateway
EventLogEntry from
Link number not found in connec- EventType: csevMinor
tion table
EventCode:
VCAPI_ NO_LNK_CONN
EventText: Link number not found in connection table
Unknown notication
Description
MSG_VCAPI_NO_ Minor
LNK_CONN
EventLogEntry from
EventCode:
VCAPI_ UNKNOWN_NTFY
EventText: Unknown notication.Used
value:%d
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
MSG_VCAPI_
Warning
UNKNOWN_NTFY
EventCode
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
EventLogentry from
EventCode:
VCAPI_UNANTICIPATED_MESSAGE
EventText: Unanticipated Message %s
for CSID %s in state %s.
EventLogentry from
The CAPI Manager has received a EventType: csevWarning
CAPI message with an unknown
EventCode:
command and subcommand
VCAPI_UNANTICIPATED_CAPI_
MESSAGE
EventText: Unanticipated CAPI message
%s.
EventLogentry from
EventCode:
VCAPI_UNANTICIPATED_DISP_
MESSAGE
EventText: Unanticipated VCAPI Dispatcher message %d.
EventLogentry from
EventCode:
VCAPI_UNANTICIPATED_MESSAGE_
BASE
EventText: Unanticipated Message Base
%m.
MSG_VCAPI_
Warning
UNANTICIPATED_
MESSAGE
MSG_VCAPI_
Warning
UNANTICIPATED_
CAPI_MESSAGE
MSG_VCAPI_
Warning
UNANTICIPATED_
DISP_MESSAGE
A31003-H3540-A800-1-7619, 2003-05-02
MSG_VCAPI_
Warning
UNANTICIPATED_
MESSAGE_BASE
The VCAPI Server, VCAPI Interface or CAPI Manager has received a message base with an
unanticipated ID
The VCAPI Server has received a VCAPI Dispatcher message with

an unknown event
The CAPI Manager has received an unanticipated message for the

current state of the according
CAPI object
Various VCAPI Server errors from the HXG2 code
EventLogentry from
EventCode: VCAPI_SERVER_ERROR
EventText: VCAPI Server error: %p.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Warning
Description
MSG_VCAPI_
SERVER_ERROR
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
VCAPI Application Events
EventCode
C.2.22
Admain_anhang_C.fm
Tables
Event Templates
C-99
C-100
Warning
Warning
MSG_VCAPI_
MSGBASE_
WITHOUT_
DATAGWMSG
MSG_VCAPI_
ILLEGAL_LINK_
NUMBER
Warning
MSG_VCAPI_
MSGBASE_
WITHOUT_
CAPIMSG
Warning
Warning
MSG_VCAPI_
MESSAGE_
LENGTH_TOO_
SHORT
MSG_VCAPI_
MSGBASE_
WITHOUT_
DISPMSG
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
An attempt was made to address a member of the dynamic link table

with an illegal index
The VCAPI Server has received

from the VCAPI Dispatcher a message base not containing the mandatory VCAPI Dispatcher message
The CAPI Manager has received from NU or from the Data GW dispatcher a message base not containing the mandatory Data GW
message
The VCAPI Server, CAPI Interface or CAPI Manager has received a

CapiInd or CapiReq not containing
the mandatory CAPI message
Automatic
Remedy Actions
Actions,
performed by
the Gateway
The length of the CAPI message is greater than the size of the VBString containing this CAPI message
Description
Tables
Event Templates
EventLogentry from
EventCode:
VCAPI_ILLEGAL_LINK_NUMBER
EventText: Illegal link number: %d.
EventLogentry from
EventCode:
VCAPI_MSGBASE_WITHOUT_
DISPMSG
EventText: Message Base without VCAPI
Dispatcher message.
EventLogentry from
EventCode:
DATAGWMSG
EventText: Message Base without Data
GW message.
EventLogentry from
EventCode:
CAPIMSG
EventText: Message Base without CAPI
message.
EventLogentry from
EventCode:
VCAPI_MESSAGE_LENGTH_TOO_
SHORT
EventText: Part of the CAPI Message is
missing (%d > %d).
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
EventLogentry from
EventCode:
VCAPI_COULD_NOT_DELETE_
OBJECT
EventText: Could not delete a CAPI object.
EventLogentry from
EventCode:
VCAPI_NO_PLCI_AVAILABLE
EventText: No PLCI available.
MSG_VCAPI_NO_ Warning
PLCI_AVAILABLE
EventLogentry from
EventCode:
VCAPI_ADD_OBJECT_FAILED
EventText: Could not add a CAPI object
to the managed object list.
MSG_VCAPI_
Major
COULD_NOT_
DELETE_OBJECT
Major
MSG_VCAPI_
ADD_OBJECT_
FAILED
EventLogentry from
EventCode:
VCAPI_ILLEGAL_PARTNER_NUMBER
EventText: Illegal partner number: %d.
EventLogentry from
EventCode:
VCAPI_COULD_NOT_CREATE_
OBJECT
EventText: Could not create a CAPI object.
Warning
MSG_VCAPI_
ILLEGAL_
PARTNER_
NUMBER
MSG_VCAPI_
Warning
COULD_NOT_
CREATE_OBJECT
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
All available PLCI are seized
The specied CAPI object could

not be deleted
Reboot
No new CAPI object could be created
Automatic
Remedy Actions
Actions,
performed by
the Gateway
A newly created CAPI object could Reboot

not be added to the managed object list
An attempt was made to address

the info of a non allocated VCAPI
partner
Description
Admain_anhang_C.fm
Tables
Event Templates
C-101
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Warning
Warning
Warning
Warning
Major
EventCode
MSG_VCAPI_
CSID_MISSING
C-102
MSG_VCAPI_
COULD_NOT_
FIND_PLCI
MSG_VCAPI_
COULD_NOT_
FIND_OBJECT
MSG_VCAPI_
COULD_NOT_
FIND_CSID
MSG_VCAPI_
COULD_NOT_
STORE_REQ
EventLogentry from
EventCode:
VCAPI_COULD_NOT_STORE_REQ
EventText: Could not store the request
%x %x for PLCI %d.
No space available anymore in the Reboot

CAPI interface to store the request
EventLogentry from
The call and session ID belonging EventType: csevWarning
to a given PLCI could not be found
EventCode:
VCAPI_COULD_NOT_FIND_CSID
EventText: Could not nd the corresponding CSID.
EventLogentry from
The CAPI object belonging to a
given call and session ID could not
EventCode:
be found
VCAPI_COULD_NOT_FIND_OBJECT
EventText: Could not nd the corresponding CAPI Object.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
The CAPI Manager has received a message from NU or from CCP

that doesnt contain a call and session ID
Description
EventLogentry from
The PLCI belonging to a given call EventType: csevWarning
and session ID or a given channel
EventCode:
ID could not be found
VCAPI_COULD_NOT_FIND_PLCI
EventText: Could not nd the corresponding PLCI.
EventLogentry from
EventCode: VCAPI_CSID_MISSING
EventText: CSID is missing.
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
MSG_VCAPI_
Warning
CONF_WITHOUT_
REQ
EventCode
Description
Automatic
Remedy Actions
Actions,
performed by
the Gateway
EventLogentry from
The CAPI interface has received a EventType: csevWarning
conrmation without an according
EventCode:
stored request
VCAPI_CONF_WITHOUT_REQ
EventText: Conrmation %x %x for PLCI
%d without stored Request.
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
Tables
Event Templates
C-103
C-104
Major
Major
MSG_
H323CLIENT_
NWRS_ENTRY_
FAILED
MSG_
H323CLIENT_
MAPS_DIFFER
Minor
MSG_
H323CLIENT_
INVALID_ADMIN_
MSG
Major
Major
MSG_
H323CLIENT_
INVALID_
CLIENTID
MSG_
H323CLIENT_
INVALID_PARAM
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Software error: invalid parameter
Create NWRS entry failed
Stop Trace
Prole:
H323ClientInternal
Stop Trace
Prole:
H323ClientInternal
Stop Trace
Prole:
H323ClientInternal
Tables
Event Templates
EventLogEntry from
Software error: invalid parameter
EventCode:
MSG_H323CLIENT_MAPS_DIFFER
EventText: size of maps differ (call no: %i,
IP: %i)
EventLogEntry from
EventCode:
MSG_H323CLIENT_INVALID_PARAM
EventText: invalid parameter %s, value
%x
EventLogEntry from
EventCode:
MSG_H323CLIENT_NWRS_ENTRY_
FAILED
EventText: create %s entry failed for client (%i, %i)
Stop Trace
Prole:
H323ClientInternal
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Software error: index of client table Stop Trace

incorrect
Prole:
H323ClientInternal
Description
EventLogEntry from
Error received while reading/ writEventType: csevMinor
ing conguration les
EventCode:
MSG_H323CLIENT_INVALID_ADMIN_
MSG
EventText: invalid admin message for le
%s received
EventLogEntry from
EventCode:
MSG_H323CLIENT _
INVALID_CLIENTID
EventText: invalid Peer ID: %d
H.323 Client Events
EventCode
C.2.23
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Major
Major
Major
Major
Major
MSG_IPNCA_
ERROR
MSG_IPNC_
MESSAGE_
ERROR
MSG_IPNC_
MESSAGE_
DUMP
MSG_
IPNC_PARAM_
ERROR
MSG_IPNC_
INTERNAL_
ERROR
IPNC Events
EventCode
C.2.24
A31003-H3540-A800-1-7619, 2003-05-02
EventLogEntry from
EventCode:
MSG_IPNC_INTERNAL_ERROR
EventText: internal error:%i
EventLogEntry from
EventCode:
MSG_IPNC_PARAM_ERROR
EventText: message parameter error:%s%x
EventLogEntry from
EventCode:
MSG_IPNC_MESSAGE_DUMP
EventText: message error:%s%M
EventLogEntry from
EventCode:
MSG_IPNC_MESSAGE_ERROR
EventText: message error:%s
EventLogEntry from
EventCode:
MSG_IPNCA_ERROR
EventText: IPNCA error:%s%x
Stop Trace
Prole: IPNCDetailed
Automatic
Remedy Actions
Actions,
performed by
the Gateway

data detected
message with invalid parameter

received - will be ignored
Stop Trace
Prole IPNCDetailed
Stop Trace
Prole: IPNCStd
unexcpected message received - Stop Trace

will be ignored
Prole: IPNCStd
unexcpected message received - Stop Trace

will be ignored
Prole: IPNCStd

data detected
Description
Admain_anhang_C.fm
Tables
Event Templates
C-105
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Major
Major
EventCode
MSG_IPNC_
INCONSISTENT_
STATE
C-106
MSG_IPNC_CP_
ASYNCH
EventLogEntry from
EventCode:
MSG_IPNC_CP_ASYNCH
EventText: : CP and IPNC asynchronous: %s%s
EventLogEntry from
EventType: csevMajor r
EventCode:
MSG_IPNC_INCONSISTENT_STATE
EventText: inconsistent internal state:
%s%x
Stop Trace
Prole: IPNCStd
Automatic
Remedy Actions
Actions,
performed by
the Gateway
asynchronity between states of Hi- Stop Trace

com-CP and IPNC detected
Prole: IPNCStd
Software error: data became inconsistent during processing
Description
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
IPNCA Events
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Information
MSG_MPH_INFO
MPH Events
EventCode
C.2.26
MSG_IPNCA_ERR Minor
OR
EventCode
C.2.25
SGP Message cannot be sent to

IPNC
SGP Message not sent
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Event log for all MPH-events w/ severity Information
Description
A minor error has occurred.
Description
EventLogEntry from
EventText: %p
EventLogEntry from
EventCode:
MSG_IPNCA_ERROR
EventText: IPNC Adapter: (some) Error
description
("IPNC Adapter: %s")
Admain_anhang_C.fm
Tables
Event Templates
C-107
C-108
Warning
Information
MSG_OAM_
TIMESYNC
MSG_OAM_
PRIO_
INCREASED
Critical
MSG_DISP_
SENDER_NOT_
SET
Warning
Major
MSG_TLS_
MUTEX_
BLOCKED
MSG_OAM_
TIMESYNC_
FAILED
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
OAM Events
EventCode
C.2.27
EventLogEntry from
EventType:csev Warning
EventCode:
MSG_OAM_PRIO_INCREASED
EventText:
" Priority of %s increased "
EventLogEntry from
EventType: csev Warning
EventCode:
MSG_OAM_TIMESYNC_FAILED
EventText:
"Time Synchronization failed"
EventLogEntry from
EventCode: MSG_OAM_TIMESYNC
EventText:
"Time Synchronization from %s to %s"
EventLogEntry from
EventType: csev Critical
EventCode:
MSG_DISP_SENDER_NOT_SET
EventText:
"Sender not set in message:%n%M"
EventLogEntry from
EventCode:
MSG_TLS_MUTEX_BLOCKED
EventText: Mutex blocked
Priority of a OAM Task (Trace,

Event,OAM) was increased, because of heavy load;
this is still a valid behaviour,
Time synchronization not performed
Time synchronization took place
Event is always followed by an ASSERT-Event, which causes a automatic reboot
Internal sw error,
Message sender not set,
Software error: deadlock
Description
Reboot the gateway,

Error report
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
Major
Warning
MSG_OAM_
QUEUE_
BLOCKED
MSG_OAM_
INTERNAL_
EVENT
Execution of an automatic action

failed.
Put to Msg Queue of OAM Tasks

(Trace, Event,OAM) failed.
Reason: queue blocked.
All messages are removed.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
EventLogEntry from
EventCode:
MSG_OAM_INTERNAL_EVENT
EventText:
"Execution of action %s failed."
EventLogEntry from
EventCode:
MSG_OAM_QUEUE_BLOCKED
EventText:
" Put to OAM Msg Queue (%s) failed.
Queue blocked. Remove Message "
Put to Msg Queue of OAM Tasks

(Trace, Event,OAM) failed.
No specic reason.
All messages are removed.
Major
MSG_OAM_PUT_
TO_QUEUE_
FAILED
EventLogEntry from
EventCode:
MSG_OAM_PUT_TO_QUEUE_FAILED
EventText:
" Put to OAM Msg Queue (%s) failed. Remove Message "
EventLogEntry from
Queue of OAM Tasks(Trace,
Event,OAM) full.
EventCode: MSG_OAM_QUEUE_FULL All messages are removed.
EventText:
" OAM Msg Queue (%s) full. Remove
Messages "
Major
Priority of a OAM Task (Trace,

Event,OAM) was decreased, because there is no longer heavy
load;
valid behaviour,
Description
MSG_OAM_
QUEUE_FULL
EventLogEntry from
EventCode:
MSG_OAM_PRIO_SWITCHED_BACK
EventText:
"Priority of %s switched back. OAM Msg
Queue OK "
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
MSG_OAM_
Cleared
PRIO_
SWITCHED_BACK
EventCode
Admain_anhang_C.fm
Tables
Event Templates
C-109
C-110
Information
Information
MSG_ADMIN_
LOGGED_OUT
MSG_ADMIN_
SESSION_
EXPIRED
Information
MSG_ADMIN_
SESSION_
CREATED
Information
Information
MSG_ADMIN_
LOGGED_IN
MSG_ADMIN_
INVALID_LOGIN
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Description
A session for an administrator or an automatic login procedure (like

AutoDiscovery or DataTransfer
from Hicom to HXG3)
Was created.
Invalid login attempt
(Trap ???)
- new login necessary
Tables
Event Templates
EventLogEntry from
Session expired (Session Time
out reached).
EventCode:
MSG_ADMIN_SESSION_EXPIRED
EventText:
Session id = %d of user \"%s\" expired "
EventLogEntry from
EventCode:
MSG_ADMIN_INVALID_LOGIN
EventText:
Invalid login from %s (user \"%s\") "
Automatic
Remedy Actions
Actions,
performed by
the Gateway
EventLogEntry from
Information for a successful logout EventType: csevInformation
of an administrator
EventCode:
MSG_ADMIN_LOGGED_OUT
EventText:
%s user \"%s\" (session id = %d) logged
out "
EventLogEntry from
EventCode:
MSG_ADMIN_SESSION_CREATED
EventText:
"%s session created for user \"%s\" (session id = %d)"
EventLogEntry from
Information for a successful login
of an administrator
EventCode: MSG_ADMIN_LOGGED_IN
EventText:
"%s user \"%s\" (session id = %d) logged
in"
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Information
Information
Information
Information
EventCode
MSG_ADMIN_
GOT_WRITE_
ACCESS
MSG_ADMIN_
DIDNT_GET_
WRITE_ACCESS
MSG_ADMIN_
RELEASED_
WRITE_ACCESS
A31003-H3540-A800-1-7619, 2003-05-02
MSG_ADMIN_
FORCE_
RELEASE_
WRITE_ACCESS
EventLogEntry from
EventCode:
MSG_ADMIN_FORCE_RELEASE_
WRITE_ACCESS
EventText:
"%s user \"%s\" (session id = %d) forced
release write access"
EventLogEntry from
EventCode:
MSG_ADMIN_RELEASED_WRITE_
ACCESS
EventText:
"%s user \"%s\" (session id = %d) released write access"
EventLogEntry from
EventCode:
MSG_ADMIN_DIDNT_GET_WRITE_
ACCESS
EventText:
"%s user \"%s\" (session id = %d) didn't
get write access"
EventLogEntry from
EventCode:
MSG_ADMIN_GOT_WRITE_ACCESS
EventText:
%s user \"%s\" (session id = %d) got
write access "
Current Administrator was forced to release the write access by another Administrator.
Now the other administrator is able
to make changes.
From now on no cong changes
are allowed for the current administrator.
Administrator released the write

access.
Now other administrator are able
to get the write access.
From now on no cong changes
are allowed for the current administrator.
Administrator did not get the write access.

There is another administrator,
which owns the write access.
- wait or
- force get write access (e.g. via
WBM)
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Administrator has got the write access.

Now conguration changes can be
done.
Description
Admain_anhang_C.fm
Tables
Event Templates
C-111
C-112
Not used for HXG3
Not used for HXG3
Not used for HXG3

Not used for HXG3
Not used for HXG3
MSG_WBM_
ADMIN_
UNLOCKED
MSG_WBM_
LOGGED_IN
MSG_WBM_
LOGGED_OUT
MSG_WBM_
LOGIN_
REJECTED
Description
MSG_WBM_
ADMIN_LOCK_
FORCED
Not used for HXG3
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
WBM Events
MSG_WBM_
ADMIN_LOCKED
EventCode
C.2.28
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Warning
Information
Information
MSG_CLI_
TELNET_
ABORTED
MSG_CLI_
LOGGED_IN_
FROM_TELNET
MSG_CLI_
LOGGED_IN_
FROM_V24
CLI Events
EventCode
C.2.29
Telnet client disconnected before

logging in
Description
A31003-H3540-A800-1-7619, 2003-05-02
EventLogEntry from
EventCode:
MSG_CLI_LOGGED_IN_FROM_V24
EventText:
User \"%s\" logged in (session id = %d)
from V24 CLI.
.
V24 user successfully logged in
EventLogEntry from
Telnet client successfully logged in
EventCode:
MSG_CLI_LOGGED_IN_FROM_TELNE
T
EventText:
User \"%s\" logged in (session id = %d)
from telnet CLI with IP address %s.
.
EventLogEntry from
EventCode:
MSG_CLI_TELNET_ABORTED
EventText: Telnet client \"%s\" aborted.
.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
C-113
C-114
Critical
Information
MSG_LIC_DATA_
ACCEPTED
MSG_LIC_DATA_
CORRUPTED
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventLogEntry from
EventCode:
MSG_LIC_DATA_CORRUPTED
EventText: license data are corrupted
and set back to default values
EventLogEntry from
EventCode:
MSG_LIC_DATA_ACCEPTED
EventText: license data accepted and
loaded
Licence Management Events
EventCode
C.2.30
HiPath 3000 V4.0:

License data must
be inserted via HiPath 3000 Manager E.
HiPath 3000 V1.0 /

V3.0:
License data must
be inserted by using the license key
via WBM.
Tables
Event Templates
HiPath 3000 V4.0:

This event will appear, if licmgmt
get modied license data via System Interface (SI) and the data
could not be encrypted.
HiPath 3000 V1.0 / V3.0:

SNMP Trap
During startup of component licmgmt the license data in the persistency le licmgmt.txt are
checked against the MAC address. In case the check is not successful, the license le is corrupted. Licmgmt tries to load the
default data.
HiPath 3000 V4.0:

This event will appear, if licmgmt
get modied license data via System Interface (SI) and the data
could be encrypted without any errors. In case SI sends unchanged
license data to licmgmt, no event
will appear.
Not necessary
Automatic
Remedy Actions
Actions,
performed by
the Gateway
HiPath 3000 V1.0 / V3.0:

SNMP Trap
During startup of component licmgmt the license data in the persistency le licmgmt.txt are
checked against the MAC address. In case the license data are
correct, this event appears.
Also in case license data have
been modied via WBM without
any errors, this event will appear.
Description
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Warning
EventCode
MSG_LIC_DATA_
NOT_ACCEPTED
EventLogEntry from
EventCode:
MSG_LIC_DATA_NOT_ACCEPTED
EventText: license data not accepted
HiPath 3000 V4.0:

not used
License data must

be inserted by using the correct license key via
WBM.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
HiPath 3000 V1.0 / V3.0:

SNMP Trap
In case license data have been
tried to insert via WBM, but the license key is wrong, this event will
appear.
Description
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
C-115
C-116
Warning
Warning
MSG_HIP_NO_
NETPOOL_INIT
MSG_HIP_NO_
OBJ_INIT
Warning
MSG_HIP_NO_
MEM_CL
No memory for a cluster

Available.
No heap space for cluster

Block available.
No heap space for device

data
Description
EventLogEntry from
Initialisation of END_OBJ for HIP
not
EventCode: HIP_MSG_NO_OBJ_INIT
Possible.
EventText: No initialisation of END_OBJ
Structure possible
EventLogEntry from
Initialisation of netpool
For HIP not pssible.
EventCode:
HIP_MSG_NO_NETPOOL_INIT
EventText: "NETPOOL INIT not possible:
Return value %d
EventLogEntry from
EventCode: HIP_MSG_NO_MEM_CL
EventText: hi_main: No memory for
Cluster %d available
EventLogEntry from
EventCode:
HIP_MSG_NO_MEM_CLBLK
EventText: "hi_main: No memory for
Cluster block available
Warning
MSG_HIP_NO_
MEM_CLBLK
EventLogEntry from
EventCode:
HIP_MSG_ALLOC_DEV_OBJ
EventText: "hi_main: Device allocation
memory not possible
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
HIP Events
MSG_HIP_
Warning
ALLOC_DEV_OBJ
EventCode
C.2.31
Check END_OBJ
pointer and memory.
Check return value

and
take the necessary
measures.
Check why
no allocatebale
memory
Is available on the
HXG3
Check why
no allocatebale
memory
Is available on the
HXG3.
Check available
memory.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Warning
Warning
Warning
Warning
Warning
EventCode
MSG_HIP_NO_
DEVLOAD
MSG_HIP_NO_
DEVSTART
MSG_HIP_NO_
MEM_TO_SI
MSG_HIP_NO_
CLPOOL_ID
MSG_HIP_NO_
CLUSTER
Description
A31003-H3540-A800-1-7619, 2003-05-02
-
No clusterpool ID available for

sent packet
To IP over the MUX.
EventLogEntry from
No cluster of the ask length avail- EventType: csevWarning
able.
EventCode: MSG_HIP_NO_CLUSTER
EventText: "hi_main:No cluster available
to make packet,packet_len = %d"
EventLogEntry from
EventCode:
MSG_HIP_NO_CLPOOL_ID
EventText: "hi_main: No clusterpool ID
available"
The problem can

be:
Not enough clusters of
a certain length or
the
clusters are not
given free.
Check for problem
Check why
no allocatebale
memory
Is available on the
HXG3.
Interprete the return value

And take the necessary
measure .
Check parameter
given
to muxDevLoad.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
EventLogEntry from
Allocating of memory for message EventType: csevWarning
to SI not possible
EventCode:
MSG_HIP_NO_MEM_TO_SI
EventText: "SI_main: allocating of memory for message to SI not possible"
EventLogEntry from
Starten from HIPdevice in MUX
not possible.
EventCode: MSG_HIP_NO_DEVSTART
EventText: hi_main: Start HIP device not
Possible, return value = %X
EventLogEntry from
Loading HIP device in
MUX not possible.
EventCode: MSG_HIP_NO_DEVLOAD
EventText: "hi_main:Loading device into
MUX not possible,unit = %d,pendLoad =
%X,Pinitstring = %X, Loaning = %d,pBSP
= %X
Admain_anhang_C.fm
Tables
Event Templates
C-117
C-118
Warning
MSG_HIP_
ALLOC_MES_SI
Warning
Warning
MSG_HIP_
PKTLEN_ZERO
MSG_HIP_
LENGTH_ZERO
Warning
MSG_HIP_NO_
PMBLK
Warning
Warning
MSG_HIP_NO_
CLBLK
MSG_HIP_
PMBLK_ZERO
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Nomore clusterblocks.
Description
Pointer on memory block is not

valid.
Informe the IP/

MUX responsible.
Informe the IP/

MUX responsible.
Check memory
spae.
Inform the IP-responsible for this

message.
Check interface IP> MUX

-> HIP
Number of dened
Clusterblocks not
big
Enough.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Tables
Event Templates
EventLogEntry from
Length of packet from Mux is zero.
EventCode : MSG_HIP_LENGTH_ZERO
EventText: "Length of packet from Mux is
zero "
EventLogEntry from
EventCode : MSG_HIP_PMBLK_ZERO
EventText: "Pointer on memory block
from Mux is zero "
EventLogEntry from
Sent message to SI from HIP not
possible.
EventCode :
MSG_HIP_ALLOC_MES_SI
EventText: "No allocation for message SI
possible "
EventLogEntry from
Length of packet from MUX 0.
EventCode : MSG_HIP_PKTLEN_ZERO
EventText: "Packet length from MUX =
zero "
EventLogEntry from
MUX calls HIP without
A pointer on a memory block..
EventCode: MSG_HIP_NO_PMBLK
EventText: "No memory block for incoming messages from MUX"
EventLogEntry from
EventCode: MSG_HIP_NO_CLBLK
EventText: "No clusterblock for netpool
available"
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
Warning
Warning
Warning
Warning
MSG_SI__NO_
PORT
MSG_SI_NO_
LEONEUT
MSG_SI_NO_
PID_LEOTSA
MSG_SI_NO_
PID_DL
MSG_SI_NO_LW_ Warning
SUB_EVENT
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
SI Events
EventCode
C.2.32
Description
EventLogEntry from
EventCode:
MSG_SI_NO_LW_SUB_EVENT
EventText: SI_main: unknown loadware
sub_event %2d
EventLogEntry from
EventCode:MSG_ SI_NO_PID_DL
EventText: "SI_main: unknown PID for
DL %2d
EventLogEntry from
EventCode: MSG_SI_NO_PID_LEOTSA
EventText: "SI_main: unknown PID for
LEOTSA %d"
EventLogEntry from
EventCode: MSG_SI_NO_LEONEUT
EventText: ""SI_main: unknown LEONEUT-port %d
Subevent in message not

Known.
Unknown programm identication for Download
Check DH in
Hipath3000 for
Sub_event in message.
Check Hipath3000
for
DownLoad messages.
Check TS assigment in
Hipath3000
Check Hipat3000
conguration
Check Hipat3000
conguration
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Unknown programm identication. -
Port can not be determinated
EventLogEntry from
Port can not be determinated
EventCode: MSG_SI_MSG_NO_PORT
EventText: "SI_main: unknown LEORLSPort %d
Admain_anhang_C.fm
Tables
Event Templates
C-119
C-120
Warning
Warning
MSG_SI_NO_
KNOWN_EVENT
MSG_SI_
PRIMTIVE_NO_
PID
Warning
MSG_SI_NO_
KNOWN_
LWEVENT
Warning
Warning
MSG_SI_NO_
KNOWN_SAPI
MSG_SI_DSS_
NO_KNOWN_
SAPI
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Not known SAPI
Description
Message event not known.
EventLogEntry from
Sent to application over
MAL not possible.
EventCode:
MSG_SI_PRIMTIVE_NO_PID
EventText: "Sent not possible:no sent for
PID %d possible"
EventLogEntry from
Lw_event for DSS not known.
EventCode: MSG_SI_DSS_ERROR1
EventText: "SI_DSS_sapi_msg: unknown
lw_event %x"
EventLogEntry from
EventCode:
MSG_SI_NO_KNOWN_EVENT
EventText: "SI_main: unknown eventcode %d"
EventLogEntry from
LW-event code not known.
EventCode:
MSG_SI_NO_KNOWN_LWEVENT
EventText: "SI_main: unknown loadware
event %d"
EventLogEntry from
EventCode:
MSG_SI_NO_KNOWN_SAPI
EventText: "SI_main: unknown service(SAPI) %d"
Check PID in message
Check DH-ISDN in
Hipath3000 for
LW-Event in Message
Check DH in
Hipath3000 for
LW-Event in Message
Check DH in
Hipath3000 for
LW-Event in Message
Check DH in
Hipath3000 for
SAPI
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Warning
Critical
Warning
Warning
Critical
EventCode
MSG_SI_TO_
APPL_NO_FD
MSG_SI_DL_NO_
MEM_FAX
MSG_SI_DL_NO_
AMOUNT_
CALLNO
A31003-H3540-A800-1-7619, 2003-05-02
MSG_SI_DL_
INVALID_EV_FAX
MSG_SI_DL_NO_
MEM_HFA
No allocate memory to store

The HFA-clients
EventLogEntry from
ContiNUE message for FAX/MOEventType: csevWarning
DEM is sent without a start mesEventCode:
sage.
MSG_SI_DL_INVALID_EV_FAX
EventText: SI_OAM:invalid subevent,SYS_REINIT_FAX_TAB_CONTINUE
"
EventLogEntry from
EventType: : csevCritical
EventCode:
MSG_SI_DL_NO_MEM_HFA
EventText: " FATAL no memory for HFAclients"
Check stream for

This message
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Check DL- message sequence in

hipath3000.
Check DL-message from the system.

matically.
SNMP Trap;
Allocating of memory not passible. Requested re- No action, reboot is

matically.
SNMP Trap;
Sent over DLPI not possible.
Description
EventLogEntry from
For DL of FAX/MODEM
No number of callno
EventCode:
MSG_SI_DL_NO_AMOUNT_CALLNO
EventText: "SI_OAM: no amount_call_no
in message from system"
EventLogEntry from
EventCode:
MSG_SI_DL_NO_MEM_FAX
EventText: "SI_OAM: FATAL no memory
in SYS_REINIT_FAX_TAB
EventLogEntry from
EventCode
MSG_SI_TO_APPL_NO_FD:
EventText:"Sent not possible:no FD "
Admain_anhang_C.fm
Tables
Event Templates
C-121
C-122
EventLogEntry from
EventCode:MSG_SI_LOGON_
UNKNOWN_SYSTEM_CALLNO
EventText: " callno %s unknown in the
system "
EventLogEntry from
EventCode
MSG_SI_LOGON_CALLNO_NOPHY:
EventText: " callno %s has no Phy port in
the system "
MSG_SI_LOGON_ Warning
UNKNOWN_
SYSTEM_
CALLNO
CALLNO_NOPHY
Callno in Hipath3000 is not

Connected to a physical port.
Callno in Hipath3000 not known.
EventLogEntry from
Callno in Hipath3000 not known
For ISDN subscriber.
EventCode:
MSG_SI_LOGON_UNKNOWN_DSSNO
EventText: "unknown DssNo %s "
UNKNOWN_
DSSNO
Check Conguration hipath3000

with those in
HG1500

with those in
HG1500

with those in
HG1500
Check DL-messages from

Hipath3000.
Check DL-messages from

Hipath3000.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Subevent in Message from device- handler hipath3000 not

Known.
EventLogEntry from
Subevent in DL-message not
known.
EventCode: MSG_SI_DL_NO_KNOWNSUBEVENT
EventText: "unknown download subevent
0x%x"
Description
EventLogEntry from
EventCode:
MSG_SI_MSG_UNKNOWN_PORT
EventText: "SI_port/LEODAT: unknown
subevent %x"
Warning
MSG_SI_DL_NO_
KNOWN-SUBEVENT
MSG_SI_
Warning
UNKNOWN_PORT
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Description
EventLogEntry from
Callno is not active in application. EventType: csevWarning
EventCode:
MSG_SI_VERIFY_CALLNO_NOT_ACTI
VE
EventText: " SI_Port/
CLIENT_VERIFY_IN: number not activet
%d "
EventLogEntry from
Port number can not be connected EventType: csevWarning
to the card.
EventCode:
MSG_SI_VERIFY_UNKNOWN_CARD_
PORT
EventText: "Si_Port/VERIFY_CONF: unknown card_port %d"
MSG_SI_VERIFY_ Warning
UNKNOWN_
CARD_PORT
CALLNO_NOT_
ACTIVE
Port in error state in the

hipath3000.
A31003-H3540-A800-1-7619, 2003-05-02
Check VERIFY
Message.
Check conguratons of
callno

with those in
HG1500

with those in
HG1500
Automatic
Remedy Actions
Actions,
performed by
the Gateway
EventLogEntry from
EventCode:
MSG_SI_LOGON_ERROR_ON_PORT
EventText: " SI_Port/LOGON_CONF:
error_on port %x "
EventText: " callno %s assigned to other

card/port "
EventLogEntry from
Callno is in the Hipath3000 alEventType: csevWarning
Ready given to an other port.
EventCode:
MSG_SI_LOGON_ASSIGN_TO_OTHER
_PORT
ERROR_ON_
PORT
ASSIGN_TO_
OTHER_PORT
EventCode
Admain_anhang_C.fm
Tables
Event Templates
C-123
C-124
Warning
Warning
MSG_SI_HFA_
INVALID_HFA_
INDEX
MSG_SI_HFA_
UNKNOWN_
LEODAT
Warning
MSG_SI_HFA_
UNKNOWN_
LEORLS
EventLogEntry from
EventCode:
MSG_SI_HFA_UNKNOWN_LEODAT
EventText: "SI_vop: unknown LEODAT
subevent %x"
EventLogEntry from
EventCode:
MSG_SI_HFA_INVALID_HFA_INDEX
EventText: "SI_Vop/SUBNO_CONF: invalid vop_index %x"
EventLogEntry from
EventCode:
MSG_ SI_HFA_UNKNOWN_LEORLS
EventText: "SI_Vop: unknown LEORLSSubevent %x"
EventLogEntry from
EventCode:
MSG_SI_PORT_NOPLACE_IN_TABLE
EventText: " SI_Port_check_callno:
si_port_table full "
Warning
MSG_SI_PORT_
NOPLACE_IN_
TABLE
EventLogEntry from
EventCode:
MSG_SI_VERIFY_STATE_NOK
EventText: "si_port_handle_logon_req:
state not ok"
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
STATE_NOK
EventCode
Sub-event in L3-message not

known.
Index for HFA-client to big.
Subevent in LEORLS message

Not possible.
Porttable in SI is to small for

All call number
Client is not in the right state.
Description
Check HFA-DH in
hipath3000.
Check HFA-manager for

HFA-indexs.
Check HFA-DH in
hipath3000.
Change demension of
The table.
Check state in
HG1500 and the
Hipath3000.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
Warning
Warning
Warning
Warning
MSG_SI_HFA_
UNUSED_LW_
EVENT
MSG_SI_HFA_
LEDINFO_PORT_
INVALID
MSG_SI_HFA_
LEDINFO
MSG_SI_HFA_
INVALID_HFA_
INDEX
MSG_SI_HFA_
Warning
UNKNOWN_SUB_
EVENT
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
EventLogEntry from
EventCode:
MSG_SI_HFA_UNKNOWN_SUB_
EVENT
EventText: "SI_vop: HFA-message with
unknown subevent %d"
EventLogEntry from
EventCode:
MSG_SI_HFA_INVALID_HFA_INDEX
EventText: "SI_Vop/SUBNO_REQ: invalid vop_index %x"
EventLogEntry from
EventCode:MSG_SI_HFA_ERROR6
EventText: " led_art=%d
led_gruppe=%d funktion=%d"
EventLogEntry from
EventCode:
MSG_SI_HFA_LEDINFO_PORT_
INVALID
EventText: "SI_vop/XCLED_INFO:
log_port 0x%x invalid"
EventLogEntry from
EventCode:
MSG_SI_HFA_UNUSED_LW_EVENT
EventText: "SI_vop: SAPI-Msg with unused lw_event"
Sub_event in HFA-message not

known.
HFA-index not possible for

Subscriber no
Check DH-HFA in
hipath3000.
Check HFA-index
in HFA manager
And in message
from hipath3000.
Check message
from hipath3000.
Check HFA-DH in
hipath3000.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
LED-Information for port not possible.
LW-event can not be validated.
Description
Admain_anhang_C.fm
Tables
Event Templates
C-125
C-126
EventLogEntry from
EventCode:
MSG_SI_L2STUB_COUDNT_OPEN_
STREAM
EventText: "Stream coudnt be opened
for device %X"
Error in Vxworks-Costream
to open a stream for a device.
Check errorcode in
Vxworks.
Check max number of device.

Interprete error
Code.
Check MAL,to
See why its calling
SI_open
Twice.
See kind of error

Contact owner of
the data.
Tables
Event Templates
Warning
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Device is already opened with the SI_open procedure.
EventLogEntry from
EventCode:
MSG_SI_L2STUB_NO_CLONE
EventText: "Unsupported non-Clone
open!"
Warning
MSG_SI_
L2STUB_
COUDNT_OPEN_
STREAM
EventLogEntry from
EventCode :
MSG_SI_L2STUB_STREAM_
ALREADY_OPEN
EventText: "Stream already open for device %X"
The DL-data are not delivred to

the owner(component).
MSG_SI_
L2STUB_NO_
CLONE
Warning
MSG_SI_
L2STUB_
STREAM_
ALREADY_OPEN
EventLogEntry from
EventCode:
MSG_SI_OAM_NOT_POSSIBLE
EventText: " System data to COMPONENT %l not possible, error %l
Description
EventLogEntry from
Initialisation of L2 not possible
EventCode:
MSG_SI_L2STUB_ERROR_INIT_
DRIVER
EventText: "Critical Error in Initialising L2
driver"
Warning
MSG_SI_MSG_
OAM_NOT_
POSSIBLE
MSG_SI_
Critical
L2STUB_ERROR_
INIT_DRIVER
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Warning
Warning
Critical
Warning
Warning
EventCode
MSG_SI_
L2STUB_OPEN_
OTHER_
STREAM_NOT_
POSSIBLE
MSG_SI_
L2STUB_
UNEXPECTED_
DB_TYPE
MSG_SI_
L2STUB_NO_
ALLOC
A31003-H3540-A800-1-7619, 2003-05-02
MSG_SI_
L2STUB_PORT_
NOT_OPEN
MSG_SI_
L2STUB_
UNKOWN_
SOURCE_PID
EventLogEntry from
EventCode:
MSG_SI_L2STUB_UNKOWN_
SOURCE_PID
EventText: "Source PID not known
(0x%x)"
EventLogEntry from
EventCode:
MSG_SI_L2STUB_PORT_NOT_OPEN
EventText:"Port has not been opened"
EventLogEntry from
EventType: csev Critical
EventCode:
MSG_SI_L2STUB_NO_ALLOC
EventText:"Unable to allocb(%d)\n"
EventLogEntry from
EventCode:
MSG_SI_L2STUB_UNEXPECTED_DB_
TYPE
EventText:"Unexpecteddb_type(0x%x)"
EventLogEntry from
EventCode:
MSG_SI_L2STUB_OPEN_OTHER_
STREAM_NOT_POSSIBLE
EventText: "Unable to open another L2
stream!"
Message from an unkown PID
Port must be open befor transfer

can be done
Nomore memory available.
Description
Type of message
for DLPI not allowed.
Check for error

code of Vxworks
Check hwo is
sending this message.
Check why port is

closed.

matically.
SNMP Trap;
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
C-127
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Warning
Warning
EventCode
MSG_SI_
L2STUB_
UNEXPECTED_
EVENT_CODE
C-128
MSG_SI_SWC_
ERROR
Description
EventLogEntry from
Negative return on SWCEventType: csevWarning
routine : swc_si_if()
EventCode: MSG_SI_SWC_ERROR
EventText: "si_main: TS connection in
SWC not possible,return = %x,lw_port
=%x,tsx,tsr = %x,channel = %x,tei = %x
EventLogEntry from
Eventcode sent from hipat3000
Is not known.
EventCode:
MSG_SI_L2STUB_UNEXPECTED_
EVENT_CODE
EventText: "Unexpected event code (%d)
from SWU"
Check parameter
inconcistence to
SWC.
Check DH in
hipath3000.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
MAGIC / Device Manager Events
A31003-H3540-A800-1-7619, 2003-05-02
Major
Major
Major
Major
Major
MSG_DVMGR_
NO_DEVICE_
TYPE_FOR_
DEVICE
MSG_DVMGR_
NO_DEVICE_ID_
FOR_DEVICE
MSG_DVMGR_
CREATE_FAILED
MSG_DVMGR_
CAN_NOT_
READ_
PERSISTENCY
MSG_DVMGR_
SCN_TASK_
FAILED
Class instance of SCN_TASK

couldnt be created; startup interrupted
The specied persistency le

could not be read
Device object instance of specied

class couldnt be created
No entry found in persistency for

specied device type
Restart system;
Check pers les;

Restart system;
Too less memory!

Restart system;
Check and correct

content of pers le
devmgr.txt
Check and correct

content of pers le
devmgr.txt
Check and correct

content of pers le
devmgr.txt
Check and correct

content of pers le
devmgr.txt
Check and correct

content of pers le
devmgr.txt
Automatic
Remedy Actions
Actions,
performed by
the Gateway
SCN Task create failed
Can not read %s persistency le
%s create failed
No DeviceId for %s Device available in

persistency
No Device Type for %s Device available in Invalid device type in persistancy

persistency
Specied device id is out of valid

range
Major
MSG_DVMGR_
DEVICEID_OUT_
OF_RANGE
The current DeviceId: %d is out of range
Protocol rejected. Device '%u' will be tak- Invalid protocol specied in persisen out of service
tancy
Major
Description
MSG_DEVM_
BINDING_FAILED
Device %u could not be bound to protocol Specied device couldnt be as%d. Device has been taken out of service signed to a protocol and is therefore out-of-service
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
MSG_DEVM_NO_ Major
PROTOCOL_
FOR_DEVICE
EventCode
Startup and Internal Messages
C.2.33
Admain_anhang_C.fm
Tables
Event Templates
C-129
C-130
DeviceId (%x): Got NULL pointer instead Got a NULL pointer to Resource
of Resource!
DeviceId (%x): No container object found! Could not nd a valid object pointer in the global Table.
DeviceId (%x): No protocol manager
found!
DeviceId (%x): No protocolId in message! Could not read protocolId from
persistency le.
DeviceId (%x): If Table init failed, DVMGR Error in system startup; could not
not initialized!
create IfTables
Major
Major
Major
Major
Major
DeviceId (%x): is not a fax deviceId. Could Got a wrong deviceId.

not set fax status.
DeviceId (%x): Amount of congured resources exceeds overall limit.
DeviceId (%x): Unknown AdminState! Ad- Unknown AdminState

minState set to AStateDown
Major
Warning
Information
Check conguration of resources in

devmgr.txt
Restart system; if
condition ongoing
a new APS is necessary
Restart system; if
condition ongoing
a new APS is necessary
Check and correct

content of pers le
devmgr.txt
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Tables
Event Templates
The number of overall resources is

smaller than the number of resources assigned to this device
DeviceId (%x): Startup failed, DVMGR not Error in system startup; could not
initialized!
startup device manager
Major
Could not nd a valid protocol

manager.
Could not nd a valid device pointer in the global Device Table.
DeviceId (%x): No entry in global device

table
Major
Description
MSG_DVMGR_
INTERROR_
DEVID
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
DeviceId (%x): Unknown Device Type!
DeviceId (%x): Not enough memory to

create Resource object!!
DeviceId (%x): Unexpected SUSY id !!!
DeviceId (%x): iAdmCommand: Unexpected value received
DeviceId (%x): id >=
MAX_RESOURCE_NUMBER!
DeviceId (%x): Wrong param from persis- Could not read parameter from
tency le gwglobal.txt!
persistency le.
DeviceId (%x): Device %d can't be creat- Could not create the device. For
ed!
this device no connections are
possible.
DeviceId (%x): Insert in global Device Ta- Insert into the global device table
ble failed!
failed. This device will not be
known to the system.
DeviceId (%x): Shutdown of SCN_Task
failed! Continue with Shutdown.
Major
Minor
Warning
Warning
A31003-H3540-A800-1-7619, 2003-05-02
Warning
Warning
Major
Major
Information
DeviceId (%x): BChannel not found in re- Bchannel could not found within
sources!
resources.
The shutdown of the SCN_TASK

failed. Shutdown will be continued
anyway.
Got a wrong resource.
Got an unexpected command.
Got an unexpected SUSY
Not enough memory to create e

resource.
Got an unknown device type.
Did not nd a free channel.
Check and correct

content of pers le
gwglobal.txt
Check and correct

content of pers le
devmgr.txt
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Warning
DeviceId (%x): No free channel found!
Major
Got a NULL pointer.
DeviceId (%x): Got NULL pointer !!!
Major
Description
MSG_DVMGR_
INTERROR_
DEVID
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Admain_anhang_C.fm
Tables
Event Templates
C-131
C-132
ResourceId (%x):
G711TransparentChannel Indication not
from SCN-side
ResourceId (%x): State
RESOURCE_IN_USE not set!
ResourceId (%x): State
RESOURCE_IDLE not set!
ResourceId (%x): DecreaseResourceCounter() failed
ResourceId (%x): Leg not opened
ResourceId (%x): GOT NULL POINTER
!!!
Warning
Warning
Warning
Warning
Warning
Major
Got a NULL pointer.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Tables
Event Templates
Leg is not opened yet.
Decrease of the resource counter

failed.
Could not change the state.
Could not change the state.
Wrong indication.
ResourceId (%x): No ASCII character de- Wrong digit.

ned for digit %d .
The congured Trunk channels

(Manager E) exceed the number
of licensed B-Channels.
Warning
DeviceId (%x): Congured Trunk Channels exceed licensed B-Channels!
Warning
The congured Trunk channels

(Manager E) exceed the physical
number of B-Channels.
ResourceId (%x): Fax Indication received Wrong device type.

from wrong device
DeviceId (%x): Congured Trunk Channels exceed physical Limit!
Warning
Unknown state of resource.
Got a message for wrong device.
Description
Warning
DeviceId (%x): Unknown resource state!
Warning
MSG_DVMGR_
INTERROR_
RESID
DeviceId (%x): Got a LOGON_TRK_IND

msg for wrong device!
Warning
MSG_DVMGR_
INTERROR_
DEVID
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
Could not connect legs;
FAX_STATUS_ERROR from MSC
Warning
ResourceId (%x): No Dtmf tone dened

for character %c .
Warning
Could not connect legs. TIMEOUT, Faxstatus not changed from MSC
ResourceId (%x): Resource not in state

RESOURCE_IN_USE
Warning
Warning
ResourceId (%x): ChangeState(%d): N/A Change state is not possible due

in state %s
to wrong state.
Warning
MSG_DVMGR_
MSCERROR_
RESID
ResourceId (%x): Leg already in a connection
Warning
ChannelId (%x): Channel out of range!
ResourceId (%x): new state not expected! Got unexpected state.
Warning
Warning
ResourceId (%x): Number of licenses out Wrong codec amount.

of range!
Warning
MSG_DVMGR_
INTERROR_
CHNID
ResourceId (%x): Codec value out of

range!
Warning
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Legs could not be connected, because of FAX_STATUS_ERROR

from MSC.
Legs could not be connected, because of TIMEOUT.
Wrong channel number.
Wrong character.
Wrong state.
The own or the partner leg is already connected. Reject order.
Unknown codec.
Did not nd a codec. Calls are not

possible.
ResourceId (%x): No Codecs available!
Warning
Description
MSG_DVMGR_
INTERROR_
RESID
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Admain_anhang_C.fm
Tables
Event Templates
C-133
C-134
Warning
Close of %s Leg failed; MSC Error Code Proper close of payload leg failed;
%d
closed anyway
Disconnect of payload legs failed;

MSC responds with specied error
code
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Tables
Event Templates
Disconnect of %s Leg failed; MSC Error

Code %d
Connect on the Fax channel failed,

because either of wrong state or
wrong mode.
MSG_DVMGR_
CLOSE_LEG_
FAILED
Connect of payload legs failed;

code
Warning
Connect of %s Leg failed; MSC Error

Code %d
Partner Leg has a wrong Leg

Type, therefore the connect will not
performed.
MSG_DVMGR_
DISCONNECT_
LEGS_FAILED
Warning
MSG_DVMGR_
CONNECT_LEGS
_FAILED
Connect of %s Leg failed; Partner not a

%s Leg
Connect on %s Leg failed; State %d

Mode %d
Warning
MSG_DVMGR_
CONNECT_
WRONG_LEGS
Update of %s Leg failed; MSC Error Code Data of payload leg couldnt be up%d
date; MSC responds with specied error code
State of the resource is in an unexpected state. State will not

changed, but returns false to the
caller.
Warning
Warning
MSG_DVMGR_
UPDATE_LEG_
FAILED
Open of %s Leg failed; Resource State

%d
MSG_DVMGR_
CONNECT_
WRONG_RES_
STATE
Warning
MSG_DVMGR_
OPEN_WRONG_
RES_STATE
Open of %s Leg failed; MSC Error Code Payload leg couldnt be opened;
%d
code
Description
ListenForConnect on %s Leg failed; State Listen on the Fax channel failed,

%d Mode %d
because either of wrong state or
wrong mode.
Warning
MSG_DVMGR_
OPEN_LEG_
FAILED
MSG_DVMGR_
Warning
LISTEN_WRONG_
RES_STATE
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
LEG Management Messages
Admain_anhang_C.fm
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
Major
Major
MSG_SCN_
UNEXPECTED_
L2_MSG
MSG_SCN_
OPEN_ADMFD_
FAILED
Major
MSG_SCN_
OPEN_STREAM_
FAILED
Opening communication path to

layer2 failed
Restart system;
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Open stream failed on device %d
Poll returned unexpected value -1
Major
MSG_SCN_
POLL_FD
Polling failed.
Operation on stream failed for device %u Operation on the given stream

failed.
Open of the admin stream failed.
Layer2 has sent an unexpected

DLPI message; only logging
Can not read the message from

the given device.
MSG_SCN_
Major
OPERATION_ON_
STREAM_FAILED
Open admin stream failed
Unexpected layer2 message on device

%d
Reading message for device %d failed
Major
MSG_SCN_GET_
LAPDMSG_FAILE
D
Can not read the message from

the admin stream.
Reading message from admin stream

failed
Add parameter failed for device %u mes- Add parameter failed.

sage %s
Layer2 has sent an error message; only logging
MSG_SCN_GET_ Major
ADMMSG_FAILED
Major
MSG_SCN_ADD_
PARAMETER_
FAILED
L2 Error: %d Primitive: %d received on

Device: %d
Description
Device %d not in devicelist of SCN_TASK Given device not found in devlist.
Major
MSG_SCN_
ERROR_L2_MSG
MSG_SCN_DEV_ Major
NOT_IN_DEVLIST
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Layer 2 Communication Messages
Admain_anhang_C.fm
Tables
Event Templates
C-135
C-136
DEVMGR DevId: %d Layer2 In-Service
DEVMGR DevId: %d Layer2 Out-Of-Ser- Message from SI is missing, there- SNMP Trap;
vice; Waiting for DL_CONNECT_IND
fore the Layer 2 does not come up.
DEVMGR DevId: %d Layer2 Out-Of-Ser- SI takes Layer 2 out of service. No SNMP Trap;
vice; Initiated by Layer2
more calls possible for this device.
DEVMGR DevId: %d Layer2 Out-Of-Ser- Administrator takes the Layer 2 out SNMP Trap;
vice; Initiated by Application/Operator
of service. No more calls possible
for this device.
Information
Critical
Critical
Critical
MSG_DVMGR_
LAYER2_
SERVICE_TRAP
Layer 2 is up. Connections for this SNMP Trap;

device possible.
Binding administration communication path failed
Bind for admin stream failed !
Binding layer2 communication

path failed
Got an unexpected event on the

given device.
None;
None;
None;
None;
Restart system;
Restart system;
Automatic
Remedy Actions
Actions,
performed by
the Gateway
MSG_SCN_BIND_ Major
_ADMFD_FAILED
Unexpected poll event on device %u
Description
Bind for device: %d failed
Major
MSG_SCN_
UNEXPECTED_
POLL_EVENT
MSG_SCN_BIND_ Major
FAILED
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
Information
Information
MSG_ASP_INFO
MSG_ASP_INFO
EventCode: MSG_ASP_INFO
EventText: ,Booting DSP module #<nr>
done.
EventText: ," Loading ...
EventText: ,Booting DSP module #<nr>
with <DSP SW Version > from < date>
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Indeterminate
EventCode
MSG_ASC_
ERROR
EventLogEntry from
EventType: csev Indeterminate
EventCode: MSG_ASC_ERROR
EventText: DSP channel not initialized
.
Major ASC Events
Information
MSG_ASP_INFO
C.2.35
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Important Platform SW Status Events
EventCode
C.2.34
Possibly a Conguration Problem
Description
Comes up during startup,

marks the successful end of DSP
Module Boot Process
Comes up during startup

marks the beginning of DSP-SW
download
Comes up during startup,

marks the beginn of DSP Module
Boot Process
Description
Verication of ASC
conguration in
Gateway
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
C-137
C-138
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Critical
MSG_ASP_
ERROR
Within RG2500 different DSP

modules (DDM1, DDM2) plugged
in
Possibly a RTP packet of invalid
length received from LAN
Out of streams memory condition,
something is blocked at the DSP
side
DSP Error 7,<nr>,0,0,0,0...

DSP Error 9,<nr>,0,0,0,0...
Description
EventCode: MSG_ASP_ERROR
EventText: Hardware Conguration invalid: <error string>
Major ASP Events
EventCode
C.2.36
Comes up on the
console only
Comes up on the
console only
Check the DSP

modules on the
main board
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Value
-32
-31
-30
-29
-28
-27
-26
-25
-24
-23
-22
-21
-20
-19
-18
-17
-16
-15
-14
-13
-12
ASC_RESOURCE_ALREADY_USED
ASC_NO_MORE_DSP_RESOURCES
ASC_ENTRY_NOT_FOUND
ASC_RTCP_ERROR
ASC_INVALID_MSG
ASC_INVALID_MSG_BOX
ASC_NOT_READY
ASC_TIMEOUT_ERROR
ASC_DSP_ERROR
ASC_CONNECTION_ERROR
ASC_NO_CONNECTION
ASC_PARAM_MISSING
ASC_VXWORKS_ERROR
ASC_IOCTL_ERROR
ASC_WRONG_LEG_TYPE
ASC_STREAMS_ERROR
ASC_INVALID_MSG_TYPE
ASC_INVALID_STATE
ASC_TRACE_ERROR
ASC_NETWORK_ERROR
ASC_WRONG_PAR
ASC Error Codes
Error Code
C.2.37
A31003-H3540-A800-1-7619, 2003-05-02
wrong or unsufcient parameters
error with networking
Error from Trace server
Automatic
Remedy Actions
Actions,
performed by
the Gateway
wrong connection state
Unknown message type
Error returned by streams functions
Unknown Leg Type
IOCTL sent to ASP failed
general err. from VxWorks calls
Parameters missing
searched connection could not be found
connect() or accept() failed in TCP socket
problems with DSP driver(s)
a timeout condition occured
ASC is not ready, i.e. no Cong Data available
Invalid message box
Invalid message received
RTCP error
The entry was not found in ASC internal Tables
The maximum number of DSP channels is already

used
The addressed resource is already in use
Description
Admain_anhang_C.fm
Tables
Event Templates
C-139
Value
-11
-10
-9
-8
-7
-6
-5
-4
-3
-2
-1
Error Code
ASC_NO_MEM
C-140
ASC_SOCKET_ERROR
ASC_OPEN_FAX_ERROR
ASC_CLOSE_FAX_ERROR
ASC_INVALID_TASK_ID
ASC_HANDLE_NOT_ASSIGNED
ASC_INDEX_NOT_ASSIGNED
ASC_NO_FREE_ENTRY_LEFT
ASC_ENTRY_NOT_ALLOCATED
ASC_INVALID_INDEX
ASC_ERROR
Generel ASC error
Internal ASCtable error
Access to an entry which doesnt exist
All available channels taken
Index is not assigned in ASC leg tables
Handle is not assigned in ASC leg tables
Invalid Task ID
Error when closing a fax driver
Error when opening a fax driver
Error from socket interface
not enough memory
Description
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Information
Information
Information
Critical
Critical
EventCode
MSG_IPF_
STARTED
MSG_IPF_
STOPPED
MSG_IPF_ON_
OFF
MSG_IPF_
PARAMETER
MSG_IPF_NO_
OF_RULES
IP Filter Events
Information
MSG_ASP_INFO
C.2.39
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Automatic
Remedy Actions
Actions,
performed by
the Gateway
When reading in the mentioned

rule is was not possible to read in
the mentioned parameter.
IP Filter was switched ON/OFF.
A IP Filter object has been destructed.
A IP Filter object has been created.
Description
verify LAN Trafc
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Comes up every thenth time if

FEC Sender
FEC sender is blocked by colliRestart
sions or high trafc. Some Packets
will be lost during restart of FEC
Description
EventText: Number of rules is bigger than The number of rules that have
the maximum of %d.
been entered is bigger than the
predened maximum.
EventText: Rule number %d: missing parameter %s.
EventText: IP Filter is switched %s.
EventText: IP Filter stopped.
EventText: IP Filter started.
EventLogEntry from
EventType: csev Information
EventText: fec restarts because of high
trafc on LAN Restart counter <nr>
Minor ASP Events
EventCode
C.2.38
Admain_anhang_C.fm
Tables
Event Templates
C-141
C-142
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Information
Information
Information
Critical
Critical
Critical
Critical
MSG_MAF_
STARTED
MSG_MAF_
STOPPED
MSG_MAF_ON_
OFF
MSG_MAF_
PARAMETER
MSG_MAF_NO_
OF_RULES
MSG_MAF_
NETBUFFER
MSG_MAF_
ETHERNET_
HEADER
EventText: Cannot nd ethernet header of An error occured when trying to

IP packet.
access the ethernet header of an
IP packet.
EventText: IP packet seems to be corrupt. An error occured when trying to

access the memory area where
the IP packet should be.
When reading in the mentioned

rule is was not possible to read in
the mentioned parameter.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
MAC Address Filter was switched ON/OFF.
A MAC Address Filter object has

been destructed.
A MAC Address Filter object has

been created.
Description
EventText: Number of rules is bigger than The number of rules that have
the maximum of %d.
been entered is bigger than the
predened maximum.
EventText: Rule number %d: missing parameter %s.
EventText: MAC Address Filter is

switched %s.
EventText: MAC Address Filter stopped.
EventText: MAC Address Filter started.
MAC Filter Events
EventCode
C.2.40
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Critical
Critical
Critical
Critical
Information
Information
Information
Information
Minor
MSG_IPSTACK_
NAT_ERROR
MSG_IPSTACK_
SOH_ERROR
MSG_IPSTACK_
ERROR
MSG_IPSTACK_
LOW_MEM
MSG_IPSTACK_
ETH0_LINK_
DOWN
MSG_IPSTACK_
ETH1_LINK_
DOWN
MSG_IPSTACK_
ETH0_LINK_UP
MSG_IPSTACK_
ETH1_LINK_UP
MSG_IPSTACK_
INVALID_PARAM
Critical error occurred during net

address translation
Description
Error occurred in IP-Stack
A31003-H3540-A800-1-7619, 2003-05-02
The Ethernet Link of port 1 is down -
The Ethernet Link of port 0 is down -
Event Text: IP-Stack invalid parameter

%s, value %s;
EventText: Ethernet Link down of port 1;

%s
IP-Stack receives invalid parameter.
The Ethernet Link of port 1 is up
Automatic
Remedy Actions
Actions,
performed by
the Gateway
EventText: Ethernet Link up of port 0; %s The Ethernet Link of port 0 is up; -
EventText: Ethernet Link down of port 1
EventText: Ethernet Link down of port 0
EventText: IP-Stack reaches low memory Low memory state in IP-Stack
EventText: Error occurred in IP-Stack
EventText: Error occurred in Socket Han- Error occurred in Socket Handler

dler
EventText: NAT Error: %s
IP Stack Events
EventCode
C.2.41
Admain_anhang_C.fm
Tables
Event Templates
C-143
C-144
critical
MSG_DELIC_
ERROR
EventText: delic mailbox fatal error; reboot delic.
EventLogEntry from
EventCode:MSG_DELIC_ERROR
A reboot after delic mailbox

fatal error
(not another function).
Description
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
Information
Warning/ Major
MSG_TESTLW_
INFO
MSG_TESTLW_
ERROR
EventLogEntry from
EventType: csevWarning/ csevMajor
EventCode:
MSG_TESTLW_ERROR
EventText: Error: %p
EventLogEntry from
EventCode:
MSG_TESTLW_INFO
EventText: Info: %p
Test Loadware Events
EventCode
C.2.43
Errors during initialization, receiving an unknown message, buffer

errors, timer errors
Information about TESTLW functions.

(Successful initialization, )
Description
* Nicht mglich, da die fehlerhafte Mailbox des Delics, die Schnittstelle zum System nicht bedienen kann.
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
DELIC Events
EventCode
C.2.42
Not necessary
Not necessary
Automatic
Remedy Actions
Actions,
performed by
the Gateway
*Hicom is not
informed

matically.
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
A31003-H3540-A800-1-7619, 2003-05-02
Information
Warning
MSG_FAXCONV_
INFO
MSG_FAXCONV_
ERROR
Information
Warning/ Major
Information
MSG_T90_INFO
MSG_T90_
ERROR
MSG_X25_INFO
Major
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventLogEntry from
EventCode:
MSG_X25_INFO
EventText: Info: %p
EventLogEntry from
EventCode:
MSG_T90_ERROR
EventLogEntry from
EventCode:
MSG_T90_INFO
EventText: Info: %p
EventLogEntry from
EventType: csevMajor / csevWarning
EventCode:
MSG_FAXCONV_ ERROR
EventLogEntry from
EventCode:
MSG_FAXCONV_INFO
EventText: Info: %p
Fax Converter, HDLC, X.25 Events
EventCode
C.2.44
Information about X.25 Protocol

Module
(Successful initialization, or opening)

errors
Information about T.90 Protocol

Module
Errors during opening Fax Converter Module

errors
Information about Fax Converter

Module.
Description
Not necessary
Not necessary
Not necessary
Not necessary
Not necessary
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
C-145
C-146
Information
Warning/ Major
Information
MSG_X75_INFO
MSG_X75_
ERROR
MSG_MSP_
HDLC_INFO
Warning/ Major
Warning/ Major
MSG_X25_
ERROR
MSG_MSP_
HDLC_ERROR
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
EventCode
EventLogEntry from
EventCode:
MSG_MSP_HDLC_ERROR
EventLogEntry from
EventCode:
MSG_MSP_HDLC_INFO
EventText: Info: %p
EventLogEntry from
EventCode:
MSG_X75_ERROR
EventLogEntry from
EventCode:
MSG_X75_INFO
EventText: Info: %p
EventLogEntry from
EventCode:
MSG_X25_ERROR

errors, errors during opening
HDLC Driver ...
Information about HDLC Driver


errors
Information about X.75 Protocol

Module

errors
Description
Not necessary
Not necessary
Not necessary
Not necessary
Not necessary
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
EventLogEntry from
The other errors, e.g. OAM returns display
an error code
EventText: Internal Error in IP Accounting
(code: %d %s)
EventLogEntry from
EventText: Wrong internal message (origin: %s, code %d)
EventLogEntry from
EventText: IP Accounting data reached
upper mark, it shall be read
EventLogEntry from
EventText: IP Accounting data has overown
MSG_IPACCSRV_ Major
INTERNAL_
ERROR
MSG_IPACCSRV_ Warning
MESSAGE_
ERROR
A31003-H3540-A800-1-7619, 2003-05-02
MARK_REACHED
OVERFLOW
IP Counting table is overown

Data is getting lost
IP Counting table upper mark

reached
SNMP TRAP
SNMP TRAP
Received unknown message from display

IP Counting or from IP Accounting
Client
Application doesnt get requested reboot

memory
EventLogEntry from
EventText: Memory allocation failed
If IP Accounting information shall be

processed, logon
IP Accounting client
If IP Accounting information shall be

processed, logon
IP Accounting client
Automatic
Remedy Actions
Actions,
performed by
the Gateway
A fatal error occurred at the socket reboot

interface
Description
MSG_IPACCSRV_ Major
MEMORY_ERROR
EventLogEntry from
EventText: Socket Error: %d (%s)
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
IP Accounting Events
MSG_IPACCSRV_ Major
SOCKET_ERROR
EventCode
C.2.45
Admain_anhang_C.fm
Tables
Event Templates
C-147
C-148
Severity
(Information,
Warning, Minor,
Major, Critical,
Cleared,
Indeterminate)
MSG_IPACCSRV_ Information
LOGON
EventCode
Description
EventLogEntry from
Logon is done successfully or inEventType: csev Information
successfully
EventText: Login of IP Accounting client:
%s
#### = Text, either done or rejected,
wrong user/password or rejected, wrong
IP Address or rejected, wrong number of
version
display
If rejected, look for

reason
Automatic
Remedy Actions
Actions,
performed by
the Gateway
Admain_anhang_C.fm
Tables
Event Templates
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_D.fm
Appendix
Suggested LAN Solutions
Appendix
The administration of linked networks in WAN/LAN is a highly technical procedure. When performing this task, the network administrator will always find configuration problems which need
to be corrected quickly and efficiently. This appendix is designed to help you.
D.1
D.1.1
BNC Network at a Twisted Pair
Extension of BNC network segment (max. 185 m) by 100 m with twisted pair.
10 MB Ethernet HUB with BNC port
TCP/IP and/or IPX/SPX
1
26
3
4
5
78
09
ABC
DEF
ABC
DEF
GHI
JKL
MNO
GHI
MNO
PQRS
TUV
WXYZ
PQRS
TUV
10 MB HUB with BNC port

New PCs can be connected to the
twisted pair
HiPath 3000
Ethernet LAN twisted pair
Figure D-1
Ethernet LAN BNC 10 MB
Connection of BNC Network at Twisted Pair to HiPath HG 1500
Advantage:
Simple expansion of BNC network, e. g. 3COM OfficeConnect
Hub TP 4 Combo (4xRJ-45, 1xAUI, 1xBNC, unmanaged hub)
Hub 8/TPC (8xRJ-45, 1xBNC, unmanaged hub)
Hub TP16C (16xRJ-45, 1xBNC, unmanaged hub)
A31003-H3540-A800-1-7619, 2003-05-02
D-1
Admain_anhang_D.fm
Appendix
D.1.2
3COM Dual Speed hub
HiPath HG 1500 in 100 MB networks

3COM Dual Speed hub solution
HiPath 3000
1
26
3
4
5
78
09
ABC
DEF
ABC
DEF
GHI
JKL
MNO
GHI
MNO
PQRS
TUV
WXYZ
PQRS
TUV
Ethernet LAN 10/100 MB
Ethernet LAN 100 MB
Ethernet LAN 10 MB
Using a hub with automatic recognition for every

100 MB and 10 MB port
Figure D-2
Example: 3COM SuperStack II Dual Speed
Hub 500 TP 12 port (12 RJ-45, stackable, manageable)
Hub 500 TP 24 port (12 RJ-45, stackable, manageable)
D-2
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_D.fm
Appendix
D.1.3
Solution with a Switch
HiPath HG 1500 in 100 MB networks

Solution with switch
HiPath 3000
1
29
3
4
75
8
06
ABC
DEF
ABC
DEF
GHI
JKL
MNO
GHI
MNO
PQRS
TUV
WXYZ
PQRS
TUV
Ethernet LAN 100 MB
Ethernet LAN 10 MB
Using a switch with 100MB and 10MB ports

Figure D-3
Switch with 100 MB and 10 MB Ports
Example: Siemens HiNet
WS 4100 (12 port 10MB, 2 port 100 MB)
WS 4400 (24 port 10MB, 2 port 100 MB, managed)
WS 4700 (24 port Autosense 10/100 MB)
or 3COM OfficeConnect
Switch 140M (4x10/100 BaseT, 1x100BASE-TX) DCF:3C16730-ME
Switch 280 (8x10/100 BaseT, 2x100BASE-TX) DCF:3C16732-ME
>
It is always advisable to use switches for Voice over IP connections to keep voice
connection interference by other data loads in the LAN to a minimum.
We recommend using switches that support Quality of Service: this ensures the necessary prioritization of voice packets over data and improves the quality of voice
connections (see also the Technical Description manual).
A31003-H3540-A800-1-7619, 2003-05-02
D-3
Admain_anhang_D.fm
Appendix
Utility Programs for TCP/IP Diagnostics
D.1.4
HiPath HG 1500 in Token Ring Networks
Routing via network server (Token Ring > Ethernet 10/100 MB)
Use of an additional 10/100 MB Ethernet network card in the server. (NT Server 3.51/ 4.0, Netware Server 3.12 / 4.X).
Token Ring network card solution
TCP/IP and/or IPX/SPX
1
26
3
4
5
78
09
ABC
DEF
ABC
DEF
GHI
JKL
MNO
GHI
MNO
PQRS
TUV
WXYZ
PQRS
TUV
HiPath 3000

Token Ring
Figure D-4
D.2
Server with an additional

10/100 MB Ethernet network card
HiPath HG 1500 in Token Ring Networks
Any operating system provides tools designed for finding faults in a TCP/IP environment which
do not have an obvious explanation. As each operating system includes its own tools and corresponding command parameters, only the main Microsoft operating system functions are described here. Other tools for UNIX-based operating systems are described in detail in RFC
1147. Special parameters are contained in the Help for the corresponding operating system
and can normally be queried by entering <Command> -?
D.2.1
ping
The tool most often used is probably the PING command. This command allows you to check
whether a computer in the network can be reached, i.e whether communication with that computer is possible. An ICMP ECHO message is sent to the computer and then returned to the
sender. If the answer reaches the sending computer, communication with the specified computer is possible. Most variants of the PING command produce connection statistics.
D-4
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_D.fm
Appendix
Syntax for Windows operating systems:

:
ping <Host> [<Parameter>]

<Host>
Contains the destination address or the host name of the destination computer
<Parameter>
-t
Uninterrupted transfer of test packets to the computer. Normally only 4 test

packets are transferred.
-a
IP addresses are resolved to host names.
-n <number>
Sends <Number> test packets to the computer.
-l <size>
Sends test packets with <Size> bytes
-i <TTL>
Number of router hops allowed for one packet. The counter is set to a starting value by the sender and decremented by each router that forwards the
packet.
-w <timeout>
Timeout in milliseconds to wait for each reply. If this time elapses, a timeout message appears. This value is set by default to 1000 (1s). It is advisable to set this value to 5000 (5s) or 10000 (10s) in the case of slow connections such as via modem or GSM. If the reply takes more than 1
second, a timeout message will be received even though a connection is
possible.
Example:
Check connection to local computer. The local computer can normally be reached under the
loopback address 127.0.0.1 and the name localhost.
C:\>ping localhost
PING is executed for the local host [127.0.0.1] with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Messages:
If the remote computer does not reply, the error can be deduced from the messages.
A31003-H3540-A800-1-7619, 2003-05-02
D-5
Admain_anhang_D.fm
Appendix
Invalid IP address (unknown host):

The host name could not be converted to a valid IP address. This message is generated
when the DNS server cannot be reached or is out of service. This message is only output
when the host is addressed using a name.
Destination host not available (network unreachable):

There are no valid routes to the destination system. The destination address could not be
reached, as a gateway is out of service or was not correctly specified on the local host.
Timeout:
The computer has a route to the destination computer but there is no reply. The message
reaches the destination host, but cannot be returned. This error is caused by incorrect routing of the destination computer.
D-6
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_D.fm
Appendix
D.2.2
ipconfig
The ipconfig program is a quick way of querying the TCP/IP network configuration. In this
way you can display IP addresses, netmasks, gateways and network card statistics. It also enables IP addresses assigned via DHCP to be released or renewed.
ipconfig [<Parameter>]
<Parameter>
/all
Shows details of the network configuration. This includes the host

name, DNS servers used, MAC addresses of each network adapter
and DHCP information.
/release [Adapter]
Releases the IP address assigned via DHCP at the adapter.
/renew [Adapter]
Assigns a new IP address to the adapter via DHCP.
If no adapter is specified under the parameters release and renew, all IP addresses at all
adapters assigned via DHCP will be released or re-assigned.
Example:
Detailed query of current configuration:
C:\>ipconfig /all
Windows NT IP Configuration
Host Name ...............:
myhost.Siemens.de
DNS Server...............:
192.168.50.23
192.168.50.160
Node Type ...............:
Broadcast
NetBIOS Scope ID .....:

IP Routing Enabled.....:
No
WINS Proxy Enabled.....:
No
NetBIOS Resolution Uses DNS:
Yes
A31003-H3540-A800-1-7619, 2003-05-02
D-7
Admain_anhang_D.fm
Appendix
Ethernet adapter El90x2:

Description..............:
Physical Address.........:
DHCP Enabled.............:
IP Address...............:
Netmask..................:
Default Gateway..........:
3Com 3C90x Ethernet adapter

00-10-5A-DD-56-55
No
192.168.129.1
255.255.255.0
Ethernet adapter El90x1:
D-8
Description..............:
3Com 3C90x Ethernet adapter
Physical Address.........:
00-10-5A-37-26-B1
DHCP Enabled.............:
Yes
IP Address...............:
192.168.14.6
Netmask..................:
255.255.255.0
Default Gateway..........:
192.168.14.1
DHCP Server..............:
192.168.11.103
Lease Supplied....... ...:
Tue, 17.08.1999 08:43:30
Lease Expires............:
Tue, 19.01.2038 04:14:07
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_D.fm
D.2.3
Appendix
nslookup
An IP address can be assigned via a host name. This assignment of name and IP address is
stored in the DNS server (DNS = Domain Name Server). The command nslookup can be
used to query data that was saved for a specific host in the DNS server. By entering the command nslookup in the MS-DOS prompt, the program tries to contact the DNS server provided
in the network. If a name is queried, the corresponding IP address is returned. Conversely, if
an IP address is queried, the host name is returned. If neither the IP address nor the host name
is stored in the DNS server, a corresponding error message is output.
The ping command message Invalid IP address indicates that the host name specified
cannot be converted into an IP address. This occurs when the DNS server is out of service or
the entry does not exist. This requires that the DNS servers are entered in the network configuration and can be addressed via network.
nslookup can be used to query various entries (records) on the DNS server. Once the program has been started, the following entries can be used to query the corresponding data.
set Type=<Type>
<Type>
a
Address entries
any
All entries
mx
Mail Exchanger entries
ns
Name Server entries
soa
Start of Authority entries
hinfo
Host Info entries
axfr
All entries in a single area
txt
Text entries

nslookup <Host>
<Host>
Example:
C:\>nslookup localhost
Server: ns.domain.com
Address: 192.168.0.1
Name: localhost
A31003-H3540-A800-1-7619, 2003-05-02
D-9
Admain_anhang_D.fm
Appendix
Address: 127.0.0.1
The host localhost has the IP address 127.0.0.1.
D-10
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_D.fm
D.2.4
Appendix
hostname
The command hostname returns the name of the local computer. Unlike other operating systems, in Microsoft operating systems the host name cannot be changed using this command.
Example:
C:\>hostname
localhost
A31003-H3540-A800-1-7619, 2003-05-02
D-11
Admain_anhang_D.fm
Appendix
D.2.5
netstat
The command netstat is used to check existing connections and configured routes, and returns detailed statistics and information on individual network interfaces. Besides the routing
table, the most frequently used netstat function is the query feature, which ascertains which
connections exist at the local computer as well as the status of these connections.
netstat [<Parameter>] [<Interval>]
<Parameter>
-a
Displays all connections, i. e. listening applications such as a Telnet server are

also displayed.
-e
Displays Ethernet statistics
-n
Displays IP addresses instead of host names
-p <Proto>
Displays connections established via the <Proto> protocol
-r
Displays the routing table, which can also be displayed using route print.
-s
Displays statistics for each protocol
<Interval>
Repeats the display after <Interval> seconds
Example:
Queries all connections in IP address format (abbreviated)
C:\>netstat -a -n
Active Connections
Proto
Local address
Remote address
Status
TCP
0.0.0.0:25
0.0.0.0:0
LISTENING
TCP
0.0.0.0:80
0.0.0.0:0
LISTENING
TCP
192.168.129.3:110
192.168.129.1:1037
ESTABLISHED
TCP
192.168.129.3:23
192.168.129.2:1038
ESTABLISHED
....
....
....
....
D-12
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_D.fm
Appendix
TCP
192.168.129.3:1031 192.168.129.1:80
ESTABLISHED
....
....
UDP
0.0.0.0:25
*:*
UDP
0.0.0.0:80
*:*
....
IP connections and their statuses can be displayed using this table. Before explaining this example in more detail, we will briefly discuss the variables.
<Proto>
Indicates the protocol used for the communication. In this case, Windows only distinguishes between TCP and UDP. Unfortunately, certain servers which only operate via a single protocol are displayed
both as TCP and as UDP servers. This prevents accurate determination of the actual protocol in use.
<Local address>
This indicates the local address which has established a connection

or is listening for a connection. The local address and the remote address are displayed in the format
<IP address>:<Port number>.
<Remote address>
This indicates the remote address which has established a connection or to which a connection has been established.
<State>
Shows the current state of the connections:
ESTABLISHED
The local computer has set up a connection to a server. In this case

the local computer is a client.
LISTENING
The local computer is ready to accept a connection. In this case the

local computer is a server.
SYN_SENT
The local computer signals to the server that it would like to establish
a connection.
SYN_RECEIVED
The local computer where the server is running has received a

SYN_SENT signal, i. e. the client would like a connection to be established.
FIN_WAIT_1
The local computer would like to clear down the connection to the
server.
TIME_WAIT
The local computer is waiting for server confirmation that the connection is to be terminated.
CLOSE_WAIT
The local computer where the server is running has received a

FIN_WAIT_1 signal, i. e. the client would like a connection to be
cleared down.
A31003-H3540-A800-1-7619, 2003-05-02
D-13
Admain_anhang_D.fm
Appendix
FIN_WAIT_2
The local computer has received confirmation from the server to

clear down the connection.
LAST_ACK
The server has sent confirmation that the connection is to be cleared

down.
CLOSED
The server has received client confirmation that the connection has
been cleared down.
A computer can be both a client and a server at the same time. This is the case, for example,
where the local computer is connected to its own server. This is possible using the loopback
interface 127.0.0.1. If, for example, a Telnet server is running on the local computer, a Telnet
session can be opened on the local computer using the command telnet localhost.
In order to determine which data can be collated using the above example, we will now explain
the procedure step by step.
Proto
Local address
Remote address
Status
TCP
0.0.0.0:80
0.0.0.0:0
LISTENING
TCP
0.0.0.0:25
0.0.0.0:0
LISTENING
The first two entries are in the LISTENING state, i. e. two programs (servers) have been started on the local computer, both of which are waiting for a client to establish a connection with
them. Both are connected to the IP address 0.0.0.0. This IP address indicates that the server
is connected to all available network interfaces. Even if only one network card is installed, this
already has two interfaces, i.e the local network card (192.168.129.3) and the loopback interface 127.0.0.1 which is installed as standard by Windows. In this example, a HTTP server
(Port 80) and an SMTP server (Port 25) are running on the local computer. In order to determine whether the network card is working correctly, send a test ping from the local computer,
e. g. ping 192.168.129.3. Any error message triggered by this test indicates an incorrectly
configured network interface. If you wish to test the connection to the local HTTP server for
example , simply use your Web browser and enter the URL http://127.0.0.1 or http:/
/192.168.129.3. Entering telnet localhost 25 or telnet 192.168.129.3 25 allows a connection to be established to the local SMTP server. In this case, the port (i. e. the application) is
specified using 25.
The next three entries are all active connections. These can be established either from the local
to the remote computer, or from the remote to the local computer.
Proto
Local address
Remote address
Status
TCP
192.168.129.3:1037
192.168.129.1:110
ESTABLISHED
TCP
192.168.129.3:1038
192.168.129.2:23
ESTABLISHED
TCP
192.168.129.3:80
192.168.129.1:1039 ESTABLISHED
D-14
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_D.fm
Appendix
In order to distinguish between an incoming and an outgoing connection, the entries contained
in the LISTENING state (server) are required. To do this, you need to check whether the port
specified for the local computer is running on the local computer itself. The first line shows port
1037. This port is not running as a server (LISTENING) on the local computer
(192.168.129.3). Thus this must be a connection from the local computer to a remote computer
(192.168.129.1) with the port 110 (POP3). In other words, the local computer is in the process
of downloading its e-mails from the POP3 server.
The second entry must also be an outgoing connection, as it is also not in the LISTENING
state on the local computer. The local computer has therefore set up a connection to the computer 192.168.129.2 and port 23 (Telnet). This means that the local computer has opened
a Telnet session on the remote PC.
In the third entry, the local port 80 (HTTP) corresponds to that of a server. Thus the remote
computer 192.168.129.1 is in the process of opening Web pages on the local computer.
A31003-H3540-A800-1-7619, 2003-05-02
D-15
Admain_anhang_D.fm
Appendix
D.2.6
nbtstat
This utility program allows connections which use the NetBIOS over TCP/IP protocol (WINSClient(TCP/IP)) to be tested. In the NetBIOS over TCP/IP protocol, the NetBIOS packet is
packaged in a TCP/IP packet and then unpacked again on the remote side. This is necessary
because NetBIOS cannot be routed like TCP/IP. As Windows drives can only be enabled via
NetBIOS, such enablements must be packaged in TCP/IP in order to be transferred to other
physical networks. For this purpose, Windows creates a NetBIOS name cache which can also
be created manually. IP addresses are resolved in a table as computer names. This file is
called lmhosts and is located in either the system directory or a system subdirectory, depending on the operating system
Win95/98:
%systemroot%
WinNT/2000:
%systemroot%\system32\drivers\etc
In these directories, Windows provides various test files which can be used as samples. The
structure of each test file is explained. These files have the extension sam. In this case, the file
is called lmhosts.sam. If this lmhosts file does not already exist, it can simply be copied to
lmhosts and edited.
nbtstat [<Parameter>]
<Parameter>
-a <Host Name>
Returns the name table for the computer specified under <Host Name>
-A<IP address>
Returns the name table for the computer specified under <IP Address>
-c
The NetBIOS Name Cache is listed with NetBIOS names and corresponding IP addresses
-n
Lists all local NetBIOS names used
-R
Deletes the NetBIOS Name Cache and reloads the file LMHOST.
-r
Lists the names which have been resolved for the Windows networks
-S
Shows client and server connections as IP addresses.
-s
Shows client and server connections and resolves the IP addresses into
names.
D-16
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_D.fm
D.2.7
Appendix
route
In order to interconnect several TCP/IP networks, you will need to configure routing. Without
routing, it is impossible to leave the local network. Note when routing that the gateway which
connects the local network to other networks must be located in the same TCP/IP network as
the local computer.
route <Command> <Destination> <Netmask> <Gateway> [metric <Hops>]
[<Parameter>]
<Command>
print
Displays the current routing table
add
Adds a new route
delete
Deletes an existing route
change
Modifies an existing route
<Destination> Indicates the destination host or destination network reachable via the <Gateway>.
<Subnet>
Specifies the subnet mask.
<Gateway>
Indicates the IP address of the gateway via which the IP address specified under <Destination> can be reached.
<Hops>
Indicates the number of gateways located between the sender and the destination. This parameter is only relevant when several routes exist for one destination. Certain routes can be assigned priority using this parameter. However, since there is usually only one gateway, the value 1 can be set here.
<Parameter>
-f
Deletes all routing entries in the routing table
-p
Creates a permanent entry. This parameter can only be specified using the
command add. Normally routes are only set statically with the route command. This means that routes set in this way will be deleted by a system reboot. The parameter -p sets the entry permanently, so that it will not be deleted by a system reboot.
Example 1:
Adding a permanent default route
C:\cmd>route add 0.0.0.0 mask 0.0.0.0 192.168.0.199 -p
A31003-H3540-A800-1-7619, 2003-05-02
D-17
Admain_anhang_D.fm
Appendix
Example 2:
Querying a routing table
C:\>route print
Active Routes:
Network Address Netmask
Gateway
Address
Interface
Number
0.0.0.0
0.0.0.0
192.168.128.1
192.168.128.14 1
10.2.0.0
255.255.0.0
192.168.128.1
192.168.128.14 1
127.0.0.0
255.0.0.0
127.0.0.1
127.0.0.1
192.168.128.14
255.255.255.255
127.0.0.1
127.0.0.1
192.168.128.255 255.255.255.255
192.168.128.14 192.168.128.14 1
224.0.0.0
192.168.128.14 192.168.128.14 1
224.0.0.0
255.255.255.255 255.255.255.255
192.168.128.14 192.168.128.14 1
The last two entries are multicast or broadcast entries which will not be described in detail here.
D-18
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_D.fm
Appendix
D.2.8
tracert
Tracert (trace route) is used to trace the route from the local computer to the destination host.
It indicates all gateways located on the route to the destination host.
tracert <Host> [<Parameter>]
<Host>
<Parameter>
-d
IP addresses are not resolved to host names
-h <number>
Indicates the maximum number of gateways to the destination host
-j <list>
Suggests a gateway route
-w <timeout>
Wait <Timeout> milliseconds for each reply
Example:
C:\cmd>tracert localhost
Tracing route to localhost [127.0.0.1] over a maximum of 30 hops:
1
<10 ms
<10 ms
<10 ms localhost [127.0.0.1]
Trace complete.
A31003-H3540-A800-1-7619, 2003-05-02
D-19
Admain_anhang_D.fm
Appendix
D.2.9
arp
Before a packet can be sent from one host to another, the hardware address (MAC address)
of the destination hosts network card must be determined. For this purpose, each computer
which communicates via the TCP/IP protocol has an ARP table. ARP (Address Resolution
Protocol) is used for resolving the IP address to the hardware address (MAC address). Before
a connection is established, the ARP table is searched for the required destination host. If the
host is not contained in the table, an ARP request with the IP address of the destination host
is sent via the network. When the destination host receives this request, it sends its hardware
address to the requesting computer. This in turn enters the hardware address in its local ARP
table. The next time this connection is set up, the hardware address of the destination host is
known and can be applied as usual. If a hardware address located outside the logical TCP/IP
network is requested, the only hardware address necessary is that of the router via which the
destination host can be reached.
arp <Parameter>
<Parameter>
-
Displays the ARP table
-d
Deletes an entry from the ARP table
-s
Adds a host entry to the ARP table
Example 1:
Entering a new MAC address into the ARP table
C:\>arp -s 192.168.0.199 02-60-8c-f1-3e-6b
Example 2:
Querying the ARP table
C:\>arp -a
Interface: 192.168.0.1 on Interface 1
Internet Address
Physical Address
Type
192.168.0.1
00-00-5a-42-66-60
dynamic
192.168.0.10
00-60-70-cd-59-22
dynamic
192.168.0.199
02-60-8c-f1-3e-6b
static
D-20
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_D.fm
D.2.10
Appendix
telnet
Telnet enables the user to log onto a remote computer. The program uses port 23 as standard
for this procedure. If you wish to log onto a computer with another port, you must additionally
specify the port number.
telnet [<Host> [<Port>]
]
<Host>
<Port>
Port number which identifies the application on the destination computer
Example:
C:\>telnet localhost 110
A31003-H3540-A800-1-7619, 2003-05-02
D-21
Admain_anhang_D.fm
Appendix
IP Addressing: Sub-Networks
D.3
To circumvent the scarcity of official IP addresses and to divide an IP network into separate
sub-networks, the sub-netting procedure can be used.
For the allocation of official IP addresses, for example, sub-netting makes it possible to generate additional independent IP networks by using existing Class A, B and C network addresses.
Various classes and standard network masks have been agreed upon for networks:
Class
Netmask
255.0.0.0
255.255.0.0
255.255.255.0
Table D-1
Network Classes and Standard Network Masks
Division into independent subnets also offers the considerable advantage that local network
traffic remains in its own subnet. Access to third-party networks is only possible via a router.
The basic functionality of sub-netting is relatively simple and is based on the netmask. This
mask is used for defining bits which represent either the network or the host segment within an
IP address. Set bits (1) represent the network segment, while deleted bits (0) represent the host
segment.
The best way to analyze a netmask is in binary format. The Class C standard netmask
255.255.255.0 is a good example.
Network
Host
Bytes
1st byte
2nd byte
3rd byte
4th byte
Netmask
255
255
255
Binary format 1111 1111 1111 1111 1111 1111 0000 0000
Table D-2
Example of a Class C Standard Network Mask
In netmask 255.255.255.0, the first 3 bytes represent the network segment (all bits 1) and the
last byte represents the host segment (all bits 0).
The host (router, workstation, etc.) uses this netmask to determine whether the IP address being addressed is located in the local network. If the destination host is not located in the same
network, packets are forwarded to this address via suitably defined routing mechanisms.
To create customized subnets, you will first need to determine the number of sub-networks to
be established within a class-based network (Class A, B, C). When a network is divided, 2n
subnets are always created as a result. An example will illustrate this more clearly.
D-22
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_D.fm
Appendix
The Class C network 192.168.1.0 is to be divided into 4 subnets. A Class C network has the
default netmask 255.255.255.0. Two bits are required for four different combinations in the
binary system. The following table illustrates the interdependency between the bit number and
the number of networks.
Bits Combinations
Bits Combinations
21
=2
17
217 = 131072
22 = 4
18
218 = 262144
23 = 8
19
219 = 524288
24 = 16
20
220 = 1048576
25 = 32
21
221 = 2097152
26 = 64
22
222 = 4194304
27 = 128
23
223 = 8388608
28 = 256
24
224 = 16777216
29 = 512
25
225 = 33554432
10
210 = 1024
26
226 = 67108864
11
211 = 2048
27
227 = 134217728
12
212 = 4096
28
228 = 268435456
13
213 = 8192
29
229 = 536870912
14
214 = 16384
30
228 = 1073741824
15
215 = 32768
31
231 = 2147483648
16
216 = 65536
32
232 = 4294967296
Table D-3
Bit Number Depending on Number of Networks
A31003-H3540-A800-1-7619, 2003-05-02
D-23
Admain_anhang_D.fm
Appendix
So that no gaps are left in the address range, additional 1s are added from left to right to the
existing 1s of the netmask.
Class C
Network
Host
Bytes
1st byte
2nd byte
3rd byte
4th byte
Netmask
255
255
255
Binary format
1111 1111
1111 1111
1111 1111
0000 0000
New
Network
Host
Bytes
1st byte
2nd byte
3rd byte
4th byte
Binary format
1111 1111
1111 1111
1111 1111
11
Netmask
255
255
255
192
Table D-4
00 0000
Example of a Subnet Mask Binary Format
If the new subnet is converted from binary to decimal form, the result is the subnet mask
255.255.255.192. Now 26 bits are available for the network segment and 6 for the host segment. Computers with a network segment with the same bit pattern can communicate directly
in a physical network. Other networks can only be reached via a gateway. If the modified 4th
byte is viewed in terms of the two new network bits (25 and 26), the newly created subnets can
now be calculated.
4th byte
Decimal
New networks
Broadcast address
Host addresses
0000 0000
192.168.1.0
192.168.1.63
162
0100 0000
64
192.168.1.64
192.168.1.127
65126
1000 0000
128
192.168.1.128
192.168.1.191
129190
1100 0000
192
192.168.1.192
192.168.1.255
193254
Table D-5
Calculating New Subnets
Thus sub-netting essentially involves the extension of the network segment of an IP address
by reducing the host segment. The number of available subnets and hosts depends on the following conditions:
The number of available host addresses depends largely on the length of the host segment of
the IP address. Viewed mathematically, a 6-bit host segment provides for 64 addresses. However, as each IP network and thus each individual subnet has two reserved addresses, the
maximum number of addresses is reduced by two. These are the host addresses which contain
either zeros or ones. The former is used for addressing a network, while the latter is used for
broadcasts in the network in question.
D-24
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_D.fm
Appendix
As mentioned above, the new network segment bits are added from left to right to the existing
bits. The reasons for this are described below. For example, if you use subnet mask
255.255.255.3 for the network 192.168.1.0, the host segment is located in the middle of the
network segment.
Network
Host
Bytes
1st byte
2nd byte
3rd byte
4th byte
Netmask
255
255
255
Binary format 1111 1111 1111 1111 1111 1111

Table D-6
Network
0000 00
11
Host Segment in a Network Segment
No associated IP address areas are provided for by this subnet as only the hosts which have
set the last two bits are located in a network. The resulting addresses are listed in the following
table.
4th byte
Decimal New networks
Broadcast address Host addresses
0000 0000
192.168.1.0
192.168.1.252
4,8,12,16,20,...,248
0000 0001
192.168.1.1
192.168.1.253
5,9,13,17,21,...,249
0000 0010
192.168.1.2
192.168.1.254
6,10,14,18,22,...,250
0000 0011
192.168.1.3
192.168.1.255
7,11,12,19,23,...,251
Table D-7
Network Addresses Depending on Last Two Bit Digits
The host addresses indicate that the individual hosts are not located in associated areas. This
type of sub-netting makes it difficult to maintain an overview for administration. This is why this
type of sub-netting should not be used.
Up to now we have described how sub-networks are created. We will now explain how the IP
addresses of computers are assigned to the respective subnets.
The following table shows four IP addresses for a network (Class C) and their connection to the
netmask being used 255.255.255.224.
Network
Host
255.255.255.224 11111111.11111111.11111111.111
00000
193.98.44.33
11000001.01100010.00101100.001
00001
193.98.44.101
11000001.01100010.00101100.011
00101
193.98.44.129
11000001.01100010.00101100.100
00001
193.98.44.61
11000001.01100010.00101100.001
11101
Table D-8
Allocating IP Addresses to Class C Networks
A31003-H3540-A800-1-7619, 2003-05-02
D-25
Admain_anhang_D.fm
Appendix
The binary illustration of masks and addresses shows quite clearly which subnet the IP addresses in question belong to. Addresses 1 and 4 are in subnet .32 (00100000), address 2
belongs to subnet .96 (01100000) and address 3 is located in subnet .128 (10000000).
If the example is based on the standard mask 255.255.255.0 of a Class C network, the length
of the network segment is 24 bits, while the host segment is 8 bits long. Based on netmask
255.255.255.224 the network segment of an IP address in the network is exactly 27 bits long.
Accordingly the host segment is just 5 bits long.
The following overview provides the most commonly-used Class C masks as a reference, together with the corresponding network and host allocations.
D-26
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_D.fm
Appendix
Netmask
Number of
networks
255.255.255.0
1
255.255.255.128 2
255.255.255.192 4
255.255.255.224 8
255.255.255.240 16
Table D-9
Hosts per subnet Subnet Broadcast Address

253
0
255
126
0
127
128
255
62
0
63
64
127
128
191
192
255
30
0
31
32
63
64
95
96
127
128
159
160
191
192
223
224
255
16
0
15
16
31
32
47
48
63
64
79
80
95
96
111
112
127
128
143
144
159
160
175
176
191
192
207
208
223
224
239
240
255
Hosts
1 254
1 126
129 254
1 62
65 126
129 190
193 254
1 30
33 62
65 94
97 126
129 158
161 190
193 222
225 254
1 14
17 30
33 46
47 62
65 78
81 94
97 110
113 126
129 142
145 158
161 174
177 190
193 206
209 222
225 238
241 254
Overview of the Most Commonly-Used Class C Masks
A31003-H3540-A800-1-7619, 2003-05-02
D-27
Admain_anhang_D.fm
Appendix
Example:
A LAN with two Ethernet networks is to be connected to the Internet via ISDN access. All stations in the local Ethernet are to have Internet access and also be directly accessible from the
Internet. Based on the corresponding structures of a Class C address, a complete Class C network would normally have to be provided for each of the two Ethernet networks and for the
ISDN network. However, as the maximum number of stations in a Thin Ethernet segment is
limited to thirty, 223 host addresses per network would be lost here alone.
This is where sub-netting is of particular significance: With a corresponding netmask, just one
Class C network is required to achieve a complete LAN connection, without the loss of host
addresses.
For this purpose, an Internet Service Provider provides a Class C network with the following
basic data:
Provider IP address:
192.93.98.222
Gateway IP address:
192.93.98.222
Networks IP address:
192.93.98.0
Netmask:
255.255.255.0
The following diagram shows the corresponding configuration:
Figure D-5
D-28
Connection of BNC Network at Twisted Pair to HiPath HG 1500
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_D.fm
Appendix
255.255.255.224 is available as a netmask, as this mask provides 8 subnets with 30 hosts

each. The number of hosts in each subnet is thus equivalent to the maximum number of stations in an Ethernet segment.
This illustration shows that two subnets, in this case 192.93.98.32 and 192.93.98.64, have
been assigned to the two LAN boards of the ITK router. One of the LAN boards is assigned the
IP address 192.93.98.33 and the other is assigned 192.93.98.65. In this way each board can
supply 29 additional stations with IP addresses.
The ISDN (WANODI or Virtual Ethernet) is assigned the IP address 192.93.98.193 from subnet 192.93.98.192. The default gateway in this case is the IP address of the provider access.
This ensures that all outgoing packets to networks which are not in the local LAN subnet will
be forwarded to the provider.
A31003-H3540-A800-1-7619, 2003-05-02
D-29
Admain_anhang_D.fm
Appendix
Port Numbers
D.4
Port Numbers
D.4.1
Port numbers on HG 1500 V3.0
Client/Server
Protocol
Server
Client
Application
H.323 (H.225/Q931)
TCP
1720
ephemeral
Voice over IP for system

clients, H.323 clients,
AllServe and IP networking
RTP/RTCP
UDP
1500
ephemeral
H.245
TCP
ephemeral
ephemeral
HFA LAN IF
TCP
4060
Network Unit
TCP
12050
12050
HiPath 5000,
IP networking
Data Gateway
TCP
8765
8765
HiPath 5000,
IP networking
VCAPI
TCP
12001
ephemeral
VCAPI
Accounting Server
TCP
13042
SNMP (Get/Set)
UDP
161
RTCP/MSC
UDP
162
Registration
TCP
Call Address Resolution
TCP
12062
12062
TFTP
TCP
ephemeral
ephemeral
WBM
TCP
8085
Telnet
TCP
23
IPNC
TCP
12051
MPH
TCP
12052
IPSEC
UDP
500
Table D-10
D-30
System client
SNMP browser, HiPath

FM
12061
HiPath 5000 networking
APS transfer via TFTP

Administration
Port numbers on HG 1500
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_D.fm
Appendix
Port Numbers
D.4.2
Port Numbers on the HiPath 3000/5000 Server
Client/Server
Protocol
Server Port
(Lists Port)
Application
CAR_Server
TCP
12062
HiPath 5000 RSM
REG_Server
TCP
12061
HiPath 5000 RSM
TFTP Server
UDP
69
APS transfer via TFTP
HiPath FM Server
UDP
161
SNMP (Get/Set)
UDP
162 (or 3162)
SNMP (traps)
RMI
3042 defined
range of ports
3050 - 3065
Communication from Client to HiPath FM Server
Socket:
Proprietary
Protocol
3041, 3043,
3044, 3045
Communication from Client to HiPath FM Server
SQL Server
TCP
1433
Database of DB Feature Server,

CCMC, GetAccount
SQL Server
UDP
1434
SW Viewer (SNMP)
UDP
161
Between Application Server:

SW Viewer to SW Viewer
Deployment Tool
UPD
5100
Software upgrade
FTP Server
FTP
21
FTP Server
DNS
UDP
53
ADS name resolution
DHCP
UDP
67
IP address assignment
Table D-11
Port Numbers on the HiPath 3000/5000 Server
A31003-H3540-A800-1-7619, 2003-05-02
D-31
Admain_anhang_D.fm
Appendix
Port Numbers
D.4.3
Port Numbers on HiPath 3000
Client/Server
Protocol
Server
Client
Application
TFTP
UDP
69
69
APS transfer via TFTP,

ADM
TCP
7000
SYNC
TCP
7024
FCT
TCP
7100
SNMP (Get/Set)
UDP
161
CSTA
TCP
71001
Table D-12
D-32
SNMP browser, HiPath

FM
Port Numbers on HiPath 3000
A31003-H3540-A800-1-7619, 2003-05-02
Admain_anhang_D.fm
D.5
Appendix
Unwanted Internet connections (DNS queries)
Unwanted Internet connections (DNS queries)
If the LAN module establishes Internet connections for no apparent reason, or if existing connections do not automatically switch to short-hold, then this is due to DNS queries which are
sent from the PC in the LAN to the Internet. To prevent DNS queries from this PC, a corresponding name resolution entry must be made in the Host/Lmhost file on the PC, so that all
subsequent DNS queries can be replied to locally on the PC. In this way an Internet connection
will not be established unless the user specifically initiates it (e. g. by starting the browser). This
problem can also be observed with other standard routers (e. g. 3COM). It is a protocol-based
procedure which can be canceled by appropriate analysis and configuration of the network/PC.
D.6
PC sound settings for Voice over IP
A number of special PC sound card configurations must be observed when using Voice over
IP to make calls via networks and PCs. Faults such as poor sound quality and one-sided or
non-existent connections can often be corrected by modifying your settings. The following
chapter suggests solutions which should help when configuring a voice client. This help is kept
rather general, since the exact settings depend on the hardware and software and on the environment where the PC is located. A detailed description would be too extensive and therefore
unclear.
Poor sound quality is not always an indication of a configuration error or of hardware/software
faults. For example, crackling noises, i. e. brief interruptions (lost voice packets), could also be
an indication that the LAN load is too high. It may be possible to improve the quality of the Voice
over IP connection by restructuring the LAN, migrating to 100BaseT or using a switch. If the
G.711 audio standard is used (64 kbps) rather than G.723 (5 kbps), a considerably higher LAN
load may result. For a small number of voice applications, G.711 has no noticeable effect on
the LAN load. However, if Voice over IP is used intensively when the LAN is already overloaded, the voice quality may deteriorate significantly.
Configuration options
1.
Simultaneous talking and listening is not possible
The sound card driver is not fully duplex-compatible, an update must be installed to
correct this.
Incorrect configuration of the voice application, activate full duplex functionality in the
software.
2.
Full duplex functionality of the sound card driver can be tested with Netmeeting. Under Options Audio you can activate/deactivate full duplex functionality. If this item cannot be
modified, a fully-duplex driver must be installed for the sound card.
3.
One-sided voice connections
A31003-H3540-A800-1-7619, 2003-05-02
D-33
Admain_anhang_D.fm
Appendix
PC sound settings for Voice over IP
4.
Full duplex functionality activated
Microphone connected
Microphone activated for voice application
Check PC volume setting, activate Microphone under Record
You hear your own voice, either immediately or after a delay.
5.
6.
Check PC volume setting, deactivate Microphone under Playback and deactivate

Wave under Record
Call partner has difficulty hearing you
Check volume setting of PC or voice application, increase volume
If available, activate Microphone Booster under Volume Playback Advanced

Settings
The called party hears loud background noise (over-modulation).
If available, deactivate microphone booster under Volume Playback Advanced

Settings
Adjust microphone sensitivity in the voice application, e. g. in Netmeeting under Options Audio Microphone, activate Set manually and adjust sensitivity.
Adjust recording volume, e. g. in Netmeeting go to Options Audio and activate the

Audio Wizard.
Change the audio standard, e. g. in Netmeeting go to Options Audio Extended,

and switch from G.723 Audio Codec to G.711 Audio Codec (increases the LAN
load).
D-34
A31003-H3540-A800-1-7619, 2003-05-02
bkglos.fm
Glossary
Glossary
A
ARP
The Address Resolution Protocol is a protocol which maps Level 3 IP addresses to Level
2 hardware addresses (MAC addresses).
B
B channel
An ISDN user data channel (bearer channel) with a capacity of 64 Kbps.
Bandwidth
The bandwidth of a communication channel is its capacity for transferring data.
Boot
This term refers to the startup procedure. The boot ROM contains the start code; booting
is another word for starting.
C
Codec
Codecs convert analog audio or video data into digital format (encoding) and back into
analog format (decoding).
CorNet-NQ
CorNet-NQ (from Corporate Networking) is a Siemens proprietary signaling protocol.
CorNet-NQ is a superset of CorNet-N which supports QSIG.
D
D channel
A D channel is an ISDN signaling channel which transmits call control information.
DID
Abbreviation of Direct Inward Dialing. DID is a method of forwarding incoming calls
directly to H.323 terminals.
DTMF
Abbreviation of dual-tone multifrequency. DTMF is the multifrequency signaling mode for
transmitting telephone numbers.
A31003-H3540-A800-1-7619, 2003-05-02
X-1
bkglos.fm
Glossary
E
E-DSS1
Abbreviation of European Digital Subscriber System No.1. E-DSS1 is the ISDN transfer
protocol normally used in Europe.
G
G.711
G.711 is an ITU standard (International Telecommunication Union) standard for voice
codecs for a data rate of 64 Kbps.
G.723.1
G.723.1 is an ITU standard (International Telecommunication Union) for voice codecs for
transmission rates of 5.3 and 6.3 Kbps.
G.729
G.729 is a group of ITU standards (International Telecommunication Union) for voice
codecs for transmission rates of 8 Kbps.
Gatekeeper
A gatekeeper is a H.323 component that provides address conversion and access control
services for terminals in a H.323 network.
Gateway
A gateway is a H.323 component which connects H.323 endpoints in an IP network to telephones in the public telephone network. It translates between H.323 and ISDN protocols.
H
H.323
H.323 is a group of standards which describes the transmission of call and fax data in packet-oriented networks such as IP networks. These standards are set down in the H.323 series of ITU-T recommendations (International Telecommunication Union Telecommunication Standardization Sector).
HiPath
Siemens HiPath (from Highly Integrated Pathwork) is an innovative strategy which implements an extensive IP migration concept and thereby facilitates the integration of multimedia communication in existing corporate IP networks.
I
IP address
An IP address (IP Internet Protocol) is a group of four numbers that identify a device.
Each number can have a value between 0 and 255.
X-2
A31003-H3540-A800-1-7619, 2003-05-02
bkglos.fm
Glossary
ISDN
Abbreviation of Integrated Services Digital Network. ISDN is a fully digital public telephone network.
IVR
Abbreviation for Interactive Voice Response. IVR is a procedure for forwarding calls if an
individual line does not have numbers for dialing H.323 endpoints directly. HiPath HG 1500
does not support IVR.
L
LAN
Abbreviation for Local Area Network. A local area network (LAN) connects computers
within a company.
M
MCU
Abbreviation for Multipoint Controller Unit. MCUs are used for audio and video calls with
multiple subscribers. They centralize data distribution and combine voice and video.
MIB
Abbreviation for Management Information Base. An MIB compiles information and parameters of a network device. It is required for administration via SNMP.
Multicast
Multicast designates data transfer from a source to several recipients in networks.
P
PBX
Abbreviation of Private Branch Exchange. A PBX is a telecommunications system.
PRI
Abbreviation of Primary Rate Interface. A PRI is an ISDN interface comprising 23 (TS1)
or 30 (TS2) B channels each with a capacity of 64 Kbps and one D channel with a capacity
of 16 Kbps.
PSTN
Abbreviation of Public Switched Telephone Network. PSTN is the worldwide public telephone network.
Q
Q.931
Q.931 is a call signaling protocol for setting up and clearing down calls.
A31003-H3540-A800-1-7619, 2003-05-02
X-3
bkglos.fm
Glossary
QSIG
QSIG is a protocol for networking nodes which has been adapted by the ITU-T (International Telecommunication Union Telecommunication Standardization Sector). QSIG can
be used to network PBXs from different manufacturers.
R
RAS
Registration Admission Status is a protocol which conveys automatic recognition and registration messages between the client and the gateway.
Router
A router is a network component which connects subnetworks and transfers packets between them.
RTP
The Real-Time Transport Protocol governs the transmission of real-time audio and video
packets from a terminal to one or more different terminals.
T
T.38
T.38 is an ITU standard for fax transmission. It determines the communication of group 3
fax machines via IP networks.
Terminal
A terminal is a H.323 component that can initiate or receive calls. Information ows begin
or end here. Examples include clients, gateways or MCUs.
V
VoIP
The Voice over Internet Protocol (IP) controls telephone calls via IP networks.
X-4
A31003-H3540-A800-1-7619, 2003-05-02
bkabb.fm
Abbreviations
Abbreviations
This list explains some important abbreviations.

Abbreviation
Denition
A
ARP
Address Resolution Protocol
C
CLI
Command Line Interface
E
ESD
Electrostatically Sensitive Devices
H
HTML
Hypertext Markup Language
HTTP
Hypertext Transfer Protocol
M
MIB
Management Information Base
N
NAT
Network Address Translation
NMS
Network Management System
P
PDU
Protocol Data Unit
R
RAM
Random Access Memory
RG
Realtime Gateway
ROM
Read-Only Memory
A31003-H3540-A800-1-7619, 2003-05-02
Y-1
bkabb.fm
Abbreviations
S
SNMP
Simple Network Management Protocol
T
TFTP
Trivial File Transfer Protocol
U
URI
Universal Resource Identifier
URL
Uniform Resource Locator
V
VT
Video Terminal
W
WBM
Web-Based Management
A
ARP Address Resolution Protocol
C
CLI Command Line Interface
E
ESD Electrostatically Sensitive Devices,
H
HTML Hypertext Markup Language
HTTP Hypertext Transfer Protocol
M
MIB Management Information Base
N
NAT Network Address Translation
NMS Network Management System
P
PDU Protocol Data Unit
Y-2
A31003-H3540-A800-1-7619, 2003-05-02
bkabb.fm
Abbreviations
R
RAM Random Access Memory
RG Realtime Gateway
ROM Read-Only Memory
S
SNMP Simple Network Management Protocol
T
TFTP Trivial File Transfer Protocol
U
URI Universal Resource Identifier
URL Uniform Resource Locator
V
VT Video Terminal
W
WBM Web-Based Management
A31003-H3540-A800-1-7619, 2003-05-02
Y-3
bkabb.fm
Abbreviations
Y-4
A31003-H3540-A800-1-7619, 2003-05-02
bkIX.fm
Index
Index
A
Accidents, reporting 5-6
Action Activated (parameter) 4-57, 4-59, 516, 5-36
Active (parameter) 4-28
Address Resolution Protocol X-1
Administrator 2-10
ARP X-1
arp D-20
Associated Trace Profile (parameter) 4-39
Authentication 4-1, A-2
B
B channels X-1
Backing up system files 4-7
Bandwidth X-1
Behavior in emergencies 5-5
BNC network D-1
Boot sequence 5-13
Booting 5-13
C
Chapter overview 1-2
Clear All Debug Switches (parameter) 4-15
CLI 2-8
Codecs X-1
Command line 2-8
authentication 2-9
authentication command A-2
configuration 2-9
configuration commands A-4
editing the command line 2-9
installation commands
default router A-4
IP address A-4
name A-4
subnet masks A-4
TFTP A-4
maintenance command
view A-7
A31003-H3540-A800-1-7619, 2003-05-02
maintenance commands 2-10, A-7

assigning a default router A-8
ping A-8
restart A-9
shell commands A-2
editing command A-2
Help A-2
last command A-2
next command A-2
Command lines A-1
commands A-1
Community (parameter) 4-44, 4-45, 4-48, 449, 4-51, 4-53
Configuration A-5, A-6, A-7
Configuration file 5-18
CorNet NQ X-1
D
D channels X-1
Data Included in the Trace Output (parameter) 4-22
Days on which to Perform Action (parameter)
4-59
Debug Level (parameter) 4-15
Debug Modules (parameter) 4-15
DID X-1
Direct Inward Dialing X-1
DNS queries D-33
DSS1 X-2
DTMF X-1
E
E-DSS1 X-2
E-mail Address (Recipients) (parameter) 436
E-mail Settings (parameter) 4-36
Emergencies 5-5
Error Correction 6-1
Error messages when switching on 6-2
Event Level (parameter) 4-28, 4-30
Z-1
bkIX.fm
Index
Events 4-31, 6-4, 6-6

Explorer 3-10
functions 3-10
navigation 3-11
window 3-11
G
G.711 X-2
G.723.1 X-2
G.729 X-2
Gatekeeper X-2
Gateway
configuration A-7
restart A-9
status A-7
Gateway Name (parameter) 5-25, 5-28
Gateways X-2
H
HiPath X-2
hostname D-11
HTTP 2-2
HUB, 3COM Dual Speed D-2
I
Interface status A-7
Internet Explorer 2-2
Interrupting boot procedure 5-13
IP Address (parameter) 4-44, 4-45, 4-48, 449, 4-51, 4-53, 5-25, 5-28
IP addresses X-2
IP addressing D-22
ipconfig D-7
ISDN X-3
IVR X-3
configuring ISDN 3-10

configuring trap destinatio 3-10
loading configuration data 3-10
loading trace data or event logs 3-10
upgrading software 3-10
MCU X-3
MIB 2-10, X-3
Monitoring 4-7
Multicast X-3
N
Name of configuration file (parameter) 5-15,
5-19, 5-22
Navigation 3-10
nbtstat D-16
netstat D-12
None (parameter) 4-28
nslookup D-9
P
Padlock icon 3-2
Password 4-1
PBX X-3
Performance statistics 4-8
Permitted IP Address (parameter) 4-6
ping A-8, D-4
PRI X-3
Problems during system startup 6-1
Profile Name (parameter) 4-17, 4-19
Proprietary MIB 2-10
PSTN X-3
Q
Q.931 X-3
QSIG X-4
LAN X-3
Log file name (parameter) 5-34
Log in 4-1
RAS X-4
Reporting accidents 5-6
Reset icon 3-3
Restart 5-12, A-9, B-1
route D-17
Router X-4
RTP X-4
M
Maintenance 5-1
software 5-12
Maintenance functions 3-10
Z-2
A31003-H3540-A800-1-7619, 2003-05-02
bkIX.fm
Index
Safety information
Caution 5-3
Danger 5-2
Warning 5-3
Save icon 3-3
Security 4-1
Select distribution of configuration data (parameter) 5-25, 5-28
Send an E-mail (parameter) 4-39
Set All to 0 (parameter) 4-28
SMTP Server Settings (parameter) 4-36
SNMP 2-10
agent 2-10
traps 2-11
Software image 5-14, A-5
Sound cards D-33
Sound settings for Voice over IP D-33
Start / Stop Trace Profile (parameter) 4-39
Start Action in (parameter) 4-57, 5-16, 5-36
Start Action on (parameter) 4-57, 5-16, 5-36
Start sequence B-1
Start Time (after midnight) (parameter) 4-59
Starting the System
Cold start 5-12, B-1
Interrupting the Boot Procedure B-2
Warm start 5-12, B-1
Starting the system 5-13
Sub-networks D-22
Suggested LAN solutions D-1
Switch D-3
Switch Component Event Generation on (parameter) 4-30
Switch Console Trace On (parameter) 4-12
Switch Event Logging via LAN On (parameter) 4-32
Switch File Trace On (parameter) 4-12
Switch Global Event Generation on (parameter) 4-30
Switch Trace via LAN On (parameter) 4-12
System files
backup 4-7
T.38 X-4
TCP/IP 2-2
diagnostics tools D-4
Telnet 2-8
Telnet Access (parameter) 4-6
Terminal 2-8
Terminals X-4
TFTP A-6
TFTP Server (parameter) 4-13, 4-33, 5-15, 519, 5-22, 5-34
Trace Level (parameter) 4-17, 4-19, 4-22, 425
Trace On (parameter) 4-22, 4-25
tracert D-19
Traps 4-39, 6-4
performance traps 6-5
system traps 6-4
types of traps 4-39, 6-4
Twisted pair D-1
A31003-H3540-A800-1-7619, 2003-05-02
U
Utility programs D-4
V
V.24 connector 2-8
Voice over IP
sound settings D-33
VoIP X-4
W
WBM 2-2
banner area 2-3
contents area 2-4
control area 2-3
function area 2-3
icons 3-1
menu area 2-3
starting 3-5
window layout 2-3
WBM Access (parameter) 4-6
WBM functions 2-5
Explorer 2-6
Help 2-6
Z-3
bkIX.fm
Index
Logoff 2-5
Maintenance 2-5
Wizards 2-5
WBM icons 3-1
padlock icon 3-2
reset icon 3-3
save icon 3-3
Wizards 3-5
window 3-6
Write access A-3
Z-4
A31003-H3540-A800-1-7619, 2003-05-02

Administration Maintenance

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Administration Maintenance

Hochgeladen von

Copyright:

Verfügbare Formate

s

Administration and Maintenance

The device meets the requirements contained in the EU Directive 1999/5/

List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0-7

2 Management Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

For internal use only

3.6.1 Explorer View Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

4.8.7 Trap Communities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5 Maintenance Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

For internal use only

5.6.11 Checking the Processing Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A Command Line (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B Boot Command Line (Boot CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.1 Trace Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

For internal use only

WBM Window Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

For internal use only

Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

For internal use only

For internal use only

the layout of the documentation (see Section 1.1, Documentation Structure),

this manuals target audience (see Section 1.2, Target Audience),

the typographical conventions used (see Section 1.4, Conventions Used).

The HiPath HG 1500 documentation consists of the following manuals:

Administration and Maintenance (this document)

Data communications hardware

WAN (Wide Area Network) concepts and terms

LAN (Local Area Network) concepts and terms

Internet concepts and terms

For internal use only

Contents of this Manual

Contains information on the various HiPath HG 1500

Describes the basic layout of Web-Based Management

Contains information and guidelines for handling problems and errors.

Command Line (CLI)

Contains all the CLI commands including a brief description.

Boot Command Line (Boot

Contains a brief description of the Boot CLI commands.

Contains a collection of trace and event templates.

Contains additional information which may be helpful

Describes important terms used in this manual.

Lists the abbreviations used in this manual in alphabetical

An alphabetic list of key words.

For internal use only

The following display conventions are used in this manual:

Input and output

Indicates user interface elements

Warning of critical points in a procedure.

For internal use only

For internal use only

Overview of Management Tools

Web-Based Management (WBM) via an integrated HTTP server

Command line (CLI) via Telnet or the serial V.24 interface

SNMP-supported management via an SNMP agent

HTTP applications via a command interface

HiPath 3000 Manager E via a HiPath 5000 RSM server PC

For internal use only

Web-Based Management (WBM)

Each computer with a TCP/IP-supported network connection on which a compatible Web

Windows 98SE, NT 4.0, 2000 or XP

Java plug-in JRE 1.3.1

Microsoft Internet Explorer 5.5 or 6.0

XML Extension DLL V3.0 SP2

Explorer settings must permit the use of ActiveX and Java.