Dm704 Iv10 97 Configuration Monitoring

Teldat Router
Configuration and Monitoring

Doc. DM704-I Rev. 10.97
February, 2014
INDEX
Chapter 1 Teldat Router Console ....................................................................................1
1.
2.
3.
Introduction ........................................................................................................................ 2
Local and remote terminal .................................................................................................. 3
User interface ..................................................................................................................... 4
3.1.
Teldat Router connection ........................................................................................ 4
3.2.
Executing a command ............................................................................................. 7
3.3.
User Interface Processes ......................................................................................... 7
3.4.
Accessing the processes .......................................................................................... 9
3.5.
Returning to the Console Manager.......................................................................... 9
3.6.
Obtaining help ......................................................................................................... 10
4.
GESTCON process commands .......................................................................................... 11
4.1.
MONITOR .............................................................................................................. 11
4.2.
CONFIG .................................................................................................................. 11
4.3.
RUNNING-CONFIG .............................................................................................. 12
4.4.
FLUSH .................................................................................................................... 12
4.5.
INTERCEPT ........................................................................................................... 12
4.6.
LOAD ..................................................................................................................... 12
4.7.
LOGOUT ................................................................................................................ 14
4.8.
PROCESS ............................................................................................................... 14
4.9.
STATUS ................................................................................................................. 15
4.10.
RESTART ............................................................................................................... 15
4.11.
TELNET ................................................................................................................. 15
4.12.
VRF-TELNET ........................................................................................................ 17
Chapter 2 Teldat Router Configuration..........................................................................18

1.
2.
3.
4.
Introduction ........................................................................................................................ 19
Configuration Process ........................................................................................................ 23
Configuration procedure user interface .............................................................................. 24
Configuration commands ................................................................................................... 30
4.1.
ADD ........................................................................................................................ 30
4.2.
AUTOINSTALL ..................................................................................................... 31
4.3.
BACKUP-FILES .................................................................................................... 32
4.4.
BANNER ................................................................................................................ 33
4.5.
CONFIG-MEDIA ................................................................................................... 35
4.6.
CONFIRM-CFG ..................................................................................................... 37
4.7.
CONFIRM-CFG-NEEDED .................................................................................... 37
4.8.
COPY ...................................................................................................................... 40
4.9.
DESCRIPTION....................................................................................................... 40
4.10.
DISABLE ................................................................................................................ 40
4.11.
DUMP-COMMAND-ERRORS .............................................................................. 41
4.12.
ENABLE ................................................................................................................. 41
4.13.
EVENT ................................................................................................................... 42
4.14.
FEATURE............................................................................................................... 42
4.15.
FILE ........................................................................................................................ 53
4.16.
FIRMWARE-CHECKING ..................................................................................... 58
4.17.
FORMAT ................................................................................................................ 59
4.18.
GLOBAL-PROFILES ............................................................................................. 59
4.19.
LICENCE-CHANGE .............................................................................................. 60
4.20.
LIST ........................................................................................................................ 61
4.21.
LOG-COMMAND-ERROR ................................................................................... 63
4.22.
MANAGEMENT .................................................................................................... 63
4.23.
NETWORK............................................................................................................. 64
4.24.
NO ........................................................................................................................... 64
4.25.
NODE ..................................................................................................................... 68
- ii -
4.26.
4.27.
4.28.
4.29.
4.30.
4.31.
4.32.
4.33.
4.34.
4.35.
4.36.
PRIVILEGE ............................................................................................................ 69
PROTOCOL ........................................................................................................... 73
QUICK CONFIGURATION .................................................................................. 74
SAVE ...................................................................................................................... 74
SET ......................................................................................................................... 75
TELEPHONY ......................................................................................................... 86
TIME....................................................................................................................... 87
UCI.......................................................................................................................... 93
UNSET-DEMO-LICENSE ..................................................................................... 93
USER ...................................................................................................................... 94
END ........................................................................................................................ 97
Chapter 3 Teldat Router Monitoring ..............................................................................99

1.
2.
Introduction ........................................................................................................................ 100

Monitoring procedure commands ...................................................................................... 101
2.1.
? (HELP) ................................................................................................................. 102
2.2.
BUFFER ................................................................................................................. 102
2.3.
CLEAR ................................................................................................................... 104
2.4.
CONFIGURATION ................................................................................................ 104
2.5.
DEVICE .................................................................................................................. 107
2.6.
ERROR ................................................................................................................... 108
2.7.
EVENT ................................................................................................................... 108
2.8.
FEATURE............................................................................................................... 109
2.9.
LAST-CONFIG-CHANGES .................................................................................. 116
2.10.
MALLOC-MONITOR ............................................................................................ 116
2.11.
MANAGEMENT .................................................................................................... 117
2.12.
MEMORY............................................................................................................... 117
2.13.
NETWORK............................................................................................................. 118
2.14.
NODE commands ................................................................................................... 118
2.15.
PROTOCOL ........................................................................................................... 119
2.16.
QUEUE ................................................................................................................... 120
2.17.
QUICK .................................................................................................................... 121
2.18.
STATISTICS .......................................................................................................... 121
2.19.
SYSTEM ................................................................................................................. 122
2.20.
TFTP ....................................................................................................................... 136
2.21.
TELEPHONY ......................................................................................................... 136
2.22.
UCI.......................................................................................................................... 136
2.23.
WEB-PROBE ......................................................................................................... 137
2.24.
LOG ........................................................................................................................ 137
Chapter 4 Event Logging System ELS ............................................................................138

1.
2.
3.
4.
Introduction ........................................................................................................................ 139

Event Logging System ....................................................................................................... 140
Event Logging System user interface ................................................................................. 147
Event Logging System Commands .................................................................................... 152
4.1.
Configuration Process Commands .......................................................................... 152
4.2.
Monitoring process commands ............................................................................... 172
5.
Supported personalized parameters .................................................................................... 183
- iii -
Chapter 1
Teldat Router Console
1. Introduction
All Teldat Router devices employ the same user interface for every model. They only differ on the
protocol software loaded in each device.
The information contained in this chapter is divided in the following sections:
Local and remote terminal.
User interface.
User interface description.
GESTCON process commands.
TELDAT ROUTER - The Console

I-2
Doc.DM704-I
Rev.10.97
2. Local and remote terminal

The Teldat Router allows user access for configuration and monitoring functions through a local or
remote terminal.
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 functionality as the local ones, except that 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 TCP-IP Configuration Manual (Dm 702-I) for
further information on how to enable the IP protocol.
By means of local or remote terminal it is possible to access the Teldat Router and carry out the distinct
processes. These processes are related to device configuration with status monitoring and related
statistics. Messages can also be received on any events produced. These processes are named as follows:
P 1 (GESTCON): This is the console management process (GESTCON). This is the starting point
on booting a console session and that accesses other processes.
P 2 (VISEVEN):
This process allows events produced in the system to be displayed, from

established 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 Chapter 4 Event
Logging System ELS for further information.
P 3 (MONITOR): This permits you to MONITOR the state of the system as well as the statistics
gathered by the device.
P 4 (CONFIG):
This process permits you to edit all the configuration parameters. From this
process you can generate a complete configuration for the device without
altering the operation procedure. In order to activate this configuration, you
need to save it in the file system and restart the device.
P 5 (RUNNING-CONFIG):
This is the process through which changes in the devices
active configuration are affected. The configuration changes executed from
this process take immediate effect, however if it is not saved in the file system,
it will be lost on rebooting the device.
These processes are accessed from the console by striking the keys P 2, P 3 P 4 or P 5.

I-3
Doc.DM704-I
Rev.10.97
3. User interface
The following steps are the same for all Teldat Router, regardless the software installed.
Teldat Router connection.
Executing a command.
User interface processes.
Accessing the process.
Return to the Console Manager.
Obtaining help.
3.1. Teldat Router connection

You can establish console sessions with the device both locally through serial port RS-232 and also
remotely through a TELNET session. The following paragraphs explain both methods of accessing
the device.
Local Connection
During device booting, information will be displayed to the user on the configuration of the device
hardware and software and the system startup progress. Once this booting stage has completed, the
user is asked to initiate a session by pressing any key.
A user and password control the access to the router local connection. By default no user is registered.
In this case it will not be requested when you access the device and 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
1 LAN, 2 WAN Line , 2 ISDN Line
CIT software version: ZZZZZ
S/N: YYYY/YYYYY
where XXXXX is the specific router model.

In order to register a user, please see the user command in Chapter 2 Teldat Router
Configuration. In cases where there are enabled users, the introduction of a user and the
corresponding password will be requested. If the authentication is accepted, then the welcome text
will be shown.
User: Root
Password:****
Teldat
(c)2001-2002
S/N: YYYY/YYYYY

I-4
Doc.DM704-I
Rev.10.97
where XXXXX is the specific router model, YYYY/YYYY the unit serial number and ZZZZ the CIT
code release currently running.
If the password is not valid, the following text will appear:
User: Root
Password:******
Access denied
If the password is incorrectly introduced, you will not be able to access the console. If you exhaust the
maximum number of erroneous attempts, the application will block for one minute.
If you have been authenticated in the system and an inactive period of time has also been configured
(see the set command in Chapter 2 Teldat Router Configuration"), a monitoring process will
begin. If the configured inactive time period times out without the user touching any of the keys, the
local connection will close. In this case the user must reenter the password again when he wishes to
use the console.
Depending on the user you have authenticated with, you have permission when accessing the different
processes and executing some restricted commands.
The user access level is specified with a value between 0 and 15 and a mode, default or strict.
Five different predetermined access levels have been defined in the default mode:
NONE [0]:
System access is not permitted.
EVENTS [1]: Access is permitted to the Console Management (P1), to the Events Viewing (P2)
but you cannot execute the Ping, Telnet, Restart or Load commands.
MONITOR [5]:
Access is permitted to the Console Management (P1), to the Events Viewing
(P2) and the Monitoring process (P3). You are also permitted to execute the Ping
and Telnet commands but not the Restart or Load commands.
CONFIG [10]:
Access is permitted for all the process and all the 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 will be explained
further on in this manual.
You must save the configuration (see the save command in Chapter 2) if you wish to maintain the
users registered on restarting the device as contrariwise you lose the said user configuration.
The user command manages the users and permits 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 it if it does not exist.
no user name:
Deletes a user from the user list. You can eliminate as many users as you wish except if there is
only one Root user and there are other registered users. In this case, you can only delete the rest of
the users as if not you cannot manage the remaining users. If you eliminate all the users except the
last Root, then you can delete the latter. The system then will not request user and password in
order to access the device, as there are no more users registered in the system.
user name active:

I-5
Doc.DM704-I
Rev.10.97
Permits you to enable users. Simply indicate the user name you wish to enable.
user name no active:
Permits 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.
Permits you to change the access level of any registered user with the exception of users with Root
access level.
For further information on the user command, please see the explanation given in Chapter 2.
The user management is compatible with the password defined through the set password command.
Therefore if you update a device that has this password enabled, this will continue to permit access
using this password while not registering any user.
The user management has priority over the device password; therefore when there are
registered and enabled users (these are enabled by default when they are registered) the
old password will no longer be 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 of the device you wish 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, if necessary, a user and password will
be requested in order to access the system. Once correctly authenticated in the system, the following
welcome text will appear.
User: Root
Password:****
Teldat
(c)2001-2002
S/N: YYYY/YYYYY
where XXXXX is the specific router model, YYYY/YYYY the unit serial number and ZZZZ the CIT
code release currently running.
The access control to the Teldat Router is similar to the local mode access. If there are users defined
and these are enabled (these enable by default when created), the introduction of a user and their
corresponding password is requested in order to connect to the system. When the authentication is
correct, the welcome text and prompt appear and you have access to the authenticated user
permissions as indicated in the connection via local.
If the password is not valid, the following text will be displayed:

I-6
Doc.DM704-I
Rev.10.97
User: Root
Password:******
Access denied
If the password is not entered within approximately 20 seconds or the password

provided is incorrect, at the third attempt the device will disconnect the TELNET
session.
3.2. Executing a command

To enter a command, simply enter the necessary letters that differentiate one command from another
within the menu you are working in.
Example:
Within the menu containing the following commands:
user
upload
down
If you key in a u, an error will be produced indicating that you have introduced an ambiguous
command (both user and upload begin with a u). If you introduce a d, do, dow or down, this
command will be executed. In the same way if you introduce us, use or user, this command will
execute and similarly up, upl, uplo, uploa or upload will execute the upload command.
Any other entry will produce an error, as no command will coincide with the characters entered.
To delete the last character(s) from the command line use the backspace () key.
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 following diagram describes the structure of the processes in the Teldat Router.
As shown in the figure, each process has a different prompt. You can find out which process you are
in by checking the prompt.
The following list shows the prompts for the different processes:
Process
Prompt
GESTCON
MONITOR
CONFIG
Config>
RUNNING-CONFIG
Config$

I-7
Doc.DM704-I
Rev.10.97
process 5
RUNNINGCONFIG
Config$
process 4
CONFIG
Config>
process 3
MONITOR
+
GESTCON
*
process 2
VISEVEN
The Teldat Router offers the possibility of personalizing the device, including a text before the
prompt. This text can contain a maximum of 8 characters and takes the name assigned to the device.
To introduce the 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 protocol 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 thus permitting protocol parameter configuration. You can carry out the
whole of the device configuration from this process; however it will not activate until you have saved
it and rebooted the device. This process is used to edit the device boot up configuration.

I-8
Doc.DM704-I
Rev.10.97
RUNNING-CONFIG Process
Provides access to configure the interfaces, protocols, etc. All parameters configured through this
process take immediate effect, however if not saved, they will be lost when the device is restarted.
This process serves to dynamically modify the devices active configuration.
VISEVEN Process
Receives messages from the Events Logging System and displays them at the terminal in accordance
with the user selection criterion.
3.4. Accessing the processes

Prompt * will appear once the session has initiated. Prompt * is the Console Manager prompt. From
this prompt it is possible to access the distinct process. Prompts are the symbols that identify each
process:
To access a process, the following steps must be executed:
1. Look for the number that identifies the process. This information can be obtained by entering the
status command at the * prompt.
2. Enter process pid, where pid is the process number we wish to access. For example, to configure
Teldat Router, enter
*process 4
User Configuration
Config>
The most common processes however can be accessed through specific commands.
displayed in the following table.
Command
Process
monitor
Process 2: monitoring
config
Process 4: startup configuration editor
running-config Process 5: active configuration
These are
3.5. Returning to the Console Manager

To return to the Console Manager (prompt *) from a process, e.g. CONFIG (prompt Config>) or
MONITOR (prompt +), enter Ctrl + p (the escape character). ALWAYS RETURN TO THE
CONSOLE MANAGER BEFORE ENTERING ANOTHER PROCESS. For example if you are in
MONITOR and wish to enter CONFIG, enter Ctrl + p and return to prompt * before doing so.
To end a TELNET session initiated from the Teldat Router toward another device, you can use the
Ctrl + s escape character. This escape character forces the TELNET session, started by the Teldat
Router, to close.
The Ctrl. + p escape character is used to return to the console Manager, while the Ctrl.
+ s escape character is used to end a TELNET session.
Example:
*config
User Configuration
Config>
*
Press (Ctrl +

I-9
p)
Doc.DM704-I
Rev.10.97
*monitor
Console Operator
+
*
Press (Ctrl +
p)
Other protocol configuration/monitoring menus can be accessed from the

configuration or monitoring processes. Returning to the corresponding process is
achieved through the EXIT command and to the Console Manager via the escape
character (Ctrl + p by default).
3.6. Obtaining help

In all processes there is a command ? (HELP). This gives information on the 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 also enter an ? after any command to obtain a list of options permitted in the said
command.
You can also terminate a command or an option with an ? to get a list of commands or options
which match that written. The tabulation key can also be used to automatically complete a command
or option which is already completely determined.
Example:
Config>protocol ?
arp
Access ARP protocol configuration
asrt
Access ASRT protocol configuration
bgp
Access BGP protocol configuration
dep
Access DEP protocol configuration
dhcp
Access DHCP protocol configuration
dls
Access DLS protocol configuration
h323
Access H323 protocol configuration
ip
Access IP protocol configuration
l2tp
Access L2TP protocol configuration
noe
Access NOE protocol configuration
ospf
Access OSPF protocol configuration
rip
Access RIP protocol configuration
sip
Access SIP protocol configuration
snmp
Access SNMP protocol configuration
Config>protocol a?
arp
Access ARP protocol configuration
asrt
Access ASRT protocol configuration
Config>protocol a

I - 10
Doc.DM704-I
Rev.10.97
4. GESTCON process commands

The GESTCON process (P1) allows you to configure and monitor all the device operation parameters.
During the GESTCON process, the Teldat Router processes and transfers data traffic. When the device
is switched on and enters the GESTCON process the copyright, information on the device, together with
an asterisk * appear at the connected local terminal. This asterisk * is the prompt for GESTCON
process which is the main user interface permitting access to all other processes. Most changes made in
the Teldat Router operation parameters in the GESTCON process have an immediate effect i.e. it is
unnecessary to restart the device.
From the GESTCON process it is possible to access a set of commands that permit you to check the status
of the processes, monitor the device interface and packet transference efficiency, as well as the
configuration of various parameters.
GESTCON process commands table
Commands
Function
MONITOR
CONFIG
RUNNING-CONFIG
FLUSH
INTERCEPT
LOAD
LOGOUT
PROCESS
RESTART
STATUS
RESTART
TELNET <address>
Accesses the monitoring process.

Accesses the startup configuration editing process.
Accesses the active configuration editing process.
Clears all the messages stored up to that moment in the events buffer.
Permits you to change the procedures escape character.
Reloads the application from the flash memory
Ends the Telnet connection established with the device.
Permits access to a different device procedure and to enable its commands.
Allows you to restart the device rereading the configuration.
Displays the names and identifiers of each process.
Allows you to restart the device.
Establishes a Telnet connection as the remote device client whose remote
address is specified.
VRF-TELNET <vrf> <address>
Establishes a Telnet connection as client for the remote device
whose address is specified in the indicated VRF.
4.1. MONITOR
Accesses the monitoring process.
Syntax:
*monitor
Example:
*monitor
Console Operator
+
4.2. CONFIG
Accesses the startup configuration editing process.

I - 11
Doc.DM704-I
Rev.10.97
Syntax:
*config
Example:
*config
Config>
4.3. RUNNING-CONFIG
Accesses the active configuration editing process.
Syntax:
*running-config
Example:
*running-config
Config$
4.4. FLUSH
Deletes all the current events messages from the VISEVEN procedure output buffer.
Syntax:
*flush
Example:
*flush
*
4.5. INTERCEPT
Allows you to change the processes escape character. In the below example the default character given
is changed, (Ctrl+u) in place of (Ctrl+p).
Syntax:
*intercept
Example:
*intercept
Press the new escape key and then Enter:
Press the new escape key again and then enter:
Escape key updated
*
Press (Ctrl+u) and <>

Press (Ctrl+u) and <>
The escape key should not be a character that can be displayed.
4.6. LOAD
Allows you to load the program from flash memory.

I - 12
Doc.DM704-I
Rev.10.97
Syntax:
* load <option>
ACTIVATE
DEACTIVATE
IMMEDIATE
RACTIVATE
RDEACTIVATE
<option> specifies the load type you want to execute.
a) LOAD ACTIVATE
The activate option allows the user to program a specific time to reload the routing application
program. The 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
*
b) LOAD DEACTIVATE
The deactivate option allows you to cancel a pre-configured loading which has not as yet been carried
out. If no loading has been programmed, then an error message will appear.
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
*
c) 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
*
d) LOAD RACTIVATE
Permits the user to program a specific time where the routing application program restarts. The time is
configured in a 24-hour format.
Syntax:
*load ractivate

I - 13
Doc.DM704-I
Rev.10.97
Example:
*load ractivate 17:26
Are you sure to restart the system at the configured time (Yes/No)? y
*
e) LOAD RDEACTIVATE
Permits you to deactivate the programmed restart process. If there is no restart programmed, an error
message will appear.
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
*
4.7. LOGOUT
Ends the Telnet connection established with the device without using a Telnet client command.
Syntax:
*logout
Example:
*logout
Do you wish to end telnet connection (Yes/No)?
4.8. PROCESS
This permits access to another device process e.g. MONITOR, VISEVEN, or CONFIG. Once a new
process has been accessed, it is possible to 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) in order to return to the
Console Manager (GESTCON).
Syntax:
*process <pid>
<pid> this is the process identifier number whose console we wish 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 in order to return
to the menu of the process you are currently in.

I - 14
Doc.DM704-I
Rev.10.97
4.9. STATUS
Permits you to know each process identifier (pid), as well as the name.
Syntax:
*status
Example:
*status
System Processes:
PID NAME
1
2
3
4
5
6
Main console
Event viewer
Monitor console
Config console
Running config console
Telnet client
4.10. RESTART
Restarts Teldat Router without reloading the software. This has the following effects:
Software counters are set to zero.
Connected networks are tested.
Routing tables are cleared.
All packets are discarded until the restart has completed.
Current software is executed.
If this command is used during a remote terminal connection, the TELNET session
will be lost since all the device procedures will be 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
4.11. TELNET
Establishes a Telnet connection as the remote device client with a specified address. This address can
be a domain name in cases where the DNS client has been configured.

I - 15
Doc.DM704-I
Rev.10.97
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. In cases
where this option is not used, the main VRF is used.
In cases where no parameters are entered (telnet <cr> option), you are asked for all the telnet
parameters taking the main VRF as the VRF.
The parameters you can specify in Telnet are:
<address> specifies the IP address or the device domain name which 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 the 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 device 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
Telnet to device 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
Telnet to device with domain name router1.midominio.es:

FTP *telnet router1.midominio.es
Telnet to device 172.24.78.92 using the router_aux VRF.

FTP *telnet vrf router_aux 172.24.78.92

I - 16
Doc.DM704-I
Rev.10.97
4.12. 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 in cases 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.
In cases where no additional parameters are entered (vrf-telnet <vrf> <cr> option), you are asked for
all the telnet parameters.
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 device with address 172.123.23.67 in the VRF client:
*vrf-telnet client 176.123.23.67
Telnet to device 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
Telnet to device 172.24.78.92 in the client VRF using source address 80.1.1.1 and port 6623
specifying the parameters with options.
FTP *vrf-telnet client 172.24.78.92 source 80.1.1.1 port 6623
Telnet to device with domain name router1.midominio.es in the VRF client:

FTP *vrf-telnet client router1.midominio.es

I - 17
Doc.DM704-I
Rev.10.97
Chapter 2
Teldat Router Configuration
1. Introduction
From the functional point of view there are two virtual devices integrated in Teldat Router:
1. A router that performs the internetworking functions.
2. A packet switch coming from the router as well as from the X.25 and ISDN ports when they
carry X.25
ROUTER
NODE
X.25
As the figure shows, each virtual device manages its own set of interfaces. Therefore it is necessary to
accurately identify the different interfaces and to 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 its location 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 the said type of 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 subinterfaces as their name is made up with the base interface number, over which these
are configured, following by a period (.) and an identifier number. This identifier number again must
be unique for each of the subinterfaces pertaining to the same base interface.
The table of interface identifiers is obtained through the list devices command in the configuration
process. The output of this command in a specific device is shown below:
Config>list devices
Interface
ethernet0/0
serial0/0
atm0/0
bri0/0
x25-node
Config>
Connector
LAN1
SERIAL0/WAN1
DSL1
BRI/ISDN1
---
Type of interface
Quicc Ethernet
AT COM
ATM
ISDN Basic Rate Int
Router->Node
The first column indicates the interface name (Interface), the second column indicates the physical
connector which 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 dont necessarily have to enter all
the characters). For physical interfaces, simply enter the beginning of the text thus ensuring this does
not coincide with any other interface text, following by the position if there is more than one interface
of the same type. You do not always need to introduce the position (X/X); this is only necessary in
cases where various interfaces of the same type are present (e.g. various serial interfaces).
TELDAT ROUTER - Configuration

II - 19
Doc.DM704-I
Rev.10.97
Examples:
Config>list devices
Interface
ethernet0/0
serial0/0
serial0/1
serial0/2
bri0/0
x25-node
Config>
Con
LAN1
WAN1
WAN2
WAN3
ISDN1
---
Type of interface
Fast Ethernet interface
X25
X25
X25
ISDN Basic Rate Int
Router->Node
CSR
fa200e00
fa200a00
fa200a20
fa200a60
fa200a40
0
CSR2
fa203c00
fa203d00
fa203f00
fa203e00
int
27
5e
5d
5b
5c
0
Example of the valid commands to access the first serial interface of the motherboard (WAN 1)
according to the devices listed in the above box.
Config>network
Config>network
Config>network
Config>network
serial0/0
ser0/0
ser0
s0
Example of erroneous commands:

Config>network
Config>network
Config>network
Config>network
serial
ser
ser0/4
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
Config>network
Config>network
Config>network
bri0/0
b0/0
bri0
b
As, in this case, there is only one bri, you do not need to indicate the position within the equipment,
simply introduce its text string. This does not necessarily need to be complete. The only characters
necessary are those distinguishing this from other interfaces. As in this case there arent any other
interfaces beginning with the letter b, this letter will suffice.
Another important aspect is that there are interfaces which do not have a physical
connector associated. This is the case of the x25-node interface in the example. This is due
to the fact it is this interface that permits the virtual machines to join and consequently does
not have an external connector associated.
With this information you can redo the previous figure for this case:
ethernet0/0
X25-node
ethernet0/1
ROUTER
serial0/0
X.25
R N
serial0/1
NODE
bri0/0
Suppose now that you change the protocol in one of the WAN lines through the command set datalink and we then consult the interface table.
In the following example the X25 protocol is assigned to the physical line 1:

II - 20
Doc.DM704-I
Rev.10.97
Config>set data-link x25 serial0/0

Config>list devices
Interface
ethernet0/0
ethernet0/1
serial0/0
serial0/1
bri0/0
x25-node
Config>
Connector
FE0/LAN1
FE1/LAN2
SERIAL0/WAN1
SERIAL1/WAN2
BRI/ISDN1
---
Type of interface
X25
X25
ISDN Basic Rate Int
Router->Node
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 of the device is now as follows:
ethernet0/0
X25-node
ethernet0/1
serial0/0
X.25
ROUTER
R N
NODE
serial0/1
bri0/0
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 permits you to distinguish the created
interface from other interfaces of the same type i.e. other frame-relay dial interfaces.
Config>list devices
Interface
ethernet0/0
ethernet0/1
serial0/0
serial0/1
bri0/0
x25-node
fr1
Config>
Connector
FE0/LAN1
FE1/LAN2
SERIAL0/WAN1
SERIAL1/WAN2
BRI/ISDN1
-----
Type of interface
X25
X25
ISDN Basic Rate Int
Router->Node
Generic FR
For those dial interfaces added by the user, you dont have to introduce the whole name in order to
refer to the interface. Simply introduce the necessary characters in order 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 of the device is as follows:

II - 21
Doc.DM704-I
Rev.10.97
ethernet0/0
X25-node
serial0/0
ethernet0/1
ROUTER
X.25
R N
bri0/0
NODE
serial0/1
fr1
In cases where we have ATM interfaces, subinterfaces associated to the said interfaces can be
configured. E.g. in a configuration with an xDSL card in SLOT 3:
Config>list devices
Interface
ethernet0/0
ethernet0/1
x25-node
atm3/0
Config>
Connector
GE0/FE0/LAN1
GE1/FE1/LAN2
--SLOT3
Type of interface
GigabitEthernet interface
Router->Node
Generic ATM
Add a subinterface associated to the said interface:
Config>add device atm-subinterface atm3/0 2

Config>list devices
Interface
ethernet0/0
ethernet0/1
x25-node
atm3/0
atm3/0.2
Config>
Connector
GE0/FE0/LAN1
GE1/FE1/LAN2
--SLOT3
---
Type of interface
Router->Node
Generic ATM
ATM subinterface
In order to access the said interface, you need to 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 in order to access the
subinterface even if only one subinterface exists. 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 previous box:
Config>network
Config>network
Config>network
Config>network
atm3/0.2
atm3.2
atm.2
a.2
As there is only one ATM base interface, you do not need to indicate the location.

II - 22
Doc.DM704-I
Rev.10.97
2. Configuration Process
The Configuration Process (config or running-config) permits 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 smartcard. In order to store the changes made in this procedure,
execute the save command. The router must be restarted so the configuration changes can take effect. To
restart the router we can do 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 permits you to display and dynamically change the
router active configuration and store it either in the flash memory or in a smartcard. So that the
changes made in this process are stored, you need to 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. Therefore, not all of the CONFIG process
commands are available in the RUNNING-CONFIG process such as the no config
command.
The Configuration procedures CONFIG and RUNNING-CONFIG are framed into the router structure as
shown in the following figure:
process 5
RUNNINGCONFIG
Config$
process 4
CONFIG
Config>
process 3
MONITOR
+
GESTCON
*
process 2
VISEVEN

II - 23
Doc.DM704-I
Rev.10.97
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 RUNNIG-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, with the
aim of avoiding contradictions due to parallel configuration processes, will block simultaneous access
to certain configuration menus.
In cases where a conflict of this type is produced, the device will not permit the user to access the
configuration environment and provide information on the circumstances provoking the situation.
Example:
Atlas +system telnet
ID USER
IP ADDRESS:PORT
CONNECTION TIME INACTIVITY TIME
------------------------------------------------------------------2 teldat
1 root
Atlas +
192.168.1.2:1
172.24.51.128:131
08/03/05 12:29:26
08/03/05 12:28:59
0 min *
29 min
User Console root

Atlas *config
Atlas Config>protocol ip
-- Internet protocol user configuration -Atlas IP config>
User Console teldat

Atlas *config
Atlas Config>protocol ip
CLI Error: Command locked by another user
CLI Error: Command error
Atlas Config>
In this case, the teldat user tries to access the IP protocol configuration environment and the device
prevents this as the root user is currently accessing the said menu.
Show Command
The show command can be executed from any configuration process menu. This permits three
options:

II - 24
Doc.DM704-I
Rev.10.97
Config>show ?
all-config
config
menu
Config>
The show all-config command displays the net configuration of all the device menus and submenus
that the user can access. I.e. displays all the commands that must be introduced through the console in
order 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 -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>

II - 25
Doc.DM704-I
Rev.10.97
This command shows the whole of the net configuration of the device that the user can access
independently of the menu and submenu where the user is located. Therefore, for example, from the
IP menu:
IP config>show all-config
log-command-errors
no configuration
;
network ethernet0/0
;
;
;
;
;
exit
;
;
;
;
network ethernet0/1
;
exit
;
;
;
;
;
network x25-node
;
exit
;
protocol ip
;
tvrp
;
group 1 ip 172.24.78.128
;
exit
;
exit
;
;
dump-command-errors
end
; --- end --IP config>
The show config command displays the net configuration of all the menus and submenus that the user
can access and that can be accessed from the menu where the user is located when he executes this
command.

II - 26
Doc.DM704-I
Rev.10.97
Example:
Config>show config
log-command-errors
no configuration
;
network ethernet0/0
;
;
;
;
;
exit
;
;
;
;
network ethernet0/1
;
exit
;
;
;
;
;
network x25-node
;
exit
;
protocol ip
;
tvrp
;
group 1 ip 172.24.78.128
;
exit
;
exit
;
;
dump-command-errors
end
; --- end --Config>
the show all-config. However if you execute the show config command from the IP menu, only the
IP and the TVRP configurations are shown:

II - 27
Doc.DM704-I
Rev.10.97
IP config>show config
; Showing Menu and Submenus Configuration for access-level 15 ...
classless
;
tvrp
;
group 1 ip 172.24.78.128
;
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
classless
;
IP config>
TVRP config>show menu

enable
;
group 1 ip 172.24.78.128
;
TVRP config>
The configuration generated by the show command can be copied to a text file and edited to the users
requirements. Subsequently this can be installed in an unconfigured device so that this is now
configured.
If, during the period where the router is displaying the configuration, you wish to abort the process
simply 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 (Dm 703-I) or TVRP groups (Dm 725-I).

II - 28
Doc.DM704-I
Rev.10.97
When selecting an option, you do not need to enter all the text for this, simply introducing the
necessary characters in order to distinguish this option from the rest will suffice.
Examples:
serial0/0 FR config>pvc
backup
Bc
Be
CIR
compression
default
encapsulation
encrypt
fragmentation-size
inverse-arp
name
no
route
serial0/0 FR config>pvc
serial0/0 FR config>
16 ?
Configure several backup parameters
Outgoing Committed Burst Size
Outgoing Excess Burst Size
Outgoing Committed Information Rate
Enable/disable compression for this circuit
Create the virtual circuit
Encapsulation type
Enable/disable encryption
Forced fragmentation size
Inverse ARP configuration for this dlci
Set the virtual circuit name
Set static route for PVC switching
16 cir 32000
In this particular case, 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 that begins with c
(compression) consequently this would have produced an error.

II - 29
Doc.DM704-I
Rev.10.97
4. Configuration commands
This section describes the configuration commands (CONFIG and RUNNING CONFIG process). Each
command includes a description, syntax and one example. The following table summarizes the
configuration commands.
Command
Function
ADD
AUTOINSTALL
BACKUP-FILES
BANNER
CONFIG-MEDIA
Allows you to create a virtual interface.

Sets the autoinstall parameters.
Makes a backup copy of the system files.
Permits you to configure banners in the device.
Permits you to specify the active storage unit: flash or SmartCard or
both.
CONFIRM-CFG-NEEDED
Enables the need to confirm the saved configuration.
CONFIRM-CFG
Confirms the current configuration.
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
predetermined interface.
FILE
Permits 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 of a specific interface.
NO
Invalidates a command action or sets the default values.
NODE
Enters the X.25/ISDN, XOT or 270 Node configuration.
PRIVILEGE
Permits you to specify personalized execution permissions.
PROTOCOL
Enters the configuration of a specific protocol.
SAVE
Allows you to save the configuration in the active storage unit.
SET
Configures system parameters, buffers, device name, etc.
TELEPHONY
Sets the Voice over IP parameters.
TIME
Permits you to view and change the system data and time.
UCI
Permits you to configure the Teldat Router encryption unit.
USER
Permits you to configure users.
END
End of configuration.
4.1. ADD
Allows you to create a virtual interface to be used by an ISDN basic access B channel, ATM
subinterfaces, PPP interfaces etc.

II - 30
Doc.DM704-I
Rev.10.97
Syntax:
Config>add <option>
device
Create a virtual device
<option> specifies the selected option.

The only option available for this command is:
a) ADD DEVICE
Syntax:
Config>add device <virtual interface> [options]
<virtual interface> this is the virtual interface you want to create. To find out what types
of interfaces are available, enter add device ?.
Config>add device ?
270
atm-subinterface
bvi
dial-routing
eth-subinterface
fr
hdlc
l2tp
loopback
pcmcia
ppp
tnip
voip-dummy
voip-isdn
x25
xot
Create
Create
Create
Create
Create
Create
Create
Create
Create
Create
Create
Create
Create
Create
Create
Create
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
virtual
virtual
virtual
virtual
virtual
virtual
virtual
virtual
virtual
virtual
virtual
virtual
virtual
virtual
virtual
virtual
270 interface
ATM Subinterface interface
Bridge interface
Dial-Route interface
Ethernet Subinterface interface
Frame-Relay interface
HDLC interface
L2TP interface
Loopback interface
PCMCIA interface
PPP interface
TNIP interface
VoIP interface with no hardware
VoIP interface over ISDN
X25 interface
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 the said interface.
Example:
Config>add
modem
umts
Config>add
<1..3>
Config>add
<0..1>
Config>add
<cr>
Config>add
Config>
device pcmcia ?
PCCARD Modem type
PCCARD UMTS type
device pcmcia modem ?
Slot number
device pcmcia modem 1 ?
Interface Id
device pcmcia modem 1 0 ?
device pcmcia modem 1 0
For further information, please see the manual associated to the virtual interface you wish to create.
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.

II - 31
Doc.DM704-I
Rev.10.97
[value] value to assign to the above specified parameter.

There are two types of configurable parameters:
a) 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>
b) AUTOINSTALL MANAGEMENT-HOST
Identifies the management station where the remote autoconfiguration is executed.
Syntax:
Config>autoinstall management-host <host identifier>
<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>
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. Consequently, should the filing system become corrupt, the device will
automatically restore the files from the recovery point and is able continue operating.
The configuration monitoring command shows information relative to the recovery process, indicating
if it has started up normally (from the first partition) or if its restored from the recovery point (from
the backup partition).
The configuration command [no] firmware-checking determines if the restoration for the filing system
is enabled in cases where a necessary firmware file is corrupt.
This command only works 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

II - 32
Doc.DM704-I
Rev.10.97
CLI Error: Backup device not available.

Config>
In this example, the device does not have a partitioned flash and therefore the command has returned
an error message without creating any recovery point.
4.4. BANNER
Permits you to configure banner in the device.
Syntax:
Config>banner <type>
login
Set login banner
<type> specifies the type of banner to configure.
a) Banner login
Permits you to configure an access banner in the device which is always displayed when a user tries to
access the device through console, telnet or ftp.
To enter various lines of text in the banner, execute the banner login command, orderly and
consecutively, followed by each line of text (between inverted commas should there be spaces).
The size of an access banner is limited to 15 lines of text each containing 80 characters.
Syntax:
Config>banner login <line of text>
Example:
Config>banner login
"################################################################################"
Config>banner login "# Este equipo es propiedad de Teldat, S.A. y su uso est
restringido a sus
#"
Config>banner login "# empleados. Por favor, aborte esta conexin si usted no es
empleado de
#"
Config>banner login "# Teldat, S.A. o tiene una autorizacin legal para acceder al
equipo.
#"
Config>banner login
"################################################################################"
Config>show config
log-command-errors
no configuration
banner login
"################################################################################"
banner login "# Este equipo es propiedad de Teldat, S.A. y su uso est restringido a
sus
#"
banner login "# empleados. Por favor, aborte esta conexin si usted no es empleado
de
#"
banner login "# Teldat, S.A. o tiene una autorizacin legal para acceder al equipo.
#"
banner login
"################################################################################"
;
user GPEREZ hash-password 9DDE06D391B87902FD9FCC8AACC9641B
;
user TELDAT hash-password A44AD55CE197114B241EE3DDEBB04660
;
;

II - 33
Doc.DM704-I
Rev.10.97
;
network ethernet0/0
;
exit
;
;
;
network ethernet0/1
;
exit
;
;
;
;
network x25-node
;
exit
;
;
;
dump-command-errors
end
; --- end --Config>save yes
Building configuration as text... OK
Writing configuration... OK on Flash
Config>
*restart
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
Initializing
################################################################################
# Este equipo es propiedad de Teldat, S.A. y su uso est restringido a sus
#
# empleados. Por favor, aborte esta conexin si usted no es empleado de
#
# Teldat, S.A. o tiene una autorizacin legal para acceder al equipo.
#
################################################################################
User:
By default, the device does not have an access banner configured.
b) Banner Exec
Configures a welcome banner that is displayed when a user accesses the device through the console,
Telnet, SSH or FTP.

II - 34
Doc.DM704-I
Rev.10.97
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
Config>banner exec
Config>banner exec
Config>save yes
"##############################################################"
" "
"............:::::::::::
WELCOME
:::::::::::............"
" "
"##############################################################"

Writing configuration... OK on Flash as CONFIG
Config>
*restart
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.
Initializing
Teldat
(c)2001-2012
Router model Super * * CPU MPC8260 S/N: 472/04709

2 LAN, 2 WAN Lines, 1 ISDN Line
CIT software version: 10.09.04 Oct 25 2012 18:43:58
##############################################################
............:::::::::::
WELCOME
:::::::::::............
##############################################################
4.5. CONFIG-MEDIA
This permits you to select the active storage device in which the configurations are saved on applying
the configuration command save. This is also the default media in the file list command.
You might find two storage medias in the devices: flash memory and SmartCard cards. All devices
have the flash memory as the basic storage unit. The availability of SmartCard cards depends on the

II - 35
Doc.DM704-I
Rev.10.97
type of device. In order to find out if your device supports SmartCard, please see the installation
manual.
By default, the device has the value smartcard-flash configured in those devices that support the
SmartCard and the flash option in those that dont. 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 the storage units, please see the file list and file copy commands
described in this manual as well as the installation manual for your device. 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 device.
a) CONFIG-MEDIA FLASH
Specifies the flash memory as the only active storage unit when reading or writing configurations.
On booting the device the configuration is read from Flash. If the active configuration file is not
found, the device will boot with the default configuration. On saving the configuration through the
save command, this will be saved in the Flash memory with the name of the active file.
Example:
Config>config-media flash
b) CONFIG-MEDIA SMARTCARD
Specifies the SmartCard 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 configuration file is not found, the device will boot with the default configuration. On saving
the configuration through the save command, this will be saved in the Smart Card with the name of
the active file.
Example:
Config>config-media smartcard
c) CONFIG-MEDIA SMARTCARD-FLASH
Specifies both the SmartCard as well as the flash memory as active storage devices when reading or
writing configurations. The SmartCard 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 in the Flash memory. If the file is
not found in the Flash memory then the device will boot with the default configuration. After reading
the Smart Card configuration file the device checks to see that this is written in the Flash memory. If
the configuration is not present then the device enters it so that both medias are synchronized.
On saving the configuration through the save command, the configuration is saved in both the Smart
Card and the Flash with the name of the active file. The console indicates the devices where the
configuration has been stored and through a warning text will show the devices where recording has
not been possible.

II - 36
Doc.DM704-I
Rev.10.97
Example:
Config>config-media smartcard-flash
4.6. CONFIRM-CFG
Confirms the current configuration. You need to have saved a configuration with the configuration
confirmation function activated. Please see confirm-cfg-needed.
Syntax:
Config>confirm-cfg
This action can also be executed via SNMP. Please see section 4.7
4.7. CONFIRM-CFG-NEEDED
Enables the need to confirm the saved configuration. If you have executed this command, the
configuration is saved in TEMP.CFG in order to be checked. If, after restarting, the configuration is
not confirmed with the confirm-cfg command within the configured time, the device will restart 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 make the device
restart before the programmed test time is reached, if after ten restarts without the configuration being
confirmed, the previous configuration will be restored. If you execute the no confirm-cfg command,
the device will restart with the previous configuration. The no confirm-cfg-needed command
disables the need to confirm the 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.
a) CONFIRM-CFG-NEEDED DEFAULT
Enables the need to confirm the saved configurations with a test time of 10 minutes.
Syntax:
Config>confirm-cfg-needed default
Example:
Config>
b) CONFIRM-CFG-NEEDED TIMEOUT
Configures the new configuration test time which the device will wait before restarting the previous
configuration if confirmation 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.

II - 37
Doc.DM704-I
Rev.10.97
Example:
Config>confirm-cfg-needed timeout 30s
Config>
There is the possibility of executing 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/not confirm the current configuration.
In a write operation, setting this variable to 1 confirms the current configuration and
setting it to 0 rejects the current test configuration so the device restarts with the previous
configuration.
In a read operation, a 0 value (confirmed) indicated that the current configuration has been
confirmed. A 1 value (test_cnfg_inactive) indicates that the current configuration has not
been confirmed as yet (consequently this is a test configuration) and neither is it active.
Its the previous configuration which is still active. A 2 value (test_cnfg_active) indicates
that the current configuration has not been confirmed as yet (and consequently this is a test
configuration), but we are dealing with an active configuration. A value of 3
(configuration_recovered) indicates that the previous configuration has been recovered
and is confirmed and active. A value of 4 (undefined) only occurs in cases where the
confirmed saved configuration is disabled as in this case the use of this SMNP variable
makes no sense.
There are three scenarios where recuperation of the old configuration can be produced
(and
therefore
the
telAdminStatusConfirmConfig
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 intention to restore the old configuration in this scenario is in order to
protect us should the new configuration make the device restart before reaching the
programmed test time.
c) After rejecting the current test configuration through the no confirm-cnfg command
(or through SNMP by entering 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 confirmed save.
In a write operation, setting this variable to 1 enables the need to confirm the saved
configuration. Setting this variable to 0 disables the need to configure the new saved
configurations.
In a read operation, a 0 value (disable) indicates that the confirmed save configuration
functionality is disabled. And a value of 1 (enable) indicates that the confirmed save
configuration functionality is enabled.
telAdminStatusTimeoutConfirm (OID: 1.3.6.1.4.1.2007.1.2.16). This variable serves to

configure the value (in seconds) that the confirmed save configuration functionality timer
takes. I.e. this is the time the device waits before restarting the old configuration if this is
not confirmed.
The values permitted for this variable are within the range of 60 (1 minute) and 3024000
(5 weeks). Default is 600 (10 minutes).

II - 38
Doc.DM704-I
Rev.10.97
In a write operation, values between 60 and 3024000 configure the timer to the said
introduced value.
In a read operation, values between 60 and 3024000 returns the seconds value to that 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:
o telAdminStatusConfirmConfig = 4 (undefined)
o telAdminStatusConfirmEnabled = 0 (disable)
o telAdminStatusTimeoutConfirm = 600
Enable the confirmed save configuration (setting the telAdminStatusConfirmEnabled
SNMP variable value to 1). The SNMP variables take the following values:
o telAdminStatusConfirmConfig = 0 (confirmed)
o telAdminStatusConfirmEnabled = 1 (enable)
Set the confirmation wait timer value to the value you want (1 minute for example). To
do this, set the telAdminStatusTimeoutConfirm SNMP variable value to 60. The SNMP
variables take the following values:
Make the changes in the device configuration that you consider opportune and save them
(setting the telAdminStatusSaveConfig SNMP variable value to 1). The SNMP variables
take the following values:
o telAdminStatusConfirmConfig = 1 (test_cnfg_inactive)
Restart the device. The SNMP variables take the following values:
o telAdminStatusConfirmConfig = 2 (test_cnfg_active)
Confirm the tests configuration (which are active) before the 60 second timer times out
(setting the telAdminStatusConfirmConfig SNMP variable value to 1). The SNMP
variables take the following values:
Continuing with the example, we could carry out some new changes in the device
configuration and save them (setting the telAdminStatusSaveConfig SNMP variable to 1).
The SNMP variables take the following values:
o telAdminStatusConfirmConfig = 1 (test_cnfg_inactive)
Restart the device. We can see that the test configuration is active. The SNMP variables
take the following values:
o telAdminStatusConfirmConfig = 2 (test_cnfg_active)

II - 39
Doc.DM704-I
Rev.10.97
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 following values:
o telAdminStatusConfirmConfig = 3 (configuration_recovered)
4.8. COPY
This command allows you to copy the Running Config (P5) configuration to Config (P4).
Confirmation will be requested in cases where the Config (P4) configuration has been modified.
Syntax:
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>
4.9. DESCRIPTION
Permits you to introduce descriptive texts regarding the device configuration. This description is
displayed on screen on executing the list configuration configuration command.
Syntax:
Config>description <text>
<text> the configuration description text. If this text contains spaces, this must be written
between quotation marks (e.g. description description containing spaces).
Example:
Config>description Madrid_Branch_Outcoming_Router
4.10. DISABLE
Disables a specific personalized parameter. This command is used to deactivate the behavior activated
through the enable patch <parameter> command. In order to use this, you need to know the name of
the activated parameters. To do this 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 parameters will be deactivated.

II - 40
Doc.DM704-I
Rev.10.97
Example:
Config>disable patch arpi_snd_lcl
Config>
4.11. DUMP-COMMAND-ERRORS
Displays, on screen, a list of the first five erroneous commands introduced in the configuration console
from the point where the log-command-errors command was executed. This command is
particularly useful for detecting errors that have been produced 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>
4.12. ENABLE
This enables a specific personalized parameter. This command allows you under certain
circumstances to modify the routers behavior. It deals with the management of personalized versions.
You need the names of the available parameters 1 and their possible admitted values in order to use it.
Introducing the name and desired value for the parameter will activate it.
Syntax:
Config>enable patch <id> [value]
<id> name of the parameter to activate.

[value] value of the said parameter.
Example:
Config>enable patch arpi_snd_lcl 1
Config>
In order to check the active parameters in your device at any point, use the list patch command. To
disable an active personalized parameter, use the disable patch command followed by the parameter
name.
1
The personalized parameters relative to each Teldat device functionality can be found correctly documented in the manuals associated to
these said functionalities.

II - 41
Doc.DM704-I
Rev.10.97
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>
In order to see the commands that can be executed from this prompt, please see Chapter 4 Event
Logging System ELS.
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
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
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
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

II - 42
Doc.DM704-I
Rev.10.97
syslog
tftp
tms
vlan
vli
vrf
wrr-backup-wan
wrs-backup-wan
Syslog configuration environment

TFTP configuration enviroment
TMS configuration environment
IEEE 802.1Q switch configuration environment
Virtual Linux Interface configuration
VRF configuration environment
WRR configuration environment
WRS configuration environment
<option> name of the feature to configure.

[parameters] parameters required for the specified option.
a) FEATURE AAA
Accesses the AAA feature configuration menu.
Syntax:
Config>feature aaa
Example:
Config>feature aaa
-- AAA user configuration -AAA config>
For further information on the AAA feature configuration, please see manual Dm800-I AAA Feature.
b) 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 on configuring generic access lists, please see manual Dm752-I Access
Control.
c) FEATURE ACT
Accesses the ACT feature configuration menu.
Syntax:
Config>feature act
Example:
Config>feature act
-- Alsa Custom Trap configuration -ACT config>
For further information on configuring the ACT feature, please see manual Dm818-I ACT Feature.
d) FEATURE AFS
Accesses the afs configuration environment.
Syntax:
Config>feature afs

II - 43
Doc.DM704-I
Rev.10.97
Example:
Config>feature afs
AFS config>
For further information on afs configuration, please see manual Dm786-I AFS.
e) FEATURE AUTOSET-CFG
Accesses the autoset-cfg configuration environment for those devices that support this.
Syntax:
Config>feature autoset-cfg
Example:
Config>feature autoset-cfg
-- Autosetcfg Configuration -Autoset-cfg Config>?
For further information on autoset-cfg configuration, please see manual Dm797-I Dynamic
Configuration Control.
f) FEATURE BANDWIDTH-RESERVATION
This permits access to 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 on configuring bandwidth reservation, please see manual Dm715-I Bandwidth
Reservation System.
g) 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 on class-map configuration, please see manual Dm795-I Policy map Class
map.
h) FEATURE CONTROL-ACCESS
This permits access to 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

II - 44
Doc.DM704-I
Rev.10.97
Example:
Config>feature control-access
CtrlAcc Config>
i) FEATURE DNS
Permits access to the DNS configuration environment. For further information please see manual Dm
723-I DNS Client.
Syntax:
Config>feature dns
Example:
Config>feature dns
-- DNS resolver user configuration -DNS config>
j) 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 on dns-updater configuration, please see manual Dm785-I DNS Updater.
k) 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 on echo-responder configuration, please see manual Dm702-I TCP IP.
l) FEATURE ERR-DISABLE
Accesses the err-disable configuration environment.
Syntax:
Config>feature err-disable
Example:
Config>feature err-disable
-- Error Disable user configuration -errdisable config>
m) FEATURE FRAME-RELAY-SWITCH
Accesses the Frame Relay switch configuration environment. For further information on this, please
see manual Dm 703-I Frame Relay.

II - 45
Doc.DM704-I
Rev.10.97
Syntax:
Config>feature frame-relay-switch
Example:
Config>feature frame-relay-switch
-- Frame Relay Switch configuration -Frame Relay Switch>
n) FEATURE GPS-APPLICATIONS
Accesses the gps-applications configuration environment for those devices that support this.
Syntax:
Config>feature gps-applications
Example:
Config>feature gps-applications
-- GPS Applications Configuration -GPS-Apps Cfg>
For further information on gps-applications configuration, please see manual Dm812-I GPS.
o) FEATURE HTTP
This 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>
p) FEATURE IP-DISCOVERY
Accesses the TIDP (Teldat IP Discovery Protocol) configuration environment.
Syntax:
Config>feature ip-discovery
Example:
Config>feature ip-discovery
-- Teldat IP Discovery Protocol configuration -TIDP config>
q) 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 on istud configuration, please see manual Dm784-I ISTUD Feature.

II - 46
Doc.DM704-I
Rev.10.97
r) 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 on key-chain configuration, please see manual Dm792-I Key Management.
s) FEATURE LDAP
Accesses the LDAP (Lightweight Directory Access Protocol) configuration environment.
Syntax:
Config>feature ldap
Example:
Config>feature ldap
-- LDAP User Configuration -LDAP config>
t) 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>
u) FEATURE MANAGEMENT
This command access the feature management configuration menu. This feature permits you to
program tasks so they are executed when they received the notification from an NSLA advisor
(Network Service Level Advisor). For further information on NSLA, please see manual 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
operation
exit
Negate a command or set its defaults

Configure an operation to be executed
Exit to parent menu

II - 47
Doc.DM704-I
Rev.10.97
An operation is defined as a task that must be executed on receiving a notification from an advisor.
The configuration for an operation consists of two phases. In the first, the task to execute is specified
and its possible parameters. In the second phase, the advisor, whose notification provokes the
operation to begin, is configured.
operation <id> syatem reset

This command programs a device reset so 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 2 system reset
An operation can be deleted through the no operation <id> command.
operation <id> track nsla-advisor <advisor id>

Through this command an operation is subscribed to receive notifications from an NSLA advisor.
Example:
MGT config>operation 2 track nsla-advisor 1
To cancel the subscription, execute the no operation <id> track command.
v) FEATURE NETFLOW
Accesses the netflow configuration environment.
Syntax:
Config>feature netflow
Example:
Config>feature netflow
NETFLOW config
For further information on netflow configuration, please see manual Dm789-I NETFLOW.
w) FEATURE NSLA
Accesses the NSLA (Network Service Level Advisor) configuration environment which provides
management functions at the service level offered by the network (Service Level) and the generation of
reports relative to the SLA (Service Level Agreements).
Syntax:
Config>feature nsla
Example:
Config>feature nsla
-- Feature Network Service Level Advisor -NSLA config>
For further information, please see manual Dm 754-I NSLA (Network Service Level Advisor).
x) FEATURE NSM
Accesses the NSM system (Network Service Monitor) configuration environment which provides
information on the network service level by using different polls incorporated in the router and which
permit the performance of this to be measured.

II - 48
Doc.DM704-I
Rev.10.97
Syntax:
Config>feature nsm
Example:
Config>feature nsm
-- Network Service Monitor configuration -NSM config>
For further information on this, please see manual Dm 749-I NSM (Network Service Monitor).
y) FEATURE NTP
Permits access to 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 Dm 728-I NTP Protocol.
z) FEATURE POLICY-MAP
Accesses the policy-map configuration environment.
Syntax:
Config>feature policy-map
Example:
Config>feature policy-map
-- Policy-Map Menu Configuration -Policy-map Config>
For further information on policy-map configuration, please see manual Dm795-I Policy map Class
map.
aa) 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 on prefix lists configuration, please see manual Dm780-I Prefix Lists.
bb) FEATURE RADIUS

Permits access to the RADIUS protocol configuration environment.
Syntax:
Config>feature radius

II - 49
Doc.DM704-I
Rev.10.97
Example:
Config>feature radius
-- RADIUS User Configuration -RADIUS Config>
For further information on the RADIUS protocol configuration, please consult the associated manual
Dm 733-I RADIUS Protocol).
cc) FEATURE RMON

Accesses the rmon configuration environment.
Syntax:
Config>feature rmon
Example:
Config>feature rmon
-- Remote Network Monitoring configuration -RMON config>
For further information on rmon configuration, please see manual Dm796-I RMON Feature.
dd) FFEATURE 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 on route map configuration, please see manual Dm 745-I Policy Routing.
ee) 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>
ff) FEATURE SNIFFER

Accesses the packet capturer configuration environment, integrated in the device.
Syntax:
Config>feature sniffer
Example:
Config>feature sniffer
-- SNIFFER configuration -SNIFFER config>

II - 50
Doc.DM704-I
Rev.10.97
gg) FEATURE SPI

Accesses the spi configuration environment.
Syntax:
Config>feature spi
Example:
Config>feature spi
-- SPI global configuration -SPI Config>
For further information on spi configuration, please see manual Dm793-I SPI Agent.
hh) FEATURE SSH

Accesses the ssh configuration environment.
Syntax:
Config>feature ssh
Example:
Config>feature ssh
-- SSH protocol configuration -SSH Config>
For further information on ssh configuration, please see manual Dm787-I SSH Protocol.
ii) FEATURE STUN

Accesses the STUN client configuration environment.
Syntax:
Config>feature stun client
Example:
Config>feature stun client
STUN Client Config>
For further information on this, please see manual Dm 769-I STUN Protocol.
jj) FEATURE SYSLOG

Accesses the syslog client configuration environment.
Syntax:
Config>feature syslog
Example:
Config>feature syslog
-- SYSLOG client configuration -SYSLOG config>
For further information on this, please see manual Dm 753-I Syslog Client.
kk) FEATURE TFTP

Accesses the tftp configuration environment.

II - 51
Doc.DM704-I
Rev.10.97
Syntax:
Config>feature tftp
Example:
Config>feature tftp
-- TFTP user configuration -TFTP config>
For further information on tftp configuration, please see manual Dm765-I TFTP Protocol.
ll) FEATURE TMS

Accesses the TMS (Teldat Management System) configuration environment.
Syntax:
Config>feature tms
Example:
Config>feature tms
TMS config>
mm) FEATURE VLAN

Accesses the IEEE 802.1Q switch configuration environment to provide support for creating virtual
private networks (Virtual LAN).
Syntax:
Config>feature vlan
Example:
Config>feature vlan
-- VLAN configuration -VLAN config>
For further information on this, please see manual Dm 751-I VLAN.
nn) FEATURE VLI

Accesses the vli configuration environment for those devices that support this.
Syntax:
Config>feature vli
Example:
Config>feature vli
-- VLI configuration -VLI config>
For further information on vli configuration, please see manual Dm803-I Virtual Linux Interface VLI.
oo) FEATURE VRF

Accesses the VRF tables (VPN Routing/Forwarding) configuration environment.
Syntax:
Config>feature vrf
Example:
Config>feature vrf
-- VRF user configuration -VRF config>

II - 52
Doc.DM704-I
Rev.10.97
For further information, please see manual Dm 775-I VRF-Lite Facility.
pp) FEATURE WRR-BACKUP-WAN

Permits access to the WRR (WAN ReRoute) configuration environment.
Syntax:
Config>feature wrr-backup-wan
Example:
Config>feature wrr-backup-wan
-- WAN Reroute Backup user configuration -Backup WRR>
For further information on this configuration environment, please see manual Dm 727-I Backup WAN
Reroute.
qq) FEATURE WRS-BACKUP-WAN

This permits access to 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 on WRS backup configuration, please see manual Dm 711-I Frame Relay
ISDN Backup Configuration.
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 SmartCard is labeled
S:. Not all devices support both storage units. For further details, please see the installation manual
for your device.
One of the present units is considered as the active or predetermined unit. In order 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 so that when information is stored it is compressed with the gzip
program algorithm. In order to indicate this each time you store something in this unit, change the last
character. For further details on how to operate with this type of unit, please see the installation
manual for your device.
Syntax:
Config>file
copy
delete
format
list
rename
type
<operation> [parameters]
Copy files in the storage units
Delete files present in the device storage units
Format a storage unit in the device
Lists the files present in the storage units
Rename the files present in the device storage units
Show files by console
<operation> operation to execute over the storage unit or file.

[parameters] parameters required for the specified operation.

II - 53
Doc.DM704-I
Rev.10.97
a) FILE COPY
This permits 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, you do not need to 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.
Example 1:
Config>file copy xot1.cfg xot2.cfg
Config>
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 appears as MIKE11.CFZ indicating that it is a compressed file.
b) FILE DELETE
Permits you to delete files present in the device storage units. For security reasons, you cannot delete
the 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
A:
TKR.CFG
A:
TEST.CFG
A:
SINTEST.CFG
A:
MIKE.CFG
A:
MIKE2.CFG
A:
XOT1.CFG
A:
XOT2.CFG
A:
XOT3.CFG
A:
ATLASXOT.BIN
A:
ATLAS.BIN
3510
1050
4708
4593
1494
6302
1494
1494
1554
2757188
2760544
12/09/02
09/19/02
04/26/02
09/25/02
12/26/02
12/13/02
12/26/02
12/27/02
12/26/02
12/26/02
01/03/03
12:45
18:08
15:33
15:28
16:47
10:09
14:33
12:27
13:18
14:17
10:39
Flash
Flash
Flash
Flash
Flash
Flash
Flash
Flash
Flash
Flash
Flash
Flash Available Space : 2496 Kbytes

S:
ROUTER.CFZ
802
SmartCard Available Space : 14400 bytes

Config>file delete s:router.cfz
Config>file list
A:
ROUTER.CFG
3510
12/09/02
A:
TKR.CFG
1050
09/19/02
A:
TEST.CFG
4708
04/26/02
A:
SINTEST.CFG
4593
09/25/02
A:
MIKE.CFG
1494
12/26/02
A:
MIKE2.CFG
6302
12/13/02
A:
XOT1.CFG
1494
12/26/02

II - 54
SmartCard
12:45
18:08
15:33
15:28
16:47
10:09
14:33
Flash
Flash
Flash
Flash
Flash
Flash
Flash
Doc.DM704-I
Rev.10.97
A:
A:
A:
A:
XOT2.CFG
XOT3.CFG
ATLASXOT.BIN
ATLAS.BIN
1494
1554
2757188
2760544
12/27/02
12/26/02
12/26/02
01/03/03
12:27
13:18
14:17
10:39
Flash
Flash
Flash
Flash

Config>
Example 2:
Config>file delete atlas.bin
CLI Error: Application code files can not be deleted
Config>
c) FILE FORMAT
Permits you format a storage unit in the device. Currently, you can only format the SmartCard.
Please note that when you format a unit, all the files contained in the said unit will be deleted.
Syntax:
Config>file format <store unit>
<store unit> name of the storage unit to format. Currently only the SmartCard can be
formatted.
Example:
Config>file format smartcard
Formatting, please wait ... OK
Config>
d) FILE LIST
Lists the files present in the storage units of the device. This also shows you which unit is active. In
order 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
this 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
A:
ROUTER.CFG
A:
TKR.CFG
A:
TEST.CFG
A:
SINTEST.CFG
A:
MIKE.CFG
A:
MIKE2.CFG
A:
XOT1.CFG
A:
XOT2.CFG
A:
XOT3.CFG
A:
ATLASXOT.BIN
A:
ATLAS.BIN
3510
1050
4708
4593
1494
6302
1494
1494
1554
2757188
2760544
12/09/02
09/19/02
04/26/02
09/25/02
12/26/02
12/13/02
12/26/02
12/27/02
12/26/02
12/26/02
01/03/03
12:45
18:08
15:33
15:28
16:47
10:09
14:33
12:27
13:18
14:17
10:39
Flash
Flash
Flash
Flash
Flash
Flash
Flash
Flash
Flash
Flash
Flash

II - 55
Doc.DM704-I
Rev.10.97
S:
MIKE11.CFZ
802
SmartCard

Config>
Please note that the SmartCard unit is a slow storing unit and may take various seconds to respond.
e) FILE RENAME
Permits you to rename the files present in the device storage units. You must first indicate the original
name and subsequently 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 permitted to rename the
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
A:
ROUTER.CFG
A:
TKR.CFG
A:
TEST.CFG
A:
SINTEST.CFG
A:
MIKE.CFG
A:
MIKE2.CFG
A:
XOT1.CFG
A:
XOT2.CFG
A:
XOT3.CFG
A:
ATLASXOT.BIN
A:
ATLAS.BIN
3510
1050
4708
4593
1494
6302
1494
1494
1554
2757188
2760544
12/09/02
09/19/02
04/26/02
09/25/02
12/26/02
12/13/02
12/26/02
12/27/02
12/26/02
12/26/02
01/03/03
12:45
18:08
15:33
15:28
16:47
10:09
14:33
12:27
13:18
14:17
10:39
Flash
Flash
Flash
Flash
Flash
Flash
Flash
Flash
Flash
Flash
Flash

S:
ROUTER.CFZ
802

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

S:
BACKUP.CFZ
802
SmartCard

Config>
Example 2:
Config>file rename atlas.bin atlas_bak.bin
CLI Error: Application code files can not be renamed
Config>

II - 56
Doc.DM704-I
Rev.10.97
Example 3:
Config>file rename s:router.cfz a:router.cfg
Disk Units do not match
Config>
f) FILE TYPE
Permits you to display the files present in the device storage units. Each character that cannot
be printed is substituted with a period when being viewed.
Syntax:
Config>file type [header] <filename> [hex | text]
header this option means that 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
point in the corresponding text.
text displays the file content in text mode. Non-standard characters are substituted for a
point on the display.
The complete file will be displayed in text mode if you do not specify any option.
Example 1:
Config>file type header temp.cfg
; 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
; 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
;
;

II - 57
Doc.DM704-I
Rev.10.97
;
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
3b 20 53 68
20 43 6f 6e
6f 72 20 61
30 20 2e 2e
65 63 20 52
65 72 73 69
0d 0a 0d 0a
65 72 72 6f
69 67 75 72
64 61 74 61
65 72 69 61
74 6f 63 6f
6e 74 65 72
20 75 73 65
69 6f 6e 20
6e 61 6c 2d
37 32 2e 32
0a 20 20 20
72 6e 65 74
38 2e 31 31
30 0d 0a 3b
0d 0a 3b 0d
20 62 67 70
72 20 47 61
6f 6c 20 75
type header
6f 77 69 6e
66 69 67 75
63 63 65 73
2e 0d 0a 3b
6f 75 74 65
6f 6e 20 31
6c 6f 67 2d
72 73 20 0d
61 74 69 6f
2d 6c 69 6e
6c 30 2f 30
6c 20 69 70
6e 65 74 20
72 20 63 6f
2d 2d 0d 0a
69 70 2d 61
34 2e 37 38
61 64 64 72
30 2f 30 20
36 20 32 35
0d 0a 3b 0d
0a 3b 0d 0a
0d 0a 3b 20
74 65 77 61
73 65 72 20
temp.cfg
67 20 53
72 61 74
73 2d 6c
20 43 34
72 20 31
30 2e 36
63 6f 6d
0a 6e 6f
6e 20 0d
6b 20 61
0d 0a 3b
0d 0a 3b
70 72 6f
6e 66 69
20 20 20
64 64 72
2e 31 31
65 73 73
31 37 32
35 2e 32
0a 3b 0d
70 72 6f
2d 2d 20
79 20 50
63 6f 6e
hex
79 73
69 6f
65 76
69 20
20 31
2e 32
6d 61
20 63
0a 73
73 74
0d 0a
20 2d
74 6f
67 75
69 6e
65 73
36 0d
20 65
2e 32
35 35
0a 65
74 6f
42 6f
72 6f
66 69
74
6e
65
49
36
37
6e
6f
65
6d
70
2d
63
72
74
73
0a
74
34
2e
78
63
72
74
67
65
20
6c
50
20
54
64
6e
74
20
72
20
6f
61
65
20
3b
68
2e
30
69
6f
64
6f
75
6d
66
20
53
56
4d
2d
66
20
73
6f
49
6c
74
72
31
0d
65
37
2e
74
6c
65
63
72
;
;
;
;
;
;
;
;
;
;
;
;
;
;
;
;
;
;
;
;
;
;
;
;
;
; Showing System
Configuration f
or access.level
0 .....; C4i IPS
ec Router 1 16 V
ersion 10.6.27TM
....log.command.
errors ..no conf
iguration ..set
data.link astm s
erial0.0..;..pro
tocol ip..; .. I
nternet protocol
user configurat
ion ....
inter
nal.ip.address 1
72.24.78.116..;.
.
address ethe
rnet0.0 172.24.7
8.116 255.255.0.
0..;..;..;..exit
..;..;..protocol
bgp..; .. Borde
r Gateway Protoc
ol user configur
Config>
4.16. FIRMWARE-CHECKING
Enables the integrity checking for the firmware. This command is used together with the backup-files
command to ensure device availability when faced with serious cases of corruption in the filing
system.
This command is only effective in devices with partitioned flash memory.
Syntax:
Config> firmware-checking

II - 58
Doc.DM704-I
Rev.10.97
Example:
Config>firmware-checking
Config>
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
smartcard system (smartcard option).
Example:
Config>format smartcard
Formatting, please wait ... OK
Config>
4.18. GLOBAL-PROFILES
Defines the router PPP, ATM etc profiles.
Syntax:
Config>global-profiles
dial
Access
ppp
Access
tcp-menu
Access
trmtp-menu
Access
<profile name>
the DIAL profiles configuration environment
the PPP profiles configuration environment
the TCP profiles configuration environment
the TRMTP profiles configuration environment
<profile name> profile type identifier whose configuration menu you wish to access.
a) 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 Dm 732-I Call Profiles.
b) GLOBAL-PROFILES PPP
Accesses the PPP (Point-to-Point Protocol) profiles configuration environment.
Syntax:
Config>global-profiles ppp

II - 59
Doc.DM704-I
Rev.10.97
Example:
Config>global-profiles ppp
-- PPP Profiles Configuration -PPP Profiles config>
Please see the associated manual Dm 710-I PPP Interface.
c) GLOBAL-PROFILES TCP-MENU
Accesses the DEP protocol over TCP (Transport Control Protocol) profiles configuration
environment in order to encapsulate the traffic from POS or Dataphones in IP networks. For further
information on this configuration environment, please see manual Dm 263-I Forwarder DEP.
Syntax:
Config>global-profiles tcp-menu
Example:
Config>global-profiles tcp-menu
-- UDAFO TCP Configuration Menu -UDAFO TCP Cfg>
d) GLOBAL-PROFILES TRMTP-MENU
Accesses the DEP protocol over TRMTP (Trivial Message Transfer Protocol) profiles configuration
environment in order to encapsulate the traffic from POSs or Dataphones in IP networks. For further
information on this configuration environment, please see manual Dm 263-I Forwarder DEP.
Syntax:
Config>global-profiles trmtp-menu
Example:
Config>global-profiles trmtp-menu
-- UDAFO TRMTP Configuration Menu -UDAFO TRMTP Cfg>
4.19. LICENCE-CHANGE
Permits you to change the device license so that determined functionalities are enabled or disabled.
This command is only operative if you have a special license. After selecting the language the texts
will appear in for the interaction, the configuration for the current license is displayed. So the new
license can be introduced, after specifying the type of executed installation, you need to determine if
you want to enable all of the available functions. Once this process has finalized, you need to confirm
if you want these changes to be saved, and in affirmative cases you will be asked if the device should
be immediately restarted. If you wish to carry out this operation later on, the changes will not take
effect until the device has been restarted.
Syntax:
Config>licence-change
Example:
Config>licence-change
1. English
2. Espaol

II - 60
Doc.DM704-I
Rev.10.97
Language/Idioma[1]? 1
Current licence: 1 249 C4i_AdHoc IPSec SNA
Last executed task was Register
FUNCTIONALITY
-------------ISDN
IPSEC
SNA
VOIP
ENABLED
---------NO
YES
YES
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
-------------ISDN
IPSEC
SNA
VOIP
NOE
ENABLED
---------YES
YES
YES
YES
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>
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
devices
patch
pool
user
List generic configuration information

List router devices
Check the personalized parameters that are active
Number of bytes assigned to each memory pool
Displays the list of registered users
<info> identifier for the type of information you wish to list.
a) LIST CONFIGURATION
Lists the information on the active device configuration.
Syntax:
Config>list configuration

II - 61
Doc.DM704-I
Rev.10.97
Example:
Router Teldat Config>list configuration
Hostname: Router Teldat

Contact person: ......
Host Location: .......
No console authentication
No Telnet authentication
No FTP access authentication
Configurable protocols:
Num
Name
Protocol
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 Teldat Config>
b) LIST DEVICES
Lists the information on the available/configured interfaces in the device.
Syntax:
Config>list devices
Example:
Config>list devices
Interface
ethernet0/0
ethernet0/1
bri0/0
x25-node
Config>
Connector
GE0/FE0/LAN1
GE1/FE1/LAN2
BRI/ISDN1
---
Type of interface
ISDN Basic Rate Int
Router->Node
c) LIST PATCH
This command enables you to check the personalized parameters that are active.
Syntax:
Config>list patch
Example:
Config>list patch
Patch Name
Value
----------------------------------------ARPI_SND_LCL
1 (0x1)
Config>

II - 62
Doc.DM704-I
Rev.10.97
d) LIST POOL
This command is used to see the number of bytes assigned to each memory pool as well as the bytes
that have not been assigned.
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>
e) LIST USER
Displays the list of registered users, their password, access level, the access mode and whether they are
enabled or not.
Syntax:
Config>list user
Example:
Config>list user
Name
config
monitor
root
mabm
guest
viewer
Config>
Password
****************
****************
****************
****************
****************
****************
Access Level
[10]Config
[ 5]Monitor
[15]Root
[15]Root
[ 2]
[ 1]Events
Strict
N
N
N
N
Y
N
Enabled
N
Y
Y
Y
Y
Y
4.21. LOG-COMMAND-ERROR
This command initializes (deletes) the register of errors which has been produced when executing
commands from the configuration 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 so that later you
can see the possible errors using the dump-command-errors command.
4.22. MANAGEMENT
Enters the master router configuration environment.
Syntax:
Config>management

II - 63
Doc.DM704-I
Rev.10.97
Example:
Config>management
-- Routers management user configuration -Management config>
4.23. NETWORK
Accesses the commands menu to configure a specific interface. In order 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
CLI Error: Unrecognized command or invalid value
Config>
For further information on interfaces, please see the common configuration for interfaces manual
(Dm722-I Common Configuration for Interfaces) and the manual associated to the specific network
interface whose configuration environment you wish to access.
4.24. NO
Permits you to delete a previously added virtual interface created to be used by an ISDN basic access
B channel, an ATM subinterface, a PPP interface etc. This also permits you to eliminate a registered
user in the user management or the current configuration in order to configure the device from scratch.
Syntax:
Config>no <command> [parameters]
autoinstall
Delete autoinstall configuration
banner
Deletes a banner
configuration
Delete the static configuration
confirm-cfg
Reloads safe configuration
confirm-cfg-needed
Disables the need of configuration confirmation
contact-person
Assign a name or identification to the contact-person
description
Configuration description
device
Delete a virtual device
firmware-checking
Disables checking when firmware files are required
host-location
Physical location of the router
hostname
Assign a name to a device
login
Configure login options
password
Delete the device access password
privilege
Set default command privilege parameters
user
Delete a registered user
<command> name of the command where you want to invalidate execution.

[parameters] the parameters required for the specified command.

II - 64
Doc.DM704-I
Rev.10.97
a) NO AUTOINSTALL
Eliminates the autoinstallation parameters configuration.
Syntax:
Config>no autoinstall
Example:
Config>no autoinstall
Config>
b) 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>
c) NO CONFIGURATION
Eliminates the whole of the existing configuration.
Syntax:
Config>no configuration
Example:
Config>no configuration
Config>
d) NO CONFIRM-CFG
Rejects the current test configuration, therefore after receiving a warning message, the device restarts
with the previous configuration. For further information, please see confirm-cfg-needed and
confirm-cfg.
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 section 4.7.
e) NO CONFIRM-CFG-NEEDED
Disables the need to confirm the new configurations. Please see confirm-cfg-needed.

II - 65
Doc.DM704-I
Rev.10.97
Syntax:
Config>no confirm-cfg-needed
Example:
Config>no confirm-cfg-needed
Config>
This action can also be executed through SNMP. Please see section 4.7.
f) NO CONTACT-PERSON
Deletes the name of identification assigned as the contact person. For further information, please see
the set-contact-person command.
Syntax:
Config>no contact-person
Example:
Config>no contact-person
Config>
g) NO DESCRIPTION
Deletes the description(s) assigned to the device configuration. For further information, please see the
description command.
Syntax:
Config>no description
Example:
Config>no description
Config>
h) NO DEVICE
Eliminates the specified virtual interface.
Syntax:
Config>no device <name>
<name> name of the interface to delete.

Example:
Config>no device fr1
Config>
i) NO FIRMWARE-CHECKING
Disables checking when working with the firmware files.
Syntax:
Config>no firmware-checking
Example:
Config>no firmware-checking
Config>
j) NO HOST-LOCATION
Deletes the text indicating device location. For further information, please see the set-host-location
command.

II - 66
Doc.DM704-I
Rev.10.97
Syntax:
Config>no host-location
Example:
Config>no host-location
Config>
k) 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>
l) 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 deactivates upper-case/lower-case checking.
Example:
Config> no login case-sensitive
Config>
m) NO PASSWORD
Eliminates the device access password configuration. For further information, please see the set
password command.
Syntax:
Config>no password
Example:
Config>no password
Config>
n) 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 it is specified, it only eliminates the
command corresponding to this command-path. If it is not specified, it eliminates all the
privilege commands relative to the indicated access level.
Example:
Config>no privilege 3
Config>

II - 67
Doc.DM704-I
Rev.10.97
o) 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. In this case, you can only delete the rest of the
users, as contrariwise you will not be able to manage the remaining users. If you eliminate all the
users except for the last Root, then this may be deleted. In this way, the system will not request user
or password in order 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>
4.25. NODE
This allows you to access the node configuration (X.25, XOT and 270). You can also access this through
the network command followed by the interface over which the node is configured.
Syntax:
Config>node <name>
270
Access the 270 configuration
x25
Access the X25 node configuration
xot
Access the XOT configuration
<name> name of the part of the node whose configuration menu you wish to access.
There are three types of configurable nodes:
a) NODE 270
Accesses the configuration environment for the node part relative to 270 in the device.
Syntax:
Config>node 270
Example:
Config>node 270
270 Config>
b) NODE X25
Accesses the configuration environment for the node part relative to the X.25 for the device.
Syntax:
Config>node x25
Example:
Config>node x25
X25 Config>
For further information on the configuration environment for the node part relative to X.25, please see
manual Dm 707-I X.25 Configuration.

II - 68
Doc.DM704-I
Rev.10.97
c) NODE XOT
Accesses the configuration environment for the node part relative to the XOT (X.25 over TCP/IP).
Syntax:
Config>node xot
Example:
Config>node xot
XOT config>
For further information on the relative node part configuration environment, please see manual Dm
713-I XOT Protocol.
4.26. PRIVILEGE
Permits you to specify personalized execution privileges for process commands for the device.
Syntax:
Config>privilege <level> <command path> [all]
<level> this is the access level to assign to the command specified in <command path>.
<command path> this is the command path.
<all> this is an option which permits you to apply the specified level to all the
subcommands (where the paths coincide) for the command specified in <command path>.
The <level> parameter, which specifies the access level to assign to the command, permits values
between 0 and 15.
The <command path> parameter, which specifies the specific path for the command whose access
level you wish to personalize, 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 which identifies 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, the said
initial character will be omitted and you will not be able to 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 >)
Config$
The >config path refers to both the static and the dynamic configuration. It is not possible to give
different permissions 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.

II - 69
Doc.DM704-I
Rev.10.97
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.).
In order to find the complete path for a parameter configuration command in a device, execute show
from the configuration.
Example:
Config>show config
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
;
;
;
;
exit
;
;
;
network ethernet0/1
;
exit
;
;
;
;
network x25-node
;
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
;

II - 70
Doc.DM704-I
Rev.10.97
base-interface
; -- Base Interface Configuration -base-interface serial0/0 link
;
exit
;
exit
;
;
;
dump-command-errors
end
; --- end --Config>
For example, to establish an access level 12 to the assignment of a base interface to net ppp1 (baseinterface serial0/0 link command), the path you need to use is >config>network ppp1>baseinterface>base-interface serial0/0 link.
The <all> option permits you to apply the specified level to all the subcommands for that specified in
<command path> i.e. to all those commands whose path coincides from the start (taking into account
all the wildcards).
Example:
Config>privilege 12 >config>network all
Config>
This configuration is applied at the access level for all commands whose path 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 execution ends with a carriage return <CR>. Consequently, if we 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 we access with a user level 10 and try and carry out the following executions:
Config>confirm-cfg
CLI Error: Incomplete command
Config>protocol ip
-- Internet protocol user configuration -IP config>no description
IP config>
Here we get an error in the execution as these commands have an access level 12, however if we
executed:
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 which have access level 10 by default.
This system permits you to specify different access levels for the same command, attending the
possibility of creating two types of users: default and strict (see the user command). In cases where
this situation arises and a default user (not strict) accesses, the system will assigned the most
restrictive access layer (highest) to the command.

II - 71
Doc.DM704-I
Rev.10.97
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 devices IP telephony. Two users are defined, one with root
privileges and the other with access 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 the access lists 50 and 51 in order to 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. In this way, the user has full control over the IP telephony configuration for the
device; however he cannot modify any routing parameter nor 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
; -- 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

II - 72
Doc.DM704-I
Rev.10.97
Additionally the sending of events to a syslog server is configured with each command executed in the
device, so that there is a register of all the commands executed by each user. The IP of the device
which sends the event and the complete prompt used when executing the device is included in the
event. As you can see below, the event also includes the user who executed the command and where
the user connected, this could be a remote IP or local console.
06-23-2006
CNSL:001 usr
06-23-2006
CNSL:001 usr
06-23-2006
CNSL:003 usr
06-23-2006
CNSL:001 usr
06-23-2006
CNSL:003 usr
06-23-2006
CNSL:001 usr
10:54:48
Local7.Info
172.24.78.156 Jun 23
voip (172.24.79.34:209) exe *logout
10:54:31
Local7.Info
172.24.78.156 Jun 23
voip (172.24.79.34:209) exe Config$<Esc>
10:54:27
Local7.Info
172.24.78.156 Jun 23
voip (172.24.79.34:209) run Telephony Config$exit
10:54:21
Local7.Info
172.24.78.156 Jun 23
voip (172.24.79.34:209) exe Telephony Config$sho conf
10:54:18
Local7.Info
172.24.78.156 Jun 23
voip (172.24.79.34:209) run Config$telephony
10:54:02
Local7.Info
172.24.78.156 Jun 23
voip (172.24.79.34:209) exe *p 5
09:46:43
09:46:26
09:46:23
09:46:16
09:46:13
09:45:57
4.27. PROTOCOL
This accesses the configuration environment of a specific protocol. The protocol command followed by a
protocol name that accesses the configuration of the desired protocol. The number of available protocols
depends on the type of device and on the application license possessed by the device.
To enter the configuration environment of a specific protocol:
1. Enter protocol ? to see the list of configurable protocols in the router:
Example:
Config>protocol ?
arp
Access
asrt
Access
bfd
Access
bgp
Access
dep
Access
dhcp
Access
dls
Access
dot1x
Access
gw104
Access
nhrp
Access
h323
Access
igmp
Access
ip
Access
ipv6
Access
l2tp
Access
mgcp
Access
noe
Access
ospf
Access
pim
Access
rip
Access
sccp
Access
sip
Access
snmp
Access
Config>protocol
ARP protocol
ASRT protocol
BFD protocol
BGP protocol
DEP protocol
DHCP protocol
DLS protocol
802.1X protocol
GW-104 protocol
NHRP protocol
H323 protocol
IGMP protocol
IP protocol
IPv6 protocol
L2TP protocol
MGCP protocol
NOE protocol
OSPF protocol
PIM protocol
RIP protocol
SCCP protocol
SIP protocol
SNMP protocol
2. Enter protocol following by the name of the protocol you wish to configure. Subsequently the
specified protocol prompt will appear. From here you can enter the chosen protocols
configuration commands.

II - 73
Doc.DM704-I
Rev.10.97
Example:
Config>protocol arp
-- ARP user configuration -ARP config>
3. Enter exit in order to return to the Config> prompt menu.

Example:
ARP config>exit
Config>
Syntax:
Config>protocol <name>
<name> name of the protocol whose configuration menu you wish to access.
Example:
Config>protocol ip
-- Internet protocol user configuration -IP config>
4.28. QUICK CONFIGURATION

This accesses the quick menu configuration environment. Please see the associated manual Dm 211-I.
This command or functionality depends on the device i.e. it might not apply to your device.
Example:
Config>quick-configuration
-- Quick Configuration Menu -Quick config>
4.29. SAVE
This allows you to store the configuration in the active storage unit. The active storage unit is configured
through the config-media command.
Before executing this, if the command is not accompanied by parameters indicating the contrary, the
operation will request confirmation for the process. If the confirmation is positive, the selected media
will be accessed and subsequently the operation results will be displayed. In cases where the active
unit is made up of various medias, the operation will be 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, this is 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 will be restored if confirmation is not carried out. However, this does not
eliminate the timer so once the test time has timed out if the device has not restarted, the previous
configuration will be restored. For further information, please see the confirm-cfg and confirm-cfgneeded commands.
On using the save command, its essential you remember which configuration is being saved. There
are two configurations in the device at all times, which coincide on startup until the user modifies one

II - 74
Doc.DM704-I
Rev.10.97
of them. One configuration is accessible from the RUNNING-CONFIG (Config$) process and is used
at all times. The other configuration is accessible from the CONFIG (Config>) process and is only
available for editing.
Consequently, if you execute save in the RUNNING-CONFIG process, you are saving the
configuration being used when executing the save command. However, if you execute save from the
CONFIG process, you will be saving the configuration you edited in the 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 this is not included, the device requests confirmation.
<file-name> filename where you wish to save the configuration. If you do not enter any
name, the device will use the active configuration filename (see set file-cfg).
Example 1:
Config>save
Save configuration (Yes/No)? y
Writing configuration... OK on Flash
Config>
Example 2:
Config>save yes atlas11
Writing configuration... OK on Flash as ATLAS11
Config>
4.30. SET
This allows you to configure various general parameters in the system.
Syntax:
Config>set <parameter>
application-active
console
contact-person
data-link
default-conf
file-cfg
ftp
host-location
hostname
inactivity-timer
login
password
pool
schedule-restart
telnet
web-probe
Permits you to select the code used to boot the router

Set console configuration
Assign a name or identification to the contact-person
Type of data link for a WAN line
Restores the default configuration
Configure a configuration file as active
Permits you to access the FTP configuration menu
Physical location of the router
Assign a name to a device
Configure the maximum inactivity time
Configure login options
Configure the device access password
Number of bytes assigned to each memory pool
Allows to configure router reset schedule
Access the TELNET protocol configuration
Access the Web probe configuration
<parameter> name of the parameter you wish to configure.

II - 75
Doc.DM704-I
Rev.10.97
a) SET APPLICATION-ACTIVE
Permits 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 wish to boot the router with. If you dont fill out
this field, the available code files will be displayed.
Example:
Config>set application-active atlas.bin
Config>
b) SET CONSOLE
This command accesses the configuration menu in order 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.
ACCOUNTING
This command associates a list of accounting methods that have been defined using the AAA feature.
In this way, the console service applies the accounting exec methods from the list when an access to
the Shell is registered, and the accounting commands methods from the list when an executed
command is registered.
Syntax:
Con config>accounting {commands <level> | exec} <listname>
commands indicates that the methods list contains accounting commands.

<level> indicates the access level for the command you want to count.
exec indicates that 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 the accounting for a level 10
command is executed.

II - 76
Doc.DM704-I
Rev.10.97
Example 2:
Con config>accounting exec AccExec
Con config>
In example 2, the AccExec methods list is configured to be used when the accounting for access to the
Shell is executed.
The lists of methods can only be applied if the AAA feature is enabled. To do this, once the AAA
configuration has finalized, you need to enable it so the lists can be applied to the different services.
The information on how to configure the AAA feature can be found in manual Dm800-I AAA
Feature.
AUTHORIZATION
This command associates a list of authorization methods that have been defined using the AAA
feature. In this way, the console service applies the authorization exec methods from the list when
authorization is needed from the Shell and authorization commands when authorization from a
command is needed.
Syntax:
Con config>authorization {commands <level> | exec} <listname>
commands indicates that the methods list contains authorization commands.

<level> indicates the access level for the commands that require authorization.
exec indicates that 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 AuthorCmds methods list is configured to be used when authorization is required
from the level 10 commands.
Example 2:
Con config> authorization exec AuthorExec
Con config>
In example 2, the AuthorExec methods list is configured to be used when authorization is required
from the Shell.
Feature.
FUNCTION
This command permits 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) functionality. In these 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 equipments devices.

II - 77
Doc.DM704-I
Rev.10.97
Example:
Config>list dev
Interface
ethernet0/0
serial0/0
uart0/0
x25-node
cellular1/0
cellular1/1
ppp1
Config>
Connector
EXP/SWITCH
SERIAL0/WAN1
CONF
--SLOT1
SLOT1
---
Type of interface
Marvell Fast Ethernet Switch
Auto Install Interface
Asynchronous Serial Line
Router->Node
AT COM
AT COM
Generic PPP
This command permits the following options:

Con config>function ?
set
Set CONF port functionality
list
List CONF port functionality
Con config>
As this is a function that affects the device BIOS, as in Asynchronous serial port mode the device
doesnt send data through this interface during startup, this command is not affected by the SAVE
command. The device also has to be rebooted 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 command that affects the BIOS behavior on startup, the behavior of
the CONF port is configured when installing the device and subsequently is not
modified.
FUNCTION SET
This permits you to select the operating mode for the CONF port. The two permitted 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
This command allows you to list the mode the CONF port is configured in.
Syntax:
Con config>function list

II - 78
Doc.DM704-I
Rev.10.97
Example:
Con config>function list
CONF port functionality: async-serial-line
Con config>
LOGIN ATTEMPTS
This command allows you to configure the number of successive failed login attempts before blocking
access through the local console.
Syntax:
Con config>login attempts <max_attempts>
<max_attempts> this is the maximum number of login attempts.

Example:
Con config>login attempts 2
Con config>
LOGIN AUTHENTICATION
This command associates an authentication login methods list defined through the AAA feature. In
this way the console service can apply the methods from the associated list when authentication needs
to be 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 accessing through the console.
Feature.
LOGIN BLOCKING
This command allows you to configure the blocking time for the local console in cases where the
configured number of failed login attempts has been reached.
Syntax:
Con config>login blocking <blocking_time>
<blocking_time> this is the time that the local console stays blocked for in cases where
the configured number of failed login attempts has been reached.
Example:
Con config>login blocking 1m
Con config>

II - 79
Doc.DM704-I
Rev.10.97
SPEED
This command 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
14400
bits
19200
bits
38400
bits
57600
bits
115200
bits
Con config>speed
Con config>
?
per second
per second
per second
per second
per second
per second
115200
EXIT
Returns to the previous prompt.
Syntax:
Con config>exit
Example:
Con config>exit
Config>
c) SET CONTACT-PERSON
This allows you to assign a name or identification to the contact-person for this router. The name is
limited to a maximum 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>
d) 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.

To find out what types are available, enter the set data-link ? command.

II - 80
Doc.DM704-I
Rev.10.97
Example:
Config>set data-link ?
arly
Alarm Relay on asynchronous 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
ethernet0/0
ethernet0/1
serial0/0
serial0/1
bri0/0
x25-node
Config>
Connector
GE0/FE0/LAN1
GE1/FE1/LAN2
SERIAL0/WAN1
SERIAL1/WAN2
BRI/ISDN1
---
Type of interface
Auto Install Interface
X25
ISDN Basic Rate Int
Router->Node
Example:
Config>set data-link frame-relay serial0/0
Config>list devices
Interface
ethernet0/0
ethernet0/1
serial0/0
serial0/1
bri0/0
x25-node
Config>
Connector
GE0/FE0/LAN1
GE1/FE1/LAN2
SERIAL0/WAN1
SERIAL1/WAN2
BRI/ISDN1
---
Type of interface
Frame Relay
X25
ISDN Basic Rate Int
Router->Node
Subsequently, you can enter the list devices command to see if the above command has been
successful.
e) SET DEFAULT-CONFIG
Eliminates the current configuration and restores the default configuration. This command or its
functionality 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>
f) SET FILE CFG

Permits you to configure a configuration file as active and it will be this one that will be processed
when the device is restarted.

II - 81
Doc.DM704-I
Rev.10.97
The active storage unit will also be 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 will use the default configuration.
Example:
Config>set file-cfg
Config Media: Flash only
A:
A:
Current config: ROUTER
Config>set file-cfg
Config>
ROUTER
ATLAS11
494
523
12/05/06
12/11/06
20:15
15:15
Flash
Flash
g) SET FTP
Accesses the FTP (File Transfer Protocol) configuration menu. For further information please see the
associated manual Dm724-I FTP Protocol.
Syntax:
Config>set ftp
Example:
Config>set ftp
-- FTP user configuration -FTP config>
h) SET HOST-LOCATION
Physical location of the router. This information can be 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>
i) SET HOSTNAME
This permits you to assign a name to a device. This information can be seen by entering list
configuration.
Syntax:
Config>set hostname <name>
<name> device name. Up to a maximum of 79 characters is permitted for the said name.
Example:
Config>set hostname SuperRouter
Config>

II - 82
Doc.DM704-I
Rev.10.97
j) SET IGNITION-OFF-POWERDOWN-TIMER
This command is only available in devices that have the power management feature,
usually intended to be installed in vehicles and be powered by the vehicle battery. To
determine if your device supports this feature, we recommend you check the device
installation manual.
This command permits you to configure the time the device remains on after switching off the ignition
in the vehicle it is installed in. The aim is to keep the device operating during a configurable period of
time, automatically powering down once this period has timed out thus preventing the battery, in the
vehicle where this is installed, from being used
Syntax:
Config>set ignition-off-powerdown-timer [<time> | disabled]
<time> this is the time (in minutes) that the device remains powered after switching off
the vehicles ignition where the said device is installed. Once this timer has timed out, the
device executes an ordered shutdown and subsequently powers down. The permitted
range is between 0 and 1044 minutes (24 hours).
disabled this 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 and if you do not configure a time period then the
device will power down as soon as the ignition, in the vehicle where it is installed, is
switched off (this is the same as a set ignition-off-powerdown-timer disabled).
k) SET INACTIVITY-TIMER
This allows you to configure the maximum inactivity time in the process that accesses the device
through a remote terminal (TELNET). Once this has timed out, the devices Telnet server
disconnects.
This maximum inactivity time period is also applied to the local connection in the device console. If
the configured inactive time period times out without any of the keys being touched, the local
connection will close. In this case the user must reenter the password again when he wishes to use the
console.
Syntax:
Config>set inactivity-timer [<time> | disabled]
<time> maximum inactivity time in minutes you wish to set before the telnet connection
closes or the console blocks. The permitted 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 the 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).
l) SET LOGIN
Permits you to configure parameters relative to the device access name.

II - 83
Doc.DM704-I
Rev.10.97
Syntax:
Config>set login <option>
case-sensitive
Activate login case-sensitiveness
<option> this is the option to configure.
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 the user name authentication is
deactivated.
m) SET PASSWORD
This permits 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>
n) SET POOL
This permits you to configure the memory distribution in the devices various POOLs. If this is not
correctly configured, it can cause the device to 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>
This command is problematic and should only be executed by a specialist. An incorrect

configuration can cause the device to malfunction.

II - 84
Doc.DM704-I
Rev.10.97
o) SET SCHEDULE-RESTART
The aim of this command is to periodically execute a 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 will begin. This must be expressed in hh:mm format. The exception being in
the case where the value is 0.
<time-offset> this indicates the period movement to execute device reset. Its units are
seconds, that 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 its used in a
different way:
o day-time = 0. Indicates the time that must lapse from device start up in order to
reset.
o day-time 0. Indicates the time that must lapse 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>
This command permits you to configure the devices programmed reset in three different ways:
a) Every day at the same time:
To do this you must not configure the offset value, i.e. it should be 0.
In the following example the device restarts every day at 3:30.
Config> Config>set schedule-restart time 03:30
Config>
Or:
Config> Config>set schedule-restart time 03:30 offset 0
Config>
b) Every so many days or an hour + offset:

You need to program the time when 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 dont do that you have
to calculate when a device reset 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, it will only be necessary to attend 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 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>
c) A period of time after device start up:

II - 85
Doc.DM704-I
Rev.10.97
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 until the reset occurs.
In this example, this restarts every 18 hours.
Config> Config> set schedule-restart time 0 offset 18h
Config>
We dont recommend the case a) configuration in devices that do not have a Real Time Clock powered
with a battery, or another type of system clock updating (NTP).
To eliminate this programming you can set both fields to 0 or execute the NO command. E.g.
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 firmware or saving the configuration, you must ensure
that the automatic process DOES NOT reset the device.
p) SET TELNET
Accesses the TELNET protocol configuration. For further details please see the associated manual
Dm 738-I TELNET Protocol.
Syntax:
Config>set telnet
Example:
Config>set telnet
-- Telnet user configuration -Telnet config>
q) SET WEB-PROBE
This 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 on web poll configuration environment, please see manual Dm 749-I NSM
(Network Service Monitor).
4.31. TELEPHONY
Permits access to the Voice over IP (VoIP) telephony parameters configuration environment.
Syntax:
Config>telephony

II - 86
Doc.DM704-I
Rev.10.97
Example:
Config>telephony
-- Telephony configuration -Telephony Config>
For further information on this configuration environment, please see manual Dm 722-I Voice over IP.
4.32. TIME
This allows you to change and check the date and time of the device. Its also possible to configure the
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:
a) TIME LIST
This command allows you 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>
b) TIME SET
This command allows you 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.

II - 87
Doc.DM704-I
Rev.10.97
Example:
Config>time set 3 2 5 3 16 29 59
Config>
Some devices lose the date and time settings when restarted, in this case, these
parameters must be configured using the NTP Protocol. Please see the associated
manual Dm728 NTP Protocol for further information.
c) TIME NO
Invalidates a command action within the time configuration environment or establishes the default
values.
Syntax:
Config>time no <option>
<option> specifies the selected option. The available options are summer-time and
timezone.
TIME NO SUMMER-TIME
Deletes the previously configured summer-time application period.
Syntax:
Config>time no summer-time <option>
zone-name
Deletes summer time zone name
<cr>
Deletes summer time configuration
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
log-command-errors
no configuration
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
log-command-errors
no configuration
;
dump-command-errors
end
Config>

II - 88
Doc.DM704-I
Rev.10.97
ii) time no summer-time

Deletes the entire configuration associated with the summer period, both for dates and the start and
end times for these with the name associated to the time period.
Syntax:
Config>time no summer-time
Example:
Config>show menu
log-command-errors
no configuration
time summer-time zone-name "CET"
;
dump-command-errors
end
Config>time no summer-time
Config>show menu
log-command-errors
no configuration

dump-command-errors
end
Config>
d) TIME SUMMER-TIME
Through this command you can configure the summer time start and end times. Here you apply an
offset of one hour that must be added to the clock value which you would obtain 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

There are four available options (three in configuration and one in monitoring).
TIME SUMMER-TIME DATE
Permit 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).

II - 89
Doc.DM704-I
Rev.10.97
<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
<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>
TIME SUMMER-TIME RECURRING

Permits 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 introduced, 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 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> the weekday you want summer time to start. Indicate which day this is
by entering the first three appropriate letters (mon/tue/wed/thu/fri/sat/sun).
<start month> the month to set for starting the summer-time period. Indicate which
<start hour> this is the time, in hours and minutes (HH:MM) to set for starting the
summer-time period.
<end week number> the number of the week within the month to apply the return to the
normal timetable (1 to 5).
<end week day> the day of the month to set for the return to the normal timetable.
Indicate which day this is by entering the first three appropriate letters
(mon/tue/wed/thu/fri/sat/sun).
<end month> the month to set for the return to the normal timetable. Indicate which
month by using the first three appropriate letters (jan/feb/mar/apr/may/jun/jul/aug/sep
/oct/nov/dec).
<end hour> this is the time, in hours and minutes (HH:MM) to set to return to the normal
timetable.
Example:
Supposing that the 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), you need to enter the following:

II - 90
Doc.DM704-I
Rev.10.97
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 Sundays. In order 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 will be applied to the last day of
the week configured within the configured month, both in cases where 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>
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 commas (e.g. description description containing spaces).
Example:
Config>time summer-time zone-name CET
Config>
Below you will see a table containing the acronyms commonly used in the distinct time zones for this
parameter.
ACRONYM
GMT
BST
IST
WET
WEST
CET
CEST
EET
EEST
MSK
MSD
TIME ZONE NAME AND OFFSET WITH RESPECT TO UTC

Europe
Greenwich Mean Time, as UTC
British Summer Time, as UTC + 1 hour
Irish Summer Time, as UTC + 1 hour
Western Europe Time, as UTC
Western Europe Summer Time, as UTC + 1 hour
Central Europe Time, as UTC + 1
Central Europe Summer Time, as UTC + 2
Eastern Europe Time, as UTC + 2
Eastern Europe Summer Time, as UTC + 3
Moscow Time, as UTC + 3
Moscow Summer Time, as UTC + 4
AST
United States and Canada

Atlantic Standard Time, as UTC 4 hours

II - 91
Doc.DM704-I
Rev.10.97
ADT
ET
EST
EDT
CT
CST
CDT
MT
MST
MDT
PT
PST
PDT
AKST
AKDT
HST
Atlantic Daylight Time, as UTC 3 hours

Eastern Time, either as EST or EDT, depending on place and time of year
Eastern Standard Time, as UTC 5 hours
Eastern Daylight Saving Time, as UTC 4 hours
Central Time, either as CST or CDT, depending on place and time of year
Central Standard Time, as UTC 6 hours
Central Daylight Saving Time, as UTC 5 hours
Mountain Time, either as MST or MDT, depending on place and time of year
Mountain Standard Time, as UTC 7 hours
Mountain Daylight Saving Time, as UTC 6 hours
Pacific Time, either as PST or PDT, depending on place and time of year
Pacific Standard Time, as UTC 8 hours
Pacific Daylight Saving Time, as UTC 7 hours
Alaska Standard Time, as UTC 9 hours
Alaska Standard Daylight Saving Time, as UTC 8 hours
Hawaiian Standard Time, as UTC 10 hours
Australia
Western Standard Time, as UTC + 8 hours
Central Standard Time, as UTC + 9.5 hours
Eastern Standard/Summer Time, as UTC + 10 hours (+11 hours during summer
time)
WST
CST
EST
TIME SUMMER-TIME LIST

Displays the period established as summer time.
Syntax:
Config>time summer-time list
Example 1:
Absolute summer time configured:
Start: Date: 30/03/03
Time: 02:00
End:
Date: 26/10/03
Zone-name: CET
Time: 03:00
Config>
Example 2:
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 its possible to obtain the summer time configuration in text mode through the
show config command.

II - 92
Doc.DM704-I
Rev.10.97
Example 1:
Config>show menu
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
log-command-errors
no configuration
time summer-time recurring 4 sun mar 02:00 4 sun oct 03:00
;
dump-command-errors
end
Config>
e) TIME TIMEZONE
Through this command you can configure the differences in hours with respect to UTC time, thus
determining the time zone where the device is located.
Syntax:
Config>time timezone <-1212>
Example:
Config>time timezone 1
Config>
The permitted values are from -12 to 12. Default is 1.
4.33. UCI
The UCI command allows you to configure the Teldat Router encryption unit.
Syntax:
Config>uci <option> [parameters]
cfg
change cfg
keys
lqueue
mode
table
user_password
lqueue

[parameters] parameters which must be entered depending on the selected option.
4.34. UNSET-DEMO-LICENSE
Unsets demo license currently being used in the device so that after a restart the base license is used.
This command is only enabled when there actually is an active demo license.

II - 93
Doc.DM704-I
Rev.10.97
Syntax:
Config> unset-demo-licence
Example:
Config>unset-demo-licence
Demo licence disabled. Restart device to start using the base licence
Config>
4.35. USER
Permits you to crate and configure the users who have permission to access the device.
a) 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 introduced for the specified user.
<pwd> access password in the selected format to give to the specified user.
Example:
Config>user teldat 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 the said users will always appear using the
hash-password option, independently 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 password, the said user will have to be recreated
with a new access password.
Example:
Config>show menu
log-command-errors
no configuration
user teldat hash-password E7AE08B3FEB1F020EEEDE75FCD0D41F1
;
dump-command-errors
end
Config>
b) User management
Once two or more users 2 have been created, you can manage the access level for them, enable or
disable their access, etc. To access a user configuration menu, carry out the following process:
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.

II - 94
Doc.DM704-I
Rev.10.97
Syntax:
Config>user <name>
access-level
active
hash-password
keymanager
no
password
<option> <parameter>
Specify the user access level
Activate the user
Entry the hash of the password
IPSec keys manager
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:
access-level
Specifies the user access level.
Syntax:
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>

<level> access level you wish to assign to the specified user. You can 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> this is the device operating mode with respect to the configured access level.
There are two modes:
o Default. The user can execute commands that require an execution level less or
equal to his/her access level.
o Strict. The user can execute commands that require an execution level exactly the
same as his/her access level.
Example:
Config>user teldat2 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.
active
Enables access to the device for a user.
Syntax:
Config>user <name> active
<name> name of the user to enable.

II - 95
Doc.DM704-I
Rev.10.97
Example:
Config>user teldat2 active
Config>
You can display the created users access level through the list user command in the configuration
console.
By default in creating new users, access to the device, for the said users, is enabled.
hash-password
Configures the password hash code for the user.
Syntax:
Config>user <name> hash-password <hash code>

<hash code> password hash code to assign to the specified user.
Example:
Config>user teldat2 hash-password E7AE08B3FEB1F020EEEDE75FCD0D41F1
Config>
You can view the created users password hash code by using the show configuration command in
the configuration console.
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, should there be one, by another keymanager user.
This command divides the permission management system creating two completely independent
profiles: one only for IPSec key configuration 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 teldat2 keymanager
Config>
Given the existence of this type of special user, there would be no specific user who has
total control over the device configuration system. Therefore, 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.
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.

II - 96
Doc.DM704-I
Rev.10.97
There are two possible options.

active
Disables the user access to the device.
Syntax:
Config>user <name> no active
<name> user name.

Example:
Config>user teldat2 no active
Config>
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 teldat2 no keymanager
Config>
password
Configures the password for the user.
Syntax:
Config>user <name> password <text>

<text> password to assign to the specified user.
Example:
Config>user teldat2 password trescantos1985
Config>
4.36. 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, however, is automatically added as the last command in the device configuration files
(cfg) on executing the save or show config commands.
Syntax:
Config>end

II - 97
Doc.DM704-I
Rev.10.97
Example:
Config>show config
log-command-errors
no configuration
;
;
network ethernet0/0
;
exit
;
;
;
network ethernet0/1
;
exit
;
;
;
;
network x25-node
;
Exit
;
;
;
dump-command-errors
end
; --- end --Config>

II - 98
Doc.DM704-I
Rev.10.97
Chapter 3
Teldat Router Monitoring
1. Introduction
This chapter describes the devices monitoring (p3) process. This process permits you to view the system
status as well as the statistics gathered by the device. It also enables users with an appropriate access level
to manage the said statistics and to execute operating tests over certain 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-). In order 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, 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 access 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 the terminal of another session connected to the device
to force a user to exit a determined menu or to force the termination of a session established
with the device). In order to execute these commands, the user must have a ROOT access
level (level 15).
Within the monitoring process, the device will only display, when requesting help (?), those
commands that the user has permission to execute.
The access levels available in the device as well as the configuration process for these are specified in
chapters 1 (section 3.1 Teldat Router connection) and 2 (section 4.32 USER) in this manual.
TELDAT ROUTER - Monitoring

III - 100
Doc.DM704-I
Rev.10.97
2. Monitoring procedure commands

MONITOR process entry/exit
To enter the monitoring procedure MONITOR from prompt * in the Console Manager GESTCON,
enter the monitor command or the process command followed by the number which identifies 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)
BUFFER
Lists the MONITOR process commands.

Displays information about packet buffers assigned to each
interface.
Clears network statistics.
Lists the status of current protocols and interfaces.
Displays network hardware statistics or statistics for the
specified interface.
Displays the error counters.
Enters the Event Logging System environment.
Accesses to monitoring commands for router features outside
the usual protocol and network interface monitoring
processes.
Displays the last changes made in the configuration.
Accesses the monitoring commands for memory management
in the device.
Enters the master router environment.
Displays memory, buffer and packet data.
Enters the console environment of a specified network.
Enters the node monitoring environment.
Enters the commands environment for a specified network.
Displays buffer statistics for a specified interface.
Accesses the quick menu monitoring.
Displays statistics for a specified interface.
SYSTEM
Permits monitoring of the systems memory
and stacks, the use of the CPU, configure the speed of the
console port, display the firmwares needed so the device
operates
correctly,
activate
determined
debugging
information, show the history of the users who have accessed
the device, view the open Telnet and SSH sessions and
exchange commands or messages between the terminals
corresponding to these open sessions.
CLEAR
CONFIGURATION
DEVICE
ERROR
EVENT
FEATURE
LAST-CONFIG-CHANGES
MALLOC-MONITOR
MANAGEMENT
MEMORY
NETWORK
NODE
PROTOCOL
QUEUE
QUICK
STATISTICS

III - 101
Doc.DM704-I
Rev.10.97
TFTP
TELEPHONY
Accesses the devices TFTP client.

Enters the monitoring environment for the device telephony
functions.
Encryption statistics.
Accesses the VisorNet monitoring environment.
Accesses the Web poll monitoring.
Activates or views the logging level for events not included in
the Event Logging System.
UCI
VISORNET
WEB-PROBE
LOG
2.1. ? (HELP)
List the commands that are available at the current prompt level. You can also type ? after a specific
command to list its options.
Syntax:
+?
Example:
+?
buffer
clear
configuration
device
error
event
feature
last-config-changes
log
malloc-monitor
management
memory
network
node
protocol
queue
quick
statistics
system
telephony
uci
web-probe
exit
Packet buffers assigned to each interface

Clear network statistics
List status of current protocols and interfaces
List statistics for the specified interface
List error counters
Event Logging System environment
Access to monitoring commands for router features
Display the last changes made in the configuration
Dump log data
Malloc monitor information
Master router environment
Display memory, buffer and packet data
Enter the console environment of a specified network
Enter the node monitoring environment
Enter the commands environment for a specified
protocol
Display buffer statistics for a specified interface
Access the quick menu monitoring
Display statistics for a specified interface
Permit monitoring of the systems memory and stacks
Monitoring environment for the telephony functions
Encryption statistics
Access the Web poll monitoring
2.2. BUFFER
Displays information about packet buffers assigned to each interface.
Note: Each buffer on a single device is the same size and is dynamically built. Buffers
vary in size from one device to another.
Syntax:
+buffer [<verbose> | <interface>]
<interface > name of the interface you wish to display information for.
<verbose> displays additional information.

III - 102
Doc.DM704-I
Rev.10.97
To obtain the available interfaces in the device, enter the command configuration at the + prompt. If
you do not enter a name, information for all the interfaces will be displayed.
Example:
+buffer
Interface
ethernet0/0
serial0/0
serial0/1
serial0/2
bri0/0
x25-node
Buffer size:
Packet size:
Trailer size:
Packet offset:
Input Buffers
Req Alloc
Low
40
40
5
40
40
5
0
0
0
0
0
0
160
160
5
0
0
0
Curr
40
40
0
0
160
100
Buffer
Hdr Wrap
22
62
18
62
0
62
0
62
17
62
20
62
Sizes
Data Trail
1500
4
2048
12
0
0
0
0
2048
12
1500
0
Total
1588
2140
62
62
2139
1582
Curr
40
Buffer
Hdr Wrap
22
62
Sizes
Data Trail
1500
4
Total
1588
2144
2048
12
84
+ buffer ethernet0/0
Interface
ethernet0/0
Buffer size:
Packet size:
Trailer size:
Packet offset:
Input Buffers
Req Alloc
Low
40
40
5
2144
2048
12
84
The meaning of each of the fields is as follows:

Interface
Interface name.
Input buffers
Req
Alloc
Low
Curr
Number of input buffers requested.

Number of input buffers allocated.
Low water mark (flow control).
Current number of input buffers in this device. If value is 0 the device is disabled.
When a packet is received, if the value of Curr is below Low, then the flow control
can select it. See the queue command 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.

Margin given for MAC, LLC or network level.
Maximum data link level packet size.
Sum of the largest MAC and hardware trailers.
Global size of each packet buffer. This value is calculated by adding together the
previous four fields.
Wrap
Data
Trail
Total
Alloc
Bytes
Amount of buffer memory bytes for this device. This value is determined by
multiplying the values of Curr x Total.

III - 103
Doc.DM704-I
Rev.10.97
Buffer size
Packet size
Trailer size
Packet offset
Complete size of the buffer.

Maximum packet size.
Maximum trailer size.
Packet offset in the buffer.
2.3. CLEAR
Restarts the statistical information on all of the routers interfaces zeroizing all the counters. This
command is useful when searching for changes in large counters. However, you need to bear in mind
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)?
+
2.4. CONFIGURATION
Displays information about the protocol and network interfaces. The output presented by this
command can be divided into three sections: the first section contains data such as the router
identification, software version, boot ROM version, and the state of the watchdog, as well as the
device date and time together with the length of time since the last reboot. The second and third
sections display information regarding protocols that can be monitored and the current interfaces.
Syntax:
+configuration
Example:
+configuration
Teldat's Router, ATLAS50 9 48 S/N: 524/00130
P.C.B.=91 Mask=0c10 Microcode=134f0 CLK=262144 KHz
KHz
ID: AT50-16F64R L9.48
BUSCLK=65536 KHz PCICLK=32768
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:
Date: Wednesday, 12/27/06
Router uptime: 9m4s
Num
0
Name
IP
Active user:
Time: 12:41:40
Protocol
DOD-IP

III - 104
Doc.DM704-I
Rev.10.97
3
4
6
11
13
17
30
31
ARP
H323
DHCP
SNMP
RIP
SIP
EAPOL
Preauth
4 interfaces:
Connector
GE0/FE0/LAN1
GE1/FE1/LAN2
BRI/ISDN1
---

H323
Dynamic Host Configuration Protocol
SNMP
Route Information Protocol
SIP
Extensible Authentication Protocol Over LAN
WLAN Preauthentication
Interface
ethernet0/0
ethernet0/1
bri0/0
x25-node
MAC/Data-Link
Ethernet/IEEE 802.3
Ethernet/IEEE 802.3
BRI Net
internal
Status
Up
Testing
Testing
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, the user license and its serial number.
The second block (lines 4-5) displays information on the demo license indicating the time remaining
until the said license expires, and the 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 version of the Boot ROM (Read Only Memory) memory that
is currently installed in the router from the BIOS and the current setting of the watchdog timer.
The fourth block (lines 13-15) lists the version of the software that is currently running on the router.
The fifth block (lines 16-18) displays the Hostname, active user, the date and time, and the length of
time since the last device boot up.
The sixth block lists the configured protocols and interfaces are also displayed. The meaning of each
of the following fields is:
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 of the
fields is as follows:
Connector
Connector associated to the interface.
Interface
Interface name.
MAC/Data Link Type of MAC/Data link configured for this interface.
Status
Current status of the network interface.
Testing
The interface is undergoing an auto-test. This occurs
the first time the router is started and this detects a
problem in the interface. Once the interface is on the
network, it periodically sends out test packets to
ensure that it is still functioning properly. If the test

III - 105
Doc.DM704-I
Rev.10.97
fails, the router removes the interface from the

network and runs the self-test to ensure its 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 autotest. The router continues to carry out the test towards
the network at increasing intervals beginning at five
seconds, until the router does not test the interface any
more (approximately two minutes).
Disabled
The shutdown configuration command has disabled
the interface.
Not present
Either there is no interface present in the router, or the
console is incorrectly configured.
Unsupported
The current release/license does not support the
interface hardware.
Available
This is the state of the secondary interface in a WAN
configuration when the main one is active.
Error Disabled
An error in the interface has been detected and has
made it disable.
The eighth block SNMP OperStatus displays a list for the Interface operating status from the
point of view of the SNMP protocol, as defined in RFC 2233. The meaning of each of the fields is as
follows:
Interface
Interface name.
OperStatus
The possible SNMP operating states are as follows:
Up
The interface is ready to transmit and receive network
traffic.
Down
The interface is not operative.
Testing
The interface is executing some test; consequently the
real traffic packets cannot be transmitted.
Unknown
The interface operating status cannot be determined
for unknown reasons.
Dormant
The interface is operating, but waiting for an external
event in order to begin sending or receiving packets.
It will presumably pass to Up once the expected
event occurs. An example of this is when dial
interfaces do not have any traffic to send (therefore
have not initiated a call) or when only incoming calls
are permitted and the remote end has not initiated the
connection.
Not present
This state is a refinement of Down and indicates the
interface is down specifically due to the lack of a
component (often hardware).
Lower layer down
This is another refinement of Down which indicates
the interface has been assembled on top of one or
more interfaces and one of these latter is down.

III - 106
Doc.DM704-I
Rev.10.97
The ninth block displays information on the versions for the encryption cards, the cellular and the
wireless LAN drivers.
2.5. DEVICE
Displays statistical information on the network interfaces such as Ethernet, Token Ring etc. This
command can be used to obtain a summary report on all the interfaces or to obtain detailed
information on a specific interface.
Syntax:
+device [<interface>]
<interface > name of the interface you wish to display information for.
If you do not enter the interface name, the generic information on all interfaces will be displayed.
Example 1:
+device
Interface
ethernet0/0
serial0/0
serial0/1
serial0/2
bri0/0
x25-node
+
CSR
fa200e00
fa200a00
fa200a20
fa200a60
fa200a40
0
Vect
27
5E
5D
5B
5C
0
Auto-test
valids
1
0
0
0
1
1
Auto-test
failures
0
156
156
7
0
0
Maintenance
failures
0
0
0
0
0
0
Vect
27
Auto-test
valids
1
Auto-test
failures
0
Maintenance
failures
0
Example 2:
+device ethernet0/0
Interface
ethernet0/0
CSR
fa200e00
Physical address:
PROM address:
Speed:
00A0267001E8
00A0267001E8
10 Mbps
Input statistics:
failed, frame too long
failed, alignment error
internal MAC rcv error
Output statistics:
deferred transmission
multiple collisions
failed, excess collisions
failed, carrier sense err
late collision
Ethernet MAC code release 1
+
0
0
1
failed, FCS error

failed, FIFO overrun
packets missed
0
1
1
0
0
0
0
0
single collision
total collisions
failed, FIFO underrun
SQE test error
internal MAC trans errors
0
0
0
0
0

Interface
Interface name.
CSR
Command and Status Register address.
Vect
Interruption vector.
Auto Test Valids
Number of times the auto-test succeeded (state of interface changes
from down to up).
Auto-Test Failures
Number of times the auto-test failed (state of interface changes from
up to down).
Maintenance Failures
Number of maintenance failures.

III - 107
Doc.DM704-I
Rev.10.97
The fields that subsequently appear depend on the type of interface selected and have self-explanatory
names regarding the information they display.
Note: The screen being displayed can vary depending on the router and device.
2.6. ERROR
Displays error statistics for the segmented network for the various interfaces available in the device.
This command provides error counters.
Syntax:
+error
Example:
+error
Interface
ethernet0/0
serial0/0
serial0/1
serial0/2
bri0/0
x25-node
+
Input
Discards
0
0
0
0
0
0
Input
Errors
0
0
0
0
0
0
Input
Unk Proto
1016
0
0
0
0
0
Input
Flow Drop
0
0
0
0
0
0
Output
Discards
0
0
0
0
0
0
Output
Errors
0
0
0
0
0
0

Interface
Interface name.
Input Discards
Number of packets discarded by flow control at reception.
Input Errors
Number of packets found to be defective at the data link.
Input Unk Proto
Number of packets received for an unknown protocol.
Input Flow Drop
Number of received packets that have been subsequently discarded by the
flow control in transmission.
Output Discards
Number of packets discarded by flow control in transmission.
Output Errors
Number of output errors, such as attempts to send over a network that is
down or over a network that went down during transmission.
The sum between all the Input Flow Drop and Output Discards interfaces is not the same. This
is due to the fact that the Output Discards may contain locally generated packets.
2.7. EVENT
Through this command you can enter the Event Logging System (ELS+) prompt. Here you can
temporally create filters for the messages 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 Chapter 4 Events Logging System. To return to the + prompt, enter the
command exit.
Syntax:
+event
Example:
+event
-- ELS Monitor -ELS+

III - 108
Doc.DM704-I
Rev.10.97
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 the features available for your software version.
With this command you enter in the corresponding feature monitoring. For further information please
consult the corresponding manual.
You need to enable the feature at the configuration prompt before monitoring it.
Syntax:
+feature <option>
access-lists
afs
bandwidth-reservation
dns
dns-updater
err-disable
gps-applications
http
ip-discovery
istud
ldap
mac-filtering
netflow
nsla
nsm
ntp
policy-map
power-switch
prefix-lists
radius
rmon
scada-forwarder
spi
stun
syslog
tftp
ttcp
vli
wrr-backup-wan
Generic IP lists monitoring

Advanced firewall system feature
Bandwidth-Reservation System feature monitoring
DNS monitoring environment
DNS UPDATER monitoring enviroment
Error disable monitoring
GPS Applications monitoring
HTTP server monitoring
Ip-discovery monitoring
IPSEC Tunnel Server Discovery Protocol monitoring
LDAP (Lightweight Directory Access Protocol)
monitoring
MAC-Filtering feature monitoring
Netflow client monitoring
NSLA (Network Service Level Advisor) monitoring
NSM (Network Service Monitor) monitoring
NTP (Network Time Protocol) monitoring
Policy map monitoring
TeleControl Module control environment
Prefix lists monitoring
RADIUS feature monitoring
RMON (Remote Network Monitoring)
Scada protocol monitoring
SPI agent monitoring
Stun protocol monitoring
Syslog client monitoring
Access the devices TFTP client.
Ttcp (test tcp)
Virtual Linux Interface monitoring
WAN Reroute feature monitoring
<option> specifies the type of information you wish to display.
a) FEATURE ACCESS-LISTS
Through this command you can enter the 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 Dm 752-I Access Control.
b) FEATURE AFS
Use this command to enter the AFS monitoring.
Syntax:
+feature afs

III - 109
Doc.DM704-I
Rev.10.97
Example:
+feature afs
-- AFS Monitor -AFS+
For further information on afs monitoring, please see manual Dm786-I AFS.
c) FEATURE BANDWIDTH-RESERVATION
With this command you enter in the Bandwidth-Reservation System feature monitoring. For further
information please consult manual Dm 715-I Bandwidth Reservation System.
System:
+feature bandwidth-reservation
Example:
+feature bandwidth-reservation
-- Bandwidth Reservation console -BRS+
d) FEATURE DNS
Accesses the DNS monitoring environment. For further information please see the corresponding
manual Dm 723-I DNS Client.
Syntax:
+feature dns
Example:
+feature dns
-- DNS resolver user console -DNS+
e) FEATURE DNS-UPDATER
Use this command to enter the dns-updater monitoring.
Syntax:
+feature dns-updater
Example:
+feature dns-updater
-- DNS Updater console -DNS Updater
For further information on dns-updater monitoring, please see manual Dm785-I DNS Updater.
f) FEATURE ERR-DISABLE
Use this command to enter the err-disable monitoring.
Syntax:
+feature err-disable
Example:
+feature err-disable
-- Error Disable user console -errdisable+

III - 110
Doc.DM704-I
Rev.10.97
g) FEATURE GPS-APPLICATIONS
Use this command to enter the 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 Dm812-I GPS.
h) FEATURE HTTP
Accesses the HTTP protocol monitoring. For further information, please see manual Dm 737-I HTTP
Protocol
Syntax:
+feature http
Example:
+feature http
-- HTTP server user console -HTTP+
i) FEATURE IP-DISCOVERY
Through this command you can enter the features ip-discovery monitoring.
functionality is dependent on the device i.e. it may not apply to your device.
Syntax:
This command or
+feature ip-discovery
Example:
+feature ip-discovery
-- TIDP Console -TIDP+
j) FEATURE ISTUD
Use this command to enter the istud monitoring.
Syntax:
+feature istud
Example:
+feature istud
-- ISTUD console -ISTUD+
For further information on istud monitoring, please see manual Dm784-I ISTUD Feature.
k) FEATURE LDAP
Use this command to enter the LDAP protocol (Lightweight Directory Access Protocol) monitoring.
Syntax:
+feature ldap

III - 111
Doc.DM704-I
Rev.10.97
Example:
+feature ldap
LDAP client monitor
LDAP+
l) FEATURE MAC-FILTERING
With this command you enter in the MAC-Filtering feature monitoring.
Syntax:
+feature mac-filtering
Example:
+feature mac-filtering
-- MAC Filtering user console -Filter+
m) FEATURE NETFLOW
Use this command to enter the netflow monitoring.
Syntax:
+feature netflow
Example:
+feature netflow
NETFLOW Monitor
NETFLOW Mon+
For further information on netflow monitoring, please see manual Dm789-I NETFLOW.
n) FEATURE NSLA
Use this command to enter the NSLA facility (Network Service Level Advisor) monitoring.
Syntax:
+feature nsla
Example:
+feature nsla
-- NSLA console -NSLA+
For further information please see manual Dm 754-I NSLA (Network Service Level Advisor).
o) FEATURE NSM
Use this command to enter the NSM facility (Network Service Monitor) monitoring.
Syntax:
+feature nsm
Example:
+feature nsm
-- NSM console -NSM+
For further information please see manual Dm 749-I NSM (Network Service Monitor).

III - 112
Doc.DM704-I
Rev.10.97
p) FEATURE NTP
Accesses the NTP (Network Time Protocol) monitoring environment. For further information please
see the corresponding manual Dm 728-I NTP Protocol.
Syntax:
+feature ntp
Example:
+feature ntp
-- NTP user console -NTP+
q) FEATURE POLICY-MAP
Use this command to enter the policy-map monitoring.
Syntax:
+feature policy-map
Example:
+feature policy-map
-- Policy Map user console --
Policy-Map+
For further information on policy-map monitoring, please see manual Dm795-I Policy map Class map.
r) FEATURE POWER-SWITCH
Use this command to access the 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.
Syntax:
+feature power-switch
Example:
+feature power-switch
POWER-SWITCH monitor
POWER-SWITCH+
For further information please see manual Dm 296-I Telecontrol Module (MTC).
s) FEATURE PREFIX-LISTS
Use this command to enter the prefix lists monitoring.
Syntax:
+feature prefix-lists
Example:
+feature prefix-lists
-- Prefix Lists user console -Prefix Lists+
For further information on prefix lists monitoring, please see manual Dm780-I Prefix Lists.
t) FEATURE RADIUS
Through this command you enter the RADIUS feature monitoring. For further information on the
RADIUS protocol monitoring please see the corresponding manual Dm 733-I RADIUS Protocol.

III - 113
Doc.DM704-I
Rev.10.97
Syntax:
+feature radius
Example:
+feature radius
-- RADIUS user console -RADIUS+
u) FEATURE RMON
Use this command to enter the rmon monitoring.
Syntax:
+feature rmon
Example:
+feature rmon
-- RMON (Remote Network Monitoring) console -RMON+
For further information on rmon monitoring, please see manual Dm796-I RMON Feature.
v) FEATURE SCADA-FORWARDER
Use this command to enter the SCADA forwarder monitoring.
Syntax:
+feature scada-forwarder
Example:
+feature scada-forwarder
SCADA Forwarder Console
SCADA FWD+
w) FEATURE SPI
Use this command to enter the spi monitoring.
Syntax:
+feature spi
Example:
+feature spi
-- SPI Agent user console -SPI+
For further information on spi monitoring, please see manual Dm793-I SPI Agent.
x) FEATURE STUN
Accesses the STUN client monitoring environment. For further information on this, please see manual
Dm 769-I STUN Protocol.
Syntax:
+feature stun client
Example:
+feature stun client
STUN Client Monitor
STUN Client Mon+

III - 114
Doc.DM704-I
Rev.10.97
y) FEATURE SYSLOG
Use this command to enter the Syslog client monitoring.
Syntax:
+feature syslog
Example:
+feature syslog
-- SYSLOG client console -SYSLOG+
For further information please see manual Dm 753-I Client syslog.
z) FEATURE TFTP
Use this command to enter the tftp monitoring.
Syntax:
+feature tftp
Example:
+feature tftp
TFTP manager
TFTP+
For further information on tftp monitoring, please see manual Dm765-I TFTP Protocol.
aa) FEATURE TTCP

Use this command to enter a menu to carry out test son tcp traffic loading.
bb) FEATURE VLI

Use this command to enter the vli monitoring.
Syntax:
+feature vli
Example:
+feature vli
-- VLI monitor -vli+
For further information on vli monitoring, please see manual Dm803-I Virtual Linux Interface VLI.
cc) FEATURE WRR-BACKUP-WAN

With this command you enter in the Backup WAN Reroute feature monitoring.
information please consult manual Dm 727-I Backup WAN Reroute.
Syntax:
For further
+feature wrr-backup-wan
Example:
+feature wrr-backup-wan
-- Back-up WAN Reroute user console -WRR+

III - 115
Doc.DM704-I
Rev.10.97
2.9. LAST-CONFIG-CHANGES
This command permits you to monitor the last configuration recordings. The first row is the latest
configuration the device has stored and will be the active one if no other configuration change has
been produced after re-starting the device. If a change has been made, the active configuration will be
in the second information register. The first information register is modified each time the
configuration is saved without restarting the device.
Syntax:
+last
Example:
+last
Last configuration changes
------------------------------------------------------------------------------File
Acc-Type Address
User
Date/Time
------------------------------------------------------------------------------ATLAS.CFG
TFTP.CFG
TFTP.CFG
TFTP.CFG
IGMP.CFG
TFTP.CFG
TFTP.CFG
IGMP.CFG
IGMP.CFG
+
Console
Console
Telnet
Telnet
Console
Console
Console
Console
Console
0.0.0.0
0.0.0.0
172.24.51.128
172.24.51.128
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
CONSOLE
Teldat
TELNET
TELNET
Teldat
Teldat
CONSOLE
Teldat
CONSOLE
03/03/05
02/28/05
02/24/05
02/24/05
02/24/05
02/24/05
02/24/05
02/23/05
02/22/05
10:40:29
13:37:02
15:29:40
15:24:21
13:45:33
11:56:51
11:54:51
19:34:36
17:20:45

File
Name of the recorded file which is active.
Acc-Type
Type of access (telnet, console) carried out to modify the configuration.
Address
IP address used for the access. This field value will be 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 will appear in this field.
Date/Time
Time and date these changes were executed.
2.10. MALLOC-MONITOR
This command permits you to monitor the internal system of the device memory management.
Through this commands options you can control the diagnosis systems for the administration of the
system memory. The use of this command requires in-depth knowledge of the Teldat routers software
and hardware architecture, therefore should only be used when expressly indicated by Teldat
personnel.
Syntax:
+malloc-monitor <option>
DISABLE
ENABLE
ASSIGNED-MEMORY-BLOCKS
LIST
SHOW-FLAGS
ALL-REQUESTS

III - 116
Doc.DM704-I
Rev.10.97
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 you wish to carry out.
2.11. MANAGEMENT
Enters the master router monitoring environment.
Syntax:
+management
Example:
+management
-- Routers management user console-MANAGEMENT+
2.12. MEMORY
This command displays information relative to the different types of memory available in the device.
The information displayed on executing the command is divided into different blocks.
In the first block, information relative to the memory POOL1 is displayed. POOL1 is an area of
memory which is in fixed size partitions reserved for messages and buffers from the node.
For 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 second block, information is displayed on the HEAP memory. Specifically you can see the
total number of bytes assigned to the said memory, the used and free fragments as well as the number
of free bytes.
In the third block the parameters relevant to the systems RAM memory are displayed:
Total mem: systems total memory in bytes.
Total free mem: unused memory in the device in bytes.
Available cache mem: unused memory in the device in bytes, susceptible to being used as
cache memory.
Available non-cache mem: unused memory in the device in bytes not susceptible to being used
as cache memory.
Used cache mem: memory: amount of memory used supporting cache.
Used non-cache mem: amount of memory used that does not support cache.
Caches: status of the memory cache devices for the equipment.
In the fourth block, the parameters relevant to:
Flash memory: systems flash memory measured in bytes.
Free global Buffers: number of public buffers available in the system. The minimum number
of available public buffers that have been reached is displayed between brackets.

III - 117
Doc.DM704-I
Rev.10.97
Spurious INT 47: spurious interruption counter in the system.

Syntax:
+memory
Example:
+memory
POOL1
Sz:1204000
HEAP
bytes total
chunks used
chunks free
bytes free
AllocPart:16
AvlPart:3366
3747840
15507
508
16344
Total mem:
67108864
Available cache mem:
34693120
Used cache mem:
3747840
Caches: ON
Write Back
Total free mem:

Available non-cache mem:
Used non-cache mem:
34694652
34694652
10156548
Flash Memory: 16777216

Free global Buffers:1661 (1659)
Spurious INT 47: 0
+
2.13. 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 the said prompt.
Syntax:
+network <interface>
<interface> name of the network interface whose monitoring environment you wish to
access.
Type device at the + prompt to see the networks for which the router is configured.
Example:
+device
Interface
CSR
ethernet0/0
fa200e00
serial0/0
fa200a00
serial0/1
fa200a20
serial0/2
fa200a60
bri0/0
fa200a40
x25-node
0
+network serial0/0
Vect
27
5E
5D
5B
5C
0
Auto-test
valids
1
0
0
0
1
1
Auto-test
failures
0
373
373
10
0
0
Maintenance
failures
0
0
0
0
0
0
-- Frame Relay Console -serial0/0 FR+
For further information, please see the manual associated to the specified network interface regarding
the monitoring environment you wish to access.
2.14. NODE commands

Accesses the node monitoring (X.25, XOT and 270).

III - 118
Doc.DM704-I
Rev.10.97
Syntax:
+node <name>
X25
XOT
270
<name> name of the node part for the monitoring menu you wish to access.
a) NODE X25
Accesses the node monitoring relative to X.25. The parameters relative to a port can be configured in
the network for this port (+network port command).
Syntax:
+node x25
Example:
+node x25
-- X25 Monitor -X25+
For further information on the X.25 node monitoring environment, please see manual Dm 707-I X.25.
b) NODE 270
Accesses the 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>
2.15. PROTOCOL
Through this command you can enter into the commands environment for the protocols software
installed in the router. The protocol command followed by the desired protocol number or short name
Accesses a protocols command environment. After you enter this command, the specified protocol
prompt appears. From this prompt, you can enter the specific commands specific for the said protocol.
To enter a protocol command environment you need to:
1. Enter protocol ? to see a list of the protocols configured in your router.
2. Enter the name of the required protocol. The specified protocol prompt will immediately appear.
From this prompt you can enter the specific commands for the said protocol.
3. Enter exit to return to the + prompt.
Syntax:
+protocol <identifier>
<identifier> protocol identifier name whose monitoring menu you wish to access.

III - 119
Doc.DM704-I
Rev.10.97
Example:
+protocol ?
arp
Access
asrt
Access
bfd
Access
bgp
Access
dep
Access
dhcp
Access
dls
Access
dot1x
Access
gw104
Access
nhrp
Access
h323
Access
igmp
Access
ip
Access
ipv6
Access
l2tp
Access
mgcp
Access
noe
Access
ospf
Access
pim
Access
rip
Access
sccp
Access
sip
Access
snmp
Access
+protocol ip
ARP protocol
ASRT protocol
BFD protocol
BGP protocol
DEP protocol
DHCP protocol
DLS protocol
802.1X protocol
GW-104 protocol
NHRP protocol
H323 protocol
IGMP protocol
IP protocol
IPv6 protocol
L2TP protocol
MGCP protocol
NOE protocol
OSPF protocol
PIM protocol
RIP protocol
SCCP protocol
SIP protocol
SNMP protocol
-- IP protocol monitor -IP+
2.16. QUEUE
Displays statistics about 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 low-level buffer value
The number of buffers currently active in the interface
Syntax:
+queue <interface>
access.
In order to view the networks that the router has been configured for, enter the command device at the
+ prompt. If you do not specify the interface, information on all interfaces available in the device will
be displayed.
Example:
+queue
Interface
ethernet0/0
serial0/0
serial0/1
serial0/2
bri0/0
x25-node
+
Input Queue
Alloc
Low Curr
40
5
40
0
0
0
0
0
0
40
5
40
160
5
0
0
0
100
Output Queue
Fair
Current
40
0
0
0
0
0
8
0
4
0
40
0

III - 120
Doc.DM704-I
Rev.10.97
Interface
Input Queue
Alloc
Low
Curr
Interface name.
Number of buffers allocated to this device.

Water mark for flow control in this device.
Current number of buffers in this device. The value is 0 if the device is
disabled.
Output Queue
Fair
Fair level for the output queue in this device.
Current
Number of packets currently waiting to be transmitted in this device.
The router attempts to keep at least the Low value packets available for receiving over an interface. If
the router receives 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.
Due to the scheduling algorithms of the router, the Curr dynamic number (particularly the Input
Queue Curr) may not be fully representative of typical values during packet forwarding. The console
code runs only when the input queues have been emptied. Thus, Input Queue Curr will generally be
non-zero only when those packets are waiting in a slow transmission queue.
2.17. QUICK
In order to access the quick monitoring menu, you need to have previously accessed the general
monitoring menu and from there enter quick. Through this command you enter the quick monitoring
menu.
Syntax:
+quick
Example:
+quick
Quick Monitor Menu
Quick Monitor+
2.18. STATISTICS
Displays statistical information about the network software, such as the configuration of the networks
in the router.
Syntax:
+statistics <interface>
access.
In order to view the networks that 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 will be displayed.

III - 121
Doc.DM704-I
Rev.10.97
Example:
+statistics
Interface
ethernet0/0
serial0/0
serial0/1
serial0/2
bri0/0
x25-node
+
Unicast
Pqts Rcv
0
0
0
0
0
0
Multicast
Pqts Rcv
5384
0
0
0
0
0
Bytes
Received
3090255
0
0
0
0
0
Packets
Transmitted
0
0
0
0
0
0
Bytes
Transmitted
0
0
0
0
0
0

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 this interface at the MAC sub-level.
Packets Trans
Number transmitted unicast, multicast, or broadcast packets.
Bytes Trans
Number of bytes transmitted at the MAC sub-level.
2.19. SYSTEM
Permits monitoring of the systems memory and stacks, the use of the CPU, configure the speed of the
console port, display the firmwares needed so the device operates correctly, activate determined
debugging information, show the history of the users who have accessed the device, view the open
Telnet and SSH sessions and exchange commands or messages between the terminals corresponding
to these open sessions.
Syntax:
+system <option>
console-speed
cpu-graph
cpu-history-48h
cpu-text
dba-debug
disable-process-monitor
enable-process-monitor
firmwares-required
login
login-historic
memory
pcmcia
power-off-status
process-list
ssh
stack-status
telnet
telnet-clients
terminal
usb
Configure the console-serial port speed

Display a system load measurement graph
Display the system load for the last 48 hours
Display the average load in the system
DBA subsystem debug level
Disable CPU load monitoring of processes
Enable CPU load monitoring of processes
Display the firmware required
Shows if the difference between upper and lower
case characters is activated
Display a list containing information on the users
who have accessed the device console
Display statistics on the system memory
Access the PCMCIA interface status monitoring
Display power off timers and ignition status
Display the system processes status
Display information on the users connected by SSH
Display the system stack status
Display information on the users connected to the
device
Display information on open Telnet session to
remote devices
Interchange commands or messages between terminals
Access the USB interface status monitoring
<option> specifies the action to take.
a) SYSTEM CONSOLE-SPEED
Permits you to configure the console serial port speed.

III - 122
Doc.DM704-I
Rev.10.97
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
+
By default the speed of the console serial port is set to 9600 bps.
b) SYSTEM CPU-GRAPH
This 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 this 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:
+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 writing at the top of the said column). This load has varied over time (18% in the following
15 seconds, 23% in the next 5 seconds, etc) until it has established at a current load of 17% (right hand
column).
c) SYSTEM CPU-HISTORY-48H
This command displays a graph showing the CPU usage in the system over the last hours, up to a
maximum of 48 hours. From lift 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 range of time displayed in the graphs
horizontal axis. Consequently, a time range of 2 hours displays the maximum CPU usage percentages
for each interval of 2 minutes, and a time range of 48 hours displays the maximum percentages for
each interval of 48 minutes. The numerical percentage values are located in 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.

III - 123
Doc.DM704-I
Rev.10.97
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 that you wish to view.
min_hour
Right limit in hours for the horizontal axis range that you wish to view.
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
+
In this example, entry parameters havent been specified, displayed all the available history up to the
current moment. 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. This way, each graph percentage value represents the
maximum CPU usage in a 3 minute interval. This horizontal axis range automatically increases
depending on how long the device has been operating up to a maximum of 48 hours, after which 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 (%):
1
100_ 222222222322222222222222222222259222222222222222222223124222
95_|
90_|
85_|
80_|
75_|
70_|
65_|
60_|
55_|
50_|
45_|

III - 124
Doc.DM704-I
Rev.10.97
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, which determine that the
temporary viewing range is from 12 hours ago to 3 hours ago.
d) 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.):
CPU Medium-Term Usage (1 min.):
CPU Long-Term Usage (5 min.):
+
24.5%
19.2%
17.6%
e) SYSTEM DISABLE-PROCESS-MONITOR
This command disables the monitoring for the system processes preventing you from getting the CPU
usage statistics for processing. The processes monitoring is disabled on device startup.
Syntax:
+system disable-process-monitor
Example:
Process monitoring disabled
+
f) SYSTEM ENABLE-PROCESS-MONITOR
This command enables the monitoring for the system processes which allows you to get the CPU
usage statistics for processing. The 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.
+
When the processs monitoring is enabled, this can negatively affect device performance.

III - 125
Doc.DM704-I
Rev.10.97
g) SYSTEM FIRMWARES-REQUIRED
Displays the firmware required so the system operates correctly.
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
+
h) SYSTEM LOGIN
This firstly shows if the difference between upper and lower case characters is activated in the user
name authentication process when accessing the device, and subsequently dumps a list with
information on the 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 displaying it on screen. If no value is introduced here, the device
will ask the user for a value after showing the list.
Example:
+system login
Case-sensitive login: enabled
Date
-------------01/03 10:41:01
01/03 10:42:05
02/04 16:58:06
02/04 16:58:19
02/04 16:59:55
03/07 10:09:49
03/07 10:26:29
03/07 10:27:06
03/07 10:30:06
03/07 10:30:09
03/07 10:30:16
Login
Type
---------- -----root
REMOTE
teldat
REMOTE
LOCAL
teldat
REMOTE
teldat
REMOTE
omateo
REMOTE
rsanchez
LOCAL
teldat
REMOTE
root
REMOTE
LOCAL
root
REMOTE
Clean historic?(Yes/No) [No]? No

+
i) SYSTEM LOGIN-HISTORIC
Displays a list containing information on the users who have accessed the Teldat device console.
Syntax:
+system login-historic <clear after show>

III - 126
Doc.DM704-I
Rev.10.97
<clear after show> parameter (possible values yes / no) which indicates if you want to
delete the history after showing it on screen. If you do not enter a value, the device will
prompt you for one after displaying the list.
Example:
+system login-historic
Date
Login
-------------- ---------01/03 10:41:01 root
01/03 10:42:05 teldat
02/04 16:58:06
02/04 16:58:19 teldat
02/04 16:59:55 teldat
03/07 10:09:49 omateo
03/07 10:26:29 rsanchez
03/07 10:27:06 teldat
03/07 10:30:06 root
03/07 10:30:09
03/07 10:30:16 root
Type
-----REMOTE
REMOTE
LOCAL
REMOTE
REMOTE
REMOTE
LOCAL
REMOTE
REMOTE
LOCAL
REMOTE
Clean historic?(Yes/No) [No]? No

+

Date
Date (month/day) and time of access.
Login
Name of user who has connected to the device. This field is empty if there are no
users created in the device.
Type
Type of access executed by the user: through telnet (REMOTE) or console (LOCAL).
j) SYSTEM MEMORY
This command displays statistics on the system memory.
Syntax:
+system memory
Example:
+system memory
Caller Second C. Third C. Address Size
Age
------------------------------------------------xxxxxxx
xxxxxxxx xxxxxxxx
xxxxxx xxxx
xxxxx
Hsh
xxxxxx
Times couldnt monitor a request X

Times couldnt match a free X
Entries created X Entries available X Entries in use x
+
This command should only be executed by the Teldat technical team.
k) 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

III - 127
Doc.DM704-I
Rev.10.97
Example:
<option> specifies the action to execute: events enable/disable [DEBUG] or dump the
controller and card status information [DUMP].
<parameters> parameters required for the different possible actions.
+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 on PCMCIA interface monitoring, please see manual Dm 757-I PCMCIA
UMTS Interface.
l) SYSTEM POWER-OFF-STATUS
This command displays the current status of the ignition signal, the value programmed in the timer
and in cases where the ignition signal is not active, the time elapsed from the moment the ignition
was switched off.
Syntax:
+system power-off-status
Example 1:
Ignition signal state ACTIVE
Programmed time to power off: 60 seconds
+
Example 2:
Ignition signal state DEACTIVE
Programmed time to power off: 60 seconds
Time elapsed with ignition off: 10 seconds
+
m) SYSTEM PROCESS-LIST
This command displays the percentage of CPU usage and the statue of the stack for each process
active in the system. This command displays three CPU usage percentages corresponding to the latest
5 seconds, the last minute and the last 5 minutes respectively. In order to use this command, you need
to have previously enabled the processs monitoring. These processes can be three types:

III - 128
Doc.DM704-I
Rev.10.97
1. Interrupts. This is a high priority process which responds to petitions from the different
hardware components, such as the reception of a packet or a change in the physical layer of an
interface.
2. High level interrupt handler. These processes respond at a higher level (lower priority) the
interruptions captured through the Interrupts process.
3. 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).
Name
Name of process.

III - 129
Doc.DM704-I
Rev.10.97
Stack size
Status
cpu % (5s/1m/5m)
Task stack size in bytes.

Stack status. ok indicates that the stack is operating correctly. overflow
indicates the stack has overflowed due to lack of memory. unknown in cases
with unmanaged stacks.
CPU usage percentages for each process. From left to right, each column
displays the use in the last 5 seconds, the last minute and the last 5 minutes
respectively.
When the processes monitoring is enabled, this may negatively affect device performance.
n) 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 the said process is stored. Through this command you can
see the stack status for each of the active processes in the system. These processes can be one of three
types:
1. Interrupts. This is the highest priority process, which manages the 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 the interruptions captured through the
Interrupts process at a high level (lower priority).
3. Task. These processes handle the rest of the devices 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

III - 130
Doc.DM704-I
Rev.10.97
T
T
T
T
T
T
T
T
T
GESTCON
VISEVEN
TASKER
CONTROL
MTC
RESET
FTP
NU SCEP
TELNETSR
16000
8192
32000
1024
4096
1024
4096
4096
8192
(01230040)
(01234040)
(01237040)
(0123F040)
(01240040)
(0123F840)
(0145D040)
(01477040)
(01495040)
12408
7672
30680
792
3848
860
3848
3856
7072
10464
7592
29364
712
3768
852
3768
3776
6952
ok
ok
ok
ok
ok
ok
ok
ok
ok

Type
Type of process (I for Interrupts, H for High level interrupt handler, and T for
Task).
Name
Name of the process.
Stack size (addr)
Size of the task stack in bytes. The base address for the said stack is displayed
between brackets).
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 that the stack is operating correctly. overflow
indicates that the stack has overflowed due to lack of memory. unknown in
cases of non-managed stacks.
This command should only be executed by the Teldat technical team.
o) SYSTEM TELNET
Displays information on the 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
2
teldat 15
teldat 15
teldat 15
Local Console 03/03/05 10:40:57

172.24.51.128:59671 04/05/05 16:59:46
192.168.1.1:0
04/03/05 16:57:58
0
0
0
10
0
0 *
0

ID
Telnet session identifier number.
USER
Name of the user connected to the device. This field will be blank if
no users have been created in the device.
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. In cases where this parameter is
deactivated in the device configuration, this value is 0.

III - 131
Doc.DM704-I
Rev.10.97
IDLETIME
Maximum time permitted without activity. In cases where there is no

maximum time, this value is 0.
TIMEOUT
Maximum time permitted for the session. In cases where there is no
maximum time, this value is 0.
An asterisk will appear in the list next to the inactivity time field indicating the session you are
accessing from.
p) SYSTEM TELNET-CLIENTS
This command displays information about the Telnet sessions opened from the device towards the
remote devices.
Syntax:
+system telnet-clients
Example:
+system telnet-clients
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
-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 each of the columns displayed by the command is as follows:

SESSIN
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 of the device being used to communicate with the remote
device.
REMOTE-IP
IP address of the remote device the Telnet session was opened with.
SESSION-START
Date and time the session was opened.
URL
URL of the remote device the Telnet session was opened with, in
cases where this has been used.
q) SYSTEM TERMINAL
This command permits the Exchange of messages and commands between the terminals for the
different sessions established 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
SYSTEM TERMINAL KILL-TERMINAL

This command forces the termination of an established session. This will not take into account any
data entered after the said command, subsequently displaying the list of established sessions at that
moment followed by a request so the user indicates which of these he wishes to end. Only users with
ROOT permission are allowed to execute this command (access level 15).

III - 132
Doc.DM704-I
Rev.10.97
Example:
+system terminal kill-terminal ?
<cr>
+system terminal kill-terminal
Current active terminal sessions:
Local console session:
Time unit: minutes
ID USER
LEVEL
0
teldat 15
IP ADDRESS:PORT
Local Console
09/12/13 19:21:34
0 *
Current active Telnet sessions:

Time unit: minutes
ID USER LEVEL
IP ADDRESS:PORT
----------------------------------------------------------------------------------1
2
rafa
pepe
15
5
[192.168.212.26]:47354 09/12/13 19:22:49

[192.168.212.26]:47353 09/12/13 19:22:24
0
0
0
0
0
0
Current active SSH sessions:

Time unit: minutes
ID USER LEVEL
IP ADDRESS:PORT
----------------------------------------------------------------------------------3
rafa
15
192.168.212.26:47621 09/12/13 19:22:10
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 teldat in console ID 0:
Your session is going to finish
Connection closed by foreign host.
SYSTEM TERMINAL SEND-ESCAPE

This command sends the escape character (Ctrl+p by default) to the terminal corresponding to a
determined session. This will not take into account any data entered after the said command,
subsequently displaying the list of established sessions at that moment followed by a request so the
user indicates which of these he wishes to send the escape character, achieving by this that the user
who initiated this other session exits the console menu he is currently in. Only users with ROOT
permission are allowed to execute this command (access level 15).
Example:
+system terminal send-escape ?
<cr>
+system terminal send-escape

III - 133
Doc.DM704-I
Rev.10.97
Time unit: minutes

ID USER
LEVEL
IP ADDRESS:PORT
-----------------------------------------------------------------------------------0
teldat 15
Local Console
09/12/13 19:21:34
0 *

Time unit: minutes
ID USER
LEVEL
IP ADDRESS:PORT
-----------------------------------------------------------------------------------1
2
rafa
pepe
15
5
[192.168.212.26]:47357 09/12/13 19:41:30

[192.168.212.26]:47353 09/12/13 19:22:24
0
0
0
0
0
0

Time unit: minutes
ID USER LEVEL
IP ADDRESS:PORT
-----------------------------------------------------------------------------------3
rafa
15
192.168.212.26:47621 09/12/13 19:22:10
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:

I have sent you the escape sequence
SYSTEM TERMINAL WRITELN

This command sends a message to another terminal, i.e. to the user using the other established session
with the monitored device. This will not take into account any data entered after the said command,
subsequently displaying the list of established sessions at the moment followed by a request so the
user indicates which one of these he wishes to send the message to (-1 to send to all of them) and
another to write 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
Time unit: minutes
ID USER
LEVEL
IP ADDRESS:PORT
-----------------------------------------------------------------------------------0
teldat 15
Local Console
09/12/13 19:21:34
0 *

III - 134
Doc.DM704-I
Rev.10.97
Time unit: minutes

ID USER
LEVEL
IP ADDRESS:PORT
-----------------------------------------------------------------------------------1
2
rafa
pepe
15
5
[192.168.212.26]:47357 09/12/13 19:41:30

[192.168.212.26]:47353 09/12/13 19:22:24
0
0
0
0
0
0

Time unit: minutes
ID USER LEVEL
IP ADDRESS:PORT
-----------------------------------------------------------------------------------3
rafa
15
192.168.212.26:47621 09/12/13 19:22:10
Destination console ID (-1 for broadcast):[0]? -1

Message text (maximum 100 characters): []? I have to restart the router
I have to restart the router
Message sent
+
The following is displayed in one of the remote terminals:

I have to restart the router
r) SYSTEM USB
This command accesses the PCMCIA interface status monitoring environment at the physical layer
(controller and card).
Syntax:
+system usb <option> <parameters>
DEBUG
LSIT
Example:
<option> specifies the action to execute: events enable/disable [DEBUG] or dump the
controller and card status information [DUMP].
<parameters> parameters required for the different possible actions.
+system usb list supported

Option Fusion Globettroter
Manufacturer ID 0x0af0 Card ID 0x6000
Vodafone Connect 3G
Option Globettroter Quad
Option Globettroter 3G GT Fusion Lite
Novatel Merlin U740 R.0 HSDPA
Manufacturer ID 0x1410 Card ID 0x1400
Novatel Merlin U740 HSDPA
Novatel Merlin V620 CDMA EV-DO
Sierra Aircard 580

III - 135
Doc.DM704-I
Rev.10.97

Huawei Mobile Connect E612
Manufacturer ID 0x12d1 Card ID 0x1001
+
For further information on PCMCIA interface monitoring, please see manual Dm 757-I PCMCIA
UMTS Interface.
2.20. TFTP
This command provides access for the device TFTP client (Trivial File Transfer Protocol).
Syntax:
+tftp
Example:
+tftp
TFTP manager
TFTP+
For further information on the TFTP client interface, please see manual Dm 765-I TFTP Protocol.
2.21. TELEPHONY
The telephony command provides access to the monitoring environment of the device telephony
functions based on the Voice over IP.
Syntax:
+telephony
Example:
+telephony
Telephony Monitor
Telephony Mon+
For further information on this monitoring environment, please see manual Dm 722-I Voice over IP.
2.22. 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 you wish to monitor.

Example:
+uci help_statistics
Statistics meanings

III - 136
Doc.DM704-I
Rev.10.97
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:
DECRYPTED:
DEC.KEY.DEF:
TRANSPARENTS:
Frames encrypted correctly

Frames decrypted with DLCI key
Decrypted frames with the default key, not decrypted
with the DLCI key
Transparent frames
TOTAL PROCESSED FRAMES =ENCRYPTED + DECRYPTED +

0
0
0
0
+
DES.KEY.DEF + TRANSPARENTS0
2.23. WEB-PROBE
Accessing the web-probe monitoring menu.
Syntax:
+web-probe
Example:
+web-probe
-- Web Probe user monitoring -PROBE+
2.24. LOG
Permits you to obtain additional information on the device operation. This is only useful for Teldats
technical support service maintenance tasks. The 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
0000
3030
3720
3A33
726F
4F32
+
5
0000
2030
4D61
303A
6A6F
007D
0100
303A
7220
3139
206F
004A
3030
3133
2062
6E20
0D0A
3A30
2032
7920
204D
3031
3020
3030
2020
4245
2F30
392E
3220
6D62
5252
312F
312E
3137
6572
4F4A

III - 137
Doc.DM704-I
Rev.10.97
Chapter 4
Event Logging System ELS
1. Introduction
This chapter describes the Event Logging System (ELS). It also describes the VISEVEN procedure and
how to obtain messages from the Event Logging System. The VISEVEN procedure provides information
on the internal performance of the device and its interfaces.
This chapter contains the following sections:
Event Logging System
Event Logging System user interface
Event Logging System commands
TELDAT ROUTER Event Logging System

IV - 139
Doc.DM704-I
Rev.10.97
2. Event Logging System

Events occur continuously while the device is operating. These can be provoked by various causes:
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 messages as a result of its
activity. When something occurs, the Event Logging System (ELS) receives data from the system which
identifies the source and nature of the event. A message is then generated using the received data.
By appropriately configuring the Events Logging System, you can choose the messages to be displayed,
sent as traps or through syslog messages, so only those messages which are really useful to the user are
given.
The Event Logging System and the MONITOR procedure counters, allow you to isolate problems in the
device. A quick view of the messages informs the user if there is a problem in the device and where to
start searching for it.
In ELS config> prompt, there are commands that may be used to establish a default configuration. This
configuration does not take effect until the device is restarted.
At the ELS config$ prompt there are commands to establish a configuration that can be immediately
applied without having to reboot the device.
Sometimes, you may wish to temporarily obtain messages with a different configuration to that
established in the ELS Configuration procedure (ELS config> or ELS config$ prompt). This can be done
in the ELS monitoring procedure (ELS+ prompt) without needing to restart the device. With this
prompts commands, it is possible to temporarily change the selection of events to be displayed on the
screen or be sent as traps or through syslog messages. These changes take effect immediately and are not
stored in the system configuration.
There is another system similar to this events logging system, which stores logs in non-volatile memory.
These logs registrar information relative to accessing the system (through ftp or telnet), restarts for this,
modifications in the configuration etc. The chief difference between this and the events is that these logs
are saved in the non-volatile memory i.e. they remain stored even when the device restarts the application
or is switched off.
Below you can see a summary on the process to access the ELS Config> prompt from the Config>
prompt, the ELS config$ prompt from the Config$ prompt and the ELS+ prompt from the + prompt.
Event Logging System Configuration
To access the Event Logging System configuration procedure:
1. At the Console Manager procedure prompt *, enter STATUS in order to find out the process
identifier (pid) for the configuration environment.

IV - 140
Doc.DM704-I
Rev.10.97
*STATUS
System Processes:
PID NAME
1
2
3
4
5
6
Main console
Event viewer
Monitor console
Config console
Telnet client
2. Enter PROCESS and the process identifier (pid) to access the CONFIG process (number 4 in this
case).
*PROCESS 4
Config>
An alternative to the sequence previously indicated by steps 1 and 2, is to access the configuration
process through the CONFIG command from the Console Manager * process.
*CONFIG
Config>
3. Enter EVENT to access the Event Logging System.
Config>event
-- ELS Config -ELS config>
Now it is possible to execute Event Logging System commands.

To exit the Event Logging System configuration and return to prompt Config>, enter EXIT.
ELS config>exit
Config>
All the changes performed in this procedure will only take effect when the device is
restarted, provided that the configuration has been previously saved either in Flash
memory or in the Smart Card.
If you want the configuration changes to take a dynamic effect without having to reboot the device, you
need to access the Events Logging Systems dynamic configuration process.
1. From the Console Manager process * prompt, enter PROCESS and the process identifier (pid) to
enter the dynamic configuration process, which in this case is 5.

IV - 141
Doc.DM704-I
Rev.10.97
*PROCESS 5
Config$
An alternative to the above sequence is to access the dynamic configuration process through the
RUNNING-CONFIG command from the Console Manager process * prompt:
*RUNNING-CONFIG
Config$
2. Enter EVENT to access the Events Logging System.
Config$event
-- ELS Config -ELS config$
Now you can execute the Events Logging System commands.

To exit the Events Logging System configuration, enter EXIT to return the Config> prompt.
ELS config$exit
Config$
All the changes made in this process take immediate effect. If you want to maintain the
configuration in future reboots, you need to save it in the Flash memory or in the
Smart Card in the same way as done in the static configuration process (config>).
Event Logging System Monitoring
To access the Event Logging System monitoring process:
1. Enter STATUS to find the MONITOR (+ prompt) process identifier.
*STATUS
System Processes:
PID NAME
1
2
3
4
5
6
Main console
Event viewer
Monitor console
Config console
Telnet client
2. Enter PROCESS and the process identifier (pid) to access the MONITOR procedure, number 3 in this
case.

IV - 142
Doc.DM704-I
Rev.10.97
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 it is possible to execute Event Logging System monitoring commands.

To exit the Event Logging System monitoring and return to +, enter EXIT.
ELS+EXIT
+
Events display (Traces)

Events that have occurred while the system was 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 the VISEVEN process is that they are only displayed when the
user requires them and not when they occur. The advantage of viewing from the active process is that
they are displayed as soon as they occur and additionally you can execute command from the active
process. I.e. you can carry out additional tasks or consult other types of information.
Disadvantages of displaying events from the VISEVEN process is the fact that you cannot carry out any
other task and if the events buffer is small, these can be easily lost. The disadvantage of displaying the
events in the active process is that this interferes with the information displayed by the process currently
running and complicates task execution.
To enter the VISEVEN process form the Console Manager, you need to do the following:
1. If you do not know the VISEVEN process PPID, enter STATUS at the * prompt.

IV - 143
Doc.DM704-I
Rev.10.97
*STATUS
System Processes:
PID NAME
1
2
3
4
5
6
Main console
Event viewer
Monitor console
Config console
Telnet client
2. Enter PROCESS and the process identifier (PID) in order to access the VISEVEN process, in this case
number 2.
*PROCESS 2
This process does not present prompts or permit you to execute commands. However it shows the
messages that have been saved.
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 the VISEVEN process. The VIEW command permits you to display the events and the
HIDE command the opposite.
Interpreting the Event Logging System messages
On entering the following command, a message from the Event Logging System has the following
appearance:
ELS+LIST SUBSYSTEM GW
GW.019
(Subsystem Event Number)
C-INFO
(Type of Event)
Slf tst ifc %s
(Message Text)
Subsystem
Subsystem is an abbreviated and pre-defined name for a Teldat Router component or functionality such
as protocol or interface, etc. The name GW identifies the subsystem through which this event has
occurred. GW is an 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 the CONFIG or P4 configuration process or from the
MONITOR or P3 monitoring process).
Enter the subsystem as a parameter in an Event Logging System Command, if the command is required to
affect the whole subsystem. For example, the ENABLE SUBSYSTEM GW command enables all the
events in GW subsystem so that when events are produced they will be collected by the VISEVEN
procedure.

IV - 144
Doc.DM704-I
Rev.10.97
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 subsystem. It is possible to obtain a list of all the events in a subsystem through the
LIST SUBSYSTEM <subsystem name>command. This is available both in the configuration process
(CONFIG or P 4) and in the monitoring process (MONITOR or P 3).
The event number always appears together with the subsystem identifier it pertains 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 required to affect only one
specific event, enter the subsystem and event number as a command parameter.
Type of Event
Type of Event or Filter Level is a pre-defined identifier that classifies each message in accordance 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 configuration confirmation is displayed.
UI-ERROR
Abnormal internal errors.
CI-ERROR
Usual internal errors.
UE-ERROR
Abnormal external errors.
CE-ERROR
Usual 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. By default.
P-TRACE
Packet trace.
U-TRACE
Abnormal operationTrace message.
C-TRACE
Usual operationTrace 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.

IV - 145
Doc.DM704-I
Rev.10.97
Groups
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. It is necessary to create a group before the name of the group can be specified in the command
line.
To create a group, execute the configuration command ADD, specify the name required for the group, and
then specify the events to be included in the group. The events included in the group may 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, include 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>
ELS config>delete
all
<1..11 chars>
ELS config>delete
<cr>
ELS config>delete
ELS config>
?
Group name
MYGROUP ?
The whole group
Event
MYGROUP all ?
MYGROUP all

IV - 146
Doc.DM704-I
Rev.10.97
3. Event Logging System user interface

In order to work efficiently with the Event Logging System:
You need to know what you wish to analyze through the said system. The problem or events
you wish 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
configuration, as well as the groups created. Or execute the same command in the Monitoring
procedure to erase all the events enabled during execution.
Enable only those messages that are 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 carefully.
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 are not viewed on screen at the same rate they are produced in the
VISEVEN process, the circular message buffer may become full and consequently the initial messages
are lost. In cases of sending events as traps, if the storage buffer overflows the last traps that 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 on which
events is of interest to you.
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 the VISEVEN (P2) process or from the active process using the
VIEW command. When using this latter command, use the HIDE command to conceal the events.
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 that a determined event can be sent as a specified private
company trap to any station with SNMP management. The information sent with this type of trap is
the message that will be 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 more information on how to configure the
SNMP Protocol, please consult the manual Dm 712-I SNMP Agent.
Any individual event, group of events or subsystem can be enabled as an SNMP trap.
For example, in order to enable the SNMP.002 event so it can be sent as a specific company trap,
1. At the ELS config> prompt, ELS config$ or ELS+, enter
ENABLE SNMP-TRAP EVENT SNMP.002

IV - 147
Doc.DM704-I
Rev.10.97
Note: If you are in the ELS Config> you need to save the configuration and restart the
device in order 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: You need to save the configuration and restart the device in order 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 remote stations. Any event, be it individual or belonging to a group or subsystem, can be
enabled with this aim.
For example, in order to enable the ICMP.002 event so it can be sent as a syslog message,
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> you need to save the configuration and restart the
device in order for the change to take 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 on the available configuration
parameters related to this functionality, please consult manual Dm 753-I Client Syslog.
Note: You need to save the configuration and restart the device in order for the change
to take effect.
If, under these conditions 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 that the problem
is or could be related to the IP protocol, enable all the events of 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
which contain the information that you require.
The Event Logging System allows you to specify which messages which are to be shown temporarily
or permanently.

IV - 148
Doc.DM704-I
Rev.10.97
The Event Logging Systems configuration commands allow you to design a permanent message filter
which takes effect each time the system is switched on or reset.
The monitoring commands allow you to start up the temporary filters which ignore the permanent
filter. When the system 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
12/29/06
12/29/06
12/29/06
12/29/06
12/29/06
2
13:07:41
13:07:41
13:07:41
13:07:42
13:07:42
click on <Ctrl
*
calls the events viewing system

GW.001 System restarted -- ATLAS50 router cold start
GW.002 Portable CGW ATLAS50 Rel 10.7.0 strtd
GW.005 Bffrs: 1762 avail 1762 idle
fair 195 low 352
USB registered new driver hub
USB registered new driver serial
+ 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
Example 3. GW protocol operation messages

ELS+ENABLE ALL SUBSYSTEM GW ALL
ELS+
*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
click on <Ctrl + p>
Conditional Events through the Access List

This deals with a functionality (similar to the previous one) that allows you to display, on console, all
traces for all the subsystems associated to reception and processing of packet that complies with a
series of conditions corresponding to an IP access list, dropping those that dont match this list. It is
therefore possible to closely follow the path taken by the packet from when it enters the system until it
exits, know which subsystems its passed through and to be able to locate possible errors.
To activate this, carry out the following:
Configure the access to the generic access lists configuration environment. For further
information on configuring generic access lists, please see manual Dm752-I Access
Control.
Add the lists where you want to enable incoming packet marking so all the events
associated to packet processing are displayed on the console. The corresponding
command is ENABLE TRACE CONDITION ACCESS-LIST <1.1999>.

IV - 149
Doc.DM704-I
Rev.10.97
Enables all the events to be viewed as consol traces. To do this, you need to use the
ENABLE TRACE ALL command. This is available both in the configuration process
(CONFIG or P 4 / RUNNING-CONFIG o P 5) as well as in the monitoring process
(MONITOR or P 3). This command should only be used with the corresponding filtering
so the events associated to a packet are displayed. If you dont add this restriction, all the
events available in the device are displayed with the consequential repercussions in
performance.
Example:
This is connected to the device through Telnet, but you do not want to view the events associated to
telnet. To do this, you need to configure an access list that excludes port 23 tcp.
feature access-lists
; -- Access Lists user configuration -access-list 100
entry 1 default
entry 1 deny
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 functionality that allows you to display, on console, all traces for all the subsystems
associated to reception and processing of packet coming through a determined interface, without
displaying traces not associated to this packet. It is therefore possible to closely follow the path taken
by the packet from when it enters one interface until exits through another, know which subsystems
its passed through and to be able to locate possible errors.
To activate this, carry out the following:
Add the interfaces where you want to enable incoming packet parking so all the events
associated to the packet processing are displayed on the console. The corresponding
command is ENABLE TRACE CONDITION INTERFACE <interface name>.
Although you can add any interface that is in the device to the list, you need to keep in
mind that it only makes sense to select incoming interfaces with an associated physical
layer (i.e. those known as base interfaces). In the same way you can select as a condition
that the packet is one from the free buffers global list, normally locally sourced packets, or
it is a packet from a protocol, through the ENABLE TRACE CONDITION GLOBALBUFFERS and ENABLE TRACE CONDITION PROTOCOL <protocol name>
commands respectively.

IV - 150
Doc.DM704-I
Rev.10.97
Enables all the events to be viewed as consol traces. To do this, you need to use the
ENABLE TRACE ALL command. This is available both in the configuration process
(CONFIG or P 4 / RUNNING-CONFIG o P 5) as well as in the monitoring process
(MONITOR or P 3). This command should only be used with the corresponding filtering
so the events associated to a packet are displayed. If you dont add this restriction, all the
events available in the device are displayed with the consequential repercussions in
performance.
Below you can see an example of what appears on the screen when this functionality is enabled in an
ethernet0/0 interface and a packet encapsulated in IPSec has been received:
01/25/07
01/25/07
01/25/07
01/25/07
444
01/25/07
f5b73944
01/25/07
01/25/07
01/25/07
09:45:02
09:45:02
09:45:02
09:45:02
POLR.004 dis int ethernet0/0

SNAT.004 NAT_OUT: (172.25.6.0, 172.24.100.129)-> no nat
IPSEC.001 esp encode, spi f5b73944
IPSEC.031 prot 17 (172.25.6.0[5060])->(172.24.100.129[5060]) len
09:45:02
IPSEC.003 Pack ESP suc encap (80.36.189.123->83.55.22.247) spi
09:45:02
09:45:02
09:45:02
IP.061 add lcl pkt to ip op q

IP.007 80.36.189.123 -> 83.55.22.247
SNAT.003 NAT_IN: (80.36.189.123, 83.55.22.247)-> no nat
IMPORTANT: In cases where you enable various conditional events at the same time,
you must bear in mind that any of the conditions can produce a trace.

IV - 151
Doc.DM704-I
Rev.10.97
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>or ELS config$ prompt and others in the Monitoring procedure at the ELS+ prompt.
4.1. Configuration Process Commands

These commands are executed in the Configuration procedure at the ELS config> prompt. The
following steps must be performed so that the changes made in the Event System take effect are:
1. Once the changes have been made, save the configuration (Flash or Smart Card) with the SAVE
command at the Config> prompt.
2. Restart the device again.
You can also configure the Events Logging System from the dynamic configuration process, at the
ELS config$ prompt, and therefore avoid the need to reboot. However, if you want to maintain the
configuration for future reboots, you need to save it through the SAVE command from the Config$
prompt.
Command
Function
? (HELP)
ADD
APPLY-FILTER
Lists all the commands for the Event Logging System configuration.
Adds an event to a specific group or creates a new group.
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
Permits you to disable messages so that they are not displayed on
screen and to disable the events filtering.
ENABLE
Permits you to enable messages so that they are displayed on screen
and to enable the 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 the events that
are currently relevant 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 that are registered in the NVRAM
when a RESET occurs in the device.
NVRAM-LOG-PRIORITY
Establishes the minimum priority that the logs must have to be saved
in the non-volatile memory.
OPTIONS
Modifies the behavior of the events logging system.

IV - 152
Doc.DM704-I
Rev.10.97
PPP
PRINT
STOP-TRACES
TRACE-LEVEL
VRF
EXIT
Accesses the specific PPP events menu.

Configures additional information to display in each event.
Stops saving traces.
Configures the trace level to display.
Accesses the events filtering through VRF menu.
Permits you to exit the Event Logging System configuration.
a) ? (HELP)
Lists the available commands in the current prompt. It is also possible to enter ? after a specific
command in order to list its options.
Syntax:
ELS config>?
Example 1:
ELS config>?
add
apply-filter
clear
console
delete
disable
enable
environment-monitor
ev-buffer
filter
list
no
number-events-log
nvram-log-priority
options
ppp
print
trace-level
stop-traces
vrf
exit
ELS config>
Adds an event to a specific group or creates a new

group
Applies dynamically the events filtering configuration
Erases all the event and group configuration from the
ELS
Enters the specific Console (CNSL) events menu
Deletes an event from a specific group or the whole
group
Disables events
Enables events
Enables environment monitor
Sets the events buffer size
Adds a filter
List configuration
Number of events to be logged in case of fatal error
Sets the priority of logs saved
Modify els subsystem behavior
Enters the specific PPP events menu
Configure els show options
Configures subsystem trace level
Stops saving traces
Enters the specific VRF filter events menu
Example 2:
ELS config>list ?
all
configuration
ev-buffer
event
filter
groups
nvram-log-priority
subsystem
ELS config>
Lists the configuration and all the subsystems

Lists the status of the subsystems, groups and events
Lists the events buffer parameters
Lists the filter level and the specified event message
Lists status of the filtering and the configured
filters
Lists the groups defined by the user and their content
Lists the minimum priority of logs saved
Lists all the events of a specified subsystem
b) ADD group
Adds an individual event to a previously created group or creates a new group. The names of groups
must be composed with alphabetical characters. Numbers or other types of ASCII characters are not
permitted. The name can have a maximum extension of 7 characters. The maximum number of
groups that can be created is 10 and the maximum number of events in a group is 20.

IV - 153
Doc.DM704-I
Rev.10.97
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>
c) APPLY-FILTER
Allows the configuration of events filtering to be dynamically applied over the currently generated
events.
Syntax:
ELS config>apply-filter
d) CLEAR configuration
Clears all the configuration information from the Events 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 Smartcard.
Syntax:
ELS config>clear
Example:
ELS config>clear ?
<cr>
ELS config>clear
ELS config>
e) CONSOLE
Accesses the specific console events menu.
Example:
ELS config>console
-- Console Events Configuration
Console Events config>
--
The console events menu permits you to configure various parameters related to this type of event.
Syntax:
Console Events
log
no
wait-time
config> ?
Includes additional information into console events messages
Negates a command or set its defaults
Sets time to wait for console events processing before effective
execution of a command
exit
LOG <info>
Activates the inclusion of additional information within the text corresponding to the console events.
Syntax:

IV - 154
Doc.DM704-I
Rev.10.97
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
By default, the prompt in the console events is not included.

LOG SOURCE-IP
Activates the inclusion of the device IP address and port, through which the user accesses the router
via telnet, in the console event user (usr) information field. In cases of users accessing via the local
console, the text Local Console will be displayed together with the user name.
Syntax:
Console Events config>log source-ip
Example:
Console Events config>log source-ip
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.
WAIT-TIME <time>
Establishes the period of time the device waits before actually executing critical a command with the
aim that 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 applied 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.)
- When the view command is executed, which permits you to see all the Events 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
By default, the wait time value is 1 tenth of a second.

IV - 155
Doc.DM704-I
Rev.10.97
NO
Permits you to establish the default values for the configuration parameters of 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
NO WAIT-TIME
Sets the default time (1 tenth of a second) the device waits before actually executing a command with
the objective of giving the system time to finalize the whole of the associated console events process
(including the sending of syslog messages or snmp traces).
Example:
Console Events config>no wait-time
f) DELETE group
Deletes an event from an already created group or deletes the whole group. A message will be
displayed if the event specified is the last one in the group. When ALL is specified instead of
subsystem.event_num, the whole group will be deleted.
Syntax:
ELS config>delete <nom_group> <subsystem.event_num>
Example 1:
ELS config>delete
<1..7 chars>
ELS config>delete
all
<1..11 chars>
ELS config>delete
ELS config>
?
Group name
MYGROUP ?
The whole group
Event
MYGROUP IP.001
Example 2:
ELS config>delete MYGROUP all
ELS config>

IV - 156
Doc.DM704-I
Rev.10.97
g) DISABLE
Selects and disables events so that their messages are not displayed on screen, nor sent as traps or
transmitted as syslog messages. It is also possible to disable groups and subsystems, as well as all the
traces if you have previously enabled them through the ENABLE TRACE ALL command.
Additionally this permits you to disable the events filtering.
In cases where youve selected an incoming interface, in order to view the traces associated to the
process and path the packets received in the said interface have followed, the DISABLE TRACE
CONDITION INTERFACE <interface name> command permits you to disable packet marking in
this 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
GROUPS <nom_group>
SYSLOG
GROUPS <nom_group>
TRACE
ALL
CONDITION INTERFACE <nom_interfaz>
CONDITION GLOBAL-BUFFERS
CONDITION PROTOCOL <nom_protocolo>
GROUPS <nom_group>
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
ELS config>
MYGROUP
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.
h) ENABLE
Selects and enables events so that their messages are displayed on screen, sent as traps or transmitted as
syslog messages. It is also possible to enable groups and subsystems. Additionally this permits you to
enable the events filtering. This also permits you to enable events filtering.
In section 3 in this chapter, we explained how to activate the functionality known as conditional
events: this is done by using the ENABLE TRACE CONDITION INTERFACE <interface name>
command, in order to enable packet marking in a determined interface. In addition, you can filter the

IV - 157
Doc.DM704-I
Rev.10.97
events for an IP access list through the ENABLE TRACE CONDITION ACCESS-LIST <list
command.
In this way you can view all the events associated to packet processing as console traces by then using
the ENABLE TRACE ALL command. We do not recommend you use this command except in cases
of using the said conditional events functionality, and that you restrict the number of traces to be
shown to those associated to a packet as contrariwise all traces will be shown and device performance
could be seriously affected.
As already indicated 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, using the ENABLE TRACE CONDITION GLOBAL-BUFFERS
and ENABLE TRACE CONDITION PROTOCOL <protocol name> commands respectively.
If you want to debug the condition events feature, you can enable a special trace through the
ENABLE CONDITION-DEBUG command, which will print every time you uncheck a packet.
Syntax:
ELS config>enable
ALL
GROUPS <nom_group>
CONDITION-DEBUG
FILTER
SNMP-TRAP
GROUPS <nom_group>
SNMP-TRAP-GROUP1
GROUPS <nom_grupo>
SNMP-TRAP-GROUP2
EVENT <subsistema.num_evento>
GROUPS <nom_grupo>
SNMP-TRAP-GROUP3
GROUPS <nom_grupo>
SNMP-TRAP-GROUP4
GROUPS <nom_grupo>
SYSLOG
GROUPS <nom_group>
TRACE
ALL
CONDITION INTERFACE <nom_interfaz>
GROUPS <nom_group>
NOTE: On enabling an event as a trap through the snmp-trap command, this is

enabled for all the trap groups.

IV - 158
Doc.DM704-I
Rev.10.97
Example:
ELS config>enable TRACE EVENT ICMP.001
ELS config>
This example enables the individual ICMP.001 event so it is displayed on screen.

Example:
ELS config>enable SYSLOG GROUP
ELS config>
MYGROUP
This example enables the MYGROUP group so it is sent as a syslog message.

Example:
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, since 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 provoke the situation where the device spends the
vast majority of its time contacting the remote terminal.
i) ENVIROMENT-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 that a temperature sensor in the device is indicating the temperature has risen
above 69C.
In order to view the 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).
This command is only available for those devices where you can monitor the fans
and/or are equipped with temperature sensors.
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 hasnt been
configured. If you configure the periodic-event option, the event is sent each time the configured
timeout times out and the problem still hasnt 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 in cases where the fault is persistent.
Likewise, this command activates the temperature sensor viewing when the CONFIGURATION
command for the monitoring procedure is executed.

IV - 159
Doc.DM704-I
Rev.10.97
Example:
*monitor
Console Operator
+configuration
[]
Watchdog timer Enabled
CASE 1 fan speed: 0 rpm (0 %)
CPU temperature: 51C
ADSL1 temperature: 50C
ADSL2 temperature: 53C
[]
j) EV-BUFFER <num. Lines> <line size>

Permits you to select the amount of memory reserved for the events buffer. The two parameters to be
configured are the number of lines (each event is stored in a line) and 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>
k) FILTER
Adds a filter so this can be applied.
Events filtering permits filtering within a given event so that the relevant information is projected and
the irrelevant information is eliminated. The filter has the added advantage that the discarded events
are not stored therefore reducing the risk of losing events due to overflow.
An index is associated to the filters that is used to determine the order of the application so that the
lower orders are applied before the higher orders. The order must be between 1 and 10. Its possible
to define a maximum of 10 simultaneous filters.
Another parameter associated to a filter is the application condition which if this is fulfilled the filter is
applied. The filters are checked one by one until there are no more or until one of these 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 this is: the text
is delimitated by quotation marks; the position where this is can be given explicitly or the 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 respectively.
Syntax:
ELS config>filter ?
<1..10>
Entry

IV - 160
Doc.DM704-I
Rev.10.97
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 that of 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 in a situation where the quantity of IP events is excessive. In order to resolve this
you can enable the events filter so that all the events occurred by 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 event (an internal event that occurs when a self test is carried out on an
interface) 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 event (an internal event that occurs when a self test is carried out on an
interface) 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 the traces when the first event is produced that includes the IP address 192.168.212.116.
ELS config>filter 1 text "192.168.212.116"
ELS config>filter 1 action stop-traces
ELS config>
l) LIST
Lists information on enabled events, created groups, subsystems and configuration.
Syntax:
ELS config>list ?
all
configuration
ev-buffer
event
filter
groups
Lists the configuration and all the subsystems

Lists the status of the subsystems, groups and events
Lists the events buffer parameters
Lists the filter level and the specified event message
Lists status of the filtering and the configured
filters
Lists the groups defined by the user and their content

IV - 161
Doc.DM704-I
Rev.10.97
nvram-log-priority
subsystem
ELS config>
Lists the minimum priority of logs saved

Lists all the events of a specified subsystem
LIST ALL
Lists all the created groups together with the events making these up, 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
Trace
Syslog
SNMP-Trap
Subsystem
Trace
Syslog
SNMP-Trap
:GW
:ALL
:ALL
(all groups):ALL
:IP
:STANDARD
:none
(all groups):none
Group
MYGROUP
Trace
Off
Syslog
On
SNMP-Trap
On ( group 1 group 3 )
Event
ICMP.001
Trace
On
Syslog
Off
SNMP-Trap
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) of the subsystems, groups and individual events which have
been configured. This will begin to operate when the device is restarted provided it has previously
been saved in the memory.
Suppose that you had previously enabled the GW subsystem in order to send SNMP traps, for the
transmission of syslog messages and for displaying from the VISEVEN process, the IP subsystem for
the on screen presentation of events which have a STANDARD filter level, and that there exists a
group called MYGROUP. This group is enabled so it can be notified through syslog messages and the
user enabled an ICMP.001 event to be sent as a specific company trap. You would achieve the results
that appear in the below example.

IV - 162
Doc.DM704-I
Rev.10.97
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
MYGROUP
Trace
Off
Syslog
On
SNMP-Trap
On ( group 1 group 3 )
Event
ICMP.001
ELS config>
Trace
Off
Syslog
Off
SNMP-Trap
On (all groups )
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.

IV - 163
Doc.DM704-I
Rev.10.97
Example:
ELS config>list groups
Group: MYGROUP
IP.002
IP.003
IP.004
ELS config>
LIST SUBSYSTEM
Lists all the events of a specified subsystem.
Example:
ELS config>list subsystem icmp
Event
Level
Message
ICMP.001
ICMP.002
ICMP.003
ICMP.004
ICMP.005
ICMP.006
ICMP.007
ICMP.008
ICMP.009
ICMP.010
ICMP.011
ICMP.012
ICMP.013
ICMP.014
ICMP.015
ICMP.016
ICMP.017
ICMP.018
ICMP.019
ICMP.020
ICMP.021
ICMP.022
ELS config>
UE-ERROR
C-INFO
U-INFO
CI-ERROR
U-TRACE
UE-ERROR
C-TRACE
C-TRACE
UI-ERROR
UE-ERROR
UI-ERROR
C-INFO
U-INFO
U-TRACE
UE-ERROR
U-TRACE
UE-ERROR
U-TRACE
UE-ERROR
U-TRACE
P-TRACE
P-TRACE
bd cks 0x%04x (exp 0x%04x) %I -> %I

ech %I -> %I
ech rp %I -> %I
unhnd typ %d %d %I -> %I
unhnd brd typ %d %d %I -> %I
bd typ %d %d %I -> %I
addr msk %I -> %I
addr msk rep %I -> %I
no pkt or mem
amb addr msk %I -> %I
err %d sndng pkt to ifc %s
rdr %I -> %I to %I
bd prm off %d %I -> %I
snd %d %d pkt %I -> %I
shrt ICMP hdr %d src %I
%I rdr dest %I to %I
Bad rdr from %I, rsn: %S
Router advertisement received from %I
Bad router adv from %I, rsn: %S
rcvd typ %d %d %I -> %I
redirect message filtered at interface %s
unreachable message filtered at interface %s
If the subsystem name is not entered, a list will appear with the name, event number and a description
of all the subsystems.
Example:
ELS config>list subsystem
Name
Events
Description
ADSL
AFS
AINST
ARP
ASDP
ARLY
ASYN
AT
ATM
BAN
BGP
BR
BRS
BSPF
CIF
CNSL
DEP
DHCP
8
6
23
10
11
41
5
20
15
29
27
48
9
10
34
4
30
14
ADSL
Advanced Filtering Subsystem
AutoInstall
Asynchronous Serial Device Proxy
Alarm Relay
AT Commands Interface
Asynchronous Transfer Mode
Boundary Access Node
Border Gateway Protocol
Bridge/Routing
Bandwidth Reservation
Bridge Spoofing
Encryption
Console
DEP Forwarder
DHCP

IV - 164
Doc.DM704-I
Rev.10.97
DHCPC
DLS
DNAT
DNS
EAP
ETH
FLT
FR
FRBK
FTP
G703
GW
H323
HDLC
HDSL
HSSI
HTTP
ICMP
IGMP
IKE
IP
IP6
IPHC
IPSEC
IPX
ISDN
L2TP
LAPD
LDAP
LLC
MCF
NAPT
NBS
NHRP
NOE
NSLA
NSM
NTP
P3OE
PHYS
PGMO
POLR
PPP
R2
RAD
RIP
RSTP
SCADA
SCDFW
SCEP
SDLC
SIP
SL
SNAT
SNMP
SPF
SRT
STP
STUN
SYNC
TCP
TIDP
TKR
TLNT
TLPHY
TNIP
TTTP
TVRP
23
459
12
30
6
54
7
53
8
4
25
64
19
11
57
5
25
22
26
51
87
200
46
33
105
40
56
11
16
33
9
30
50
58
17
8
82
25
23
4
5
16
100
9
46
30
9
28
20
17
95
16
36
5
26
61
89
42
3
2
55
18
46
8
23
39
18
26
DHCP Client
Data Link Switching
Dynamic NAT
Domain Name System
EAP
Ethernet
Filter Library
Frame Relay
Frame Relay BACKUP
File Transfer Protocol
G703 Digital Interface
Router kernel
H323
HDLC Interface
Symetric High Bitrate Digital Subscriber Line
High Speed Serial Interface
HyperText Transfer Protocol
Internet Control Message Protocol
Internet Group Management Protocol
Internet Key Exchange
Internet Protocol
IPv6
IP Header Compression
Ip Security
Internetwork Packet Exchange Protocol
Integrated Services Digital Net
Layer 2 Tunneling Protocol
ISDN Layer 2
Lightweight Directory Access Protocol
Logical Link Control
MAC Filtering
Network Address Port Translation
NetBIOS Support Subsystem
NOE
Network Service Level Advisor
Network Service Monitor
Network Time Protocol
PPP over Ethernet
ISDN BRI Layer 1
POS Gateway Monitor
Policy routing
Point to Point Protocol
R2
Remote Authentication Dial In User Service
IP Routing Information Protocol
Rapid Spanning Tree Protocol
SCADA Network
SCADA Forwarder
Simple Certificate Enrollment Protocol
IBM SDLC
SIP
Serial Line
Static NAT
Simple Network Management Protocol
Source Routing Transparent Bridge
Spanning Tree Protocol
STUN
Synchronous Serial Line
Transmission Control Protocol
T. IP Discovery Protocol
Token Ring
Telnet
TLPHY
IP Tunnel
T. Transaction Transfer Protocol
T. Virtual Router Protocol

IV - 165
Doc.DM704-I
Rev.10.97
UDAFO
UDP
VOIP
VRRP
WLAN
X252
X253
XN
41
4
14
8
4
23
26
21
UDAFO Forwarder
User Datagram Protocol
Voice over IP
Virtual Router Redundancy Protocol
Wireless LAN
X.25 Layer 2
X.25 Layer 3
Core Xerox Network System
ELS config>
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>
m) NO
Permits you to eliminate a given filter or to reestablish the default value for the parameters relative to
the size of the storage 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.
Additionally this permits you to eliminate and reestablish the configuration over the enabled or
disabled events at any point.
Syntax:
ELS config>no ?
environment-monitor
disable
enable
ev-buffer
filter
number-events-log
nvram-log-priority
print
stop-traces
trace-level
ELS config>
Enables environment monitor

Disables events
Enables events
Sets default events buffer size
Eliminates a given filter
Number of events to be logged in case of fatal error
Sets the default priority of logs saved
Configure els show options
Stops saving traces
configures subsystem trace level
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 events default parameters (disabled) shown on the screen, sent as
traps or transmitted as syslog messages. You can reestablish groups and subsystems.
Example:
ELS config>no disable TRACE GROUPS miGrupo
ELS config>

IV - 166
Doc.DM704-I
Rev.10.97
This example reestablishes the default values for the 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 events default parameters (enabled) shown on the screen, sent as
traps or transmitted as syslog messages. You can reestablish groups and subsystems.
Example:
ELS config>no enable SNMP-TRAP SUBSYSTEM ARP ALL
ELS config>
This example reestablishes the default values for the events with the ALL filter level for the ARP
subsystem so they are sent as SNMP traps and the corresponding entry is deleted from the
configuration.
Example:
ELS config>no enable SYSLOG EVENT IP.007
ELS config>
This example reestablishes the 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 the default values for the parameters relative to the storage buffer for the events waiting
to be displayed as traces on the console (VISEVEN process), parameters which permit you to select
the amount of reserved memory. These default 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 the additional information to be printed with each previously configured event.
Example:
ELS config>no print extra-info
ELS config>
NO STOP-TRACES
Eliminates the command 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.

IV - 167
Doc.DM704-I
Rev.10.97
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>
n) NUMBER-EVENTS-LOG
This command configures the number of events that are registered in the non-volatile memory when a
RESET occurs in the device. Default is 3, the range of configurable values being from 3 to 10000.
Knowing the latest events generated before an error occurs is very useful in order to detect the cause
of the error. We therefore suggest that a value greater than the default value for this parameter is
configured as you will then have more information in order 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>
o) NVRAM-LOG-PRIORITY
Configures the minimum priority that the logs must have in order to be saved. A priority is defined for
each log between 1 and 5 (1 being the highest priority and 5 the lowest). Given that 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 and not the lowest ones.
Logs related to device startups take priorities between 1 and 3. The rest of the logs (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>
p) OPTIONS
Permits you to modify the events logging system behavior.
Syntax:
ELS config>options ?
circular-buffer
no
time-as-incremental
time-as-ticks
time-stamp
usb-save
ELS config>
Enable circular buffer

Negate options
Show time as incremental in milliseconds
Show time as ticks
Include time in events
Save events on external USB

IV - 168
Doc.DM704-I
Rev.10.97
CIRCULAR-BUFFER
Establishes the default behavior for the events logging system, corresponding to events entering in the
circular buffer. The new events are always added to the circular buffer and if this is full, the oldest
events are dropped.
NO
Permits you to deactivate some options which by default are enabled. These are as follows:
CIRCULAR BUFFER
The events logging system stops entering events in the viewing circular buffer when it is full.
Consequently, when the events cannot be seen and the buffer is full, CPU time is not taken up so the
system increases its performance. The secondary effect is that the last events to arrive are lost, not the
oldest.
TIME-AS-INCREMENTAL
Deactivates the milliseconds mark with the time elapsed since the last event entry.
TIME-AS-TICKS
Deactivates the mark with the ticks counter.
TIME STAMP
When viewing this, the date and the time do not appear; consequently this does not consult the real
time clock thus diminishing the probability of losing events and improving performance.
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
USB-SAVE
Deactivates events dumping in a massive USB external storage device. Please see the options usbsave command.
TIME-AS-INCREMENTAL
The events are marked with a value measured in milliseconds that corresponds to the time that has
lapsed since the last event entered until the arrival of a new one.
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 of being marked with the date and time and
consequently more accurate.

IV - 169
Doc.DM704-I
Rev.10.97
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 the default behavior for the events logging system, corresponding to the time-stamp
viewing.
USB-SAVE
Permits the possibility to save the devices active events in a massive storage device connected to the
external USB. The events are saved in a file called event.log in the root directory of the first detected
partition. The partition must be formatted with the 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, this dumping does not occur
even if you subsequently connect a device.
The command can dynamically activate and deactivate (options 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
the events dumping in the external USB is activated, you can deactivate events dumping by executing
the options no save-usb command in the dynamic configuration. You must always dynamically
deactivate the events dumping to the USB before removing the external storage device. If you extract
this without deactivating the dumping, the latest evens are lost and you wont be able to dynamically
initiate dumping; you will 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.

IV - 170
Doc.DM704-I
Rev.10.97
q) PPP
Accesses the specific PPP events menu. For further information, please see manual Dm 710-I
Interface PPP.
Example:
ELS config>ppp
-- PPP Events Configuration
PPP Events config>
--
r) PRINT
This permits 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 isnt 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
s) 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 in cases where you want the events logging system to start when a determined event
is produced. The device boots with the events logging system stopped and a filter that detects the
desired event associating it with the start traces action is configured.
t) TRACE-LEVEL
Permits 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 the events subsystems, only for a few.
The trace levels available are as follows:
error: messages produced due to grave errors that can make the associated feature stop
functioning.
warning: messages produced due to unexpected errors while the associated feature is
functioning.
info: traces related to the normal functioning of the associated feature.
debug: debug traces. These permit you to monitor the HTTP server function in more
detail.
msg-dump: displays traces related to messages exchanged while the associated feature
is functioning.
excessive: displays all the available traces.

IV - 171
Doc.DM704-I
Rev.10.97
Each level includes all the previous levels. If, for example, the debug trace level is enabled,
the infor, warning and error trace levels are also included.
Syntax:
ELS config>trace-level <subsystem> <error-level>
Example:
ELS config>trace-level wlan debug
u) VRF
Accesses the events filtering through VRF menu.
Example:
ELS config>vrf
-- VRF Events Configuration -VRF Filter Events Config>?
You can configure the VRFs you want to view the events through from 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
v) EXIT
This allows you to exit the Events Logging System configuration and return to the Config> prompt.
Syntax:
ELS config>exit
Example:
ELS config>exit
Config>
4.2. Monitoring process commands

These commands are executed in the Monitoring process at the ELS+ prompt.
The changes made in this procedure are automatically executed and are lost when the device is
restarted. These commands allow you to enable events during execution time.
Command
Function
? (HELP)
CLEAR-ACTIVES
CONDITION-DEBUG
Lists all the commands for monitoring the Event Logging

System.
Permits you to disable all enabled events at a given time.
Displays useful information if you wish to debug the
condition events feature.

IV - 172
Doc.DM704-I
Rev.10.97
DISABLE
ENABLE
FILTER
HIDE
LIST
NVRLOG
RESTORE-CONFIGURATION
VIEW
EXIT
Allows you to disable event messages so they are not

displayed on the screen, nor sent as syslog messages or as
specific company traps.
Allows you to enable event messages to be displayed on the
screen, sent as syslog messages or as specific company traps.
Configures the rules permitting events filtering so that only
those events which are currently relevant are displayed.
Prevents the events from being displayed in the active process.
From this point on, the events can only be viewed from the
VISEVEN process.
This command is available from any process although it does
not appear when requesting all the available commands. In
order to execute this, you must enter the full command name.
Lists information on established events and messages.
Permits you to view the logs stored in the non-volatile
memory as well as to initialize this.
Permits you to activate the current Events Logging System
configuration, previously introduced in the corresponding
configuration process menu, without having to save and
reboot the device.
Permits the events to be displayed in the active process. From
this point on, the events cannot be viewed from the VISEVEN
process.
This command is available from any process although it does
not appear when requesting all the available commands. In
order to execute this, you must enter the full command name.
Permits you to exit event monitoring.
a) ? (HELP)
Lists the commands available for the current prompt. It is also possible to enter ? after a specific
command in order to list its options.
Syntax:
ELS+?
Example 1:
ELS+?
clear-actives
condition-debug
disable
enable
filter
hide
list
nvrlog
restore-configuration
view
exit
ELS+
Disable all enabled events at a given time

Monitoring options of condition events debugging
Disable event messages
Enable event messages
Configure the rules permitting events filtering
Prevent the events from being displayed
List information on established events and messages
View/Initialize the logs stored in the non-volatile
memory
Activate the current Events Logging System
configuration
Display the events in the active process
Example 2:
ELS+LIST ?
active
List the enabled events of the specified subsystem

IV - 173
Doc.DM704-I
Rev.10.97
condition
event
groups
subsystem
ELS+
List
List
List
List
the interfaces where packet marking has been enabled

event information
group information
subsystem information
b) CLEAR-ACTIVES
Permits 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+
c) CONDITION-DEBUG
Provides useful information if you want to debug the condition events feature that we saw in section 3.
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. This 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 when one of the enabled conditions has been fulfilled.
The information on the semaphore state that is displayed when the SEMAPHORE-DUMP
option is used is as follows:
Semaphore state: displays 1 if the semaphore is blocked and 0 if it isnt.
Buffer address: address for the memory where the packet that was checked is located, and
which blocked the semaphore.
Trigger condition: conduction that triggered packet checking.
Calls sequence: calls sequence in the program code through which the semaphore is blocked.
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+
d) DISABLE
Selects and disables events so that their messages are not displayed on the screen in the VISEVEN
process, nor sent as SNMP traps or syslog messages. It is possible to disable groups and subsystems,

IV - 174
Doc.DM704-I
Rev.10.97
as well as all the traces if you have previously enabled them through the ENABLE TRACE ALL
command. Additionally this permits you to disable the events filtering.
In cases where youve selected an incoming interface, in order to view the traces associated to the
process and path the packets received in the said interface have followed, the DISABLE TRACE
CONDITION INTERFACE <interface name> command permits you to disable packet marking in
this 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+disable
ALL
GROUPS <nom_group>
SYSLOG
GROUPS <nom_group>
FILTER
TRACE
ALL
CONDITION INTERFACE <interface name>
GROUPS <nom_group>
SNMP-TRAP
GROUPS <nom_group>
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+
This example disables the MYGROUP group so that the events pertaining to it are not notified via
syslog messages.
Example 3:
ELS+disable all subsystem ip info
ELS+
This example disables the INFO filter level events of the IP subsystem so that they are not displayed
nor sent as SNMP traps or through syslog messages.
e) ENABLE
Selects and enable events so that their messages are displayed on the screen, sent as traps or
transmitted through syslog messages. It is possible to enable groups and subsystems. Additionally this
permits you to enable the use of events filtering.
In section 3 in this chapter, we explained how to activate the functionality known as conditional
events: this is done by using the ENABLE TRACE CONDITION INTERFACE <interface name>
command, in order to enable packet marking in a determined interface. In this way you can view all
the events associated to packet processing as console traces by then using the ENABLE TRACE

IV - 175
Doc.DM704-I
Rev.10.97
ALL command. We do not recommend you use this command except in cases of using the said
conditional events functionality, and that you restrict the number of traces to be shown to those
associated to a packet as contrariwise all traces will be shown and device performance could be
seriously affected.
As already indicated 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, using the ENABLE TRACE CONDITION GLOBAL-BUFFERS
and ENABLE TRACE CONDITION PROTOCOL <protocol name> commands respectively.
Syntax:
ELS+enable
ALL
GROUPS <nom_group>
SYSLOG
GROUPS <nom_group>
FILTER
TRACE
ALL
CONDITION INTERFACE <interface name>
GROUPS <nom_group>
SNMP-TRAP
GROUPS <nom_group>
SNMP-TRAP-GROUP1
GROUPS <nom_group>
SNMP-TRAP-GROUP2
GROUPS <nom_group>
SNMP-TRAP-GROUP3
GROUPS <nom_group>
SNMP-TRAP-GROUP4
GROUPS <nom_group>
NOTE: On enabling an event as a trap through the snmp-trap command, this is

enabled for all the trap groups.
Example 1:
ELS+enable trace event icmp.001
ELS+
This example enables the ICMP.001 individual event so it is displayed on screen.

IV - 176
Doc.DM704-I
Rev.10.97
Example 2:
ELS+enable syslog group mygroup
ELS+
This example enables the MYGROUP group so the events pertaining to it are notified through syslog
messages.
Example 3:
ELS+enable all subsystem ip info
ELS+
This example enables the INFO filter level events of the IP subsystem so they are displayed on screen,
sent as SNMP 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 will be spent in communicating
with the VISEVEN process. If you execute this command when this 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.
f) FILTER
Permits you to add, change or delete filters individually. You need to enable the filter through the
ENABLE FILTER command in order to active it.
For further information, please see the FILTER command found in the events 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, its 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

IV - 177
Doc.DM704-I
Rev.10.97
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+
g) HIDE
Prevents the events from being displayed in the active process. From this point on, the events can only
be viewed from the VISEVEN process.
This command is available from any process although it does not appear when requesting all the
available commands. In order to execute this, you must enter the full command name.
Syntax:
ELS+hide
Example:
ELS+hide
ELS+
h) LIST
Lists information on events enabled, groups created and subsystems. This also displays the interfaces
enabled to use the conditional events functionality.
Syntax:
ELS+list ?
active
condition
event
groups
subsystem
ELS+
List
List
List
List
List
the enabled events of the specified subsystem

the interfaces where packet marking has been enabled
event information
group information
subsystem information
LIST ACTIVE
Example:
ELS+list active arp
Actives
Count
ARP.001
0
ELS+
Trace
on
Syslog
off
Snmp-Trap
on ( group 1 )
This lists the enabled events in the ARP subsystem, the number of times that each event has occurred
and the enabling vector of each event.
Note: Events with ALWAYS filter levels are always enabled to be displayed on screen
(e.g. GW.001). In the same way there are events enabled as traps which cannot be
disabled as they generate the SNMP generic traps (e.g. GW.021 link up).

IV - 178
Doc.DM704-I
Rev.10.97
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 displayed. For further information on this, please see section 3 (Events
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
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.

Lets suppose that the event is enabled to be displayed on screen, sent as a syslog message and as a
specific company trap, the information that we can receive is shown in the example.
LIST GROUP
Example:
ELS+list group
Group: MYGROUP
Event
IP.002
IP.003
IP.004
Globaly enable as:
ELS+
Trace
on
on
on
(Trace)
Syslog
off
off
off
Snmp-Trap
on ( all groups )
on ( group 2 group 4 )
off
This shows the group name, the set of events which it is composed of, the enabling status of each
event and the current global 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 the example.
LIST SUBSYSTEM
Example 1:
ELS+list subsystem icmp
Event
Level
Message
ICMP.001
ICMP.002
ICMP.003
ICMP.004
ICMP.005
ICMP.006
ICMP.007
ICMP.008
ICMP.009
UE-ERROR
C-INFO
U-INFO
CI-ERROR
U-TRACE
UE-ERROR
C-TRACE
C-TRACE
UI-ERROR
bd cks 0x%04x (exp 0x%04x) %I -> %I

ech %I -> %I
ech rp %I -> %I
unhnd typ %d %d %I -> %I
unhnd brd typ %d %d %I -> %I
bd typ %d %d %I -> %I
addr msk %I -> %I
addr msk rep %I -> %I
no pkt or mem

IV - 179
Doc.DM704-I
Rev.10.97
ICMP.010
ICMP.011
ICMP.012
ICMP.013
ICMP.014
ICMP.015
ICMP.016
ICMP.017
ICMP.018
ICMP.019
ICMP.020
ICMP.021
ICMP.022
ELS+
UE-ERROR
UI-ERROR
C-INFO
U-INFO
U-TRACE
UE-ERROR
U-TRACE
UE-ERROR
U-TRACE
UE-ERROR
U-TRACE
P-TRACE
P-TRACE
amb addr msk %I -> %I

err %d sndng pkt to ifc %s
rdr %I -> %I to %I
bd prm off %d %I -> %I
snd %d %d pkt %I -> %I
shrt ICMP hdr %d src %I
%I rdr dest %I to %I
Bad rdr from %I, rsn: %S
Router advertisement received from %I
Bad router adv from %I, rsn: %S
rcvd typ %d %d %I -> %I
redirect message filtered at interface %s
unreachable message filtered at interface %s
Example 2:
ELS>list subsystem
Name
Events
Description
ADSL
AFS
AINST
ARP
ASDP
ARLY
ASYN
AT
ATM
BAN
BGP
BR
BRS
BSPF
CIF
CNSL
DEP
DHCP
DHCPC
DLS
DNAT
DNS
EAP
ETH
FLT
FR
FRBK
FTP
G703
GW
H323
HDLC
HDSL
HSSI
HTTP
ICMP
IGMP
IKE
IP
IP6
IPHC
IPSEC
IPX
ISDN
L2TP
LAPD
LDAP
LLC
ADSL
Advanced Fitering Subsystem
AutoInstall
Asynchronous Serial Device Proxy
Alarm Relay
AT Commands Interface
Asynchronous Transfer Mode
Boundary Access Node
Border Gateway Protocol
Bridge/Routing
Bandwidth Reservation
Bridge Spoofing
Encryption
Console
DEP Forwarder
DHCP
DHCP Client
Data Link Switching
Dynamic NAT
Domain Name System
EAP
Ethernet
Filter Library
Frame Relay
Frame Relay BACKUP
File Transfer Protocol
G703 Digital Interface
Router kernel
H323
HDLC Interface
Symetric High Bitrate Digital Subscriber Line
High Speed Serial Interface
HyperText Transfer Protocol
Internet Control Message Protocol
Internet Group Management Protocol
Internet Key Exchange
Internet Protocol
IPv6
IP Header Compression
Ip Security
Internetwork Packet Exchange Protocol
Integrated Services Digital Net
Layer 2 Tunneling Protocol
ISDN Layer 2
Lightweight Directory Access Protocol
Logical Link Control
8
6
23
10
11
41
5
20
15
29
27
48
9
10
34
4
30
14
23
459
12
30
6
54
7
53
8
4
25
64
19
11
57
5
25
22
26
51
87
200
46
33
105
40
56
11
16
33

IV - 180
Doc.DM704-I
Rev.10.97
MCF
NAPT
NBS
NHRP
NOE
NSLA
NSM
NTP
P3OE
PHYS
PGMO
POLR
PPP
R2
RAD
RIP
RSTP
SCADA
SCDFW
SCEP
SDLC
SIP
SL
SNAT
SNMP
SPF
SRT
STP
STUN
SYNC
TCP
TIDP
TKR
TLNT
TLPHY
TNIP
TTTP
TVRP
UDAFO
UDP
VOIP
VRRP
WLAN
X252
X253
XN
9
30
50
58
17
8
82
25
23
4
5
16
100
9
46
30
9
28
20
17
95
16
36
5
26
61
89
42
3
2
55
18
46
8
23
39
18
26
41
4
14
8
4
23
26
21
MAC Filtering
Network Address Port Translation
NetBIOS Support Subsystem
NOE
Network Service Level Advisor
Network Service Monitor
Network Time Protocol
PPP over Ethernet
ISDN BRI Layer 1
POS Gateway Monitor
Policy routing
Point to Point Protocol
R2
Remote Authentication Dial In User Service
IP Routing Information Protocol
Rapid Spanning Tree Protocol
SCADA Network
SCADA Forwarder
Simple Certificate Enrollment Protocol
IBM SDLC
SIP
Serial Line
Static NAT
Simple Network Management Protocol
Source Routing Transparent Bridge
Spanning Tree Protocol
STUN
Synchronous Serial Line
Transmission Control Protocol
T. IP Discovery Protocol
Token Ring
Telnet
TLPHY
IP Tunnel
T. Transaction Transfer Protocol
T. Virtual Router Protocol
UDAFO Forwarder
User Datagram Protocol
Voice over IP
Virtual Router Redundancy Protocol
Wireless LAN
X.25 Layer 2
X.25 Layer 3
Core Xerox Network System
ELS+
i) NVRLOG
Permits you to view the logs saved in the non-volatile memory as well as to 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
Permits you to select the number of logs to be displayed on the console.
Syntax:
ELS+nvrlog list <number_of_logs>

IV - 181
Doc.DM704-I
Rev.10.97
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 associated to the said log (between hyphens) and a text containing information relative to
the 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+
j) RESTORE-CONFIGURATION
This permits you to reestablish 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
ELS+
k) VIEW
Permits the events to be displayed in the active process.
This command is available from any process although it does not appear when requesting all the
available commands. In order to execute this, you must enter the full command name.
Syntax:
ELS+view
Example:
ELS+view
ELS+
l) EXIT
This allows you to exit the Event Logging System monitoring and return to + prompt.
Syntax:
ELS+exit
Example:
ELS+exit
+

IV - 182
Doc.DM704-I
Rev.10.97
5. Supported personalized parameters

The Teldat devices have personalized parameters which modify the behavior of the device under
certain special circumstances (personalized versions). For further information on the activation,
deactivation and listing of these parameters, please see the help command in the enable, patch,
disable patch and list patch commands respectively. These can be found in Chapter 2, Teldat Router
Configuration, of this manual (Dm704 Configuration and Monitoring).
The Events Logging System has the following personalized parameters:
SRE_INT_FLAGS
This patch permits you to modify the events logging system behavior. Normally it is not necessary to
use this, but it is useful to have this patch for debugging and development effects. The patch value is
the sum of the flags used.
Value: 0
Normal event logging system operation.
Flag: 1
The event logging system stops introducing events in the round viewing buffer when
this is full. This means that when the events cannot be viewed and the buffer is full,
CPU time is not consumed thus increasing performance. The secondary effect of this
is that the latest events to arrive are lost, not the oldest.
Flag: 2
In viewing, the time and date do not appear as it does not consult the real time clock
and the performance is improved.
Example:
Config>enable patch sre_int_flags 1
Config>list patch
Patch Name
Value
----------------------------------------SRE_INT_FLAGS
1 (0x1)

IV - 183
Doc.DM704-I
Rev.10.97

Dm704 Iv10 97 Configuration Monitoring

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Dm704 Iv10 97 Configuration Monitoring

Transféré par

Droits d'auteur :

Formats disponibles

Teldat Router

Configuration and Monitoring

Chapter 2 Teldat Router Configuration..........................................................................18

Chapter 3 Teldat Router Monitoring ..............................................................................99

Introduction ........................................................................................................................ 100

Chapter 4 Event Logging System ELS ............................................................................138

Introduction ........................................................................................................................ 139

TELDAT ROUTER - The Console

2. Local and remote terminal

This process allows events produced in the system to be displayed, from

TELDAT ROUTER - The Console

3.1. Teldat Router connection

where XXXXX is the specific router model.

TELDAT ROUTER - The Console

System access is not permitted.

TELDAT ROUTER - The Console

TELDAT ROUTER - The Console

If the password is not entered within approximately 20 seconds or the password

3.2. Executing a command

3.3. User Interface Processes

TELDAT ROUTER - The Console

TELDAT ROUTER - The Console

3.4. Accessing the processes

3.5. Returning to the Console Manager

TELDAT ROUTER - The Console

Other protocol configuration/monitoring menus can be accessed from the

3.6. Obtaining help

TELDAT ROUTER - The Console

4. GESTCON process commands

Accesses the monitoring process.

TELDAT ROUTER - The Console

Press (Ctrl+u) and <>

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

TELDAT ROUTER - The Console

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

TELDAT ROUTER - The Console

TELDAT ROUTER - The Console

TELDAT ROUTER - The Console

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

Telnet to device 172.24.78.92 using the router_aux VRF.

TELDAT ROUTER - The Console

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

TELDAT ROUTER - The Console

TELDAT ROUTER - Configuration

Example of erroneous commands:

TELDAT ROUTER - Configuration

Config>set data-link x25 serial0/0

In this new example, the diagram of the device is as follows:

TELDAT ROUTER - Configuration

Add a subinterface associated to the said interface:

Config>add device atm-subinterface atm3/0 2

TELDAT ROUTER - Configuration

TELDAT ROUTER - Configuration

3. Configuration procedure user interface

User Console root

User Console teldat

TELDAT ROUTER - Configuration

TELDAT ROUTER - Configuration

TELDAT ROUTER - Configuration

TELDAT ROUTER - Configuration

TVRP config>show menu

TELDAT ROUTER - Configuration

TELDAT ROUTER - Configuration

Allows you to create a virtual interface.