Teldat SA Manual

Configuration and Monitoring

Teldat-Dm704-I

Copyright© Version 11.0I Teldat SA

Configuration and Monitoring 1

Manual Teldat SA

Legal Notice

Warranty

This publication is subject to change.

Teldat offers no warranty whatsoever for information contained in this manual.

Teldat is not liable for any direct, indirect, collateral, consequential or any other damage connected to the delivery,
supply or use of this manual.

2 Configuration and Monitoring

Teldat SA Table of Contents

Table of Contents

Chapter 1 Router Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.2 Local and remote terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.3 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.3.1 Teldat Router connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3.2 Executing a command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3.3 User Interface Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3.4 Accessing the processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3.5 Returning to the Console Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3.6 Obtaining help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.4 GESTCON process commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.4.1 MONITOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.4.2 CONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.4.3 RUNNING-CONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.4.4 FLUSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.4.5 INTERCEPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.4.6 LOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.4.7 LOGOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.4.8 PROCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.4.9 RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.4.10 SSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.4.11 STATUS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.4.12 TELNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.4.13 VRF-TELNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 2 Teldat Router Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.2 Configuration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.3 Configuration procedure user interface . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.4 Configuration commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2.4.1 ADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.4.2 AUTOINSTALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.4.3 BACKUP-FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.4.4 BANNER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.4.5 CONFIG-MEDIA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.4.6 CONFIRM-CFG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.4.7 CONFIRM-CFG-NEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.4.8 COPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.4.9 DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.4.10 DISABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.4.11 DUMP-COMMAND-ERRORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.4.12 ENABLE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.4.13 EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.4.14 FEATURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Configuration and Monitoring i

Table of Contents Teldat SA

2.4.15 FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.4.16 FIRMWARE-CHECKING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
2.4.17 FORMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
2.4.18 GLOBAL-PROFILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
2.4.19 LICENCE-CHANGE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.4.20 LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.4.21 LOG-COMMAND-ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
2.4.22 MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
2.4.23 NETWORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
2.4.24 NO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.4.25 NODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2.4.26 PRIVILEGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2.4.27 PROTOCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
2.4.28 QUICK CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
2.4.29 RUSH-ENGINE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
2.4.30 SAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
2.4.31 SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
2.4.32 STRONG PASSWORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
2.4.33 TELEPHONY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
2.4.34 TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
2.4.35 UCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
2.4.36 UNSET-DEMO-LICENCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
2.4.37 USER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
2.4.38 END . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Chapter 3 Router Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

3.2 Monitoring procedure commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

3.2.1 ? (HELP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
3.2.2 BUFFER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
3.2.3 CLEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
3.2.4 CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
3.2.5 DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
3.2.6 ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
3.2.7 EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
3.2.8 FEATURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
3.2.9 LAST-CONFIG-CHANGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
3.2.10 LAST-APP-VERSION-CHANGES. . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
3.2.11 LIST CURRENT-DEVICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
3.2.12 MALLOC-MONITOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
3.2.13 MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
3.2.14 MEMORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
3.2.15 NETWORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
3.2.16 NODE commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
3.2.17 PROTOCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
3.2.18 QUEUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
3.2.19 QUICK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
3.2.20 RUSH-ENGINE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
3.2.21 STATISTICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

ii Configuration and Monitoring

Teldat SA Table of Contents

3.2.22 SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

3.2.23 TFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
3.2.24 TELEPHONY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
3.2.25 UCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
3.2.26 UPTIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
3.2.27 VERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
3.2.28 WEB-PROBE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
3.2.29 LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Chapter 4 Event Logging System ELS . . . . . . . . . . . . . . . . . . . . . . . . . . 135

4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

4.2 Event Logging System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

4.3 Event Logging System user interface . . . . . . . . . . . . . . . . . . . . . . . . . . 139

4.4 Event Logging System Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

4.4.1 Configuration Process Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
4.4.2 Monitoring process commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

4.5 Supported personalized parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Configuration and Monitoring iii

Table of Contents Teldat SA

iv Configuration and Monitoring

Teldat SA 1 Router Console

Chapter 1 Router Console

1.1 Introduction
All our devices employ the same user interface for every model. They only differ regarding the protocol software
loaded in each.

The information contained in this chapter is divided in the following sections:

• Local and remote terminal.

• User interface.
• User interface description.
• GESTCON process commands.

1.2 Local and remote terminal

Every Teldat Router allows user access, for configuration and monitoring functions, through a local or remote ter-
minal.

Local Terminal
A local terminal is directly connected to the Teldat Router through an RS-232 serial cable. For further information
see the Device Installation Manual.

Remote Terminal
The remote connections provide the same features as the local ones, except a local terminal must be used for the
initial configuration. The remote terminals are connected to the Teldat Router through TELNET, once the IP protocol
has been enabled. See manual Teldat Dm702-I TCP-IP Configuration for further information on how to enable the IP
protocol.

Through a local or remote terminal you can access the Teldat Router and carry out different processes. Said pro-
cesses are related to device configuration with status monitoring and related statistics. Messages can also be re-
ceived on any generated events. The following table provides names and additional information:
P 1 (GESTCON): This is the console management process (GESTCON). This is the starting point
for booting a console session, which accesses other processes.
P 2 (VISEVEN): This process allows events generated in the system to be displayed, from estab-
lished connections to errors in the system ( VISEVEN). These events should be
pre-configured either in process 4 (CONFIG), or in process 3 (MONITOR), through
the Event Logging System. See Event Logging System ELS on page 135 for further
details.
P 3 (MONITOR): This allows you to MONITOR the state of the system as well as the statistics
gathered by the device.
P 4 (CONFIG): This process allows you to edit all configuration parameters. From here you can
generate a complete configuration for the router without altering the operation pro-
cedure. To activate said configuration, save it in the file system and restart the
device.
P 5 (RUNNING-CONFIG): This is the process where changes in the router active configuration are affected.
The configuration changes executed here take immediate effect, however if they
aren't saved in the file system, they are lost on reboot.

Note

These processes are accessed from the console by striking keys P 2, P 3 P 4 or P 5.

1.3 User interface

The following steps are the same for each Teldat Router, regardless the software installed.

• Teldat Router connection.

Configuration and Monitoring 1

1 Router Console Teldat SA

• Executing a command.
• User interface processes.
• Accessing the process.
• Return to the Console Manager.
• Obtaining help.

1.3.1 Teldat Router connection

You can establish console sessions with the router both locally through serial port RS-232 and remotely through a
TELNET session. The following paragraphs explain both methods:

Local Connection

During device booting, the user can see information on both the device hardware and software configuration and
system startup progress. Once booting is complete, the user is asked to initiate a session by pressing any key.

User/password controls access the router local connection. By default no user is registered, so they are not reques-
ted. The first thing to appear is the welcome text and the console management prompt, as shown below.

Teldat (c)2001-2002
Router model XXXXX CPU MPC860 S/N: YYYY/YYYYY
1 LAN, 2 WAN Line , 2 ISDN Line
CIT software version: ZZZZZ
*

where XXXXX is the specific router model.

To register a user, please see the user command in Teldat Router Configuration on page 16. Where there are en-
abled users, a user and corresponding password is requested. If authentication is accepted, then the welcome text is
shown.

User: Root
Password:****
Teldat (c)2001-2002
Router model XXXXX CPU MPC860 S/N: YYYY/YYYYY
1 LAN, 2 WAN Line , 2 ISDN Line
CIT software version: ZZZZZ

where XXXXX is the specific router model, YYYY/YYYY the unit serial number and ZZZZ the CIT code release cur-
rently running.

If the password is not valid, the following text appears:

User: Root
Password:******
Access denied

If the password is incorrectly entered, you won't be able to access the console. If you exhaust the maximum number
of erroneous attempts, the application blocks for one minute.

If you have been authenticated in the system and an inactive time period has also been configured (see the set com-
mand in Teldat Router Configuration on page 16 ), a monitoring process begins. If the configured inactive time period
times out, without the user touching any of the keys, the local connection closes. Consequently, the user must
reenter the password again when he wishes to use the console.

Depending on the user you have authenticated with, you can access the different processes and possibly execute
some restricted commands.

The user access level is specified with a value between 0 and 15 together with a mode: default or strict.

Five different predetermined access levels are defined in the default mode:
NONE [0]: System access is not allowed.
EVENTS [1]: You can access the Console Management (P1), the Events Viewing (P2), but you
cannot execute the Ping, Telnet, Restart or Load or commands.
MONITOR [5]: You can access the Console Management (P1), the Events Viewing (P2) and the
Monitoring process (P3). You can also execute the Ping and Telnet and com-
mands, but not the Restart or Load commands.

2 Configuration and Monitoring

Teldat SA 1 Router Console

CONFIG [10]: You can access all processes and standard commands.
ROOT [15]: In addition to being able to access all the processes and the standard commands,
you can also access the user management own commands. These are explained
further on in this manual.

You must save the configuration (see the save command in chapter Teldat Router Configuration on page 16) To
maintain the users registered on restarting the device as contrariwise you lose said user configuration.

The user command manages the users and allows the following actions: add, delete, enable and disable users, list
and change the user access level:

user name password password:

Configures a user password, creating one if it does not exist.

no user name:

Deletes a user from the user list. You can eliminate as many users as you want, except if there is only one Root user
and there are other registered users. This means you can only delete the rest of the users as contrariwise you can-
not manage the remaining users. If you eliminate all the users except the last Root, then you can also delete the lat-
ter. The system subsequently does not request a user and password to access the device, as there are no users re-
gistered in the system.

user name active:

Allows you to enable users. Simply indicate the user name you wish to enable.

user name no active:

Allows you to disable users. You cannot disable Root users.

list user:

Displays a list of registered users, their access level and if they are enabled or not.

Allows you to change the access level for any registered user, except for users with a Root access level.

For further information on the user command, please see Teldat Router Configuration on page 16.

User management is compatible with the password defined through the set password command. Therefore if you
update a device with said password enabled, this continues to allow access (through the password) while not regis-
tering any user.

Note

User management has priority over the device password; when there are registered and enabled users
(these are enabled by default when they are registered) the old password is no longer valid.

Remote connection

To connect to Teldat Router initializing a TELNET session in the host (the host being the system connected to the
remote terminal), you need the IP address for the device you want to connect to.

Example:

telnet 128.185.132.43

The Teldat Router acts as a TELNET server. The remote terminal acts as a TELNET client.

Once a TELNET session is established with the Teldat Router, you may find a user and password is requested to
access the system. Once correctly authenticated, the following welcome text appears.

User: Root
Password:****
Teldat (c)2001-2002
Router model XXXXX CPU MPC860 S/N: YYYY/YYYYY
1 LAN, 2 WAN Line , 2 ISDN Line
CIT software version: ZZZZZ
*

where XXXXX is the specific router model, YYYY/YYYY the unit serial number and ZZZZ the CIT code release cur-
rently running.

Configuration and Monitoring 3

1 Router Console Teldat SA

Access control to the Teldat Router is similar to local mode access. If there are users defined and these are enabled
(these enable by default when created), the introduction of a user and his corresponding password is requested for
connection purposes. Once authenticated, the welcome text and prompt appear and you can access the user per-
mits (as indicated in the connection via local).

If the password is invalid, the following text is displayed:

User: Root
Password:******
Access denied

Note

If the password is not entered within approximately 20 seconds, or the password provided is invalid, at
the third attempt the device disconnects the TELNET session.

1.3.2 Executing a command

To enter a command, simply enter the necessary letters, which differentiate one command from another, in the menu
you are using.

Example:

In a menu containing the following commands:

user

upload

down

If you key in a u , an error is produced indicating you have entered an ambiguous command (both user and upload
begin with a u). If you enter a d , do , dow or down , said command is executed. In the same way, if you enter us ,
use or user , this command executes, and likewise up, upl , uplo , uploa or upload . Any other entry produces an
error, as no command coincides with those characters.

To delete the last character(s) from the command line use the backspace ( <-) key.

To split a long command into multiple lines, you can end a line with a backslash ( \).

Example:

Config>set \
Config>host\
Config>n MY_\
Config>HOST_N\AME

is equivalent to:

Config>set hostn MY_HOST_N\AME

Command history:

Release Modification
11.00.05 This command option was introduced as of version 11.00.05.

1.3.3 User Interface Processes

The user interface is made up of various processes, which can be accessed through the console sessions.

The processes normally handled are: GESTCON, MONITOR, CONFIG, RUNNING-CONFIG and VISEVEN. The fol-
lowing diagram describes the structure of the processes in the Teldat Router.

As shown in the figure, each process has a different prompt. The prompt indicates which process you are in.

The following list shows the prompts for the different processes:
Prompt
Process
GESTCON *
MONITOR +

4 Configuration and Monitoring

Teldat SA 1 Router Console

CONFIG Config>
RUNNING-CONFIG Config$

The Teldat Router offers the possibility of personalizing the device and can include a text before the prompt. This
text can contain a maximum of 8 characters and takes the name assigned to the device. To enter said text, please
see the configuration command set hostname.

Each of these processes is described below:

GESTCON Process

This is the console manager: its task is to simplify access to the rest of the processes on the console.

MONITOR Process

Allows the user to monitor the status and statistics of the router hardware and software. Provides access to the pro-
tocol and interface menus, which in turn allow the user to monitor the configured protocols and other parameters.

CONFIG Process

Enables configuration of various parameters such as net addresses and events. Provides access to the configuration
of protocols permitting protocol parameter configuration. As user, you execute all the device configuration from this
process; however it doesn't activate until saved and you have rebooted. This process is used to edit the device boot
up configuration.

RUNNING-CONFIG Process

Provides access to configure the interfaces, protocols, etc. All parameters configured through this process take im-
mediate effect, however if not saved, they are lost on device restart. This process serves to dynamically modify the
device active configuration.

VISEVEN Process

Receives messages from the Event Logging System and displays them on the terminal, complying with the user se-
lection criterion.

Configuration and Monitoring 5

1 Router Console Teldat SA

1.3.4 Accessing the processes

* prompt appears once the session has initiated. The * is the console manager prompt. From here, you can access
the distinct processes. Prompts are the symbols identifying each process:

To access a process, execute the following steps:

(1) Look for the number identifying the process. This information is obtained by entering the status command at the
* prompt.
(2) Enter process pid, where pid is the process number you want to access. For example, to configure the Teldat
Router, enter:

*process 4
User Configuration
Config>

The most common processes however, can be accessed through specific commands. These are as follows.
Command Process
monitor Process 2: monitoring.
config Process 4: startup configuration editor.
running-config Process 5: active configuration.

1.3.5 Returning to the Console Manager

To return to the console manager ( *) from a process, e.g. CONFIG (Config> prompt) or MONITOR (+), enter Ctrl + p
(escape character). ALWAYS RETURN TO THE CONSOLE MANAGER BEFORE ENTERING ANOTHER PRO-
CESS. For example, if you are in MONITOR and wish to enter CONFIG, enter Ctrl + p and return to * before doing
so.

To end a TELNET session initiated from a Teldat Router to another device, use Ctrl + s. Said escape character
forces the TELNET session, started by a Teldat Router, to close.

Note

The Ctrl. + p escape character is used to return to the console Manager, while Ctrl. + s is used to end a
TELNET session.

Example:

*config
User Configuration
Config> Press (Ctrl + p)
*

*monitor
Console Operator
+ Press (Ctrl + p)
*

Note

Other protocol configuration/monitoring menus can be accessed from the configuration or monitoring
processes. To return to the corresponding process, use the exit command. To return to the console
manager use the escape character ( default is Ctrl + p).

1.3.6 Obtaining help

In all processes there is a ? (HELP) command. This provides information on commands that can be used with the
prompt, not only in the console manager (*), but also in the configuration (Config> and Config$) and monitoring (+)
processes.

You can enter an ? after any command to get a list of options available in said command.

You can also terminate a command, or an option, using the ? to access a list of commands or options, which match
the entered one. The tabulation key can also be used to automatically complete a fully determined command or op-
tion.

6 Configuration and Monitoring

Teldat SA 1 Router Console

Example:

Config>protocol ?
arp Access ARP protocol
asrt Access ASRT protocol
bfd Access BFD protocol
bgp Access BGP protocol
dhcp Access DHCP protocol
dhcpv6 Access DHCPv6 protocol
dls Access DLS protocol
dot1x Access 802.1X protocol
gw104 Access GW-104 protocol
h323 Access H323 protocol
igmp Access IGMP protocol
ip Access IP protocol
ipv6 Access IPv6 protocol
l2tp Access L2TP protocol
mgcp Access MGCP protocol
msdp Access MSDP protocol
nhrp Access NHRP protocol
noe Access NOE protocol
ospf Access OSPF protocol
ospfv3 Access OSPFv3 protocol
pim Access PIM protocol
rip Access RIP protocol
ripng Access RIPNG protocol
sccp Access SCCP protocol
sip Access SIP protocol
snmp Access SNMP protocol
Config>protocol a?
arp Access ARP protocol
asrt Access ASRT protocol
Config>protocol a

1.4 GESTCON process commands

The GESTCON process (P1) allows you to configure and monitor all device operation parameters. During GEST-
CON, the Teldat Router processes and transfers data traffic. When the router is switched on and enters GESTCON,
the copyright, information on the router, together with an asterisk *, appear on the connected local terminal. Said as-
terisk * is the prompt for GESTCON, which is the main user interface permitting access to all other processes. Most
changes made in the Teldat Router operation parameters, in GESTCON, take immediate effect i.e. you don't need
to restart the device.

From GESTCON, you can access a set of commands allowing you to check the status of the processes, monitor
device interface and packet transference efficiency, as well as the configuration of various parameters.
GESTCON process commands table
Commands Function
MONITOR Accesses the monitoring process.
CONFIG Accesses the startup configuration editing process.
RUNNING-CONFIG Accesses the active configuration editing process.
FLUSH Clears all the stored messages from the events buffer.
INTERCEPT Allows you to change the procedures’ escape character.
LOAD Reloads the application from the flash memory.
LOGOUT Ends the Telnet connection established with the device.
PROCESS Allows you to access a different device procedure and to enable the commands.
RESTART Allows you to restart the device rereading the configuration.
SSH Establishes a SSH connection as the remote device client, whose remote address
is specified.
STATUS Displays the names and identifiers for each process.
TELNET<address> Establishes a Telnet connection as the remote device client, whose remote ad-
dress is specified.
VRF-TELNET <vrf> <address> Establishes a Telnet connection as client for the remote device, whose address is
specified in the indicated VRF.

Configuration and Monitoring 7

1 Router Console Teldat SA

1.4.1 MONITOR
Accesses the monitoring process.

Syntax:

*monitor

Example:

*monitor
Console Operator
+

1.4.2 CONFIG
Accesses the startup configuration editing process.

Syntax:

*config

Example:

*config
Config>

1.4.3 RUNNING-CONFIG
Accesses the active configuration editing process.

Syntax:

*running-config

Example:

*running-config
Config$

1.4.4 FLUSH
Deletes all the current events messages from the VISEVEN procedure output buffer.

Syntax:

*flush

Example:

*flush
*

1.4.5 INTERCEPT
Allows you to change the escape character for processes. The following example shows the default escape charac-
ter being changed from (Ctrl+u) to (Ctrl+p).

Syntax:

*intercept

Example:

*intercept
Press the new escape key and then Enter: Press (Ctrl+u) and <¿>
Press the new escape key again and then enter: Press (Ctrl+u) and <¿>
Escape key updated
*

8 Configuration and Monitoring

Teldat SA 1 Router Console

Note

The escape key should not be a character that can be displayed.

1.4.6 LOAD
Allows you to load the program from flash memory.

Syntax:

* load <option>
ACTIVATE
DEACTIVATE
IMMEDIATE
RACTIVATE
RDEACTIVATE

• < option > specifies the load type you want to execute.

1.4.6.1 LOAD ACTIVATE

The activate option allows the user to program a specific time to reload the routing application program. Said time is
configured in a 24-hour format.

Syntax:

*load activate

Example:

*load activate 17:21

Are you sure to reload the system at the configured time (Yes/No)? y
*

1.4.6.2 LOAD DEACTIVATE

The deactivate option allows you to cancel a preconfigured loading, which has not as yet been carried out. If no
loading has been programmed, an error message appears.

Syntax:

*load deactivate

Example:

*load deactivate
Reload is timed at 20:00
Are you sure to cancel the timed reload(Yes/No)? y
Timed reload was cancelled
*

1.4.6.3 LOAD IMMEDIATE

The immediate option reloads the application immediately.

Syntax:

*load immediate

Example:

*load immediate
Are you sure to reload the device(Yes/No)? y
*

1.4.6.4 LOAD RACTIVATE

Allows the user to program a specific time when the routing application program restarts. Said time is configured in a
24-hour format.

Configuration and Monitoring 9

1 Router Console Teldat SA

Syntax:

*load ractivate

Example:

*load ractivate 17:26

Are you sure to restart the system at the configured time (Yes/No)? y
*

1.4.6.5 LOAD RDEACTIVATE

Allows you to deactivate the programmed restart process. If there is no restart programmed, an error message ap-
pears.

Syntax:

*load rdeactivate

Example:

*load rdeactivate
Reload is timed at 17:00
Are you sure to cancel the timed restart(Yes/No)? y
Timed restart was cancelled
*

1.4.7 LOGOUT
Ends the Telnet connection established with the router without using a Telnet client command.

Syntax:

*logout

Example:

*logout
Do you wish to end telnet connection (Yes/No)?

1.4.8 PROCESS
This provides access to another device process e.g. MONITOR, VISEVEN, or CONFIG. Once a new process has
been accessed, you can send specific commands or receive the process output. To obtain the process identifier,
enter the status command. Once connected to another process, such as MONITOR, VISEVEN, or CONFIG, use the
escape character (Ctrl+p) to return to the console manager (GESTCON).

Syntax:

*process <pid>

• < pid > this is the process identifier number for the console you want to access.

Example:

*process 4
User Configuration
Config>

When in one of the protocol menus such as Conf IP> or IP>, use the exit command to return from the process menu
you are currently in.

1.4.9 RESTART
Restarts Teldat Router without reloading the software. This has the following effects:

• Software counters are zeroized.

• Connected networks are tested.
• Routing tables are cleared.
• All packets are discarded until restart has completed.

10 Configuration and Monitoring

Teldat SA 1 Router Console

• Current software is executed.

Note

If this command is used during a remote terminal connection, the TELNET session is lost since all
device procedures are restarted.

Syntax:

*restart

Example:

*restart
Are you sure to restart the system(Yes/No)? y
Done
Restarting. Please wait ...............................................
APP DATA DUMP..........................................
Running application
Flash configuration read
Parsing text mode configuration ...
Configuration parsed
Initializing
Press any key to get started

1.4.10 SSH
Establishes an SSH connection as the remote device client with a specified address. This address can be an IPv4
Address or a domain name when a DNS client has been configured.

Syntax:

*ssh <address> [login <login-name> | port <port> | version <1-2> | cipher <cipher> | <cr> ]

The parameters you can specify in SSH are:

• < address > specifies the IP address or the device domain name you wish to access via SSH.
• login < login-name > specifies the user ID to use when logging in on the remote networking device running the
SSH server. If no user ID is specified, the default is the current user ID.
• port < port > specifies the port number for the remote host. Default is 22.
• version < 1-2 > specifies the SSH version to be used.
• cipher < cipher > selects the cipher specification for encrypting the session.

Examples:

SSH to router with address 192.168.212.201 specifing the user ID:

Router2 *ssh 192.168.212.201 login mbejar

(Press Control C to come back to local router)
The authenticity of host '192.168.212.201 (192.168.212.201)' can't be established.
RSA1 key fingerprint is 59:b7:6e:d3:1e:85:95:b4:88:03:a7:2e:3d:35:41:c5.
Are you sure you want to continue connecting (Yes/No)? yes
[email protected]'s password: ******

Teldat (c)2001-2015
Router model XXXXX CPU MPC860 S/N: YYYY/YYYYY

1 LAN, 2 WAN Line , 2 ISDN Line

CIT software version: ZZZZZ

Router1 *

SSH to router with address 192.168.212.201 with no user ID (local user root).

Router2 *ssh 192.168.212.201

(Press Control C to come back to local router)
[email protected]'s password: ******

Configuration and Monitoring 11

1 Router Console Teldat SA

Teldat (c)2001-2015
Router model XXXXX CPU MPC860 S/N: YYYY/YYYYY

1 LAN, 2 WAN Line , 2 ISDN CIT software version: ZZZZZ

Router1 *

SSH to router with address 192.168.212.201 using user ID and port 50 when the SSH server is NOT listening to this
port and connection cannot be established.

Router2 *ssh 192.168.212.201 login mbejar port 50

(Press Control C to come back to local router)
Connect to host 192.168.212.201 port 50: Connection reset by peer.
Router2 *

SSH to router with address 192.168.212.201 using user ID and port 50 when the SSH server is listening to port 50
too.

Router2 *ssh 192.168.212.201 login mbejar port 50

(Press Control C to come back to local router)
[email protected]'s password: ******

Teldat (c)2001-2015
Router model XXXXX CPU MPC860 S/N: YYYY/YYYYY

1 LAN, 2 WAN Line , 2 ISDN Line

CIT software version: ZZZZZ

Router1 *

SSH to router with address 192.168.212.201 forcing version 1 when SSH server only supports SSHv2 and connec-
tion cannot be established.

Router2 *ssh 192.168.212.201 login mbejar version 1

(Press Control C to come back to local router)
Protocol major versions differ: 1 vs. 2.
SSH connection closed.
Router2 *

SSH to router with hostname ares.id.teldat.com using user ID.

Router2 *ssh ares.id.teldat.com login mbejar

(Press Control C to come back to local router)
The authenticity of host '192.168.212.7 (192.168.212.7)' can't be established.
RSA key fingerprint is b4:53:cc:47:3e:bc:c9:82:ca:0c:97:8e:4f:f4:6c:b6.
Are you sure you want to continue connecting (Yes/No)? yes
[email protected]'s password: ******
Linux ares 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent

permitted by applicable law.
Last login: Fri Nov 20 08:31:24 2015 from 192.168.212.19
mbejar@ares:~$

Command history:

Release Modification
11.00.05 SSH client was introduced as of version 11.00.05.
11.01.00 SSH client was introduced as of version 11.01.00.

12 Configuration and Monitoring

Teldat SA 1 Router Console

1.4.11 STATUS
Provides you with each process identifier (pid), as well as the name.

Syntax:

*status

Example:

*status
System Processes:
PID NAME

1 Main console
2 Event viewer
3 Monitor console
4 Config console
5 Running config console
6 Telnet client
*

1.4.12 TELNET
Establishes a Telnet connection as the remote device client with a specified address. This address can be an IPv4
Address, an IPv6 Address or a domain name when the DNS client has been configured.

Syntax:

*telnet
<address> [source <address> | port <port> | <cr> ]
vrf <vrf>
<cr>

You can specify the VRF through the vrf option when you want to start the telnet session. Where this option is not
used, the main VRF is used. When a VRF is specified, the source and destination addresses must be IPv4.

Where no parameters are entered ( telnet <cr> option), you are asked for all the telnet parameters taking the main
VRF as the VRF. Consequently, the telnet source and destination addresses must be IPv4.

The parameters you can specify in Telnet are:

• < address > specifies the IP address or the device domain name you wish to access via telnet.
• source < address > specifies the source IP address to use for Telnet. If a domain name has been specified as
destination, the source address must be IPv4.
• port < port > specifies the destination port to use for Telnet.

Examples:

Telnet to device with address 172.123.23.67:

*telnet 176.123.23.67
Trying to connect...
(Press Control S to come back to local router)
Connection established

Telnet to router 172.24.78.92 using source address 80.1.1.1 and port 6623.

FTP *telnet
Telnet destination []? 172.24.78.92
Telnet source [172.24.78.94]? 80.1.1.1
Telnet port [23]? 6623
Trying to connect...
(Press Control S to come back to local router)
Connection established

Telnet to router 172.24.78.92 using source address 80.1.1.1and port 6623, specifying the parameters with options.

FTP *telnet 172.24.78.92 source 80.1.1.1 port 6623

Trying to connect...
(Press Control S to come back to local router)

Configuration and Monitoring 13

1 Router Console Teldat SA

Connection established

Telnet to router with IPv6 2001:db8:1::1 address using source address 2001:db8:1::2. As the destination is IPv6, you
need to specify the parameters with options:

*telnet 2001:db8:1::1 source 2001:db8:1::2

Trying to connect...
(Press Control S to come back to local router)
Connection established

Telnet to router with domain name router1.midominio.es:

FTP *telnet router1.midominio.es

Trying to connect...
(Press Control S to come back to local router)
Connection established

Telnet to router 172.24.78.92 using the router_aux VRF.

FTP *telnet vrf router_aux 172.24.78.92

Trying to connect...
(Press Control S to come back to local router)
Connection established

1.4.13 VRF-TELNET
Establishes a Telnet connection in the indicated VRF, as client for the remote device whose address is specified.
This address can be a domain name where the DNS client is configured.

Syntax:

*telnet <vrf>
<address> [source <address> | port <port> | <cr> ]
<cr>

• < vrf > specifies the VRF name where you wish to initiate the telnet session.

Where no additional parameters are entered ( vrf-telnet <vrf> <cr> option), you are asked for all the telnet paramet-
ers.

Parameters that can be specified in Teldat are as follows:

• < address > specifies the IP address or domain name for the device you wish to access via telnet.
• source < address > specifies the source IP address to use for Telnet.
• port < port > specifies the destination port to use for Telnet

Examples:

Telnet to router with address 172.123.23.67 in the VRF client:

*vrf-telnet client 176.123.23.67

Trying to connect...
(Press Control S to come back to local router)
Connection established

Telnet to router with address 172.24.78.92 in the VRF client using source address 80.1.1.1 and port 6623.

FTP *vrf-telnet
vrf tag []? client
Telnet destination []? 172.24.78.92
Telnet source [172.24.78.94]? 80.1.1.1
Telnet port [23]? 6623
Trying to connect...
(Press Control S to come back to local router)
Connection established

Telnet to router 172.24.78.92 in the client VRF using source address 80.1.1.1 and port 6623 specifying the paramet-
ers with options.

FTP *vrf-telnet client 172.24.78.92 source 80.1.1.1 port 6623

Trying to connect...
(Press Control S to come back to local router)

14 Configuration and Monitoring

Teldat SA 1 Router Console

Connection established

Telnet to router with domain name router1.midominio.es in the VRF client:

FTP *vrf-telnet client router1.midominio.es

Trying to connect...
(Press Control S to come back to local router)
Connection established

Configuration and Monitoring 15

2 Teldat Router Configuration Teldat SA

Chapter 2 Teldat Router Configuration

2.1 Introduction
There are two virtual devices integrated in the Teldat Router:

• A router performing the internetworking functions.

• A packet switch from the router, as well as from the X.25, and ISDN ports when they carry X.25.

As the above figure shows, each virtual device manages its own set of interfaces. You must accurately identify the
different interfaces and know whether an interface belongs to the router or the node.

The interfaces in the Teldat Router configuration are identified through a name.

The name for the physical interfaces is made up of a text string followed by two numbers separated by a slash. This
text indicates the type of interface (serial line, ISDN, etc). The first of these two numbers indicates the interface loca-
tion in the device (0 for the motherboard, 1 for the first extension pci, 2 for the second etc.) and the second number
indicates the event number for said interface for the same location (serial line 0, 1, 2, etc.).

For interfaces added by the user, the name consists of a text string, which indicates the type of interface, and an
identifier number, which must be unique for each interface of the same type. An exception to this rule is the subinter-
faces, as their name is made up with the base interface number, over which these are configured, following by a peri-
od (.) and an identifier number. Once again, this identifier number must be unique for each subinterface pertaining to
the same base interface.

The table of interface identifiers is obtained through the list devices command in the configuration process. The out-
put of this command in a specific device is shown below:

Config>list devices
Interface Connector Type of interface
ethernet0/0 LAN1 Quicc Ethernet
serial0/0 SERIAL0/WAN1 AT COM
atm0/0 DSL1 ATM
bri0/0 BRI/ISDN1 ISDN Basic Rate Int
x25-node --- Router->Node
Config>

The first column indicates the interface name ( Interface), the second column, the physical connector the interface
(Connector) corresponds to, and the third column specifies the type of interface programmed.

You must enter the name when selecting an interface (although you don’t have to enter all the characters). For phys-
ical interfaces, simply enter the beginning of the text, thus ensuring this does not coincide with any other interface
text, followed by the position, if there is more than one interface of the same type. You don't always need to introduce
the position (X/X): this is only necessary when various interfaces of the same type are present (e.g. various serial in-
terfaces).

Examples:

Config>list devices
Interface Con Type of interface CSR CSR2 int
ethernet0/0 LAN1 Fast Ethernet interface fa200e00 27
serial0/0 WAN1 X25 fa200a00 fa203c00 5e
serial0/1 WAN2 X25 fa200a20 fa203d00 5d
serial0/2 WAN3 X25 fa200a60 fa203f00 5b
bri0/0 ISDN1 ISDN Basic Rate Int fa200a40 fa203e00 5c

16 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

x25-node --- Router->Node 0 0

Config>

Example of the valid commands to access the first serial interface on the motherboard (WAN 1) depending on the
devices listed in the above box.

Config>network serial0/0
Config>network ser0/0
Config>network ser0
Config>network s0

Example of erroneous commands:

Config>network serial
Config>network ser
Config>network ser0/4
Config>network s7

This network serial command is incorrect as there are various interfaces in the device with serial text; consequently
you need to specify the interface location.

Example of valid commands to access the bri interface:

Config>network bri0/0
Config>network b0/0
Config>network bri0
Config>network b

As there is only one bri , you don't need to indicate the position within the equipment, simply introduce its text string,
which does not necessarily need to be complete. The only characters necessary are those distinguishing this from
other interfaces. As there aren’t any other interfaces beginning with the letter b, said letter suffices.

• Another important aspect is there are interfaces, which do not have a physical connector associated. This is the
case of the x25-node interface in the example. Said interface allows the virtual machines to join and consequently
does not have an external connector associated.

With this information, you can modify the previous figure for this case:

Suppose now you change the protocol in one of the WAN lines, through the set data-link command and then consult
the interface table.

In the following example, the X25 protocol is assigned to physical line 1:

Config>set data-link x25 serial0/0

Config>list devices

Interface Connector Type of interface

ethernet0/0 FE0/LAN1 Fast Ethernet interface
ethernet0/1 FE1/LAN2 Fast Ethernet interface
serial0/0 SERIAL0/WAN1 X25
serial0/1 SERIAL1/WAN2 X25
bri0/0 BRI/ISDN1 ISDN Basic Rate Int
x25-node --- Router->Node
Config>

Configuration and Monitoring 17

2 Teldat Router Configuration Teldat SA

As you can see, there is now an additional interface managed by the router and, one less managed by the node.

In this new example the diagram is as follows:

In the following example, a generic Frame Relay interface is added over an ISDN basic access:

Config>add device fr 1
Config>

The interface identifier is a number between 1 and 9999. This allows you to distinguish the created interface from
other interfaces of the same type i.e. other frame-relay dial interfaces.

Config>list devices

Interface Connector Type of interface

ethernet0/0 FE0/LAN1 Fast Ethernet interface
ethernet0/1 FE1/LAN2 Fast Ethernet interface
serial0/0 SERIAL0/WAN1 X25
serial0/1 SERIAL1/WAN2 X25
bri0/0 BRI/ISDN1 ISDN Basic Rate Int
x25-node --- Router->Node
fr1 --- Generic FR
Config>

For those dial interfaces added by the user, you don’t have to enter the whole name to refer to the interface. Simply
enter sufficient characters to distinguish this from the other interfaces. The identifier however is mandatory.

Example of valid commands to access the FR dial interface, created according to the devices listed in the previous
box:

Config>network fr1
Config>network f1

In this new example, the diagram is as follows:

Where we have ATM interfaces, subinterfaces associated to said interfaces can be configured. E.g. in a configura-
tion with an xDSL card in SLOT 3:

18 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

Config>list devices
Interface Connector Type of interface
ethernet0/0 GE0/FE0/LAN1 GigabitEthernet interface
ethernet0/1 GE1/FE1/LAN2 GigabitEthernet interface
x25-node --- Router->Node
atm3/0 SLOT3 Generic ATM
Config>

Add a subinterface associated to said interface:

Config>add device atm-subinterface atm3/0 2

Config>list devices
Interface Connector Type of interface
ethernet0/0 GE0/FE0/LAN1 GigabitEthernet interface
ethernet0/1 GE1/FE1/LAN2 GigabitEthernet interface
x25-node --- Router->Node
atm3/0 SLOT3 Generic ATM
atm3/0.2 --- ATM subinterface
Config>

To access said interface, enter the base interface name followed by a period and the subinterface ID. This ID must
be unique for all subinterfaces associated to the same base interface, so they can be differentiated from each other.
The ID must be entered to access the subinterface, even if there is only one subinterface. When indicating the base
interface name, follow the same rules as for the physical interfaces.

Example of the valid commands to access an atm subinterface created according to the devices listed in the previ-
ous box:

Config>network atm3/0.2
Config>network atm3.2
Config>network atm.2
Config>network a.2

As there is only one ATM base interface, you don't need to indicate the location.

2.2 Configuration Process

The configuration process (config or running-config) allows you to configure router parameters such as:

• Interfaces.
• Protocols.

The configuration process CONFIG allows you to display and change the router startup configuration and store it in
flash memory or in a smart card. To store the changes made in this procedure, execute the save command. The
router must be restarted so the configuration changes take effect. To restart the router, do either of the following:

• Execute the restart command at the * prompt in the console manager or

• Switch the router off then on.

The RUNNING-CONFIG configuration process allows you to display and dynamically change the router active con-
figuration and store it either in the flash memory or in a smart card. So the changes made in this process are stored,
execute the save command. Changes made in the RUNNING-CONFIG process take immediate effect.

Note

All the active configuration can be displayed in the RUNNING-CONFIG process, however you cannot
modify all of it. This means not all the commands are available in the RUNNING-CONFIG process, for
example no config.

The configuration procedures CONFIG and RUNNING-CONFIG are framed into the router structure as shown in the
following figure:

Configuration and Monitoring 19

2 Teldat Router Configuration Teldat SA

2.3 Configuration procedure user interface

Configuration procedure enter/exit

To enter the configuration procedure CONFIG from prompt * in the console manager GESTCON, enter the config
command.

To enter the configuration procedure RUNNING-CONFIG from prompt * in the console manager GESTCON, enter
the running-config command.

Example:

*config
Config>

To exit the configuration procedure and return to console manager GESTCON prompt *, press the escape character
(Ctrl-p by default).

Simultaneously accessing the configuration menus

When various users simultaneously access a device (via telnet or console), the Teldat Router, to prevent contradic-
tions due to parallel configuration processes, blocks simultaneous access to certain configuration menus.

When this conflict arises, the user can't access the configuration environment and device sends information on the
circumstances triggering said situation.

Example:

+system telnet
ID USER IP ADDRESS:PORT CONNECTION TIME INACTIVITY TIME
-------------------------------------------------------------------

2 sample 192.168.1.2:1 08/03/05 12:29:26 0 min *

1 root 172.24.51.128:131 08/03/05 12:28:59 29 min
+

• User Console “root”

20 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

*config
Config>protocol ip
-- Internet protocol user configuration --
IP config>

• User Console “sample”

*config
Config>protocol ip
CLI Error: Command locked by another user
CLI Error: Command error
Config>

Here, the sample user is trying to access the IP protocol configuration environment and the device prevents it, as the
root user is currently accessing said menu.

Show Command
The show command can be executed from any configuration process menu. This allows three options:

Config>show ?
all-config
config
menu
Config>

The show all-config command displays the net configuration for all device menus and submenus the user can ac-
cess. I.e. displays all the commands, which must be entered through the console to configure the device as it is,
when executing the show all-config command.

Example:

Config>show all-config
; Showing System Configuration for access-level 15 ...
; ATLAS50 Router 9 48 Version 10.7.0
log-command-errors
no configuration
;
network ethernet0/0
; -- Ethernet Interface User Configuration --
ip address 172.24.78.116 255.255.0.0
;
;
;
;
;
exit
;
;
;
;
network ethernet0/1
; -- Ethernet Interface User Configuration --
no ip address
;
exit
;
;
;
;
;
network x25-node
; -- X25-node interface configuration --
no ip address
;
exit
;
protocol ip
; -- Internet protocol user configuration --

Configuration and Monitoring 21

2 Teldat Router Configuration Teldat SA

classless
;
tvrp
; -- TVRP Configuration --
enable
;
group 1 ip 172.24.78.128
group 1 local-ip 172.24.78.116
;
exit
;
exit
;
;
dump-command-errors
end
; --- end ---
Config>

This command shows the whole of the device net configuration, which the user can access independently of the
menu and submenu, where the user is located. From the IP menu, for example:

IP config>show all-config
; Showing System Configuration for access-level 15 ...
; ATLAS50 Router 9 48 Version 10.7.0
log-command-errors
no configuration
;
network ethernet0/0
; -- Ethernet Interface User Configuration --
ip address 172.24.78.116 255.255.0.0
;
;
;
;
;
exit
;
;
;
;
network ethernet0/1
; -- Ethernet Interface User Configuration --
no ip address
;
exit
;
;
;
;
;
network x25-node
; -- X25-node interface configuration --
no ip address
;
exit
;
protocol ip
; -- Internet protocol user configuration --
classless
;
tvrp
; -- TVRP Configuration --
enable
;
group 1 ip 172.24.78.128
group 1 local-ip 172.24.78.116
;

22 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

exit
;
exit
;
;
dump-command-errors
end
; --- end ---
IP config>

The show config command displays the net configuration for all menus and submenus the user can access, which
can be accessed from the menu where the user is located when he executes this command.

Example:

Config>show config
; Showing System Configuration for access-level 15 ...
; ATLAS50 Router 9 48 Version 10.7.0
log-command-errors
no configuration
;
network ethernet0/0
; -- Ethernet Interface User Configuration --
ip address 172.24.78.116 255.255.0.0
;
;
;
;
;
exit
;
;
;
;
network ethernet0/1
; -- Ethernet Interface User Configuration --
no ip address
;
exit
;
;
;
;
;
network x25-node
; -- X25-node interface configuration --
no ip address
;
exit
;
protocol ip
; -- Internet protocol user configuration --
classless
;
tvrp
; -- TVRP Configuration --
enable
;
group 1 ip 172.24.78.128
group 1 local-ip 172.24.78.116
;
exit
;
exit
;
;
dump-command-errors
end

Configuration and Monitoring 23

2 Teldat Router Configuration Teldat SA

; --- end ---

Config>

PROBLEM HERE: CONSULT Miguel Fadon

As you can see, executing the show config command (from the root menu) is the same as executing the show all-
config command. However, if you execute said show config command from the IP menu, only the IP and the TVRP
configurations are shown:

IP config>show config
; Showing Menu and Submenus Configuration for access-level 15 ...
; ATLAS50 Router 9 48 Version 10.7.0
classless
;
tvrp
; -- TVRP Configuration --
enable
;
group 1 ip 172.24.78.128
group 1 local-ip 172.24.78.116
;
exit
;
IP config>

The show menu command displays the configuration of the menu where the command is executed, but does not
display the submenu configuration.

Examples:

Config>show menu
; Showing Menu Configuration for access-level 15 ...
log-command-errors
no configuration
dump-command-errors
end
Config>

IP config>show menu
; Showing Menu Configuration for access-level 15 ...
classless
;
IP config>

TVRP config>show menu

; Showing Menu Configuration for access-level 15 ...
enable
;
group 1 ip 172.24.78.128
group 1 local-ip 172.24.78.116
;
TVRP config>

The configuration generated by the show command can be copied to a text file and edited to the user’s require-
ments. Subsequently it can be installed in an unconfigured device, automatically configuring it.

If, during the period where the router is displaying the configuration, you wish to abort the process, enter the escape
character (default is Ctrl + p).

Options List
When configuring a device, you are frequently asked to select an option to configure determined entities for the
router such as Frame Relay PVCs ( Teldat Dm703-I ) or TVRP groups (Teldat Dm725-I ).

On selecting an option, you don't need to enter the whole the text, simply enter sufficient characters to distinguish
this option from the rest.

Examples:

serial0/0 FR config>pvc 16 ?
backup Configure several backup parameters

24 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

Bc Outgoing Committed Burst Size

Be Outgoing Excess Burst Size
CIR Outgoing Committed Information Rate
compression Enable/disable compression for this circuit
default Create the virtual circuit
encapsulation Encapsulation type
encrypt Enable/disable encryption
fragmentation-size Forced fragmentation size
inverse-arp Inverse ARP configuration for this dlci
name Set the virtual circuit name
no
route Set static route for PVC switching
serial0/0 FR config>pvc 16 cir 32000
serial0/0 FR config>

Here, you could have simply entered ci as no other option begins with this. However entering just c would be invalid
as there is another option with c (compression), consequently triggering an error.

Transaction command
This allows you to execute the transactions from the configuration menus. A transaction allows you to enter configur-
ation commands, temporarily suspending its application. Once the transaction has terminated, the commands
entered prior to the start of the transaction are executed and permanently applied to the configuration.

You can abort an active transaction, so commands entered the beginning of the transaction are not applied to the
configuration.

Optionally you can configure the transaction so when a command, from one of those entered, returns an error, no
change is applied to the configuration on termination. This is useful when, through a remote management applica-
tion, you want to automatically apply a set of configuration commands.

The transaction command can be executed from any configuration menu, both in static as well as the dynamic con-
figuration. There are four options:

Config$transaction ?
abort Terminate an active transaction discarding changes
commit Terminate an active transaction and apply changes
fail-on-error Make a transaction to fail if any command returns an error
start Start a CLI transaction
Config$

The transaction abort command aborts an active transaction, canceling execution of commands entered from the
start of the transaction.

The transaction commit command terminates an active transaction, applying changes in the configuration due to
commands entered prior to the start of the transaction. If you have configured the transaction to not apply changes
when a command fails (through transaction fail-on-error) and one of the entered commands returns an error, the
errors detected are reported and no change is applied.

The transaction fail-on-error command configures an active transaction to prevent the application of any changes
to finalize the transaction with transaction commit, if one of the entered commands returns an error.

The command transaction start starts a transaction, at this point this begins to register the commands entered, and
apply them simultaneously, to terminate the transaction with transaction commit.

2.4 Configuration commands

This section describes the configuration commands (CONFIG and RUNNING CONFIG process). Each command in-
cludes a description, syntax and one example. The following table summarizes the configuration commands.
Command Function
ADD Allows you to create a virtual interface.
AUTOINSTALL Configures the autoinstall parameters.
BACKUP-FILES Makes a backup copy of the system files.
BANNER Allows you to configure banners in the device.
CONFIG-MEDIA Allows you to specify the active storage unit: flash, smart card or both.
CONFIRM-CFG-NEEDED Enables the necessity to confirm the saved configuration.
CONFIRM-CFG Confirms the current configuration.

Configuration and Monitoring 25

2 Teldat Router Configuration Teldat SA

COPY Allows you to copy the Running Config configuration to Config.

DESCRIPTION Configuration description.
DISABLE Disables a specific feature in the router.
DUMP-COMMAND-ERRORS Displays errors in the commands line.
ENABLE Enables a specific feature in the router.
EVENT Enters the events monitoring configuration procedure.
FEATURE Defines the additional features of the router, not associated with any predeter-
mined interface.
FILE Allows you to carry out operations with files (list and copy).
FIRMWARE-CHECKING Enables checking when firmware files are required.
FORMAT Formats a storage unit in the device.
GLOBAL-PROFILES Accesses the profiles configuration menu, ATM, PPP etc.
LICENCE-CHANGE Changes the current license.
LIST Shows the system parameters and hardware configuration.
LOG-COMMAND-ERRORS Begins to save errors in the commands line.
MANAGEMENT Enters the master router configuration environment.
NETWORK Enters the configuration menu for a specific interface.
NO Invalidates a command action or sets the default value.
NODE Enters the X.25/ISDN, XOT or 270 Node configuration.
PRIVILEGE Allows you to specify personalized execution permissions.
PROTOCOL Enters the configuration of a specific protocol.
RUSH-ENGINE Rush engine configuration.
SAVE Allows you to save the configuration in the active storage unit.
SET Configures system parameters, buffers, device name, etc.
STRONG-PASSWORD Enables checking for a safe password.
TELEPHONY Configures Voice over IP parameters.
TIME Allows you to view and change the system data and time.
UCI Allows you to configure the Teldat Router encryption unit.
USER Allows you to configure users.
END End of configuration.

2.4.1 ADD
Allows you to create a virtual interface.

Syntax:

Config>add <option>
device Create a virtual device

• < option > specifies the selected option.

The only option available for this command is:

2.4.1.1 ADD DEVICE

Syntax:

Config>add device <virtual interface> [options]

• < virtual interface> this is the virtual interface you want to create. To discover what types of interfaces are avail-
able, enter add device ?

Config>add device ?
atm-subinterface Create a virtual ATM Subinterface interface
bvi Create a virtual Bridge interface
bvi-subinterface Create a virtual Bridge subinterface
dial-routing Create a virtual Dial-Route interface
direct-ip Create a virtual Direct IP interface
eth-subinterface Create a virtual Ethernet Subinterface interface
fr Create a virtual Frame-Relay interface

26 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

fr-subinterface Create a virtual FR Subinterface interface

hdlc Create a virtual HDLC interface
l2tp Create a virtual L2TP interface
loopback Create a virtual Loopback interface
ppp Create a virtual PPP interface
rcellular Create a virtual Remote Celullar interface
tnip Create a virtual TNIP interface
voip-cellular Create a virtual VoIP interface over cellular network
voip-dummy Create a virtual VoIP interface with no hardware
voip-isdn Create a virtual VoIP interface over ISDN
wlan-subinterface Create a virtual Wireless LAN subinterface
x25 Create a virtual X25 interface
xot Create a virtual XOT interface

• [options] The options available depend on the type of virtual interface you wish to create. These are described in
the manual specifically related to said interface.

Example:

Config>add device ppp ?

<1..10030> Interface Id
Config>add device ppp 1 ?
<cr>
Config>add device ppp 1
Config>

For further information, please see the manual associated to the virtual interface you wish to create.

2.4.2 AUTOINSTALL
Establishes the device parameters for autoinstallation through Frame Relay from a TELDAGES network manager.

Syntax:

Config>autoinstall <parameter> [value]

identifier Configure identifier type
management-host Configure management host

• < parameter> this is the autoinstallation parameter identifier to configure.

• [value] value to assign to the above specified parameter.

Command history:

Release Modification
11.00.03 This command is obsolete as of version 11.00.03.

There are two types of configurable parameters:

2.4.2.1 AUTOINSTALL IDENTIFIER

Specifies the type of device identifier, so it is correctly interpreted from the TELDAGES network manager.

Syntax:

Config>autoinstall identifier <type>

• <type> this is the type of device identifier. Currently only serial is available, which uses the device serial number to
identify it for the network manager.

Example:

Config>autoinstall identifier serial

Config>

2.4.2.2 AUTOINSTALL MANAGEMENT-HOST

Identifies the management station where remote autoconfiguration is executed.

Syntax:

Config>autoinstall management-host <host identifier>

Configuration and Monitoring 27

2 Teldat Router Configuration Teldat SA

• <host identifier> management station identifier. This identifier can be an IP address or a Fully Qualified Domain
Name/Hostname.

Example:

Config>autoinstall management-host www.gestion.teldat.es

Config>

2.4.3 BACKUP-FILES
This creates a recovery point by making a copy of the system files, from the primary partition to the backup partition.
Should the filing system become corrupt, the device automatically restores the files from the recovery point and can
continue operating.

The configuration monitoring command shows information relative to the recovery process, indicating if it has star-
ted up normally (from the first partition) or if it’s being restored from the recovery point (from the backup partition).

The configuration command [no] firmware-checking determines if restoration for the filing system is enabled where
a significant firmware file is corrupt.

Note

This command is only valid in devices with partitioned flash memory.

Syntax:

Config>backup-files

Example 1:

Config>backup-files
Backup in progress...
Backup successful.
Config>

In this example, a recovery point has been successfully created.

Example 2:

Config>backup-files
CLI Error: Backup device not available.
CLI Error: Command error
Config>

In this example, the device does not have a partitioned flash. Consequently, the command has returned an error
message, without creating a recovery point.

2.4.4 BANNER
Allows you to configure banner in the device.

Syntax:

Config>banner <type>
login Set login banner
exec Set exec banner

< type > specifies the type of banner to configure.

2.4.4.1 Banner login

Allows you to configure an access banner in the device, which is always displayed when a user tries to access said
device through console, telnet or ftp.

To enter various lines of text in the banner, execute the banner login command, in order and consecutively, followed
by each line of text (between inverted commas if there are any spaces).

The size of an access banner is limited to 15 lines of text, each containing 80 characters.

Syntax:

28 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

Config>banner login <line of text>

Example:

Config>banner login "###########################################################################"

Config>banner login "#Este equipo es propiedad de Sample, S.A. y su uso está restringido a sus #"
Config>banner login "# empleados. Por favor, aborte esta conexión si usted no es empleado de #"
Config>banner login "# Sample, S.A. o tiene una autorización legal para acceder al equipo. #"
Config>banner login "###########################################################################"
Config>show config
; Showing System Configuration for access-level 15 ...
; ATLAS50 Router 9 48 Version 10.7.0
log-command-errors
no configuration
banner login "################################################################################"
banner login "# Este equipo es propiedad de Sample, S.A. y su uso está restringido a sus #"
banner login "# empleados. Por favor, aborte esta conexión si usted no es empleado de #"
banner login "# Sample, S.A. o tiene una autorización legal para acceder al equipo. #"
banner login "################################################################################"
;
;
;
;
network ethernet0/0
; -- Ethernet Interface User Configuration --
no ip address
;
exit
;
;
;
network ethernet0/1
; -- Ethernet Interface User Configuration --
no ip address
;
exit
;
;
;
;
network x25-node
; -- X25-node interface configuration --
no ip address
;
exit
;
;
;
dump-command-errors
end
; --- end ---
Config>save yes

Building configuration as text... OK

Writing configuration... OK on Flash
Config>
*restart
Are you sure to restart the system(Yes/No)? y
Done
Restarting. Please wait ..................................................
APP DATA DUMP......................................................................
Bios-stack used: 0x1498
Bios-stack free: 0x2B68
Aux-stack used: 0x0
Aux-stack free: 0x2000
Running application
Flash configuration read
Parsing text mode configuration ...

Configuration and Monitoring 29

2 Teldat Router Configuration Teldat SA

Configuration parsed
Initializing
Press any key to get started

################################################################################
# Este equipo es propiedad de Sample, S.A. y su uso está restringido a sus #
# empleados. Por favor, aborte esta conexión si usted no es empleado de #
# Sample, S.A. o tiene una autorización legal para acceder al equipo. #
################################################################################
User:

By default, the device does not have an access banner configured.

2.4.4.2 Banner exec

Configures a welcome banner, which is displayed when a user accesses the device through console, Telnet, SSH or
FTP.

If the banner contains more than one line, then each line must be independently configured through the banner exec
command, entering each line in the order you want them displayed. If the line text contains spaces, these must be
entered between quotation marks.

The banner is limited to a maximum of 15 lines of text and 80 characters per line.

Syntax:

Config>banner exec <text>

Example:

Config>banner exec "##############################################################"

Config>banner exec " "
Config>banner exec "............::::::::::: WELCOME :::::::::::............"
Config>banner exec " "
Config>banner exec "##############################################################"
Config>save yes
Building configuration as text... OK
Writing configuration... OK on Flash as CONFIG
Config>
*restart
Are you sure to restart the system(Yes/No)? y
Restarting. Please wait ....................................................
APP DATA DUMP...................................................
Bios-stack used: 0x14E8
Bios-stack free: 0x2B18
Aux-stack used: 0x0
Aux-stack free: 0x2000
Running application
WARNING: Running with super licence.
Flash configuration read
Parsing text mode configuration ...
Configuration parsed
Initializing
Press any key to get started
Teldat (c)2001-2012

Router model Super * * CPU MPC8260 S/N: 472/04709

2 LAN, 2 WAN Lines, 1 ISDN Line
CIT software version: 11.00.00 Oct 25 2012 18:43:58

##############################################################
............::::::::::: WELCOME :::::::::::............

##############################################################
*

30 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

2.4.5 CONFIG-MEDIA
This allows you to select the active storage device where the configurations are saved on applying the configuration
command save. This is also the default media in the file list command.

There may be two storage medias in the routers: flash memory and smart cards. All routers take flash as the basic
storage unit. The availability of smart cards depends on the type of router. To find out if your router supports smart
card, please see the installation manual.

By default, the router has smartcard-flash configured in those routers that support smart card, and flash in those that
don’t. You can check which unit is active through the file list configuration command.

Syntax:

Config>config-media <media>
flash Configurations are stored only in Flash
smartcard Configurations are stored only in SmartCard
smartcard-flash Configurations are stored in SmartCard and Flash

• < media > specifies the name of the storage unit to be used.

For further information on the use of storage units, please see the file list and file copy commands described in this
manual, as well as the installation manual for your router. For further information on how to select a file as the active
configuration, please see the set file command described in this manual.

The behavior described below alters slightly if the microswitch e is set to ON. For further information please see the
installation manual for your router.

2.4.5.1 CONFIG-MEDIA FLASH

Specifies the flash memory as the only active storage unit when reading or writing configurations.

On booting the router, the configuration is read from flash. If the active configuration file is not found, the device
boots with the default configuration. On saving the configuration, through the save command, it's saved in flash
memory with the name of the active file.

Example:

Config>config-media flash

2.4.5.2 CONFIG-MEDIA SMARTCARD

Specifies the smart card as the only active storage unit when reading or writing configurations.

On booting the device the configuration is read from the smart card . If the card is not present or the active configura-
tion file is not found, the device boots with the default configuration. On saving the configuration through the save
command, it is saved in the smart card with the name of the active file.

Example:

Config>config-media smartcard

2.4.5.3 CONFIG-MEDIA SMARTCARD-FLASH

Specifies both the smart card as well as the flash memory as active storage devices when reading or writing config-
urations. The smart card is considered as having priority over the flash memory.

Initially on booting, the configuration is read from the smart card . If the card is not present or the active configuration
file cannot be found, the operation is repeated from flash. If the file is not found in flash, then the router boots with the
default configuration. After reading the smart card configuration file, the router checks to see if this is written in flash .
If the configuration is not present, then the device enters it so both medias are synchronized.

On saving the configuration through the save command, the configuration is saved in both the smart card and flash
with the name of the active file. The console indicates the devices where the configuration has been stored and,
through a warning text, shows the devices where recording has not been possible.

Example:

Config>config-media smartcard-flash

Configuration and Monitoring 31

2 Teldat Router Configuration Teldat SA

2.4.6 CONFIRM-CFG
Confirms the current configuration. A configuration must be saved with the configuration confirmation function activ-
ated. Please see confirm-cfg-needed.

Syntax:

Config>confirm-cfg

This action can also be executed via SNMP. Please see CONFIRM-CFG-NEEDED on page 32.

2.4.7 CONFIRM-CFG-NEEDED
Enables the necessity to confirm the saved configuration. If you have executed this command, the configuration is
saved in TEMP.CFG for subsequent checking. If after restarting the configuration is not confirmed with the confirm-
cfg command, within the configured time, the device restarts with the previous configuration. If the configuration is
confirmed, it is saved with the corresponding name i.e. the use of TEMP.CFG is transparent to the user. Should the
new configuration force the device restart before the programmed test time is reached, after ten restarts without the
configuration being confirmed, the previous configuration is restored. If you execute the no confirm-cfg command,
the device restarts with the previous configuration. The no confirm-cfg-needed command disables the necessity to
confirm newly saved configurations.

Syntax:

Config>confirm-cfg-needed <option>
default Enables the need of configuration confirmation
timeout Sets a timeout to wait for confirmation

• < option > specifies the selected action.

2.4.7.1 CONFIRM-CFG-NEEDED DEFAULT

Enables the necessity to confirm the saved configurations with a test time of 10 minutes.

Syntax:

Config>confirm-cfg-needed default

Example:

Config>confirm-cfg-needed default
Config>

2.4.7.2 CONFIRM-CFG-NEEDED TIMEOUT

Configures the new configuration test time, which the device waits before restarting the previous configuration if con-
firmation is not carried out. The minimum is one minute and the maximum is 5 weeks.

Syntax:

Config>confirm-cfg-needed timeout <time>

• < option > specifies the test time in any of the following formats: Xw, Xd, Xh, Xm, Xs, HH:MM, HH:MM:SS.

Example:

Config>confirm-cfg-needed timeout 30s

Config>

You can execute the confirmed save configuration feature through SNMP. To do this, three new SNMP variables
have been created with their corresponding OIDs:

• telAdminStatusConfirmConfig (OID: 1.3.6.1.4.1.2007.1.2.14). This variable serves to confirm (or not) the current
configuration.

In a write operation, setting this variable to 1 confirms the current configuration, and setting it to 0 rejects the cur-
rent test configuration and the device restarts with the previous configuration.

In a read operation, a 0 value (confirmed) indicates the current configuration has been confirmed. A 1 value
(test_cnfg_inactive) indicates the current configuration has not been confirmed as yet (consequently this is a test
configuration) and neither is it active: the previous configuration is still active. A 2 value (test_cnfg_active) indicates
the current configuration has not been confirmed as yet (and consequently this is a test configuration), but we are

32 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

dealing with an active configuration. A value of 3 (configuration_recovered) indicates the previous configuration
has been recovered, is confirmed and active. A value of 4 (undefined) only occurs where the confirmed saved con-
figuration is disabled, so the use of said SMNP variable makes no sense.

There are three scenarios where recuperation of the old configuration can be produced (consequently the telAd-
minStatusConfirmConfig variable takes the configuration_recovered value 3):

a) After the confirmation wait timer has timed out without confirming the test configuration.

b) After 10 consecutive device restarts (produced before the confirmation wait timer has timed out). The aim of
restoring the old configuration in this scenario is to protect us should the new configuration make the device restart
before reaching end of the programmed test time.

c) After rejecting the current test configuration through the no confirm-cnfg command (or through SNMP by enter-
ing a 0 in the telAdminStatusConfirm Config variable).
• telAdminStatusConfirmEnabled (OID: 1.3.6.1.4.1.2007.1.2.15). This variable serves to enable/disable the con-
firmed save.

In a write operation, setting this variable to 1 enables the necessity to confirm the saved configuration. Setting this
variable to 0 disables the necessity to configure the new saved configurations.

In a read operation, a 0 value (disable) indicates the confirmed save configuration feature is disabled. And a value
of 1 (enable) indicates that the confirmed save configuration is enabled.
• telAdminStatusTimeoutConfirm (OID: 1.3.6.1.4.1.2007.1.2.16). This variable serves to configure the value (in
seconds) the confirmed save configuration feature timer takes. I.e. this is the time the device waits before restart-
ing the old configuration if this is not confirmed.

The permitted values for this variable are from 60 (1 minute) and 3024000 (5 weeks). Default is 600 (10 minutes).

In a write operation, values between 60 and 3024000 configure the timer to the entered value.

In a read operation, values between 60 and 3024000 returns the seconds value to the value the timer is configured
with.

Therefore, a logical operating sequence for the confirmed save configuration via SNMP is:

• Initially the confirmed save configuration is disabled. The SNMP variables have the following values:

- telAdminStatusConfirmConfig = 4 (undefined)

- telAdminStatusConfirmEnabled = 0 (disable)

- telAdminStatusTimeoutConfirm = 600
• Enable the confirmed save configuration (setting the telAdminStatusConfirmEnabled SNMP variable value to 1).
The SNMP variables take the following values:

- telAdminStatusConfirmConfig = 0 (confirmed)

- telAdminStatusConfirmEnabled = 1 (enable)

- telAdminStatusTimeoutConfirm = 600
• Set the confirmation wait timer value to the value you want (1 minute for example). To do this, set the telAdmin-
StatusTimeoutConfirm SNMP variable value to 60. The SNMP variables take the following values:

- telAdminStatusConfirmConfig = 0 (confirmed)

- telAdminStatusConfirmEnabled = 1 (enable)

- telAdminStatusTimeoutConfirm = 60
• Make the changes in the device configuration you consider opportune and save them (setting the telAdminStatus-
SaveConfig SNMP variable value to 1). The SNMP variables take the following values:

- telAdminStatusConfirmConfig = 1 (test_cnfg_inactive)

- telAdminStatusConfirmEnabled = 1 (enable)

- telAdminStatusTimeoutConfirm = 60
• Restart the device. The SNMP variables take the following values:

- telAdminStatusConfirmConfig = 2 (test_cnfg_active)

- telAdminStatusConfirmEnabled = 1 (enable)

Configuration and Monitoring 33

2 Teldat Router Configuration Teldat SA

- telAdminStatusTimeoutConfirm = 60
• Confirm the tests configuration (that is active) before the 60 second timer times out (setting the telAdmin-
StatusConfirmConfig SNMP variable value to 1). The SNMP variables take the following values:

- telAdminStatusConfirmConfig = 0 (confirmed)

- telAdminStatusConfirmEnabled = 1 (enable)

- telAdminStatusTimeoutConfirm = 60
• Continuing with the example, we could execute some new changes in the device configuration and save them
(setting the telAdminStatusSaveConfig SNMP variable to 1). The SNMP variables take the following values:

- telAdminStatusConfirmConfig = 1 (test_cnfg_inactive)

- telAdminStatusConfirmEnabled = 1 (enable)

- telAdminStatusTimeoutConfirm = 60
• Restart the device. We can see the test configuration is active. The SNMP variables take the following values:

- telAdminStatusConfirmConfig = 2 (test_cnfg_active)

- telAdminStatusConfirmEnabled = 1 (enable)

- telAdminStatusTimeoutConfirm = 60
• Now we need to leave the timer to timeout (1 minute) without confirming the test configuration. Or we could restore
the previous configuration by setting the telAdminStatusConfirmEnabled SNMP variable value to 0. In both cases,
the device restarts with the old configuration as the active configuration and the SNMP variables displays the fol-
lowing values:

- telAdminStatusConfirmConfig = 3 (configuration_recovered)

- telAdminStatusConfirmEnabled = 1 (enable)

- telAdminStatusTimeoutConfirm = 60

2.4.8 COPY
This command allows you to copy any configuration (Running Config (P5) or a config file) to Config (P4). Confirma-
tion is requested when the Config (P4) configuration has been modified.

Syntax:

Config>copy ?
config-file Copy a config. file to Config.
running-config Copies Running Config

2.4.8.1 COPY CONFIG-FILE

Command history:

Release Modification
11.00.04 This command option was introduced as of version 11.00.04.

Allows a configuration file, presaved in the flash unit, to be applied to Config (P4) .

Syntax:

Config>copy config-file <file-name> config

Example:

Config>copy config-file prueba.cfg config

Configuration copied OK
Config>

2.4.8.2 COPY RUNNING-CONFIG

It allows Running-Config (P5) to be applied to Config (P4).

Syntax:

34 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

Config>copy running-config config

Example:

Config>copy running-config config

Warning: Static-config has been changed.
Copy Running-Config to Config(Yes/No)? y
Copying configuration... OK
Config>

2.4.9 DESCRIPTION
Allows you to enter descriptive texts for the device configuration. Said description is displayed on screen on execut-
ing the list configuration configuration command.

Syntax:

Config>description <text>

• < text > the configuration description text. If this text contains spaces, it must be written between quotation marks
(e.g. description “description containing spaces”).

Example:

Config>description Madrid_Branch_Outcoming_Router

2.4.10 DISABLE
Disables a specific personalized parameter. This command is used to deactivate behavior activated through the en-
able patch <parameter> command. To use this, you need to know the name of the activated parameters. Use the
list patch command in the configuration console.

Syntax:

Config>disable patch <id>

• < id > name of the parameter to deactivate. If you introduce default as the parameter name, ALL the active para-
meters are deactivated.

Example:

Config>disable patch arpi_snd_lcl

Config>

2.4.11 DUMP-COMMAND-ERRORS
Displays a list of the first five erroneous commands entered in the configuration console from the point where the
log-command-errors command was executed. This command is particularly useful for detecting errors generated
when loading a complete configuration file in a device.

Syntax:

Config>dump-command-errors

Example:

Config>dump-command-errors
Warning: possible errors in the configuration, at least these found:
line 2 -> ast
line 4 -> dev eth1
line 5 -> dev ser134
line 6 -> conf 0
line 7 -> list interf eth1
(lines counting since last log-command-erros command)
Too many errors, some cannot be printed (printed 5 of 8)
Config>

Configuration and Monitoring 35

2 Teldat Router Configuration Teldat SA

2.4.12 ENABLE
This enables a specific personalized parameter. This command allows you, under certain circumstances, to modify
router behavior. It deals with the management of personalized versions. You need the names of the available para-
meters 1 and their possible admitted values to use it. Entering the name and desired value for the parameter activates
it.

Syntax:

Config>enable patch <id> [value]

• < id > name of the parameter to activate.

• [value] value of said parameter.

Example:

Config>enable patch arpi_snd_lcl 1

Config>

To check the active parameters in your device at any point, use the list patch command. To disable an active per-
sonalized parameter, use the disable patch command followed by the parameter name.

2.4.13 EVENT
This allows you to record those events you wish to be stored by the Event Logging System in the configuration. Enter
exit to return to the Config> prompt.

Syntax:

Config>event

Example:

Config>event
-- ELS Config --
ELS Config>

To see the commands that can be executed from this prompt, please see Event Logging System ELS on page 135.

2.4.14 FEATURE
This defines the additional features of the router, which are not associated to a pre-determined interface.

Syntax:

Config>feature <option> [parameters]

aaa AAA configuration environment
access-lists Access generic access lists configuration
environment
act Alsa custom trap configuration enviroment
afs Advanced stateful firewall and routing
autoset-cfg Autoset-Config configuration environment
bandwidth-reservation Bandwidth-Reservation configuration environment
class-map Class Map configuration environment
control-access Control-access configuration environment
dns DNS configuration environment
dns-updater DNS Updater configuration environment
echo-responder Echo protocol configuration environment
err-disable Error disable configuration
frame-relay-switch Frame Relay Switch configuration environment
gps-applications GPS applications configuration environment
hotspot Hotspot configuration environment
http Access the router http protocol configuration
ip-discovery TIDP configuration environment
istud IPSEC Tunnel Server Discovery configuration environment
key-chain Key chain management
ldap LDAP configuration environment
mac-filtering Mac-filtering configuration environment
[1] The personalized parameters relative to each Teldat device functionality can be found correctly documented in the manuals associated to said
functionalities.

36 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

management Management configuration environment

netflow Netflow client configuration
nsla Network Service Level Advisor configuration
nsm Network Service Monitor configuration environment
ntp NTP configuration environment
policy-map Policy Map configuration environment
power-switch TeleControl Module control environment
prefix-lists Access generic prefix lists configuration
environment
radius RADIUS protocol configuration environment
rmon Remote Network Monitoring configuration environment
route-map Route-map configuration environment
scada-forwarder SCADA Forwarder configuration environment
sniffer Sniffer configuration environment
spi SPI, mobile IP Presence Service,configuration
environment
ssh Secure Shell configuration environment
stun Stun facility configuration environment
syslog Syslog configuration environment
tftp TFTP configuration enviroment
tms TMS configuration environment
vlan IEEE 802.1Q switch configuration environment
vli Virtual Linux Interface configuration
vrf VRF configuration environment
wnms Wireless Network Management System
wrr-backup-wan WRR configuration environment
wrs-backup-wan WRS configuration environment

• < option > name of the feature to configure.

• [parameters] parameters required for the specified option.

2.4.14.1 FEATURE AAA

Accesses the AAA feature configuration menu.

Syntax:

Config>feature aaa

Example:

Config>feature aaa
-- AAA user configuration --
AAA config>

For further information, please see manual Teldat-Dm800-I AAA Feature .

2.4.14.2 FEATURE ACCESS-LISTS

Accesses the configuration environment for the generic access lists.

Syntax:

Config>feature access-lists

Example:

Config>feature access-lists
-- Access Lists user configuration --
Access Lists config>

For further information, please see manual Teldat Dm752-I Access Control .

2.4.14.3 FEATURE ACT

Accesses the ACT feature configuration menu.

Syntax:

Config>feature act

Configuration and Monitoring 37

2 Teldat Router Configuration Teldat SA

Example:

Config>feature act
-- Alsa Custom Trap configuration --
ACT config>

For further information, please see manual Teldat Dm818-I ACT Feature .

2.4.14.4 FEATURE AFS

Accesses the afs configuration environment.

Syntax:

Config>feature afs

Example:

Config>feature afs
AFS config>

For further information, please see manual Teldat Dm786-I AFS .

2.4.14.5 FEATURE AUTOSET-CFG

Accesses the autoset-cfg configuration environment for routers that support this.

Syntax:

Config>feature autoset-cfg

Example:

Config>feature autoset-cfg
-- Autosetcfg Configuration --Autoset-cfg Config>?

For further information, please see manual Teldat Dm797-I Dynamic Configuration Control .

2.4.14.6 FEATURE BANDWIDTH-RESERVATION

Accesses the Bandwidth-Reservation configuration environment (BRS).

Syntax:

Config>feature bandwidth-reservation

Example:

Config>feature bandwidth-reservation
-- Bandwidth Reservation user configuration --
BRS Config>

For further information, please see manual Teldat Dm715-I Bandwidth Reservation System.

2.4.14.7 FEATURE CLASS-MAP

Accesses the class-map configuration environment.

Syntax:

Config>feature class-map

Example:

Config>feature class-map
-- Class-Map Menu Configuration --
Class-map Config>

For further information, please see manual Teldat Dm795-I Policy map Class map .

38 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

2.4.14.8 FEATURE CONTROL-ACCESS

Accesses the control-access configuration environment for the Corporate Encryption System. This environment is
only accessible in devices with encryption cards.

Syntax:

Config>feature control-access

Example:

Config>feature control-access
CtrlAcc Config>

2.4.14.9 FEATURE DNS

Accesses the DNS configuration environment. For further information please see manual Teldat Dm723-I DNS
Client.

Syntax:

Config>feature dns

Example:

Config>feature dns
-- DNS resolver user configuration --
DNS config>

2.4.14.10 FEATURE DNS-UPDATER

Accesses the dns-updater configuration environment.

Syntax:

Config>feature dns-updater

Example:

Config>feature dns-updater
-- DNS UPDATER configuration --
DNS UPDATER config>

For further information, please see manual Teldat Dm785-I DNS Updater .

2.4.14.11 FEATURE ECHO-RESPONDER

Accesses the echo-responder configuration environment.

Syntax:

Config>feature echo-responder

Example:

Config>feature echo-responder
-- ECHO user configuration --
ECHO config>

For further information, please see manual Teldat-Dm702-I TCP IP .

2.4.14.12 FEATURE ERR-DISABLE

Accesses the err-disable configuration environment.

Syntax:

Config>feature err-disable

Example:

Config>feature err-disable
-- Error Disable user configuration --

Configuration and Monitoring 39

2 Teldat Router Configuration Teldat SA

errdisable config>

2.4.14.13 FEATURE FRAME-RELAY-SWITCH

Accesses the Frame Relay switch configuration environment. For further information, please see manual Teldat
Dm703-I Frame Relay.

Syntax:

Config>feature frame-relay-switch

Example:

Config>feature frame-relay-switch
-- Frame Relay Switch configuration --
Frame Relay Switch>

2.4.14.14 FEATURE GPS-APPLICATIONS

Accesses the gps-applications configuration environment for devices supporting this.

Syntax:

Config>feature gps-applications

Example:

Config>feature gps-applications
-- GPS Applications Configuration --
GPS-Apps Cfg>

For further information, please see manual Teldat Dm812-I GPS .

2.4.14.15 FEATURE HOTSPOT

Accesses the HotSport feature configuration menu. Please see Dm820-I HotSpot Feature manual for further inform-
ation.

Syntax:

Config>feature hotspot

Example:

Config>feature hotspot

-- Hotspot configuration --
HS config>

Command history:

Release Modification
11.00.03 New command added.

2.4.14.16 FEATURE HTTP

Accesses the router http protocol configuration. This command or functionality depends on the device i.e. it might not
apply to your device.

Syntax:

Config>feature http

Example:

Config>feature http
-- HTTP user configuration --
HTTP config>

2.4.14.17 FEATURE IP-DISCOVERY

Accesses the TIDP (Teldat IP Discovery Protocol)configuration environment.

40 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

Syntax:

Config>feature ip-discovery

Example:

Config>feature ip-discovery
-- Teldat IP Discovery Protocol configuration --
TIDP config>

2.4.14.18 FEATURE IPV6-ACCESS-LIST

Accesses the ipv6-access-list configuration environment.

Syntax:

Config>feature ipv6-access-list

Example:

Config>feature ipv6-access-list
-- IPv6 Access Lists user configuration --
IPV6 Access Lists config>

For further information, please see manual Teldat Dm808-I IPv6 Access Control .

2.4.14.19 FEATURE ISTUD

Accesses the istud configuration environment for those devices that support this.

Syntax:

Config>feature istud

Example:

Config>feature istud
-- ISTUD configuration --
ISTUD config>

For further information, please see manual Teldat Dm784-I ISTUD Feature .

2.4.14.20 FEATURE KEY-CHAIN

Accesses the key-chain configuration environment.

Syntax:

Config>feature key-chain

Example:

Config>feature key-chain
-- Key Chain user configuration --
Key-chain Config>

For further information, please see manual Teldat Dm792-I Key Management .

2.4.14.21 FEATURE LDAP

Accesses the LDAP (Lightweight Directory Access Protocol ) configuration environment.

Syntax:

Config>feature ldap

Example:

Config>feature ldap
-- LDAP User Configuration --
LDAP config>

Configuration and Monitoring 41

2 Teldat Router Configuration Teldat SA

2.4.14.22 FEATURE MAC-FILTERING

Accesses the packet filtering based on MAC addresses configuration environment.

Syntax:

Config>feature mac-filtering

Example:

Config>feature mac-filtering
-- MAC Filtering user configuration --
Filter config>

2.4.14.23 FEATURE MANAGEMENT

This command accesses the feature management configuration menu. This allows you to program tasks so they ex-
ecute when they receive a notification from an NSLA advisor (Network Service Level Advisor). For further informa-
tion, please see manual Teldat-Dm754-I NSLA.

Syntax:

Config>feature management

Example:

Config>feature management
-- Management user configuration --
MGT config>

The commands available in the feature management menu are as follows:

MGT config>?
no Negate a command or set its defaults
operation Configure an operation to be executed
script Configure a script to be executed
exit Exit to parent menu

An operation is defined as a task that must be executed on receiving a notification from an advisor. The configuration
for said operation consists of two phases. First, the task to execute is specified together with its possible parameters.
Next, the advisor (whose notification triggered the operation) is configured.

A script is a list of commands that can be executed in an operation when receiving a notification from an advisor.

Command history:

Release Modification
11.00.05 Script execution and command script were introduced as of version 11.00.05.
11.01.00 Script execution and command script were introduced as of version 11.01.00.

2.4.14.23.1 operation <id> system reset

This command programs a device reset, which executes as soon as a notification from the advisor is received and is
configured through the operation <id> track nsla-advisor <advisor id> command.

Example:

MGT config>operation 2 system reset

An operation can be deleted through the no operation <id> command.

2.4.14.23.2 operation <id> system script <id_script>

This command programs an execution of the list of commands configured on the script identified by <id_script> con-
figured on an operation, which executes as soon as a notification from the advisor is received and is configured
through the operation <id> track nsla-advisor <advisor id> command.

Example:

MGT config>operation 1 system script 3

An operation can be deleted through the no operation <id> command.

42 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

Command history:

Release Modification
11.00.05 Script execution and command script were introduced as of version 11.00.05.
11.01.00 Script execution and command script were introduced as of version 11.01.00.

2.4.14.23.3 operation <id> feature-power-switch reset <MTC+ id>

This command programs a reset for the MTC+ with the corresponding id This executes as soon as a notification from
the advisor is received (configured through the operation <id> track nsla-advisor <advisor id> command).

Example:

MGT config>operation 1 feature-power-switch reset f

Operations can be deleted through the no operation <id> command.

Command history:

Release Modification
11.00.03 New command added.

2.4.14.23.4 operation <id> track nsla-advisor <advisor id>

Use this command to subscribe an operation to receive notifications from an NSLA advisor.

Example:

MGT config>operation 2 track nsla-advisor 1

Cancel said subscription through the no operation <id> track command.

2.4.14.23.5 operation <id> name <text>

Use this command to add a descriptor to an operation when monitoring.

Example:

MGT config>operation 1 name lte-up

Cancel said subscription through the no operation <id> name command.

Command history:
Release Modification
11.00.05 name command was introduced as of version 11.00.05.
11.01.00 name command was introduced as of version 11.01.00.

2.4.14.23.6 script <id_script> commands <text>

Use this command to add commands on a determined script to be executed in an operation when a notification from
the advisor is received.

The commands should start from the next menu to GESTCON menu, as the first thing carried out then executing a
command is allocating the monitor on that menu.

Example:

MGT config>script 1 commands "p 4"

Cancel said subscription through the no script <id_script> command.

Command history:
Release Modification
11.00.05 Command script <id_script> commands was introduced as of version 11.00.05.
11.01.00 Command script <id_script> commands was introduced as of version 11.01.00.

2.4.14.24 FEATURE NETFLOW

Accesses the netflow configuration environment.

Configuration and Monitoring 43

2 Teldat Router Configuration Teldat SA

Syntax:

Config>feature netflow

Example:

Config>feature netflow
NETFLOW config

For further information, please see manual Teldat Dm789-I NETFLOW .

2.4.14.25 FEATURE NSLA

Accesses the NSLA ( Network Service Level Advisor ) configuration environment. This offers management functions
at the Service Level (offered by the network) and also generates reports relative to the SLA ( Service Level Agree-
ments ).

Syntax:

Config>feature nsla

Example:

Config>feature nsla
-- Feature Network Service Level Advisor --
NSLA config>

For further information, please see manual Teldat Dm754-I NSLA (Network Service Level Advisor) .

2.4.14.26 FEATURE NSM

Accesses the NSM system (Network Service Monitor) configuration environment. This provides information on the
network service level by using different polls incorporated in the router. It also measures performance.

Syntax:

Config>feature nsm

Example:

Config>feature nsm
-- Network Service Monitor configuration --
NSM config>

For further information, please see manual Teldat Dm749-I NSM (Network Service Monitor).

2.4.14.27 FEATURE NTP

Accesses the NTP ( Network Time Protocol ) configuration environment.

Syntax:

Config>feature ntp

Example:

Config>feature ntp
-- NTP Protocol user configuration --
NTP config>

For further information, please see manual Teldat Dm728-I NTP Protocol .

2.4.14.28 FEATURE POLICY-MAP

Accesses the policy-map configuration environment.

Syntax:

Config>feature policy-map

Example:

Config>feature policy-map
-- Policy-Map Menu Configuration --

44 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

Policy-map Config>

For further information, please see manual Teldat Dm795-I Policy map Class map .

2.4.14.29 FEATURE POWER-SWITCH

Allows you to configure a test to determine if an MTC+ is connected to a power supply.

Syntax:

Config$feature power-switch

Example:

Config$feature power-switch

-- POWER-SWITCH user configuration --

POWER-SWITCH$

For further information, please see manual Teldat Dm689-I MTC+ .

Command history:

Release Modification
11.00.04 New feature added.

2.4.14.30 FEATURE PREFIX-LISTS

Accesses the prefix lists configuration environment.

Syntax:

Config>feature prefix-lists

Example:

Config>feature prefix-lists
-- Prefix Lists user configuration --
Prefix Lists config>

For further information, please see manual Teldat Dm780-I Prefix Lists .

2.4.14.31 FEATURE RADIUS

Accesses the RADIUS protocol configuration environment.

Syntax:

Config>feature radius

Example:

Config>feature radius
-- RADIUS User Configuration --
RADIUS Config>

For further information, please see manual Teldat Dm733-I RADIUS Protocol .

2.4.14.32 FEATURE RMON

Accesses the rmon configuration environment.

Syntax:

Config>feature rmon

Example:

Config>feature rmon
-- Remote Network Monitoring configuration --
RMON config>

Configuration and Monitoring 45

2 Teldat Router Configuration Teldat SA

For further information, please see manual Teldat Dm796-I RMON Feature .

2.4.14.33 FEATURE ROUTE-MAP

Accesses the route map configuration environment.

Syntax:

Config>feature route-map

Example:

Config>feature route-map
-- Route maps user configuration --
Route map config>

For further information, please see manual Teldat Dm745-I Policy Routing .

2.4.14.34 FEATURE SCADA-FORWARDER

Accesses the SCADA forwarder configuration environment.

Syntax:

Config>feature scada-forwarder

Example:

Config>feature scada-forwarder
-- SCADA Forwarder Configuration --
SCADA-FWD Cfg>

2.4.14.35 FEATURE SNIFFER

Accesses the packet capture (sniffer) configuration environment, integrated in the device.

Syntax:

Config>feature sniffer

Example:

Config>feature sniffer
-- SNIFFER configuration --
SNIFFER config>

2.4.14.36 FEATURE SPI

Accesses the spi configuration environment.

Syntax:

Config>feature spi

Example:

Config>feature spi
-- SPI global configuration --
SPI Config>

For further information, please see manual Teldat Dm793-I SPI Agent .

2.4.14.37 FEATURE SSH

Accesses the ssh configuration environment.

Syntax:

Config>feature ssh

Example:

Config>feature ssh
-- SSH protocol configuration --

46 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

SSH Config>

For further information, please see manual Teldat Dm787-I SSH Protocol .

2.4.14.38 FEATURE STUN

Accesses the STUN client configuration environment.

Syntax:

Config>feature stun client

Example:

Config>feature stun client

STUN Client Config>

For further information, please see manual Teldat Dm769-I STUN Protocol.

2.4.14.39 FEATURE SYSLOG

Accesses the syslog client configuration environment.

Syntax:

Config>feature syslog

Example:

Config>feature syslog
-- SYSLOG client configuration --
SYSLOG config>

For further information, please see manual Teldat Dm753-I Syslog Client .

2.4.14.40 FEATURE TFTP

Accesses the tftp configuration environment.

Syntax:

Config>feature tftp

Example:

Config>feature tftp
-- TFTP user configuration --
TFTP config>

For further information, please see manual Teldat Dm765-I TFTP Protocol .

2.4.14.41 FEATURE TMS

Accesses the TMS (Teldat Management System) configuration environment.

Syntax:

Config>feature tms

Example:

Config>feature tms
TMS config>

Command history:

Release Modification
11.00.02 This command is obsolete as of version 11.00.02. TMS feature is no longer supported.

2.4.14.42 FEATURE VLAN

Accesses the IEEE 802.1Q switch configuration environment to support creation of virtual private networks (Virtual
LAN).

Configuration and Monitoring 47

2 Teldat Router Configuration Teldat SA

Syntax:

Config>feature vlan

Example:

Config>feature vlan
-- VLAN configuration --
VLAN config>

For further information, please see manual Teldat Dm751-I VLAN .

2.4.14.43 FEATURE VLI

Accesses the vli configuration environment for devices supporting this.

Syntax:

Config>feature vli

Example:

Config>feature vli
-- VLI configuration --
VLI config>

For further information, please see manual Teldat Dm803-I Virtual Linux Interface VLI .

2.4.14.44 FEATURE VRF

Accesses the VRF tables (VPN Routing/Forwarding) configuration environment.

Syntax:

Config>feature vrf

Example:

Config>feature vrf
-- VRF user configuration --
VRF config>

For further information, please see manual Teldat Dm775-I VRF-Lite Facility.

2.4.14.45 FEATURE WNMS

Accesses the WNMS (Wireless Network Management System) configuration.

Syntax:

Config>feature wnms

Example:

Config>feature wnms

-- Wireless Network Management System configuration --

WNMS config>

For further information, please see manual Teldat Dm819-I Wireless Network Management System .

Command history:

Release Modification
11.00.03 New command added.

2.4.14.46 FEATURE WRR-BACKUP-WAN

Accesses the WRR (WAN ReRoute) configuration environment.

Syntax:

Config>feature wrr-backup-wan

48 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

Example:

Config>feature wrr-backup-wan
-- WAN Reroute Backup user configuration --
Backup WRR>

For further information, please see manual Teldat Dm727-I Backup WAN Reroute .

2.4.14.47 FEATURE WRS-BACKUP-WAN

Accesses the WRS (WAN ReStoral) configuration environment.

Syntax:

Config>feature wrs-backup-wan

Example:

Config>feature wrs-backup-wan
-- WAN Back-up user configuration --
Back-up WAN>

For further information, please see manual Teldat Dm711-I Frame Relay ISDN Backup Configuration.

2.4.15 FILE
Accesses the files present in the device storage units.

The storage units are explicitly represented through a letter and the colon symbol (:). The unit supported over the
flash memory is labeled A: and the unit supported by the smart card is labeled S:. Not all devices support both stor-
age units. For further details, please see the installation manual for your device.

One of the (present) units is considered the active, or predetermined, unit. To change the active unit, please see the
config-media command found in this manual. If you wish to refer to the active unit, do not include the name of any
unit.

The S: unit is a compressed unit. When information is stored, it's compressed with the gzip program algorithm. To
show this when you store something in said unit, change the last character. For further details on how to operate with
this unit, please see the installation manual for your device.

Syntax:

Config>file <operation> [parameters]

copy Copy files in the storage units
create Create a new file in the storage units
delete Delete files present in the device storage units
format Format a storage unit in the device
list Lists the files present in the storage units
rename Rename the files present in the device storage units
type Show files by console

• < operation > operation to execute over the storage unit or file.
• [parameters] parameters required for the specified operation.

2.4.15.1 FILE COPY

Allows you to copy files in the storage units. The source and destination files can be in the same unit or in different
units. If these are in different units (and not in the active unit), you must indicate the storage units. If both files pertain
to the active unit, don't indicate the storage unit.

Syntax:

Config>file copy <origin file> <destination file>

• < origin file > name of the file you wish to copy.
• < destination file > name of the destination file where you wish to copy the original specified file to.

Example 1:

Config>file copy xot1.cfg xot2.cfg

Config>

Configuration and Monitoring 49

2 Teldat Router Configuration Teldat SA

Example 2:

Config>file copy mike.cfg s:mike11.cfg

Config>

The results of both examples can be seen in the figure in the next section. Please note that the MIKE11.CFG file ap-
pears as MIKE11.CFZ, as it is a compressed file.

2.4.15.2 FILE CREATE

Command history:

Release Modification
11.00.04 This command option was introduced as of version 11.00.04.

Allows you to create files in the storage unit. You can create files from ASCII or HEX content. To finish file creation,
press CTRL+P.

Syntax:

Config>file create <destination file> <input mode>

• < destination file > name of the file you wish to create.
• < input mode > type of input content used to create the specified file.

Example 1:

Config>file create example.txt ascii

Input File Content: (End CTRL+P)
Hi! This is a txt example file.
Save file(Yes/No)? Yes
File Successfully Saved

Config>

Example 2:

Config>file create examplehex.txt hex

Input File Content: (End CTRL+P)
0123456789abcdff000000010000000200000000000004100000000000000000
0076e88f8b76cc1b62371bc1aa227130c63ca9614f7290bc56a52b8810eb4cc2
dcbc320e3f42b26f796ead2127e2d658495563afe35ac4aa149b0fef2207390d
467a95634d7592976b2f5bd92145cf1844912683bca7683fefaf6e0a8fa016dc
Save file(Yes/No)? Yes
File Successfully Saved

Config>

The results of both examples can be seen through options list and type. (Checks if the files are properly created.)

2.4.15.3 FILE DELETE

Allows you to delete files present in the device storage units. For security reasons, you cannot delete a file containing
the device code.

Syntax:

Config>file delete <filename>

• < filename > name of the file to delete.

Example 1:

Config>file list
Active Device: Flash
A: ROUTER.CFG 3510 12/09/02 12:45 Flash
A: TKR.CFG 1050 09/19/02 18:08 Flash
A: TEST.CFG 4708 04/26/02 15:33 Flash
A: SINTEST.CFG 4593 09/25/02 15:28 Flash
A: MIKE.CFG 1494 12/26/02 16:47 Flash
A: MIKE2.CFG 6302 12/13/02 10:09 Flash

50 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

A: XOT1.CFG 1494 12/26/02 14:33 Flash

A: XOT2.CFG 1494 12/27/02 12:27 Flash
A: XOT3.CFG 1554 12/26/02 13:18 Flash
A: APPCODE1.BIN 2760544 01/03/03 10:39 Flash

Flash Available Space : 2496 Kbytes

S: ROUTER.CFZ 802 SmartCard

SmartCard Available Space : 14400 bytes

Config>file delete s:router.cfz
Config>file list
Active Device: Flash
A: ROUTER.CFG 3510 12/09/02 12:45 Flash
A: TKR.CFG 1050 09/19/02 18:08 Flash
A: TEST.CFG 4708 04/26/02 15:33 Flash
A: SINTEST.CFG 4593 09/25/02 15:28 Flash
A: MIKE.CFG 1494 12/26/02 16:47 Flash
A: MIKE2.CFG 6302 12/13/02 10:09 Flash
A: XOT1.CFG 1494 12/26/02 14:33 Flash
A: XOT2.CFG 1494 12/27/02 12:27 Flash
A: XOT3.CFG 1554 12/26/02 13:18 Flash
A: APPCODE1.BIN 2760544 01/03/03 10:39 Flash

Flash Available Space : 2496 Kbytes

SmartCard Available Space : 15300 bytes
Config>

Example 2:

Config>file delete appcode1.bin

CLI Error: Application code files can not be deleted
CLI Error: Command error
Config>

2.4.15.4 FILE FORMAT

Allows you format a storage unit in the device. Currently, you can only format the smart card. Please note that when
you format a unit, all the files contained in said unit are deleted.

Syntax:

Config>file format <store unit>

• < store unit > name of the storage unit to format. Currently only the smart card can be formatted.

Example:

Config>file format smartcard

Formatting, please wait ... OK
Config>

2.4.15.5 FILE LIST

Lists the files present in the device storage units. This also shows which unit is active. To change the active unit,
please see the config-media command found in this manual.

Each line displays the unit identifier, the file name, the extension, the size in bytes, the date and time it was created
and finally the storage unit as a text. The free available space in each unit is also displayed.

Syntax:

Config>file list

Example:

Config>file list
Active Device: Flash
A: ROUTER.CFG 3510 12/09/02 12:45 Flash
A: TKR.CFG 1050 09/19/02 18:08 Flash
A: TEST.CFG 4708 04/26/02 15:33 Flash

Configuration and Monitoring 51

2 Teldat Router Configuration Teldat SA

A: SINTEST.CFG 4593 09/25/02 15:28 Flash

A: MIKE.CFG 1494 12/26/02 16:47 Flash
A: MIKE2.CFG 6302 12/13/02 10:09 Flash
A: XOT1.CFG 1494 12/26/02 14:33 Flash
A: XOT2.CFG 1494 12/27/02 12:27 Flash
A: XOT3.CFG 1554 12/26/02 13:18 Flash
A: APPCODE1.BIN 2760544 01/03/03 10:39 Flash

Flash Available Space : 2496 Kbytes

S: MIKE11.CFZ 802 SmartCard

SmartCard Available Space : 14400 bytes

Config>

Please note that the smart card unit is a slow storing unit and may take various seconds to respond.

2.4.15.6 FILE RENAME

Allows you to rename the files present in the device storage units. You must first indicate the original name and sub-
sequently enter the new name you wish to give the file. The unit indicated in the original name and in the new name
must coincide. For security reasons, you are not allowed to rename a file containing the device code.

Syntax:

Config>file rename <filename> <new name>

• < filename > name of the file you wish to rename.

• < new name > the new name to give to the specified file.

Example 1:

Config>file list
Active Device: Flash
A: ROUTER.CFG 3510 12/09/02 12:45 Flash
A: TKR.CFG 1050 09/19/02 18:08 Flash
A: TEST.CFG 4708 04/26/02 15:33 Flash
A: SINTEST.CFG 4593 09/25/02 15:28 Flash
A: MIKE.CFG 1494 12/26/02 16:47 Flash
A: MIKE2.CFG 6302 12/13/02 10:09 Flash
A: XOT1.CFG 1494 12/26/02 14:33 Flash
A: XOT2.CFG 1494 12/27/02 12:27 Flash
A: XOT3.CFG 1554 12/26/02 13:18 Flash
A: APPCODE1.BIN 2760544 01/03/03 10:39 Flash

Flash Available Space : 2496 Kbytes

S: ROUTER.CFZ 802 SmartCard

SmartCard Available Space : 14400 bytes

Config>file rename s:router.cfz s:backup.cfz
Config>file list
Active Device: Flash
A: ROUTER.CFG 3510 12/09/02 12:45 Flash
A: TKR.CFG 1050 09/19/02 18:08 Flash
A: TEST.CFG 4708 04/26/02 15:33 Flash
A: SINTEST.CFG 4593 09/25/02 15:28 Flash
A: MIKE.CFG 1494 12/26/02 16:47 Flash
A: MIKE2.CFG 6302 12/13/02 10:09 Flash
A: XOT1.CFG 1494 12/26/02 14:33 Flash
A: XOT2.CFG 1494 12/27/02 12:27 Flash
A: XOT3.CFG 1554 12/26/02 13:18 Flash
A: APPCODE1.BIN 2760544 01/03/03 10:39 Flash

Flash Available Space : 2496 Kbytes

S: BACKUP.CFZ 802 SmartCard

SmartCard Available Space : 14400 bytes

52 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

Config>

Example 2:

Config>file rename appcode1.bin appcode1_bak.bin

CLI Error: Application code files can not be renamed
CLI Error: Command error
Config>

Example 3:

Config>file rename s:router.cfz a:router.cfg

Disk Units do not match
Config>

2.4.15.7 FILE TYPE

Allows you to display the files present in the device storage units. Each character that cannot be printed is substi-
tuted with a period when viewed.

Syntax:

Config>file type [header] <filename> [hex | text]

• header this option means you only see the first lines of the file.
• < filename > name of the file you wish to view.
• hex dumps the file content, byte by byte, in hexadecimal format with the corresponding texts characters. Codes
that do not correspond to the standard text characters, appear as a period in the corresponding text.
• text displays the file content in text mode. Non-standard characters are substituted for a period on the display.

The complete file is displayed in text mode if you do not specify any option.

Example 1:

Config>file type header temp.cfg

; Showing System Configuration for access-level 0 ...
; C4i IPSec Router 1 16 Version 10.6.27TM
log-command-errors
no configuration
set data-link astm serial0/0
;
protocol ip
; -- Internet protocol user configuration --
internal-ip-address 172.24.78.116
;
address ethernet0/0 172.24.78.116 255.255.0.0
;
;
;
exit
;
;
protocol bgp
; -- Border Gateway Protocol user configur
Config>

Example 2:

Config>file type temp.cfg

; Showing System Configuration for access-level 0 ...
; C4i IPSec Router 1 16 Version 10.6.27TM
log-command-errors
no configuration
set data-link astm serial0/0
;
protocol ip
; -- Internet protocol user configuration --
internal-ip-address 172.24.78.116
;
address ethernet0/0 172.24.78.116 255.255.0.0

Configuration and Monitoring 53

2 Teldat Router Configuration Teldat SA

;
;
;
exit
;
;
protocol bgp
; -- Border Gateway Protocol user configuration --
enable
;
aggregate default 192.168.0.0 mask 255.255.0.0
aggregate default 10.0.0.0 mask 255.0.0.0
;
aggregate 10.0.0.0 mask 255.0.0.0 10.0.0.0 mask 255.0.0.0 refines
;
as 100
exit
;
dump-command-errors
end
; --- end ---

Config>

Example 3:

Config>file type header temp.cfg hex

3b 20 53 68 6f 77 69 6e 67 20 53 79 73 74 65 6d ; ; Showing System
20 43 6f 6e 66 69 67 75 72 61 74 69 6f 6e 20 66 ; Configuration f
6f 72 20 61 63 63 65 73 73 2d 6c 65 76 65 6c 20 ; or access.level
30 20 2e 2e 2e 0d 0a 3b 20 43 34 69 20 49 50 53 ; 0 .....; C4i IPS
65 63 20 52 6f 75 74 65 72 20 31 20 31 36 20 56 ; ec Router 1 16 V
65 72 73 69 6f 6e 20 31 30 2e 36 2e 32 37 54 4d ; ersion 10.6.27TM
0d 0a 0d 0a 6c 6f 67 2d 63 6f 6d 6d 61 6e 64 2d ; ....log.command.
65 72 72 6f 72 73 20 0d 0a 6e 6f 20 63 6f 6e 66 ; errors ..no conf
69 67 75 72 61 74 69 6f 6e 20 0d 0a 73 65 74 20 ; iguration ..set
64 61 74 61 2d 6c 69 6e 6b 20 61 73 74 6d 20 73 ; data.link astm s
65 72 69 61 6c 30 2f 30 0d 0a 3b 0d 0a 70 72 6f ; erial0.0..;..pro
74 6f 63 6f 6c 20 69 70 0d 0a 3b 20 2d 2d 20 49 ; tocol ip..; .. I
6e 74 65 72 6e 65 74 20 70 72 6f 74 6f 63 6f 6c ; nternet protocol
20 75 73 65 72 20 63 6f 6e 66 69 67 75 72 61 74 ; user configurat
69 6f 6e 20 2d 2d 0d 0a 20 20 20 69 6e 74 65 72 ; ion .... inter
6e 61 6c 2d 69 70 2d 61 64 64 72 65 73 73 20 31 ; nal.ip.address 1
37 32 2e 32 34 2e 37 38 2e 31 31 36 0d 0a 3b 0d ; 72.24.78.116..;.
0a 20 20 20 61 64 64 72 65 73 73 20 65 74 68 65 ; . address ethe
72 6e 65 74 30 2f 30 20 31 37 32 2e 32 34 2e 37 ; rnet0.0 172.24.7
38 2e 31 31 36 20 32 35 35 2e 32 35 35 2e 30 2e ; 8.116 255.255.0.
30 0d 0a 3b 0d 0a 3b 0d 0a 3b 0d 0a 65 78 69 74 ; 0..;..;..;..exit
0d 0a 3b 0d 0a 3b 0d 0a 70 72 6f 74 6f 63 6f 6c ; ..;..;..protocol
20 62 67 70 0d 0a 3b 20 2d 2d 20 42 6f 72 64 65 ; bgp..; .. Borde
72 20 47 61 74 65 77 61 79 20 50 72 6f 74 6f 63 ; r Gateway Protoc
6f 6c 20 75 73 65 72 20 63 6f 6e 66 69 67 75 72 ; ol user configur

Config>

2.4.16 FIRMWARE-CHECKING
Enables the integrity checking for firmware. This command is used together with the backup-files command to en-
sure device availability when faced with serious cases of corruption in the filing system.

Note

This command is only effective in devices with partitioned flash memory.

Syntax:

Config> firmware-checking

54 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

Example:

Config>firmware-checking
Config>

2.4.17 FORMAT
Formats the specified storage device.

Syntax:

Config>format <device>

• < device > name of the storage device to format. Currently you can only format the smart card system (smartcard
option).

Example:

Config>format smartcard

Formatting, please wait ... OK

Config>

2.4.18 GLOBAL-PROFILES
Defines the router PPP, ATM etc. profiles.

Syntax:

Config>global-profiles <profile name>

dial Access the DIAL profiles configuration environment

ppp Access the PPP profiles configuration environment
tcp-menu Access the TCP profiles configuration environment
trmtp-menu Access the TRMTP profiles configuration environment

• < profile name > profile type identifier whose configuration menu you wish to access.

Command history:

Release Modification
11.00.02 Options tcp-menu and trmtp-menu are obsolete as of version 11.00.02. DEP protocol is
no longer supported.

2.4.18.1 GLOBAL-PROFILES DIAL

Accesses the dial profiles configuration environment.

Syntax:

Config>global-profiles dial

Example:

Config>global-profiles dial
-- Dial Profiles Configuration --
Dial Profiles config>

For further details on this configuration environment, please see manual Teldat Dm732-I Call Profiles .

2.4.18.2 GLOBAL-PROFILES PPP

Accesses the PPP (Point-to-Point Protocol) profiles configuration environment.

Syntax:

Config>global-profiles ppp

Example:

Config>global-profiles ppp

Configuration and Monitoring 55

2 Teldat Router Configuration Teldat SA

-- PPP Profiles Configuration --

PPP Profiles config>

Please see manual Teldat Dm710-I PPP Interface .

2.4.18.3 GLOBAL-PROFILES TCP-MENU

Accesses the DEP protocol over TCP ( Transport Control Protocol ) profiles configuration environment to encapsulate
the traffic from POS or Dataphones in IP networks. For further information, please see manual Teldat Dm263-I For-
warder DEP.

Syntax:

Config>global-profiles tcp-menu

Example:

Config>global-profiles tcp-menu
-- UDAFO TCP Configuration Menu --
UDAFO TCP Cfg>

Command history:

Release Modification
11.00.02 This command is obsolete as of version 11.00.02. DEP protocol is no longer supported.

2.4.18.4 GLOBAL-PROFILES TRMTP-MENU

Accesses the DEP protocol over TRMTP (Trivial Message Transfer Protocol) profiles configuration environment to
encapsulate the traffic from POSs or Dataphones in IP networks. For further information, please see manual Teldat
Dm263-I Forwarder DEP .

Syntax:

Config>global-profiles trmtp-menu

Example:

Config>global-profiles trmtp-menu
-- UDAFO TRMTP Configuration Menu --
UDAFO TRMTP Cfg>

Command history:

Release Modification
11.00.02 This command is obsolete as of version 11.00.02. DEP protocol is no longer supported.

2.4.19 LICENCE-CHANGE
Allows you to change the device license so determined features are enabled or disabled. This command is only oper-
ative if you have a special license. After selecting the language where the texts appear for the interaction, the config-
uration for the current license is displayed. To introduce a new license (after specifying the type of installation), indic-
ate if you want to enable all the available functions. Once this process has finalized, confirm if you want these
changes to be saved. If you do, confirm restart (Yes). However, you can delay restart until later on although the
changes will not take affect until the device is restarted.

Syntax:

Config>licence-change

Example:

Config>licence-change

1. English
2. Español
Language/Idioma[1]? 1

Current licence: 1 249 C4i_AdHoc IPSec SNA

Last executed task was Register

56 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

FUNCTIONALITY ENABLED
-------------- ----------
ISDN NO
IPSEC YES
SNA YES
VOIP NO

Please indicate here if you are installing the router to carry out one of the fol
lowing tasks:
R. Register for the first time
M. Maintenance to resolve an event
Please select an option > m
Enable ISDN (Yes/No)[Y]?y
Enable IPSEC (Yes/No)[Y]?y
Enable SNA (Yes/No)[Y]?y
Enable VOIP (Yes/No)[Y]?y
Enable NOE (Yes/No)[Y]?n

Executed task was Maintenance

FUNCTIONALITY ENABLED
-------------- ----------
ISDN YES
IPSEC YES
SNA YES
VOIP YES
NOE NO
Do you want to save changes (Yes/No)[N]?y
Searching licence code for new configuration...
New licence established: 1 261 C4i_AdHoc ISDN IPSec SNA VoIP
You must restart/reload for the changes to take effect
Are you sure you want to reload the device (Yes/No)[N]?n
Config>

2.4.20 LIST
Lists information on the active unit configuration (flash or smart card), protocols, interfaces, users, pools and enabled
patches configuration.

Syntax:

Config>list <info>
configuration List generic configuration information
devices List router devices
patch Check the personalized parameters that are active
pool Number of bytes assigned to each memory pool
user Displays the list of registered users

• < info > identifier for the type of information you wish to list.

2.4.20.1 LIST CONFIGURATION

Lists the information on the active device configuration.

Syntax:

Config>list configuration

Example:

Router Config>list configuration

Hostname: Router
Contact person: ......
Host Location: .......
No console authentication
No Telnet authentication
No FTP access authentication
Configurable protocols:
Num Name Protocol

Configuration and Monitoring 57

2 Teldat Router Configuration Teldat SA

0 IP DOD-IP
3 ARP Address Resolution Protocol
4 H323 H323
6 DHCP Dynamic Host Configuration Protocol
10 BGP BGP
11 SNMP SNMP
12 OSPF Open SPF-Based Routing Protocol
13 RIP Route Information Protocol
17 SIP SIP
23 ASRT Adaptive Source Routing Transparent Enhanced Bridge
25 NHRP Next Hop Resolution Protocol
26 DLS Data Link Switching
29 L2TP L2TP
30 EAPOL Extensible Authentication Protocol Over LAN
31 Preauth WLAN Preauthentication

713 bytes of memory used for configuration

Router Config>

2.4.20.2 LIST DEVICES

Lists the information on the available/configured interfaces in the device.

Syntax:

Config>list devices

Example:

Config>list devices
Interface Connector Type of interface
ethernet0/0 GE0/FE0/LAN1 Fast Ethernet interface
ethernet0/1 GE1/FE1/LAN2 Fast Ethernet interface
bri0/0 BRI/ISDN1 ISDN Basic Rate Int
x25-node --- Router->Node
Config>

2.4.20.3 LIST PATCH

Use this command to check any active personalized parameters.

Syntax:

Config>list patch

Example:

Config>list patch
Patch Name value
-----------------------------------------
ARPI_SND_LCL 1 (0x1)
Config>

2.4.20.4 LIST POOL

Use this command to see the number of bytes assigned to each memory pool as well as the unassigned bytes.

Syntax:

Config>list pool

Example:

Config>list pool
3 Iorbs pool: 4194304
4 MSGs pool: 1204000
Total memory pools: 5398304 Total free memory: 0
Config>

58 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

2.4.20.5 LIST USER

Displays the list of registered users, their password, access level, access mode and whether they are enabled or not.

Syntax:

Config>list user

Example:

Config>list user
Name Password Access Level Strict Enabled
config **************** [10]Config N N
monitor **************** [ 5]Monitor N Y
root **************** [15]Root N Y
mabm **************** [15]Root N Y
guest **************** [ 2] Y Y
viewer **************** [ 1]Events N Y
Config>

2.4.21 LOG-COMMAND-ERROR
This command initializes (deletes) the generated errors register log when executing commands from the configura-
tion console.

Syntax:

Config>log-command-errors

Example:

Config>log-command-errors
Config>

This is usually executed as the first command before loading a new configuration file. Subsequently you can see
possible errors through the dump-command-errors command.

2.4.22 MANAGEMENT
Accesses the master router configuration environment.

Syntax:

Config>management

Example:

Config>management
-- Routers management user configuration --
Management config>

2.4.23 NETWORK
Accesses the commands menu to configure a specific interface. To exit this menu, enter exit.

Syntax:

Config>network <name>

• Where < name > is the interface name.

To find out what interfaces are available in the device, enter list devices.

Example 1:

Config>network ethernet0/0
-- Ethernet Interface User Configuration --
ethernet0/0 config>

Example 2:

Config>network serial0/4

Configuration and Monitoring 59

2 Teldat Router Configuration Teldat SA

CLI Error: Unrecognized command or invalid value

Config>

For further information on interfaces, please see the common configuration for interfaces manual ( Teldat Dm722-I
Common Configuration for Interfaces) and the manual associated to the specific network interface you wish to ac-
cess.

2.4.24 NO
Sets parameters to their default value, disables options or deletes previously added configuration elements.

Syntax:

Config>no <command> [parameters]

• < command > name of the command where you want to invalidate execution.
• [parameters] the parameters required for the specified command.

2.4.24.1 NO ADD DEVICE

Deletes the specified virtual interface. (See also the no device command for another way to delete an interface.)

Syntax:

Config>no add device <virtual interface type> [options]

• < virtual interface type> this is the virtual interface you want to delete.

• [options] The options depend on the type of virtual interface to delete. These are the same as those used to cre-
ate the interface through the add device command.

Example:

Config>no add device ppp 1

Config>

Release Modification
11.01.00 New command was introduced as of version 11.01.00.

2.4.24.2 NO AUTOINSTALL

Eliminates autoinstallation parameter configuration.

Syntax:

Config>no autoinstall

Example:

Config>no autoinstall
Config>

Release Modification
11.00.03 This command is obsolete as of version 11.00.03.

2.4.24.3 NO BANNER

Deletes a specified banner.

Syntax:

Config>no banner <type>

< type > specifies the type of banner to delete. The only one currently available is access (login).

Example:

Config>no banner login

Config>

60 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

2.4.24.4 NO CONFIGURATION

Eliminates the whole of the existing configuration.

Syntax:

Config>no configuration

Example:

Config>no configuration
Config>

2.4.24.5 NO CONFIRM-CFG

Rejects the current test configuration. After the warning message, the device restarts with the previous configuration.
For further information, please see confirm-cfg-needed and confirm-cfg commands.

Syntax:

Config>no confirm-cfg

Example:

Config>no confirm-cfg
!!!!LOOK OUT!!!!
This command reboots the system
If you go on, previous configuration will be restored
You can test this configuration again with: set file-cfg TEMP
To go on write RECOVER: RECOVER

This action can also be executed through SNMP. Please see CONFIRM-CFG-NEEDED on page 32.

2.4.24.6 NO CONFIRM-CFG-NEEDED

Disables the necessity to confirm the new configurations. Please see confirm-cfg-needed.

Syntax:

Config>no confirm-cfg-needed

Example:

Config>no confirm-cfg-needed
Config>

This action can also be executed through SNMP. Please see CONFIRM-CFG-NEEDED on page 32.

2.4.24.7 NO CONTACT-PERSON

Deletes the identification assigned to the contact person. For further information, please see the set-contact-person
command.

Syntax:

Config>no contact-person

Example:

Config>no contact-person
Config>

2.4.24.8 NO DESCRIPTION

Deletes the description(s) assigned to the device configuration. For further information, please see the description
command.

Syntax:

Config>no description

Example:

Configuration and Monitoring 61

2 Teldat Router Configuration Teldat SA

Config>no description
Config>

2.4.24.9 NO DEVICE

Eliminates the specified virtual interface. See also the no add device command for an alternative way to delete an
interface.

Syntax:

Config>no device <name>

• < name> name of the interface to delete.

Example:

Config>no device fr1

Config>

2.4.24.10 NO FIRMWARE-CHECKING

Disables checking when working with the firmware files.

Syntax:

Config>no firmware-checking

Example:

Config>no firmware-checking
Config>

2.4.24.11 NO HOST-LOCATION

Deletes the text indicating device location. For further information, please see the set-host-location command.

Syntax:

Config>no host-location

Example:

Config>no host-location
Config>

2.4.24.12 NO HOSTNAME

Deletes the name assigned to the device. For further information, please see the set hostname command.

Syntax:

Config>no hostname

Example:

Config>no hostname
Config>

2.4.24.13 NO LOGIN

Deactivates the login options configured through the set login command.

Syntax:

Config>no login <option>

• <option> this is the login option to deactivate. Currently only the case-sensitive option is supported. This deactiv-
ates upper-case/lower-case sensitivity.

Example:

Config> no login case-sensitive

Config>

62 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

2.4.24.14 NO PASSWORD

Eliminates the device access password configuration. For further information, please see the set password com-
mand.

Syntax:

Config>no password

Example:

Config>no password
Config>

2.4.24.15 NO PRIVILEGE

Eliminates the configuration introduced through the privilege command.

Syntax:

Config>no privilege <access-level> [<command-path>]

• <access-level> this is the access level the command is applied to.

• <command-path> this is an optional parameter. If specified, it only eliminates the command corresponding to said
command-path. If it is not specified, it eliminates all the privilege commands related to the indicated access level.

Example:

Config>no privilege 3
Config>

2.4.24.16 NO RUSH-ENGINE

Disables Rush engine or sets default idle flows timeout configuration, which is 5 seconds.

Syntax:

Config>no rush-engine [timeout]

• timeout this is an optional parameter. If specified, the idle flows timeout is set to default. If this is omitted, the com-
mand disables Rush engine.

Example:

Config>no rush-engine timeout

Config>

Command history:

Release Modification
11.01.00 This command was introduced as of version 11.01.00.

2.4.24.17 NO USER

Deletes a user from the user list. You can eliminate as many users as you wish except for a Root user, if there is only
one, and there are other registered users. You can only delete the rest of the users, as if you do, you won't be able to
manage the remaining users. If you eliminate all the users except for the last Root, then this may be deleted. Sub-
sequently, the system doesn't request user or password to access the device as there are no users registered in the
system.

Syntax:

Config>no user <user-name>

• < user-name > registered user name.

Example:

Config>no user mabm

Config>

Configuration and Monitoring 63

2 Teldat Router Configuration Teldat SA

2.4.25 NODE
Accesses the node configuration (X.25, XOT and 270). You can also access this through the network command fol-
lowed by the interface the node is configured over.

Syntax:

Config>node <name>
270 Access the 270 configuration
x25 Access the X25 node configuration
xot Access the XOT configuration

• < name > name of the node whose configuration menu you wish to access.

There are three types of configurable nodes:

2.4.25.1 NODE 270

Accesses the node configuration environment relative to 270.

Syntax:

Config>node 270

Example:

Config>node 270
270 Config>

2.4.25.2 NODE X25

Accesses the node configuration environment relative to X.25.

Syntax:

Config>node x25

Example:

Config>node x25

X25 Config>

For further information, please see manual Teldat Dm707-I X.25 Configuration .

2.4.25.3 NODE XOT

Accesses the node configuration environment relative to XOT (X.25 over TCP/IP).

Syntax:

Config>node xot

Example:

Config>node xot
XOT config>

For further information on the node, please see manual Teldat-Dm 713-I XOT Protocol.

2.4.26 PRIVILEGE
Allows you to specify personalized execution privileges for process commands.

Syntax:

Config>privilege <level> <command path> [all]

• < level > access level to assign to the command specified in < command path>.
• < command path> this is the command path.
• < all > option allowing you to apply the specified level to all the subcommands (where the paths coincide) for the
command specified in <command path>.

64 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

The <level> parameter, which specifies the access level to assign to the command. This takes values between 0 and
15.

The < command path> parameter. This specifies the specific path for the command where you are going to person-
alize the access level. This latter is constructed by consecutively writing the necessary commands, separated by the
> character, needed to execute this.

You must write between inverted commas ( “) and your syntax must adjust to the following norms:

1) As a general rule, to define the access level for a specified command, the path identifying this must begin with the
> character.

Example:

Config>privilege 12 “>monitor>network ppp1”

Config>

If you try and assign an access level to a command independently of the menu you are in, said initial character is
omitted and you can't use the command in the path.

Example:

Config$privilege 7 "list"
Config$privilege 7 "ppp>ipcp"
CLI Error: Wrong specification of command path (misuse of >)
CLI Error: Command error
Config$

The >config path refers to both the static and the dynamic configuration. It is not possible to give different permis-
sions to the same command, depending on whether the user is dynamically or statically configuring the device.

2) The > character is used to as a separator between the device process level/menus when specifying the command
path.

Example:

Config$privilege 12 ">config>network ppp1>ppp>ipcp"

Config$

3) The * character can be used as a wildcard parameter in the command path definition.

Example:

Config$privilege 5 ">config>network *>list"

Config$

This assigns an access level 5 to the list command in any net configuration menu (net ppp1, net ppp2, net fr1, etc.).

To find the complete path for a parameter configuration command in a device, execute show from the configuration.

Example:

Config>show config
; Showing System Configuration for access-level 15 ...

log-command-errors
no configuration
set inactivity-timer disabled
add device ppp 1
set data-link sync serial0/0
set data-link x25 serial0/1
;
network ethernet0/0
; -- Ethernet Interface User Configuration --
ip address 172.24.73.23 255.255.0.0
;
;
;
;
exit
;
;
;

Configuration and Monitoring 65

2 Teldat Router Configuration Teldat SA

network ethernet0/1
; -- Ethernet Interface User Configuration --
no ip address
;
exit
;
;
;
;
network x25-node
; -- X25-node interface configuration --
no ip address
;
exit
;
;
network ppp1
; -- Generic PPP User Configuration --
ip address 1.1.1.1 255.255.255.0
;
;
;
;
ppp
; -- PPP Configuration --
ipcp remote address fixed 1.1.1.2
exit
;
base-interface
; -- Base Interface Configuration --
base-interface serial0/0 link
;
exit
;
exit
;
;
;
dump-command-errors
end
; --- end ---
Config>

For example, to establish access level 12 to a base interface assignment for net ppp1 ( base-interface serial0/0
command), you need to use path ">config>network ppp1>base-interface>base-interface serial0/0 link “

The <all> option allows you to apply the specified level to all the subcommands for that specified in <command
path> i.e. to all commands whose path coincides from the start (taking into account all wildcards).

Example:

Config>privilege 12 “>config>network” all

Config>

This configuration is applied at the access level for all commands whose paths begins with " >network" such as
">config>network ppp1" or ">network ppp2>ppp"

If this option is not specified, the access level is strictly applied to the command defined by the path, i.e. whose exe-
cution ends with a carriage return <CR>. Consequently, if you have a configuration as shown below (without the all
option being active):

Config>privilege 12 “>config>confirm-cfg”
Config>privilege 12 “>config>protocol *>no *"
Config>

And access with user level 10 and try and carry out the following executions:

Config>confirm-cfg
CLI Error: Incomplete command
Config>protocol ip

66 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

-- Internet protocol user configuration --

IP config>no description
CLI Error: Command error
IP config>

You get an error in execution, as these commands have access level 12. However if you execute:

Config>confirm-cfg-needed default
Config>protocol ip
-- Internet protocol user configuration --
IP config>no aggregation-route 192.168.0.0 255.255.0.0
IP config>

No error has been produced as the all option has not been configured. The access level change has not affected
these commands (they take access level 10 by default).

This system allows you to specify different access levels for the same command, with the possibility of creating two
types of users: default and strict (see the user command). Where this situation arises and a default user (not strict)
accesses, the system assigns the most restrictive access layer (highest) to the command .

2.4.26.1 Example: user to configure IP telephony

Here we are going to see how to use the commands execution privilege to define a user who can only configure
parameters related to the device IP telephony. Two users are defined: one with root privileges and the other with ac-
cess level 7, which has monitoring privileges as well as the privileges configured through the privilege command.

The voip user can access all the voip voice interfaces: the telephony menu, the sip and h323 protocols; he can
configure access lists 50 and use them in telephony, configure two nsm operations and two filters, nsla alarm
and adviser, a global-profiles dial profile known as voip to be applied in an isdn voice interface, he can exit any
menu through the exit command and save the configuration. This user has full control over the IP telephony con-
figuration for the device; however he cannot modify any routing parameter or restart the device.

; -- Privilege Configuration –
privilege 7 ">config>feature access-list>access-list 50" all
privilege 7 ">config>feature access-list>access-list 51" all
privilege 7 ">config>feature access-list>no access-list 50" all
privilege 7 ">config>feature access-list>no access-list 51" all
privilege 7 ">config>feature nsla>advisor 10" all
privilege 7 ">config>feature nsla>advisor 11" all
privilege 7 ">config>feature nsla>alarm 10" all
privilege 7 ">config>feature nsla>alarm 11" all
privilege 7 ">config>feature nsla>filter 10" all
privilege 7 ">config>feature nsla>filter 11" all
privilege 7 ">config>feature nsla>no advisor 10" all
privilege 7 ">config>feature nsla>no advisor 11" all
privilege 7 ">config>feature nsla>no alarm 10" all
privilege 7 ">config>feature nsla>no alarm 11" all
privilege 7 ">config>feature nsla>no filter 10" all
privilege 7 ">config>feature nsla>no filter 11" all
privilege 7 ">config>feature nsm>no operation 10" all
privilege 7 ">config>feature nsm>no operation 11" all
privilege 7 ">config>feature nsm>operation 10" all
privilege 7 ">config>feature nsm>operation 11" all
privilege 7 ">config>global-profiles dial>no profile voip" all
privilege 7 ">config>global-profiles dial>profile voip" all
privilege 7 ">config>network voip" all
privilege 7 ">config>protocol h323" all
privilege 7 ">config>protocol sip" all
privilege 7 ">config>save" all
privilege 7 ">config>telephony" all
privilege 7 "exit"
;
;
user root hash-password A44AD55CE197114B241EE3DDEBB04660
;
user voip hash-password 7A325D20A3B026A12D094C61DB21D880
user voip access-level 7
;
event

Configuration and Monitoring 67

2 Teldat Router Configuration Teldat SA

; -- ELS Config --
enable syslog subsystem CNSL ALL
console
; -- Console Events Configuration --
log source-ip
log prompt
exit
;
exit
;
feature syslog
; -- SYSLOG client configuration --
enable
server 172.24.51.47
exit

In addition, the sending of events to a syslog server is configured with each command executed in the device, so
there is a register of all commands executed by each user. The IP of the device, which sends the event and the com-
plete prompt used when executing the device, is included in the event. As you can see below, the event also in-
cludes the user who executed the command and where the user connected: this could be a remote IP or local con-
sole.

06-23-2006 10:54:48 Local7.Info 172.24.78.156 Jun 23 09:46:43

CNSL:001 usr voip (172.24.79.34:209) exe *logout
06-23-2006 10:54:31 Local7.Info 172.24.78.156 Jun 23 09:46:26
CNSL:001 usr voip (172.24.79.34:209) exe Config$<Esc>
06-23-2006 10:54:27 Local7.Info 172.24.78.156 Jun 23 09:46:23
CNSL:003 usr voip (172.24.79.34:209) run Telephony Config$exit
06-23-2006 10:54:21 Local7.Info 172.24.78.156 Jun 23 09:46:16
CNSL:001 usr voip (172.24.79.34:209) exe Telephony Config$sho conf
06-23-2006 10:54:18 Local7.Info 172.24.78.156 Jun 23 09:46:13
CNSL:003 usr voip (172.24.79.34:209) run Config$telephony
06-23-2006 10:54:02 Local7.Info 172.24.78.156 Jun 23 09:45:57
CNSL:001 usr voip (172.24.79.34:209) exe *p 5

2.4.27 PROTOCOL
This accesses the configuration environment for a specific protocol. The protocol command, followed by a protocol
name, accesses the configuration for the desired protocol. The number of available protocols depends on the type of
device and on the application license the device has.

To enter the configuration environment for a specific protocol:

(1) Enter protocol ? to see the list of configurable protocols in the router:
Example:

Config>protocol ?
arp Access ARP protocol
asrt Access ASRT protocol
bfd Access BFD protocol
bgp Access BGP protocol
dhcp Access DHCP protocol
dhcpv6 Access DHCPv6 protocol
dls Access DLS protocol
dot1x Access 802.1X protocol
gw104 Access GW-104 protocol
h323 Access H323 protocol
igmp Access IGMP protocol
ip Access IP protocol
ipv6 Access IPv6 protocol
l2tp Access L2TP protocol
mgcp Access MGCP protocol
msdp Access MSDP protocol
nhrp Access NHRP protocol
noe Access NOE protocol
ospf Access OSPF protocol
ospfv3 Access OSPFv3 protocol
pim Access PIM protocol
rip Access RIP protocol

68 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

ripng Access RIPNG protocol

sccp Access SCCP protocol
sip Access SIP protocol
snmp Access SNMP protocol
Config>protocol

(2) Enter protocol followed by the name of the protocol you want to configure. The specified protocol prompt ap-
pears. Here, enter the selected protocol configuration commands.
Example:

Config>protocol arp
-- ARP user configuration --
ARP config>

(3) Enter exit to return to the Config> prompt menu.

Example:

ARP config>exit
Config>
Syntax:

Config>protocol <name>

• <name> name of the protocol for the configuration menu you want to access.
Example:

Config>protocol ip
-- Internet protocol user configuration --
IP config>

2.4.28 QUICK CONFIGURATION

This accesses the quick menu configuration environment. Please see manual Teldat Dm211-I . This command de-
pends on the device i.e. it might not apply to your device.

Example:

Config>quick-configuration
-- Quick Configuration Menu --
Quick config>

Command history:

Release Modification
11.00.02 This command is obsolete as of version 11.00.02. Quick menu configuration is no longer
supported.

2.4.29 RUSH-ENGINE
Configures Rush engine parameters.

Rush engine is a traffic flow accelerator, which optimizes routing performance by learning existing flows and using a
cache for packets received from each flow.

When a flow is learned from existing traffic, it is stored in the cache while said traffic persists. After a predefined time
of traffic inactivity (idle flow timeout), said flow is removed from the cache.

Syntax:

Config>rush-engine ?
disable Disable Rush Engine
timeout Rush Engine idle flows timeout in seconds
<cr>
Config>

• disable disables Rush engine.

• timeout configures idle flows timeout in seconds. Default is 5. The valid range is between 1 and 3600 seconds.

Command history:

Configuration and Monitoring 69

2 Teldat Router Configuration Teldat SA

Release Modification
11.01.00 This command was introduced as of version 11.01.00.

2.4.30 SAVE
Allows you to store the configuration in the active storage unit. The active storage unit is configured through the con-
fig-media command.

Before executing this, if the command does not have parameters indicating the contrary, the operation requests con-
firmation for said process. If confirmed, the selected media is accessed and the operation results are displayed.
Where the active unit is made up of various medias, the operation is carried out over both as indicated in the final
message. For further information, please see the config-media command found in this manual and the installation
manual for your device.

If the configuration confirmation is activated, it's saved in a temporary file (TEMP.CFG ). If the new configuration is
confirmed (confirm-cfg), it is resaved using the corresponding name. If you execute save in a test configuration, it
resaves over TEMP.CFG without modifying the previous configuration, which is restored if you do not confirm.
However, this does not eliminate the timer, so once the test time has timed out if the device has not restarted, the
previous configuration is restored. For further information, please see the confirm-cfg and confirm-cfg-needed
commands.

On using the save command, it’s essential you remember which configuration is being saved. There are two config-
urations in the device at all times, which coincide on startup until the user modifies one of them. One configuration is
accessible from the RUNNING-CONFIG (Config$) process and is used at all times. The other configuration is ac-
cessible from the CONFIG (Config>) process and is only available for editing.

If you execute save in the RUNNING-CONFIG process, you are saving the configuration in use when executing said
command. However, if you execute save from the CONFIG process, you save the configuration you edited in said
process. As a result, you need to be very careful when modifying and saving configurations, particularly if the device
is managed by several users.

Syntax:

Config>save [yes [<file-name>]]

• yes this is an optional parameter that prevents the device prompting the user for confirmation before executing the
save operation. If this value is yes, confirmation is not required. If it is not included, the device requests confirma-
tion.
• < file-name > filename where you wish to save the configuration. If you do not enter any name, the device uses
the active configuration filename (see set file-cfg).

Example 1:

Config>save
Save configuration (Yes/No)? y
Building configuration as text... OK
Writing configuration... OK on Flash
Config>

Example 2:

Config>save yes sample

Building configuration as text... OK
Writing configuration... OK on Flash as sample
Config>

2.4.31 SET
Allows you to configure various general parameters in the system.

Syntax:

Config>set <parameter>
application-active Permits you to select the code used to boot the router
console Set console configuration
contact-person Assign a name or identification to the contact-person
data-link Type of data link for a WAN line
default-conf Restores the default configuration
file-cfg Configure a configuration file as active
ftp Permits you to access the FTP configuration menu

70 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

host-location Physical location of the router

hostname Assign a name to a device
inactivity-timer Configure the maximum inactivity time
login Configure login options
password Configure the device access password
pool Number of bytes assigned to each memory pool
schedule-restart Allows to configure router reset schedule
telnet Access the TELNET protocol configuration
web-probe Access the Web probe configuration

• < parameter > name of the parameter you want to configure.

2.4.31.1 SET APPLICATION-ACTIVE

Allows you to select the code used to boot the router.

Syntax:

Config>set application-active [<code file>]

• < code file > name of the code file you want to boot the router with. If you don’t fill out this field, the available code
files are displayed.

Example:

Config>set application-active appcode1.bin

Config>

2.4.31.2 SET CONSOLE

Accesses the configuration menu to access the device through the local console.

Syntax:

Config>set console

Example:

Config>set console
-- Console configuration --
Con config>?
accounting Set accounting options
authorization Set authorization options
function Set CONF port functionality
login Set login options
speed Set console serial port speed
exit
Con config>

The commands available in the console menu are shown below.

2.4.31.2.1 ACCOUNTING

This command associates a list of accounting methods, which have been defined using the AAA feature. The con-
sole service applies the accounting exec methods from the list when an access to the Shell is registered, and the ac-
counting commands methods from the list when an executed command is registered.

Syntax:

Con config>accounting {commands <level> | exec} <listname>

• commands indicate the methods list contains accounting commands.

• < level > indicates the access level for the command you want to count.
• exec indicates the methods list contains accounting exec.
• < listname > this is the identifier for the accounting methods list.

Example 1:

Con config>accounting commands 10 AccCmds

Con config>

In example 1, the AccCmds methods list is configured to be used when accounting for a level 10 command is ex-

Configuration and Monitoring 71

2 Teldat Router Configuration Teldat SA

ecuted.

Example 2:

Con config>accounting exec AccExec

Con config>

In example 2, the AccExec methods list is configured to be used when accounting for access to the Shell is ex-
ecuted.

The lists of methods can only be applied if the AAA feature is enabled. To do this, once the AAA configuration has fi-
nalized, you need to enable it so the lists can be applied to the different services. Further information on this can be
found in manual Teldat Dm800-I AAA Feature .

2.4.31.2.2 AUTHORIZATION

This command associates a list of authorization methods, which have been defined using the AAA feature. The con-
sole service applies the authorization exec methods from the list when authorization is needed from the Shell and au-
thorization commands when authorization from a command is needed.

Syntax:

Con config>authorization {commands <level> | exec} <listname>

• commands indicate the methods list contains authorization commands.

• < level > indicates the access level for the commands needing authorization.
• exec indicates the methods list contains authorization exec.
• < listname > this is the identifier for the authorization methods list.

Example 1:

Con config>authorization commands 10 AuthorCmds

Con config>

In example 1, the AccCmds methods list is configured to be used when authorization is required from level 10 com-
mands.

Example 2:

Con config> authorization exec AuthorExec

Con config>

In example 2, the AccExec methods list is configured to be used when authorization is needed from the Shell.

The lists of methods can only be applied if the AAA feature is enabled. To do this, once the AAA configuration has fi-
nalized, you need to enable it so the lists can be applied to the different services. Further information on this can be
found in manual Teldat Dm800-I AAA Feature .

2.4.31.2.3 FUNCTION

Allows you to configure the CONF port behavior as well as listing its configuration state.

In some device versions, you can select the local console port (CONF) function. In said devices, this port can behave
as a local console or as an asynchronous serial port (UART).

On configuring the Asynchronous serial port mode, the CONF connector appears as a UART interface when listing
the equipment’s devices.

Example:

Config>list dev

Config>list dev
Interface Connector Type of interface
ethernet0/0 EXP/SWITCH Marvell Fast Ethernet Switch
serial0/0 SERIAL0/WAN1 Auto Install Interface
uart0/0 CONF Asynchronous Serial Line
x25-node --- Router->Node
cellular1/0 SLOT1 AT COM
cellular1/1 SLOT1 AT COM
ppp1 --- Generic PPP
Config>

72 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

This command allows the following options:

Con config>function ?
set Set CONF port functionality
list List CONF port functionality
Con config>

As this function affects the device BIOS, as in Asynchronous serial port mode, the device doesn’t send data through
this interface during startup. This command is not affected by the save command. The device also has to be re-
booted so the configured value takes effect.

Note

This command is not affected by the save command.

Note

The device must be rebooted so the configured mode can take effect.

Note

This command cannot be seen through the show configuration command. As this is a special com-
mand affecting BIOS behavior on startup, the CONF port behavior is configured when installing the
device and consequently is not modified.

FUNCTION SET

Allows you to select the operating mode for the CONF port. The two options are console or asynchronous serial
line.

Syntax:

Con config>function set <mode>

• < mode > operating mode.

Example:

Con config>function set ?

console Console CLI
async-serial-line asynchronous serial line
Con config>function set async-serial-line

FUNCTION LIST

Allows you to list the mode the CONF port is configured in.

Syntax:

Con config>function list

Example:

Con config>function list

CONF port functionality: async-serial-line
Con config>

2.4.31.2.4 LOGIN ATTEMPTS

Allows you to configure the number of successive failed login attempts before blocking access through the local con-
sole.

Syntax:

Con config>login attempts <max_attempts>

• < max_attempts > this is the maximum number of login attempts.

Example:

Con config>login attempts 2

Configuration and Monitoring 73

2 Teldat Router Configuration Teldat SA

Con config>

2.4.31.2.5 LOGIN AUTHENTICATION

This command associates an authentication login methods list defined through the AAA feature. The console service
can apply the methods from the associated list when authentication is executed.

Syntax:

Con config>login authentication <listname>

• <listname> this is the identifier for the authentication methods list.

Example:

Con config>login authentication AutheLogin

Con config>

In example, the AutheLogin methods list is configured to be used when authentication is required from a user ac-
cessing through the console.

The lists of methods can only be applied if the AAA feature is enabled. To do this, once the AAA configuration has fi-
nalized, enable it so the lists can be applied to the different services. Further information this can be found in manual
Teldat Dm800-I AAA Feature .

2.4.31.2.6 LOGIN BLOCKING

Allows you to configure the blocking time for the local console where the configured number of failed login attempts
has been reached.

Syntax:

Con config>login blocking <blocking_time>

• < blocking_time > this is the time the local console stays blocked for, when the configured number of failed login
attempts has been reached.

Example:

Con config>login blocking 1m

Con config>

2.4.31.2.7 SPEED

Allows you to configure the speed (baud rate) for the local console port.

Syntax:

Con config>speed <baud>

• < baud > This is the baud rate for the local console port in bits per second. This can only support certain values.

Example:

Con config>speed ?
9600 bits per second
14400 bits per second
19200 bits per second
38400 bits per second
57600 bits per second
115200 bits per second
Con config>speed 115200
Con config>

2.4.31.2.8 EXIT

Returns to the previous prompt.

Syntax:

Con config>exit

Example:

Con config>exit

74 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

Config>

2.4.31.3 SET CONTACT-PERSON

Allows you to assign a name or identification to the contact-person for this router. The name is limited to a maxim-
um of 79 characters. This information can be displayed by entering list configuration.

Syntax:

Config>set contact-person <name>

• < name > contact person name or identifier.

Example:

Config>set contact-person Antonio Leon

Config>

2.4.31.4 SET DATA-LINK

Selects the type of data-link for a WAN line.

Syntax:

Config>set data-link <type> <interface name>

• < type > type of data link to apply to the WAN line.

Enter the set data-link ? command to find out what types are available.

Example:

Config>set data-link ?
arly Alarm Relay on asyncronous data link for a WAN line
asdp ASDP data link for a WAN line
astm ASTM data link for a WAN line
async Asynchronous data link for a WAN line
at AT modem data link for a WAN line
frame-relay Frame-Relay data link for a WAN line
scada SCADA data link for a WAN line
sdlc SDLC data link for a WAN line
sepi SEPI data link for a WAN line
sync Synchronous data link for a WAN line
udafo Udafo data link for a WAN line
x25 X25 data link for a WAN line
x28 X28 data link for a WAN line

• < interface name > WAN interface name over which you wish to apply the specified link type.

To find out what WAN interfaces are available in the device, enter the list devices command.

Example:

Config>list devices
Interface Connector Type of interface
ethernet0/0 GE0/FE0/LAN1 Fast Ethernet interface
ethernet0/1 GE1/FE1/LAN2 Fast Ethernet interface
serial0/0 SERIAL0/WAN1 Auto Install Interface
serial0/1 SERIAL1/WAN2 X25
bri0/0 BRI/ISDN1 ISDN Basic Rate Int
x25-node --- Router->Node
Config>

Example:

Config>set data-link frame-relay serial0/0

Config>list devices
Interface Connector Type of interface
ethernet0/0 GE0/FE0/LAN1 Fast Ethernet interface
ethernet0/1 GE1/FE1/LAN2 Fast Ethernet interface
serial0/0 SERIAL0/WAN1 Frame Relay
serial0/1 SERIAL1/WAN2 X25
bri0/0 BRI/ISDN1 ISDN Basic Rate Int

Configuration and Monitoring 75

2 Teldat Router Configuration Teldat SA

x25-node --- Router->Node

Config>

Subsequently, enter the list devices command to see if the above command has been successful.

2.4.31.5 SET DEFAULT-CONFIG

Eliminates the current configuration and restores the default configuration. This command depends on the device
and consequently may not apply to the equipment you have.

Syntax:

Config>set default-conf [yes]

Example:

Config>set default-conf yes

Config>

2.4.31.6 SET FILE CFG

Allows you to configure a configuration file as active. This is the one processed when the device is restarted.

The active storage unit is also displayed. For further information on how to change the unit, please see the config-
media command found in this manual.

Syntax:

Config>set file-cfg [<file name>]

• < file name > name of the configuration file to activate.

The file name is indicated without extensions. If none is passed by the line command, a list of available files with cfg
extension is displayed. If the selected file does not exist the device, on rebooting, uses the default configuration.

Example:

Config>set file-cfg
Config Media: Flash only
A: ROUTER 494 12/05/06 20:15 Flash
A: SAMPLE 523 12/11/06 15:15 Flash
Current config: ROUTER
Config>set file-cfg sample
Config>

2.4.31.7 SET FTP

Accesses the FTP (File Transfer Protocol) configuration menu. For further information please see manual Teldat
Dm724-I FTP Protocol.

Syntax:

Config>set ftp

Example:

Config>set ftp
-- FTP user configuration --
FTP config>

2.4.31.8 SET HOST-LOCATION

Physical location of the router. This information is displayed by entering list configuration.

Syntax:

Config>set host-location <place>

• < place > physical location of the router. Admits up to a maximum of 79 characters for the location length.

Example:

Config>set host-location Tres cantos (Madrid)

Config>

76 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

2.4.31.9 SET HOSTNAME

Allows you to assign a name to a device. This information is seen by entering list configuration.

Syntax:

Config>set hostname <name>

• < name > device name. Up to a maximum of 79 characters.

Example:

Config>set hostname SuperRouter

Config>

2.4.31.10 SET IGNITION-OFF-POWERDOWN-TIMER

Note

This command is only available in devices, with the power management feature installed, usually inten-
ded for vehicles and powered by the vehicle battery. To determine if your device supports this feature,
please see the device installation manual.

CHECK THIS WITH THE PARAGRAPH WRITTEN EARLIER IN THE MANUAL

Allows you to configure the time the device remains operating after switching off the ignition in the vehicle it is in-
stalled in. The aim is to keep the device operating during a configurable period of time, automatically powering down
once said period has timed out. This prevents the battery in the vehicle from being used (or flattened).

Syntax:

Config>set ignition-off-powerdown-timer [<time> | disabled]

• < time > time (in minutes) the device remains powered after switching off the vehicle’s ignition where said device is
installed. Once this timer has timed out, the device executes an ordered shutdown and subsequently powers down.
The range is between 0 and 1044 minutes (24 hours).
• disabled disables the timer so as soon as you switch off the ignition, the device powers down.

Example:

Config>set ignition-off-powerdown-timer 20
Config>

• By default, this feature is disabled. If you do not configure a time period then the device powers down as soon as
the ignition is switched off (this is the same as a set ignition-off-powerdown-timer disabled).

2.4.31.11 SET INACTIVITY-TIMER

Allows you to configure the maximum inactivity time in the process to access the device through a remote terminal
(TELNET). Once this has timed out, the device Telnet server disconnects.

This maximum inactivity time period is also applied to the local connection in the device console. If the configured in-
active time period times out without any of the keys being touched, the local connection closes. If the user wishes to
use the console again, he must reenter the password.

Syntax:

Config>set inactivity-timer [<time> | disabled]

• < time > maximum inactivity time in minutes before the telnet connection closes or the console blocks. The range
is between 1 minute and 10 hours.
• disabled disables the timer so neither the telnet connection nor the console block closes, unless the remote device
closes said telnet connection or the user terminates the session through the logout command.

Example:

Config>set inactivity-timer 20
Config>

By default the inactivity timer is set at 10 minutes (equivalent to set inactivity-timer 10).

Configuration and Monitoring 77

2 Teldat Router Configuration Teldat SA

2.4.31.12 SET LOGIN

Allows you to configure parameters relative to the device access name.

Syntax:

Config>set login <option>

case-sensitive Activate login case-sensitiveness

• < option > this is the option to configure.

2.4.31.12.1 SET LOGIN CASE-SENSITIVE

Activates the difference between uppercase and lowercase letters, in the user name authentication process, when
accessing a device through console, telnet or ftp.

Syntax:

Config>set login case-sensitive

Example:

Config>set login case-sensitive

Config>

By default, the difference between uppercase and lowercase letter in user name authentication is disabled.

2.4.31.13 SET PASSWORD

Allows you to configure the device access password through a TELNET remote terminal, a local connection via the
console or connection via FTP.

Syntax:

Config>set password <word>

• < word > password you wish to set.

Example:

Config>set password mk34po99

Config>

2.4.31.14 SET POOL

Allows you to configure the memory distribution in the device’s various POOLs. If this is not correctly configured, the
device may malfunction.

Syntax:

Config>set pool <option> <size>

iorbs Iorbs pool size in bytes
msg Message pool size in bytes

• < option > pool name you want to set the byte size for.
• < size> size in bytes to set for the pool.

Pools available for configuration can be listed by executing the set pool ? command.

Example:

Config>set pool iorbs 2048000

Config>

Note

This command is problematic and should only be executed by a specialist. Incorrect configuration can
cause the device to malfunction.

78 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

2.4.31.15 SET SCHEDULE-RESTART

The aim of this command is to periodically execute device reset at a specific time, or after a determined period of
time from start up. This can be useful for devices that are difficult to access and due to installation conditions, are
susceptible to losing connectivity. In many cases a device reset can reestablish connectivity.

Syntax:

Config> set schedule-restart time <day-time> offset <time-offset>

time Set time of day at which device will restart
offset Set Offset for periods longer than 24 hours

• <day-time> the time of day when you want the device reset to execute or, if you configure time-offset with a value
different to 0, the time of day when the countdown indicated in time-offset begins. This must be expressed in
hh:mm format. The exception being where value is 0.
• < time-offset> this indicates the period movement to execute device reset. The units are seconds, which can be
directly entered: weeks (w), days (d), hours (h), minutes (m) and seconds (s) (e.g. 1w2d3h). Depending on the
value configured in day-time, it’s used in a different way:

- day-time = 0. Indicates the time period between device start up to reset.

- day-time # 0. Indicates the time period from the point where the time indicated in day-time is reached until a
device reset is produced.

Example:

Config> set schedule-restart time 03:30 offset 2d

Config>

Allows you to configure a device programmed reset in three different ways:

• Every day, at the same time:

Do not configure the offset value, i.e. it should be 0.

The following example shows a daily device restart at 03:30.

Config> Config>set schedule-restart time 03:30

Config>

Or:

Config> Config>set schedule-restart time 03:30 offset 0

Config>

• Every X many days or an hour + offset:

You need to program the time you want the device to reset and the required time period.

Logically you should program a multiple of a day in the offset. If you don’t, you have to calculate when a device re-
set is going to be produced (time + offset).

In either case, the device has a time window of 180 seconds, so if at startup the current time is in the configured
hour + 180 seconds, you only need to check the offset field as this deals with a periodic reset at the same time.
This must be taken into account if you program shorter times (less than one day) in the offset.

In this example the device restarts every 2 days at 16:04.

Config> Config> set schedule-restart time 16:04 offset 2d

Config>

• A period of time after device start up:

You need to set the time field to 0 for this. In the offset field, you program the time that must lapse from start up un-
til the reset occurs.

In this example, this restarts every 18 hours.

Config> Config> set schedule-restart time 0 offset 18h

Config>

We don’t recommend case a) configuration in devices that do not have a Real Time Clock powered with a battery, or
other types of system clock updating (NTP).

To eliminate this programming, you can set both fields to 0 or execute the NO command. E.g.

Configuration and Monitoring 79

2 Teldat Router Configuration Teldat SA

Config> Config>no set schedule-restart time 16:04 offset 2d

Config>

Important

This command can risk the integrity of the device. Before loading a new software version, module firm-
ware or saving the configuration, ensure that the automatic process DOES NOT reset the device.

2.4.31.16 SET TELNET

Accesses the TELNET protocol configuration. For further information, please see manual Teldat Dm738-I TELNET
Protocol.

Syntax:

Config>set telnet

Example:

Config>set telnet
-- Telnet user configuration --
Telnet config>

2.4.31.17 SET WEB-PROBE

Accesses the Web probe configuration. This command or functionality depends on the device i.e. it might not apply
to your device.

Syntax:

Config>set web-probe

Example:

Config>set web-probe
-- Web Probe user configuration --
Probe config>

For further information, please see manual Teldat Dm749-I NSM (Network Service Monitor).

2.4.32 STRONG PASSWORD

Enables user password checking and does not allow unsafe or weak passwords. The robustness of the password
can be configured from 0 to 5, 0 being the default value and another allowing you to set a stronger password.

Syntax:

Config>strong-password ?
<0..5> Level of strength (0: strongest)
<cr>

Example:

Config>strong-password 1

2.4.33 TELEPHONY
Accesses Voice over IP (VoIP) telephony parameters configuration environment.

Syntax:

Config>telephony

Example:

Config>telephony
-- Telephony configuration --
Telephony Config>

For further information, please see manual Teldat Dm722-I Voice over IP.

80 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

2.4.34 TIME
Allows you to change and check the device date and time. You can also configure summer time (or daylight saving)
start and end times.

Syntax:

Config>time <option> [parameters]

list Check the date and time of the device
no Negates a command or sets its defaults
set Change the date and time of the device
summer-time Configure summer (daylight savings) time
timezone Changes the difference in hours with respect to UTC times

• < option > name given to the action to execute.

• [parameters] parameters required for the specified option.

The available operations (options) are as follows:

2.4.34.1 TIME LIST

Use this command to check the date and time of the device.

Syntax:

Config>time list

Example:

Config>time list
Set by: operator
Date: Wednesday, 03/02/05 Time: 16:28:46 CET
Config>

2.4.34.2 TIME SET

Use this command to change the date and time of the device.

Syntax:

Config>time set <month> <day> <year> <week day> <hour> <minute> <seconds>

• < month > month corresponding to the date you wish to set.
• < day > day corresponding to the date you wish to set.
• < year > year corresponding to the date you wish to set.
• < week day > weekday corresponding to the date you wish to set.
• < hour > hours corresponding to the time you wish to set.
• < minute > minutes corresponding to the time you wish to set.
• < seconds > seconds corresponding to the hour you wish to set.

Example:

Config>time set 3 2 5 3 16 29 59
Config>

Note

Some devices lose the date and time settings when restarted. Said parameters must be configured us-
ing the NTP Protocol. Please see manual Teldat-Dm728 NTP Protocol for further information.

2.4.34.3 TIME NO

Invalidates a command action within the time configuration environment or establishes the default values.

Syntax:

Config>time no <option>

Configuration and Monitoring 81

2 Teldat Router Configuration Teldat SA

• < option > specifies the selected option. The available options are summer-time and timezone.

2.4.34.3.1 TIME NO SUMMER-TIME

Deletes the preconfigured summer-time application period.

Syntax:

Config>time no summer-time <option>

zone-name Deletes summer time zone name
<cr> Deletes summer time configuration

• < option > specifies the selected option.

i) time no summer-time zone-name

Only deletes the name associated to the summer period.

Syntax:

Config>time no summer-time zone-name

Example:

Config>sho menu
; Showing Menu Configuration for access-level 15 ...
log-command-errors
no configuration
set inactivity-timer disabled
time summer-time recurring 1 mon jan 03:00 1 mon dec 03:00
time summer-time zone-name "CET"
;
dump-command-errors
end
Config>time no summer-time zone-name
Config>show menu
; Showing Menu Configuration for access-level 15 ...
log-command-errors
no configuration
set inactivity-timer disabled
time summer-time recurring 1 mon jan 03:00 1 mon dec 03:00
;
dump-command-errors
end
Config>

ii) time no summer-time

Deletes the entire configuration associated to the summer period, both for dates and the start and end times and the
name associated to said time period.

Syntax:

Config>time no summer-time

Example:

Config>show menu
; Showing Menu Configuration for access-level 15 ...
log-command-errors
no configuration
set inactivity-timer disabled
time summer-time recurring 1 mon jan 03:00 1 mon dec 03:00
time summer-time zone-name "CET"
;
dump-command-errors
end
Config>time no summer-time
Config>show menu
; Showing Menu Configuration for access-level 15 ...

log-command-errors

82 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

no configuration
set inactivity-timer disabled
dump-command-errors
end
Config>

2.4.34.4 TIME SUMMER-TIME

Use this command to configure summer-time start and end times. Apply an offset of one hour (must be added to the
clock value), which you would get if you were not within this period.

Config>time summer-time <option>

date Configure absolute summer time
list Display configured summer time
recurring Configure recurring summer time
zone-name Configure summer time zone name

• < option > specifies the selected option.

There are four available options (three in configuration and one in monitoring).

2.4.34.4.1 TIME SUMMER-TIME DATE

Allows you to configure the summer-time period indicating the summer-time start and end using precise times and
dates. This is known as absolute time configuration.

Syntax:

Config>time summer-time date <start day> <start

month> <start
year> <start
hour> <end
day> <end
month> <end
year> <end
hour>

• < start day > the day of the month to set for starting the summer-time period.
• < start month > the month to set for starting the summer-time period. Indicate which month by using the first three
letters (jan/feb/mar/apr/may/jun/jul/aug/sep/oct/nov/dec).
• < start year > the year to set for starting the summer-time period using the last two digits for the appropriate year
(05 for 2005).
• < start hour > this is the time, in hours and minutes (HH:MM) to set for starting the summer-time period.
• < end day > the day of the month to set for the end of the summer-time period.
• < end month > the month to set for the end of the summer-time period. Indicate which month by using the first
three letters (jan/feb/mar/apr/may/jun/jul/aug/sep/oct/nov/dec).
• < end year > the year to set for the end of the summer-time period, using the last two digits for the appropriate
year (05 for 2005).
• < end hour > this is the time, in hours and minutes (HH:MM) to set for the end of the summer-time period.

Example:

Config>time summer-time date 30 mar 05 02:00 26 oct 05 03:00

Config>

2.4.34.4.2 TIME SUMMER-TIME RECURRING

Allows you to configure the summer-time period establishing the summer-time start and end using the weekday, the
number of the week within the month, the month, the hour and minute after which the one hour offset must be taken
into consideration and the same parameters to configure return to normal time. Once this data has been entered, the
switch to summer-time and return to normal time is repetitively carried out each year.

Syntax:

Config>time summer-time recurring <start

week number> <start
week
day> <start
month> <start

Configuration and Monitoring 83

2 Teldat Router Configuration Teldat SA

hour> <end
week number> <end
week
day> <end
month> <end
hour>

• < start week number > the number of the week within the month to apply summer-time start (1 to 5).
• < start week day > weekday you want summer-time to start. Indicate the day by entering the first three appropriate
letters (mon/tue/wed/thu/fri/sat/sun).
• < start month > month to set for starting the summer-time period. Indicate the month by using the first three letters
(jan/feb/mar/apr/may/jun/jul/aug/sep/oct/nov/dec).
• < start hour > time, in hours and minutes (HH:MM) to set for starting the summer-time period.
• < end week number > number of the week within the month to apply the return to the normal timetable (1 to 5).
• < end week day > day of the month to set for the return to the normal timetable. Indicate the day by entering the
first three appropriate letters ( mon/tue/wed/thu/fri/sat/sun).
• < end month > month to set for the return to the normal timetable. Indicate the month by using the first three ap-
propriate letters (jan/feb/mar/apr/may/jun/jul/aug/sep /oct/nov/dec).
• < end hour > time, in hours and minutes (HH:MM) to set to return to the normal timetable.

Example:

Supposing summer-time period starts on the fourth (start week number = 4) Sunday (start week day = sun) of March
(start month = mar) at 2 a.m. (start hour = 02:00), and ends the fourth (end week number = 4) Sunday (end week
day = sun) in October (end month = oct) at 3 a.m. (end hour = 03:00), enter the following:

Config>time summer-time recurring 4 sun mar 02:00 4 sun oct 03:00

Config>

However on occasions, this rule is not flexible enough; for example, March 2007 has four Sundays while in 2008 it
has five. To adapt to this situation, you can configure 5 as the week number within the month < start week number
> and/or < end week number >). Given the special significance of these parameters, when you configure a 5, the
changes are applied to the last day of the week configured within the configured month, both when in one year there
are 5 weeks as when there are only four.

Example:

Supposing we want our summer-time period to annually begin the last Sunday in March at 2 a.m. and end the last
Sunday in October (again every year) at 3 a.m., we need to enter:

Config>time summer-time recurring 5 sun mar 02:00 5 sun oct 03:00

Config>

2.4.34.4.3 TIME SUMMER-TIME ZONE-NAME

Configures the name associated to the summer-time period.

The assigned text can have a maximum of 15 characters.

Syntax:

Config>time summer-time zone-name <text>

• < text > name associated to the summer-time period. If this text contains spaces, it must be entered between com-
mas (e.g. description “description containing spaces”).

Example:

Config>time summer-time zone-name CET

Config>

The following shows a table containing the acronyms commonly used in the distinct time zones for this parameter.
ACRONYM
TIME ZONE NAME AND OFFSET WITH RESPECT TO UTC
Europe
GMT Greenwich Mean Time, as UTC
BST British Summer Time, as UTC + 1 hour
IST Irish Summer Time, as UTC + 1 hour
WET Western Europe Time, as UTC
WEST Western Europe Summer Time, as UTC + 1 hour
84 Configuration and Monitoring
Teldat SA 2 Teldat Router Configuration

CET Central Europe Time, as UTC + 1

CEST Central Europe Summer Time, as UTC + 2
EET Eastern Europe Time, as UTC + 2
EEST Eastern Europe Summer Time, as UTC + 3
MSK Moscow Time, as UTC + 3
MSD Moscow Summer Time, as UTC + 4
United Stataes and Canada
AST Atlantic Standard Time, as UTC –4 hours
ADT Atlantic Daylight Time, as UTC –3 hours
ET Eastern Time, either as EST or EDT, depending on place and time of year
EST Eastern Standard Time, as UTC –5 hours
EDT Eastern Daylight Saving Time, as UTC –4 hours
CT Central Time, either as CST or CDT, depending on place and time of year
CST Central Standard Time, as UTC –6 hours
CDT Central Daylight Saving Time, as UTC –5 hours
MT Mountain Time, either as MST or MDT, depending on place and time of year
MST Mountain Standard Time, as UTC –7 hours
MDT Mountain Daylight Saving Time, as UTC –6 hours
PT Pacific Time, either as PST or PDT, depending on place and time of year
PST Pacific Standard Time, as UTC –8 hours
PDT Pacific Daylight Saving Time, as UTC –7 hours
AKST Alaska Standard Time, as UTC –9 hours
AKDT Alaska Standard Daylight Saving Time, as UTC –8 hours
HST Hawaiian Standard Time, as UTC –10 hours
Australia
WST Western Standard Time, as UTC + 8 hours
CST Central Standard Time, as UTC + 9.5 hours
EST Eastern Standard/Summer Time, as UTC + 10 hours (+11 hours during summer time)

2.4.34.4.4 TIME SUMMER-TIME LIST

Displays the period established as summer-time.

Syntax:

Config>time summer-time list

Example 1:

Config>time summer-time list

Absolute summer time configured:
Start: Date: 30/03/03 Time: 02:00
End: Date: 26/10/03 Time: 03:00
Zone-name: CET
Config>

Example 2:

Config>time summer-time list

Recurring summer time configured:
Start: Sunday 4th week of March at 02:00
End: Sunday 4th week of October at 03:00
Zone-name: CET
Config>

Lastly, this indicates it’s possible to obtain the summer-time configuration in text mode. through the show config
command.

Example 1:

Config>show menu
; Showing Menu Configuration for access-level 15 ...

Configuration and Monitoring 85

2 Teldat Router Configuration Teldat SA

log-command-errors
no configuration
time summer-time date 30 mar 3 02:00 26 oct 3 03:00
;
dump-command-errors
end
Config>

Example 2:

Config>show menu
; Showing Menu Configuration for access-level 15 ...
log-command-errors
no configuration
time summer-time recurring 4 sun mar 02:00 4 sun oct 03:00
;
dump-command-errors
end
Config>

2.4.34.5 TIME TIMEZONE

Use this command to configure the differences in hours with respect to UTC time. This determines the time zone
where the device is located.

Syntax:

Config>time timezone <-12…12>

Example:

Config>time timezone 1
Config>

Note

Permitted values are from -12 to 12. Default is 1.

2.4.35 UCI
Use the UCI command to configure the router encryption unit.

Syntax:

Config>uci <option> [parameters]

cfg
change cfg
keys
lqueue
mode
table
user_password
lqueue

• < option > specifies the selected option.

• [parameters] parameters, which must be entered depending on the selected option.

2.4.36 UNSET-DEMO-LICENCE
Unsets demo licence currently being used in the device. After a restart, restart the base licence is used.

This command is only enabled when there actually is an active demo licence.

Syntax:

Config> unset-demo-licence

Example:

86 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

Config>unset-demo-licence
Demo licence disabled. Restart device to start using the base licence
Config>

2.4.37 USER
Use this command to create and configure the users who have permission to access the device.

2.4.37.1 Creating a user

Syntax:

Config>user <name> <password | hash-password> <pwd>

• < name > name of the new user you wish to create.
• <password | hash-password> specifies the password format – text in clear or hash code – to be subsequently
entered for the specified user.
• < pwd> access password in the selected format to give to the specified user.

Example:

Config>user usersample password trescantos1985

Config>

On displaying the configuration – show configuration command - for a device where users have been created, for
security reasons, creation command lines for said users always appears using the hash-password option, independ-
ently of whether this option was originally chosen. This means a user password does not appear in clear and cannot
be discovered from the device configuration file. Should the user and the device administrator forget his/her pass-
word, said user must be recreated with a new access password.

Example:

Config>show menu
; Showing Menu Configuration for access-level 15 ...
log-command-errors
no configuration
user usersample hash-password E7AE08B3FEB1F020EEEDE75FCD0D41F1
;
dump-command-errors
end
Config>

2.4.37.2 User management

One, two or more users2 have been created, you can manage the access level for them, enable or disable their ac-
cess, etc. To access a user configuration menu, carry out the following:

Syntax:

Config>user <name> <option> <parameter>

access-level Specify the user access level
active Activate the user
hash-password Entry the hash of the password
keymanager IPSec keys manager
no Negates a command or sets its defaults
password Entry the password

• < name > name of the user you wish to manage.

• <option> specifies the management operation you wish to execute.
• < parameter> parameters required for the selected option.

The available management operations (options) are:

2.4.37.2.1 access-level

Specifies the user access level.

Syntax:
[2] Previously, this would have made no sense as if there is only one user, he/she must be the device administrator - root - and consequently would
have all permissions activated.

Configuration and Monitoring 87

2 Teldat Router Configuration Teldat SA

Config>user <name> access-level <level> <mode>

<level>
<0..15> value in the specified range
configuration Configuration access level [10]
events Events access level [1]
monitor Monitor access level [5]
none None access level [0]
root Root access level [15]
<mode>
strict Restricts user access level to exactly the specified value
<cr>

• < name > name of the user you wish to manage.

• < level > access level you wish to assign to the specified user. Select a value from 0 to 15, either by specifying the
digit or using the configuration, access to events, monitoring, none or root labels.
• < mode > device operating mode with respect to the configured access level. There are two modes:

- Default. The user can execute commands requiring an execution level less or equal to his access level.

- Strict. The user can execute commands requiring an execution level, which is exactly the same as his access
level.

Example:

Config>user usersample2 access-level 8 strict

Config>

You can display the created users access level through the list user command in the configuration console.

By default, access level root in default mode is assigned when creating new users.

2.4.37.2.2 active

Enables access to the device for a user.

Syntax:

Config>user <name> active

• < name > name of the user to enable.

Example:

Config>user usersample2 active

Config>

You can display the created users’ access level through the list user command in the configuration console.

By default, when creating new users access to the device for said users is enabled.

2.4.37.2.3 hash-password

Configures the password hash code for the user.

Syntax:

Config>user <name> hash-password <hash code>

• < name > name of the user you wish to manage.

• <hash code> password hash code to assign to the specified user.

Example:

Config>user usersample2 hash-password E7AE08B3FEB1F020EEEDE75FCD0D41F1

Config>

You can view the created users password hash code by using the show configuration command in the configura-
tion console.

2.4.37.2.4 keymanager

Configures a user as the IPSec keymanager for the device. This action can only be carried out by a user with root
access level or, if there be one, by another keymanager user.

88 Configuration and Monitoring

Teldat SA 2 Teldat Router Configuration

This command divides the permission management system, creating two completely independent profiles: one for
IPSec key configuration only and the other exclusively for configuring the rest of the device parameters.

Syntax:

Config>user <name> keymanager

• < name > name of the user you wish to configure.

Example:

Config>user usersample2 keymanager

Config>

Note

Given the existence of this type of special user, there would be no specific user with total control over
the device configuration system. We do not recommend using this option except in extreme cases
where the device management is shared.

You can view the users configured as keymanager using the list user command in the configuration console.

2.4.37.2.5 no

Invalidates a command action or establishes its default values.

Syntax:

Config>user <name> no <option>

active Deactivate the user
keymanager IPSec keys manager

• < name > name of the user you wish to configure.

• < option > specifies the operation to execute.

There are two possible options.

2.4.37.2.6 active

Disables the user access to the device.

Syntax:

Config>user <name> no active

• < name > user name.

Example:

Config>user usersample2 no active

Config>

2.4.37.2.7 keymanager

Invalidates the configuration of a user as IPSec keymanager for the device.

Syntax:

Config>user <name> no keymanger

• < name > user name.

Example:

Config>user usersample2 no keymanager

Config>

2.4.37.2.8 password

Configures the password for the user.

Syntax:

Config>user <name> password <text>

Configuration and Monitoring 89

2 Teldat Router Configuration Teldat SA

• < name > name of the user you wish to manage.

• <text> password to assign to the specified user.

Example:

Config>user usersample2 password trescantos1985

Config>

2.4.38 END
Indicates the end of a configuration file. All configuration files must include this command at the end so the file loads
correctly in the device startup process.

This command is automatically added as the last command in the device configuration files (cfg) when executing the
save or show config commands.

Syntax:

Config>end

Example:

Config>show config
; Showing System Configuration for access-level 15 ...
; ATLAS50 Router 9 48 Version 10.7.0
log-command-errors
no configuration
;
;
network ethernet0/0
; -- Ethernet Interface User Configuration --
no ip address
;
exit
;
;
;
network ethernet0/1
; -- Ethernet Interface User Configuration --
no ip address
;
exit
;
;
;
;
network x25-node
; -- X25-node interface configuration --
no ip address
;
Exit
;
;
;
dump-command-errors
end
; --- end ---
Config>

90 Configuration and Monitoring

Teldat SA 3 Router Monitoring

Chapter 3 Router Monitoring

3.1 Introduction
This chapter describes the device monitoring (p3) process. It allows you to view the system status as well as the stat-
istics gathered by the device. It also enables users, with the appropriate access level, to manage said statistics and
execute operating tests over certain features or functionalities in the device.

Bearing in mind the access level required for execution, the following types of commands have been differentiated
within the monitoring process:

• Event type (event -view/hide-). To execute these commands, the user must have an access level higher or equal to
EVENT.
• Show type (listing statistics, interface status, counters, etc.). The user must have an access level higher or equal to
MONITOR to execute these commands. Within this typology, commands such as telnet, ssh, ping, vrf-ping, atm-
ping, traceroute, etc., are also located.
• Clear type (delete/reset of information regarding statistics, registers, counters, etc.). The user must have an access
level higher or equal to CONFIG to execute these commands.
• Conf type (testing of interfaces, events management, IPSec tunnels activation, etc.). The user must have an ac-
cess level higher or equal to CONFIG to execute these commands. Within this typology, commands such as
bping, vrf-bping, tftp, etc., are also located.
• Root type (sends an escape character to a terminal connected to the device and running a session, to force a user
to exit a determined menu or to close the session ). To execute these commands, the user must have a ROOT ac-
cess level (level 15).

When in the monitoring system, the device only shows the commands a user can use (or execute) when he uses the
help command ?

Access levels available in the device, as well as the configuration process for these, are specified in Router Console
on page 1 (section Teldat Router connection on page 2 ) and Teldat Router Configuration on page 16 (section
USER on page 87) in this manual.

3.2 Monitoring procedure commands

MONITOR process entry/exit

Enter the monitoring procedure MONITOR from prompt “*” in the console manager GESTCON using the monitor or
process command, followed by the number identifying the configuration procedure, in this case 3.

Example:

*monitor
Console Operator
+

To exit the MONITOR procedure and return to console manager GESTCON prompt “*”, press the escape character
(Ctrl-p by default).
Command Function
? (HELP) Lists the MONITOR process commands.
BUFFER Displays information on packet buffers assigned to each interface.
CLEAR Clears network statistics.
CONFIGURATION Lists the status of current protocols and interfaces.
DEVICE Displays network hardware statistics or statistics for the specified interface.
ERROR Displays the error counters.
EVENT Enters Event Logging System environment.
FEATURE Accesses monitoring commands for router features, outside usual protocols, and
network interface monitoring processes.
LAST-CONFIG-CHANGES Displays the latest changes made to the configuration.
MALLOC-MONITOR Accesses monitoring commands for device memory management.
MANAGEMENT Enters master router environment.

Configuration and Monitoring 91

3 Router Monitoring Teldat SA

MEMORY Displays memory, buffer and packet data.

NETWORK Enters console environment for a specified network.
NODE Enters node monitoring environment.
PROTOCOL Enters commands environment for a specified network.
QUEUE Displays buffer statistics for a specified interface.
QUICK Accesses quick menu monitoring.
RUSH-ENGINE Accesses Rush engine monitoring.
STATISTICS Displays statistics for a specified interface.
SYSTEM Allows monitoring over the system memory and stacks, the use of the CPU, con-
figure the console port speed, display the firmwares needed (so the device oper-
ates correctly), activate determined debugging information, show the user history
(those who have accessed the device), view the open Telnet and SSH sessions
and exchange commands or messages between terminals corresponding to these
open sessions.
TFTP Accesses device TFTP client.
TELEPHONY Enters monitoring environment for device telephony features.
UCI Encryption statistics.
UPTIME Lists router uptime since last boot.
VERSION Lists running software version.
VISORNET Accesses VisorNet monitoring environment.
WEB-PROBE Accesses web poll monitoring.
LOG Activates or views logging level for events not included in the Event Logging Sys-
tem.

3.2.1 ? (HELP)
List the commands available at the current prompt level. You can also type ? after a specific command to list its op-
tions.

Syntax:

+?

Example:

+?
buffer Packet buffers assigned to each interface
clear Clear network statistics
configuration List status of current protocols and interfaces
device List statistics for the specified interface
error List error counters
event Event Logging System environment
feature Access to monitoring commands for router features
last-config-changes Display the last changes made in the configuration
log Dump log data
malloc-monitor Malloc monitor information
management Master router environment
memory Display memory, buffer and packet data
network Enter the console environment of a specified network
node Enter the node monitoring environment
protocol Enter the commands environment for a specified
protocol
queue Display buffer statistics for a specified interface
quick Access the quick menu monitoring
rush-engine Rush Engine Monitor
statistics Display statistics for a specified interface
system Permit monitoring of the system’s memory and stacks
telephony Monitoring environment for the telephony functions
uci Encryption statistics
web-probe Access the Web poll monitoring
exit
+

92 Configuration and Monitoring

Teldat SA 3 Router Monitoring

3.2.2 BUFFER
Displays information on packet buffers assigned to each interface.

Note

Each buffer on a single device is the same size and dynamically built. Buffers vary in size from one
device to another.

Syntax:

+buffer [<verbose> | <interface>]

• < interface > name of interface you wish to display information for.
• < verbose > displays additional information.

To view available interfaces in the device, enter the configuration command at the + prompt. If you do not enter a
name, information on all interfaces is displayed.

Example:

+buffer
Input Buffers Buffer Sizes
Interface Req Alloc Low Curr Hdr Wrap Data Trail Total
ethernet0/0 40 40 5 40 22 62 1500 4 1588
serial0/0 40 40 5 40 18 62 2048 12 2140
serial0/1 0 0 0 0 0 62 0 0 62
serial0/2 0 0 0 0 0 62 0 0 62
bri0/0 160 160 5 160 17 62 2048 12 2139
x25-node 0 0 0 100 20 62 1500 0 1582

Buffer size: 2144

Packet size: 2048
Trailer size: 12
Packet offset: 84

+ buffer ethernet0/0
Input Buffers Buffer Sizes
Interface Req Alloc Low Curr Hdr Wrap Data Trail Total
ethernet0/0 40 40 5 40 22 62 1500 4 1588

Buffer size: 2144

Packet size: 2048
Trailer size: 12
Packet offset: 84
+

The meaning of each of the fields is as follows:

Interface Interface name.

• Input buffers
Req Number of input buffers requested.
Alloc Number of input buffers allocated.
Low Low water mark (flow control).
Curr Current number of input buffers in this device. If value is 0, the device is disabled. When a packet is
received and the Curr value is below Low, then the flow control can select it. See the queue com-
mand for conditions.

• Buffer sizes
Hdr This is the maximum value between the two following terms:

- largest LLC, plus MAC, plus size of devices headers on output.

- MAC plus size of devices headers on input.

Wrap Margin given for MAC, LLC or network level.
Data Maximum data link level packet size.

Configuration and Monitoring 93

3 Router Monitoring Teldat SA

Trail Sum of the largest MAC and hardware trailers.

Total Global size of each packet buffer. This value is calculated by adding the previous four fields togeth-
er.

• Bytes
Alloc Amount of buffer memory bytes for this device. This value is determined by multiplying the values
of Curr x Total .
Buffer size Complete size of the buffer.
Packet size Maximum packet size.
Trailer size Maximum trailer size.
Packet offset Packet offset in the buffer.

3.2.3 CLEAR
Restarts statistical information on all router interfaces, zeroizing all counters. This command is useful when search-
ing for changes in large counters. Please note that this command does not save memory space or increase the
router speed.

Syntax:

+clear

Example:

+clear
Are you sure to clear stats?(Yes/No)?
+

3.2.4 CONFIGURATION
Displays information on the protocol and network interfaces. The output presented by this command can be divided
into three sections: the first contains data such as router identification, software version, boot ROM version, and the
state of the watchdog, as well as device date and time together with the length of time since last reboot. The second
and third sections display information on protocols that can be monitored and the current interfaces.

Syntax:

+configuration

Example:

+configuration

Teldat's Router, XXXXX 9 48 S/N: 524/00130

P.C.B.=91 Mask=0c10 Microcode=134f0 CLK=262144 KHz BUSCLK=65536 KHz PCICLK=32768 KHz
ID: AT50-16F64R L9.48

DEMO licence active:

Licence will expire in 0 days 23 hours 53 minutes (base licence: 28 1013)

Boot ROM release:

BIOS CODE VERSION: 01.10 Oct 30 2006 17:17:43
gzip Oct 30 2006 17:08:44
io1 Oct 30 2006 17:17:36
io2 Oct 30 2006 17:08:20
io3 Oct 30 2006 17:17:36
START FROM FLASH L1 Watchdog timer Enabled

Software release: 10.7.0 Nov 10 2006 15:20:04

Compiled by INTEGRATOR on INTEGRATOR2000
Loaded from primary partition

Hostname: Active user:

Date: Wednesday, 12/27/06 Time: 12:41:40
Router uptime: 9m4s
Num Name Protocol
0 IP DOD-IP
3 ARP Address Resolution Protocol

94 Configuration and Monitoring

Teldat SA 3 Router Monitoring

4 H323 H323
6 DHCP Dynamic Host Configuration Protocol
11 SNMP SNMP
13 RIP Route Information Protocol
17 SIP SIP
30 EAPOL Extensible Authentication Protocol Over LAN
31 Preauth WLAN Preauthentication

4 interfaces:
Connector Interface MAC/Data-Link Status
GE0/FE0/LAN1 ethernet0/0 Ethernet/IEEE 802.3 Up
GE1/FE1/LAN2 ethernet0/1 Ethernet/IEEE 802.3 Testing
BRI/ISDN1 bri0/0 BRI Net Testing
--- x25-node internal Up

SNMP OperStatus:
Interface OperStatus
ethernet0/0 Up
ethernet0/1 Down
bri0/0 Down
x25-node Up

Encryption Engines:
Hardware: SEC-8272 Revision: 0xA, block 0x0

Cellular Driver Version: 00.09

WLAN Driver Version: 9.5.0.35.1

+

The first block (lines 1-3) display general technical information on the device. The first line lists the type of router,
user license and its serial number.

The second block (lines 4-5) displays information on the demo license (referencing when said license expires) and
base license, which the device returns to on expiry or when manually deactivated. This block only appears if there is
an active demo license.

The third block (lines 6-12) displays the Boot ROM (Read Only Memory) version currently installed in the router from
the BIOS and the current setting for the watchdog timer.

The fourth block (lines 13-15) lists software version currently running on the router.

The fifth block (lines 16-18) displays hostname, active user, the date and time, and the length of time since last
device boot up.

The sixth block lists configured protocols and interfaces. The meaning of each field is as follows:
Num Number associated with the protocol.
Name Abbreviated name of the protocol.
Protocol Full name of the protocol.

The seventh block displays a list of interfaces available in the device. The meaning of each field is as follows:
Connector Connector associated to the interface.
Interface Interface name.
MAC/Data Type of MAC/Data link configured for this interface.
Link
Status Current status of network interface.
Testing The interface is undergoing an auto-test. This occurs the first time the router is
started and this detects problems in the interface. Once the interface is on the net-
work, it periodically sends out test packets to ensure it is still functioning properly.
If the test fails, the router removes the interface from the network and runs the
self-test to ensure integrity. If a failure occurs during auto-test, the router declares
the network down. If the self-test is successful, the router declares the network up.
Up The interface is operational and connected.
Down The interface is not operational and has failed an auto-test. The router continues
to carry out the test over the network at increasing intervals, beginning at five
seconds, until the router stops testing said interface (approximately two minutes).
Disabled Shutdown configuration command has disabled the interface.

Configuration and Monitoring 95

3 Router Monitoring Teldat SA

Not present Either there is no interface present in the router, or the console is incorrectly con-
figured.
Unsupported The current release/license does not support the interface hardware.
Available State of the secondary interface in a WAN configuration when the main one is act-
ive.
Error Disabled. An error has been detected and the interface has been disabled.

The eighth block – SNMP OperStatus – displays a list on the interface operating status (from the SNMP protocol
point of view, defined in RFC 2233). The meaning of each field is as follows:
Interface Interface name.
OperStatus Possible SNMP operating states are as follows:
Up Interface is ready to transmit and receive network traffic.
Down Interface is not operative.
Testing Interface is executing a test; real traffic packets cannot be transmitted.
Unknown Interface operating status cannot be determined for unknown reasons.
Dormant Interface is operating, but waiting for an external event to begin sending or receiv-
ing packets. It presumably passes to ‘Up’ once the expected event occurs. For ex-
ample: when dial interfaces do not have any traffic to send (have not initiated a
call) or, when only incoming calls are permitted and the remote end has not initi-
ated connection.
Not present This state is a refinement of ‘Down’. This indicates the interface is down, specific-
ally due to the lack of a component (often hardware).
Lower layer This is another refinement of ‘Down’, which indicates the interface has been as-
down sembled on top of one or more interfaces and one of the latter is down.

The ninth block displays information on versions for encryption cards and cellular and wireless LAN drivers.

3.2.5 DEVICE
Displays statistical information on network interfaces such as Ethernet, Token Ring etc. This command is used to ob-
tain a summary report on all interfaces, or to obtain detailed information on a specific interface.

Syntax:

+device [<interface>]

• < interface > name of the interface you wish information on.

If you do not enter the interface name, generic information on all interfaces is displayed.

Example 1:

+device
Auto-test Auto-test Maintenance
Interface CSR Vect valids failures failures
ethernet0/0 fa200e00 27 1 0 0
serial0/0 fa200a00 5E 0 156 0
serial0/1 fa200a20 5D 0 156 0
serial0/2 fa200a60 5B 0 7 0
bri0/0 fa200a40 5C 1 0 0
x25-node 0 0 1 0 0
+

Example 2:

+device ethernet0/0
Auto-test Auto-test Maintenance
Interface CSR Vect valids failures failures
ethernet0/0 fa200e00 27 1 0 0

Physical address: 00A0267001E8

PROM address: 00A0267001E8
Speed: 10 Mbps

Input statistics:
failed, frame too long 0 failed, FCS error 0
failed, alignment error 0 failed, FIFO overrun 1

96 Configuration and Monitoring

Teldat SA 3 Router Monitoring

internal MAC rcv error 1 packets missed 1

Output statistics:
deferred transmission 0 single collision 0
multiple collisions 0 total collisions 0
failed, excess collisions 0 failed, FIFO underrun 0
failed, carrier sense err 0 SQE test error 0
late collision 0 internal MAC trans errors 0
Ethernet MAC code release 1
+

The meaning of each field is as follows:

Interface Interface name.
CSR Command and Status Register address.
Vect Interruption vector.
Auto Test Val- Number of times the auto-test succeeded (interface state changes from “down” to “up”).
ids
Auto-Test Number of times the auto-test failed (interface state changes from “up” to “down”).
Failures
Number of maintenance failures.
Maintenance
Failures

The fields subsequently appearing, depend on the type of interface selected. These have self-explanatory names for
the information they display.

Note

The screen display can vary depending on the router and device.

3.2.6 ERROR
Displays error statistics for the segmented network for various interfaces available in the device. This command
provides error counters.

Syntax:

+error

Example:

+error
Input Input Input Input Output Output
Interface Discards Errors Unk Proto Flow Drop Discards Errors
ethernet0/0 0 0 1016 0 0 0
serial0/0 0 0 0 0 0 0
serial0/1 0 0 0 0 0 0
serial0/2 0 0 0 0 0 0
bri0/0 0 0 0 0 0 0
x25-node 0 0 0 0 0 0
+

The meaning of each of the fields is as follows:

Interface Interface name.
Input Discards Number of packets discarded by flow control at reception.
Input Errors Number of packets found to be defective at data link.
Input Unk Proto Number of packets received for an unknown protocol.
Input Flow Drop Number of received packets subsequently dropped by flow control at reception.
Output Discards Number of packets dropped by flow control at transmission.
Output Errors Number of output errors, such as attempts to send over a down network, or over a
network that went down during transmission.

The sum between all “Input Flow Drop” and “Output Discards” interfaces is not the same. This is because “Output
Discards” may contain locally generated packets.

Configuration and Monitoring 97

3 Router Monitoring Teldat SA

3.2.7 EVENT
Use this command to enter the Event Logging System (ELS+) prompt. Here you can temporally create filters for mes-
sages with the aim of solving problems. All changes carried out at the ELS+ prompt are immediate, however these
disappear when the router is re-started. For further information please see Event Logging System ELS on page 135.
To return to the + prompt, enter the exit command.

Syntax:

+event

Example:

+event
-- ELS Monitor --
ELS+

3.2.8 FEATURE
This provides access to the features monitoring menu, which are neither network protocols nor interfaces. Enter ?
after feature to get a list of features available for your software version.

Through this command, enter the corresponding feature monitoring. For further information please see the corres-
ponding manual.

Note

Said feature must be enabled at the configuration prompt before you can monitor it.

Syntax:

+feature <option>
access-lists Generic IP lists monitoring
afs Advanced firewall system feature
bandwidth-reservation Bandwidth-Reservation System feature monitoring
dns DNS monitoring environment
dns-updater DNS UPDATER monitoring enviroment
err-disable Error disable monitoring
gps-applications GPS Applications monitoring
hotspot Hotspot monitoring enviroment
http HTTP server monitoring
ip-discovery Ip-discovery monitoring
ipv6-access-list IPv6 access list monitor
istud IPSEC Tunnel Server Discovery Protocol monitoring
ldap LDAP (Lightweight Directory Access Protocol)
monitoring
mac-filtering MAC-Filtering feature monitoring
management Management Monitoring
management-platform Management Platform monitoring
netflow Netflow client monitoring
nsla NSLA (Network Service Level Advisor) monitoring
nsm NSM (Network Service Monitor) monitoring
ntp NTP (Network Time Protocol) monitoring
policy-map Policy map monitoring
power-switch TeleControl Module control environment
prefix-lists Prefix lists monitoring
radius RADIUS feature monitoring
rmon RMON (Remote Network Monitoring)
scada-forwarder Scada protocol monitoring
spi SPI agent monitoring
stun Stun protocol monitoring
syslog Syslog client monitoring
tftp Access the device#s TFTP client.
ttcp Ttcp (test tcp)
vli Virtual Linux Interface monitoring
wnms Wireless Network Management System monitoring
wrr-backup-wan WAN Reroute feature monitoring

98 Configuration and Monitoring

Teldat SA 3 Router Monitoring

• < option > specifies the type of information you wish to display.

3.2.8.1 FEATURE ACCESS-LISTS

Use this command to enter generic IP lists monitoring.

Syntax:

+feature access-lists

Example:

+feature access-lists
-- Access Lists user console --
Access Lists+

For further information on generic access list monitoring, please see manual Teldat Dm752-I Access Control.

3.2.8.2 FEATURE AFS

Use this command to enter the AFS monitoring.

Syntax:

+feature afs

Example:

+feature afs
-- AFS Monitor --
AFS+

For further information, please see manual Teldat Dm786-I AFS.

3.2.8.3 FEATURE BANDWIDTH-RESERVATION

Use this command to enter Bandwidth-Reservation System feature monitoring. For further information please see
manual Teldat Dm715-I Bandwidth Reservation System .

System:

+feature bandwidth-reservation

Example:

+feature bandwidth-reservation
-- Bandwidth Reservation console --
BRS+

3.2.8.4 FEATURE DNS

Accesses the DNS monitoring environment. For further information please see manual Teldat Dm723-I DNS Client .

Syntax:

+feature dns

Example:

+feature dns
-- DNS resolver user console --
DNS+

3.2.8.5 FEATURE DNS-UPDATER

Use this command to enter dns-updater monitoring.

Syntax:

+feature dns-updater

Example:

Configuration and Monitoring 99

3 Router Monitoring Teldat SA

+feature dns-updater
-- DNS Updater console --
DNS Updater

For further information, please see manual Teldat Dm785-I DNS Updater.

3.2.8.6 FEATURE ERR-DISABLE

Use this command to enter err-disable monitoring.

Syntax:

+feature err-disable

Example:

+feature err-disable
-- Error Disable user console --
errdisable+

3.2.8.7 FEATURE GPS-APPLICATIONS

Use this command to enter gps-applications monitoring.

Syntax:

+feature gps-applications

Example:

+feature gps-applications
-- GPS Applications user console --
GPS Apps+

For further information on gps-applications monitoring, please see manual Teldat Dm812-I GPS.

3.2.8.8 FEATURE HOTSPOT

Use this command to access the HotSpot feature monitoring menu. Please see Dm 820-I HotSpot Feature for further
information.

Syntax:

+feature hotspot

Example:

+feature hotspot

-- Hotspot User Console --

HS+

Command history:

Release Modification
11.00.03 New command added.

3.2.8.9 FEATURE HTTP

Accesses HTTP protocol monitoring. For further information, please see manual Teldat Dm737-I HTTP Protocol.

Syntax:

+feature http

Example:

+feature http
-- HTTP server user console --
HTTP+

100 Configuration and Monitoring

Teldat SA 3 Router Monitoring

3.2.8.10 FEATURE IP-DISCOVERY

Use this command to enter feature ip-discovery monitoring. This command or feature depends on the device i.e. it
may not apply to your device.

Syntax:

+feature ip-discovery

Example:

+feature ip-discovery
-- TIDP Console --
TIDP+

3.2.8.11 FEATURE IPV6-ACCESS-LIST

Use this command to enter ipv6-access-list monitoring.

Syntax:

+feature ipv6-access-list

Example:

+feature ipv6-access-list
-- IPv6 Access Lists user console --
IPv6 Access Lists+

For further information, please see manual Teldat Dm808-I IPv6 Access Control.

3.2.8.12 FEATURE ISTUD

Use this command to enter istud monitoring.

Syntax:

+feature istud

Example:

+feature istud
-- ISTUD console --
ISTUD+

For further information, please see manual Teldat Dm784-I ISTUD Feature.

3.2.8.13 FEATURE LDAP

Use this command to enter LDAP protocol (Lightweight Directory Access Protocol) monitoring.

Syntax:

+feature ldap

Example:

+feature ldap
LDAP client monitor
LDAP+

3.2.8.14 FEATURE MAC-FILTERING

Use this command to enter mac-filtering feature monitoring.

Syntax:

+feature mac-filtering

Example:

+feature mac-filtering
-- MAC Filtering user console --

Configuration and Monitoring 101

3 Router Monitoring Teldat SA

Filter+

3.2.8.15 FEATURE MANAGEMENT

Use this command to enter management feature monitoring.

Syntax:

+feature management

Example:

+feature management
-- Management Console --
management+

Command history:
Release Modification
11.00.05 FEATURE MANAGEMENT menu was introduced as of version 11.00.05.
11.01.00 FEATURE MANAGEMENT menu was introduced as of version 11.01.00.

3.2.8.15.1 SCRIPT <id_script>

Use this command to execute the commands configured on the script.

Syntax:

management+script <id_script>

Example:

management+script 1
Starting executing Script 1
Sending command: p 4
Response: *
Response: Config>
Response: *
Command p 4 sent without errors
management+

Command history:
Release Modification
11.00.05 script <id_script> command was introduced as of version 11.00.05.
11.01.00 script <id_script> command was introduced as of version 11.01.00.

3.2.8.15.2 STATISTICS

Use this command to list all operations associated to advisor notifications and information such as, the times they
have been executed, the last time each operation was executed and if any errors were produced during execution.

Syntax:

management+statistics

Example:

management+statistics

Management Operation Statistics

----------------------------------------------------------------------

----------------------------------------------------------------------

ID Count Last Start Time Errors Name

----------------------------------------------------------------------

2 1 2016-02-05 16:08:47 0 lte-up

3 2 2016-02-05 16:09:00 0 lte-down

102 Configuration and Monitoring

Teldat SA 3 Router Monitoring

4 2 2016-02-05 16:09:00 0 ip-config

5 0 1970-01-01 00:00:00 0 prueba

6 0 1970-01-01 00:00:00 0

Command history:
Release Modification
11.00.05 statistics command was introduced as of version 11.00.05.
11.01.00 statistics command was introduced as of version 11.01.00.

3.2.8.16 FEATURE NETFLOW

Use this command to enter netflow monitoring.

Syntax:

+feature netflow

Example:

+feature netflow
NETFLOW Monitor
NETFLOW Mon+

For further information, please see manual Teldat Dm789-I NETFLOW.

3.2.8.17 FEATURE NSLA

Use this command to enter NSLA feature (Network Service Level Advisor) monitoring.

Syntax:

+feature nsla

Example:

+feature nsla
-- NSLA console --
NSLA+

For further information please see manual Teldat Dm754-I NSLA (Network Service Level Advisor) .

3.2.8.18 FEATURE NSM

Use this command to enter NSM feature (Network Service Monitor) monitoring.

Syntax:

+feature nsm

Example:

+feature nsm
-- NSM console --
NSM+

For further information please see manual Teldat Dm749-I NSM (Network Service Monitor) .

3.2.8.19 FEATURE NTP

Accesses the NTP (Network Time Protocol) monitoring environment. For further information, please see manual
Teldat Dm728-I NTP Protocol .

Syntax:

+feature ntp

Example:

+feature ntp

Configuration and Monitoring 103

3 Router Monitoring Teldat SA

-- NTP user console --

NTP+

3.2.8.20 FEATURE POLICY-MAP

Use this command to enter policy-map monitoring.

Syntax:

+feature policy-map

Example:

+feature policy-map
-- Policy Map user console --
Policy-Map+

For further information, please see manual Teldat-Dm795-I Policy map Class map.

3.2.8.21 FEATURE POWER-SWITCH

Use this command to access device Telecontrol Module control environment. This environment is only accessible to
the user via telnet, and its use only affects devices connected to a power source through an MTC+ or MTC.

Syntax:

+feature power-switch

Example:

+feature power-switch
POWER-SWITCH monitor
POWER-SWITCH+

For further information please see manuals: Teldat Dm296-I Telecontrol Module (MTC) or Teldat Dm689-MTC+
(MTC+).

3.2.8.22 FEATURE PREFIX-LISTS

Use this command to enter prefix lists monitoring.

Syntax:

+feature prefix-lists

Example:

+feature prefix-lists
-- Prefix Lists user console --
Prefix Lists+

For further information, please see manual Teldat-Dm780-I Prefix Lists.

3.2.8.23 FEATURE RADIUS

Use this command to enter RADIUS feature monitoring. For further information, please see manual Teldat Dm733-I
RADIUS Protocol.

Syntax:

+feature radius

Example:

+feature radius
-- RADIUS user console --
RADIUS+

3.2.8.24 FEATURE RMON

Use this command to enter rmon monitoring.

Syntax:

104 Configuration and Monitoring

Teldat SA 3 Router Monitoring

+feature rmon

Example:

+feature rmon
-- RMON (Remote Network Monitoring) console --
RMON+

For further information, please see manual Teldat Dm796-I RMON Feature.

3.2.8.25 FEATURE SCADA-FORWARDER

Use this command to enter SCADA forwarder monitoring.

Syntax:

+feature scada-forwarder

Example:

+feature scada-forwarder
SCADA Forwarder Console
SCADA FWD+

3.2.8.26 FEATURE SPI

Use this command to enter spi monitoring.

Syntax:

+feature spi

Example:

+feature spi
-- SPI Agent user console --
SPI+

For further information, please see manual Teldat Dm793-I SPI Agent.

3.2.8.27 FEATURE STUN

Accesses STUN client monitoring environment. For further information, please see manual Teldat Dm769-I STUN
Protocol.

Syntax:

+feature stun client

Example:

+feature stun client

STUN Client Monitor
STUN Client Mon+

3.2.8.28 FEATURE SYSLOG

Use this command to enter feature Syslog client monitoring.

Syntax:

+feature syslog

Example:

+feature syslog
-- SYSLOG client console --
SYSLOG+

For further information please see manual Teldat Dm753-I Client syslog .

Configuration and Monitoring 105

3 Router Monitoring Teldat SA

3.2.8.29 FEATURE TFTP

Use this command to enter feature tftp monitoring.

Syntax:

+feature tftp

Example:

+feature tftp
TFTP manager
TFTP+

For further information, please see manual Teldat Dm765-I TFTP Protocol.

3.2.8.30 FEATURE TTCP

Use this command to enter a menu to carry out tests on ttcp traffic loading.

3.2.8.31 FEATURE VLI

Use this command to enter vli monitoring.

Syntax:

+feature vli

Example:

+feature vli
-- VLI monitor --
vli+

For further information, please see manual Teldat Dm803-I Virtual Linux Interface VLI.

3.2.8.32 FEATURE WNMS

Accesses WNMS (Wireless Network Management System) feature monitoring. For further information, please see
manual Teldat Dm819-I Wireless Network Management System .

Syntax:

+feature wnms

Example:

+feature wnms
-- WNMS Console --
WNMS+

Command history:

Release Modification
11.00.03 New command added.

3.2.8.33 FEATURE WRR-BACKUP-WAN

Use this command to enter WRR-Backup WAN feature monitoring. For further information please see manual Teldat
Dm727-I Backup WAN Reroute .

Syntax:

+feature wrr-backup-wan

Example:

+feature wrr-backup-wan
-- Back-up WAN Reroute user console --
WRR+

106 Configuration and Monitoring

Teldat SA 3 Router Monitoring

3.2.9 LAST-CONFIG-CHANGES
Use this command to monitor the latest configuration recordings. The first row is the latest configuration the device
has stored. This is the active one provided no other configuration change has been produced after re-starting the
device. If a change has been made, the active configuration is in the second information register. The first informa-
tion register is modified each time the configuration is saved without restarting the device.

Syntax:

+last-config-changes

Example:

+last-config-changes
Last configuration changes
-------------------------------------------------------------------------------
File Acc-Type Address User Date/Time
-------------------------------------------------------------------------------
SAMP1.CFG Console 0.0.0.0 CONSOLE 03/03/05 10:40:29
TFTP.CFG Console 0.0.0.0 usersample 02/28/05 13:37:02
TFTP.CFG Telnet 172.24.51.128 TELNET 02/24/05 15:29:40
TFTP.CFG Telnet 172.24.51.128 TELNET 02/24/05 15:24:21
IGMP.CFG Console 0.0.0.0 usersample 02/24/05 13:45:33
TFTP.CFG Console 0.0.0.0 usersample 02/24/05 11:56:51
TFTP.CFG Console 0.0.0.0 CONSOLE 02/24/05 11:54:51
IGMP.CFG Console 0.0.0.0 usersample 02/23/05 19:34:36
IGMP.CFG Console 0.0.0.0 CONSOLE 02/22/05 17:20:45
+

The meaning of the fields is as follows:

File Name of active recorded file.
Acc-Type Type of access (telnet, console) used to modify the configuration.
Address IP address used for the access. This field value is 0.0.0.0 if you access through the device console.
User User who carried out the configuration modification. If there are no defined users in the device, the
type of access appears in this field.
Date/Time Time and date these changes were executed.

3.2.10 LAST-APP-VERSION-CHANGES
Command history:

Release Modification
11.00.05 This command was introduced as of version 11.00.05.

Use this command to monitor the latest CIT version upgrades. The first row shows the latest update the device has.
Only the latest 15 upgrades are stored.

Syntax:

+last-app-version-changes

Example:

+last-app-version-changes

Last Application version changes

---------------------------------------------------
VERSION Date/Time
---------------------------------------------------
11.00.05-Beta-9ed5700 04/11/16 17:41:30
11.00.05-Beta-1e55c42 03/29/16 12:23:41
11.00.05-Beta-2d75a03 03/27/16 08:01:05
11.00.05-Beta-e853dde 03/20/16 21:15:42
11.00.05-Beta-9393dab 02/27/16 00:01:49
+

The meaning of the fields is as follows:

Configuration and Monitoring 107

3 Router Monitoring Teldat SA

VERSION
Date/Time Time and date this version was loaded by the device.

3.2.11 LIST CURRENT-DEVICES

Lists information on available/configured interfaces in the device.

Syntax:

+list current-devices

Example:

+list current-devices
Interface Connector Type of interface
ethernet0/0 GE0/FE0/LAN1 Fast Ethernet interface
ethernet0/1 GE1/FE1/LAN2 Fast Ethernet interface
bri0/0 BRI/ISDN1 ISDN Basic Rate Int
x25-node --- Router->Node
+

Command history:

Release Modification
10.08.34.05.12 This command option was introduced as of version 10.08.34.05.12.
11.00.05 This command option was introduced as of version 11.00.05.
11.01.01 This command option was introduced as of version 11.01.01.

3.2.12 MALLOC-MONITOR
Use this command to monitor the internal system of the device memory management. Through command options,
you can control the diagnosis systems for system memory administration. The use of this command requires in-depth
knowledge of the Teldat Routers software and hardware architecture and should only be used when expressly indic-
ated by Teldat personnel.

Syntax:

+malloc-monitor <option>
DISABLE
ENABLE
ASSIGNED-MEMORY-BLOCKS
LIST
SHOW-FLAGS
ALL-REQUESTS
IGNORE-START-REQUESTS-FLAG
NEWEST-REQUESTS-FLAG (less than a minute age)
OLDEST-REQUESTS-FLAG (more than a minute age)
START-RECORD
STOP-RECORD
GET-MEMORY
VIEW-MEMORY
FREE-MEMORY

• < option > specifies the action to carry out.

3.2.13 MANAGEMENT
Enters the master router monitoring environment.

Syntax:

+management

Example:

+management
-- Routers management user console--
MANAGEMENT+

108 Configuration and Monitoring

Teldat SA 3 Router Monitoring

3.2.14 MEMORY
This command displays information relative to the different types of memory available in the device.

Information displayed on executing the command is divided into different blocks.

The first, SYSTEM MEMORY, shows an overview, highlighting how the system has assigned RAM memory. These
values are set when the router starts and do not change during operation.

Next, the SYSTEM MEMORY is shown:

• Total : total RAM installed in the equipment.

• Dynamically managed: size of memory dedicated to support running processes.
• Code: fixed memory size, which is loaded with the system code.
• Caches: status of memory cache devices.

In the second block, information on the HEAP memory is displayed. Data displayed in this block is subdivided in
four extra sub-blocks, separated by a blank line, providing a snapshot of the HEAP status. The first sub-block sum-
marizes the current use of the HEAP; the second sub-block lists currently existing chunks (a size smaller than block
size); the third sub-block provides information on chunks one size bigger than the block size. Their statistics are
stored in registers, which are labeled by an arithmetic progression, based on their chunk size; the forth sub-block
provides information on chunks one size bigger than those displayed in the previous sub-block. Statics on the latter
are stored in registers, labeled with a geometric progression, based on their chunk size.

The first sub-block of HEAP shows the following fields:

• Total : amount of memory assigned to the HEAP, including internal system data.
• Usable: maximum amount of memory the HEAP can allocate to support running processes.
• Free: free memory in HEAP.
• Block size: the heap is divided in bocks of n size.

The second sub-block of HEAP displays data as follows:

64 bytes chunks: 7104 ( 454656 bytes) total, 10 ( 640 bytes) free

Chunk usage: 99.00%

The meaning of each column is as follows:

• Size of registered chunk.

• Total number of assigned chunks of this size in HEAP.
• Total number of assigned bytes for this chunk size in HEAP.
• Total number of free chunks of this size in HEAP.
• Total number of bytes of free chunks of this size in HEAP.

Chunk usage is a global measurement used for currently assigned chunks smaller than block size.

In this second sub-block, the number of assigned chunks, for a given size, is allocated as needed by taking memory
space from chunks displayed in next sub-blocks. The more chunks in this sub-block the less size for chunks in the
next sub-blocks.

The third and fourth sub-blocks of HEAP display data as follows:

12288 bytes chunks: 85 ( 1044480 bytes) used ( 85 max), 0 ( 0 bytes) free

16822272 bytes chunks: 2 ( 54730752 bytes) used ( 2 max), 0 ( 0 bytes) free

The meaning of each column is as follows:

• Size of registered chunk.

• Total number of assigned chunks of this size in HEAP.
• Total number of assigned bytes for this chunk size in HEAP.
• Maximum number of assigned chunks of this size that has been allocated concurrently in HEAP.
• Total number of free chunks of this size in HEAP.
• Total number of bytes of free chunks of this size in HEAP.

As already said, it is important to know that statistics for chunk sizes in the third sub-block are registered in an arith-
metical progression, while in the fourth sub-block they are stored geometrically. This means that in the third sub-
block, the number of assigned bytes for a chunk size is calculated by multiplying the chunk size by the number of

Configuration and Monitoring 109

3 Router Monitoring Teldat SA

chunks, and this does not match the fourth sub-block.

Size chunks for registers in third sub-block are separated by block size. The first line in the example is interpreted as
follows: in the register for chunk sizes of 12288 bytes, there are 85 allocated chunks with a total size of 1044480
bytes. The maximum number of chunks concurrently assigned for this register is 85 and there are no free chunks of
12288 bytes to be stored in this register.

Size chunks for registers in the fourth sub-block are separated by a multiple of block size, resulting in the evolution of
registered chunk sizes in a geometrical progression form. Here, each register shares statistics between different
chunk sizes; this is what happens in the second line of the previous example. This line is interpreted as follows: in
the register for chunk sizes between 16822272 bytes and the next registered chunk size, there are two allocated
chunks with a total size of 54730752 bytes. The maximum number of chunks concurrently assigned for this register
is two and there are no free chunks with said size to be stored in this register.

Depending on the equipment, statistics relative to different chunk sizes are not available, global information on used
and free chunks are displayed instead.

In the third block, information relative to the memory POOL1 is displayed. POOL1 is an area of memory reserved
for messages and buffers from the node in fixed size partitions.

The following information is displayed for POOL1:

• Sz: total size of the POOL in bytes.

• AllocPart: number of partitions in use.
• AvlPart : number of available partitions.

In the fourth block, the parameters relevant to:

• Flash memory: system flash memory measured in bytes.

• Free global Buffers : number of public buffers available in the system. The minimum number of available public buf-
fers reached is displayed between brackets.
• Orphan data buffers : number of data buffers available to be assigned to a global buffer. These are known as
orphan as they have not as yet been assigned.
• Spurious INT 47: spurious interruption counter in the system.

Syntax:

+memory

Example:

+memory

SYSTEM MEMORY:
Total 536870912
Dynamically managed 502296576
Code 34574336
Caches ON Write Back

HEAP:
total 502296576
usable 501772288
free 377067688
block size 4096

8 bytes chunks: 39936 ( 319488 bytes) total, 345 ( 2760 bytes) free
16 bytes chunks: 5888 ( 94208 bytes) total, 244 ( 3904 bytes) free
32 bytes chunks: 35072 ( 1122304 bytes) total, 105 ( 3360 bytes) free
64 bytes chunks: 7168 ( 458752 bytes) total, 24 ( 1536 bytes) free
128 bytes chunks: 544 ( 69632 bytes) total, 11 ( 1408 bytes) free
256 bytes chunks: 80 ( 20480 bytes) total, 4 ( 1024 bytes) free
512 bytes chunks: 28968 ( 14831616 bytes) total, 1 ( 512 bytes) free
1024 bytes chunks: 56 ( 57344 bytes) total, 0 ( 0 bytes) free
2048 bytes chunks: 36934 ( 75640832 bytes) total, 0 ( 0 bytes) free
Chunk usage: 99.00%

4096 bytes chunks: 22638 ( 92725248 bytes) used ( 22638 max), 0 ( 0 bytes) free
8192 bytes chunks: 28 ( 229376 bytes) used ( 28 max), 0 ( 0 bytes) free
12288 bytes chunks: 85 ( 1044480 bytes) used ( 85 max), 0 ( 0 bytes) free
16384 bytes chunks: 45 ( 737280 bytes) used ( 45 max), 0 ( 0 bytes) free

110 Configuration and Monitoring

Teldat SA 3 Router Monitoring

20480 bytes chunks: 10 ( 204800 bytes) used ( 10 max), 0 ( 0 bytes) free

24576 bytes chunks: 1 ( 24576 bytes) used ( 1 max), 0 ( 0 bytes) free
32768 bytes chunks: 1 ( 32768 bytes) used ( 1 max), 0 ( 0 bytes) free
36864 bytes chunks: 13 ( 479232 bytes) used ( 13 max), 0 ( 0 bytes) free

61440 bytes chunks: 5 ( 331776 bytes) used ( 5 max), 0 ( 0 bytes) free

110592 bytes chunks: 1 ( 151552 bytes) used ( 1 max), 0 ( 0 bytes) free
176128 bytes chunks: 2 ( 503808 bytes) used ( 2 max), 0 ( 0 bytes) free
307200 bytes chunks: 1 ( 524288 bytes) used ( 1 max), 0 ( 0 bytes) free
16822272 bytes chunks: 1 ( 27729920 bytes) used ( 1 max), 0 ( 0 bytes) free
67153920 bytes chunks: 0 ( 0 bytes) used ( 1 max), 0 ( 0 bytes) free
268480512 bytes chunks: 0 ( 0 bytes) used ( 0 max), 1 ( 377053184 bytes) free

POOLS:
POOL1 Sz:9631710 AllocPart:1 AvlPart:27917

Flash Memory: 67108864

Free global Buffers:36261 (36258)

Orphan Data Buffers(maximum reached):36261 (36873)

Spurious INT 47: 0

+

Important

The appearance of the data resulting from this command depends on the device model.

3.2.15 NETWORK
Displays the monitoring prompt for the specified network interface, such as the Frame Relay, PPP, X.25 network etc.
Statistical information can be displayed from said prompt.

Syntax:

+network <interface>

• < interface > name of the network interface whose monitoring environment you wish to access.

Enter device at the + prompt to see the networks the router is configured for.

Example:

+device
Auto-test Auto-test Maintenance
Interface CSR Vect valids failures failures
ethernet0/0 fa200e00 27 1 0 0
serial0/0 fa200a00 5E 0 373 0
serial0/1 fa200a20 5D 0 373 0
serial0/2 fa200a60 5B 0 10 0
bri0/0 fa200a40 5C 1 0 0
x25-node 0 0 1 0 0
+network serial0/0

-- Frame Relay Console --

serial0/0 FR+

For further information, please see the manual associated to the specified network interface for the monitoring envir-
onment you wish to access.

3.2.16 NODE commands

Accesses the node monitoring (X.25, XOT and 270).

Syntax:

+node <name>

Configuration and Monitoring 111

3 Router Monitoring Teldat SA

X25
XOT
270

• < name > name of the node for the monitoring menu you wish to access.

3.2.16.1 NODE X25

Accesses node monitoring relative to X.25. The parameters relative to a port can be configured in the network for
said port (+network port command).

Syntax:

+node x25

Example:

+node x25
-- X25 Monitor --
X25+

For further information, please see manual Teldat Dm707-I X.25.

3.2.16.2 NODE 270

Accesses node monitoring relative to 270. You can also access from the 270 network (+ network port command).

Syntax:

+node 270

Example:

+node 270
270 Monitoring
270>

3.2.17 PROTOCOL
Use this command to enter the commands environment for the protocols' software installed in the router. The pro-
tocol command followed by the desired protocol number, or short name, accesses a protocol command environ-
ment. After entering this command, the specified protocol prompt appears. From this prompt, enter the specific com-
mands for said protocol.

To enter a protocol command environment:

(1) Enter protocol ? for a list of protocols configured in your router.
(2) Enter the name of the required protocol. The specified protocol prompt immediately appears. From this prompt,
enter the specific commands for said protocol.
(3) Enter exit to return to the + prompt.

Syntax:

+protocol <identifier>

• < identifier > protocol identifier name whose monitoring menu you wish to access.

Example:

+protocol ?
arp Access ARP protocol
asrt Access ASRT protocol
bfd Access BFD protocol
bgp Access BGP protocol
dhcp Access DHCP protocol
dhcpv6 Access DHCPv6 protocol
dls Access DLS protocol
dot1x Access 802.1X protocol
gw104 Access GW-104 protocol
h323 Access H323 protocol
igmp Access IGMP protocol
ip Access IP protocol
ipv6 Access IPv6 protocol

112 Configuration and Monitoring

Teldat SA 3 Router Monitoring

l2tp Access L2TP protocol

mgcp Access MGCP protocol
nhrp Access NHRP protocol
noe Access NOE protocol
ospf Access OSPF protocol
pim Access PIM protocol
rip Access RIP protocol
ripng Access RIPNG protocol
sccp Access SCCP protocol
sip Access SIP protocol
snmp Access SNMP protocol
+protocol ip
-- IP protocol monitor --
IP+

3.2.18 QUEUE
Displays statistics on the length of input and output queues in the specified interfaces. Information provided by the
queue command includes:

• The total number of buffers allocated.

• The maximum number of buffers processed in the burst.
• The low-level buffer value.
• The number of buffers currently active in the interface.
• The maximum or minimum number of buffers in the interface.

Syntax:

+queue <interface>

• < interface > name of the network interface whose monitoring environment you wish to access.

If you do not specify the interface, information on all interfaces available in the device is displayed.

Example:

+queue
Input Queue Output Queue
Interface Alloc Burst Low Curr Min Cur.Req Max.Req Fair Current Max
ethernet0/0 256 16 5 256 256 256 257 246 0 0
ethernet0/1 256 16 5 256 0 256 256 246 0 0
x25-node 0 --- 0 100 0 0 0 40 0 0
ethernet1/0 40 16 5 40 40 40 41 40 0 0
+

The meaning of each field is as follows:

Interface Interface name.

• Input Queue
Alloc Number of buffers allocated to this device.
Burst Maximum number of buffers processed in the burst. Where there is overload, various buffers are
processed in burst to increase performance and consequently reach maximum speed. This inform-
ation is only available for certain interfaces.
Low Water mark for flow control in this device.
Curr Current number of buffers in this device. Value is 0 if the device is disabled.
Min Minimum number of buffers in the input queue for this device.
Cur.Req Number of buffers currently used to receive through this interface. This is the sum of the buffers
ready to receive and the buffers used to receive, which are presently being processed by the
router.
Max.Req Maximum number of buffers used to receive through the interface.

• Output Queue
Fair Fair level for the output queue in this device.
Current Number of packets currently waiting to be transmitted in this device.
Max Maximum number of buffers in the output queue for this device.

Configuration and Monitoring 113

3 Router Monitoring Teldat SA

The router attempts to keep at least the Low value packets available for receiving over an interface. If the router re-
ceives a packet and the value of Curr is less than Low, then the packet is subject to flow control. If a buffer subject to
flow control is on this device and the Curr level is greater than Fair, the router drops the buffer instead of queuing it.
The error command displays the dropped buffer in its Output Discards column. It also generates ELS event GW.036
or GW.057.

3.2.19 QUICK
To access the quick monitoring menu, first access the general monitoring menu and from there enter quick.

Syntax:

+quick

Example:

+quick
Quick Monitor Menu
Quick Monitor+

Command history:

Release Modification
11.00.02 This command is obsolete as of version 11.00.02. Quick menu configuration is no longer
supported.

3.2.20 RUSH-ENGINE
Displays statistical information on the Rush engine and existing flows on each interface.

Syntax:

+rush-engine ?
all Monitor all interfaces
interface Monitor interface information
state Display Rush Engine state
+

Command history:

Release Modification
11.01.00 This command was introduced as of version 11.01.00.

3.2.20.1 RUSH-ENGINE ALL

Display statistics for all interfaces. It is possible to specify a filter to display only those flows that match the filter.

This command also allows you to clear the current counters and remove all flows from the Rush engine.

Syntax:

+rush-engine all [<filter> | clear | flush]

<filter>:
ipv4 [destination-address <dstaddr>]
[source-address <srcaddr>]
[address <addr>]
protocol {tcp [destination-port <dstport>] [source-port <srcport>] [port <port>] |
udp [destination-port <dstport>] [source-port <srcport>] [port <port>] |
gre}
+
ipv4 Only selects IPv4 protocol flows.
destination-address Only selects flows with a destination address equal to the one
referenced.
source-address Only selects flows with a source address equal to the one refer-
enced.
address Only selects flows with a source or destination address equal to
the one referenced.

114 Configuration and Monitoring

Teldat SA 3 Router Monitoring

protocol Only selects flows for the referenced protocol.

tcp Only selects flows for TCP protocol.
udp Only selects flows for UDP protocol.
destination-port Destination port for TCP or UDP flows.
source-port Source port for TCP or UDP flows.
port Source or destination port for TCP or UDP flows.
gre Only selects flows for GRE protocol.

Example:

Lists TCP flows in all interfaces.

+rush all protocol tcp

Rush Engine is Enabled

Idle flow timeout 5

Memory sizes: RBD 20, Ifc 15944, Flow 204, Flow add 144, Max flows 2644

Rush Ifc ethernet0/0:

active flows 4/9 hash collissions 0/0
in packets 72 in bytes 51076
out packets 53 out bytes 10533
stats cleared 0 times
Active flows details:
key 0da0 age 0 TCP 64.233.184.188:5228 -> 192.168.212.245:52791 tos 0/0 mtu 1500 prcs 0 NAT stats 7/924
key 0ca4 age 6000 TCP 173.192.222.189:443 -> 192.168.212.245:36265 tos 0/0 mtu 1500 prcs 0 NAT stats 6/663
key 03cf age 10000 TCP 216.58.211.238:443 -> 192.168.212.245:46999 tos 0/0 mtu 1500 prcs 0 NAT stats 15/6028
key 0631 age 8000 TCP 216.58.211.238:443 -> 192.168.212.245:60657 tos 0/0 mtu 1500 prcs 0 NAT stats 50/44250

Rush Ifc wlan0/0:

active flows 4/6 hash collissions 0/0
in packets 53 in bytes 10533
out packets 72 out bytes 51076
stats cleared 0 times
Active flows details:
key 0dac age 0 TCP 192.168.1.31:52791 -> 64.233.184.188:5228 tos 0/0 mtu 1500 prcs 0 NAT stats 4/784
key 0207 age 6000 TCP 192.168.1.31:36265 -> 173.192.222.189:443 tos 0/0 mtu 1500 prcs 0 NAT stats 7/733
key 0e03 age 10000 TCP 192.168.1.31:46999 -> 216.58.211.238:443 tos 0/0 mtu 1500 prcs 0 NAT stats 11/3351
key 0561 age 8000 TCP 192.168.1.31:60657 -> 216.58.211.238:443 tos 0/0 mtu 1500 prcs 0 NAT stats 34/6397
+

3.2.20.2 RUSH-ENGINE INTERFACE

Display statistics for a specific interface. It is possible to specify a filter to display only those flows that match the fil-
ter.

This command also allows you to clear the current counters and remove all flows in the interface from the Rush en-
gine.

Syntax:

+rush-engine interface <interface> [<filter> | clear | flush]

<filter>:
ipv4 [destination-address <dstaddr>]
[source-address <srcaddr>]
[address <addr>]
protocol {tcp [destination-port <dstport>] [source-port <srcport>] [port <port>] |
udp [destination-port <dstport>] [source-port <srcport>] [port <port>] |
gre}
+

ipv4 Only selects IPv4 protocol flows.

destination-address Only selects flows with a destination address equal to the one
referenced.
source-address Only selects flows with a source address equal to the one refer-
enced.

Configuration and Monitoring 115

3 Router Monitoring Teldat SA

address Only selects flows with a source or destination address equal to

the one referenced.
protocol Only selects flows for the referenced protocol.
tcp Only selects flows for TCP protocol.
udp Only selects flows for UDP protocol.
destination-port Destination port for TCP or UDP flows.
source-port Source port for TCP or UDP flows.
port Source or destination port for TCP or UDP flows.
gre Only selects flows for GRE protocol.

Example:

Remove all flows from interface ethernet0/0.

+rush-engine interface ethernet0/0 flush

+

3.2.20.3 RUSH-ENGINE STATE

Display Rush engine state.

Show Rush engine enabled state, current idle flow timeout value and information on the memory used by internal
structures.

Syntax:

+rush-engine state

Rush Engine is Enabled

Idle flow timeout 5

Memory sizes: RBD 20, Ifc 15944, Flow 204, Flow add 144, Max flows 2644
+

3.2.21 STATISTICS
Displays statistical information on the network software, such as networks configured in the router.

Syntax:

+statistics <interface>

• < interface > name of the network interface whose monitoring environment you wish to access.

To view the networks the router has been configured for, enter the command device at the + prompt. If you do not
specify the network interface, information on all networks available in the device is displayed.

Example:

+statistics
Unicast Multicast Bytes Packets Bytes
Interface Pqts Rcv Pqts Rcv Received Transmitted Transmitted
ethernet0/0 0 5384 3090255 0 0
serial0/0 0 0 0 0 0
serial0/1 0 0 0 0 0
serial0/2 0 0 0 0 0
bri0/0 0 0 0 0 0
x25-node 0 0 0 0 0
+

The meaning of the fields is as follows:

Interface Interface name.
Unicast Pkts Rcv Number of non-multicast, non-broadcast addressing, specifically in the sub-level
MAC packets.
Multicast Pkts Rcv Number of multicast or broadcast packets received.
Bytes Received Number of bytes received at the MAC sub-level.
Packets Trans Number transmitted unicast, multicast, or broadcast packets.

116 Configuration and Monitoring

Teldat SA 3 Router Monitoring

Bytes Trans Number of bytes transmitted at the MAC sub-level.

3.2.22 SYSTEM
Allows monitoring for system memory and stacks, CPU use, configuration of console port speed, display firmwares
needed for device operation, activate determined debugging information, show the history of users who have ac-
cessed the device, view open Telnet and SSH sessions and exchange commands or messages between terminals
corresponding to said open sessions.

Syntax:

+system <option>
console-speed Configure the console-serial port speed.
cpu-graph Display a system load measurement graph
cpu-history-48h Display the system load for the last 48 hours
cpu-text Display the average load in the system
dba-debug DBA subsystem debug level
disable-process-monitor Disable CPU load monitoring of processes
enable-process-monitor Enable CPU load monitoring of processes
firmwares-required Display the firmware required
http Display information on the users connected by HTTP
licence Show information about licences in the equipment
login Shows if the difference between upper and lower
case characters is activated
login-historic Display a list containing information on the users
who have accessed the device console
memory Display statistics on the system memory
pcmcia Access the PCMCIA interface status monitoring
power-off-status Display power off timers and ignition status
process-list Display the system processes status
ssh Display information on the users connected by SSH
stack-status Display the system stack status
telnet Display information on the users connected to the
device
telnet-clients Display information on open Telnet sessions to
remote devices
terminal Interchange commands or messages between terminals
usb Access the USB interface status monitoring
+

• < option > specifies the action to take.

3.2.22.1 SYSTEM CONSOLE-SPEED

Allows you to configure the console serial port speed.

Syntax:

+system console <speed>

< speed > speed in bps you wish to set. Permitted values are 9.600, 14.400, 19.200, 38.400, 57.600 and 115.200.

Example:

+system console 9600

+

Default is 9600 bps.

3.2.22.2 SYSTEM CPU-GRAPH

Displays graphic measurement of the system load in percent for the last five minutes. The left hand side shows the
oldest values and the right, the most recent. Each column represents the load during 5 seconds and is displayed
both in graph (a vertical bar of points, which ascends until the corresponding percentage) as well as in numerical
format (written vertically from top to bottom).

Syntax:

+system cpu-graph

Example:

Configuration and Monitoring 117

3 Router Monitoring Teldat SA

+system cpu-graph
CPU usage during the last 5 minutes (%):

211122222211111111111111111111111111111111111111111111111111
100_ 588837877797797777777777777777777777777777777777777777777777
90_|
80_|
70_|
60_|
50_|
40_|
30_|
20_|. ..:...
10_|:::::::::::..:..............................................
0_|::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
5min. 1min. 0

In the above example, you can see that in the last 5 minutes (left hand column) there was a 25 % load (vertical writ-
ing at the top of said column). This load has varied over time (18 % in the following 15 seconds, 23 % in the next 5
seconds, etc) until it established at a current load of 17 % (right hand column).

3.2.22.3 SYSTEM CPU-HISTORY-48H

This command displays a graph showing CPU usage in the system, up to a maximum of 48 hours. From left to right,
the graph shows the oldest time values to the most recent ones. The read values for the CPU load vary, depending
on the time range displayed on the graph horizontal axis. Consequently, a time range of 2 hours displays the maxim-
um CPU usage percentages for each interval of 2 minutes, and a time range of 48 hours displays the maximum per-
centages for each interval of 48 minutes. The numerical percentage values are located on the upper part of the
graph and is read from top to bottom. This command can specify a temporary range in viewing hours in the available
history.

Syntax:

+system cpu-history-48h [<max_hour>] [<min_hour>]

The parameters to configure are:

max_hour Left limit in hours for the horizontal axis range.
min_hour Right limit in hours for the horizontal axis range.

Example 1:

+system cpu-history-48h
CPU usage during the last 48 hours (%):
21
100_ 225222222222222222222222222222229262222222222222222232422222
95_|
90_|
85_|
80_|
75_|
70_|
65_|
60_|
55_|
50_|
45_|
40_|
35_|
30_|
25_|
20_| .
15_| :
10_| ::
5_| :::
0_|..:.............................:::........................
48h. 36h 24h 12h 0h

118 Configuration and Monitoring

Teldat SA 3 Router Monitoring

In this example, entry parameters haven’t been specified and all available history, up to the current moment, is dis-
played. The device has not been operating for more than three hours; consequently the time range shown by the
graph is from 3 to 0 hours. Each graph percentage value represents the maximum CPU usage in a 3 minute interval.
The horizontal axis range automatically increases (depending on how long the device has been operating for) up to a
maximum of 48 hours. After this, the axis maintains the range from 48 to 0 hours.

Example 2:

+system cpu-history-48h 12 3
CPU usage in range from 12 to 3 hours ago (%):
100_ 222222222322222222222222222222259222222222222222222223124222
95_|
90_|
85_|
80_|
75_|
70_|
65_|
60_|
55_|
50_|
45_|
40_|
35_|
30_|
25_|
20_|
15_|
10_|
5_| : :
0_|.........:.......................:.....................:.....
12h. 11h 7h 3

In this example, the max_hour and min_hour parameters have been specified. This determines the viewing range is
from 12 hours ago to 3 hours ago.

3.2.22.4 SYSTEM CPU-TEXT

Displays the average load in the system as a percentage, for short, medium and long term.

Syntax:

+system cpu-text

Example:

+system cpu-text
CPU Short-Term Usage (5 sec.): 24.5%
CPU Medium-Term Usage (1 min.): 19.2%
CPU Long-Term Usage (5 min.): 17.6%
+

3.2.22.5 SYSTEM DISABLE-PROCESS-MONITOR

This command disables monitoring for the system processes, preventing you from getting CPU usage statistics for
processing. The processes monitoring is disabled on device startup.

Syntax:

+system disable-process-monitor

Example:

+system disable-process-monitor
Process monitoring disabled
+

Configuration and Monitoring 119

3 Router Monitoring Teldat SA

3.2.22.6 SYSTEM ENABLE-PROCESS-MONITOR

This command enables monitoring for the system processes where you can obtain CPU usage statistics for pro-
cessing. Processes monitoring is disabled on device startup.

Syntax:

+system enable-process-monitor

Example:

+system enable-process-monitor
Process monitoring enabled
Equipment performances can be affected while process monitoring is enabled.
+

Note

When process monitoring is enabled, this can negatively affect device performance.

3.2.22.7 SYSTEM FIRMWARES-REQUIRED

Displays the required firmware to ensure correct system operation.

Syntax:

+system firmwares-required

Example:

+system firmwares-required
List of required firmwares for detected hardware
------------------------------------------------
Filename Description
-------------- ---------------------------------------------------
fw000000.bfw Alcatel-SGS Thomson DynaMiTe ADSL over POTS
+

3.2.22.8 SYSTEM HTTP

Command history:

Release Modification
10.08.34.05.12 This command option was introduced as of version 10.08.34.05.12.
11.00.05 This command option was introduced as of version 11.00.05.
11.01.01 This command option was introduced as of version 11.01.01.

Allows you to view information on users currently connected to the Web.

Example:

+system http

ID USER LEVEL IP ADDRESS:PORT LAST_ACCESS

---------------------------------------------------------------------------------------

1 mon 5 192.168.214.170 01/01-22:30:06

2 TEL10 10 192.168.214.170 01/01-22:30:06

3.2.22.9 SYSTEM LICENCE

Command history:

Release Modification
11.01.01 This command option was introduced as of version 11.01.01. This system is in use as of
version 11.01. Earlier devices do not have this.

120 Configuration and Monitoring

Teldat SA 3 Router Monitoring

Allows you to view license information and execute actions over the new license system.

Syntax:

+system licence ?
check Check licence file previously loaded
create Create a licence file
files Show information about licence files loaded in the equipment
+system licence

3.2.22.9.1 SYSTEM LICENCE CHECK

This command allows a user to check a precreated license file, find out if the license is valid or if it has unsupported
parameters (for the current CIT version).

Example 1:

+system licence check

CLI Error: Licence file not found or invalid Licence file.
CLI Error: Command error
+

Example 2:

+system licence check

Licence file OK
+

Example 3:

+system licence check

CLI Error: Error checking licence
Warning: possible errors in the configuration, at least these found:
line 4 -> check
CLI Error: Invalid functionality M5G.

(lines counting since last log-command-errors or transaction fail-on-error command)

CLI Error: Command error
+

3.2.22.9.2 SYSTEM LICENCE CREATE

This command allows a user to create a licence file. On completion, the created file is checked to see if it contains a
valid licence or has unsupported parameters for the current CIT version.

Example 1:

+system licence create

Input Licence File Hex Content: (End CTRL+P)
0123456789abcdff000000010000000200000000000004100000000000000000
00149a262aa66aaadd3c0a75163821c748d63af3940745aa9ec42f8afe5bfc29
cf8fc848d49c879b8052066f1a1885a2415fce84e805b9e502176266aae6cdf0
398abe8b52fb8e1c99d23ae7ac720dc3ca571aa0915fc2a20b50f0ea28d56247
163bb4a92d90909d0e32d33c4b0929994a3770acf1fc7d8eebf2f5327a998deb
3a7e26406cf92d2e11278a3403985e3aec5a8cd124d5637c7b084ef220d34365
5b4f478e3e2b81a6082ece798449d728c0808e5ceb7815a7679d7f94fedb50ac
8f51fe602ced5296a004f66f5e3fb991694d829be0867ccc9d44ba9c963ad8e1
064a794e275aa174452e8545fe0e520cc2cb77712135393fde90e2585a30a8c7
a5a44ca3456376c9bc72807bcd3d112455e42b25cbce6047bb9dae39ee2f5cdf
fcee23a3544b0e4c3f5cd252e5cb5237b4e9402c89308c6ca386d261725d4f5b
d55902ffe2294e2fa1bbbfd127a7f9746a0e07f5be4b3683ccec3c3eb8165f4b
8f3c13a3de698a16a2216c533337da02c8ebd4f0b8a66a97f6766339f7687daf
ae910a3e634b9d6c73666ed391d2f496d2fcef60b6dac30e074b9fdb0296135a
40751524e1634d17e1257567b946800d692205a88b15ba9b6d9999ea3c9634cc
32ac5a6f561704c14d3dfb98ef53c4c50e213122139841dc1d12c8597e939f75
5a1a0b80ee24d432e1510c91e52dc4cfe22099c5a039b9bda96af91dfa6b9202
9c4b023efe1ad078dc491948effeb834fe2b930d33e22800b2daf135ad316ca1
a2ecf6bdfddbb0ca04cfdc2b0c615ce4d3b45ef22910d07273a0177a47ac1f6a
9b4f3b2cd220cc727bd34fed93e80211340e6defe25504c4b07d2f0599d77551
aaeb0d1f75f45a2d2608ae683e98860444f1395ab7d65ffe99352948785f2052
30da79b2c83710ba00648ad9696801b812f9b38b80cd3f0d9c13fc1ac5289cb5

Configuration and Monitoring 121

3 Router Monitoring Teldat SA

855ac70f321cff994da4f3ccf6c657b87127359ef30893e23362935ca5c9e3a6
7e4d7c4266abd133a1c5a883cd119321615e0bc2dc68f817faf5caf3570bf278
ebb8ec7caf404fd82f8c5db6241f0cbbace7906a80632d251da07b43036d144b
49475b2ed30a33619cff0eeeedb9657e4feed4d52e83cc8569bc9763b4a30df5
02c8a98cab8d5264c2ea67e25f1b5713d202d4b064e55b68d0a757b15c130865
f5ac9973792014359c5c35907375460a209940daa9bbabc016427688fb5658d9
65899cbbed70352e7227ebf94c6cb3df3e89db85bdca84d7f7717d374abd0fa0
3b9a346aebfbe1fdf56338c4f4997112e9915c4285eda6b18f9e228130ca5e46
1a3de55d0e9619eec9ebab207c09b3d64eceeaa3a29017e85237b33c00b2c761
ec74b35714e8666339de68b8a0bbe22f254625958935c0cb322c91e7f6e2205d
8a65368460ece50b951feb884a254f7bbb61bb906ff35ceecd72bf39cc7767f3
6bda37e6f3739a78bad6dbe4c9b0a4b5062020206c6963656e63650a09626173
652d6465766963652058595a0a096c6963656e63652d6e616d65205355504552
0a09636865636b0a202020657869740a5993419d3900333abf2fd592a265d927
File Successfully Saved
Licence file OK
+

Example 2:

+system licence create

Input Licence File Hex Content: (End CTRL+P)
0123456789abcdff000000010000000200000000000004110000000000000000
00187ca97881ca4d9abd7e14324db7817b2fc1d374191c4c4beee70c8be19deb
5725aa9e94263525e3317066d19fc70e389df32be8e717e557806391d39d0544
00901bea608be2352d7c993ed0cd15ada73d5b2d0f17740324808261ff822c44
cc5ecc09608dfbb9f1f3719df933129c4a9b2d8ebd4ad5bbf8ddb98cf77fd95d
d643fa81b1af5a8dcebc6b25f27171dde539c9c07d0388fb5298d268dd0498ee
382c2778e0989c6c1055fac7f3e9f0b7dd0a602cbd2b19d8ce47d878548744da
ddb5ebbba890c0d5920be99ce6422b1efff771e0d58e7e09779457d36fffa83a
0db39927c407592cd28401de53e87c6b8a5e174dfc5ccf503dbceca1556c29b6
02acae82650f4c033f3602419589f8286e8d1bca9ea98ccd76112294a44d804f
715a1650c1dd23ae1bede429f0996bcc044be7f6f3ed7983d5799e5f88288bc0
452d3d32e84cef7b6f49756f01cf72a354503b3d4c8405937eeca3a7330627b2
27c5f2ce4159b23de53d37acfba69e5cc5c9ba003a2e41e68af9dde526f31c63
327b1c5d2aa866fabc929d55bfdda7e07ad54545cb916a547642802e45821e90
1dd9374690fe8bf252629013c1f7b36d090a24d6deb2037ebffbb4e93848d2ae
971dad85f2c44855209d431208bca92603f0fe3716807be3406f5bdc135df0cd
e2bbf1afcb8b1a4984875d484bb69588f384acef044966f8997b161a67de6eac
ddd87acb4882162a16386deb59b51e78b9b7c9e7044346355511abba486dbed9
82cf7f652602ba1fbc1ab18c884c0ad9d4ed24ff8605e46956b7ae6cdeaf16f1
8fb08c8cb1034b6c436f2d98d151d1e1287ff809ce0b37d28205863f0dcdd241
77bce49a35a4c817c2c91230b561449de839f5cfc135deaf822bb33ee0f4dd76
f6ebb4fa92a76bd89b90749ea959404cdfdc1cd1ee48286af26874b810d52f0f
ad66164e56f2b65a9e804fd71ade72990a9d6cdbd66bac765794b249dc2559b9
d50de1a46a0f184b4b28e0c48cd62ed188a457bb6dac728cb3973f09fe1e20e4
d5f14daa6cac17c3106b495871ed508f318f1191fc79ace39eef646c31fd2c16
afdb69f4b71c1afce2038b98a8123495cbeca894ad27fd83682fc2be1e82c6de
7dc457df82d5af6964f9c7296ef7b5b9b6c2f152b16f52e3d97a7b47f2739e71
1a5b639ec0f0759d8b2edd06ad944b250d0940ad45ec4c57e10cb8752818ae3f
9f82e36c0cad869680d647674fa4254cb32df225e69e381b95b170ae4ac0221f
12d1ec0894ec795e3df85b0b262665588a8fcb43946995ecb64c8e95713c5ad4
ac12d4e1d2b4f51558efca686fdd5ff6fc041f1676972f801e5258ec625fef0d
4ac380a4f2afced23eec7971dcd1f4b46a54c9230052c851374c335f0a84d625
4c978f0fd1acb8f11771a8ee2dccf06b8abcfb4e7f2b4e900c59afdcdd078a39
ebf54439fe1d87bd6bd766aa2ade825ab86d2020206c6963656e63650a096261
73652d6465766963652058595a0a0966756e6374696f6e616c697479204d3547
0a09636865636b0a202020657869740a5836dc6b85dd442958ceb184c52430a3
File Successfully Saved
CLI Error: Error checking licence
Warning: possible errors in the configuration, at least these found:
line 4 -> check
CLI Error: Invalid functionality M5G.

(lines counting since last log-command-errors or transaction fail-on-error comma nd)

CLI Error: Command error
+

122 Configuration and Monitoring

Teldat SA 3 Router Monitoring

3.2.22.9.3 SYSTEM LICENCE FILES

Allows a user to check if the licence file is processed properly by the device on startup and whether the license is ap-
plied or discarded (due to errors).

Example 1:

+system licence create+system licence files

Information about .LIC files loaded in the system

New found files: 1

Disk Unit: A
Default file generated: OK
Loaded default: OK
Loaded new base: YES

Table of new found files

NAME STATUS SIZE DATE TIME

-----------------------------------------------------------
SAMPLE.LIC Loaded 1152 10/12/00 00:00

Example 2:

+system licence files

Information about .LIC files loaded in the system

New found files: 1

Disk Unit: A
Default file generated: OK
Loaded default: OK
Loaded new base: NO

Table of new found files

NAME STATUS SIZE DATE TIME

-----------------------------------------------------------
SAMPLE.LIC Errors 1152 10/12/00 00:00

3.2.22.10 SYSTEM LOGIN

This first shows if the difference between upper and lower case characters is activated in the user name authentica-
tion process. Subsequently it dumps a list with information on users who have accessed the Teldat device console.

Syntax:

+system login <clear after show>

<clear after show> this parameter (possible values: yes / no) indicates if you wish to delete the history after display-
ing it on screen. If no value is introduced here, the device asks the user for a value after showing the list.

Example:

+system login
Case-sensitive login: enabled

Date Login Type

-------------- ---------- ------
01/03 10:41:01 root REMOTE
01/03 10:42:05 user1 REMOTE
02/04 16:58:06 LOCAL
02/04 16:58:19 user1 REMOTE
02/04 16:59:55 user1 REMOTE
03/07 10:09:49 omateo REMOTE

Configuration and Monitoring 123

3 Router Monitoring Teldat SA

03/07 10:26:29 rsanchez LOCAL

03/07 10:27:06 user1 REMOTE
03/07 10:30:06 root REMOTE
03/07 10:30:09 LOCAL
03/07 10:30:16 root REMOTE
Clean historic?(Yes/No) [No]? No
+

3.2.22.11 SYSTEM LOGIN-HISTORIC

Displays a list containing information on the users who have accessed the device console.

Syntax:

+system login-historic <clear after show>

<clear after show> parameter (possible values yes / no) allowing you to delete the history after showing it on
screen. If you do not enter a value, the device prompts you for one after displaying the list.

Example:

+system login-historic
Date Login Type
-------------- ---------- ------
01/03 10:41:01 root REMOTE
01/03 10:42:05 user1 REMOTE
02/04 16:58:06 LOCAL
02/04 16:58:19 user1 REMOTE
02/04 16:59:55 user1 REMOTE
03/07 10:09:49 omateo REMOTE
03/07 10:26:29 rsanchez LOCAL
03/07 10:27:06 user1 REMOTE
03/07 10:30:06 root REMOTE
03/07 10:30:09 LOCAL
03/07 10:30:16 root REMOTE
Clean historic?(Yes/No) [No]? No
+

The meaning of each field is as follows:

Date Date (month/day) and time of access.
Login Name of user connected to the device. This field is empty if no users have been created.
Type Type of access executed by the user: through telnet (REMOTE) or console (LOCAL).

3.2.22.12 SYSTEM MEMORY

This command displays statistics on the system memory.

Syntax:

+system memory

Example:

+system memory
Caller Second C. Third C. Address Size Age Hsh
-------------------------------------------------
xxxxxxx xxxxxxxx xxxxxxxx xxxxxx xxxx xxxxx xxxxxx

Times couldnt monitor a request X

Times couldnt match a free X
Entries created X Entries available X Entries in use x
+

Note

This command should only be executed by the Teldat technical team.

124 Configuration and Monitoring

Teldat SA 3 Router Monitoring

3.2.22.13 SYSTEM PCMCIA

This command accesses the PCMCIA interface status monitoring environment at the physical layer (controller and
card).

Syntax:

+system pcmcia <option> <parameters>

DEBUG
DUMP

• <option> specifies an action to execute: events enable/disable [DEBUG] or dump the controller and card status in-
formation [DUMP].
• <parameters> parameters required for different possible actions.

Example:

+system pcmcia dump socket

Identification and revision= *(0x00)=0x84
Chip information = *(0x1f)=0x00

PCMCIA Socket -0/A- Controller Registers

----------------------------------------------
Interface status = *(0x01)=0x7f: [bvd1/stschg] [bvd2/spkr] [detect]
[wrprot] [ready] [poweron]
Power control = *(0x02)=0x90: [output] [resetdrv] [Vcc=5v] [Vpp off]
Interrupts and control = *(0x03)=0x70: [iocard] [intr ena] [irq=0]
Card status changes = *(0x04)=0x00:
Card status chng int cntrl = *(0x05)=0x09: [bvd1/stschg] [detect] [irq=0]
Misc control 1 = *(0x16)=0xc0: [inpack]
Misc control 2 = *(0x1e)=0x00:
MemMap(0) = 0x21, 240 ns, 0xf0001000-0xf0001fff, 00000 [active] [attrib]
MemMap(1) = 00, 0 ns, 00000-0x01fff, 00000
MemMap(2) = 00, 0 ns, 00000-0x01fff, 00000
MemMap(3) = 00, 0 ns, 00000-0x01fff, 00000
MemMap(4) = 00, 0 ns, 00000-0x01fff, 00000
IoMap (0) = 0x09, 0 ns, 0x03f8-0x03ff [active] [0ws]
IoMap (1) = 00, 0 ns, 0000-0x0001
TmrSet(0) = setup = 0, command = 0, recovery = 0
TmrSet(1) = setup = 0, command = 0, recovery = 0
ExtRegs = mask 0 = 0x7f, mask 1 = 0x90, DMA ctl = 0x70 [dreq is inpack] [pullup]

For further information, please see manual Teldat Dm757-I PCMCIA UMTS Interface.

3.2.22.14 SYSTEM POWER-OFF-STATUS

This command displays the current status of the ignition signal, the value programmed in the timer and where the
ignition signal is not active, the time lapsed from the moment the ignition was switched off.

Syntax:

+system power-off-status

Example 1:

+system disable-process-monitor
Ignition signal state ACTIVE
Programmed time to power off: 60 seconds
+

Example 2:

+system disable-process-monitor
Ignition signal state DEACTIVE
Programmed time to power off: 60 seconds
Time elapsed with ignition off: 10 seconds
+

Configuration and Monitoring 125

3 Router Monitoring Teldat SA

3.2.22.15 SYSTEM PROCESS-LIST

This command displays the percentage of CPU usage and the stack status stack for each active process in the sys-
tem. This command displays three CPU usage percentages corresponding to the latest 5 seconds, the last minute
and the last 5 minutes respectively. To use this command, process monitoring must be enabled. These processes
come in three types:

(a) Interrupts. This is a high priority process which responds to petitions from different hardware components, such
as reception of a packet or a change in the physical layer of an interface.
(b) High level interrupt handler. These processes respond at a higher level (lower priority) the interruptions captured
through the Interrupts process.
(c) Task . These processes handle the rest of the device tasks, such as monitoring, configuration, routing protocols,
etc.

Syntax:

+system process-list

Example:

+system process-list
Process monitoring enabled.
Stack status and CPU load for each process.
Type: I (interrupts), H (high level interrupt handler), T (task)

Type Name Stack size Status cpu % (5s/1m/5m)

----------------------------------------------------------
I Ints 4112 ok 0.16 0.16 0.17
H SYSTEM H 4104 ok 0.60 0.60 0.59
H UART-RXH 4096 ok 0.00 0.00 0.00
T DISC 32768 ok 0.00 0.00 0.00
T CMDMUTEX 16000 ok 0.00 0.00 0.00
T SAVE_TXT 16000 ok 0.00 0.00 0.00
T LAPB2DRV 2048 ok 0.00 0.00 0.00
T CONFIGUR 2048 ok 0.00 0.00 0.00
T DRIVER 2048 ok 0.02 0.02 0.02
T SYSTEM_M 2048 ok 0.00 0.00 0.00
T LAPB 4096 ok 0.00 0.00 0.00
T LAPB_MNG 2048 ok 0.00 0.00 0.00
T X25 4096 ok 0.00 0.00 0.00
T X25_MNG 4096 ok 0.00 0.00 0.00
T MOTPROT 4096 ok 0.00 0.00 0.00
T PROTMOT 2048 ok 0.00 0.00 0.00
T CONTINT 2048 ok 0.02 0.02 0.02
T CRYPX25 2048 ok 0.00 0.00 0.00
H SCC1 4096 ok 0.00 0.00 0.00
H SCC2 4096 ok 0.00 0.00 0.00
H SCC3 4096 ok 0.00 0.00 0.00
H SCC4 4096 ok 0.00 0.00 0.00
T GESTCON 32000 ok 0.05 0.05 0.56
T VISEVEN 8192 ok 0.00 0.00 0.00
T TASKER 32000 ok 0.92 0.85 0.80
T CONTROL 4096 ok 0.00 0.00 0.00
T MTC 4096 ok 0.00 0.00 0.00
T RESET 4096 ok 0.00 0.00 0.00
T BFD 32768 ok 0.01 0.01 0.01
T FTP 32768 ok 0.00 0.00 0.00
T SCEP_ACT 4096 ok 0.00 0.00 0.00
T SCEP_WAL 4096 ok 0.00 0.00 0.00
T SNMP 32768 ok 0.00 0.00 0.00
T SNMP-TRA 32768 ok 0.00 0.00 0.00
T TELNETSR 8192 ok 0.09 0.17 0.03
T DNSCACHE 32768 ok 0.00 0.00 0.00

The meaning of the above fields is as follows:

Type Type of process ( I for Interrupts, H for High level interrupt handler, and T for Task ).

126 Configuration and Monitoring

Teldat SA 3 Router Monitoring

Name Name of process.

Stack size Task stack size in bytes.
Status Stack status. ok indicates the stack is operating correctly. overflow indicates the stack has over-
flowed due to lack of memory. unknown indicates unmanaged stacks.
cpu % CPU usage percentages for each process. From left to right, each column displays the use in the
(5s/1m/5m) last 5 seconds, the last minute and the last 5 minutes respectively.

Note

When the processes monitoring is enabled, this may negatively affect device performance.

3.2.22.16 SYSTEM STACK-STATUS

This command displays the stack status for each system process. Each system process has its own stack memory
where the current status of said process is stored. Use this command to view the stack status for each active pro-
cess in the system. Said processes can be one of three types:
(1) Interrupts. This is the highest priority process and manages petitions for the various hardware components,
such as packet reception or a change in the interface physical layer.
(2) High level interrupt handler. These processes handle interruptions captured through the Interrupts process at a
high level (lower priority).
(3) Task . These processes handle the rest of the device tasks, such as monitoring, configuration, routing protocols,
etc.

Syntax:

+system stack-status

Example:

+system stack-status
Stack status for each process.
Type: I (interrupts), H (high level interrupt handler), T (task)

Type Name Stack size (addr) Curr. Min. Status

---------------------------------------------------------------
I Ints 4112 (011AA040) 4112 4000 ok
H SYSTEM H 4104 (011AC040) 3728 3616 ok
H UART-RXH 4096 (011B7040) 3952 3776 ok
T DISC 4096 (011B9040) 3816 3736 ok
T CMDMUTEX 16000 (011C0040) 15720 15640 ok
T SAVE_TXT 16000 (01202040) 15696 15616 ok
T LAPB2DRV 2048 (0120B040) 1884 1876 ok
T CONFIGUR 2048 (01214040) 1584 1504 ok
T DRIVER 2048 (01215040) 1624 1608 ok
T SYSTEM_M 2048 (01216040) 1624 1544 ok
T LAPB 4096 (01217040) 3696 3616 ok
T LAPB_MNG 2048 (01219040) 1696 1616 ok
T X25 4096 (0121A040) 3592 3512 ok
T X25_MNG 4096 (0121C040) 3720 3640 ok
T MOTPROT 4096 (0121E040) 3168 3096 ok
T PROTMOT 2048 (01220040) 1584 1504 ok
T CONTINT 2048 (01221040) 1864 1784 ok
T CRYPX25 2048 (01222040) 1884 1876 ok
T X25_FR 2048 (01223040) 1600 1520 ok
T TCP270 2048 (01224040) 1512 1496 ok
H SCC1 1024 (01225040) 912 912 ok
H SCC2 1024 (01225840) 912 912 ok
H SCC3 1024 (01226040) 912 912 ok
H SCC4 1024 (01226840) 912 912 ok
T GESTCON 16000 (01230040) 12408 10464 ok
T VISEVEN 8192 (01234040) 7672 7592 ok
T TASKER 32000 (01237040) 30680 29364 ok
T CONTROL 1024 (0123F040) 792 712 ok
T MTC 4096 (01240040) 3848 3768 ok
T RESET 1024 (0123F840) 860 852 ok
T FTP 4096 (0145D040) 3848 3768 ok

Configuration and Monitoring 127

3 Router Monitoring Teldat SA

T NU SCEP 4096 (01477040) 3856 3776 ok

T TELNETSR 8192 (01495040) 7072 6952 ok
+

The meaning of field is as follows:

Type Type of process ( I for Interrupts, H for High level interrupt handler, and T for Task ).
Name Name of process.
Stack size Task stack size in bytes. The base address for said stack is displayed between brackets).
(addr)
Curr. Minimum number of free bytes, detected in the stack, in calls to the operating system.
Min. Minimum number of free bytes detected in the stack.
Status Stack Status. ok indicates the stack is operating correctly. overflow indicates the stack has over-
flowed due to lack of memory. unknown indicates non-managed stacks.

Note

This command should only be executed by the Teldat technical team.

3.2.22.17 SYSTEM TELNET

Displays information on users connected to the device.

Syntax:

+system telnet

Example:

+system telnet

Time unit: minutes

ID USER LEVEL IP ADDRESS:PORT CONNECTION-TIME INACTIV-TIME IDLETIME TIMEOUT
--------------------------------------------------------------------------------------

0 user1 15 Local Console 03/03/05 10:40:57 0 0 0

2 user1 15 172.24.51.128:59671 04/05/05 16:59:46 0 10 0 *
1 user1 15 192.168.1.1:0 04/03/05 16:57:58 2 0 0
+

The meaning of each field is as follows:

ID Telnet session identifier number.
USER Name of user connected to the device. This field is blank if no users have been
created.
LEVEL User privilege level.
IP ADDRESS:PORT IP address and port where the connection is received.
CONNECTION TIME Date and time of connection.
INACTIVITY TIME Telnet session inactivity time. Where this parameter is deactivated (through con-
figuration), this value is 0.
IDLETIME Maximum time permitted without activity. Where no maximum time is configured,
the value is 0.
TIMEOUT Maximum time permitted for the session. Where no maximum time is configured,
the value is 0.

An asterisk appears in the list next to the inactivity time field indicating the session you are accessing from.

3.2.22.18 SYSTEM TELNET-CLIENTS

This command displays information on Telnet sessions (to remote devices) opened from the device.

Syntax:

+system telnet-clients

Example:

+system telnet-clients

128 Configuration and Monitoring

Teldat SA 3 Router Monitoring

Session Local-user VRF Local-IP Remote-IP Session-start URL

------------------------------------------------------------------------------------
1 tel1 <main> 172.16.0.1 172.16.0.2 10/02/12 12:15:48 --
2 tel2 <main> 172.16.0.1 172.16.0.24 10/02/12 12:15:49 --
3 tel3 <main> 2001:db8:1::2 2001:db8:1::1 10/02/12 12:15:50 --
4 tel4 <main> 172.16.0.1 172.16.0.2 10/02/12 12:15:51 --
17 tel17 vrf2 172.17.0.1 172.17.0.2 10/02/12 12:16:04 --

The meaning of the columns is as follows:

SESSION This is the unique identification number the device assigns to Telnet session.
LOCAL-USER Name of the user, logged into the device, who opened the Telnet session.
VRF VRF table used to reach the remote device.
LOCAL-IP IP address for the device used to communicate with the remote device.
REMOTE-IP IP address for the remote device the Telnet session was opened with.
SESSION-START Date and time the session was opened.
URL URL for the remote device the Telnet session was opened with, when this is used.

3.2.22.19 SYSTEM TERMINAL

This command executes exchange of messages and commands between the terminals for the different sessions es-
tablished with the monitoring device.

Syntax:

+system terminal <option>

kill-terminal Kill another terminal
send-escape Send an escape character to another terminal
writeln Write a line to another user

3.2.22.19.1 SYSTEM TERMINAL KILL-TERMINAL

This command forces termination of an established session and doesn't take into account any data entered after said
command. A list of currently active sessions is displayed where a user selects those he wishes to end (kill) through a
request. Only users with ROOT permission can execute this command (access level 15).

Example:

+system terminal kill-terminal ?

<cr>
+system terminal kill-terminal
Current active terminal sessions:
Local console session:
Time unit: minutes
ID USER LEVEL IP ADDRESS:PORT CONNECTION-TIME INACTIV-TIME IDLETIME TIMEOUT

0 user1 15 Local Console 09/12/13 19:21:34 0 0 0 *

Current active Telnet sessions:
Time unit: minutes
ID USER LEVEL IP ADDRESS:PORT CONNECTION-TIME INACTIV-TIME IDLETIME TIMEOUT
-----------------------------------------------------------------------------------

1 rafa 15 [192.168.212.26]:47354 09/12/13 19:22:49 0 0 0

2 pepe 5 [192.168.212.26]:47353 09/12/13 19:22:24 0 0 0
Current active SSH sessions:

Time unit: minutes

ID USER LEVEL IP ADDRESS:PORT CONNECTION-TIME INACTIV-TIME IDLETIME TIMEOUT
-----------------------------------------------------------------------------------
3 rafa 15 192.168.212.26:47621 09/12/13 19:22:10 0 0 0
Destination console ID:[0]? 1
You are going to kill the terminal in [192.168.212.26]:47354
Are you sure(Yes/No)? yes
+

The following is displayed in the remote terminal:

Message from user1 in console ID 0:

Configuration and Monitoring 129

3 Router Monitoring Teldat SA

Your session is going to finish

Connection closed by foreign host.

3.2.22.19.2 SYSTEM TERMINAL SEND-ESCAPE

This command sends the escape character (Ctrl+p by default) to the terminal corresponding to a determined session
(this doesn't take into account data entered after said command). Next, a list of currently established sessions is dis-
played. A user (with ROOT permission) selects the sessions he wants to send the escape character to and sends
said escape request, with the result that users currently in the selected sessions exit the console menus. Only users
with ROOT permission can execute this command (access level 15).

Example:

+system terminal send-escape ?

<cr>
+system terminal send-escape
Current active terminal sessions:
Local console session:

Time unit: minutes

ID USER LEVEL IP ADDRESS:PORT CONNECTION-TIME INACTIV-TIME IDLETIME TIMEOUT
------------------------------------------------------------------------------------
0 user1 15 Local Console 09/12/13 19:21:34 0 0 0 *
Current active Telnet sessions:
Time unit: minutes
ID USER LEVEL IP ADDRESS:PORT CONNECTION-TIME INACTIV-TIME IDLETIME TIMEOUT
------------------------------------------------------------------------------------
1 rafa 15 [192.168.212.26]:47357 09/12/13 19:41:30 0 0 0
2 pepe 5 [192.168.212.26]:47353 09/12/13 19:22:24 0 0 0
Current active SSH sessions:

Time unit: minutes

ID USER LEVEL IP ADDRESS:PORT CONNECTION-TIME INACTIV-TIME IDLETIME TIMEOUT
------------------------------------------------------------------------------------
3 rafa 15 192.168.212.26:47621 09/12/13 19:22:10 0 0 0
Destination console ID:[0]? 1
You are going to send the escape sequence to the terminal in [192.168.212.26]:47357
Are you sure(Yes/No)? y
Escape sequence sent
+

The following is displayed in the remote terminal:

Message from user1 in console ID 0:

I have sent you the escape sequence

3.2.22.19.3 SYSTEM TERMINAL WRITELN

This command sends a message to another terminal, i.e. to a user using another established session with the mon-
itored device (this doesn't take into account any data entered after said command). A list of currently established ses-
sions is displayed. A user can then select the sessions to send a request to (-1 sends to all sessions) subsequently
writing the message to be sent. All users with access levels equal or above MONITOR can execute this command.

Example:

+system terminal writeln ?

<cr>
+system terminal writeln
Current active terminal sessions:
Local console session:
Time unit: minutes
ID USER LEVEL IP ADDRESS:PORT CONNECTION-TIME INACTIV-TIME IDLETIME TIMEOUT
------------------------------------------------------------------------------------
0 user1 15 Local Console 09/12/13 19:21:34 0 0 0 *
Current active Telnet sessions:
Time unit: minutes

ID USER LEVEL IP ADDRESS:PORT CONNECTION-TIME INACTIV-TIME IDLETIME TIMEOUT

------------------------------------------------------------------------------------
1 rafa 15 [192.168.212.26]:47357 09/12/13 19:41:30 0 0 0

130 Configuration and Monitoring

Teldat SA 3 Router Monitoring

2 pepe 5 [192.168.212.26]:47353 09/12/13 19:22:24 0 0 0

Current active SSH sessions:

Time unit: minutes

ID USER LEVEL IP ADDRESS:PORT CONNECTION-TIME INACTIV-TIME IDLETIME TIMEOUT
------------------------------------------------------------------------------------
3 rafa 15 192.168.212.26:47621 09/12/13 19:22:10 0 0 0
Destination console ID (-1 for broadcast):[0]? -1
Message text (maximum 100 characters): []? I have to restart the router

Message from user1 in console ID 0:

I have to restart the router
Message sent
+

The following is displayed in one of the remote terminals:

Message from user1 in console ID 0:

I have to restart the router

3.2.22.20 SYSTEM USB

Accesses the PCMCIA interface status monitoring environment at the physical layer (controller and card).

Syntax:

+system usb <option> <parameters>

DEBUG
LSIT

• <option> specifies an action to execute: events enable/disable [DEBUG] or dump controller and card status in-
formation [DUMP].
• <parameters> parameters required for the different possible actions.

Example:

+system usb list supported

Option Fusion Globettroter
Manufacturer ID 0x0af0 Card ID 0x6000
Vodafone Connect 3G
Manufacturer ID 0x0af0 Card ID 0x5000
Option Globettroter Quad
Manufacturer ID 0x0af0 Card ID 0x6300
Option Globettroter 3G GT Fusion Lite
Manufacturer ID 0x0af0 Card ID 0x6100
Novatel Merlin U740 R.0 HSDPA
Manufacturer ID 0x1410 Card ID 0x1400
Novatel Merlin U740 HSDPA
Manufacturer ID 0x1410 Card ID 0x1410
Novatel Merlin V620 CDMA EV-DO
Manufacturer ID 0x1410 Card ID 0x1110
Sierra Aircard 580
Manufacturer ID 0x1199 Card ID 0x0112
Huawei Mobile Connect E612
Manufacturer ID 0x12d1 Card ID 0x1001
+

For further information, please see manual Teldat Dm757-I PCMCIA UMTS Interface.

3.2.23 TFTP
This command provides access for device TFTP client (Trivial File Transfer Protocol).

Syntax:

+tftp

Example:

+tftp

Configuration and Monitoring 131

3 Router Monitoring Teldat SA

TFTP manager
TFTP+

For further information, please see manual Teldat Dm765-I TFTP Protocol.

3.2.24 TELEPHONY
The telephony command provides access to device telephony functions monitoring environment based on the Voice
over IP.

Syntax:

+telephony

Example:

+telephony
Telephony Monitor
Telephony Mon+

For further information, please see manual Teldat Dm722-I Voice over IP.

3.2.25 UCI
The UCI command allows you to configure the Teldat Router encryption unit.

Syntax:

+uci <option>
HELP_STATISTICS
INIT_STATISTICS
LINE_X25
RESET_LINE_X25
STATISTICS
GENERAL_CRYP
CLEAR_STACRYP

• < option > specifies the type of information to monitor.

Example:

+uci help_statistics
Statistics meanings
RECEIVED FRAMES REJECTED
TOO_LARGE: The received frame has, or has not, too large size
concided with encryption header
FAILURE: Frame reception failure
WITHOUT.LINE: Frame received but impossible to be transmitted to
destination because the receiver was not ready
WRONG.ENCRYPT: Impossible to encrypt a received frame
WITHOUT.MEM: Not enough memory for the transmitted frame

CONTROL FRAMES RECEIVED

DLCI not between 16 and 1007 (included)

PROCESSED FRAMES
ENCRYPTED: Frames encrypted correctly
DECRYPTED: Frames decrypted with DLCI key
DEC.KEY.DEF: Decrypted frames with the default key, not decrypted
with the DLCI key
TRANSPARENTS: Transparent frames

TOTAL PROCESSED FRAMES =ENCRYPTED + DECRYPTED + DES.KEY.DEF + TRANSPARENTS

0 0 0 0 0
+

3.2.26 UPTIME
Displays current Date and Time of the router, and time interval since last router boot up.

132 Configuration and Monitoring

Teldat SA 3 Router Monitoring

Syntax:

+uptime

Example:

+uptime

Date: Monday, 12/15/14 Time: 17:39:00

Router uptime: 8m9s

Command history:

Release Modification
11.00.03 New command added.

3.2.27 VERSION
Displays all information related to hardware, license, boot ROM version, software version, cellular driver and wireless
LAN driver versions.

Syntax:

+version

Example:

+version

Teldat's Router, M1 4GESW SLOT1 IPSec SNA VoIP T+ 34 12 S/N: 819/02727

Profile: none
ID: TM1-31F128R L34.12

Boot ROM release:

BIOS CODE VERSION: 03.00 Oct 22 2014 18:12:24 L0

System Info:
PCB:0x13A GPPORCR:0x00000000 PVR:0x80212151 SVR:0x80F90110
CLKs: CCB=396000 CPU0/1=792000/0 DDR(clk)=330000 LBUS=99000 PCI0/1=0/0
Watchdog:Enabled
MMU Mode:Dynamic
ICache:ON DCache:ON Write-Back L2Cache:ON

Software release: 11.00.03-Beta-01aac0b Dec 15 2014 11:22:07

Compiled by integrator on ares.id.teldat.com
Loaded from primary partition

Cellular Driver Version: 00.09

WLAN Driver Version: 9.5.0.35.1

Command history:

Release Modification
11.00.03 New command added.

3.2.28 WEB-PROBE
Accessing the web-probe monitoring menu.

Syntax:

+web-probe

Configuration and Monitoring 133

3 Router Monitoring Teldat SA

Example:

+web-probe
-- Web Probe user monitoring --
PROBE+

3.2.29 LOG
Allows you to obtain additional information on the device operation. This is only useful for Teldat’s technical support
service maintenance tasks. Said information is displayed as a hexadecimal dumping via the screen.

Syntax:

+log <number>

• < number > number of items you wish to save/show.

Example:

+log 5
0000 0000 0100 004A 0D0A 3031 2F30 312F
3030 2030 303A 3030 3A30 3020 392E 312E
3720 4D61 7220 3133 2032 3030 3220 3137
3A33 303A 3139 2062 7920 2020 6D62 6572
726F 6A6F 206F 6E20 204D 4245 5252 4F4A
4F32 007D
+

134 Configuration and Monitoring

Teldat SA 4 Event Logging System ELS

Chapter 4 Event Logging System ELS

4.1 Introduction
This chapter describes the Event Logging System (ELS). It also describes the VISEVEN procedure and how to ob-
tain messages from the Event Logging System. VISEVEN provides information on the internal performance of the
device and its interfaces.

This chapter contains the following sections:

(a) Event Logging System

(b) Event Logging System user interface
(c) Event Logging System commands

4.2 Event Logging System

Events occur continuously during device operation. These are generated by various things:

• System activity.
• State changes.
• Service requests.
• Data transmission and reception.
• Errors in the internal data of the system.

The Event Logging System is a device monitoring mechanism, which generates event messages. When something
occurs, the ELS receives data from the system identifying the source and nature of the event. A message is then
generated using said data.

You can select what messages to display (so only useful ones appear), send as traps or send through syslog, by ap-
propriately configuring ELS.

The ELS and the MONITOR procedure counters allow you to isolate problems in the device. A quick view of the
messages tell you if there is a problem and where to start searching for it.

In ELS config> prompt, there are commands you can use to establish a default configuration. This configuration does
not take effect until the device is restarted.

At the ELS config$ prompt, there are commands, which establish an immediately applicable configuration (no device
reboot is required).

Occasionally you may need to temporarily obtain messages through a different configuration (not established
through ELS config> or ELS config$). This is executed from ELS monitoring ( ELS+ prompt) without device reboot.
Here, you can temporarily change event selection so they're displayed on screen, sent as traps or sent through sys-
log messages. This change is immediate and not stored in the system configuration

There is another system similar to the above, which saves logs in non-volatile memory. Said logs register information
on system access (ftp or telnet) and reboots, configuration modifications, etc. The chief difference is, as they are
saved in non-volatile, they remain stored even if the device is switched off or it restarts the application.

The following summary shows the process to access the ELS Config> prompt from the Config> prompt, the ELS con-
fig$ prompt from the Config$ prompt and the ELS+ prompt from the + prompt.

Event Logging System Configuration

Accessing the ELS configuration procedure:
(1) At the console manager procedure prompt *, enter status. This locates the configuration environment process
identifier (pid).

*STATUS
System Processes:
PID NAME

1 Main console
2 Event viewer
3 Monitor console

Configuration and Monitoring 135

4 Event Logging System ELS Teldat SA

4 Config console
5 Running config console
6 Telnet client
*

(2) Enter process and the process identifier (pid) to access CONFIG (number 4).

*PROCESS 4
Config>
An alternative to steps 1 and 2, is to access configuration using the config command located in the console
manager (*) process.

*CONFIG
Config>

(3) Enter event to access ELS.

Config>event
-- ELS Config --
ELS config>
You can now execute ELS commands.
Enter exit to exit the ELS and return to the Config> prompt.

ELS config>exit
Config>

Note

All changes performed in this procedure only take effect on device restart. Please remember to
prestore the configuration in flash memory or the smart card.

If you want the configuration changes to take a dynamic effect without a device reboot, access the ELS dynamic con-
figuration process.
(1) From the console manager process * prompt, enter process and the process identifier (pid) to enter the dynam-
ic configuration process (number 5).

*PROCESS 5
Config$
An alternative to the above is to access the dynamic configuration process through the running-config com-
mand located in the console manager process (“*”) :

*RUNNING-CONFIG
Config$

(2) Enter event to access ELS.

Config$event
-- ELS Config --
ELS config$
ELS commands can now be executed.
Enter exit to exit ELS configuration and return to the Config> prompt.

ELS config$exit
Config$

Note

All the changes made in this process take immediate effect. To keep the configuration for future
reboots, save it in flash or the smart card in the same way as static configuration (config>).

Event Logging System Monitoring

Accessing the ELS monitoring process:
(1) Enter status to locate the monitoring + prompt.

*STATUS
System Processes:
PID NAME

1 Main console

136 Configuration and Monitoring

Teldat SA 4 Event Logging System ELS

2 Event viewer
3 Monitor console
4 Config console
5 Running config console
6 Telnet client
*

(2) Enter process and the process identifier (pid), here it's 3, to access the monitoring process. PROCESS and the
process identifier (pid) to access the MONITOR procedure (3).

PROCESS 3
Console operator
+
An alternative to the sequence, previously indicated by steps 1 and 2, is to access the configuration process
through the MONITOR command from the console manager * process.

*MONITOR
Console Operator
+

(3) Enter event to access the Event Logging System.

+event
-- ELS Monitor --
ELS+
Now you can execute Event Logging System monitoring commands.
To exit the Event Logging System monitoring and return to +, enter exit.

ELS+EXIT
+

Events display (Traces)

Events generated while the system is operating can be displayed from the VISEVEN process or in the active process
(provided that this notification has been enabled in console traces).

The advantage of viewing the events from VISEVEN is they are only displayed when the user requires them and not
as they occur. The advantage of viewing from the active process is they are displayed as they occur and additionally,
you can execute other commandw from the active process. I.e. you can carry out additional tasks or consult more in-
formation.

Disadvantages of displaying events from VISEVEN is you cannot carry out any other task. And if the events buffer is
small, these can be easily lost. Disadvantages of displaying events in the active process is this interferes with the in-
formation displayed by the process currently running and complicates task execution.

To enter VISEVEN from the console manager, carry out the following:
(1) If you do not know VISEVEN PPID, enter status at the * prompt.

*STATUS
System Processes:
PID NAME

1 Main console
2 Event viewer
3 Monitor console
4 Config console
5 Running config console
6 Telnet client
*

(2) Enter process and the process identifier (PID) to access VISEVEN (number 2 here).

*PROCESS 2

This process does not present prompts or allow you to execute commands. However it shows the saved messages t.

To exit VISEVEN and return to the console manager ( * prompt), enter (Ctrl + p).

If you wish to ignore all the events stored up to this point, without viewing them, use the flush command.

The commands hide and view are available to view the events from the active process. These commands must be
fully entered to take effect. If the events are displayed in the active process, you cannot enter VISEVEN. The view
command displays the events and hide command hides them.

Configuration and Monitoring 137

4 Event Logging System ELS Teldat SA

Interpreting the Event Logging System messages

On entering the following command, a message from the Event Logging System can been seen as follows:

ELS+LIST SUBSYSTEM GW
GW.019 C-INFO Slf tst ifc %s

(Subsystem Event Number) (Type of Event) (Message Text)

Subsystem
Subsystem is an abbreviated and pre-defined name for a router component or functionality such as protocol or inter-
face, etc. GW identifies the subsystem said event has occurred through. GW is the abbreviated name for Gateway.

Other examples of subsystems are ARP, IP, ETH. To see the list of available subsystems in the device, execute the
list subsystem command (from CONFIG or P4 configuration process, or from MONITOR or P3).

Enter the subsystem as a parameter in an Event Logging System command if the command is going affect the whole
subsystem. For example, the enable subsystem GW command enables all events in GW subsystem so, when
events are generated, they are collected by the VISEVEN procedure.

Event Number
The Event number is a pre-defined, unique and arbitrary number assigned to each message within a subsystem.
This does not indicate message priority. For example in GW.019, 19 indicates the event number in the GW subsys-
tem. You can obtain a list of all events in a subsystem through the list subsystem <subsystem name> command.
This is available both in the configuration process (CONFIG or P 4) and the monitoring process (MONITOR or P 3).

The event number always appears together with the subsystem identifier it belongs to, separated by “.”, e.g.
GW.019. The subsystem and event number jointly identify an individual event. They are entered as a parameter in
some Event Logging System commands. When a command is only going to affect one specific event, enter the sub-
system and event number as a command parameter.

Type of Event
Type of Event or Filter Level is a pre-defined identifier classifying each message complying with the nature of the
event generating it. This identifier appears when the command list subsystem <name_subsystem> is executed.

TYPE OF EVENTS LIST

Identifier Description
ALWAYS Each time the device software is loaded, information on the copyright and config-
uration confirmation is displayed.
UI-ERROR Abnormal internal errors.
CI-ERROR Common internal errors.
UE-ERROR Abnormal external errors.
CE-ERROR Common external errors.
ERROR Includes all previously mentioned errors.
U-INFO Comments on abnormal information.
C-INFO Comments on usual information.
INFO Includes all types of previously mentioned comments.
STANDARD Includes all types of errors and comments. Default.
P-TRACE Packet trace.
U-TRACE Abnormal operation Trace message.
C-TRACE Common operation Trace message.
TRACE Includes all types of previously mentioned traces.
ALL Includes all types of events.

In this table ERROR, INFO, TRACE, STANDARD and ALL are associated to other filtered levels. STANDARD is the
filter level recommended by default.

Groups

138 Configuration and Monitoring

Teldat SA 4 Event Logging System ELS

Groups are a collection of events defined by the user who gives them a group name. The name of the group can be
entered as a parameter in some Event Logging System commands. There are no pre-defined groups. You need to
create a group before you can specify a group name in the command line.

To create a group, execute the configuration command add, specify the name for the group, and then specify the
events to be included in the group. The included events can be from different subsystems and have different filtering
levels.

Example:

ELS config>add ?
<1..7 chars> Group name
ELS config>add MYGROUP ?
<1..11 chars> Event
ELS config>add MYGROUP GW.019 ?
<cr>
ELS config>add MYGROUP GW.019
ELS config>add MYGROUP PPP.001
ELS config>add MYGROUP PPP.002
ELS config>

Once a group has been created, it can be used to globally manage the events in the group. For example, to enable
the event messages of all events that have been added to a group called MYGROUP to be displayed on screen, in-
clude the name of the group in the command line as follows:

ELS config>ENABLE TRACE GROUP MYGROUP

To delete a group, execute the command delete.

Example:

ELS config>delete ?
<1..7 chars> Group name
ELS config>delete MYGROUP ?
all The whole group
<1..11 chars> Event
ELS config>delete MYGROUP all ?
<cr>
ELS config>delete MYGROUP all
ELS config>

4.3 Event Logging System user interface

To work efficiently with the Event Logging System:

• You need to know what you want to analyze through said system. The problem or events you need to view must
be clearly defined before using the VISEVEN process.
• Execute the clear command in the configuration procedure to erase all the events enabled in said configuration, as
well as the created groups. Or, execute the same command in the monitoring procedure to erase all events en-
abled during execution.
• Enable only those messages related to the problem you wish to investigate.
• If you are working in remote, enable those events to be sent as traps, or through syslog messages, you consider
necessary to determine the problem or analyze device behavior in the specific situation you want to check.

When enabling events to be displayed as traces on the console, you need to bear in mind that if these are produced
too frequently and not viewed on screen at the same rate as produced in the VISEVEN process, the circular mes-
sage buffer may overflow and the initial messages will be lost. When sending events as traps, if the storage buffer
overflows the latest traps, which have not been transmitted are lost. The same occurs with the syslog messages: the
oldest are reserved and the newest discarded.

At the same time as you receive the messages, they may be enabled or disabled depending what events you are in-
terested in.

Console Traces
Any individual event, group of events or subsystem can be enabled to be displayed as traces on the console. These
are visible through VISEVEN (P2) or from the active process by executing view. When using this latter command,
use the hide command to conceal said events.

Configuration and Monitoring 139

4 Event Logging System ELS Teldat SA

ELS config>enable trace event icmp.002

ELS config>enable trace subsystem ip all

ELS config>enable trace group MYGROUP

SNMP Traps
The Event Logging System can be used so a determined event can be sent as a specified private company trap to
any station with SNMP management. The information sent with said trap is a message displayed on screen if the
event is enabled as a trace. A trap occurs each time the selected event occurs (enabled as an SNMP trap). For fur-
ther information, please see the manual Teldat Dm712-I SNMP Agent

Any individual event, group of events or subsystem can be enabled as an SNMP trap.

For example, to enable the SNMP.002 event, so it can be sent as a specific company trap:
(1) At the ELS config>, ELS config$ prompt or ELS+, enter
ENABLE SNMP-TRAP EVENT SNMP.002

Note

If you are in the ELS Config>, save the configuration and restart the device for the change to take
effect.

(2) At the SNMP config> prompt, enter

COMMUNITY <community> ACCESS TRAP-ONLY
HOST <ip address of the SNMP remote manager station> TRAP VERSION <v1/v2c> <community> ALL

Note

Save the configuration and restart the device for the change to take effect.

Syslog Messages
The Event Logging System can be used for a specific event sent in a syslog message format to one or various re-
mote stations. Any event, be it individual or belonging to a group or subsystem, can be enabled with this aim.

For example, to enable the ICMP.002 event so it can be sent as a syslog message,
(1) 1. In the ELS config>, ELS config$ or in ELS+ prompts, enter
ENABLE SYSLOG EVENT ICMP.002

Note

If you are in the ELS Config>, save the configuration and restart the device so the changes takes
effect.

(2) In the SYSLOG config> prompt, configure the IP address or the name of the server domain (or servers) where
the notifications are sent. For further information , please see manual Teldat Dm753-I Client Syslog.

Note

Save the configuration and restart the device so any changes takes effect.

If you execute a ping out from any system to the router. The message is received in the configured syslog server.

Using the Event Logging System to solve problems

When you are trying to resolve a specific problem with the Event Logging System, enable all those events related to
the problem, so they are displayed on the console. E.g. if you think the problem is, or could be, related to the IP pro-
tocol, enable all the events for the IP subsystem by entering:

ELS+ENABLE TRACE SUBSYSTEM IP ALL

Once you are familiar with the distinct messages that appear, you can enable or disable those events containing the
information you need.

140 Configuration and Monitoring

Teldat SA 4 Event Logging System ELS

The Event Logging System allows you to specify which messages are to be shown temporarily or permanently.

The Event Logging System configuration commands allow you to design a permanent message filter, which takes ef-
fect each time the system is switched on or reset.

The monitoring commands allow you to start up temporary filters, which ignore the permanent filter. When the sys-
tem is restarted or reset, the temporary filter is deleted by the software.

Below there are various examples of the Event Logging System.

Example 1. Starting the device

*PROCESS 2 calls the events viewing system

12/29/06 13:07:41 GW.001 System restarted - - ATLAS50 router cold start
12/29/06 13:07:41 GW.002 Portable CGW ATLAS50 Rel 10.7.0 strtd
12/29/06 13:07:41 GW.005 Bffrs: 1762 avail 1762 idle fair 195 low 352
12/29/06 13:07:42 USB registered new driver hub
12/29/06 13:07:42 USB registered new driver serial
click on <Ctrl + p> exiting the events viewing system
*

Example 2. Enabling the Ethernet interface test event

ELS+ENABLE ALL EVENT ETH.045

ELS+ click on <Ctrl + p>
*PROCESS 2
12/29/06 13:18:05 ETH.045 Eth self-test Operational test fld 0000 ifc ethernet0/1
12/29/06 13:18:08 ETH.045 Eth self-test Operational test fld 0000 ifc ethernet0/1
12/29/06 13:18:11 ETH.045 Eth self-test Operational test fld 0000 ifc ethernet0/1

Example 3. GW protocol operation messages

ELS+ENABLE ALL SUBSYSTEM GW ALL

ELS+ click on <Ctrl + p>
*PROCESS 2
12/29/06 13:21:10 GW.026 Mnt ifc ethernet0/0
12/29/06 13:21:11 GW.022 Nt fld slf tst ifc ethernet0/1
12/29/06 13:21:12 GW.019 Slf tst ifc ethernet0/1
12/29/06 13:21:14 GW.026 Mnt ifc x25-node
12/29/06 13:21:14 GW.022 Nt fld slf tst ifc ethernet0/1

Conditional Events through the Access List

This deals with a function (similar to the previous ), which allows you to view (on the console) all traces for all sub-
systems associated to reception and processing of packets, which comply with a series of conditions corresponding
to an IP access list: dropping packets that don’t match this list for example. Therefore you can closely follow the path
taken by the packet, from when it enters the system until it exits, know which subsystems it’s passed through and
locate possible errors.

To activate this, carry out the following:

• Configure the access to the generic access lists configuration environment. For further information, please see
manual Teldat Dm752-I Access Control.
• Add the lists where you want to enable incoming packet marking, so all events associated to packet processing are
displayed on the console. The corresponding command is enable trace condition access-list <1....1999> .
• Enables all events to be viewed as console traces. Here, enter the enable trace all command. This is available
both in the configuration process (CONFIG or P 4/ RUNNING-CONFIG or P 5) as well as in the monitoring process
(MONITOR or P 3). This command should only be used with the corresponding filtering, so events associated to a
packet are displayed. If you don’t add this restriction, all events available in the device are displayed, with the con-
sequential repercussions in performance.

Example:

This is connected to the device through Telnet if you don't want to see events associated to telnet. To do this, config-
ure an access list that excludes port 23 tcp.

feature access-lists
; -- Access Lists user configuration --
access-list 100
entry 1 default
entry 1 deny

Configuration and Monitoring 141

4 Event Logging System ELS Teldat SA

entry 1 source port-range 23 23

entry 1 protocol tcp
;
entry 2 default
entry 2 deny
entry 2 destination port-range 23 23
entry 2 protocol tcp
;
entry 3 default
entry 3 permit
;
exit
;
access-list 5000
entry 1 default
entry 1 permit
;
exit
;
exit
event
; -- ELS Config --
enable trace condition access-list 100
exit
;

Conditional Events for the interface

This deals with a feature allowing you to display, on console, all traces for all subsystems associated to the reception
and processing of a packet through a determined interface: this does not display traces not associated to said pack-
et. You can closely follow the path taken by said packet from when it enters one interface until it exits another, know
which subsystems it’s passed through and locate possible errors.

To activate this, carry out the following:

• Add the interfaces where you want to enable incoming packet marking, so all events associated to the packet pro-
cessing are displayed on the console. The corresponding command is enable trace condition interface
<interface name>. Although you can add any interface in the device to the list, keep in mind that it only makes
sense to select incoming interfaces with an associated physical layer (i.e. those known as base interfaces). You
can also select, as a condition, the packet is one from the free buffers global list, normally locally sourced packets,
or one from a protocol, through the enable trace conditional global-buffers and enable trace condition pro-
tocol <protocol name> commands respectively.
• Enables all events to be viewed as console traces. To do this, use the enable trace all command. This is available
both in the configuration process (CONFIG or P 4 / RUNNING-CONFIG or P 5) as well as in the monitoring pro-
cess (MONITOR or P 3). This command should only be used with the corresponding filtering, so events associated
to a packet are displayed. If you don’t add this restriction, all events available in the device are displayed with the
consequential repercussions in performance.

The example below shows what appears on the screen when this feature is enabled in an ethernet0/0 interface and
a packet encapsulated in IPSec has been received:

01/25/07 09:45:02 POLR.004 dis int ethernet0/0

01/25/07 09:45:02 SNAT.004 NAT_OUT: (172.25.6.0, 172.24.100.129)-> no nat
01/25/07 09:45:02 IPSEC.001 esp encode, spi f5b73944
01/25/07 09:45:02 IPSEC.031 prot 17 (172.25.6.0[5060])->(172.24.100.129[5060]) len 444
01/25/07 09:45:02 IPSEC.003 Pack ESP suc encap (80.36.189.123->83.55.22.247) spi f5b73944
01/25/07 09:45:02 IP.061 add lcl pkt to ip op q
01/25/07 09:45:02 IP.007 80.36.189.123 -> 83.55.22.247
01/25/07 09:45:02 SNAT.003 NAT_IN: (80.36.189.123, 83.55.22.247)-> no nat

Important

Where you enable various conditional events at the same time, bear in mind any condition can produce
a trace.

142 Configuration and Monitoring

Teldat SA 4 Event Logging System ELS

4.4 Event Logging System Commands

This section describes the Event Logging System commands. Each command includes a description, syntax and one
example. Some commands are executed in the configuration procedure at the ELS config> prompt or the ELS con-
fig$ and others, in the monitoring procedure at the ELS+ prompt.

You can also configure the Event Logging System from the dynamic configuration process (at the ELS config$
prompt), so avoiding reboot. However, if you want to maintain the configuration for future reboots, save it through the
save command at the Config$ prompt.

4.4.1 Configuration Process Commands

These commands are executed in the configuration procedure at the ELS config> prompt. The following steps, which
must be performed so the changes made in the Event System take effect, are:
(1) Once the changes have been made, save the configuration (flash or smart card) through the save command at
the Config> prompt.
(2) Restart the device again.
Comand Function
? (HELP) Lists all the commands for the Event Logging System configuration.
ADD Adds an event to a specific group or creates a new group.
APPLY-FILTER Allows the configuration of an events filter to be dynamically applied over the
events being currently generated.
CLEAR Erases all the event and group configuration from the Event Logging System.
CONSOLE Accesses the specific console events menu (CNSL).
DELETE Deletes an event from a specific group or the whole group.
DISABLE Allows you to disable messages, so they are not displayed on screen, and disable
events filtering.
ENABLE Allows you to enable messages, so that they are displayed on screen, and enable
events filtering.
ENVIRONMENT-MONITOR Enables temperature and fan sensor monitoring.
EV-BUFFER Changes the size of the events buffer.
FILTER Configures rules to permit events filtering so that only currently relevant events are
displayed.
LIST Presents information on enabled events, messages and minimum priority of the
saved logs.
NO Eliminates an entry in the events filter list.
NUMBER-EVENTS-LOG Establishes the number of events, registered in the NVRAM, when a RESET oc-
curs in the device.
NVRAM-LOG-PRIORITY Establishes the minimum priority the logs must have, to be saved in the non-
volatile memory.
OPTIONS Modifies the behavior of the Event Logging System.
PPP Accesses a specific PPP events menu.
PRINT Configures additional information to display in each event.
STOP-TRACES Stops saving traces.
TRACE-LEVEL Configures the trace level to display.
VRF Accesses the events filtering through VRF menu.
EXIT Allows you to exit the Event Logging System configuration.

4.4.1.1 ? (HELP)

Lists the available commands in the current prompt. It is also possible to enter “?” after a specific command to list its
options.

Syntax:

ELS config>?

Example 1:

ELS config>?

Configuration and Monitoring 143

4 Event Logging System ELS Teldat SA

add Adds an event to a specific group or creates a new

group
apply-filter Applies dynamically the events filtering configuration
clear Erases all the event and group configuration from the
ELS
console Enters the specific Console (CNSL) events menu
delete Deletes an event from a specific group or the whole
group
disable Disables events
enable Enables events
environment-monitor Enables environment monitor
ev-buffer Sets the events buffer size
filter Adds a filter
list List configuration
no Negates a command or sets its defaults
number-events-log Number of events to be logged in case of fatal error
nvram-log-priority Sets the priority of logs saved
options Modify els subsystem behavior
ppp Enters the specific PPP events menu
print Configure els show options
stop-traces Stops saving traces
trace-level configures subsystem trace level
vrf Enters the specific VRF filter events menu
exit
ELS config>

Example 2:

ELS config>list ?
all Lists the configuration and all the subsystems
configuration Lists the status of the subsystems, groups and events
ev-buffer Lists the events buffer parameters
event Lists the filter level and the specified event message
filter Lists status of the filtering and the configured
filters
groups Lists the groups defined by the user and their content
nvram-log-priority Lists the minimum priority of logs saved
subsystem Lists all the events of a specified subsystem
ELS config>

4.4.1.2 ADD group

Adds an individual event to a precreated group or creates a new group. The names of groups must be composed of
alphabetical characters. Numbers or other types of ASCII characters are not permitted. The name can have a max-
imum extension of 7 characters. The maximum number of groups that can be created is 10 and the maximum num-
ber of events in a group is 20.

Syntax:

ELS config>add <nom_group> <subsystem.num_event>

Example:

ELS config>add
CLI Error: Incomplete command
ELS config>add ?
<1..7 chars> Group name
ELS config>add MYGROUP ?
<1..11 chars> Event
ELS config>add MYGROUP IP.001 ?
<cr>
ELS config>add MYGROUP IP.001
ELS config>

4.4.1.3 APPLY-FILTER

Allows the configuration of events filtering to be dynamically applied over the currently generated events.

Syntax:

144 Configuration and Monitoring

Teldat SA 4 Event Logging System ELS

ELS config>apply-filter

4.4.1.4 CLEAR configuration

Clears all the configuration information from the Event Logging System.

All the groups created, events, and subsystems enabled in configuration are erased. Execute this command followed
by the command save at the Config> prompt to clear the configuration from the flash or smart card.

Syntax:

ELS config>clear

Example:

ELS config>clear ?
<cr>
ELS config>clear
ELS config>

4.4.1.5 CONSOLE

Accesses the specific console events menu.

Example:

ELS config>console
-- Console Events Configuration --
Console Events config>

The console events menu allows you to configure various parameters related to this type of event.

Syntax:

Console Events config> ?

log Includes additional information into console events messages
no Negates a command or set its defaults
wait-time Sets time to wait for console events processing before effective
execution of a command
exit
Console Events config>

4.4.1.5.1 LOG <info>

Activates the inclusion of additional information, within the text, corresponding to the console events.

Syntax:

Console Events config>log <info>

prompt Includes command prompt into console events messages
source-ip Includes ip address and port from user equipment into console
events messages

• < info > type of additional information you wish to include in the event.

LOG PROMPT

Syntax:

Console Events config>log prompt

Example:

Console Events config>log prompt

Console Events config>

By default, the prompt in the console events is not included.

LOG SOURCE-IP

Activates the inclusion of the device IP address and port, the user uses to access the router via telnet, in the console
event user (usr) information field. Where users access via the local console, the text Local Console is displayed to-
gether with the user name.

Configuration and Monitoring 145

4 Event Logging System ELS Teldat SA

Syntax:

Console Events config>log source-ip

Example:

Console Events config>log source-ip

Console Events config>

This following type of message is received in the syslog server:

Jun 13 16:28:55 172.24.73.22 172.24.73.22 CNSL:001 usr rober

(Local Console)
exe IP config>show menu
Jun 13 16:29:02 172.24.73.22 172.24.73.22 CNSL:001 usr edu
(172.24.51.128:55)
exe +config

By default this option is deactivated.

4.4.1.5.2 WAIT-TIME <time>

Establishes the period of time the device waits before actually executing a command so the system is given time to
finalize the whole of the associated console events process (including the sending of syslog messages or snmp
traces).

This delay in the execution is only applicable to the following cases:

• When a command is executed in the active configuration editing process with the exception of the commands:
show menu, show config, show all-config and Ctrl+p (escape character to return to the console manager.)
• The view command allows you to see all Event Logging System messages.

Syntax:

Console Events config>wait-time <time>

<0..1000> Wait time value in 1/10 secs.

Example:

Console Events config>wait-time 5

Console Events config>

By default, the wait time value is 1 tenth of a second.

4.4.1.5.3 NO

Allows you to establish the default values for the configuration parameters for the console events subsystem.

Syntax:

Console Events config>no ?

log Includes additional information into console events messages
wait-time Sets time to wait for console events processing before effective
execution of a command

NO LOG <info>

Deactivates the inclusion of specified additional information (prompt or source-ip) within the text corresponding to
the console events.

Syntax:

Console Events config>no log <info>

prompt Includes command prompt into console events messages
source-ip Includes ip address and port from user equipment into console events
messages

• < info > type of additional information you want to exclude from the event.

Example:

Console Events config>no log prompt

Console Events config>no log source-ip
Console Events config>

146 Configuration and Monitoring

Teldat SA 4 Event Logging System ELS

NO WAIT-TIME

Sets the default time (1 tenth of a second) the device waits before actually executing a command so the system has
time to finalize the whole of the associated console events process (including the sending of syslog messages or sn-
mp traces).

Example:

Console Events config>no wait-time

Console Events config>

4.4.1.6 DELETE group

Deletes an event from an already created group or deletes the whole group. A message is displayed if the event spe-
cified is the last one in the group. When all is specified instead of subsystem.event_num, the whole group is de-
leted.

Syntax:

ELS config>delete <nom_group> <subsystem.event_num>

Example 1:

ELS config>delete ?
<1..7 chars> Group name
ELS config>delete MYGROUP ?
all The whole group
<1..11 chars> Event
ELS config>delete MYGROUP IP.001
ELS config>

Example 2:

ELS config>delete MYGROUP all

ELS config>

4.4.1.7 DISABLE

Selects and disables events so their messages are not displayed on screen, nor sent as traps or transmitted as sys-
log messages. You can also disable groups and subsystems, as well as all the traces if you have previously enabled
them through the enable trace all command. Additionally this allows you to disable events filtering.

Where you’ve selected an incoming interface, to view traces associated to the process and path the packets, re-
ceived in said interface, have followed, the disable trace condition interface <interface name> command allows
you to disable packet marking in said interface. In the same way, you can disable the global buffers and the protocols
condition using the disable trace condition global-buffers and disable trace condition protocol <protocol
name> commands respectively.

Syntax:

ELS config>disable
ALL
EVENT <subsystem.event_num>
GROUPS <nom_group>
SUBSYSTEM <subsystem> <filtered_layer>
FILTER
SNMP-TRAP
EVENT <subsystem.event_num>
GROUPS <nom_group>
SUBSYSTEM <subsystem> <filtered_layer>
SYSLOG
EVENT <subsystem.event_num>
GROUPS <nom_group>
SUBSYSTEM <subsystem> <filtered_layer>
TRACE
ALL
CONDITION INTERFACE <nom_interfaz>
CONDITION GLOBAL-BUFFERS
CONDITION PROTOCOL <nom_protocolo>
EVENT <subsystem.event_num>
GROUPS <nom_group>

Configuration and Monitoring 147

4 Event Logging System ELS Teldat SA

SUBSYSTEM <subsystem> <filtered_layer>

Example:

ELS config>disable TRACE EVENT ICMP.001

ELS config>

This example disables the individual ICMP.001 event so it is not displayed on screen.

Example:

ELS config>disable SYSLOG GROUP MYGROUP

ELS config>

This example disables the MYGROUP group so it is not sent as a syslog message.

Example:

ELS config>disable ALL SUBSYSTEM IP INFO

ELS config>

This example disables events with INFO filter level from the IP subsystem, so they are not shown or sent as either
SNMP traps or syslog messages.

4.4.1.8 ENABLE

Selects and enables events so their messages are displayed on screen, sent as traps or transmitted as syslog mes-
sages. You can also enable groups and subsystems. Additionally this allows you to enable the events filtering and
events filtering.

In Event Logging System user interface on page 139 in this chapter, we explained how to activate the feature known
as conditional events: this is carried out through the enable trace condition interface <interface name> command,
to enable packet marking in a determined interface. In addition, you can filter the events for an IP access list through
the enable trace condition access-list <list> command.

In this way you can view all events associated to packet processing as console traces, by using the enable trace all
command. We do not recommend you use this command, except in cases of using said conditional events feature,
and you restrict the number of traces to be shown to those associated to a packet; contrariwise all traces are shown
and device performance could be seriously affected.

As already mentioned in this section, it is possible to enable the trace by using, as an activation condition, the use of
the free global buffers, which are normally locally sourced packets, or which is a packet processed by a protocol,
through the enable trace condition global-buffers and enable trace condition protocol <protocol name> commands re-
spectively.

If you want to debug the condition events feature, you can enable a special trace through the enable condition-debug
command, which prints every time you uncheck a packet.

Syntax:

ELS config>enable
ALL
EVENT <subsystem.event_num>
GROUPS <nom_group>
SUBSYSTEM <subsystem> <filtered_layer>
CONDITION-DEBUG
FILTER
SNMP-TRAP
EVENT <subsystem.event_num>
GROUPS <nom_group>
SUBSYSTEM <subsystem> <filtered_layer>
SNMP-TRAP-GROUP1
EVENT <subsystem.event_num>
GROUPS <nom_grupo>
SUBSYSTEM <subsystem> <filtered_layer>
SNMP-TRAP-GROUP2
EVENT <subsistema.num_evento>
GROUPS <nom_grupo>
SUBSYSTEM <subsystem> <filtered_layer>
SNMP-TRAP-GROUP3
EVENT <subsystem.event_num>
GROUPS <nom_grupo>

148 Configuration and Monitoring

Teldat SA 4 Event Logging System ELS

SUBSYSTEM <subsystem> <filtered_layer>

SNMP-TRAP-GROUP4
EVENT <subsystem.event_num>
GROUPS <nom_grupo>
SUBSYSTEM <subsystem> <filtered_layer>
SYSLOG
EVENT <subsystem.event_num>
GROUPS <nom_group>
SUBSYSTEM <subsystem> <filtered_layer>
TRACE
ALL
CONDITION INTERFACE <nom_interfaz>
CONDITION GLOBAL-BUFFERS
CONDITION PROTOCOL <nom_protocolo>
EVENT <subsystem.event_num>
GROUPS <nom_group>
SUBSYSTEM <subsystem> <filtered_layer>

Note

On enabling an event as a trap through the snmp-trap command, this is enabled for all trap groups.

Example 1:

ELS config>enable TRACE EVENT ICMP.001

ELS config>

This example enables the individual ICMP.001 event, so it is displayed on screen.

Example 2:

ELS config>enable SYSLOG GROUP MYGROUP

ELS config>

This example enables the MYGROUP group, so it is sent as a syslog message.

Example 3:

ELS config>enable ALL SUBSYSTEM IP INFO

ELS config>

This example enables events with INFO filter level from the IP subsystem, so they are shown, sent as SNMP traps
and as syslog messages.

Important

Do not execute this command during long periods of time, while the device is transferring packets, as a
great deal of time is spent contacting the VISEVEN procedure. If this is executed when communicating
with the Teldat Router through a remote terminal, this may cause the device to spend the majority of
its time contacting the remote terminal.

4.4.1.9 ENVIRONMENT-MONITOR

This enables temperature and fan sensors monitoring.

These checks are executed periodically (every minute) and generate an event if an abnormality is detected. This
event can be one of two types:

• GW.069 Reports a fault in the indicated fan.

• GW.070 Reports a temperature sensor in the device is indicating a rise in temperature to above 69 ºC.

To view said events on the screen, send them as traps or transmit them as syslog messages, you need to enable
them. (For further information, please see the enable command described further on in this section).

Note

This command is only available for devices where you can monitor the fans and/or are equipped with
temperature sensors.

Configuration and Monitoring 149

4 Event Logging System ELS Teldat SA

Syntax:

ELS config>environment-monitor [periodic-event <time_between_events>]

The event is only sent once if the fault is persistent and the periodic-event option hasn’t been configured. If you con-
figure the periodic-event option, the event is sent each time the configured timeout times out and the problem still
hasn’t been resolved.

Example:

ELS config>environment-monitor periodic-event 2h

ELS config>

In this example, the temperature and fan sensors monitoring has been enabled, so the events are sent every 2 hours
where the fault is persistent.

Likewise, this command activates the temperature sensor viewing when the configuration command for the monit-
oring procedure is executed.

Example:

*monitor
Console Operator

+configuration
[…]
Watchdog timer Enabled
CASE 1 fan speed: 0 rpm (0 %)
CPU temperature: 51ºC
ADSL1 temperature: 50ºC
ADSL2 temperature: 53ºC […]

4.4.1.10 EV-BUFFER <num. Lines> <line size>

Allows you to select the amount of memory reserved for the events buffer. There are two parameters to configure:
one, the number is lines (each event is stored in a line) and the second, the size of each line reserved in memory.

Syntax:

ELS config>ev-buffer <num_lines> <line_size>

Example:

ELS config>ev-buffer ?
<2..10000> Number of lines
ELS config>ev-buffer 1000 ?
<28..200> Line size
ELS config>ev-buffer 1000 130
Please restart to take effect.
ELS config>

4.4.1.11 FILTER

Adds a filter so this can be applied.

Event filtering permits filtering within a given event, so relevant information is projected and irrelevant information is
eliminated. The filter has the added advantage that discarded events are not stored so reducing the risk of losing
events due to overflow.

An index is associated to the filters used to determine the order of the application: the lower orders are applied be-
fore the higher orders. The order must be between 1 and 10. You can define a maximum of 10 simultaneous filters.

Another parameter associated to a filter is the application condition where the filter is applied if the condition is ful-
filled. The filters are checked one by one until there are no more or, until one is applied. The condition is only applied
over the event text and not over the event identifier. The condition is given by a text, or a regular expression, to
search for and the position relative to where it is: the text is delimitated by quotation marks; the position where this is
can be given explicitly, or a value – 1 to indicate any position.

The last parameter associated to a filter is the action to be applied. This can be: excluding the event, projecting an
event or accepting an event, rebooting or stop saving traces.

Events filtering can be globally enabled and disabled through the commands enable filter and disable filter respect-
ively.

150 Configuration and Monitoring

Teldat SA 4 Event Logging System ELS

Syntax:

ELS config>filter ?
<1..10> Entry
ELS config>filter 1 ?
default Create a event filter with action exclude and pos ignore
text Text to filter
position Position
action Action to be applied
ELS config>filter 1 text ?
<0..40 chars> Text
ELS config>filter 1 action ?
include includes the trace
exclude excludes the trace
red shows the trace in red
green shows the trace in green
yellow shows the trace in yellow
blue shows the trace in blue
magent shows the trace in magent
cyan shows the trace in cyan
stop-traces stops saving traces
start-traces starts saving traces
ELS config>

Example 1:

A simple example of using the events filter is IP debugging in a device accessed through Telnet: if the IP events are
enabled, the events being searched for appear; however the events of Telnet itself also appear where the quantity of
IP events is excessive. To resolve this you can enable the events filter so all events for the Telnet client IP address
(172.24.78.94) are excluded.

ELS config>filter 1 text "172.24.78.94"

Example 2:

Displays the GW.019 (an internal event where an autotest is carried out over an interface) event in red.

ELS config>filter 1 text "GW.019"

ELS config>filter 1 action red
ELS config>

Example 3 (using regular expressions):

Displays the GW.019 (an internal event where an autotest is carried out over an interface) event in red, but only for
the ethernet0/0 interface.

ELS config>filter 1 text "GW.019.*ethernet0/0"

ELS config>filter 1 action red
ELS config>

Example 4:

Stops saving traces when the first event to include IP address 192.168.212.116 occurs.

ELS config>filter 1 text "192.168.212.116"

ELS config>filter 1 action stop-traces
ELS config>

4.4.1.12 LIST

Lists information on enabled events, created groups, subsystems and configuration.

Syntax:

ELS config>list ?
all Lists the configuration and all the subsystems
configuration Lists the status of the subsystems, groups and events
ev-buffer Lists the events buffer parameters
event Lists the filter level and the specified event message
filter Lists status of the filtering and the configured
filters
groups Lists the groups defined by the user and their content

Configuration and Monitoring 151

4 Event Logging System ELS Teldat SA

nvram-log-priority Lists the minimum priority of logs saved

subsystem Lists all the events of a specified subsystem
ELS config>

LIST ALL

Lists all the created groups together with their events, the status in the subsystems configuration, individual groups
and events, parameters relevant to the size of the storage buffer for events waiting to be displayed on screen, the
possible events filters established as well as if the filtering has been enabled or not and lastly, the minimum priority
the logs must have to be stored in the non-volatile memory.

Example:

ELS config>list all

Group: MYGROUP
IP.002
IP.003
IP.004
Subsystem :GW
Trace :ALL
Syslog :ALL
SNMP-Trap (all groups):ALL
Subsystem :IP
Trace :STANDARD
Syslog :none
SNMP-Trap (all groups):none
Group Trace Syslog SNMP-Trap
MYGROUP Off On On ( group 1 group 3 )
Event Trace Syslog SNMP-Trap
ICMP.001 On Off On ( all groups )
Events Buffer Parameters:
Number of lines: 50 Line size: 208
EVENT FILTER
Events filtering DISABLE

{ num) string, /pos -> action }

1) 172.24.78.94 /-1 -> exclude
2) Rx /1 -> red

Minimum priority of logs saved: Priority 5

ELS config>

LIST CONFIGURATION

This lists the status (enabled or disabled) for the subsystems, groups and individual events, which have been con-
figured. This begins to operate when the device is restarted, provided it has been presaved in the memory.

Suppose you preenabled the GW subsystem to send SNMP traps, to transmit syslog messages and to display (from
VISEVEN) the IP subsystem for an on screen presentation of events, which have a STANDARD filter level, and there
is a group called MYGROUP. Said group is enabled, so it can be notified through syslog messages, and the user en-
abled an ICMP.001 event to be sent as a specific company trap. You would achieve the following results.

Example:

ELS config>list configuration

Subsystem :GW
Trace :ALL
Syslog :ALL
SNMP-Trap (all groups):ALL
Subsystem :IP
Trace :STANDARD
Syslog :none
SNMP-Trap (all groups):none

Group Trace Syslog SNMP-Trap

MYGROUP Off On On ( group 1 group 3 )

Event Trace Syslog SNMP-Trap

ICMP.001 Off Off On (all groups )

152 Configuration and Monitoring

Teldat SA 4 Event Logging System ELS

ELS config>

LIST EV-BUFFER

Lists the parameters relative to the size of the storage buffer where, the events waiting to be displayed on screen are
stored.

Example:

ELS config>list ev-buffer

Events Buffer Parameters:
Number of lines: 1000 Line size: 300
ELS config>

LIST EVENT

Lists the filter level and the specified event message.

Example:

ELS config>list event ICMP.001

Level: UE-ERROR
Message: bd cks 0x%04x (exp 0x%04x) %I -> %I
ELS config>

LIST FILTER

Lists information relevant to the events filtering: general status of the filtering and the configured filters.

Example:

ELS config>list filter

EVENT FILTER
Events filtering DISABLE
{ num) string, /pos -> action }
1) 172.24.78.94 /-1 -> exclude
2) Rx /1 -> red
ELS config>

LIST GROUPS

Lists the names of the groups defined by the user and their content.

Example:

ELS config>list groups

Group: MYGROUP
IP.002
IP.003
IP.004
ELS config>

LIST SUBSYSTEM

Lists all the events for a specified subsystem.

Example:

ELS config>list subsystem icmp

Event Level Message

ICMP.001 UE-ERROR bd cks 0x%04x (exp 0x%04x) %I -> %I

ICMP.002 C-INFO ech %I -> %I
ICMP.003 U-INFO ech rp %I -> %I
ICMP.004 CI-ERROR unhnd typ %d %d %I -> %I
ICMP.005 U-TRACE unhnd brd typ %d %d %I -> %I
ICMP.006 UE-ERROR bd typ %d %d %I -> %I
ICMP.007 C-TRACE addr msk %I -> %I
ICMP.008 C-TRACE addr msk rep %I -> %I
ICMP.009 UI-ERROR no pkt or mem
ICMP.010 UE-ERROR amb addr msk %I -> %I

Configuration and Monitoring 153

4 Event Logging System ELS Teldat SA

ICMP.011 UI-ERROR err %d sndng pkt to ifc %s

ICMP.012 C-INFO rdr %I -> %I to %I
ICMP.013 U-INFO bd prm off %d %I -> %I
ICMP.014 U-TRACE snd %d %d pkt %I -> %I
ICMP.015 UE-ERROR shrt ICMP hdr %d src %I
ICMP.016 U-TRACE %I rdr dest %I to %I
ICMP.017 UE-ERROR Bad rdr from %I, rsn: %S
ICMP.018 U-TRACE Router advertisement received from %I
ICMP.019 UE-ERROR Bad router adv from %I, rsn: %S
ICMP.020 U-TRACE rcvd typ %d %d %I -> %I
ICMP.021 P-TRACE redirect message filtered at interface %s
ICMP.022 P-TRACE unreachable message filtered at interface %s
ELS config>

If the subsystem name is not entered, a list appears with the name, event number and a description of all subsys-
tems.

Example:

ELS config>list subsystem

Name Events Description

ADSL 8 ADSL
AFS 6 Advanced Filtering Subsystem
AINST 23 AutoInstall
ARP 10 Address Resolution Protocol
ASDP 11 Asynchronous Serial Device Proxy
ARLY 41 Alarm Relay
ASYN 5 Asynchronous Serial Line
AT 20 AT Commands Interface
ATM 15 Asynchronous Transfer Mode
BAN 29 Boundary Access Node
BGP 27 Border Gateway Protocol
BR 48 Bridge/Routing
BRS 9 Bandwidth Reservation
BSPF 10 Bridge Spoofing
CIF 34 Encryption
CNSL 4 Console
DEP 30 DEP Forwarder
DHCP 14 DHCP
DHCPC 23 DHCP Client
DLS 459 Data Link Switching
DNAT 12 Dynamic NAT
DNS 30 Domain Name System
EAP 6 EAP
ETH 54 Ethernet
FLT 7 Filter Library
FR 53 Frame Relay
FRBK 8 Frame Relay BACKUP
FTP 4 File Transfer Protocol
G703 25 G703 Digital Interface
GW 64 Router kernel
H323 19 H323
HDLC 11 HDLC Interface
HDSL 57 Symetric High Bitrate Digital Subscriber Line
HSSI 5 High Speed Serial Interface
HOTSPOT 39 HotSpot
HTTP 25 HyperText Transfer Protocol
ICMP 22 Internet Control Message Protocol
IGMP 26 Internet Group Management Protocol
IKE 51 Internet Key Exchange
IP 87 Internet Protocol
IP6 200 IPv6
IPHC 46 IP Header Compression
IPSEC 33 Ip Security
IPX 105 Internetwork Packet Exchange Protocol
ISDN 40 Integrated Services Digital Net
L2TP 56 Layer 2 Tunneling Protocol

154 Configuration and Monitoring

Teldat SA 4 Event Logging System ELS

LAPD 11 ISDN Layer 2

LDAP 16 Lightweight Directory Access Protocol
LLC 33 Logical Link Control
MCF 9 MAC Filtering
NAPT 30 Network Address Port Translation
NBS 50 NetBIOS Support Subsystem
NHRP 58 Next Hop Resolution Protocol
NOE 17 NOE
NSLA 8 Network Service Level Advisor
NSM 82 Network Service Monitor
NTP 25 Network Time Protocol
P3OE 23 PPP over Ethernet
PHYS 4 ISDN BRI Layer 1
PGMO 5 POS Gateway Monitor
POLR 16 Policy routing
PPP 100 Point to Point Protocol
R2 9 R2
RAD 46 Remote Authentication Dial In User Service
RIP 30 IP Routing Information Protocol
RSTP 9 Rapid Spanning Tree Protocol
SCADA 28 SCADA Network
SCDFW 20 SCADA Forwarder
SCEP 17 Simple Certificate Enrollment Protocol
SDLC 95 IBM SDLC
SIP 16 SIP
SL 36 Serial Line
SMGT 9 System Management
SNAT 5 Static NAT
SNMP 26 Simple Network Management Protocol
SPF 61 Open SPF-Based Routing Protocol
SRT 89 Source Routing Transparent Bridge
STP 42 Spanning Tree Protocol
STUN 3 STUN
SYNC 2 Synchronous Serial Line
TCP 55 Transmission Control Protocol
TIDP 18 T. IP Discovery Protocol
TKR 46 Token Ring
TLNT 8 Telnet
TLPHY 23 TLPHY
TNIP 39 IP Tunnel
TTTP 18 T. Transaction Transfer Protocol
TVRP 26 T. Virtual Router Protocol
UDAFO 41 UDAFO Forwarder
UDP 4 User Datagram Protocol
VOIP 14 Voice over IP
VRRP 8 Virtual Router Redundancy Protocol
WLAN 4 Wireless LAN
X252 23 X.25 Layer 2
X253 26 X.25 Layer 3
XN 21 Core Xerox Network System

ELS config>

Command history:
Release Modification
11.00.05 SMGT event was introduced as of version 11.00.05.
11.01.00 SMGT event was introduced as of version 11.01.00.

LIST NVRAM-LOG-PRIORITY

Lists the minimum priority of the logs saved in the non-volatile memory.

Example:

ELS config>LIST NVRAM-LOG-PRIORITY

Minimum priority of logs saved: Priority 5
ELS config>

Configuration and Monitoring 155

4 Event Logging System ELS Teldat SA

4.4.1.13 NO

Allows you to eliminate a given filter, or to reestablish the default value, for parameters relative to the size of the stor-
age buffer, where the events waiting to be displayed on screen are stored or for the minimum priority of the logs
saved in the non-volatile memory.

You can also eliminate and reestablish the configuration over the enabled, or disabled, events at any point.

Syntax:

ELS config>no ?
environment-monitor Enables environment monitor
disable Disables events
enable Enables events
ev-buffer Sets default events buffer size
filter Eliminates a given filter
number-events-log Number of events to be logged in case of fatal error
nvram-log-priority Sets the default priority of logs saved
print Configure els show options
stop-traces Stops saving traces
trace-level Configures subsystem trace level
ELS config>

NO ENVIRONMENT-MONITOR

Disables the temperature and fan sensor monitoring.

Example:

ELS config>no environment-monitor

ELS config>

This example disables the temperature and fan sensor monitoring.

NO DISABLE

This selects and reestablishes the event default parameters (disabled) shown on the screen, sent as traps or trans-
mitted as syslog messages. You can reestablish groups and subsystems.

Example:

ELS config>no disable TRACE GROUPS miGrupo

ELS config>

This example reestablishes the default values for events in miGrupo, so they are displayed on the screen and the
corresponding entry is deleted from the configuration.

NO ENABLE

This selects and reestablishes the event default parameters (enabled) shown on the screen, sent as traps or trans-
mitted as syslog messages. You can reestablish groups and subsystems.

Example:

ELS config>no enable SNMP-TRAP SUBSYSTEM ARP ALL

ELS config>

This example reestablishes default values, for events with the ALL filter level, for the ARP subsystem so they are
sent as SNMP traps, and the corresponding entry deleted from the configuration.

Example:

ELS config>no enable SYSLOG EVENT IP.007

ELS config>

This example reestablishes default values for the individual IP.007 event, so it is transmitted as a syslog message
and the corresponding entry is deleted from the configuration.

NO EV-BUFFER

Reestablishes default values for parameters relative to the storage buffer for events waiting to be displayed as traces
on the console (VISEVEN process), parameters that allow you to select the amount of reserved memory. Said de-

156 Configuration and Monitoring

Teldat SA 4 Event Logging System ELS

fault values are 50 lines, or messages, and 208 bytes per line.

Example:

ELS config>no ev-buffer

ELS config>

NO FILTER

Eliminates a previously configured filter.

Example:

ELS config>no filter 2

ELS config>

NO PRINT

Eliminates additional information to be printed with each preconfigured event.

Example:

ELS config>no print extra-info

ELS config>

NO STOP TRACES

Eliminates the order to stop saving traces.

Example:

ELS config>no stop-traces

ELS config>

NO NUMBER-EVENTS-LOG

Establishes the default value for the number of events, which are stored in the non-volatile memory when a RESET
occurs in the device.

Example:

ELS config>no number-events-log

ELS config>

NO NVRAM-LOG-PRIORITY

Establishes the default value for the minimum priority for the logs stored in the non-volatile memory (priority 5).

Example:

ELS config>no nvram-log-priority

ELS config>

4.4.1.14 NUMBER-EVENTS-LOG

This command configures the number of events registered in the non-volatile memory when a RESET occurs in the
device. Default is 3, the range of configurable values is from 3 to 10000. Knowing the latest events generated, before
an error occurs, is very useful to detect the cause of said error. We suggest configuring a value greater than the de-
fault value for this parameter. This gives you more information to diagnose the problem.

Example:

ELS config>number-events-log ?
<3..10000> value in the specified range
ELS config>number-events-log 100
ELS config>

4.4.1.15 NVRAM-LOG-PRIORITY

Configures the minimum priority the logs must have to be saved. A priority, between 1 and 5, is defined for each log
(1 being the highest priority and 5 the lowest). Given the capacity of the non-volatile memory is limited (the logs are
saved in a circular queue), you may wish to save only the highest priority logs (not the lowest ones).

Configuration and Monitoring 157

4 Event Logging System ELS Teldat SA

Logs related to device startups take priorities between 1 and 3. The rest of them (accessing the device, configuration
modifications etc.) are allocated priorities between 4 and 5.

Example:

ELS config>nvram-log-priority ?
<1..5> Minimum priority of logs saved
ELS config>nvram-log-priority 5
ELS config>

4.4.1.16 OPTIONS

Allows you to modify Event Logging System behavior.

Syntax:

ELS config>options ?
circular-buffer Enable circular buffer
no Negate options
time-as-incremental Show time as incremental in milliseconds
time-as-ticks Show time as ticks
time-stamp Include time in events
usb-save Save events on external USB
ELS config>

CIRCULAR-BUFFER

Establishes the default behavior for the Event Logging System, corresponding to events entering in the circular buf-
fer. The new events are always added to the circular buffer and if this is full, the oldest events are dropped.

NO

Allows you to deactivate options enabled by default. These are as follows:

4.4.1.16.1 CIRCULAR BUFFER

The Event Logging System stops entering events in the viewing circular buffer when it is full. When the events can-
not be seen, the buffer is full, CPU time is not taken up and system performance is increased. A second effect is the
latest events are lost, not the oldest.

4.4.1.16.2 TIME-AS-INCREMENTAL

Deactivates the milliseconds mark with the time elapsed since the last event entry.

4.4.1.16.3 TIME-AS-TICKS

Deactivates the mark with the ticks counter.

4.4.1.16.4 TIME STAMP

When viewing this the date and the time do not appear. This means the real clock time is not consulted, diminishing
the probability of losing events, and performance improves.

Example:

ELS config>options not-time

ARP.002 Pkt in 1 1 800 ethernet0/0
ARP.008 rcv IP RQST 172.24.0.203->172.24.0.206 ifc ethernet0/0
ARP.002 Pkt in 1 1 800 ethernet0/0
ARP.008 rcv IP RQST 172.24.76.2->172.24.0.25 ifc ethernet0/0
ARP.002 Pkt in 1 1 800 ethernet0/0
ARP.008 rcv IP RQST 172.24.79.3->172.24.78.99 ifc ethernet0/0

4.4.1.16.5 USB-SAVE

Deactivates events dumping in a massive USB external storage device. Please see the usb-save command options.

TIME-AS-INCREMENTAL

The events are marked with a value measured in milliseconds, corresponding to the time lapsed since the last event

158 Configuration and Monitoring

Teldat SA 4 Event Logging System ELS

was entered until a new one arrives.

Example:

ELS config>options time-as-incremental

200.892508ms IP.007 192.168.212.4 -> 192.168.212.116
0.007363ms POLR.004 dis int ethernet0/0
0.007878ms IP.036 rcv pkt prt 1 frm 192.168.212.4
0.007090ms ICMP.002 ech 192.168.212.4 -> 192.168.212.116
0.008454ms IP.061 add lcl pkt to ip op q
0.009939ms IP.007 192.168.212.116 -> 192.168.212.4

TIME-AS-TICKS

The events are marked with a tick counter instead the date and time and is consequently more accurate.

Example:

ELS config>options time-as-ticks

4065675.488814ms IP.036 rcv pkt prt 1 frm 192.168.212.4
4065675.495965ms ICMP.002 ech 192.168.212.4 -> 192.168.212.116
4065675.504844ms IP.061 add lcl pkt to ip op q
4065675.514450ms IP.007 192.168.212.116 -> 192.168.212.4

TIME-STAMP

Establishes default behavior for the Event Logging System, corresponding to time-stamp viewing.

USB-SAVE

Option to save the device’s active events in a massive storage device connected to the external USB. The events
are saved in a file (known as event.log) in the root directory of the first detected partition. The partition must be
formatted with a FAT or VFAT files system. If the file exists, the new events are added to the end, inserting a session
start mark. The existing information is never deleted.

Example:

################################################################################
# New log session started #
################################################################################
01/01/00 00:00:16 GW.001 System restarted -- H1+ WAN IPSec router cold start
01/01/00 00:00:16 GW.002 Portable CGW H1+ WAN IPSec Rel 10.08.29-Alfa strtd
01/01/00 00:00:17 GW.005 Bffrs: 1471 avail 1441 idle fair 114 low 294

If the device startup configuration has this command configured, the USB device must be connected before starting
up the device. If a device is not detected as connected, said dumping does not occur even if you subsequently con-
nect a device.

The command can dynamically activate and deactivate (option no save-usb). You must connect the USB device to
the external connector before dynamically activating the command. If there is no massive storage device connected
to the USB connector, the dynamic command produces an error. If events dumping in the external USB is activated,
you can deactivate it by executing the no save-usb option command in the dynamic configuration. You must always
dynamically deactivate the events dumping to USB before removing the external storage device. If you extract this
without deactivating dumping, the latest events are lost and you won’t be able to dynamically initiate dumping; you'll
have to restart the device.

By default, events dumping in an external USB device is disabled.

Example:

ELS config>options usb-save

Note

This command is only available in some devices with a USB interface.

4.4.1.17 PPP

Accesses the specific PPP events menu. For further information, please see manual Teldat Dm710-I Interface PPP .

Example:

Configuration and Monitoring 159

4 Event Logging System ELS Teldat SA

ELS config>ppp
-- PPP Events Configuration --
PPP Events config>

4.4.1.18 PRINT

Allows you to specify additional information to print for each event. The additional information is printed in a separate
line after the main event and does not display the date or time.

PRINT EXTRA-INFO

Prints the vrf, the input and output interfaces.

Example:

04/15/08 13:13:17 AFS.001 IP IN src 172.24.100.130 dst 172.24.100.129 prt TCP in ifc
ethernet0/0 -> ACCEPTED
AFS.001 [vrf: <main> inifc: ethernet0/0 outifc: ppp1]

PRINT IP-HEADER

Prints the IP header. The IP header is not available in all the events; in events where it isn’t available, no additional
information is displayed.

Example:

04/15/08 13:13:17 AFS.001 IP IN src 172.24.100.130 dst 172.24.100.129 prt TCP in ifc
ethernet0/0 -> ACCEPTED

4.4.1.19 STOP-TRACES

Stops the events from being logged. Despite the events not being saved, they are analyzed to see if they match a
configured filter.

This can be useful when you want the Event Logging System to startup on detection of a specific event. The device
boots with the Event Logging System detained and a filter is configured to detect the specified event and associated
to a start traces action .

4.4.1.20 TRACE-LEVEL

Allows you to configure the trace level to display for a determined subsystem. The minimum level (the least number
of traces) is error; the maximum level (the greatest number of traces) is excessive.

The events level is not available for all event subsystems, only for a few.

The available trace levels are as follows:

• error: messages produced due to grave errors that can make the associated feature stop executing.
• warning: messages produced due to unexpected errors while the associated feature is executing.
• info: traces related to the normal execution of the associated feature.
• debug: debug traces.
• msg-dump: displays traces related to messages exchanged while the associated feature is executing.
• excessive: displays all the available traces.

Each level includes all the previous levels. If, for example, the debug trace level is enabled, the info, warning and er-
ror trace levels are also included.

Syntax:

ELS config>trace-level <subsystem> <error-level>

Example:

ELS config>trace-level wlan debug

4.4.1.21 VRF

Accesses events filtering through the VRF menu.

Example:

160 Configuration and Monitoring

Teldat SA 4 Event Logging System ELS

ELS config>vrf
-- VRF Events Configuration --
VRF Filter Events Config>?

You can configure the VRFs , you want to view the events for, through the menu.

Syntax:

ELS config>vrf

-- VRF Events Configuration --

VRF Filter Events Config>vrf ?
<1..32 chars> VRF name

Example:

VRF Filter Events Config>vrf vrf-1

VRF Filter Events Config>vrf vrf-2

4.4.1.22 EXIT

Allows you to exit the Event Logging System configuration and return to the Config> prompt.

Syntax:

ELS config>exit

Example:

ELS config>exit
Config>

4.4.2 Monitoring process commands

These commands are executed in the monitoring process at the ELS+ prompt.

Changes made in this procedure are automatically executed and are lost when the device is restarted. These com-
mands allow you to enable events during execution.
Command Function
? (HELP) Lists all commands for monitoring the Event Logging System.
CLEAR-ACTIVES Allows you to disable all enabled events at a given time.
CONDITION-DEBUG Displays useful information if you wish to debug the condition event feature.
DISABLE Allows you to disable event messages so they are not displayed on the screen,
nor sent as syslog messages or as specific company traps.
ENABLE Allows you to enable event messages to be displayed on the screen, sent as sys-
log messages or as specific company traps.
EVENT-STORE Allows you to enable event messages to be stored in flash memory when CIT
crashes.
FILTER Configures the rules permitting event filtering so only currently relevant events are
displayed.
HIDE Prevents events from being displayed in the active process. At this point, events
can only be viewed from VISEVEN.

This command is available from any process, although it does not appear when
requesting all available commands: to execute said command enter the full com-
mand name.
LIST Lists information on established events and messages.
NO Disables an option.
NVRLOG Allows you to view logs stored in the non-volatile memory, as well as initialize this.
RESTORE-CONFIGURATION Allows you to activate the current Event Logging System configuration, previously
entered in the corresponding configuration process menu, without having to save
and reboot the device.
SHOW-STORED-LOG Shows a stored events log, generated when CIT crashes, and the event-store op-
tion is enabled.
VIEW Permits events to be displayed in the active process. From here, the events can-
not be viewed from VISEVEN.

Configuration and Monitoring 161

4 Event Logging System ELS Teldat SA

This command is available from any process, although it does not appear when
requesting all available commands: to execute this enter the full command name.
EXIT Allows you to exit event monitoring.

4.4.2.1 ? (HELP)

Lists the commands available for the current prompt. It is also possible to enter ? after a specific command to list its
options.

Syntax:

ELS+?

Example 1:

ELS+?
clear-actives Disable all enabled events at a given time
condition-debug Monitoring options of condition events debugging
disable Disable event messages
enable Enable event messages
filter Configure the rules permitting events filtering
hide Prevent the events from being displayed
list List information on established events and messages
nvrlog View/Initialize the logs stored in the non-volatile
memory
restore-configuration Activate the current Events Logging System
configuration
view Display the events in the active process
exit
ELS+

Example 2:

ELS+LIST ?
active List the enabled events of the specified subsystem
condition List the interfaces where packet marking has been enabled
event List event information
groups List group information
subsystem List subsystem information
ELS+

4.4.2.2 CLEAR-ACTIVES

Allows you to disable all enabled events at a given time.

Syntax:

ELS+clear-actives

Example:

ELS+clear-actives
Do you want to disable all active events?(Y/N)(N): y
All events disabled
ELS+

4.4.2.3 CONDITION-DEBUG

Provides useful information if you want to debug the condition events feature, which we saw in Event Logging Sys-
tem user interface on page 139. To exclude events generated by packets that have not been checked, a semaphore
object, which tells the system when a packet is checked, is used. Said semaphore blocks when a packet is checked,
when one of the enabled conditions has been fulfilled, and unblocks when a packet is no longer checked.

Syntax:

ELS+condition-debug ?
semaphore-clear Clear the condition semaphore
semaphore-dump Dump information on the condition semaphore

The semaphore-clear option is used to manually unblock the semaphore, so allowing another packet to be checked

162 Configuration and Monitoring

Teldat SA 4 Event Logging System ELS

when one of the enabled conditions has been fulfilled.

Information on the semaphore state displayed, when the semaphore-dump option is used, is as follows:

• Semaphore state: displays 1 if the semaphore is blocked and 0 if it isn’t.

• Buffer address: address for the memory where the checked packet is located and that blocked the semaphore.
• Trigger condition : condition triggering packet checking.
• Calls sequence: calls sequence in the program code the semaphore is blocked through.

Example:

ELS+condition-debug semaphore-dump
==================================
..: Condition events semaphore :..
==================================
Semaphore state: 1
Buffer address: 0x01d1cd8c
Trigger condition: interface ethernet0/0
Calls sequence: 00640490<-0066AD14<-00B62830<-00D62E20<-00D63044<-

ELS+

4.4.2.4 DISABLE

Selects and disables events so their messages are not displayed on the screen in VISEVEN, nor sent as SNMP
traps or syslog messages. You can disable groups and subsystems, as well as all the traces if you have pre-enabled
them through the enable trace all command. This also allows you to disable events filtering.

Where you’ve selected an incoming interface, to view the traces associated to the process and path the packets re-
ceived in said interface have followed, the disable trace condition interface <interface name> command allows
you to disable packet marking in this interface.

You can also disable the global buffers and the protocols condition using the disable trace condition global-buf-
fers and disable trace condition protocol <protocol name> commands respectively.

Syntax:

ELS+disable
ALL
EVENT <subsystem.event_num>
GROUPS <nom_group>
SUBSYSTEM <subsystem> <filtered_layer>
SYSLOG
EVENT <subsystem.event_num>
GROUPS <nom_group>
SUBSYSTEM <subsystem> <filtered_layer>
FILTER
TRACE
ALL
CONDITION INTERFACE <interface name>
CONDITION GLOBAL-BUFFERS
CONDITION PROTOCOL <nom_protocolo>
EVENT <subsystem.event_num>
GROUPS <nom_group>
SUBSYSTEM <subsystem> <filtered_layer>
SNMP-TRAP
EVENT <subsystem.event_num>
GROUPS <nom_group>
SUBSYSTEM <subsystem> <filtered_layer>

Example 1:

ELS+disable trace event icmp.001

ELS+

This example disables the ICMP.001 individual event, so it is not displayed on screen.

Example 2:

ELS+disable syslog group mygroup

ELS+

Configuration and Monitoring 163

4 Event Logging System ELS Teldat SA

This example disables the MYGROUP group, so events pertaining to said group are not notified via syslog mes-
sages.

Example 3:

ELS+disable all subsystem ip info

ELS+

This example disables the INFO filter level events for the IP subsystem, so they are not displayed nor sent as SNMP
traps or through syslog messages.

4.4.2.5 ENABLE

Selects and enable events so their messages are displayed on the screen, sent as traps or transmitted through sys-
log messages. You can enable groups and subsystems and also events filtering.

In Event Logging System user interface on page 139 in this chapter, we explained how to activate the feature known
as conditional events: this is done by using the enable trace condition interface <interface name> command, to
enable packet marking in a determined interface. You can view all events associated to packet processing as con-
sole traces by subsequently using the enable trace all command. We do not recommend you use this command ex-
cept when using said conditional events feature, and that you restrict the number of traces to be shown to those as-
sociated to a packet. Contrariwise all traces are shown and device performance could be seriously affected.

As indicated, you can enable the trace by using, as an activation condition, the use of the free global buffers, which
are normally locally sourced packets, or a packet processed by a protocol, using the enable trace condition global-
buffers and enable trace condition protocol <protocol name> commands respectively.

Syntax:

ELS+enable
ALL
EVENT <subsystem.event_num>
GROUPS <nom_group>
SUBSYSTEM <subsystem> <filtered_layer>
SYSLOG
EVENT <subsystem.event_num>
GROUPS <nom_group>
SUBSYSTEM <subsystem> <filtered_layer>
FILTER
TRACE
ALL
CONDITION INTERFACE <interface name>
CONDITION GLOBAL-BUFFERS
CONDITION PROTOCOL <nom_protocolo>
EVENT <subsystem.event_num>
GROUPS <nom_group>
SUBSYSTEM <subsystem> <filtered_layer>
SNMP-TRAP
EVENT <subsystem.event_num>
GROUPS <nom_group>
SUBSYSTEM <subsystem> <filtered_layer>
SNMP-TRAP-GROUP1
EVENT <subsystem.event_num>
GROUPS <nom_group>
SUBSYSTEM <subsystem> <filtered_layer>
SNMP-TRAP-GROUP2
EVENT <subsystem.event_num>
GROUPS <nom_group>
SUBSYSTEM <subsystem> <filtered_layer>
SNMP-TRAP-GROUP3
EVENT <subsystem.event_num>
GROUPS <nom_group>
SUBSYSTEM <subsystem> <filtered_layer>
SNMP-TRAP-GROUP4
EVENT <subsystem.event_num>
GROUPS <nom_group>
SUBSYSTEM <subsystem> <filtered_layer>

164 Configuration and Monitoring

Teldat SA 4 Event Logging System ELS

Note

When you enable an event as a trap, through the snmp-trap command, you enable it for all trap
groups.

Example 1:

ELS+enable trace event icmp.001

ELS+

This example enables an ICMP.001 individual event, so it's displayed on screen.

Example 2:

ELS+enable syslog group mygroup

ELS+

This example enables the MYGROUP group: events applying to it are notified through syslog messages.

Example 3:

ELS+enable all subsystem ip info

ELS+

This example enables the INFO filter level events for the IP subsystem, so they are displayed on screen, sent as SN-
MP traps and transmitted through syslog messages.

Important

Do not execute this command during long periods of time while the device is transferring packets, since
a great deal of time is spent in communicating with VISEVEN. If you execute this command when it is
communicating with the Teldat Router, through a remote terminal, this may give rise to the device
spending most of its time communicating with the remote terminal, with a subsequent drop in perform-
ance.

4.4.2.6 EVENT-STORE

Command History:
Release Modification
11.00.05 This command is introduced in version 11.00.05
11.01.01 This command is introduced in version 11.01.01.

Allows you to store the last event, allocated at event buffer, in a flash unit if CIT crashes . This is used for debugging
purposes. The use of this command requiresin-depth knowledge of Teldat Router software and should only be used
when expressly indicated byTeldat's personnel.

Syntax:

ELS+event-store ?
<cr>
ELS+

When this command is executed a message is shown warning the user on the possible operation risks. If said com-
mand is confirmed, the event storing system is enabled and the event buffer will be saved to flash if CIT crashes.

ELS+event-store
WARNING: This command may cause future performance or behaviour issues
Do you want to enable event-store?
Enable event-store(Yes/No)?yes
Event store is enabled. EVENTLOG.EV will be generated when CIT crashes
ELS+

If a previous log was generated, the command issues on warning on this and asks for confirmation.

ELS+event-store
WARNING: This command may cause future performance or behaviour issues
Do you want to enable event-store?
Enable event-store(Yes/No)?yes
Event store is enabled. EVENTLOG.EV will be generated when CIT crashes

Configuration and Monitoring 165

4 Event Logging System ELS Teldat SA

There is a previous event log saved

Are you sure to enable it?(This action may delete the previous one)
Enable event-store(Yes/No)? yes
ELS+

4.4.2.7 FILTER

Allows you to add, change or delete filters individually. Enable the filter through the enable filter command to active
it.

For further information, please see the filter command from the event configuration menu.

Syntax:

ELS+filter
add Add/Change filters individually
del Delete filters individually
list Display the status of events filtering
ELS+

FILTER ADD

Adds an entry to the filter table. If this already exists, it’s replaced.

Syntax:

ELS+filter add <entry_number> <text> <position> ACTION <action>

Example:

ELS+filter add 2 "rx" 1 action red

ELS+

FILTER DEL

Deletes an entry from the filter table.

Syntax:

ELS+filter del <entry_number>

Example:

ELS+filter del 2

FILTER LIST

Displays a list of the filter table.

Syntax:

ELS+filter list

Example:

ELS+filter list
EVENT FILTER
State: disabled
1) 172.24.78.94 /-1 -> Excl
2) rx /1 -> Red
3) --- - ---
4) --- - ---
5) --- - ---
6) --- - ---
7) --- - ---
8) --- - ---
9) --- - ---
10) --- - ---

ELS+

166 Configuration and Monitoring

Teldat SA 4 Event Logging System ELS

4.4.2.8 HIDE

Prevents events from being displayed in the active process. Subsequently, events can only be viewed from VISEV-
EN.

This command is available from any process, although it does not appear when requesting all the available com-
mands, to execute this enter the full command name.

Syntax:

ELS+hide

Example:

ELS+hide
ELS+

4.4.2.9 LIST

Lists information on events enabled, groups created and subsystems. This also displays the interfaces enabled to
use the conditional events feature.

Syntax:

ELS+list ?
active List the enabled events of the specified subsystem
condition List the interfaces where packet marking has been enabled
event List event information
groups List group information
subsystem List subsystem information
ELS+

LIST ACTIVE

Example:

ELS+list active arp

Actives Count Trace Syslog Snmp-Trap
ARP.001 0 on off on ( group 1 )
ELS+

This lists the enabled events in the ARP subsystem, the number of times each event has occurred and the enabling
vector for each event.

Note

Events with always filter levels are always enabled to be displayed on screen (e.g. GW.001). There are
also events enabled as traps, which cannot be disabled as they generate the SNMP generic traps (e.g.
GW.021® link up).

LIST CONDITION

Example:

ELS+list condition
Established conditions:
Traces for packets received on ethernet0/0
ELS+

Lists the interfaces where packet marking has been enabled, so they can be followed, and the traces associated to
their processing are displayed. For further information, please see section 3 (Event Logging System User Interface),
or the section explaining the use of the enable/disable trace condition interface <interface name> and enable/
disable trace all commands.

LIST EVENT

Example:

ELS+list event icmp.001

Level: UE-ERROR

Configuration and Monitoring 167

4 Event Logging System ELS Teldat SA

Message: bd cks 0x%04x (exp 0x%04x) %I -> %I

Count: 0 Status: enable as (Trace) (Syslog message) (SNMP Trap)

ELS+

Lists the ICMP.001 event information.

Let’s suppose the event is enabled to be displayed on screen, sent as a syslog message and as a specific company
trap, the information we can receive is shown in following example.

LIST GROUP

Example:

ELS+list group
Group: MYGROUP
Event Trace Syslog Snmp-Trap
IP.002 on off on ( all groups )
IP.003 on off on ( group 2 group 4 )
IP.004 on off off
Globaly enable as: (Trace)
ELS+

This shows the group name, the set of events it's made up of, the enabling status of each event and the current glob-
al status of group enabling.

If all the group events are enabled to be displayed on screen and some to be sent as traps and syslog messages,
the information we receive is as shown in following example.

LIST SUBSYSTEM

Example 1:

ELS+list subsystem icmp

Event Level Message

ICMP.001 UE-ERROR bd cks 0x%04x (exp 0x%04x) %I -> %I

ICMP.002 C-INFO ech %I -> %I
ICMP.003 U-INFO ech rp %I -> %I
ICMP.004 CI-ERROR unhnd typ %d %d %I -> %I
ICMP.005 U-TRACE unhnd brd typ %d %d %I -> %I
ICMP.006 UE-ERROR bd typ %d %d %I -> %I
ICMP.007 C-TRACE addr msk %I -> %I
ICMP.008 C-TRACE addr msk rep %I -> %I
ICMP.009 UI-ERROR no pkt or mem
ICMP.010 UE-ERROR amb addr msk %I -> %I
ICMP.011 UI-ERROR err %d sndng pkt to ifc %s
ICMP.012 C-INFO rdr %I -> %I to %I
ICMP.013 U-INFO bd prm off %d %I -> %I
ICMP.014 U-TRACE snd %d %d pkt %I -> %I
ICMP.015 UE-ERROR shrt ICMP hdr %d src %I
ICMP.016 U-TRACE %I rdr dest %I to %I
ICMP.017 UE-ERROR Bad rdr from %I, rsn: %S
ICMP.018 U-TRACE Router advertisement received from %I
ICMP.019 UE-ERROR Bad router adv from %I, rsn: %S
ICMP.020 U-TRACE rcvd typ %d %d %I -> %I
ICMP.021 P-TRACE redirect message filtered at interface %s
ICMP.022 P-TRACE unreachable message filtered at interface %s
ELS+

Example 2:

ELS>list subsystem
Name Events Description

AAA 49 Authentication, Authorization, Accounting

ACT 1 Alsa Custom Trap
ACL 3 Access List
ADSL 8 ADSL
AFS 59 Advanced Filtering Subsystem

168 Configuration and Monitoring

Teldat SA 4 Event Logging System ELS

ARP 18 Address Resolution Protocol

ASDP 25 Asynchronous Serial Device Proxy
ASYN 5 Asynchronous Serial Line
AT 21 AT Commands Interface
ATM 15 Asynchronous Transfer Mode
BAN 29 Boundary Access Node
BFD 53 Bidirectional Forwarding Detection
BGP 92 Border Gateway Protocol
BR 48 Bridge/Routing
BRS 19 Bandwidth Reservation
BSPF 10 Bridge Spoofing
CDP 6 Cisco Discovery Protocol
CELL 24 Cellular AT Commands Interface
CFLOW 10 CFLOW
CFM 10 Connectivity Fault Management
CIF 34 Encryption
CNSL 4 Console
DHCP 16 DHCP
DHCPC 23 DHCP Client
DH6C 12 IPv6 DHCP Client
DH6S 9 IPv6 DHCP Server
DLS 459 Data Link Switching
DNAT 13 Dynamic NAT
DNS 30 Domain Name System
DNSU 27 DNS Updater Feature
DOT1X 27 IEEE 802.1X Authentication Protocol
EAP 8 EAP
EOAM 13 Ethernet OAM
ETH 55 Ethernet
FLT 7 Filter Library
FR 53 Frame Relay
FRBK 8 Frame Relay BACKUP
FTP 4 File Transfer Protocol
G703 31 G703 Digital Interface
GW 72 Router kernel
GW104 20 Gateway IEC104
H323 23 H323
HDLC 15 HDLC Interface
HDSL 6 HDSL
HOTSPOT 39 Hotspot
HTTP 25 HyperText Transfer Protocol
I101 12 IEC101 Gateway Network
ICMP 22 Internet Control Message Protocol
ICMP6 14 Internet Control Message Protocol version 6
IGMP 29 Internet Group Management Protocol
IKE 76 Internet Key Exchange
IP 90 Internet Protocol
IP6 92 IPv6
IPHC 46 IP Header Compression
IPSECFT 51 IPSec fault tolerant
IPSEC 35 Ip Security
ISDN 41 Integrated Services Digital Net
L2TP 56 Layer 2 Tunneling Protocol
LAPD 11 ISDN Layer 2
LDAP 16 Lightweight Directory Access Protocol
LLC 33 Logical Link Control
LLDP 3 Link Layer Discovery Protocol
MCF 9 MAC Filtering
MGCP 23 Media Gateway Control Protocol
MLD6 17 Multicast Listener Discovery for IPv6
MROUTE 6 Multicast Routing
MSDP 42 Multicast Source Discovery Protocol
MTC 18 MTC messages
NAPT 30 Network Address Port Translation
NBS 50 NetBIOS Support Subsystem
ND 117 Neighbour Discovery IPv6
NEIG 13 Neighbour IPv6

Configuration and Monitoring 169

4 Event Logging System ELS Teldat SA

NHRP 58 Next Hop Resolution Protocol

NIC 23 NIC Interface
NOE 24 NOE
NSLA 8 Network Service Level Advisor
NSM 83 Network Service Monitor
NTP 42 Network Time Protocol
P3OE 25 PPP over Ethernet
PHYS 4 ISDN BRI Layer 1
PIM 89 Protocol Independent Multicast
PGMO 5 POS Gateway Monitor
POLR 20 Policy routing
PPP 100 Point to Point Protocol
QMI 23 QUALCOMM MSM Interface
R2 9 R2
RAD 59 Remote Authentication Dial In User Service
RIP 36 IP Routing Information Protocol
RIP6 16 RIPng protocol
RSTP 10 Rapid Spanning Tree Protocol
SCADA 29 SCADA Network
SCCP 8 SCCP
SCDFW 20 SCADA Forwarder
SCEP 17 Simple Certificate Enrollment Protocol
SDLC 95 IBM SDLC
SIP 23 SIP
SL 36 Serial Line
SMGT 9 System Management
SNAT 5 Static NAT
SNMP 29 Simple Network Management Protocol
SPF 76 Open SPF-Based Routing Protocol
SPF6 48 Open SPF-Based Routing Protocol version 3
SPI 16 SPI feature
SRT 91 Source Routing Transparent Bridge
SRVP 22 Service Policy
SSH 79 Secure Shell
SSL 1 Secure Socket Layer Subsystem
STP 48 Spanning Tree Protocol
STUN 3 STUN
SYNC 5 Synchronous Serial Line
TCP 55 Transmission Control Protocol
TFTP 6 Trivial File Transfer Protocol
TIDP 18 T. IP Discovery Protocol
TLNT 10 Telnet
TLPHY 33 TLPHY
TNIP 60 IP Tunnel
TVRP 29 T. Virtual Router Protocol
UDP 9 User Datagram Protocol
VOIP 14 Voice over IP
VRRP 16 Virtual Router Redundancy Protocol
VRRP6 13 Virtual Router Redundancy Protocol for IPv6
WLAN 12 Wireless LAN
WWAN 16 Wireless WAN Interface
X252 23 X.25 Layer 2
X253 27 X.25 Layer 3
X28 6 X28 Network

ELS+

Command history:
Release Modification
11.00.05 SMGT event was introduced as of version 11.00.05.
11.01.00 SMGT event was introduced as of version 11.01.00.

4.4.2.10 NO

Command History:

170 Configuration and Monitoring

Teldat SA 4 Event Logging System ELS

Release Modification
11.00.05 This command is introduced in version 11.00.05
11.01.01 This command is introduced in version 11.01.01.

Allows you to disable the event storing system.

Syntax:

ELS+no ?
event-store Disable event store on flash
ELS+

NO EVENT-STORE

When the command is executed, a message is shown warning the user on the possible results of the operation.

ELS+no event-store
Event store disabled
ELS+

4.4.2.11 NVRLOG

Allows you to view the logs saved in the non-volatile memory, as well as initialize this.

Syntax:

ELS+nvrlog ?
clear Initialize the bugs system, deleting all previous ones
list Select the number of logs to be displayed on the console
ELS+

NVRLOG LIST

Allows you to select the number of logs to display on the console.

Syntax:

ELS+nvrlog list <number_of_logs>

Example:

ELS+nvrlog list 2
02/26/07 11:31:05 -1- RESET:(CODE 0xc0000000) EH ES
BIOS CODE VERSION: 01.09.09 START FROM FLASH L1
02/26/07 11:28:27 -3- Reload issued by the user
ELS+

For each log displayed the following information is given: the date and the time the event took place, the priority as-
sociated to said log (between hyphens) and a text containing information relative to said event.

NVRLOG CLEAR

Initializes the bugs system, deleting all previous ones.

Example:

ELS+NVRLOG CLEAR 0
01/02/07 10:32:47 -1- Logging memory initialized.
ELS+

4.4.2.12 RESTORE-CONFIGURATION

Allows you to restore the events configuration the device started up with.

Syntax:

ELS+restore

Example:

ELS+restore
Do you want to restore ELS configuration?(Y/N)(N): y

Configuration and Monitoring 171

4 Event Logging System ELS Teldat SA

ELS+

4.4.2.13 SHOW-STORED-LOG

Command History:
Release Modification
11.00.05 This command was introduced as of version 11.00.05
11.01.01 This command was introduced as of version 11.01.01.

Allows you to see the last event log generated by the event-store command if CIT crashes. The events are dis-
played from the most recent to oldest.

Syntax:

ELS+show-stored-log ?
<1..10000> Show a specific number of events stored
<cr>
ELS+

You can view only a specified number of stored events or all of them. If there too many events in the latter, you can
stop this command by pressing Ctrl+P.

Example:

ELS+show-stored-log 2
Press (Control + P) if you want to finish operation
04/14/16 17:55:27 ethernet0/0: PHY: Link UP - 100Mbps - Full - Copper
04/14/16 17:55:26 ethernet0/0: PHY is Marvell 88E1011S (01410c67)
ELS+

ELS+show-stored-log
Press (Control + P) if you want to finish operation
04/14/16 17:55:27 ethernet0/0: PHY: Link UP - 100Mbps - Full - Copper
04/14/16 17:55:26 ethernet0/0: PHY is Marvell 88E1011S (01410c67)
04/14/16 17:55:26 GW.005 Bffrs: 25575 avail 25575 idle fair 1312 low 5063
04/14/16 17:55:26 GW.073 CIT Ver Chg: Ver: 11.01.01-Beta-f97b83d+
04/14/16 17:55:26 GW.002 Portable CGW ATLAS160Super Rel 11.01.01-Beta-f97b83d+ strtd
04/14/16 17:55:26 GW.001 System restarted -- ATLAS160Super router cold start
ELS+

4.4.2.14 VIEW

Allows events to be displayed in the active process.

This command is available from any process, although it does not appear when requesting all available commands:
to execute this, enter the full command name.

Syntax:

ELS+view ?
history Display the events history
<cr>
ELS+view

Example:

ELS+view
ELS+

4.4.2.14.1 VIEW HISTORY

Use this option to access displayed events history.

Said history stores the same number of events as events configured through the evbuffer command, provided this is
more than 1000; where there are less, then 1000 are stored.

Syntax:

ELS+view history ?
flush Delete the events history
regex Apply a filter to the events history

172 Configuration and Monitoring

Teldat SA 4 Event Logging System ELS

<cr>
ELS+view history

Example:

ELS+view history
ELS+

VIEW HISTORY FLUSH

Deletes the history for viewed events.

Example:

ELS+view history flush

ELS+

VIEW HISTORY REGEX

Applies a regular expression filter to the viewed events history.

Syntax:

ELS+view history regex ?

<0..40 chars> regex

Example 1:

Filter applied to show only ARP events (stored in the history).

ELS+view history regex ARP\.

22155610.993295ms ARP.002 Pkt in 1 1 800 ethernet0/0
22155611.017757ms ARP.008 rcv IP RQST 192.168.212.103->192.168.212.96 ifc ethernet0/0
22156151.921871ms ARP.002 Pkt in 1 1 800 ethernet0/0
22156151.945174ms ARP.008 rcv IP RQST 192.168.212.103->192.168.212.96 ifc ethernet0/0
22156691.510117ms ARP.002 Pkt in 1 1 800 ethernet0/0
22156691.533632ms ARP.008 rcv IP RQST 192.168.212.103->192.168.212.96 ifc ethernet0/0
22157237.364754ms ARP.002 Pkt in 1 1 800 ethernet0/0
22157237.387300ms ARP.008 rcv IP RQST 192.168.212.103->192.168.212.96 ifc ethernet0/0
ELS+

Example 2:

This filter only show events where a celluar1/1 text appears (stored in the history).

ELS+view history regex cellular1/1

22156053.083756ms GW.019 Slf tst ifc cellular1/1
22156053.131998ms GW.022 Nt fld slf tst ifc cellular1/1
22157053.106362ms GW.019 Slf tst ifc cellular1/1
22157053.151817ms GW.022 Nt fld slf tst ifc cellular1/1
22158053.135392ms GW.019 Slf tst ifc cellular1/1
ELS+

4.4.2.15 EXIT

Allows you to exit the Event Logging System monitoring and return to + prompt.

Syntax:

ELS+exit

Syntax:

ELS+exit
+

Configuration and Monitoring 173

4 Event Logging System ELS Teldat SA

4.5 Supported personalized parameters

The Teldat devices have personalized parameters, which modify device behavior under certain special circum-
stances (personalized versions). For further information on the activation, deactivation and listing of these paramet-
ers, please see the help command in the enable, patch, disable patch and list patch commands respectively.
These can be found in Teldat Router Configuration on page 16. Also please see manual Teldat-Dm704 Configura-
tion and Monitoring for further information.

The Event Logging System has the following personalized parameters:

SRE_INT_FLAGS
This patch allows you to modify Event Logging system behavior. You don't usually need to use this, however this
patch is useful for debugging and development effects. The patch value is the sum of the flags used.
Ve: 0 Normal Event Logging System operation.
Flag: 1 The Event Logging System stops introducing events in the round viewing buffer when the latter is
full. This means when events cannot be viewed and the buffer is full, CPU time is not consumed so
improving performance. Another effect is it's the latest events that are lost, not the oldest.
Flag: 2 When viewing, the time and date do not appear as it does not consult the real time clock and per-
formance is improved.

Example:

Config>enable patch sre_int_flags 1

Config>list patch
Patch Name Value
-----------------------------------------
SRE_INT_FLAGS 1 (0x1)

174 Configuration and Monitoring