CPU4 CARD

MAINTENANCE
Running the card
properly…
TOPICS
IP ADDRESS DEFINITION
* Via Operator Console “This method is essential if CPU4 card’s
ip address is unknown”
* Via IDEA Program
* Via Web Interface
* Via Telnet
- Setting the “hosts” file.
- Gateway
MASTER SOFTWARE UPDATE
* Via Telnet Connection
* Via TFTP Server Remotely
* Via SNMP Connection
WEB INTERFACE
TELNET COMMANDS
WINSCP CONNECTION
OBTAINING LOGS
*Ethereal Log
*Log File of the System
CPU4 ETHERNET PORTS
CPU4 Card has 2 ethernet ports on it.

• One of them, eth0 ( J10 connector), is used for the

connection for the system and sip_spc applications.
Sip_spc is a proxy server needed for the
communication of SIP phones.

• Other ethernet port on the CPU4 card is eth1( J11

connector), and used for SIP Trunk applications.
This document focuses on eth0 especially. For the
settings of eth1, KNE program will be used.
IP ADDRESS DEFINITION
VIA OPERATOR CONSOLE
In order to change the IP addresses of CPU4 Card
800490 code must be entered on operator console

800490 P XXX XXX XXX XXX

P=0 : ETH0 IP
P=1 : ETH1 IP
P=2 : Gateway address
P=3 : Subnet mask

X part notates the IP address

IP ADDRESS DEFINITION
• EXAMPLE : To assign 192.168.2.10 IP to Eth0;

800490 0 192 168 002 010

Code must be entered

(Zeros “0” must be added to the code accordingly)

Note : After changing the IP address, the PBX must be restarted.

IP ADDRESS DEFINITION
VIA IDEA :
On configuration window right-click the CPU card and select network settings
IP ADDRESS DEFINITION
CPU Network Settings menu is shown below

Note : After changing the IP address, click OK and reset the PBX .
IP ADDRESS DEFINITION
VIA WEB INTERFACE
IP addresses can be defined on System tab.

Note: Details of Web Interface connection are given at the following parts of this document
IP ADDRESS DEFINITION
Via TELNET:
• An alternate method In order to define IP address to the
CPU4 card is “Telnet”. The necessary steps below are
followed for IP address definition.
• At the maintenance computer (the Windows O.S. based
computer which is connected to the same network) , “Run”
option is selected at the “Start” menu.
• Here, in order to provide Telnet connection to the CPU4
Card,
“telnet -t vt100 192.168.128.179”
command is entered (It is assumed that the IP address of
the CPU4 card is192.168.128.179).
TELNET
The screenshot below shows how to make this process.

NOTE. This command also can be entered from the MS-DOS

Command prompt.
TELNET
• At the Telnet window , UserName and Password written
below should be entered.
Username ( login ) : root
Password : ds200
NOTE. If the system type is DS200S or DS200M, “ds200s” will be
entered as the Password.
CHGIP COMMAND
• By the “ifconfig” command, you can see eth0 and its IP
address which is the IP address of the CPU4 card.
NOTE: eth0 is the first ethernet port of the CPU4 Card. This port is
used for the connection to the system.
• When “ chgip eth0 192.168.xxx.yyy
255.255.255.0” is entered, IP address of the CPU4 card
is changed to 192.168.xxx.yyy (you can write any desired
proper IP address here ) which was 192.168.178.179 before
as shown in the figure above. And also by this command,
NetMask IP address is changed to 255.255.255.0 which was
255.255.192.0 before.
IFCONFIG COMMAND

• Finally,
Turn OFF&ON
the exchange
and check that
new IP address
is reachable.
SETTING THE “HOSTS” FILE
• At the WinSCP connection, there is a “hosts” file under the
flash/etc directory ( Details of WinSCP connection are given at
the following parts of this document). This file contains the
information about the IP addresses of the ethernet ports of CPU4
Card. According to the terminology, z1 corresponds to main CPU4
card and z2 corresponds to the redundant CPU4 card.
• In the “hosts” file, z1 at the first row specifies the first ethernet port
(eth0) of the main CPU4 Card and the second row specifies the
second one (eth1). Additionally, z2 at the 3rd row specifies eth0
and z2 at the 4th row specifies eth1 of the redundant CPU4 Card.
• If the system has redundant CPU4, “hosts” file should be set
according to this. And also similar settings should be done after
establishing a WinSCP connection for the redundant CPU4 Card.
• If the IP address of the CPU4 card or the redundant one is
changed, this file should be set as well.
HOSTS FILE
NOTE: It will be
useful to check
“hosts” file even if
the IP address of
CPU4 Card is not
changed.

IMPORTANT: If
wrong settings are
done in this file,
CPU4 cards
(main&redundant)
will not operate
properly.
GATEWAY IP ADDRESS
• In order to change the Gateway IP address of the CPU4 Card, firstly
WinSCP connection is established. After that flash/etc/rc.sh file is reached, in
this file, new Gateway IP address is written to the
“ route add default gw 192.168.xxx.yyy”
part and saved. After these, system needs to be restarted for performing with
the new Gateway IP address. A sample of rc.sh file is shown below.
WEB INTERFACE
WEB INTERFACE
• WEB INTERFACE : Provides user – friendly interface and
simple configuration options for softwares which run on new
CPU card.

• Any web browser is sufficient for connection (firefox,internet

explorer). No additional software is required (putty,winscp,...etc)

Connection Types:
1) IDEA Link
2) Manual Connection.
WEB INTERFACE
• IDEA LINK : On Idea main connection window, click advanced
button and select PABX Web Interface option.
WEB INTERFACE
• MANUAL CONNECTION: You may also use manual
connection if IDEA program is not installed on your system.

Enter the IP address of CPU4 Card (eth0 or eth1) on web

browser’s address bar and use the port number 3802
WEB INTERFACE
• LOGIN PASSWORDS :

For DS200 PBX : ds200

For DS200S/M PBX : ds200s
WEB INTERFACE
• MAIN MENU: Consists of sub 5 tabs

• System : Contains IP based system parameters

• Buddy CPU : Contains redundant CPU related parameters
• Firewall : Firewall settings are configured on this tab
• Update : Remote master software update is done on this tab
• LDAP : Provides remote LDAP server configuration
• Management : System related information and monitoring is done on
this tab.
WEB INTERFACE
• SYSTEM MENU:

• 1st IP address: IP address of eth0

• 2nd IP address: IP address of eth1
• Netmask: Netmask of connected network
• Gateway: IP address of gateway device

• DNS enabled: Enables/Disables DNS server

• DNS server : IP address of DNS server

• DHCP enabled: Enables/Disables DHCP feature

• NTP enabled: Enables/Disables NTP server

• NTP server: IP address of NTP server
WEB INTERFACE
• BUDDY (REDUNDANT) CPU MENU:

• Buddy CPU enabled : Enables / Disables the redundant CPU

• Buddy CPU : IP address of the redundant CPU is entered here

WEB INTERFACE
• FIREWALL MENU:
• Open TCP Ports: CPU only accepts connection
from specific TCP Ports
• Open UDP Ports: CPU only accepts connection
from specific UDP Ports
• Allowed Mac Addresses: CPU only accepts
connection from devices with specific Mac
addresses
• Allowed IP Addresses : CPU only accepts
connection from devices with specific IP
addresses
• Limits : CPU limits a total number of packets that
received in a period of time to protect the system
against malicious attacks
• Firewall Enabled: Enables / Disables Firewall
WEB INTERFACE
• FIREWALL MENU:
• Open TCP Ports: CPU only accepts connection
from listed TCP Ports below. Some ports are
pre-defined and they can be removed from this
list. You may add additional TCP ports for your
system needs by using New port window.

• Open UDP Ports: CPU only accepts connection

from listed UDP Ports below. Some ports are
pre-defined and they can be removed from this
list. You may add additional UDP ports for your
system needs by using New port window.

To define a port range, ex: between 2000 - 3000

This notation must be used: 2000:3000
•
WEB INTERFACE
• FIREWALL / ALLOWED IP – MAC ADDRESS MENU:
• Allowed Mac Addresses: CPU only accepts
connection from devices with listed Mac
addresses. By system default this list is empty.
If any mac address is defined here; system
automatically rejects the connection requests
from devices with different mac addresses.

• Allowed IP Addresses : CPU only accepts

connection from devices with specific IP
addresses By system default this list is empty.
If any IP address is defined here; system
automatically rejects the connection requests
from devices with different IP addresses.
WEB INTERFACE
• FIREWALL / LIMITS MENU:
• Limits : CPU can limit a total number of packets
that received in a period of time to protect the
system against malicious attacks

• Max packet count in 60 seconds: default 600

• Max packet count in 2 seconds: default 100

• Average packet count in 60 seconds: default 900

• Burst limit in 60 seconds: default 200

WEB INTERFACE
• UPDATE MENU:
• Update Server : IP address of master software
update server is defined here.

• Force on same version : If this option selected

as “Yes” downloaded new master software is
overwritten on current cpu software. In this
situation old software is deleted. If “No” option is
selected; downloaded new master software is
written on different memory location. And old
software is preserved.

• Auto restart new server : If this option selected

as “Yes” pbx immediatly restards and loads new
software after the download procedure is
completed. If “No” option is selected, Pbx
restards at first night at 02:00am.
WEB INTERFACE
• LDAP MENU:

• LDAP settings are done on this menu.

Some notations are given below:

dc : Domain Component

ou : Organizational Unit

cn : Common Name
WEB INTERFACE
• MANAGEMENT / PROCESS STATUS MENU:

• Process Status: Lists the status of all

applications that runs on CPU.

• In case of need, the first six applications (with

checkboxes) can be manualy restarted. This
feature allows to fix some issues with related
services without reseting (power off/on) the Pbx.
WEB INTERFACE
• MANAGEMENT / MONITOR MENU:

• Uptime: a period of time when the Pbx is

functioning and available for use.

• Free : This section shows the amount of ram

usage (128MB total)

• Disk free : This section shows the flash memory

usage (4GB total)
WEB INTERFACE
• MANAGEMENT / MONITOR / CONNECTED TCP PORTS MENU:

• Connected TCP ports – Local: This section

shows the local TCP communication between
applications that runs on CPU.

• Connected TCP ports : This section shows the

local TCP communication between applications
that runs on CPU and other peripheral devices/
modules.
WEB INTERFACE
• MANAGEMENT / MONITOR / LISTENED TCP/UDP PORTS MENU:

• Listened TCP ports: Applications on CPU card

periodically checks the listed TCP ports, in case
of incoming connection request/attemp.

• Listened UDP ports: Applications on CPU card

periodically checks the listed UDP ports, in case
of incoming connection request/attemp.
WEB INTERFACE
• MANAGEMENT / CHANGE PASSWORD MENU:
• Web Interface’s login password is changed in
this section. Old password is required to create a
new password.

• MANAGEMENT / VERSION MENU:

• Application version information is monitored in
this section
MASTER SOFTWARE
UPDATE
TELNET CONNECTION
• After establishing the connection via WinSCP Program, the master
software to be loaded is copied under the karel/bin directory from the PC
which is in the same network with the CPU4 Card.
DSINSTALL COMMAND
After the Telnet connection is established, following commands shown
below are entered in the Telnet screen in order to complete the update
operation.
# cd /karel/bin
In order to enter the commands shown below, firstly karel/bin directory is
reached.
# dsinstall p_xxx_yy.rpm
By this command, a directory named “p_xxx_yy.rpm” and the script files
which have “rt” extension are formed automatically in the karel/bin
directory.
And “p_xxx_yy.rpm” software is loaded to the CPU4 Card. This
command
sets the read-write-execute (r-w-x) authorities of the files under the karel
directory automatically. So there is no need to run check command.
DSINSTALL COMMAND

# stop
This command is used to restart the system.
TFTP SERVER REMOTELY
Remote software update operation is done via KTFTP Server application.

► First, a directory named karel should be created in the Server PC. Then
a directory named board should be created under the karel directory.
And a directory named ds200 should be created under board directory
and the files written below ( repo.conf, KTFTP.exe, p_xxx_yy.rpm)
should be copied into this directory.

NOTE: For DS200S and DS200M systems, karel/board/ds200s should be

created.

IMPORTANT: Names of the directories should be given as

“karel”,“board”and “ds200”. This is important because the system will
know these directories according to their names during the update operation.
DS200 DIRECTORY
repo.conf → The master software information to be loaded is saved in this file.
KTFTP.exe → TFTP Server software.
p_xxx_yy.rpm → The master software to be loaded

NOTE: Several
Master software
versions can be
copied in the
ds200 directory.
REPO.CONF FILE
A sample of repo.conf file is shown below. The latest master software
information exists in the “DSU_MASTER_CURRENT” part.
DSUPDATE.CONF FILE
karel/home/conf/dsupdate.conf file is reached by using WinSCP program
connection.
DSUPDATE.CONF FILE
Then after double-clicking the dsupdate.conf file, IP address of the TFTP
Server computer is written into this file. NOTE: In the
dsupdate.conf file there
is a parameter named
DSU_AUTO_RESTART
This parameter is set as
“yes” by default for
normal update operation.
If this parameter is set as
“no”, update operation
will be performed at at
02:00 of that
night automatically.
KTFTP.EXE
KTFTP program is started by double-clicking the KTFTP.exe file
on the PC.
DSUPDATE COMMAND
After the Telnet connection is established, “dsupdate” command is entered.
By this command, the master software version written in the repo.conf file is
automatically loaded to CPU4 Card. This command sets the read-write
execute (r-w-x) authorities of the files under the karel directory automatically.
So there is no need to run check command.
*** After the loading
operation is
completed, the
exchange restarts
Automatically and
operates with the
new software.
DSUPDATE COMMAND
NOTE: For updating the CPU4 Card software, there is an alternative
command “dsupdate master p_xxx_yy”. If this command is used, system
automatically updates the CPU4 master software to the p_xxx_yy. In this
case there will be no need to change the software written in the repo.conf file.
It will be necessary and enough to copy the master software under the
“ds200” directory.
SNMP CONNECTION
• The software update
operation can also be done
Via SNMP connection. This
operation is done by
“SwUpdateMasterSw” part
from the MIB Browser . After
the loading operation is
completed, the exchange
operates with the new
software.
TELNET COMMANDS
COMMANDS
# stop
restarts the system.

# ifconfig
lists the ethernet cards that have been defined on the CPU4 Card.

# netstat –tan
views the IP and port numbers of the TCP connections established by the CPU4
Card on the screen. Statuses and the TCP port numbers are shown below.
PORT NUMBERS & STATES
● TCP port numbers
● Statuses
IDEA&SNMP  24998
Listen  Listening
NETCONSOLE  25000
Established  Connection is done
WEBCM  24995
CloseWait  Hanged
NETCM  24999
ALARM (LOCAL)  25003
ALARM (REMOTE)  25004 (For
Public Switch Systems )
SIP_SPC  30876
NETSTAT COMMAND
NETSTAT COMMAND
#getconf lists the running software versions on the screen.

# check p_xxx_yy sets the read-write-execute (r-w-x) authorities of the files

under the karel directory. If “dsupdate” and “dsinstall” commands are
entered, these ones automatically sets the authorities, there will be no need
to run “check” command .

# ls lists the content of the related directory.

#dslog shows basic information: stop&start times of the system, connection

statuses and some software versions.

# dslog | more lists the log information page by page ( See the last page of
this document) .
WINSCP CONNECTION
WINSCP
• WinSCP program is used for making the file transfer between
the devices in the same network. The program WinSCP is
installed on the Windows-based maintenance PC that is in the
same network and then the Linux based CPU4 Card is
accessed .

• After establishing the connection to the WinSCP program as

shown below, some directories and files are supposed to be
checked. Making the essential settings are explained below.
USERNAME & PASSWORD
After the installation of the program WinSCP is over, the following window
appears. The IP address of the CPU4 Card is typed as the “Hostname”. The
username and the password are entered. FTP should be selected as “File
Protocol”.

Username: root
Password: ds200

NOTE: For DS200S and DS200M systems, the password is ds200s

WINSCP LOGIN
KAREL DIRECTORY
• The left half of the
window that opens
shows the folders on
the maintenance
computer ( Windows
PC) while the right half
displays the ones on
the CPU4 Card.
“karel” directory is
loaded to the CPU4
Card by default. But it
will be useful to check
the directories shown
below.
KAREL DIRECTORY

Normally, CPU4 Card works with the default file configuration.

In some cases, some of the files in the CPU4 software
structure may need to be edited.
CONF DIRECTORY

The information about the files in the conf directory

have been presented below :

– sip_spc.conf
– snmp.conf
– dsinit.conf
– dsupdate.conf
SIP_SPC.CONF
• The configuration file for this proxy is “sip_spc.conf” . At
the beginning, there is no need to make a definition in this
file. By default, this file does not exist. If the user connects
to the KNE Program by typing the CPU4 Card’s first
ethernet port’s IP address (eth0) and “writes into Memory”,
“sip_spc.conf” file forms under the karel/home/conf
directory.

• In order to make the necessary definitions, KNE (Karel

Network Equipment) program is used. IP address of the
SIP Server , in other words IP address of CPU4 Card, is
entered to KNE program and connection is done.
SNMP.CONF

• This file exists under karel/home/conf directory

and formed for SNMP ( Simple Network
Management Protocol ) applications . IP definiton
can be made by entering an IP address into the
“TrapTargets” field. In this case, SNMP
connection can be done from the device which
has this IP address and only that device can get
the traps (alarms) . If more than one IP address
will be entered, there should be comma between
the IP addresses.
TRAPTARGETS
EXAMPLE : TrapTargets= 192.168.179.122 , 192.168.179.101
When this definition is entered, this means getting the traps and SNMP
connection can be done only from the devices which has the IP address
192.168.179.122 and 192.168.179.101
MANAGERS
SNMP Manager IP addresses which will be allowed to connect to the
system are written into the “Managers” part of this file. If more than one IP
address will be written, they must be comma-separated.

EXAMPLE : Managers= 192.168.179.122 , 192.168.179.101

DSINIT.CONF
• The file dsinit.conf specifies the
master software to run on the system.
By the dsinstall and dsupdate
commands for updating the master
software, master software information
is written into this file automatically.

• If the system has redundant CPU4

Card, “buddy= z2” definition is
necessary for operation of this card.
“version = p_bab_11” specifies the
master software to run on the system.

IMPORTANT: If the system has redundant

CPU4 Card, WinSCP connection to the
redundant CPU4 Card should be done and
“buddy= z1” definition should be done.
DSUPDATE.CONF

• This file exists under karel/home/conf directory and used for

updating the CPU4 Card’s master software remotely. For
this, IP address of the TFTP Server should be written into
this file as shown in “Via Remote Connection” part of this
document.
OBTAINING LOGS

Ethereal Log
Log File of the System
ETHEREAL LOG
ETHEREAL LOG
• Ethereal is a network analyzer program and shows IP
signalling logs. It is an open source coded program and can
be downloaded easily from internet.

• Ethereal logs are useful to observe IP communication

problems.

IMPORTANT: In order to obtain usable Ethereal logs,

programmable network switch or hub should be used.

“tcpdump” command entered under the karel directory

forms an ethereal log file in the CPU4 Card. This file will have
the IP traffic log and SIP phones which are related to the eth0.
TCPDUMP COMMAND
This command is entered as :

“ tcpdump -i eth0 –C 10 –s 1500 –w ethereal “

-i ( interface ) : specifies which interface ( Ethernet card ) is being used.

eth0: specifies the “eth0” named ethernet card is being used.

-C (capacity ): specifies the capacity of logs to be saved.

Example: -C 10 > shows the logs will be saved as 10MB sized.

-s ( snap ): amount of data for each frame in terms of byte. If not defined,
it’s 68 byte.

-w ( write ) : determines the name of the ethereal log file to be saved under
the root directory. In the example above, name of this file is written as
“ethereal” for easiness. If desired, this file can be saved in another name.
TCPDUMP COMMAND
TCPDUMP COMMAND
There is another tcpdump command.

“ tcpdump -i lo port 30876 –C 10 –s 1500 –w ethereal “

• By this command, TCP logs between sip_spc server and

master can be obtained.
ETHEREAL LOG
To obtain Ethereal logs, establish a WinSCP connection to the CPU4 Card.
Copy the file named “ethereal “ from “root” directory into the PC. It will be
necessary and enough to send this file to Karel to be analyzed
VIEWING ETHEREAL LOGS
• Select “File/Open” option after the Ethereal program is opened.

NOTE: The screeenshots below are obtained from the Wireshark program
which is the latest version of Ethereal program.
VIEWING ETHEREAL LOGS
• Select Ethereal file and open it.
VIEWING ETHEREAL LOGS
• Logs can be viewed as shown below.
LOG FILE OF THE SYSTEM
DSLOG TAR COMMAND
• For obtaining system’s log, firstly establish a Telnet connection. At the “root”
command line, type “dslog tar” and press ENTER key. After this command, all
the log files under the directory karel/home/log are zipped and a new file
named “log.tar.bz2 “ is formed.

NOTE: There is an alternative command for “dslog tar”. For example, if

“dslog tar 5” is entered, this command gets the logs of the last 5 days. So the
capacity of the log.tar.bz2 file will be smaller.
LOG.TAR.BZ2 FILE
• In order to get the “log.tar.bz2” file from the CPU4 Card, WinSCP
program is used. WinSCP connection is established to the CPU Card and
“log.tar.bz2” file is copied to the maintenance computer. It will be necessary
and enough to send this file to Karel.
DSLOG COMMAND
• In order to follow the flow of the system’s log at that moment, you can use
“dslog” command at the Telnet screen.
• Thanks to “dslog” command, system’s start&stop times, information of
which towers are connected to the system and some information about the
versions can be observed.
• By the “dslog |more“ command, these logs can be viewed page by page.
IDEA LOG FILE

• Log of the IDEA program also exists in the system’s log.

Normally, analyzing the system’s log will be enough. But
it may not be easy to view the IDEA log inside the
system’s log when the size of system’s log is too big. If
necessary, IDEA log can be analyzed separately.