CPU4 CARD MAINTENANCE

1. CPU4 CARD MAINTENANCE Running the card properly…

2. 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

3. 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.

4. 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 IPP=1 : ETH1 IP P=2 : Gateway address P=3 : Subnet mask X part notates the IP address

5. 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.

6. IP ADDRESS DEFINITION VIA IDEA : On configuration window right-click the CPU card and select network settings

7. IP ADDRESS DEFINITION CPU Network Settings menu is shown below Note : After changing the IP address, click OK and reset the PBX .

8. 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

9. 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).

10. TELNET The screenshot below shows how to make this process. NOTE. This command also can be entered from the MS-DOS Command prompt.

11. 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.

12. 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 changedto 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.

13. IFCONFIG COMMAND • Finally, • Turn OFF&ON • the exchange • and check that • new IP address • is reachable.

14. 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.

15. 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.

16. 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.

17. WEB INTERFACE

18. 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.

19. WEB INTERFACE • IDEA LINK : On Idea main connection window, click advanced button and select PABX Web Interface option.

20. 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

21. WEB INTERFACE • LOGIN PASSWORDS : For DS200 PBX : ds200 For DS200S/M PBX : ds200s

22. 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.

23. 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

24. 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

25. WEB INTERFACE • 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 • FIREWALL MENU:

26. WEB INTERFACE • 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 • FIREWALL MENU:

27. WEB INTERFACE • 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. • FIREWALL / ALLOWED IP – MAC ADDRESS MENU:

28. WEB INTERFACE • 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 • FIREWALL / LIMITS MENU:

29. WEB INTERFACE • 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. • UPDATE MENU:

30. 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

31. WEB INTERFACE • 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. • MANAGEMENT / PROCESS STATUS MENU:

32. WEB INTERFACE • 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) • MANAGEMENT / MONITOR MENU:

33. WEB INTERFACE • 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. • MANAGEMENT / MONITOR / CONNECTED TCP PORTS MENU:

34. WEB INTERFACE • 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. • MANAGEMENT / MONITOR / LISTENED TCP/UDP PORTS MENU:

35. WEB INTERFACE • Web Interface’s login password is changed in this section. Old password is required to create a new password. • Application version information is monitored in this section • MANAGEMENT / CHANGE PASSWORD MENU: • MANAGEMENT / VERSION MENU:

36. MASTER SOFTWARE UPDATE

37. 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.

38. 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.

39. DSINSTALL COMMAND # stop This command is used to restart the system.

40. 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.

41. 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.

42. REPO.CONF FILE A sample of repo.conf file is shown below. The latest master software information exists in the “DSU_MASTER_CURRENT” part.

43. DSUPDATE.CONF FILE karel/home/conf/dsupdate.conf file is reached by using WinSCP program connection.

44. 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.

45. KTFTP.EXE KTFTP program is started by double-clicking the KTFTP.exe file on the PC.

46. 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.

47. 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.

48. 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.

49. TELNET COMMANDS

50. COMMANDS # stop restarts the system. # ifconfig lists the ethernet cards that have been defined on the CPU4 Card. # netstat –tan views theIP and port numbers of the TCP connections established by the CPU4 Card on the screen.Statuses and the TCP port numbers are shown below.