01-06 Database Management

iManager N2000 DMS Datacomm Network Management System Administrator Guide Contents

Issue 02 (2007-10-15) Huawei Technologies Proprietary i

Contents

6 Database Management..............................................................................................................6-1 6.1 Dump and Backup.........................................................................................................................................6-2 6.2 DMS Database ..............................................................................................................................................6-2

6.2.1 FaultDB................................................................................................................................................6-2 6.2.2 LogDB .................................................................................................................................................6-3 6.2.3 PerfDB .................................................................................................................................................6-3 6.2.4 SecurityDB...........................................................................................................................................6-3 6.2.5 TopoDB................................................................................................................................................6-3 6.2.6 GnldevDB ............................................................................................................................................6-4 6.2.7 iAgentDB.............................................................................................................................................6-4

6.3 Viewing the Database Status .........................................................................................................................6-4 6.4 Expanding the Database ................................................................................................................................6-5

6.4.1 Through the N2000 System Monitor ...................................................................................................6-5 6.4.2 Expanding the Sybase Database Through the Command Line ............................................................6-6 6.4.3 Expanding the SQL sever Database Through the Command Line.......................................................6-7

6.5 Dumping Alarm Database .............................................................................................................................6-8 6.5.1 Automatic Dump of Alarm Data ..........................................................................................................6-8 6.5.2 Dumping Data Manually....................................................................................................................6-10

Figures

iManager N2000 DMS Datacomm Network Management SystemAdministrator Guide

ii Huawei Technologies Proprietary Issue 02 (2007-10-15)

Figures

Figure 6-1 Database information........................................................................................................................6-5

Figure 6-2 Database expansion ..........................................................................................................................6-6

Figure 6-3 Alarm dump ......................................................................................................................................6-9

Figure 6-4 Event dump.......................................................................................................................................6-9

Figure 6-5 Log dump........................................................................................................................................6-10

Figure 6-6 Dump alarm data.............................................................................................................................6-11

iManager N2000 DMS Datacomm Network Management System Administrator Guide Tables

Issue 02 (2007-10-15) Huawei Technologies Proprietary iii

Tables

Table 6-1 Dump and backup...............................................................................................................................6-2

iManager N2000 DMS Datacomm Network Management System Administrator Guide 6 Database Management

Issue 02 (2007-10-15) Huawei Technologies Proprietary 6-1

6 Database Management About This Chapter

The following table lists the contents of this chapter.

Section Describes

6.1 Dump and Backup This section describes the concepts of dump and backup, and the difference between dump and backup.

6.2 DMS Database This section describes the DMS database.

6.3 Viewing the Database Status

This section describes how to check the database status.

6.4 Expanding the Database This section describes how to expand the database.

6.5 Dumping Alarm Database This section describes how to clear the database.

6 Database Management iManager N2000 DMS Datacomm Network Management System

Administrator Guide

6-2 Huawei Technologies Proprietary Issue 02 (2007-10-15)

6.1 Dump and Backup Dump and backup are two different operations on data. Their meaning and description are listed in Table 6-1.

Table 6-1 Dump and backup

Operation Meaning Description

Dump Exports data from the database into a file for future reference.

z The purpose is to view the data. z The source data is deleted from the

database. z The dumped data cannot be restored

from the file to the database.

Backup Copies data from the database into a file. When the source data is damaged, you can import the backup data into the database for restoration purpose.

z The purpose is to restore the data to the database in case of a fault.

z The source data is not deleted from the database.

z The backup data is restored to the database.

6.2 DMS Database Seven DMS basic databases are set up as follows:

z FaultDB z LogDB z PerfDB z SecurityDB z TopoDB z GnldevDB z IAgentDB

The master and tempdb are system databases.

6.2.1 FaultDB The alarm data is saved in the FaultDB. The data space is recommended not to be less than 750 MB and the log space not to be less than 500 MB.

The names and functions of lists in the FaultDB are shown as follows:

z tbl_AlarmCfg: Records the static configuration information of alarms. z tbl_CurAlm: Records current alarms. z tbl_Event: Records the event information.



z tbl_HisAlm: Rerecords the history alarms. z tbl_AlmShieldCondition: Records the mask conditions of the alarms and events. z Other tables: Record the internal realization information of the alarm module.

6.2.2 LogDB The NMS user operation logs and some related data are saved in the LogDB. The data space is recommended not to be less than 150 MB and the log space not to be less than 75 MB.

The names and functions of lists in the LogDB are shown as follows:

z tbl_Log: Records the operation information of the NMS user. z tbl_LogPara: Records the personal setting information of the NMS user log. z tbl_Syslog: Records the Syslog operation information. z tbl_SyslogServer: Records the running information of the Syslog server. z Other tables: Record the internal realization information of log management.

6.2.3 PerfDB The real-time performance data is saved in the PerfDB. The data space is recommended not to be less than 40 MB and the log space not to be less than 20 MB.

The names and functions of lists in the PerfDB are shown as follows:

z tbl_PerfTmpl: Records the information of the performance template. z tbl_Perflndi: Records the information of the performance indices. z tbl_IndiInTmpl: Records the performance indices and template-concerned information. z tbl_MibObj: Records the information of the Management Information Base (MIB) to be

accessed to view the performance indices. z Other tables: Record the internal realization information of performance management.

6.2.4 SecurityDB The security right data is saved in the SecurityDB. The data space is recommended not to be less than 80 MB and the log space not to be less than 80 MB.

The names and functions of lists in the SecurityDB are shown as follows:

z tbl_User: Records the user information. z tbl_Group: Records the user group information. z tbl_CmdSet: Records the operation set information. z tbl_GrantRight: Records the information of the right grant. z Other tables: Record the internal realization information of security management.

6.2.5 TopoDB The topology data is saved in the TopoDB. The data space is recommended not to be less than 80 MB and the log space not to be less than 50 MB.

The names and functions of lists in the TopoDB are shown as follows:

z tbl_Node: Records the data of the topology node. z tbl_Submap: Records the data of the topology sub-map.


Administrator Guide


z tbl_Link: Records the data of the topology connection. z Other tables: Record the topology internal realization information.

6.2.6 GnldevDB The data of the third party devices is saved in the GnldevDB. The data space is recommended not to be less than 80 MB and the log space not to be less than 40 MB.

The names and functions of lists in the GnldevDB are shown as follows:

z tbl_DevTypeAndNodeTypeTab: Records the information of the relationship between the device type and node type.

z tbl_IPIfTab: Records the information of the list of device interfaces. z Other tables: Record the internal realization information of third part device

management.

6.2.7 iAgentDB The northbound interface data is saved in the iAgentDB. The data space is recommended not to be less than 80 MB and the log space not to be less than 50 MB.

The names and functions of lists in the iAgentDB are as follows:

z tbl_Event: Records the data of information of cache. z tbl_SnmpV3Para: Records the SNMP V3 parameters of the northbound interface. z Other tables: Record the internal realization information of northbound interface

management.

6.3 Viewing the Database Status

Description View the statuses of all DMS databases to ensure that the DMS runs normally.

Precaution When the database usage exceeds the alarm threshold, the alarm prompts appear as follows:

z The database records on the N2000 System Monitor turn red. z The N2000 System Monitor service process sends alarms to the NMS and the alarms are

displayed in the alarm list of the fault management.

Procedure Step 1 Log in to the N2000 System Monitor.

Step 2 Select the Database tab.

The database information of the NMS server is displayed on the tab, as shown in Figure 6-1.



Figure 6-1 Database information

Step 3 This step is optional. Right-click the database information list. Select Refresh to refresh data of all items.

----End

6.4 Expanding the Database According to the capacity of the communication network managed by the DMS, you can expand the database manually when the data space or the log space in the database is not enough.

Two modes of expanding the database are shown as follows:

z Through the N2000 System Monitor z Expanding the Sybase Database Through the Command Line

6.4.1 Through the N2000 System Monitor

Description With the DMS N2000 System Monitor, you can expand the data space and the log space in the database.

Precaution z Before expanding the database, you need to back up the database. For operations of the

backup database, see section "9 Database Backup and Restoration." z The database cannot be restored to the initial configuration after being expanded. The

database space cannot be expanded without any limit and a single database space cannot


Administrator Guide


expand more than 5000 MB once. Therefore, do not expand the data field and log field at random.

Procedure Step 1 Log in to the N2000 System Monitor.

Step 2 Select the Database tab. Select the database records to be expanded. Right-click the page. Select Expand.

Step 3 The Database Expansion dialog box is displayed. Enter the size of the data space and the log space to be expanded, as shown in Figure 6-2.

Figure 6-2 Database expansion

Step 4 Click OK.

Step 5 The confirmation dialog box is displayed. Click OK after confirmation.

Step 6 The prompt of success in expanding the database is displayed. Click OK.

----End

6.4.2 Expanding the Sybase Database Through the Command Line

Description Expand the Sybase.

When you perform the expansion operation on the drive where the NMS database does not exist, you need to perform the operation with the command lines.

Procedure Suppose that the current FaultDB data storage path is /opt/sybase/data. The path to expand the fatultDB to the new physical medium (512 MB) is /new_data/.

Step 1 Log in to the N2000 System Monitor.



Step 2 Choose System > Stop Server in the main menu to stop all DMS processes and disconnect all database to be expanded.

Step 3 Run the following commands to initialize the device.

isql>disk init name=new_fault_dev,physname=/new_data/fault_new_dev.dat, vdevno=101,size=256000 isql>disk init name=new_fault_log_dev,physname=/new_data/fault_new_log_dev.dat, vdevno=101,size=256000

z The names of the disk and database are defined by the user. The unit of parameters is 2 KB. z The vdevno is the device number. Every database device has one and only device number. Using the

isql>sp_helpdevice command, you can query the used device number. The device_number in the displayed information is the device number.

Step 4 Run the following commands to expand the database.

isql>alter database FaultDB on new_fault_dev=512 isql>alter database FaultDB on new_fault_log_dev=512

The unit of the parameters is MB.

Step 5 Using the quit or exit commands, you can quit the DMS database.

Step 6 At the System Monitor, choose System > Start Server to start all DMS service processes.

----End

6.4.3 Expanding the SQL sever Database Through the Command Line

Description Expand the SQL Server database.

When you perform the expansion operation on the disk where the NMS database does not exist, you need to perform the operation with the command lines.

Procedure Step 1 Choose Start > Programs > Microsoft SQL Server > Query Analyzer and run the SQL

query analyzer.

Step 2 Select SQL Sever Authentication. Enter the user name and password of the database. The database query window appears.

Step 3 In the database query window, input the database expansion commands as follows:

ALTER DATABASE FaultDB ADD FILE (NAME=new_fault_dev, FILENAME = D:\new_data\fault_new_dev.dat ,SIZE=512000KB, MAXSIZE = UNLIMITED, FILEGROWTH = 10%) ALTER DATABASE FaultDB ADD LOG FILE (NAME=mylogdev, FILENAME = D:\new_data\fault_new_log_dev.dat,SIZE=512000KB, MAXSIZE = UNLIMITED, FILEGROWTH = 10%)

Step 4 Choose Tools > Execute in the main menu and run the commands in batch.


Administrator Guide


----End

6.5 Dumping Alarm Database 6.5.1 Automatic Dump of Alarm Data

Automatic dump of data includes automatic dump of the alarm, event and log data.

Description Configure the automatic dump policy of the history alarm data. Dump the history alarm data to the file in a certain period.

The automatic dump policy covers the following:

z Overflowed dump z Periodical dump

The default dump path is $N2000ROOT/server/dump.

The name format of the dump alarm file is Alarm year month data hour minute second-No..txt, such as Alarm20070329144540-00.txt.

The name format of the dump event file is Event year month data hour minute second-No..txt, such as Event20070329172833-01.txt.

The dump file supports three formats as follows:

z html z csv z txt

The dumped files can realize the cycle cover. When the amount of alarm data backup files exceeds default 1000, the system automatically covers the previous files to ensure that the disk space can be released.

Precaution z When the alarm database is filled, the system automatically dumps the alarms according

to the full dump policy. z The dumped alarm records are saved in the specified dump path and deleted from the

database. z The records of the dumped data cannot be queried in the Fault Browse window.

Procedure Step 1 Log in to the DMS client and choose System > Dump Settings in the main menu.

Step 2 The Dump Settings dialog box is displayed. Select the Alarm Dump tab. Configure the alarm dump conditions and the path to save the dumped files, as shown in Figure 6-3.



Figure 6-3 Alarm dump

Step 3 Select the Event Dump tab. Configure the event dump conditions, as shown in Figure 6-4.

Figure 6-4 Event dump

Step 4 Select the Log Dump tab. Configure the log dump conditions and the path to save files after dump, as shown in Figure 6-5.


Administrator Guide


Figure 6-5 Log dump

Step 5 Click OK to complete the configuration of automatic dump of the alarm, event and log.

----End

6.5.2 Dumping Data Manually Dumping data manually includes Dump user log, Dump Device user log , Dump Alarm and Dump Event.

The dumping procedures are similar. Take the procedure to dump the alarm data manually as an example.

Description Dump the alarm data manually. Dump the data in the current database.

Procedure Step 1 Log in to the DMS client and choose System > Dump Manually > Dump Alarm.

Step 2 The Dump Alarm dialog box is displayed. Select the format of the file to be saved and time for dumping the alarm, as shown in Figure 6-6.



Figure 6-6 Dump alarm data

Step 3 This step is optional. Click Query. The amount of the dump alarms in this period of time is displayed in Records(Pieces).

Step 4 Click OK. ----End

ContentsFiguresTables6 Database ManagementAbout This Chapter6.1 Dump and Backup6.2 DMS Database6.2.1 FaultDB6.2.2 LogDB6.2.3 PerfDB6.2.4 SecurityDB6.2.5 TopoDB6.2.6 GnldevDB6.2.7 iAgentDB

6.3 Viewing the Database Status6.4 Expanding the Database6.4.1 Through the N2000 System Monitor6.4.2 Expanding the Sybase Database Through the Command Line6.4.3 Expanding the SQL sever Database Through the Command Line

6.5 Dumping Alarm Database6.5.1 Automatic Dump of Alarm Data6.5.2 Dumping Data Manually

01-06 Database Management

Documents

database management

dms database

sybase database

database information

database expans

database status

dumping alarm database

n2000 system monitor