Chakra Max Linux Installation Guide - iri.com · Chakra Max v2.0 Chakra Max Server for Linux Installation Guide 1/107 1 Introduction This document is an operations guide for installing

Chakra Max v2.0 Chakra Max Server for Linux Installation Guide

Chakra Max Server for Linux Installation Guide

Document version 1.4

Copyright © 2010-2011 WareValley Co., Ltd. All rights reserved.


i


ii

1 INTRODUCTION................................................................................................... 1

1.1 Purpose ............................................................................................................................................... 1

1.2 Definitions of Terms ....................................................................................................................... 1

2 PREPARATION FOR SETUP................................................................................ 2

2.1 Production Composition ................................................................................................................. 2

2.1.1 Forgery/Alteration Checking Process .....................................................................................................3

2.1.1.1 Checking Sealing Condition ...........................................................................................................3

2.1.1.2 Checking for integrity violations during setup and operating security

functions 4

2.1.2 Checking Product Components................................................................................................................6

2.1.3 Checking Version .............................................................................................................................................7

2.2 System Requirements...................................................................................................................... 7

2.3 Components of Chakra Max System .......................................................................................... 9

2.3.1 Chakra Max Server ..........................................................................................................................................9

2.3.2 Chakra Max Manager ................................................................................................................................. 10

2.3.3 Chakra Max Client ........................................................................................................................................ 10

2.4 Chakra Max System Operation Environment .......................................................................... 10

2.4.1 Network traffic monitoring (sniffing) environment for protected database .................... 11

2.4.2 Configuration of Chakra Max System Gateway Environment ................................................. 13

2.4.3 Configuration of Chakra Max Hybrid Environment...................................................................... 15

2.4.4 Chakra Max HA (High Availability) Configuration ........................................................................ 15

2.5 Checking Setup Environment ...................................................................................................... 17

2.5.1 Guide to the setup of Linux CentOS 5.5 package ........................................................................ 17

2.5.2 Linux CentOS 6.4 Package Installation Guide ............................................................................ 20

2.5.3 Other Environment Settings .................................................................................................................... 20

2.5.3.1 Firewall (iptables) Setting ............................................................................................................. 20

2.5.3.2 TCP Wrapper Setting ...................................................................................................................... 22

2.5.3.3 SELinux Setup ................................................................................................................................... 24

2.5.3.4 How to change the delay allocation option ....................................................................... 24

3 CHAKRA MAX LICENSE .................................................................................... 26

3.1 Issuing Chakra Max License ........................................................................................................ 26

3.2 Inputting and Viewing Chakra Max License ........................................................................... 26


iii

3.3 Viewing Chakra Max License ...................................................................................................... 27

3.4 Changing Chakra Max License ................................................................................................... 27

4 CHAKRA MAX SERVER SETUP ........................................................................ 30

4.1 Setup preparations ........................................................................................................................ 30

4.1.1 Decompression of Distributed Files .................................................................................................... 30

4.1.2 maxsetup program ...................................................................................................................................... 31

4.1.3 Running maxsetup ....................................................................................................................................... 31

4.1.4 Language setting .......................................................................................................................................... 31

4.1.5 Initial Menu Screen Upon Initial Installation .............................................................................. 32

4.1.6 Main Menu Screen Upon Additional Installation .................................................................... 32

4.2 Install Central Management Server ........................................................................................... 33

4.2.1 Setup Menu Selection .............................................................................................................................. 33

4.2.2 Inputting license information ................................................................................................................. 34

4.2.3 Agreement with license policy ............................................................................................................... 34

4.2.4 Master IP Setup ........................................................................................................................................... 35

4.2.5 System Database Generation Option Confirmation ............................................................... 36

4.2.6 System Database Installation .............................................................................................................. 36

4.2.7 Setting top administrator ......................................................................................................................... 37

4.2.8 Backup Path Setting .................................................................................................................................... 39

4.2.9 Chakra Max Web URL Setup ............................................................................................................... 39

4.2.10 Oz Report Setup ........................................................................................................................................... 39

4.2.11 Database Reboot ........................................................................................................................................ 41

4.2.12 Completion of Setup Process ................................................................................................................. 41

4.3 Install Audit Server........................................................................................................................ 43

4.3.1 Select Install Menu .................................................................................................................................... 43

4.3.2 Master IP Address Setup ....................................................................................................................... 43

4.3.3 System Database Access Information Input ............................................................................... 44

4.3.4 Audit Log Database Installation Option Selection .................................................................. 45

4.3.5 Audit Log Database Installation ........................................................................................................ 45

4.3.6 Finish Setup ................................................................................................................................................... 47

4.4 Install Chakra Gateway Server .................................................................................................... 48




4.4.4 Finish Setup ................................................................................................................................................... 50

4.5 Install Central Management Standby Server .......................................................................... 52


iv


4.5.2 License information input ..................................................................................................................... 52

4.5.3 License Policy Agreement ..................................................................................................................... 53

4.5.4 Master IP Setup ........................................................................................................................................... 53

4.5.5 System Database Information Input ............................................................................................... 54

4.5.6 Finish Setup ................................................................................................................................................... 55

4.6 System Database Installation ...................................................................................................... 56

4.6.1 Setup Menu Selection ................................................................................................................................ 56

4.6.2 Inputting license information ................................................................................................................. 57


4.6.4 System Database Installation .............................................................................................................. 58

4.6.5 Backup Path Setup .................................................................................................................................... 60

4.6.6 Database Reboot ........................................................................................................................................ 60

4.6.7 Finish Installation ....................................................................................................................................... 61

4.7 Install Audit Log Database .......................................................................................................... 62



4.7.3 Audit Log Database Installation ........................................................................................................ 65

4.7.4 Database Reboot ........................................................................................................................................ 67

4.7.5 Finish Installation ....................................................................................................................................... 68

4.8 Install Audit Standby Server ....................................................................................................... 69


4.8.2 Master IP Setup ........................................................................................................................................... 70

4.8.3 System Database Information Input ............................................................................................... 70

4.8.4 Selecting the Master Audit Server ................................................................................................... 71

4.8.5 Finish Setup ................................................................................................................................................... 72

4.9 Configure System Database as a Separate Mechanism ...................................................... 73

4.9.1 System Database Setup in a Separate Server ............................................................................ 74

4.9.2 Install Central Management Server ................................................................................................. 74

4.9.3 Chakra Max Server Startup................................................................................................................... 75

4.10 Separate Repository Configuration in Central Management Server's Duplex Co

nfiguration ............................................................................................................................................... 76

4.10.1 Install Central Management Standby Server .............................................................................. 76

4.10.2 Secondary Chakra Max Server Startup .......................................................................................... 77

4.11 Additional Configurations for Repository Dualization using LifeKeeper ................. 77

4.11.1 Add Standby WDB Information in max_engine Table .......................................................... 77

4.11.2 Manual Tasks for Repository Setup ................................................................................................ 78


v

4.11.2.1 Manual Tasks in the Primary Server ................................................................................... 78

4.11.2.2 Manual Tasks in the Standby Server .................................................................................. 78

4.11.2.3 Installation Setup Diagram of WDB Dualization Using LifeKeeper .................. 78

4.11.3 Copy WDB Startup Script ...................................................................................................................... 79

4.12 Errors in the Chakra Max Server Setup Process and Explanations .......................... 79

4.12.1 Unsupported language setting error .................................................................................................. 80

4.12.2 Database user password input error ................................................................................................... 80

4.12.3 IP Address Input Error ................................................................................................................................ 81

4.12.4 Main Menu Selection Error ................................................................................................................... 81

4.12.5 Duplicate Error ............................................................................................................................................. 82

4.12.6 Installation Not Possible Error ............................................................................................................ 83

4.13 Checking the Result of Chakra Max Server Setup ....................................................... 84

4.14 Removing Chakra Max Server ............................................................................................ 86

4.15 Restrictions ............................................................................................................................... 87

5 OPERATION OF CHAKRA MAX SERVER ....................................................... 89

5.1 Checking Running Environment ................................................................................................. 89

5.2 Run Chakra Max Repository ....................................................................................................... 90

5.3 Running Chakra Max Server ....................................................................................................... 90

5.4 Exit Chakra Max Repository ....................................................................................................... 95

5.5 Stopping Chakra Max Server ...................................................................................................... 95

APPENDIX A. HOW TO INSTALL A CLOUD ENVIRONMENT ................................. 96

APPENDIX B. RDP MONITORING APPROACH ....................................................... 105


1/107

1 Introduction

This document is an operations guide for installing of the Chakra Max Server v2.0 database

security solution (called "Chakra Max"). This operations guide is organized as follows:

Chapter 1 introduces this operator guide including its purpose, composition, and the

definitions of terms of this operator guide.

Chapter 2 describes the system requirements and environment checkpoints for Chakra

Max Server.

Chapter 3 describes the issuance, inquiry, and update processes for Chakra Max.

Chapter 4 describes the setup process for Chakra Max Server.

Chapter 5 describes the starting, running and stopping processes for Chakra Max Server.

1.1 Purpose

This operations guide describes the setup, creation, and starting processes of Chakra Max Server,

as well as guidelines for Chakra Max Server operators.

1.2 Definitions of Terms

[Table 1-1] Definitions of Terms

Terms Description

Protected

database

A protected database is registered in the Chakra Max system, and a series of

security features are applied to it.

Protected

Server

A protected server is registered in the Chakra Max system, and a series of

security features are applied to it. TCP services provided by the server

including Telnet, FTP, SSH, and Terminal Services are protected and controlled.

Unformatted

access

An access to a protected database for unformatted jobs. In general, accesses

by developer, DBA, and maintenance staff belong to this type of access. Unlike

the programmed SQLs in the Application Server, these accesses are not

standardized, temporary, and untested. Thus, ‘unformatted access’ is the

opposite of ‘formatted access. Most of these accesses are for the development

or management of a database, but active application of security policy is


2/107

needed because data can be leaked or revealed unintentionally. This belongs

to the access for which the Chakra Max system must be applied in the

gateway method.

Authentication

data

Information used to prove the identification of a user

Formatted access

This access is for formatted jobs in a protected database. The access of

Application Server in which programmed SQLs are run belongs to this type.

This access is standardized and proven in the development process. It is

sensitive to processing speed for smooth application services. Security threats

are relatively few because it is an access type involving access by automated

programs. Considering the cost of the processing speed, sniffing is applied

rather than gateway. However, an appropriate security policy must be defined

because security threats through applications such as SQL injection always

exist.

Security policy

This is a policy to protect database and server from dangerous behaviors that

violate security rules. Examples include access control, SQL execution control,

System command execution control, SQL job approval, and masking policy to

prevent information leakage. If a policy is violated, an alarm is raised and the

access and SQL can be blocked, and the details of incident are reported to the

administrator or other linked systems.

Chakra Max

Repository

This is a database that stores various management data required for Chakra

Max operation and the audit data collected from protected database or server.

It needs to be regularly checked and backed up because large volumes of logs

are generated.

Sniffing

This is a technique for monitoring communication information in packet unit

which is exchanged on a network. The Chakra Max security audit feature sniffs

the communication details from the network and analyzes it in such a way

that the performance of the protected database dose not decline.

2 Preparation for Setup

2.1 Production Composition

When you accept Chakra Max for setup, you must first check the following:


3/107

2.1.1 Forgery/Alteration Checking Process

When you accept Chakra Max, check the product in the following process to make sure that it has

not been forged or altered.

Check the sealed condition of the product box and CD case.

Compare the version on the product box and CD with the the version in the license

of the product.

Check to see if all components are included.

Check for any integrity errors while setting up the package.

Check for any integrity errors while running the security functions.

If any problem occurs in the above process, please contact the Technical Support Center for

WareValley or your dealer.

2.1.1.1 Checking Sealing Condition

Figures 2-1 and 2-2 show the normal seal and a damaged seal, respectively. You must not set up

the product if the seal is damaged as shown in Figure 2-2.

[Figure 2-1] Seal sheet in normal condition

[Figure 2-2] Seal sheet in damaged condition


4/107

2.1.1.2 Checking for integrity violations during setup and operating security functions

To verify the setup file integrity, run the “./maxsetup” command in the setup folder.

If maxsetup is unavailable to run due to an integrity error, the following errors can be found.

root@cen65:/home/v2.0.8/setup# ./maxsetup

|#########################################################|

|# #|

|# Welcome to Server Configuration #|

|# #|

|#########################################################|

File[../setup/maxsetup.md] Open Error [No such file or directory]

root@cen65:/home/v2.0.8/setup#

[Figure 2-3] Setup screen in integrity error condition

You can verify the integrity of the Chakra Max Server binary file by checking the log messages of

Chakra Max Server. If an integrity error occurs, the error message can be found in maxsvr.log.

03-14 22:34:54: 3 *****************************************************************

03-14 22:34:54: 3 ****************** Chakra MAX Server Start **********************

03-14 22:34:54: 3 *****************************************************************

…

03-14 22:34:54: 3 Main::StartupServer(540) INVALID maxsvr

03-14 22:34:55: 0 main(309) - Failure : Failed to start server

[그림 2-3] maxsvr.log screen in integrity error condition

For the Chakra Max Manager execution file, check the integrity by whether the login window or

the warning window appears when you run the Chakra Max Manager program.

Normal condition


5/107

[Figure 2-5] Chakra Max Manager in normal condition

Error condition

[Figure 2-6] Chakra Max Manager in integrity error condition

For the Chakra Max Client execution file, check the integrity by whether the login window or the

warning window appears when you run the Chakra Max Client program.


6/107

Normal condition

[Figure 2-7] Chakra Max Client in normal condition

Error condition

[Figure 2-8] Chakra Max Client in integrity error condition

2.1.2 Checking Product Components

Check to see if there are all components of Chakra Max through the following table.

[Table 2-1] Product components

Components Remark

Chakramax_setup_v*.*.*.*.tar.gz

ClientSetup_v*.*.*.*.exe

ManagerSetup_v*.*.*.*.exe

SetupMaker_v*.*.*.*.zip

Product setup file for partial

distribution, only a part of the

components are included

Chakra Max Operator Guide.pdf

Chakra Max Administrator Guide.pdf

Chakra Max User Guide.pdf

Guides for partial distribution,

only a part of the components

are included


7/107

2.1.3 Checking Version

To make sure that you have the correct version, compare the version on the product box and CD

with the product license version.

[Product License] [Product Box] [CD Case and CD]

The following shows the product version checking screen. If the version on the screen does not

match the version on the product, please contact the Technical Support Center of WareValley or

your dealer so that they can take appropriate measure.

root@cen65:/home/v2.0.8/bin# ./maxsvr -version

Chakra Max Server v2.0.8.01 (r31271 : /trunk/server)

Libraries:

openssl: OpenSSL 1.0.1o 12 Jun 2015

2.2 System Requirements

[Table 2-2] Requirements of Chakra Max Server

Component Requirements

Processor Quad or Hex Core x64 processor

Recommendation: 2 GHz or faster.

Note: Recommended CPU speed is 3 Ghz and over.

Note: x86 processor and Itanium processor are not supported.

Memory Recommendation: 16GB RAM or greater.

Available Disk Space Recommendation: 1TB or greater.

Note: It is recommended to install the Chakra Max Server Binary and

the database in which audit logs are accumulated on separate drives.

OS software Linux CentOS v5.5 64 bits or higher (kernel 2.6.18)

Note: Recommended OS Version is CentOS v6.4.


8/107

Actual system requirements may vary depending on the Chakra Max system configuration and

optional functions.


9/107

2.3 Components of Chakra Max System

The database security solution Chakra Max System consists of the following three software

components.

2.3.1 Chakra Max Server

[Figure 2-4] Chakra Max Central Management Environment Configuration

This software component takes charge of the Chakra Max security functions. It is typically

set up as an appliance and runs nonstop 24 hours a day throughout the year. The Chakra

Max Server consists of the Audit Servers (Sniffing mode) that only monitor the

input/output Network Traffic, the Gateway Server that involves actively the Network

Traffic between databases and operators, and the Central Management Server that

maintains them.

The Central Management Server performs policy management, real-time monitoring, and

audit log collecting. The audit logs can be managed in the Central Management Server or

collected separately in the Audit Servers.

The security features of Audit Server are executed by monitoring the input/output

Network Traffic of a protected Database. Therefore, Hardware or Software setup is

mandatory for Audit Server to receive this Network Traffic input.

If the settings are configured for Audit Server to receive the input/output Network Traffic

of a protected Database, Chakra Max System can monitor and regulate all tasks executed

in the Database.

You can use the HA (High Availability) configuration to cope with possible physical or


10/107

software troubles. Gateway servers also supply the load balancing between servers to

ease the load by connecting users. Audit Servers and Gateway Servers are easy to expand

because they can be installed and run multiply when they have many protected

databases, and also support Hybrid mode that is run simultaneously.

Note: Hardware configurations for monitoring the Network Traffic are established

through the Port Mirroring function of the Network Switch equipment or Network

TAP equipment, whereas Software configurations are established using Software TAP.

It is recommended that you use the Port Mirroring method for this system, because

using Software TAP may interfere with the protected Database operation, and using

Network TAP equipment requires provisions against equipment malfunctions.

2.3.2 Chakra Max Manager

This software component for managers provides a series of Chakra Max system

management features for protected databases, users, various security policies, audit

history, and report inquiry.

2.3.3 Chakra Max Client

This software component is set up in user PCs to access the protected database or server

to perform a series of tasks. When users access the database, run SQLs, access through

server protocols such as telnet, and run server commands from their PCs, they are

transmitted to the Chakra Max Server. It also receives security issues and notifies them to

users as needed.

User authentication feature is provided by default. It also includes user interfaces for

approval of database tasks and transmission of various notices and messages.

2.4 Chakra Max System Operation Environment

For the successful Chakra Max system security functions, the following physical environment must

be prepared.


11/107

2.4.1 Network traffic monitoring (sniffing) environment for protected

database

Chakra Max monitors and controls every task on the protected databases by monitoring

the input/output network traffic of the protected databases.

For this purpose, you must configure physical input/output network traffic monitoring

(sniffing) environment. In general, one of the following methods is selected.

1) Network Switch Port Mirroring

The most general and recommended configuration method is to transmit network traffic,

which is input/output between a network switch device connected to database server and

a database switch port, to Chakra Max Server, with the mirroring setting. As shown in the

following figure, the network traffic (packets), which are input to/output from the

database port of the network switch, is mirrored and transmitted to the Chakra Max

Server.

[Figure 2-5] Environment Configuration using Network Switch Port Mirroring

In this case, both input traffic and output traffic at the port need to be transmitted. The

security function does not work if only the input traffic is transmitted to the Chakra Max

Server.

2) Using network TAP device

If the Network Switch Port Mirroring configuration in 1) is impossible, you can use a

network TAP device. This device, illustrated below, is a dedicated hardware component for


12/107

copying any network traffic. It has two communication ports and two ports to transmit

the copied network traffic (packets) with Tx (Outbound) and Rx (Inbound) separately.

As the copied packets are transmitted separately for Tx and Rx, the Chakra Max Server

needs two network interface cards.

UTP TAP device

Fiber TAP device

[Figure 2-6] TAP devices

As it is installed as shown in the following figure, the database server network can only

be disconnected temporarily.

[Figure 2-7] Environment configuration with a TAP device

Database service is temporarily stopped during the installation. If the TAP device has a

trouble, the Chakra Max security system functions not work. However, the database

service is not interrupted by any failure..


13/107

[Table 2-3] Using software TAP

When physical configuration is impossible

If the physical environment configuration described above is impossible, you can use

the Software TAP program instead. This program which is developed and supplied by

WareValley is installed in the protected database server and transmits all the input and

output communication packets to Chakra Max Server. As it is installed in a database

server in service and collects all communication packets, it could take up significant

many system resources such as CPU and memory. It is therefore not widely used.

2.4.2 Configuration of Chakra Max System Gateway Environment

To run Chakra Max in gateway mode, it is not required to construct a physical

environment, as in sniffing mode. You just need to ensure a network connection between

the protected database, the user, and Chakra Max Server.

Before installing Chakra Max Gateway, users had directly accessed the database to

perform tasks. After installing the gateway, however, such direct accesses from users must

be controlled and only allowed to access through the Chakra Max Gateway. For this

purpose, the following configuration is needed.

1) Installing Chakra Max Client

To access the protected database, users need to install the Chakra Max Client program on

their PC and receive authentication as a Chakra Max user. Once your user authentication

is successfully completed, you can access the database from the Chakra Max system

through the gateway.

However, as some users can try to access the database without installing the Client

program or with no authentication, you need to control accesses that do not pass

through the gateway.

2) Measures to control accesses that do not pass through the Chakra Max Gateway

There are four methods to control unauthorized accesses.

The first measure is to use the access control feature provided in Chakra Max system’s

sniffing mode. Enter the IP addresses or hostnames of users who are not permitted to

directly access the database and set a policy to let the Chakra Max Server, in sniffing

mode, block the forbidden users.


14/107

[Figure 2-8] Control of unauthorized access through the Chakra Max Sniffing feature

The second measure is to use the network firewall. This is usually recommended when the

protected database and the user are located in different network segments. Because users

need to access the database through the Chakra Max Gateway, the access control policy

is incorporated in the firewall using the IP addresses of user PCs.

[Figure 2-9] Control of unauthorized access through network firewall

The third measure is to use the IP control (filtering) feature of the database itself.

Although this is not widely used, it is useful for emergency responses to configuration

and database troubles that provide IP control features from Database Listener, such as

Oracle.

Finally, the fourth measure is to apply the IP control feature of a software firewall

provided from the operating system of the database server.


15/107

2.4.3 Configuration of Chakra Max Hybrid Environment

The most general operation mode for Chakra Max is hybrid mode. The hybrid mode

combines a sniffing mode for auditing and a gateway mode for control.

This configuration allows users who mainly perform nonstandard database tasks to carry

out more active security control in gateway mode while applying sniffing mode for

security audits without compromising performance for access to the Web/Application

server, which requires standard database tasks.

The above-mentioned nonstandard database tasks are mostly carried out by internal

developers, operators, or external outsourced personnel and they are generally performed

through direct access to the database. This existing environment needs to be changed so

that database tasks are processed only when they pass through the Chakra Max Gateway.

The following figure shows the conceptual diagram of the hybrid configuration. It

indicates that a Switch Port Mirroring or TAP device can be used as physical network

preparation for sniffing.

[Figure 2-10] Hybrid configuration of Chakra Max System

2.4.4 Chakra Max HA (High Availability) Configuration

Another issue that needs to be considered when configuring the Chakra Max system is

"How to continuously provide security services despite unavoidable system troubles". For

this purpose, Chakra Max allows HA configuration.

When operating in gateway mode, in which database interruption could occur in the

event of trouble, an Active-Standby or Active-Active configuration is possible. In the case

of Active-Standby, when service trouble on the active Primary Chakra Max Gateway


16/107

occurs, the Second Gateway on standby can take over the service. Once the trouble is

resolved, the Primary Gateway service is activated again.

In general, the Primary Gateway is placed at the main computer center and the Secondary

Gateway in the DR (Disaster Recovery) center.

Active-Active configuration is also possible. This configuration also allows the continued

service of security functions because another service can be activated even if one service

is in trouble. Additionally, this configuration provides a load balancing feature allowing

service loads to be distributed to multiple Chakra Max Gateways. This load balancing

feature of the Chakra Max system is provided by the Chakra Max Client and Server

themselves, without using separate network devices, such as an L4 switch.

[Figure 2-11] Normal operation status of the Active-Active configuration

[Figure 2-12] Operation in the event of a trouble in Active-Active configuration

For redundant sniffing configuration, Chakra Max Sniffing Server that is set up for audit

functions cannot collect audit data during service trouble. The Active-Standby

configuration is supported to prevent this problem. As shown in the figure below, when

trouble occurs in one Sniffing Server, the second server immediately starts to collect audit

data. For this configuration, the network traffic of the target database must be input to

both systems.


17/107

[Figure 2-13] Active-Standby operation of the Chakra Max Sniffing Servers

2.5 Checking Setup Environment

2.5.1 Guide to the setup of Linux CentOS 5.5 package

This section describes the process of setting up the Linux CentOS 5.5 64 bit in the Chakra Max

Appliance.

[Figure 2-14] Selecting the setup package

On the package selection screen of the setup process, choose “Customize now” as shown in

[Figure .

When the “Customize” screen appears, select only the packages shown in [Figure , [Figure , a


18/107

nd [Figure . Deselect all the other options in the setup process.

[Figure 2-15] Selecting the Desktop Environments package

In [Figure above, select only “GNOME Desktop Environment.”

[Figure 2-16] Selecting the Base System package

In [Figure above, select the "Base" package and “X Window System".


19/107

[Figure 2-17] Selecting the Languages package

In [Figure above, select the language to use.

For detailed information about the software applications used in connection with the OS durin

g the setup of Chakra Max Server, please refer to the setup manual supplied for each produc

t.

When the above package setup process is complete, the system reboots. After rebooting, log in as

the root user, and go through the basic setting process, including Firewall. In the basic setting

process, select “Enabled” or “Disabled” for Firewall as needed, but you must select “Disabled” for

SELinux.

In order to run the Chakra Max more safely, block unnecessary access ports. The ports required

for the Chakra Max operation include port “10054” for security administrators and client users,

port “1015” for Chakra Max Repository, port “8080” or “80” for online update or report features,

and the gateway port which is used in the gateway mode for accessing the DB through Chakra

Max. For the gateway port, it is recommended for security administrator to add a port each time a

protected database is added. The range of gateway ports used in Chakra Max is 10100 to 65535.

Please refer to [Table 2-2]

Ports can be blocked by utilizing Firewall (iptables) or TCP Wrapper. Do not use Firewall (iptables)

and TCP Wrapper simultaneously. It is recommended to use TCP Wrapper. Even though Firewall

offers more powerful security than TCP Wrapper, its excessivly strict security settings may interfere

with system operation.


20/107

2.5.2 Linux CentOS 6.4 Package Installation Guide

[Figure 2-18] Package Selection Screen

Select "Base System" from the left selection window of the Installation Package Selection Screen,

and select "Compatible Library" from the right selection window.

Click Next to continue with the installation procedures.

2.5.3 Other Environment Settings

2.5.3.1 Firewall (iptables) Setting

[Figure 2-19] Firewall setting screen setting screen shows the Firewall setting process. As shown in

the figure, select “Enabled” for Firewall and uncheck "SSH."


21/107

[Figure 2-19] Firewall setting screen

When the Firewall setting finishes, all ports except the ports required for the Linux OS are pr

ohibited and ssh access is also prohibited. Once the Firewall setting finishes, you must open t

he ports required for Chakra Max operation. To do this, follow the procedure below on the C

hakra Max system console. While logged in as root user, open the iptables file with vi, and a

dd the permitted ports listed below.

[Figure 2-20] Adding permitted IP

[Table 2-4] Permitted ports of Chakra Max

Port Description

1015 The port that Chakra Max Server and Chakra Max Manager use to

communicate with Chakra Max Repository.

10054 The port that Chakra Max Server uses to communicate with Chakra Max

Manager and Client.

10056 In HA (High Availability) configuration with two or more Chakra Max

servers, this port is used for communication between Chakra Max systems

for monitoring and policy synchronization. You don't have to permit this

port in Single configuration.

2222 This is the service port for health check of the Chakra Max Server.


22/107

8080 This is the Tomcat port for the Web service of Chakra Max system. If this

port used by Tomcat is changed to another port, you need to open the

changed port. Online update service for Chakra Max Manager and Client

programs, reporting, and e-mail approval services are provided through

the Web.

80 This is the port redirect for port 8080.

Gateway Port This is the gateway port for each protected database or server service

which is used by Chakra Max Server in gateway mode. It is determined

whenever a protected database is added. Its range is from 10100 to

65535.

[Figure 2-21] iptables Setup Example

Restarting iptables service

To apply the added ports for Chakra Max operation, stop the iptables service with the command

“service iptables stop”, and restart it with the command “service iptables start”.

2.5.3.2 TCP Wrapper Setting

Port blocking with TCP Wrapper for CentOS 5.5 is accomplished by stating the daemon (servicing

the port) to block in “/etc/hosts.deny.” If there are daemons servicing ports that are unnecessary

for Chakra Max operation, add the daemons here to prevent unnecessary ports from being

opened.


23/107

[Figure 2-22] Service setting example

* The above example shows the service setting to block telnet and ssh connections. For more

detailed description about the setting, please refer to the TCP Wrapper Guide.

The TCP port is regulated if TCP Wrapper is used, but the UDP port is not. Services providing

system information to external sources are stopped by using an additional 5353/UDP port. Run

“ntsysv” to cancel the “avahi-daemon” services. After this, “avahi-daemon” will not run even

though the system is rebooted.

[Figure 2-23] Running ntsysv

Stop “avahi-daemon” with the command "service".

[Figure 2-24] Stopping the avahi service


24/107

2.5.3.3 SELinux Setup

If Linux Security module - SELinux - is installed in the system where Chakra Max will be installed,

an error message is displayed indicating that the user is not permitted to access the necessary

library files and Chakra Max ceases operation.

[Figure 2-25] /etc/selinux/config File Edit

As shown in Figure 2-35, open the /etc/selinux/config file using an editor and change the settings

to SELINUX=disabled and reboot the system to stop using SELinux.

The OS setup and setting process of the Chakra Max system is complete.

2.5.3.4 How to change the delay allocation option

The ext4 file system can specify the delay allocation option to increase the disk performance. But

the delay allocation option in the ext4 file system have potential issues of the data loss, so this

setting must be set null. If the delay allocation option is activated when installing, the error occurs

and installing operation cannot be proceeded.

Following screen is one of the errors.

|#########################################################|

|# #|

|# Welcome to Chakra Max Server Configuration #|

|# #|

|# Copyright WareValley Co., Ltd #|

|# All rights reserved. #|

|# http://www.warevalley.com #|

|# #|

|#########################################################|

Installation of the System Database gets started.

Enter the path of the ChakraMax database. (Example: #/home/chakramax/wdb_rep) :/home/chak

ramax/wdb_rep

The path you entered is "/home/chakramax/wdb_rep". Is this correct? (Y/N) : Y


25/107

Errors can occur when following both conditions are met.

- The repository installation partition is the ext4.

- The delay allocation option is activated.

To deactivate the delay allocation option, set the setting of the partition in /etc/fstab setup file to

“nodelalloc”.

/dev/mapper/VolGroup-lv_root / ext4 defaults,nodelalloc 1 1

Restart the system after changing the setting.


26/107

3 Chakra Max License

3.1 Issuing Chakra Max License

To set up Chakra Max, you are required to issue a license. Licenses are divided into two types as

shown in the table below.

[Table 3-1] Types of License

Type Description

Workflow Edition The Chakra Max system can be run only in gateway mode.

Enterprise Edition The Chakra Max system can be run in any one of the gateway,

sniffing, and hybrid modes.

The following information is required for the issuance of license.

[Table 3-2] License information

Information Description

Customer name The name of the customer to whom the license is issued

Product version The version of the issued Chakra Max system

License type There are two types of license: Workflow Edition and Enterprise

Edition.

Number of managed

databases

This is the number of databases that can be protected by Chakra

Max.

When Chakra Max service operates, it can protect up to the number

of requested databases.

Number of controlled users This is the number of registered users who can access the

protected databases through Chakra Max Client.

Server type This is used for division of primary and secondary servers in HA

configuration.

3.2 Inputting and Viewing Chakra Max License

The license is provided as a USB dongle key or a license file containing the unique ID of the

system in which Chakra Max Server is installed, customer information, the maximum number of

protected databases, and the maximum number of users.

To input the license, connect the USB license key to the server port or register the license file

before installing Chakra Max Server. To register the license file, refer to [4.2.2 Inputting license

information].


27/107

3.3 Viewing Chakra Max License

You can view the input license information through maxsvr. As shown below, run the command

"maxsvr -v" to view the version and other license information.

[root@localhost bin]# ./maxsvr -v

11-22 11:18:27: 3 current work directory is /home/chakramax/bin

11-22 11:18:27: 3 Global Session connected to database.

----------------------------------------------------------------------

Chakra Max Server v2.0.1.20 (r11553 : /trunk/server)

Repository Version: 2.0.1.20

----------------------------------------------------------------------

License Type : Enterprise Edition

License Version : 2.0

Customer : warevalley

----------------------------------------------------------------------

Users : 100 ( 15 used)

Gateway DB : 0 ( 0 used)

Sniffing DB : 0 ( 1 used)

Hybrid DB : 20 ( 1 used)

Cyclone DB : 0 ( 0 used)

License Registered

----------------------------------------------------------------------

[Figure 3-2] Viewing license

3.4 Changing Chakra Max License

You can change the license information through maxsetup.

When you have an USB license, the license information would be recognized and updated when

you connect to the port of the target server.

When you have a license file, select "2. Update license" in "9. Manage license" and change the

license referring to [4.2.2 Inputting license information].

To check the changed license, run maxsetup, select "1. View license Information" in "9. Manage

license". The current license information is displayed as shown below.


28/107

|#########################################################|

|# #|


|# #|

|# Copyright c WareValley Co., Ltd #|



|# #|

|#########################################################|

1. Install Central Management Server (v)

2. Install Audit Server

3. Install Chakra Gateway Server

4. Install Central Management Standby Server

5. Install Audit Standby Server

6. Install Chakra Max Database

7. Install OzReport Server

8. Environment Settings

9. License management

10. Update management

0. Exit

Enter a number: 9

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|

1. View license information

2. Update license

0. Return to top menu


29/107

Enter a number: 1

[Figure 3-3] License Verification Step 1

Select the "1. View license Information" and check whether the registered license information is

displayed as follows.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|

Customer : Warevalley

----------------------------------------------------------------------

Users : 100 (Cur : 0)

Sniffing DB : 0 (Cur : 0)

Gateway DB : 0 (Cur : 0)

Hybrid DB : 50 (Cur : 0)

Cyclone DB : 0 (Cur : 0)

License Registered

----------------------------------------------------------------------

Finished.

Continue input? (Y/N):

[Figure 3-4] Confirm License Change


30/107

4 Chakra Max Server Setup

4.1 Setup preparations

4.1.1 Decompression of Distributed Files

The setup file for Chakra Max Server is distributed as a compressed file with the name

“chakramax_setup_version.tar.gz”. When you upload this file to the server and decompress it in the

setup directory, the following directories are created.

# ls

bin dbclient java_dbc mdb patchfiles setup tomcat

chakra-discovery java log ozreport temp chakrawac

[Figure 4-1] Composition of files

Upload the installation file in the /home/chakramax directory and decompress the file. The

following procedure is an example of decompressing an installation file.

# cd /home/chakramax/

# tar xvfz chakramax_setup_v2.0.X.X.tar.gz

[Figure 4-2] Decompress Chakra Max Package

After that, you can check the setup files in the setup directory.

# cd setup/

# ls

aksusbd-1.16-1.i386.rpm chakra_ad chakra_ad.sh

chakra_chad chakra_gw chakra_java

chakra_java.sh chakra_jdc chakra_jdc.sh

chakramax.crt chakramax.jks chakramax.key

chakra_maxras chakramaxrepconn.crt chakramaxrepconn.key

chakramax_schema.sql chakramax_schema_sqllog.sql chakra_maxsvr

chakra_rep chakra_schd chakra_service_template

chakra_sf chakra_tomcat change2jp.sql

getmaxhostid InstallMsgChnDBGate.txt InstallMsgEng.txt

InstallMsgJap.txt InstallMsgKor.txt lang

license_dbgate.txt license_en.txt license_jp.txt


31/107

license_ko.txt maxinstaller maxinstaller.md

maxsetup maxsetup.md maxtool

safe_sql.sql sshprx tzselect.sh

tzselect.sh.md update.yaml

#

[Figure 4-3] Setup Related File List

4.1.2 maxsetup program

Maxsetup is used to run the Chakra Max Server setup process and to change the environment

settings related to operation after setup.

When you run it, it automatically determines the setup of Chakra Max Server and runs in Wizard

Mode for setup or Menu Mode for changing the operation environment.

After decompressing the setup file (chakramax_setup_version.tar.gz) distributed from WareValley,

you can run maxsetup in the setup directory.

4.1.3 Running maxsetup

Check the execution privilege for the directory. To use the ssh monitoring function, you must have

the execution privilege for every directory to the path $CHAKRAMAX_HOME/bin. For example, if

$CHAKRAMAX_HOME is /home/chakramax, check if the root account has the execution right for

/home, /home/chakramax, and /home/chakramax/bin. If not, give these privileges.

Run the maxsetup program in the setup directory.

# cd setup/

# ./maxsetup

4.1.4 Language setting

Select a language to be used in the Chakra Max system.

Please choose the language you wish.

1: Korean

2: English

3: Japanese

4: Traditional Chinese


32/107

5: Simplified Chinese

0: Exit

Enter a number: 1

[Figure 4-4] Language Setup Screen

4.1.5 Initial Menu Screen Upon Initial Installation

The following installation menu is displayed during an initial installation.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|

1. Install Central Management Server






0. Exit

Enter a number :

[Figure 4-5] Initial Menu Screen Upon Initial Installation

4.1.6 Main Menu Screen Upon Additional Installation

During an additional installation, the following management menu is displayed along with the

installation menu.

|#########################################################|

|# #|


|# #|


33/107




|# #|

|#########################################################|


2. Install Audit Server (v)

3. Install Chakra Gateway Server (v)




7. Install OzReport Server (v)




0. Exit

Enter a number:

[Figure 4-6] Main Menu Screen Upon Additional Installation

Services already installed in the server, in which maxsetup is already executed, are marked with a

'v'. Selecting a service that is already installed will display the following message and return to the

initial menu.

Install Central Management Server

4.2 Install Central Management Server

4.2.1 Setup Menu Selection

Select [1. Install Central Management Server] as shown below.

|#########################################################|

|# #|


34/107


|# #|




|# #|

|#########################################################|







0. Exit

Enter a number: 1

[Figure 4-7] Main Menu Selection Screen

4.2.2 Inputting license information

Assign the file containing the license information issued by WareValley Co., Ltd.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|

Please enter your license file path (Default: ./license.dat): license.dat

[Figure 4-8] License Information Input Screen

4.2.3 Agreement with license policy

The maxsetup program checks if the license information matches the installation target equipment

information. To continue with the installation process, carefully read the license policy and select

"1: Yes" if you agree with the license policy.


35/107

WareValley Software Co., Ltd. "Chakra Max Server" License Agreement

IMPORTANT - READ BEFORE COPYING, INSTALLING, OR USING.

Prior to the installation and use of Chakra Max Server and its additional components (herein

referred to as "Software"), you are responsible for carefully reading and understanding the

contents of this Software product license agreement.

By installing or using the Software, you agree to the terms of this Agreement.

If you do not wish to so agree, do not install or use the Software.

(Omitted…)

WareValley Co., Ltd. Customer Information Center

Tel: (02) 743-4910 22F, Nuritkum Square Biz Tower, 1605, Sangam-dong, Mapo-gu, Seoul, Korea. Postal

Code: 121-795

Do you agree?

1: Yes 2: No

Enter a number. : 1

[Figure 4-9] License Policy Agreement Screen

4.2.4 Master IP Setup

Multiple Ethernet cards, each with a different IP address, can be installed in the Chakra Max

system. Among these Ethernet cards, the IP address used for communication between the server

module and the client or manager program is called the Master IP Address, and that Ethernet card

must be specified during the installation process.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|

Select the Master IP Address. The selected IP address will be used to access the client’s servers.

1 : eth0 192.168.13.2


36/107

Please select a number: 1

You selected the IP address "192.168.13.2". Is this correct? (Y/N): Y

[Figure 4-10] Master IP Setup Screen

4.2.5 System Database Generation Option Confirmation

Select System Database Generation Option.

Generate System Database? If it is already generated, enter N. (Y/N):

If installing the System Database prior to the Central Management Server, select 'Y' to proceed. If

the System Database is already installed, select 'N' to proceed.

4.2.6 System Database Installation

Setup the System Database information used for Chakra Max setup information management.

Enter the setup information to generate the System Database.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|

Starting System Database installation.

Please enter the ChakraMax Database path. (Example: #/home/chakramax/wdb_rep) :/home/chak

ramax/wdb_rep

The path entered is "/home/chakramax/wdb_rep". Is this correct?(Y/N): Y

[Figure 4-11] Repository setup step 1

Enter the IP address and Port information.

Select the Repository IP Address. The selected IP address will be used to access the System

Database.

1:eth0 192.168.13.2


37/107


You selected the IP address "192.168.13.2". Is this correct? (Y/N):

Please enter the Repository Server Port.. (Default:1015) Port:

You entered the port "1015". (Y/N):

[Figure 4-12] Repository Setup Step 2

Enter the database account information.

Please enter a Chakra Max database user. :chakramax

You have entered the user name "chakramax". Is this correct? (Y/N) :Y

Please enter the password for database user "chakramax". :

Please re-enter the password for database user "chakramax". :

Please enter the Chakra Max database name :chakramax

You have entered the database name "chakramax". Is this correct? (Y/N) :Y


The [chakramaxrep] database of Repository has been created. To delete the database, use the command

'monetdb stop chakramaxrep' and 'monetdb destroy -f chakramaxrep'. Press the Enter key.

[Figure 4-14] Repository Deletion Guide

If you have to delete a new account, you must exit maxsetup and manually delete the account

according to the above instructions.

Once the Chakra Max Repository is created, the schema is created.

Enter Y to start the creation. Views and tables used in Chakra Max are created and mandatory

setting information is added to the table, which takes some time.

Start schema generation. (Y/N) : Y

[Figure 4-15] Schema creation message

An error during the schema creation can cause malfunctions, which can result in a complex

process of finding the cause.

You must check the occurrence of error in detail.

4.2.7 Setting top administrator

Set the top administrator account for Chakra Max Manager. The password must satisfy the

following rule.

The account length must be 5 to 40 bytes.


38/107

Password rule: 8 to 16 characters, alphabetic + numeral + special characters (`~!@#$%^&*()-

_+=[]{}\|;:'",.<>/?)

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|

+

Please enter the Chakra Max administrator account.: chakramax

You have entered the account "chakramax". Is this correct? (Y/N): Y

Please enter the password for Chakra Max administrator:

Please re-enter the password for Chakra Max administrator:

[Figure 4-1] Top Administrator Account Information Input

Regulate the access IP address of Chakra Max administrator? (Y/N) Y

Please enter the IP address that will use the Chakra Max administrator account: 192.168.30.40

The IP address entered is "192.168.30.40". Is this correct?(Y/N): Y

[Figure 4-2] Entering the IP of the top administrator account

The administrator's access IP address can be regulated. Enter 'Y' to regulate, and 'N' to not

regulate.

Enter the Site information.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|


39/107

Chakra Max System manages protected Servers, Databases, and various other policies in groups

called Sites. One or more Sites must be registered. Please register the name of the initial Site.

The generated Site can be modified through the administrator program.

Site Name :SeoulBranch

Please enter a brief description for the Site "SeoulBranch".

Site Description :Site for SeoulBranch

[Figure 4-16] Site Information Input

4.2.8 Backup Path Setting

Set backup policy and back up operation logs and audit logs during Chakra Max operation. You

can set a specific directory of the system as backup path, and you can change the directory later

through the Chakra Max Manager.

Please enter the directory in which to save the backup files. Example:

/home/chakramax/log_backup Backup Directory: /home/chakramax/log_backup

[Figure 4-17] Setting backup path

When the above message appears, enter the path in which to store the backup files.

4.2.9 Chakra Max Web URL Setup

Chakra Max provides online Client & Manager updates. The URL entered becomes the basic

address of the update path.

Please enter the Chakra Max WEB URL (IP address or domain). (Default :

http://192.168.13.2/) :http://192.168.13.2/

[Figure 4-18] Chakra Max Web URL Setup

4.2.10 Oz Report Setup

Chakra Max analyzes the access packets to the protected database and server, collects data, and

leaves audit logs. In addition, it provides various audit reports based on the collected data. You

can receive these reports as e-mails on the specified date through Oz Scheduler. You can set up

both Oz Report and Oz Scheduler from the Oz Report setup menu.

|#########################################################|

|# #|


40/107


|# #|




|# #|

|#########################################################|

Do you want to install OZ Report? (Y/N) : Y

The OzReport install path is "$CHAKRAMAX_HOME/tomcat/webapps/ozreport".

Are you setting the SMTP connecting information? (Y/N) :Y

The Oz Scheduler install path is "$CHAKRAMAX_HOME/ozscheduler".

Enter the address of the SMTP server for Scheduler. Ex) mail.warevalley.com

SMTP Mail Server :mail.warevalley.com

The address you entered is "mail.warevalley.com". Is this correct? (Y/N): Y

Please enter the SMTP server port to be used by Scheduler Ex) 25

SMTP Mail Port :25

The address you entered is "25". Is this correct? (Y/N): Y

[Figure 4-19] Oz Report Setup

Oz Report is set up in the specified directory set up in Chakra Max. It is displayed on the screen

during the setup process. The Report path is $CHAKRAMAX_HOME/tomcat/webapps/ozreport and

the Scheduler path is $CHAKRAMAX_HOME/ozscheduler.

Setting up the Scheduler allows you to receive reports via e-mail at the specified time. The SMTP

server address and port must be assigned during installation for the relevant function to operate

normally.

Enter the SMTP user account for Scheduler. Ex) [email protected]

SMTP User Account: [email protected]

The mail address you entered is "[email protected]". Is this correct? (Y/N) : Y

Enter the SMTP user password for Scheduler:

Re-Enter the SMTP user password for Scheduler:

Please enter the SMTP sender mail address to be used by Scheduler. Ex)

[email protected]

SMTP Mail Address :[email protected]

The sender mail address you entered is "[email protected]". Is this correct?(Y/N): Y

[Figure 4-3] Oz Report Setup Step 2


41/107

4.2.11 Database Reboot

When a database is installed, the database will restart at the last step in the installation procedure.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|

If it is the initial installation of the Database, it must be rebooted for stable operation.

Stopping System Database...

Ending CHAKRA Rep Server service: stopping database 'chakramax'... done

Database successfully stopped.

Starting System Database...

Starting CHAKRA REP Server Service: starting database 'chakramax'... done

Database reboot successful.

[Figure 4-20] Database Reboot Message

4.2.12 Completion of Setup Process

When the setup process is successfully completed, the following message appears.

Press Enter to return to the initial menu.

|#########################################################|

|# #|


|# #|


42/107




|# #|

|#########################################################|

The installation process was successful. Press Enter to return to the initial menu.

[Figure 4-21] Conclusion of the setup process of Chakra Max Server

The main menu is displayed when Enter is pressed, as shown below.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|











0. Exit

Enter a number:

[Figure 4-22] Main Menu After Installation

(v) means menus that are already installed; additional services can be installed.


43/107

4.3 Install Audit Server

4.3.1 Select Install Menu

Select [2. Install Audit Server].

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|







0. Exit

Enter a number: 2


4.3.2 Master IP Address Setup


system. Among these Ethernet cards, the IP address used for communication between the server

module and the client or manager program is called the Master IP Address, and the relevant

Ethernet card must be specified during the installation process.

|#########################################################|

|# #|


|# #|




44/107


|# #|

|#########################################################|


1:eth0 192.168.13.13



[Figure 4-24] Chakra Max Server IP Setup

4.3.3 System Database Access Information Input

Enter the System Database IP information and Port information. The default service port is 1015.

Press Enter to use the default port without changing its value.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|

Starting System Database Repository setup.

Please enter the Repository Server IP Address. IP Address: 192.168.13.2


Please enter the Repository Server Port. (Default:1015) Port:


[Figure 4-25] System Database Access Information Input Step 1

Please enter a Chakra Max database user: chakramax

You have entered the user name "chakramax". Is this correct? (Y/N): Y

Please enter the password for database user "chakramax":

Please re-enter the password for database user "chakramax":

Please enter the Chakra Max database name: chakramax

You have entered the database name "chakramax". Is this correct? (Y/N): Y



45/107

4.3.4 Audit Log Database Installation Option Selection

Select Audit Log Database Generation Option.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|

Generate Audit Log Database? If selecting a database that already exists, enter N. (Y/N):

[Figure 4-27] Audit Log Database Installation Option Selection Screen

If installing an additional Audit Log Database in the Audit Server, select 'Y' to proceed. If using an

Audit Log Database that is already installed, select 'N' to proceed.

4.3.5 Audit Log Database Installation

Setup the Audit Log Database information used by Chakra Max to store Audit logs.

Enter the Database installation path.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|

Starting Audit Log Database Installation.

Please enter the ChakraMax Database path. (Example: #/home/chakramax/wdb_rep) :

/home/chakramax/wdb_rep




46/107

Enter the Database IP & Port.

Select the Repository IP Address. The selected IP address will be used to access the Audit Log

Database.

1:eth0 192.168.13.13














[chakramax] database has been generated in the Repository. In order to delete the database, use

the 'monetdb stop chakramax' and 'monetdb destroy -f chakramax' commands. Press Enter.




Once the Chakra Max Repository is generated, the schema generation process begins.

Select Y to begin the process. Views and tables used in Chakra Max are created and essential

setup information is added to the table, which may take some time.

Start schema generation. (Y/N): Y

[Figure 4-32] Schema Generation Message

Errors that occur while generating the Schema may have influence on the system operation

and thus cause system malfunctions, and may require complex causal investigations.

The cause of the error must be checked in detail.


47/107

Backup policies can be configured during Chakra Max operation and Audit Logs can be backed up

as well.

Setting up a specific system directory allows the user to assign a backup path, then the relevant

directory can be reassigned through the Chakra Max manager screen after installation.

The backup path is not setup in the Repository. Please enter the directory in which the backup

files will be saved. Ex)/home/chakramax/log_backup Backup Directory :

/home/chakramax/log_backup

[Figure 4-33] Backup Path Assignment

When the above message appears, enter the path in which the backup files will be saved.

4.3.6 Finish Setup

When the installation process is successfully completed, the following message appears on the

screen. Press Enter to return to the initial menu.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|


[Figure 4-34] Chakra Max Server Installation Complete


|#########################################################|

|# #|


|# #|




48/107


|# #|

|#########################################################|











0. Exit

Enter a number:

[Figure 4-35] Main Menu Screen After Installation


4.4 Install Chakra Gateway Server


Select [3. Install Chakra Gateway Server] as shown below.

|#########################################################|

|# #|


|# #|




|# #|


49/107

|#########################################################|







0. Exit

Enter a number: 3




system. Among them, the IP address used by the server module for communication with the Client

or Manager program is called Master IP Address. You must specify this Ethernet card during the

setup process.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|


1:eth0 192.168.13.13








50/107

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|














4.4.4 Finish Setup


screen.


|#########################################################|

|# #|


|# #|




|# #|


51/107

|#########################################################|




|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|











0. Exit

Enter a number:

[Figure 4-41] Main Menu Screen After Installation



52/107

4.5 Install Central Management Standby Server


Select [4. Install Central Management Standby Server].

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|







0. Exit

Enter a number: 4

[Figure 4-42] Setup Menu Selection Screen

4.5.2 License information input

Assign the file path where license information is saved.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|


53/107

Please enter the license file path (Default: ./license.dat) :

[Figure 4-43] License File Path Input Screen

4.5.3 License Policy Agreement

The maxsetup program checks if the license information matches the installation target equipment

information. To continue with the installation process, carefully read the license policy and select

"1: Yes" if you agree to the license policy.

WareValley Software Co., Ltd. "Chakra Max Server" License Agreement

IMPORTANT - READ THE AGREEMENT PRIOR TO COPYING, INSTALLING, OR USING THE

SOFTWARE.

Prior to the installation and use of Chakra Max Server and its additional components (herein

referred to as "Software"), you are responsible for carefully reading and understanding the

contents of this Software product license agreement. By installing or using this Software, you

agree to the terms and conditions of this product's license agreement. If you do not wish to

agree, you cannot install or use this software.

(Omitted...)

WareValley Co., Ltd. Customer Information Center / Tel: (02) 743-4910 / Address: 22F, Nuritkum

Square Biz Tower, 1605 Sangam-dong, Mapo-gu, Seoul Metropolitan City / Postal Code: 121-795

Do you agree?

1: Yes 2: No


[Figure 4-44] License Policy Agreement Screen





setup process.

|#########################################################|

|# #|


54/107


|# #|




|# #|

|#########################################################|


1: eth1 192.168.100.191

2: eth0 192.168.100.165



[Figure 4-45] Master IP Selection Screen

4.5.5 System Database Information Input



|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|











55/107





4.5.6 Finish Setup


screen.


|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|




|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|




4. Install Central Management Standby Server (v)


56/107







0. Exit

Enter a number:

[Figure 4-49] Main Menu Screen


4.6 System Database Installation


Select [6. Install Chakra Max Database] as shown below.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|







0. Exit


57/107

Enter a number: 5


Select [1. Install Chakra Max Database] from the bottom menu screen, as shown below.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|


2. Install Audit Log Database


Enter a number: 1

[Figure 4-51] Setup Menu Selection Bottom Menu

4.6.2 Inputting license information

Specify the file containing the license information issued by WareValley.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|

Please enter your license file path (Default: ./license.dat) : license.dat

[Figure 4-52] Inputting license information Screen


58/107





setup process.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|


1:eth0 192.168.13.13




4.6.4 System Database Installation

Setup the System Database information used for Chakra Max setup information management.

Enter the setup information to generate the System Database.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|

Starting System Database installation.


59/107

Please enter the ChakraMax Database path. (Example: #/home/chakramax/wdb_rep): /home/chak

ramax/wdb_rep



Enter the IP address and Port information.

Select the Repository IP Address. The selected IP address will be used to access the System

Database.

1:eth0 192.168.13.2


You selected the IP address "192.168.13.2". Is this correct? (Y/N):





Please enter a Chakra Max database user:chakramax







The [chakramaxrep] database has been generated in the Repository. In order to delete the

database, use the 'monetdb stop chakramaxrep' and 'monetdb destroy -f chakramaxrep'

commands. Press Enter.








60/107



Errors that occur while generating the Schema may cause system malfunctions, and may

require complex causal investigations.


4.6.5 Backup Path Setup

Backup policies can be configured during Chakra Max operation and operation logs and audit logs

can be backed up as well. Setting up a specific system directory allows the user to assign a

backup path, then the relevant directory can be reassigned through the Chakra Max manager

screen after installation.

Please enter the directory in which the backup files will be saved.

Ex)/home/chakramax/log_backup Backup Directory :/home/chakramax/log_backup

[Figure 4-59] Backup Path Setup Screen


If a database is installed, it must be rebooted for the final stage of installation.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|





61/107






4.6.7 Finish Installation


screen.


|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|


[Figure 4-61] Setup Complete Message


|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|



62/107





6. Install Chakra Max Database (v)





0. Exit

Enter a number:



4.7 Install Audit Log Database

Select [6. Install Chakra Max Database].

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|








63/107

0. Exit

Enter a number: 5



64/107

Select [1. Install Chakra Max Database] from the bottom menu screen, as shown below.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|




Enter a number: 2

[Figure 4-64] Setup Menu Selection Bottom Menu





setup process.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|


1:eth0 192.168.13.13





65/107


Enter the System Database IP information and Port information.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|


Please enter the Repository Server IP Address. IP Address :192.168.13.2












4.7.3 Audit Log Database Installation

Setup the Audit Log Database information used by Chakra Max for managing Audit logs.

Enter the Database installation path.

|#########################################################|

|# #|


|# #|


66/107




|# #|

|#########################################################|

Starting Audit Log Database Installation.

Please enter the ChakraMax Database path. (Example: #/home/chakramax/wdb_rep) :

/home/chakramax/wdb_rep

The path entered is "/home/chakramax/wdb_rep". Is this correct?(Y/N) :Y


Enter the Database IP & Port.

Select the Repository IP Address. The selected IP address will be used to access the Audit Log

Database.

1:eth0 192.168.13.13














The [chakramax] database has been generated in the Repository. In order to delete the database,

use the 'monetdb stop chakramax' and 'monetdb destroy -f chakramax' commands. Press Enter.





67/107






Errors that occur while generating the Schema may have influence on the system operation

and thus cause system malfunctions, and may require complex causal investigations.


Backup policies can be configured during Chakra Max operation and operation logs and audit logs

can be backed up as well. Setting up a specific system directory allows the user to assign a

backup path, then the relevant directory can be reassigned through the Chakra Max manager

screen after installation.

The backup path is not setup in the Repository. Please enter the directory in which the backup

files will be saved. Ex)/home/chakramax/log_backup Backup Directory :

/home/chakramax/log_backup

[Figure 4-73] Backup Path Assignment

When the above message appears, enter the path in which the backup files will be saved.


If a database is installed, it must be rebooted for the final stage of installation.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|



68/107








4.7.5 Finish Installation


screen.


|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|




|#########################################################|

|# #|


|# #|


69/107




|# #|

|#########################################################|











0. Exit

Enter a number:


4.8 Install Audit Standby Server


Select [5. Install Audit Standby Server].

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|


70/107







0. Exit

Enter a number: 5






setup process.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|


1 : eth1 192.168.100.191

2 : eth0 192.168.100.165



[Figure 4-78] Master IP Selection Screen

4.8.3 System Database Information Input



|#########################################################|


71/107

|# #|


|# #|




|# #|

|#########################################################|


Please enter the Repository Server IP Address. IP Address:192.168.13.2












4.8.4 Selecting the Master Audit Server

A screen is displayed to select a Audit Server that will act as the Master server.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|

Please select a Audit Server that will act as the Master server. The selected Audit Server will be

setup as the Master server of Audit Standby Server.


72/107

1: Audit Server(192.168.13.13)


The Audit Server address selected is "192.168.13.13". Is this correct?(Y/N): Y

1: Audit Server(192.168.13.13) in the list is the server installed by Audit Server. Enter the number of

that Audit Server.

When a confirmation message appears after entering the number, enter Y.

4.8.5 Finish Setup


screen.


|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|




|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|



73/107




5. Install Audit Standby Server (v)






0. Exit

Enter a number:



4.9 Configure System Database as a Separate Mechanism

[Figure 4-83] Configuring System Database as a Separate Mechanism

Chakra Max Server is capable of setting up a Chakra Max Repository in a separate server, as

shown in the image.

In order to setup a separate Repository, install Chakra Max Server and the Repository Server using

a Primary license. Then, the Chakra Max Server settings and Chakra Max Repository settings must

be changed. In order to minimize any confusion during the installation process, the Chakra Max

Server's IP address is set to 192.168.39.1, and the Chakra Max Repository's IP address is set to

192.168.39.2.


74/107

4.9.1 System Database Setup in a Separate Server

First of all, refer to "4.6 System Database Installation" to install the System Database in a separate

server.

4.9.2 Install Central Management Server

In order to separately configure Chakra Max Repository, refer to "4.2 Install Central Management

Server" to install the Central Management Server using a Primary License.

If configuring the System Database in a separate server, System Database will not be installed in

the Central Management Server during its installation. Enter "N" at the prompt, "Generate System

Database? If it is already generated, enter N. (Y/N):", and enter the access information.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|

Generate System Database? If it is already generated, enter N. (Y/N): N

[Figure 4-84] Confirm System Database Generation

In "4.9.1 System Database Setup in a Separate Server", enter the access information of the System

Database installed in a separate machine.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|


75/107

Enter the Repository administrator account information.




Please enter the Repository Server Port. (Default:1015) Port:1015

You've entered port "1015". (Y/N): Y









4.9.3 Chakra Max Server Startup

If Chakra Max Repository started up normally, connect to Chakra Max Server through ssh and

startup all necessary services.

[root@localhost bin]# service chakra_max start


76/107

4.10 Separate Repository Configuration in Central Management Se

rver's Duplex Configuration

[Figure 4-87] Central Management Server's Duplex Configuration Upon Separate System

Database Configuration

As shown in the image, Central Management Server is capable of establishing a duplex

configuration after setting up the System Database in a separate server. Refer to "4.9 Configuring

the System Database as a Separate Mechanism" and install the System Database and Central

Management Server. Then, install the Central Management Standby Server to establish a duplex

configuration for the Central Management Server. For convenience, the Central Management

Server IP address is set to 192.168.39.1, and the Central Management Standby Server IP address is

set to 192.168.39.2. Finally, the IP address of the Secondary Chakra Max Server is set to

192.168.39.3.

4.10.1 Install Central Management Standby Server

After completing the separate configuration of the Central Management Server and System

Database by referring to "4.9 Configuring the System Database as a Separate Mechanism", refer to

"4.5 Install Central Management Standby Server" to install the Central Management Standby

Server.


77/107

4.10.2 Secondary Chakra Max Server Startup

After Central Management Standby Server installation is complete, connect to the Central

Management Standby Server through ssh to execute startup by using the following service

command.

[root@localhost bin]# service chakra_max start

4.11 Additional Configurations for Repository Dualization using Lif

eKeeper

4.11.1 Add Standby WDB Information in max_engine Table

After setting up WDB dualization using LifeKeeper, additional manual configurations must be

made as shown below.

[Figure 4-88] Central Management Server's Duplex Configuration Upon Separate System

Database Configuration

The above configuration is a manual entry of the WDB information that will operate as a Standby

WDB. When entering the above information, enter the Machine Key ID of the Standby WDB

(refer to the red circle above). Enter the remaining information as shown in the example above.

The above machine_key_id can be verified using the following query.

SELECT key_id from max_machine WHERE ip_address=’{ IP of the machine where Standby WDB

is installed}’;

Information on Standby WDB server


78/107

4.11.2 Manual Tasks for Repository Setup

During installing the Log DB in the installing procedure of Chakra server (Snipping server), input

[ChakraMax database path]. In [ChakraMax database path], specify the path different from the

directory to sync with LifeKeeper. Then install it that Chakra server could move only the data

directory (bat, box, sql_logs) to be redundant to the directory to sync with LifeKeeper.

4.11.2.1 Manual Tasks in the Primary Server

Stop Repository service.

# service chakra_rep stop

Go to the installed database path.

# cd {ChakraMax Database Path}/{DB Name}/

Go to the directory that syncs the data directory through LifeKeeper.

# mv bat box sql_logs {Directory synced using LifeKeeper}/

Create a link file regarding the actual data directory in the database path.

# ln -s {Directory synced using LifeKeeper}/bat ./bat

# ln -s {Directory synced using LifeKeeper}/box ./box

# ln -s {Directory synced using LifeKeeper}/sql_logs ./sql_logs

Compress the database path.

# cd {ChakraMax Database Path}

# tar cfz db.tgz ./

Start Repository Service

# service chakra_rep start

4.11.2.2 Manual Tasks in the Standby Server

Use the command below to create a compressed {ChakraMax Database Path} file of the Primary

server in the Standby Server.

# mkdir -p {ChakraMax Database Path}

# scp root@{Primary Server}:{ChakraMax Database Path}/db.tgz ./

# tar xfz db.tgz

4.11.2.3 Installation Setup Diagram of WDB Dualization Using LifeKeeper


79/107

The following is the setup diagram after installation according to the example shown above.

[Figure 4-89] Installation Setup Diagram of WDB Dualization Using LifeKeeper

A symbolic link file exists in {ChakraMax database path}, and the actual directory is in the directory

path to be copied to LifeKeeper.

Note: The reason to do is that temporary files to be managed internally are also to be copied

when the directory path as an object is copied to LifeKeeper.

4.11.3 Copy WDB Startup Script

Copy the /etc/init.d/chakra_rep of the machine where the Primary WDB is installed to /etc/init.d/

of the server where the Standby WDB is installed.

Caution! The two machines in which dual WDB configuration will be established must have dual

configuration established for identical partitions.

4.12 Errors in the Chakra Max Server Setup Process and Explana

tions

This section describes the examples of errors that can occur in the setup process.


80/107

4.12.1 Unsupported language setting error


1: Korean

2: English

3: Japanese


0: Exit

Enter a number: 5


1: Korean

2: English

3: Japanese


5: Simplified Chinese

0: Exit

Enter a number :

[Figure 4-90] Language selection error of Chakra Max

Chakra Max currently supports Korean, English, and Japanese, and Traditional Chinese, Simplified

Chinese. Select a desired language from "1: Korean", "2: English", "3: Japanese", and "4: Traditional

Chinese", “5: Simplified Chinese” in the language selection step.

4.12.2 Database user password input error

During the Chakra Max setup process, you must enter the database user password twice. If the

two passwords are not identical, the password input menu appears again. You can solve this

problem by entering the same password twice.

Please enter the Chakra Max database user: chakramax

You have entered the user name "chakramax". Is this correct? (Y/N) : Y





[Figure 4-91] Database User Password Assignment Error


81/107

4.12.3 IP Address Input Error

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|

Select a Master IP Address. The selected IP address will be used to access the client's servers.

1 : eth1 192.168.100.191

2 : eth0 192.168.100.165


Data entered incorrectly.

[Figure 4-92] Master IP specification error

In the Master IP input step, the IPs assigned to the systems are displayed, and you must enter the

number of the IP that you want. The above error message appears if you enter an IP number that

does not exist. This problem is solved by entering a number of an IP that is assigned to a system.

4.12.4 Main Menu Selection Error

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|








82/107

0. Exit

Enter a number: 6

Data entered incorrectly.

[Figure 4-93] Main Menu Selection Error

If a number is not included as an installation target during the installation process, the error

message "Data entered incorrectly." appears. A number included as an installation target must be

entered for installation.

4.12.5 Duplicate Error

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|











0. Exit

Enter a number: 1

The selected service is already installed.

[Figure 4-94] Duplicate error


83/107

If a setup menu that is already installed is selected in the initial menu screen, the error message

"The selected service is already installed." appears. A setup menu that is not already installed must

be selected for additional installation.

4.12.6 Installation Not Possible Error

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|











0. Exit

Enter a number: 4

The selected service cannot be installed in the Central Management Server.

[Figure 4-95] Installation Not Possible Error

If "4. Central Management Standby Server" is selected for a machine that already has the Central

Management Server installed, the error message "The selected service cannot be installed in the

Central Management Server." appears, and the main menu is displayed.

Please refer to "4.15 Restrictions" for more detailed information regarding Central Management

Service installation.


84/107

4.13 Checking the Result of Chakra Max Server Setup

When the setup process finishes successfully, conclude the setup by checking the normal program

startup.

Run maxsetup to check if the normal running environment has been configured.

As the setup is complete, maxsetup automatically runs in menu mode.


1: Korean

2: English

3: Japanese


0: Exit

Enter a number :1

[Figure 4-96] Language selection

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|










85/107



0. Exit

Enter a number : 7

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|

1. Master IP address setup

2. Update System Database Information

3. Update Audit Log Database

4. Top administrator setup

5. Communication port setup

6. CGW shared memory address setup

7. Local Logging Agent setup


Enter a number :

[Figure 4-97] Menu of maxsetup

Chakra Max Server is registered as a service of the Linux system. Use the "service" command to

start or stop it.

If setup has been completed normally, you can check the Chakra Max start and stop scripts in the

directory "/etc/rc.d/init.d/" as shown below.

# ls /etc/rc.d/init.d/chakra_*

/etc/rc.d/init.d/chakra_ad /etc/rc.d/init.d/chakra_ad.sh

/etc/rc.d/init.d/chakra_chad /etc/rc.d/init.d/chakra_gw

/etc/rc.d/init.d/chakra_java /etc/rc.d/init.d/chakra_java.sh


86/107

/etc/rc.d/init.d/chakra_jdc /etc/rc.d/init.d/chakra_jdc.sh

/etc/rc.d/init.d/chakra_max /etc/rc.d/init.d/chakra_maxras

/etc/rc.d/init.d/chakra_maxsvr /etc/rc.d/init.d/chakra_rep

/etc/rc.d/init.d/chakra_schd /etc/rc.d/init.d/chakra_sf

/etc/rc.d/init.d/chakra_tomcat /etc/rc.d/init.d/chakra_wac

[Figure 4-101] Checking the Chakra Max starting script

Check to see if the Chakra Max Server starts and stops normally by referring to [Chapter 5


87/107

Operation of Chakra Max Server].

[Note] If you wish to have Chakra and Chakra Repository (WDB) start up when the server is

rebooted, execute the command shown below.

/sbin/chkconfig chakra_rep on

/sbin/chkconfig chakra_max on

4.14 Removing Chakra Max Server

You can remove Chakra Max Server by deleting the directory in which Chakra Max has been set

up and the service scripts in "/etc/init.d/".

# cd $CHAKRAMAX_HOME

#ls

bin dbclient dump_gw java mdb patchfiles temp

chakramax_repository dump chakrawac dump_sf log ozreport setup

tomcat

#rm –rf bin dbclient dump_gw java patchfiles temp dump dump_sf log

ozreport setup tomcat

[Figure 4-98] Removing Chakra Max Setup Files

It is recommended that you backup the mdb directory and chakrawac directory which are the

Chakra Max Repository and the database directory which is set in installation. (All logs & data will

be deleted upon deletion.)

After removing the directory in which Chakra Max is setup using the rm command, delete the

service scripts registered in the system.

# ls /etc/init.d/chakra_*

/etc/rc.d/init.d/chakra_chad /etc/rc.d/init.d/chakra_maxras

/etc/rc.d/init.d/chakra_gw /etc/rc.d/init.d/chakra_schd

/etc/rc.d/init.d/chakra_java /etc/rc.d/init.d/chakra_sf

/etc/rc.d/init.d/chakra_max /etc/rc.d/init.d/chakra_tomcat

/etc/rc.d/init.d/chakra_maxsvr

# rm -rf /etc/init.d/chakra_*

[Figure 4-99] Removing the Chakra Max starting script

4.15 Restrictions

Chakra Max services can be setup in individual machines for purposes of Central Management


88/107

service configuration. However, installation of the following configurations is restricted for

purposes of repair and maintenance.

The following error message appears when installing an Audit Log Database in the Central

Management Standby Server.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|




Enter a number: 2

Audit Log Database cannot be installed in the Central Management Standby Server.

[Figure 4-100] Error Message When Installing an Audit Log Database in the CM Standby

Server

OZReport Server can be installed only in the Central Management Server.

The following error message appears when installing OZReport in servers other than the Central

Management Server.

|#########################################################|

|# #|


|# #|




|# #|

|#########################################################|




4. Install Central Management Standby Server (v)


89/107







0. Exit

Enter a number: 6

The selected service can be installed only in the Central Management Server.

[Figure 4-101] Error Message When Installing OZReport

The above error message appears when selecting "7. Install OzReport Server" in the Central

Management Server.


90/107

5 Operation of Chakra Max Server

5.1 Checking Running Environment

Before running the Chakra Max Server, you must check the following.

Check available system disk capacity

Use the df command to check the available disk space of the system in which Chakra M

ax runs.

At least 500 gigabytes or 100 gigabytes is recommended as the available disk space.

# df –h

Filesystem Size Used Avail Use% Mounted on

/dev/hda2 893G 214G 633G 26% /

/dev/hda1 99M 13M 82M 13% /boot

tmpfs 3.9G 0 3.9G 0% /dev/shm

[Figure 5-1] Checking available disc space

Check the inflow of sniffing packets

When sniffing the packets input to/output from the protected database, make sure that t

he sniffed packets normally flow into the Chakra Max system. Use the tcpdump command

for this.

The tcpdump command displays on the screen the packets input through the specified ne

twork card.

As command options, enter the network card name set for the inflow of sniffing packets

and the IP address of the protected database. The following figure shows the packet inflo

w test result using tcpdump. If no sniffing packet flows in, you must check the problem

of the environment for sniffing.


91/107

[Figure 5-2] Checking the flow of sniffing packets

5.2 Run Chakra Max Repository

The Chakra Max Repository can be executed by starting up chakra_rep through a service

command.

[root@localhost chakramax]# service chakra_rep start

Starting CHAKRA REP Server services: starting database 'chakramax_repository'... done

[root@localhost chakramax]# ps -ef | grep mdb

root 2515 2510 0 15:05 ? 00:00:00 /home/chakramax/mdb/bin/mserver5 --set

gdk_dbfarm /home/chakramax/chakramax_farm --dbname= chakramax_repository --set

merovingian_uri mapi:monetdb://localhost.localdomain:1015/ chakramax_repository --set

mapi_open false --set mapi_port 0 --set mapi_usock /home/chakramax/chakramax_farm/

chakramax_repository /.mapi.sock --set monet_vault_key /home/chakramax/chakramax_farm/

chakramax_repository /.vaultkey --set gdk_nr_threads 1 --set max_clients 64 --set sql_optimizer

default_pipe --set monet_daemon yes

root 2524 2283 0 15:08 pts/1 00:00:00 grep mdb

[Figure 5-3] Run Chakra Max Repository

5.3 Running Chakra Max Server

You can run the Chakra Max Server by using the service command to start “chakra_max”.

# service chakra_max start

Chakra_max starts the maxsvr process, which automatically runs the processes needed for security


92/107

functions.

If configured with Central Management services, startup and termination of services are executed

through chakra_max. The /etc/init.d/chakra_max script is created to fit the services installed

through a setup program in relevant servers.

[root@localhost chakramax]# service chakra_max start

Chakra Max Server services starting:

Starting CHAKRA Gateway Server Service:

Starting SSH:

Starting CHAKRA Sniff Server Service:

Starting Chakra Chad Daemon Service:

Starting CHAKRA Tomcat Service: Using CATALINA_BASE: /home/chakramax/tomcat

Using CATALINA_HOME: /home/chakramax/tomcat

Using CATALINA_TMPDIR: /home/chakramax/tomcat/temp

Using JRE_HOME: /home/chakramax/java

Starting CHAKRA Java Server:

> Java Engine

Starting Oz Scheduler service:

Starting CHAKRA Rastracker Daemon Service:

[root@localhost chakramax]# ps -ef | grep runserver

root 27818 1 0 20:07 pts/1 00:00:00 ./runserver -r maxsvr

root 27821 1 0 20:07 pts/1 00:00:00 ./runserver -r cgw_gw -p -C

root 27823 1 0 20:07 pts/1 00:00:00 ./runserver -r sshprx

root 27824 1 0 20:07 pts/1 00:00:00 ./runserver -r cgw_sf -p -C -X

root 27828 1 0 20:07 pts/1 00:00:00 ./runserver -r chad -p -C -X

root 28192 1 0 20:07 pts/1 00:00:00 ./runserver -r rastracker

root 30437 3197 0 20:07 pts/1 00:00:00 grep runserver


93/107

[root@localhost chakramax]# ps -ef | grep tomcat

root 23416 1 0 Jan11 ? 00:00:08 /home/chakramax/mkkimtest/java//bin/java

-Djava.util.logging.config.file=/home/chakramax/mkkimtest/tomcat/conf/logging.properties -

Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -

Djava.endorsed.dirs=/home/chakramax/mkkimtest/tomcat/endorsed -

classpath :/home/chakramax/mkkimtest/tomcat/bin/bootstrap.jar -

Dcatalina.base=/home/chakramax/mkkimtest/tomcat -

Dcatalina.home=/home/chakramax/mkkimtest/tomcat -

Djava.io.tmpdir=/home/chakramax/mkkimtest/tomcat/temp org.apache.catalina.startup.Bootstrap

start

root 24823 24339 0 11:16 pts/5 00:00:00 grep tomcat

[root@localhost chakramax]# ps -ef | grep OZ

root 24849 24339 0 11:16 pts/5 00:00:00 grep OZ

root 28225 28193 0 2011 ? 00:00:11 /home/chakramax/mkkimtest/java/bin/java -

cp ..//conf:..//lib/ozsfw51.jar:..//lib/jcert.jar:..//lib/jnet.jar:..//lib/jsse.jar:..//lib/log4j.jar:..//lib/crimson.j

ar:..//lib/parser.jar:..//lib/xerces.jar:..//lib/mail.jar:..//lib/activation.jar:..//lib/OZUSLClientSession.jar:..//

lib/OZUSLServerDES128.jar:..//lib/icu4j_2_8.jar:..//lib/ozviewer_lib.jar:..//lib/ozrresource.jar:..//lib/poi-

scratchpad-

3.0.1.jar:..//lib/uk.co.mmscomputing.imageio.tiff.jar:..//lib/ozscheduler_ude.jar:..//lib/OZMaxSchedul

er.jar:..//lib/ozsfw-5.1-20110719.jar:..//lib/ant_parser-1.1.jar:..//lib/chakra-core-1.0.0-

SNAPSHOT.jar:..//lib/chakra-function-1.0.0-SNAPSHOT.jar:..//lib/chakra-jnilib-1.0.0-

SNAPSHOT.jar:..//lib/chakra-ozapi-3.1.2_20110720.jar:..//lib/commons-collections-

3.1.jar:..//lib/commons-dbcp-1.2.1.jar:..//lib/commons-lang-2.0.jar:..//lib/commons-logging-

1.0.4.jar:..//lib/commons-pool-1.2.jar:..//lib/ibatis-2.3.4.726.jar:..//lib/ibatis-dao-2.jar:..//lib/javassist-

3.12.1.GA.jar:..//lib/activation-1.1.jar:..//lib/mail-1.4.3.jar:..//lib/log4j-1.2.8.jar:..//lib/mysql-connector-

java-5.1.9.jar:..//lib/ognl-2.6.5.jar:..//lib/oscore-2.2.4.jar:..//lib/spring-1.1.3.jar:..//lib/spring-

1.2.6.jar:..//lib/xercesImpl-2.0.2.jar:..//lib/xml-apis-1.0.b2.jar -

javaagent:..//lib/OZSchedulerIntegration-0.0.1.jar oz.scheduler.main.OZScheduler

[root@localhost chakramax]#

[root@localhost chakramax]# ps -ef | grep java

root 16105 1 0 Sep03 ? 00:00:17 /home/chakramax/java/bin/java -

Djava.util.logging.config.file=/home/chakramax/tomcat/conf/logging.properties -

Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -

Djava.endorsed.dirs=/home/chakramax/tomcat/endorsed -

classpath :/home/chakramax/tomcat/bin/bootstrap.jar -Dcatalina.base=/home/chakramax/tomcat

-Dcatalina.home=/home/chakramax/tomcat -Djava.io.tmpdir=/home/chakramax/tomcat/temp

org.apache.catalina.startup.Bootstrap start

root 16365 1 0 Sep03 ? 00:00:00 /bin/sh /etc/init.d/chakra_java.sh


94/107

root 16367 16365 0 Sep03 ? 00:00:03 /home/chakramax/java/bin/java -Xms256m -

Xmx1024m -Dconfig=/home/chakramax/bin/gsp.conf com.warevalley.chakra.ChakraServer start

root 16380 16372 0 Sep03 ? 00:00:05 /home/chakramax/java/bin/java -Xms512m -

Xmx1024m -

cp ..//conf:..//lib/ozsfw51.jar:..//lib/jcert.jar:..//lib/jnet.jar:..//lib/jsse.jar:..//lib/crimson.jar:..//lib/parser.

jar:..//lib/xerces.jar:..//lib/mail.jar:..//lib/activation.jar:..//lib/OZUSLClientSession.jar:..//lib/OZUSLServ

erDES128.jar:..//lib/icu4j_2_8.jar:..//lib/ozviewer_lib.jar:..//lib/ozrresource.jar:..//lib/poi-scratchpad-

3.0.1.jar:..//lib/uk.co.mmscomputing.imageio.tiff.jar:..//lib/OZSchedulerIntegration-

0.0.1.jar:..//lib/ozsfw51.jar:..//lib/ozviewer_lib.jar:..//lib/ant_parser-1.1.jar:..//lib/chakra-core-1.0.0-

SNAPSHOT.jar:..//lib/chakra-function-1.0.0-SNAPSHOT.jar:..//lib/chakra-jnilib-1.0.0-

SNAPSHOT.jar:..//lib/chakra-ozapi-3.1.2_20110720.jar:..//lib/commons-collections-

3.1.jar:..//lib/commons-dbcp-1.2.1.jar:..//lib/commons-lang-2.0.jar:..//lib/commons-logging-

1.0.4.jar:..//lib/commons-pool-1.2.jar:..//lib/ibatis-2.3.4.726.jar:..//lib/ibatis-dao-2.jar:..//lib/javassist-

3.12.1.GA.jar:..//lib/activation-1.1.jar:..//lib/mail-1.4.3.jar:..//lib/log4j-1.2.8.jar:..//lib/mysql-connector-

java-5.1.9.jar:..//lib/ognl-2.6.5.jar:..//lib/oscore-2.2.4.jar:..//lib/spring-1.1.3.jar:..//lib/spring-

1.2.6.jar:..//lib/xercesImpl-2.0.2.jar:..//lib/xml-apis-1.0.b2.jar:..//lib/monetdb-jdbc-2.3-wv.jar -

javaagent:..//lib/OZSchedulerIntegration-0.0.1.jar oz.scheduler.main.OZScheduler

root 16856 16011 0 Sep03 ? 00:02:22 /home/chakramax/java/bin/java -

Dlog4j.configuration=file:/home/chakramax/java_dbc/bin/log4j.properties -

Djavadbc.home=/home/chakramax/java_dbc -jar /home/chakramax/java_dbc/bin/warevalley-java-

dbc.jar

root 32677 10163 0 15:32 pts/3 00:00:00 grep java

[Figure 5-4] Running the Chakra Max Server

Each process can also be started by individual commands.

# service chakra_maxsvr start

# service chakra_chad start

# service chakra_maxras start

# service chakra_gw start

# service chakra_sf start

# service chakra_tomcat start

# service chakra_schd start

# service chakra_ad start

# service chakra_jdc start

# service chakra_java start

[Figure 5-5] Individually starting the processes of Chakra Max Server

Each service command runs the following processes.


95/107

[Table 5-1] Service commands

Command Process Description

chakra_maxsvr maxsvr

The Chakra Max Management Server

process for user authentication, security

policies, and settings.

chakra_chad chad This is the HA Daemon process which is a

required process for high availability.

chakra_maxras rastracker

This is the Scheduler & Resource Monitor

Daemon process which monitors the

Chakra Max system and manages the

schedules and daily backups registered by

security manager.

chakra_gw cgw_gw

This is the Chakra Max Gateway Server

process which monitors and controls the

gateway access sessions of the security

client users.

chakra_sf cgw_sf

This is the Chakra Max Sniffing Server

process which monitors and controls the

sniffing access sessions of DB users.

chakra_tomcat tomcat

This is the tomcat service for providing the

online update and reporting of Chakra

Manager and Chakra Client.

chakra_schd OZ Scheduler This process provides report scheduling

feature in Chakra Manager.

chakra_ad java This is a schedule process to perform the

navigation feature.

chakra_jdc java

Java DB Collector

This is to decrypt the encrypted session, kill

a session, and collect the information of

DB objects.

chakra_java java This is a process for SQL syntax analysis.

Check through the Web Browser to see if tomcat is running normally and if the Tomcat program

update is problem-free using the Client and Manager. If the Tomcat service port needs to be

changed, refer to Appendix C, "Changing Tomcat Service Port.”

The following is an example screen for the Web Browser when checking Tomcat’s running state.


96/107

[Figure 5-6] Checking the running state of Tomcat

5.4 Exit Chakra Max Repository

Exit Chakra Max Repository by calling chakra_rep through a service command.

# service chakra_rep stop

5.5 Stopping Chakra Max Server

You can stop Chakra Max Server by stopping “chakra_max” with the service command.

# service chakra_max stop

The command "service chakra_max stop" stops all running processes.

You can also stop the processes using individual service commands.

# service chakra_chad stop

# service chakra_maxras stop

# service chakra_gw stop

# service chakra_sf stop

# service chakra_maxsvr stop

# service chakra_tomcat stop

# service chakra_schd stop

# service chakra_ad stop

# service chakra_jdc stop

# service chakra_java stop

[Figure 5-7] Stopping Chakra Max


97/107

Appendix A. How to install a cloud environment

When an environment which Chakra Max is installed is provided in a cloud environment, you need

to change the Chakra Max setting information to use the Chakra Max service.

To change the Chakra Max setting information, check first the running status of Chakra Max.

Typically, with the existing Chakra Max setting information, Chakra Max Server cannot be run.

When Chakra Max Server services are running, all services need to be shut down.

# service chakra_max stop

# ps –ef |grep server

root 2456 10163 0 15:38 pts/3 00:00:00 grep runserve

[Figure A-1] Chakra Max Server service stop

Next, Chakra Max Repository should be running. When the Repository is not running, run the

Repository.

# service chakra_rep start

# ps –ef |grep monetdbd

root 1975 10163 0 15:37 pts/3 00:00:00 grep monetdbd

root 8112 1 0 Sep02 ? 00:00:05 monetdbd start /home/chakramax/wdb_rep

[Figure A-2] The status of Chakra Max Repository On

To Chakra Max setting information, move the Tool (chakra_reconf.gz) to /usr/local/sbin and then

unzip with gunzip and run it.

# mv chakra_reconf.gz /usr/local/sbin

# gunzip chakra_reconf.gz


98/107

When the screen is displayed to enter a password for Repository after running, enter a password

to be changed and select OK.

[Figure A-3] Screen to change the Chakra Max Repository Password

Then, change ID/Password for the accessible super administrator in the Chakra Max Manager. The

password length to use should be more than 8 characters, and include at least one number and

special character.

[Figure A-4] Screen to change the Chakra Max Super administrator information


99/107

Press OK, and select Master IP on the displayed screen. The Tool automatically checks and lists all

interfaces in current environment. It also includes Virtual IP.

[Figure A-5] Screen to change the Chakra Max Server IP

Depending on the environment using the Chakra Max Server, set the information for the public IP

to use in Chakra Max Server or skip that.

[Figure A-6] NAT Environment setting Screen 1


100/107

[Figure A-7] NAT Environment Setting Screen 2

Finally, check the summary for setting information to change and press Yes to change the Chakra

Max setting information.

[Figure A-8] Summary Information Output Screen


101/107

When the changing of Chakra Max setting information is complete, svrinfo.ini and svrinfo.ini.md

files are created as a output.

[Figure A-9] List of the created files after the changing of the setting is complete

These files which are the information to connect to Chakra Max Server are copied to the program

setup path in the PC on which is installed Chakra Max Manager and Clients. If a warning window

alerting those files are existed pops up, overwrite it.

Chakra Max Client adds Users group in [Properties-Security] tab of svrinfo.ini and svrinfo.ini.md

files which are copied to the installed path, and grants read/run or read permissions. It is because

it must have a access permission for svrinfo.ini file when OS users which are ordinary users, not

administrators, use Chakra Max Client.


102/107

[Figure A-10] Chakra Max Manager, Overwrite Client files


103/107

After all tasks are complete, run Chakra Max Server and use Chakra Max Service with the following

commend.

The below examples are possible exceptions when Chakra Max setting information is changed.

[Figure A-11] When Tool is run with other users not root

[Figure A-12] When Chakra Max is not installed correctly

# service chakra_max start


104/107

[Figure A-13] When cgw.conf cannot be read

[Figure A-14] When Repository service is not running or connected


105/107

[Figure A-15] When entered password and re-entered password are not same

[Figure A-16] When Password violates the password policies


106/107

Appendix B. RDP Monitoring Approach

Chakra Max supports Remote Desktop Protocol (RDP) Monitoring of the protected system. The

RDP monitoring results can be found in the [Search] > [RDP] menu in Chakra Max Manager. To

operate this function, the Chakra Max Server requires installation and start-up of the Chakra WAC

(Chakra Windows Access Control & Audit). And, the Chakra WAC services should be installed and

operated in the Chakra Max Server.

Install Chakra WAC

This section explains how to install ChakraWAC on the Chakra Max Server.

The chakrawac directory is in Chakra Max Server installation path ($CHAKRAMAX_HOME). Move to

chakrawac and edit chakrawac.ini file by using chakrawac.ini.template provided as a sample.

root@cen65:/home/v2.0.8/chakrawac# cd $CHAKRAMAX_HOME/chakrawac

root@cen65:/home/v2.0.8/chakrawac# cp chakrawac.ini.template chakrawac.ini

root@cen65:/home/v2.0.8/chakrawac# vi chakrawac.ini

[SERVER]

ip = 192.168.31.208

port = 5648

[REPO]

max_limit = 20GB

Description of each item is as follows. Activate chakra_wac after setup.

Section Key Description

SERVER ip Chakra Max Server's master ip

port Port number that ChakraWAC will use

REPO max_limit Maximum storage of the path where a movie file is stored.

Enter values in MB or GB.

If the size is greater than the specified value, the oldest file is deleted.

If the key is missing, store it as large as the disk size.

.

Start and Stop commands are as follows.

Start command service chakra_wac start

Stop command service chakra_wac stop


107/107

Install Windows Agent

This section describes how to install ChakraWAC Service on the protected server. First, check out

the OS bit of the target Windows server and proceed with installation of a suitable installer file.

32-bit setup file: ChakraWACSetup32.msi

64-bit setup file: ChakraWACSetup64.msi

Copy ChakraWAC.ini.template file in the installation path (C:\Program

Files\WareValley\ChakraWAC\) to create and edit ChakraWAC.ini file. Description of each item is

as follows. Start ChakraWAC Service after setup.

Section Key Description

SERVER ip Chakra Max Server's IP

port The port number of server ChakraWAC

Delete Windows Agent

The ChakraWAC Service may be deleted with Add/Remove Programs in Windows. When removing,

be sure that ChakraWAC Service is stopped and all remote users are logged out.

Search RDP Audit Log

The audit log can be looked up in the [Search] > [RDP] menu in Chakra Max Manager. If the

menu cannot be found, contact a local technical support engineer for help.


108/107

22F, Nuritkum Square Biz Tower,

1605 Sangam-dong,

Mapo-gu, Seoul, Korea

TEL +82-2-743-4910

SALES +82-2-2132-5590 [email protected]

Partner +82-2-2132-5507 [email protected]

Tech. Support +82-2-2132-5516 [email protected]

mailto:[email protected]

mailto:[email protected]

Documents

Chakra Max Linux Installation Guide - iri.com · Chakra Max v2.0 Chakra Max Server for Linux Installation Guide 1/107 1 Introduction This document is an operations guide for installing