ABB EDS500 Series Operating Instruction page 4

The default configuration for the serial connection is:
57600 Baud 8N1 (8 data bits, no parity, 1 stop bit), no
hardware flow control.
IP based configuration, remote configuration
After establishing a network connection to the
device and configuring IP addresses as required (i.e.
"the device can be pinged"), the following remote
configuration features can be used:
Telnet
•
Telnet clients like HyperTerminal, PuTTY or
telnet.exe (on the PC command line interface)
can be used to establish a telnet session with the
device. The IP address of the unit has to be used
as Telnet target. Telnet access can be disabled by a
configuration command.
SSH
•
Suitable SSH clients on the PC side are programs
like Tera Term or PuTTY. The tar-get address is the
device's IP address. During the connection you will
be prompted for authentication credentials. The
default login name is edslogin, the password is
empty when in delivery status. SSH access can be
disabled by configuration.
Webserver
•
With the webserver activated (default setting)
browsers like Firefox, Opera, Safari, Chrome or
the Internet Explorer can be used to configure
the devices using the web interface. To do so
enter the device IP into the browser address
field. The device will subsequently request
authentication credentials. The default login name
is edslogin, the password is empty when in delivery
status. Webserver access can be disabled by a
configuration command.
The command line interface
The command line of the 500NMD43 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 < e n a b l e > command. Both authentication
levels can be protected by a password, the
respective commands are < s e t l o g i n p a s s
{ s t r i n g 2 0 } > and < s e t e n a b l e p a s s
{ s t r i n g 2 0 } > .
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
the command < w r i t e > . 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 < w r i t e >
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 < s h o w
r u n n i n g - c o n f i g > (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 500NMD43 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
m a s t e r > 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.
[dB]
Signal quality (SHDSL.bis)
35
30
25
20
15
10
5
0
0 1 2 3 4 5 6 7 8 9 10 11 12
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
192 kbps
256 kbps
512 kbps
768 kbps
1024 kbps
1536 kbps
2048 kbps
3072 kbps
4096 kbps
5696 kbps
8192 kbps
10240 kbps
11400 kbps
13 14 15 16 17 18 19 20 21 22 23 24 25 [km]
automatic connection