
The command line interface
The command line of the 500NMD11 is similar to the
(DOS) command line known from the PC. All device
properties can be set and shown here.
•
Commands are typed into the console, pressing
< { E n t e r } >
will start execution.
•
Commands can be abbreviated as soon as they
are unambiguous, i.e.
< s h s y >
is equivalent
to
< s h o w s y s t e m >
,
< s e s w p 1 n s >
is equivalent to
< s e t s w i t c h p o r t 1 n o
s h u t d o w n >
.
•
A command overview can be listed on every level by
typing
< ? >
. Example:
< s h s y ? >
translates to
< s h o w s y s t e m ? >
and results in
s n m p s n t p
s s h s y s l o g t e m p e r a t u r e
being shown
as command keywords to follow, i.e. one possible
command is
< s h o w s y s t e m t e m p e r a t u r e >
.
•
There are two authentication levels on the
command line: Login authentication and Enable
authentication. Login authentication can be
described as a read only mode and is accessible
directly after establishing a serial connection
with the PC. Enable authen-tication is required
once you need to change system settings or
show the complete system parameter set.
Enable authentication is reached by entering
the
levels can be protected by a password, the
•
Configuration commands entered on the
command line interface are stored in the running
configuration of the device, which represents the
current state of the system. To preserve this status
after a reboot, the running configuration must
be transferred to the startup configuration using
. During system startup
all commands from the startup configuration
are being executed and thus create the running
configuration. When a configuration stick is
attached to the device, executing the
command results in the running configuration
being copied not only to the startup configuration
but also to the stick configuration (unless the stick
is set to “read only”). During system startup with
attached config stick, the stick configuration over-
writes the startup configuration.
•
The current configuration (running configuration)
can be displayed using the command
(only with Enable
authentication). The start configuration may be
shown using
< s h o w s t a r t u p - c o n f i g >
.
When a config stick is attached, its content can be
shown using
< s h o w s t i c k - c o n f i g >
Interface configuration
SHDSL interfaces
The DSL interfaces of the 500NMD11 work as point-
to-point connections over two-wire copper lines.
One side needs to be configured as master, the other
one as slave. The current master/ slave setting is
indicated through the interface’s “Master” LED on the
front panel and can be displayed using the command
< s h o w i n t e r f a c e { d s l 1 | d s l 2 } >
respectively. To change the master / slave setting use
< s e t i n t e r f a c e { d s l 1 | d s l 2 } m o d e
and
< s e t i n t e r f a c e { d s l 1 |
d s l 2 } m o d e s l a v e >
.
In delivery status, the speed of the DSL interfaces
defaults to 192 kbps. However, depending on wire
length, condition of the line and the desired signal
quality, signif-icantly higher speed rates can be
achieved.
Signal quality (SHDSL.bis)
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
35
30
25
20
15
10
5
0
11400 kbps
10240 kbps
8192 kbps
5696 kbps
4096 kbps
3072 kbps
2048 kbps
1536 kbps
1024 kbps
768 kbps
512 kbps
256 kbps
192 kbps
[km]
[dB]
Figure 2: Signal quality with 0,8mm cable diameter, no additive noise
After activating interfaces on both sides of the line
using the command
< s e t i n t e r f a c e { d s l 1 |
d s l 2 } n o s h u t d o w n >
establishment will be initiated (this setting is already
activated when in delivery status). Depending on
line length, line condition and speed settings, this
procedure might need some time and several attempts
before a successful connection can be established. The
negotiation phase is signaled through the front panel
LEDs: the DSL activity LED is blinking while DSL link
LED is off.
Generally automatic speed negotiation is configured
on the less accessible end of the DSL line (
i n t e r f a c e { d s l 1 | d s l 2 } s p e e d a u t o >
or
< s e t i n t e r f a c e { d s l 1 | d s l 2 } s p e e d
e x t - a u t o >
, see following table), while a fixed speed
value is applied to the better reachable end of the line.
Local setting
Remote setting
Speed: local
fixed, remote
auto
192, 256, 512,
768, 1024, 1280,
1536, 1792, 2048,
2304
auto
Speed: local
fixed remote
fixed
192... 2304, step
size 8 kbps
192... 2304, step
size 8 kbps
Speed: local
fixed, remote
ext-auto
192, 256, 512,
768, 1024, 1280,
1536, 1792, 2048,
2304, 2560, 3072,
3584, 4096,
4608, 5120, 5696
ext-auto
Speed: local
fixed, remote
fixed
192...11400, step
size 8 kbps
192...11400, step
size 8 kbps
Table 1:
Speed settings for the DSL interfaces
With matching interface speed configuration and after
successful connection negotiation (signaled through
the DSL link LEDs) the status of the connection
(including the signal quality) can be shown using