13-Synchronization and Data Management.pdf

7/24/2019 13-Synchronization and Data Management.pdf

http://slidepdf.com/reader/full/13-synchronization-and-data-managementpdf 1/19

OptiX iManager T2000

Operation Manual for SDH Contents

Huawei Technologies Proprietary

i

Contents

13 Synchronization and Data Management 13-1

13.1 Synchronizing NE Time 13-2

13.2 Synchronizing Current Alarms from NE 13-3

13.3 Backing up and Restoring T2000 Database 13-5

13.3.1 Immediately Backing up T2000 Database 13-5

13.3.2 Enabling Automatical T2000 Database Backup 13-5

13.3.3 Restoring T2000 Database 13-7

13.3.4 Initializing T2000 Database 13-9

13.4 Managing NE Database 13-10

13.4.1 Checking the Consistency of NE Configuration Data 13-10

13.4.2 Uploading/Downloading NE Configuration Data 13-12

13.4.3 Duplicating NE Configuration Data 13-12

13.4.4 Initializing NE Configuration Data 13-12

13.4.5 Exporting ROME Text Files Periodically 13-14




Operation Manual for SDH Tables


ii

Tables

Table 13-1 Files and usage 13-14




Operation Manual for SDH 13 Synchronization and Data Management


13-1

13 Synchronization and Data

Management

This chapter introduces the operations of synchronization and data management.The following tasks are described:

Synchronizing NE Time






13-2

Synchronizing Current Alarms from NE

Backing up and Restoring T2000 Database

Managing NE Database






13-3

13.1 Synchronizing NE Time

Purpose

Use this procedure to synchronize NEs time with the T2000.

The occurring time of alarm and performance event is important for record andtroubleshooting, so synchronizing NEs time with the T2000 is needed.

Prerequisite

NM user with the authority of “system administrator” or above.

Procedure

Step Action

1 Select [Configuration/Common Configuration/NE Time Synchronization].

2 Select one or more NEs in the lower-left pane and click thedouble-right-arrow button.

3 Select one or more NE entries. Right-click and select [Synchronize withNM Time].

4 If you do not want to synchronize the NE time with the NM manually. Youcan enable the auto synchronization function. Select one or more NEentries, right-click and select [Enable Auto Synchronization]. Then setthe “Synchronize Starting Time” and “Synchronization Period”, click

<Apply> to confirm the settings.






13-4

13.2 Synchronizing Current Alarms from NE

Purpose

Use this procedure to synchronize the current alarm between the NE and the T2000.

Alarm synchronization will verify the alarms in T2000 database and the alarms inNEs first, and then load the inconsistent alarm from NEs and overwrite the alarms inT2000 database so as to keep alarms consistent between T2000 database and NEs.

Alarm synchronization can execute automatically under certain conditions andmanually.

Prerequisite

NM user with the authority of "system operator" or above.

Procedure

1. Synchronize alarms in multiple NEs

Step Action

1 Select [Alarm/Synchronize Alarms] from the Main Menu.

2 Select one or more NEs to be synchronized.

3 Click <Synchronize Alarms>.






13-5

2. Synchronize alarms in a single NE

Step Action

1 Select an NE in Main Topology view.

2 Right-click the NE and select [Synchronize Current Alarm].






13-6

13.3 Backing up and Restoring T2000 Database

13.3.1 Immediately Backing up T2000 Database

Purpose

Use this procedure to back up T2000 database immediately and manually.

This task ensures T2000 NM system to recover safely and quickly when systemfaults occur, but it can not recover configuration data when updating system.

Prerequisites

Super NM user: admin.

Switch over to single-user mode.

Procedure

Step Action

1 Select [System/Database Backup/Backup Immediately] from the MainMenu.

2 The T2000 backs up the database immediately and displays theprogress.

Note:

The database file is backed up in the default directory. For example, it is

"/T2000/server/database/dbbackup/mo_20031024174342" on the Unix

platform or "C:\T2000\server\database\dbbackup\mo_20031024174342" on

the Windows platform.

13.3.2 Enabling Automatical T2000 Database Backup

Purpose

Use this procedure to set the backup period for the NM to perform automatic backup.






13-7

During the operation, you need to back up the T2000 database from time to time. Inthis way, if the database fails, the loss can be minimized by restoring the saveddatabase.

Prerequisites

Super NM user: admin.

Switch over to single-user mode.

Procedure

1. Enable a single scheduled backup

Step Action

1 Select [System/ Database Backup/Scheduled Backup] from the main

menu.

2 Set the date for a single backup and the start time as required.

By default, the T2000 will back up the NM database at 1:00 a.m. of theset date.

Note:



platform or "C:\T2000\server\database\dbbackup\mo_20031024 174342"on the Windows platform.

3 Click <Apply> to enable the settings.






13-8

2. Enable the periodic scheduled backup

Step Action

1 Select [System/ Database Backup/Scheduled Backup] from the main

menu.

2 Set the interval of periodic backup and the start time as required.

By default, the T2000 will back up the NM database at 1:00 am of theset date.

Note:



platform or "C:\T2000\server\database\dbbackup\mo_20031024 174342"

on the Windows platform.

3 Click <Apply> to enable the settings.

13.3.3 Restoring T2000 Database

Purpose

Use this procedure to restore T2000 database from the original T2000 databasebackup on the UNIX platform or Windows platform respectively.

Prerequisites

Back up the T2000 Database completely.

Shut down the T2000 server before restoring the database.

On the UNIX platform, the current user should have the Sybase database writeauthority.






13-9

On the Windows platform, the current user should have the system administratorauthority.

Procedure

1. On the Unix platform

Step Action

1 Right-click on the CDE desktop and select [Tools/Terminal] to open aterminal window.

2 In the "/T2000/server/database/mo" directory, delete all old files.

3 Copy the backup data file to be restored to the "/T2000/server/database/mo" directory.

Note:

To restore the database, the T2000 takes data from the "/T2000/

server/database/mo" directory.

4 In the "/T2000/server/database" directory, run "restoremo.sh" to restorethe T2000 database.

5 Press any key to continue the restoration.

2. On the Windows platform

Step Action

1 Open the "Resource Browser" of the Windows 2000.

2 In the "C:\T2000\server\database\mo" directory, delete all old files.

3 Copy the backup data file to be restored to the "C:\T2000\server\database\mo" directory.

Note:

To restore the database, the T2000 takes data from the "C:\T2000\

server\database\mo" directory.

4 In the "C:\T2000\server\database" directory, run "restoremo.bat" torestore the T2000 database.

5 Press any key to continue the restoration.






13-10

13.3.4 Initializing T2000 Database

Purpose

Use this procedure to initialize T2000 database to the original status.

Caution:

This operation will clear all the T2000 data in the database. Please back up theT2000 database before this operation.

Prerequisites

The T2000 server has been shut down.

On the UNIX platform, the current user should have the Sybase database writeauthority and make sure that the T2000DBServer has been started.

On the Windows platform, the current user should have the system administratorauthority and make sure that the MS SQL Server database has been started.

Procedure

1. On the Unix platform

Step Action

1 Right-click on the CDE desktop and select [Tools/Terminal] to open aterminal window.

2 In the "/T2000/server/database" directory, run "InitDatabaseSYBASE.sh"to initialize the T2000 database.

3 Press any key to continue the initialization.

2. On the Windows platform

Step Action

1 Open the "Resource Browser" of the Windows 2000.

2 In the "C:\T2000\server\database" directory, run "InitDatabase.bat" toinitialize the T2000 database.

3 Press any key to continue the initialization.






13-11

13.4 Managing NE Database

13.4.1 Checking the Consistency of NE Configuration Data

Purpose

Use this procedure to check whether the T2000 configuration data and the NEconfiguration are consistent.

The configuration data in NEs and in the T2000 database is compared in this taskand a report of consistency is created. According to the report and actual reliability ofconfiguration data, uploading or downloading configuration data is selected toimplement.

This task will not change the configuration data in NEs and the T2000 database and

it is recommended to run this function periodically to keep the consistency ofconfiguration data in NEs and the T2000 server.

Prerequisite

NM user with the authority of "system maintainer" or above.

Procedure

Step Action

1 Select [Configuration/Configuration Data Management/ConfigurationData Consistency Check].

Or, select [Maintenance/Configuration Data Management/NEConfiguration Data Management] from the navigation tree of theEquipment Maintenance Console.

2 In the lower-left pane, select the appropriate NEs and click thedouble-right-arrow button (red).

3 Select one or more NEs to check in the NE Data List.

4 Right-click the NE and select [Consistency Check].






13-12

Step Action

5 Click <OK> to confirm the consistency check.

Note:

If the check result shows the modules with the configuration datainconsistent, you should solve the problem by re-uploading or

re-downloading the configuration data as required in practice.






13-13

13.4.2 Uploading/Downloading NE Configuration Data

Refer to "4.2.1 Uploading/Downloading NE Configuration Data".

13.4.3 Duplicating NE Configuration Data

Refer to "4.3 Duplicating NE Configuration Data".

13.4.4 Initializing NE Configuration Data

Purpose

Use this procedure to initialize the NE configuration data in the T2000 database orthe NE. The NE initialized in the T2000 will be in unconfigured status

Prerequisites

For initializing the configuration data in T2000 database, the NM user needs theauthority of "system maintainer" or above.

For initializing the configuration data in NE, the NE user logged in the T2000needs the authority of "system level".

Procedure

Step Action

1 Select [Configuration/Configuration Data Management/Configuration

Data Initialization].

2 In the lower-left pane, select the appropriate NEs and click thedouble-right-arrow button (red).

3 Select one or more NEs from the NE data list.






13-14

Step Action

4 For initializing the NE configuration data in T2000 database, right-clickthe NE and select [Initialize NM Data].

For initializing the configuration data in NE, right-click the NE and select[Initialize NE Data].

5 Click <OK> to confirm the operation.






13-15

13.4.5 Exporting ROME Text Files Periodically

Purpose

Use this procedure to automatically export ROME text files periodically.

The NE data in the T2000 are exported in ROME text files and stored in the specifieddirectory on the T2000 server. The T2000 can export the ROME text files at ascheduled time, that is, it automatically exports data at a specific time withoutpersonal intervention. Only when you want to manage NE data in the ROMEdatabase, you need to export the NE data in the T2000.

NE data include information about ports, boards, NEs, trails and Ethernet VLANs.

错误错误错误错误未找到引用源未找到引用源未找到引用源未找到引用源 lists ROME text files contained in the directory and their usage.

Table 13-1 Files and usageFile name Usage

c_hua_1.txt Record board information.

ct_hua_1.txt Record trail information on SDH client layer.

cte_hua_1.txt Record trail end points information at SDH client layer.

ctr12_hua_1.txt Record VC12 trail routes information at SDH client layer.



eth_hua_1.txt Record Ethernet trail information.

ethe_hua_1.txt Record Ethernet trail end points information.

ethr_hua_1.txt Record Ethernet trail routes information.

extraction_done Identification document, generated by the interface module afterall interface text files are generated, to identify the interface textfiles have been exported successfully.

ne_hua_1.txt Record NE information.

p_hua_1.txt Record port information.

st_hua_1.txt Record trail information at SDH service layer.

ste_hua_1.txt Record trail end points information at SDH service layer.

vlan_hua_1.txt Record Ethernet VLANs information.

tl_hua_1.txt Record Trunk Link trails information.

tle_hua_1.txt Record Trunk Link trail end points information.

tlr_hua_1.txt Record Trunk Link trail routes information.






13-16

File name Usage

vb_hua_1.txt Record Ethernet VBs information.

Prerequisites

NM user with the authority of "system operator" or above.

Export NE data in the T2000 only NE data need to be managed through ROMEdatabase.

To enable this function, remove the "#" out of "# item= name(ROME Text Export)OTID(4) OSTID(2) OID(1) CID(12560)" in the menu.ini file.On the Windows platform, this file is saved atC:\T2000\client\locale\C\imap12\common\profile (suppose the T2000 Client isinstalled in C:).On the UNIX platform, this file is save at/T2000/client/local/C/imap12/common/profile.

Procedure

Step Action

1 Select [System/ROME Text Export] from Main Menu.

2 Select to enable automatic export.

3 . Set the start time in the “Start Task Time”.






13-17

Step Action

4 Select an appropriate directory to store exported files. The defaultdirectory is “rome/”, You can select a subdirectory from the “OperationDirectory List” as the current directory for storing exported files.

If there is no appropriate subdirectory, you can create a newsubdirectory. Click <Create File Directory>, the “Input” dialog box isdisplayed. Type a name for the directory.

Note:

You can delete a subdirectory here. Select a subdirectory from the

“Operation Directory List” and click <Delete File Directory>.

Deleting a directory will delete all files contained in that directory.

5 Click <Apply> to confirm the operation.

Note:

You can query exported files. By default, these files are stored in:

On the Windows platform, the path is “C:\T2000\server\rome”. (Suppose the

T2000 server is installed in C:\)

On the UNIX platform, the path is “/T2000/server/ script/rome”.

Date post:	22-Feb-2018
Category:	Documents
Upload:	sunynguyen
View:	213 times
Download:	0 times

13-Synchronization and Data Management.pdf

Documents