ABB EDS500 Series Operating Instruction page 4

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
Ethernet Interfaces
The Fast Ethernet interfaces (IEEE802.3 compliant,
10Base-T/100BaseTX) support auto MDIX, therefore
terminal devices and network equipment can be
connected both with regular and crossover cables.
Cable connection uses conventional 8P8C connectors
(RJ45). Auto negotiation as well as static speed and
duplex settings are supported. In delivery state all
interfaces are activated and auto negotiation is
con-figured. If you need to configure, for instance,
a 10 Mbps half duplex connection for port 2, the
following commands must be issued: < s e t s w i t c h
p o r t 2 d u p l e x h a l f > , < s e t s w i t c h p o r t 2
s p e e d 1 0 > and < s e t s w i t c h p o r t 2 n o
s h u t d o w n > .
Optical Interfaces
The optical interfaces are realized as SFP module slots
(Small Formfactor Plugga-ble, INF-8074i) und can be
equipped with different transceivers. The speed is
fixed to 100 Mbps, the duplex setting can be changed
(full duplex, half duplex). Delivery configuration is 100
Mbps, full duplex.
A D V I C E
When using a managed SFP unit, parameters of the
optical interface like signal quality or temperature
can be displayed and monitored.
VLAN configuration
The Ethernet, DSL and optical interfaces of the
EDS500 devices support virtual LANs complying
with the IEEE 802.1Q standard. Thus it is possible to
define logical sub-nets for different applications (for
instance, one subnet for RTU communication, an-
other subnet for voice-over-IP). The interfaces can be
configured as trunk or access ports. In default state
the DSL interfaces are configured as trunk.
Example:
• < s e t s w i t c h p o r t 1 a c c e s s - v l a n 1 0 >
configures port 1 as access port for VLAN 10.
< s e t s w i t c h p o r t 2 t r u n k - v l a n 1 0 > ,
•
< s e t s w i t c h p o r t 2 t r u n k - v l a n 2 0 >
configures port 2 as trunk port for VLANs 10 and 20
(secure trunk).
< s e t s w i t c h p o r t 3 t r u n k - v l a n a l l >
•
configures port 3 as trunk for all VLANs.
System settings
Device IP Address
In delivery state the devices have following IP
configuration:
I P A d d r e s s 1 0 . 0 . 0 . 2
I P S u b n e t M a s k 2 5 5 . 0 . 0 . 0
I P G a t e w a y 1 0 . 0 . 0 . 1
These parameters can be changed by commands listed
below:
< s e t s y s t e m i p { I P a d d r e s s } >
< s e t s y s t e m s u b n e t m a s k { s u b n e t
m a s k } >
< s e t s y s t e m g a t e w a y { I P a d d r e s s } >
System Identification Settings
For an easier identification of the devices several
description parameters can be set:
Hostname: < s e t s y s t e m h o s t n a m e
•
{ n a m e } >
Contact: < s e t s y s t e m c o n t a c t
•
{ c o n t a c t } >
Location: < s e t s y s t e m l o c a t i o n
•
{ l o c a t i o n } >
Description: < s e t s y s t e m d e s c r i p t i o n
•
{ t e x t } >
Device monitoring
For central processing of device syslog messages a
syslog server can be configured with the following
command:
< s e t s y s t e m s y s l o g s e r v e r { I P
a d d r e s s } { { 0 - 7 } | a b b - s e c u r i t y -
e v e n t s } >
In order to provide "real" timestamps in the event log
and the syslog messages a SNTP time server can be
configured: