Huawei Igwb User Manual
Huawei Igwb User Manual
Contents
2 Dangerous Operations..............................................................................................................2-1
2.1 Dangerous Operations on Hardware...............................................................................................................2-2
2.2 Dangerous Operations on Software.................................................................................................................2-3
3 Daily Maintenance.....................................................................................................................3-1
3.1 Checking Device Indicators............................................................................................................................3-2
3.2 Checking the Alarms.......................................................................................................................................3-3
3.3 Checking CDR Backup...................................................................................................................................3-4
3.3.1 Checking the CDR Backup on a Third-Party Server.............................................................................3-4
3.3.2 Checking the CDR Backup Between the Two iGWB Servers...............................................................3-6
3.3.3 Checking the CDR Backup on a Tape Drive.........................................................................................3-8
3.4 Checking Resource Usage.............................................................................................................................3-10
3.5 Checking the Link States...............................................................................................................................3-11
3.6 Checking and Replacing a Tape....................................................................................................................3-12
4 Weekly Maintenance.................................................................................................................4-1
4.1 Checking the States of the iGWB Devices......................................................................................................4-2
4.1.1 Basic Knowledge of the Processes on the iGWB Server.......................................................................4-2
4.1.2 Checking the Processes of the iGWB Server.........................................................................................4-4
4.1.3 Checking the File System on the iGWB Server.....................................................................................4-5
4.1.4 Checking the Services of the iGWB Server...........................................................................................4-5
4.1.5 Checking the Connection to the iGWB Client.......................................................................................4-6
5 Monthly Maintenance...............................................................................................................5-1
5.1 Checking the System Time on the iGWB Server............................................................................................5-2
5.2 Checking the Function of Sending Alarms.....................................................................................................5-2
5.3 Checking the Parameter Settings.....................................................................................................................5-3
5.4 Checking the Functions of Handling CDR Files.............................................................................................5-4
5.4.1 Checking the Receiving and Processing of the Original CDR Files......................................................5-4
5.4.2 Checking the Function of Sending Final CDRs.....................................................................................5-5
5.5 Cleaning the Magnetic Head of the Tape Drive..............................................................................................5-6
6 Yearly Maintenance...................................................................................................................6-1
6.1 Checking the Switchover of the iGWB...........................................................................................................6-2
6.2 Checking the Restart of the Devices...............................................................................................................6-3
6.3 Checking the Cable Connections....................................................................................................................6-4
7 Appendix......................................................................................................................................7-1
7.1 User Types of the iGWB.................................................................................................................................7-2
7.2 Directory Structures for Storing CDR Files on the iGWB Server..................................................................7-4
7.3 Directory Structure for the iGWB Server........................................................................................................7-6
7.4 Important Files of the iGWB Server...............................................................................................................7-8
7.5 Directory Structure of the iGWB Client.......................................................................................................7-10
7.6 Important Files of the iGWB Client..............................................................................................................7-10
7.7 Introduction to the iGWB Channels..............................................................................................................7-10
7.8 Maintenance Records....................................................................................................................................7-11
7.8.1 Daily Maintenance Records.................................................................................................................7-11
7.8.2 Weekly Maintenance Records..............................................................................................................7-12
7.8.3 Monthly Maintenance Records............................................................................................................7-13
7.8.4 Yearly Maintenance Records...............................................................................................................7-14
7.8.5 Emergent Faults Handling Records......................................................................................................7-15
Figures
Tables
This chapter describes the basic information that maintenance personnel must be acquainted
with, including safety operation guidance, classification of routine maintenance, principles of
routine maintenance, tasks and periods, routine maintenance tools, and requirements for
maintenance personnel.
Routine maintenance is preventive maintenance work. It is planned and performed on a routine
basis to check and maintain the condition of the devices. Through routine maintenance,
maintenance personnel can detect and remove the existing or latent faults of the devices. This
helps guarantee the safety, stability, and reliability of the devices.
1.1 Safety Operation Guidance
This section describes the warning signs and safety signs and ESD-preventive measures.
1.2 Classification of Routine Maintenance
Routine maintenance includes daily maintenance and periodical maintenance.
1.3 Principles of Routine Maintenance
To fully exercise the performance and functions of the devices, avoid various accidents, and
ensure long-term, safe and stable operation of the devices, maintenance personnel must learn
and comply with the following principles before performing routine maintenance.
1.4 Tasks and Periods
Based on different periods, routine maintenance includes daily maintenance, weekly
maintenance, monthly maintenance, and yearly maintenance.
1.5 Routine Maintenance Tools
This section describes the tools used for routine maintenance of the iGWB.
1.6 Requirements on Maintenance Personnel
Before performing routine maintenance, maintenance personnel must complete the training
courses given by Huawei. Through the training courses, maintenance personnel can be familiar
with the software structure, software operations, hardware structure, and hardware operations
of the iGWB devices. Also, maintenance personnel must comply with the required operation
regulations and industry safety regulations to ensure device safety and personal safety.
Causes of ESD
The average body voltage is approximately 200 pF. ESD is generated as we walk. How many
voltage do our bodies contain is determined by factors, such as the materials of the clothes we
are wearing, the materials of the floors, the surfaces of the materials, the indoor temperature,
and and the speed at which we walk.
Table 1-2 shows the body voltages in three different cases.
ESD Hazard
ESD may cause severe damage to electrical components. In addition, ESD may induce software
failures and thus cause malfunction of electronic switches. When the voltage of the ESD reaches
hundreds of or thousands of V, touching the electronic components may cause fatal damages to
the electronic components.
Statistics show that 60% of damaged boards are induced by ESD. If a person stays in a room
without ESD prevention measures for 12 seconds or more, the person can generate a 12 kV ESD
from the body. In this case, if the person directly touches the devices, the devices are severely
damaged.
Table 1-3 lists the relationship between the electronic components and the voltages that can
damage the electronic components.
Table 1-3 Relationship between the electronic components and the voltages that can damage
the electronic components
SCR 680-1000
ESD-Preventive Measures
Proper ESD-preventive measures must be taken to control or reduce ESD in the equipment room.
The ESD-preventive measures include but are not limited to the following:
l Cover the floor of the equipment room with ESD-preventive boards or carpets.
l Enforce dust-proof measures in the equipment room to prevent or reduce ESD
accumulation.
l Maintain the temperature and humidity at the required levels in the equipment room.
l Do not clean the ESD boards on the floor with floor wax. Remove the insulated oil film,
resin, and rubber attached on the ESD-preventive table pad, floor, and floor cushion. Clean
the floor cushion with neutral detergent or antistatic additive.
l Label antistatic devices, tools, and ESD-sensitive materials with ESD-preventive signs.
Label antistatic grounding systems with grounding signs.
l Make sure that the devices are in direct contact with the floor. The grounding resistance of
the devices must be less than 10 Ω. This helps to eliminate ESD and thus prevent
electrostatic accumulation.
l Before operating the devices, maintenance personnel must wear the ESD-preventive
clothes and ESD-preventive wrist strap.
l Maintenance personnel must use ESD-preventive chairs.
Daily Maintenance
Daily maintenance refers to the simple operations carried out by maintenance personnel every
day, such as checking device states, checking the CDR backup, and checking the alarm system.
Daily maintenance serves the following purposes:
l To detect the alarms and defects of the devices in time and take proper measures to clean
the alarms or remove the defects. This helps reduce the device failure rate.
l To detect and handle the exceptions occurring when the billing system is running. This
helps reduce financial loss due to CDR loss.
l To learn the states of the devices and the network in real time. This helps improve work
efficiency in handling emergencies.
Periodical Maintenance
Periodical maintenance refers to the relatively complicated operations periodically carried out
by trained maintenance personnel, such as backing up files, checking the parameter settings, and
checking the iGWB switchover function.
Periodical maintenance serves the following purposes:
l To detect the defects of the devices in time (such as malfunction, performance degrading,
and aging) and to take proper measures to remove these defects.
l To maintain the devices in good condition and ensure safety, stability, and reliability of the
system.
with the required operation regulations and industry safety regulations to ensure device
safety and personal safety.
l Maintenance personnel must keep the administrative passwords confidential and change
them regularly. The passwords must be classified into different levels and be allocated to
maintenance personnel based on the operation permissions of the maintenance personnel.
l Maintenance personnel must back up the data before modifying it, and record the
modification.
l Record all risky operations, such as iGWB server switchover and resetting the devices.
Confirm that the operations are feasible before performing them. Do not carry out any
operation until you take proper backup and emergency measures.
l Except the software provided by Huawei along with the devices, do not use other software
to query or modify the database directly. Otherwise, unexpected problems may occur.
l Perform routine maintenance based on the instructions given in this manual and record the
necessary information. If you encounter any tricky problem, contact Huawei Customer
Service.
Maintenance Item
by Period
Maintenance Item
by Period
Cotton yarn cloth and It is used to clean device surface and device connectors.
vacuum cleaner
Maintenance personnel must acquire the following basic knowledge and skills:
2 Dangerous Operations
This chapter describes the dangerous operations on hardware and software. These operations
may affect the running of the iGWB and induce service interruption or CDR loss. Maintenance
personnel are forbidden to perform these operations.
Plugging or unplugging The serial heartbeat links are disconnected and the
heartbeat serial cables two-node signaling detection function is degraded.
Stopping the OS services The When the OS services are stopped, the
OS services include but are processes monitored by these services are
not limited to the following: also stopped. Also, the relevant services are
l Process Watch Dog affected.
OS services
Service For example, if the Cfg Server Service is
stopped, the cfg_proc process is also
l Cfg Server Service
stopped. In this case, the iGWB Parameter
l FTP Publishing Service Config Console cannot be logged in to.
IP address of Modifying the IP address of a The iGWB cannot normally run. Also, the
the network network adapter iGWB is disconnected from other devices.
adapter
iGWB Modifying the directory The iGWB cannot normally run. The
directory structure or a folder name relevant services are affected.
structure
Break Service For Upgrade Perform this operation only when the
iGWB is being upgraded. After this
operation, the iGWB cannot receive CDRs
but can still process the CDRs that were
previously received.
To roll back this operation, manually switch
over the primary and secondary iGWB
servers or restart the iGWB.
3 Daily Maintenance
This chapter describes the daily maintenance tasks, such as checking the device indicators,
checking CDR backup, and checking resource usage.
Context
Table 3-1 describes the device indicators.
iGWB server Power indicator l If this indicator is on, it indicates that the
iGWB server is running.
l If this indicator is off, it indicates that the
iGWB server is not running.
l If this indicator blinks, it indicates that the
iGWB server is starting up.
Tape drive Tape indicator l If this indicator is on, it indicates that no tape
is inserted.
l If this indicator is off, it indicates that a tape
is inserted.
l If this indicator blinks, it indicates that a tape
is being read or written.
LAN switch RUN indicator l If this indicator blinks, it indicates that the
LAN switch is running.
l If this indicator does not blink, it indicates
that the LAN switch is faulty.
Procedure
Step 1 Make sure that the power indicator and network port connection indicator of the iGWB server
are on.
Step 2 Make sure that the indicators of the hard disks are on in green. If any indicator is on in red,
replace it.
Step 3 For the LAN switch, make sure that the RUN indicator blinks, the LINK indicator is on, and the
OK indicator is on.
----End
Prerequisite
Maintenance personnel must have the operation permissions of the NMC or BAM.
Procedure
Step 1 Log in to the NMC to check whether any alarm was generated by the iGWB one day before.
Step 2 Log in to the BAM to check whether any alarm was generated by the iGWB one day before.
NOTE
----End
Postrequisite
For details about the alarm parameters and the methods of rectifying the faults, see the iGWB
Troubleshooting.
According to the type of the destination backup machine, the iGWB supports the following CDR
backup modes:
l Backing up CDR files to a third-party server
l Backing up CDR files between the two iGWB servers
l Backing up CDR files to a tape drive
It is recommended to back up the CDR files on a third-party server. To do this, you can configure
a backup task in the igwb.ini file through the iGWB Parameter Config Console.
3.3.1 Checking the CDR Backup on a Third-Party Server
If the CDR files are backed up on a third-party server, maintenance personnel must check
whether the CDR files are correctly backed up on a daily basis.
3.3.2 Checking the CDR Backup Between the Two iGWB Servers
If the CDR files are backed up between the two iGWB servers, maintenance personnel must
check whether the CDR files are correctly backed up between the two iGWB servers on a daily
basis.
3.3.3 Checking the CDR Backup on a Tape Drive
If CDR files are backed up on a tape drive, maintenance personnel must check whether the CDR
files are correctly backed up between a tape drive on a daily basis.
Prerequisite
The relevant settings are configured for backing up the CDR files on a third-party server. For
details about how to configure these settings, see the iGWB Configuration Guide.
NOTE
In the following example, the primary iGWB server is in active state and the secondary iGWB server is in
standby state.
Context
You can use the SmartBackup to configure a backup task. For details, see the iGWB Installation
Guide.
l With the SmartBackup, you can check the source backup path in the Local directory
parameter of a backup task.
l With the SmartBackup, you can check the destination backup path in the Ftp directory
parameter of a backup task.
You can configure a backup task in the igwb.ini file. For details, see the iGWB Configuration
Guide.
l On the iGWB Parameter Configuration Console, you can specify the source backup path
in the SourceDir parameter of the BackupTask%d section.
l On the iGWB Parameter Configuration Console, you can specify the destination backup
path in the DestDir parameter of the BackupTask%d section.
%d indicates the backup task number. The value can be any positive integer number except 0.
Procedure
Step 1 On the third-party server, compare the CDR files backed up one day ago with those generated
on the primary iGWB server one day ago.
If the numbers, sizes, and serial numbers of these CDR files are consistent, it indicates that the
CDR files generated on the primary iGWB server are all backed up on the third-party server.
Step 2 On the secondary iGWB server, check whether the CDR files generated one day ago exit. If any
CDR file is found, compare the CDR files with those backed up on the third-party server one
day ago.
NOTE
l Normally, only the primary iGWB server generates CDR files. These CDR files are backed up on the
third-party server. In standby state, the secondary iGWB server does not generate CDR files.
l When the two iGWB servers are switched over, the original secondary iGWB server is in active state
and can generate CDR files. These CDR files are backed up on the third-party server. In this case,
contact the BC to check whether the serial numbers of the CDRs files are consistent.
Step 4 View the trace information and log file of the SmartBackup from the following paths:
The paths are:
l C:\Billsvr\bin\Trace
l C:\Log\SmartBackup
Step 5 Right-click the disk where the destination backup path is and then choose Properties >
General to check the disk space.
Make sure that there is sufficient disk space for you to back up CDR files for at least a day. If
there is insufficient disk space, add a new hard disk or remove the existing CDR files.
----End
Postrequisite
For details about the alarm parameters and the methods of rectifying the faults, see the iGWB
Troubleshooting.
3.3.2 Checking the CDR Backup Between the Two iGWB Servers
If the CDR files are backed up between the two iGWB servers, maintenance personnel must
check whether the CDR files are correctly backed up between the two iGWB servers on a daily
basis.
Prerequisite
The relevant settings are configured for backing up the CDR files between the two iGWB servers.
For details about how to configure these settings, see the iGWB Configuration Guide.
NOTE
In the following example, the primary iGWB server is in active state and the secondary iGWB server is in
standby state.
Context
You can use the SmartBackup to configure a backup task. For details, see the iGWB Installation
Guide.
l With the SmartBackup, you can check the source backup path in the Local directory
parameter of a backup task.
l With the SmartBackup, you can check the destination backup path in the Ftp directory
parameter of a backup task.
You can configure a backup task in the igwb.ini file. For details, see the iGWB Configuration
Guide.
l On the iGWB Parameter Configuration Console, you can specify the source backup path
in the SourceDir parameter of the BackupTask%d section.
l On the iGWB Parameter Configuration Console, you can specify the destination backup
path in the DestDir parameter of the BackupTask%d section.
%d indicates the backup task number. The value can be any positive integer number except 0.
Procedure
Step 1 Log in to the secondary iGWB server as Administrator. In the destination backup path, compare
the CDR files that were backed up one day ago with those generated in the source backup path
of the primary iGWB server.
If the numbers, sizes, and serial numbers of these CDR files are consistent, it indicates that the
CDR files generated on the primary iGWB server are all backed up on the secondary iGWB
server.
Step 2 Log in to the primary iGWB server as Administrator. Check whether the CDR files that were
backed up one day ago exit in the destination backup path. If any CDR file is found, compare
the CDR files with those generated in the source backup path of the secondary iGWB server one
day ago.
NOTE
l Normally, the primary iGWB server generates CDR files. These CDR files are backed up on the
secondary iGWB server. In standby state, the secondary iGWB server does not generate CDR files.
l When the two iGWB servers are switched over, the original secondary iGWB server is in active state
and can generate CDR files. These CDR files are backed up on the original primary iGWB server that
is currently in standby state. In this case, contact the BC to check whether the serial numbers of the
CDR are consistent.
Step 4 View the trace information and log file of the SmartBackup from the following paths:
l C:\Billsvr\bin\Trace
l C:\Log\SmartBackup
Step 5 Right-click the disk where the destination backup path is and then choose Properties >
General to check the disk space.
Make sure that there is sufficient disk space for you to back up CDR files for at least a day. If
there is insufficient disk space, add a new hard disk or remove the existing CDR files.
----End
Postrequisite
For details about the alarm parameters and the methods of rectifying the faults, see the iGWB
Troubleshooting.
Prerequisite
The relevant settings are configured for backing up the CDR files on a tape drive. For details
about how to configure these settings, see the iGWB Configuration Guide.
NOTE
As Administrator, perform the following steps on the primary and secondary iGWB servers.
Procedure
Step 1 Choose Start > Programs > Accessories > System Tools > Backup. In Backup, click the
Schedule Jobs tab. See Figure 3-1.
NOTE
If multiple icons are displayed, it indicates that multiple backup task are configured.
Step 2 CLick . In the Schedule Jobs Options dialog box, click the Backup details tab. The backup
path is specified in Device. See Figure 3-2.
By default, the backup files are suffixed with .bkf. In this example, the backup file is
iGWB_backup.bkf. The file name is specified during configuring the CDR backup.
Step 3 Click OK to close the Schedule Jobs Options dialog box. In Backup, click the Restore tab.
If it is your first time to open this tab, proceed with the next step. If you have opened this tab
before, skip Step 4.
Step 4 In the navigation tree, right-click and then choose Catalog File. In the Backup File
Name dialog box, click Browse to select a backup file, for example, E:\iGWB_backup.bkf. See
Figure 3-2. Click OK to catalog the backup file.
Step 5 In the navigation tree, click . In the Backup File Name dialog box, click Browse to select
a backup file, for example, E:\iGWB_backup.bkf. Click OK to catalog the backup file.
Step 6 From the navigation tree, click the item of the last day, for example, . In the
right pane, check whether any CDR file is displayed. If CDR files are displayed, check whether
the number, sizes, and serial numbers of these CDR files are consistent with those of the CDR
files in the source backup path.
NOTE
l Normally, only the iGWB server generate CDR files. Therefore, only the tape drive of the primary
iGWB server backs up CDR files. The tape drive of the secondary iGWB server does not back up CDR
files.
l When the two iGWB servers are switched over, the original secondary iGWB server is in active state
and can generate CDR files. These CDR files are backed up in the tape drive of the original secondary
iGWB server. In this case, contact the BC to check whether the serial numbers of the CDR are consistent.
----End
Postrequisite
For details about the alarm parameters and the methods of rectifying the faults, see the iGWB
Troubleshooting.
Context
Alarms related to the hard disk space:
l When the free space of the frontsave or backsave is less than 15% of the hard disk space,
the system generates the Insufficient iGWB Disk Space (Major) alarm.
l When the free space of the frontsave or backsave is less than 5% of the hard disk space,
the system generates the Insufficient iGWB Disk Space alarm.
Memory alarms:
l When the memory usage on the active iGWB server is higher than the memory threshold
(80% by default), the system generates the Insufficient Available iGWB Memory
(Major) alarm.
l When the memory usage on the active iGWB server is higher than the memory threshold
(95% by default), the system generates the Insufficient Available iGWB Memory alarm.
l When a memory error occurs on the active iGWB server, the system generates the iGWB
Memory Failure alarm.
CPU alarms:
l When the CPU usage on the active iGWB server is higher than the CPU threshold (80%
by default), the system generates the iGWB CPU Busy (Major) alarm.
l When the CPU usage on the active iGWB server is higher than the CPU threshold (95%
by default), the system generates the iGWB CPU Busy alarm.
l When a CPU error occurs on the active iGWB server, the system generates the iGWB CPU
Failure alarm.
Procedure
Step 1 Log in to the iGWB Client as admin. Choose Operation > State Query to check the free space
of the frontsave and the backsave.
NOTE
The frontsave space and the backsave space are displayed in the format of n/m. n indicates the free space.
m indicates the total space. The unit is MB.
Make sure that both of the frontsave and the backsave have at least 15% free space.
Step 2 Press Ctrl+Alt+Del and then click Task Manager. On the Processes and Performance tabs,
check the memory usage and CPU usage of the following processes:
l ap_proc.exe
l knl_proc.exe
l cls_proc.exe
l om_proc.exe
l cfg_proc.exe
l PWD.exe
NOTE
The memory usage and CPU usage must not exceed 80%.
Make sure that no hard disk alarms, memory alarms, or CPU alarms occur.
----End
Postrequisite
For details about how to handle alarms, see the iGWB Troubleshooting.
Procedure
Step 1 Log in to the iGWB.
Step 2 Log in to the iGWB Client as admin. Choose Operation > State Query to check the heartbeat
link states.
NOTE
The heartbeat link state is displayed in the format of n/m. m indicates the total number of heartbeat links.
n indicates the number of available heartbeat links.
On a standalone iGWB, if the heartbeat link state is 0/0, it indicates that the heartbeat link is normal. On a
two-node iGWB, if the heartbeat link state is 2/2, it indicates that the heartbeat link is normal.
----End
Procedure
Step 1 To check the free space of a tape, right-click the tape and then choose Properties > General.
NOTE
Make sure that the tape has sufficient space for you to back up CDR files for at least one day.
CAUTION
When the Tape indicator blinks, do not open the tape drive. Otherwise, data loss may be induced.
Wait for a few seconds for the tape drive to open. While waiting, do not power off the tape drive
or the computer.
----End
4 Weekly Maintenance
Weekly maintenance includes tasks, such as checking the device states, checking the security
protection of the iGWB devices, and backing up important files.
to iGWB Parameter
Config Console
cls_proc cfg_proc
cls_proc
As a process that runs on a two-node iGWB, the cls_proc process is used to start and manage
the knl_proc process.
knl_proc
The knl_proc process is also known as the kernel process. As a core process of the iGWB
application, this process is used to start and manage the ap_proc and om_proc processes.
l cls_proc
l ap_proc
l om_proc
ap_proc
Also known as the access point process, the ap_proc process is used to receive, process, and
cache CDR files.
The number of the ap_proc processes are specified in the igwb.ini file.
om_proc
As an operation and maintenance process, the om_proc process is used to connect the iGWB
Client to the System Debugger, delete CDR files, back up CDR files through network, and send
alarms.
cfg_proc
After the iGWB application is installed, the cfg_proc process can run independently. The
cfg_proc process is used to connect to the iGWB Parameter Config Console and manage the
igwb.ini file.
PWD
The PWD process is used to monitor the cls_proc process. In the OS, this process is monitored
by the Process Watch Dog Service.
Relationship Between the Processes of the iGWB and the Services of the OS
The following shows the relationship between the processes of the iGWB and the services of
the OS:
l The Cfg Server Service of the OS monitors the cfg_proc process of the iGWB.
l The Process Watch Dog Service of the OS monitors the PWD process of the iGWB.
Procedure
Step 1 As Administrator, perform the following steps on the primary and secondary iGWB servers.
l If the bulb is on ( ), it indicates that the current iGWB server is in active state. If the bulb is off
( ), it indicates that the current iGWB server is in standby state.
l Normally, at least six processes are running on the primary iGWB server. At least three processes are
running on the secondary iGWB server.
Step 3 Press Ctrl+Alt+Del. In the Windows Security dialog box, click Task Manager. On the
Processes tab, check the states of the related processes.
l knl_proc.exe
l ap_proc.exe
l om_proc.exe
l cls_proc.exe
l cfg_proc.exe
l PWD.exe
l bs_proc.exe (optional)
l mtr_proc.exe (optional)
l cls_proc.exe
l cfg_proc.exe
l PWD.exe
CAUTION
l The number of the ap_proc.exe processes on the primary iGWB server is the same as the
value of the APCount parameter in the Common section. The value of the APCount
parameter indicates the number of access points.
l Make sure that the process IDs (PID) are not changed.
----End
Procedure
Step 1 As Administrator, perform the following steps on the primary and secondary iGWB servers.
Step 2 In the My Computer window, right-click drive D and then choose Properties > General.
NOTE
Also, make sure that the OS and each disk drive use the NTFS format.
Step 3 On the Security tab, check whether the SYSTEM user is added and whether the SYSTEM user
has the Full Control permission of drive D.
----End
Context
l Process Watch Dog Service
The Process Watch Dog Service is used to monitor the PWD process. If the Process Watch
Dog Service is running, when the user closes a monitored application, the PWD process
automatically restarts the application.
l Cfg Server Service
The Cfg Server Service is used to monitor the cfg_proc process.
l FTP Publishing Service
The FTP Publishing Service is used to monitor the processes of FTP applications.
l Windows Time Service
The Windows Time Service is used to monitor the processes of NTP application. The NTP
application is used to maintain the GMT of the hosts on the Internet. If the iGWB is set to
the NTP Client, check the Windows Time Service.
l UM_PPT_Service Service
The UM_PPT_Service Service is used to monitor the processes of the i3SAFE SIS
SysPatron2003. If the i3SAFE SIS SysPatron 2003 is installed on the iGWB server, check
the UM_PPT_Service Service.
Procedure
Step 1 As Administrator, perform the following steps on the primary and secondary iGWB servers.
Step 2 Choose Start > Programs > Administrative Tools > Services.
Step 3 In the Services window, make sure that the states of the following services are started and that
the startup types of these services are automatic. The services include:
l Process Watch Dog Service
l Cfg Server Service
l FTP Publishing Service
l Windows Time (optional)
l UM_PPT_Service (optional)
Step 4 If a service is not in Started state, right-click the service and then choose Start to start the service.
Step 5 If the startup type of a service is not Automatic, right-click the service and then choose
Properties. On theGeneraltab, select Automatic in Startup type, and then click OK.
CAUTION
Avoid deregistration on the iGWB server. Otherwise, the Cfg Server Service cannot be
automatically started after the system restart. The user can only manually restart the service as
shown in Step 4.
----End
Context
Generally, the server list includes the following servers:
l IGWB0:
Set the IP address of iGWB0 to the fixed IP address of network interface 0 of the primary
iGWB server. For example, 129.9.1.2. Through this IP address, the iGWB Parameter
Config Console connects to the primary iGWB server.
l IGWB1:
Set the IP address of iGWB1 to the fixed IP address of network interface 0 of the secondary
iGWB server. For example, 129.9.1.3. Through this IP address, the iGWB Parameter
Config Console connects to the secondary iGWB server.
l IGWB_CLUSTER:
Set the IP address of IGWB_Cluster to the external virtual IP address of network adapter
0 of the primary or secondary iGWB server. For example, 129.9.1.1. Through this IP
address, the iGWB Client connects to the primary or secondary iGWB server.
Procedure
Step 1 As Administrator, log in to the PC where the iGWB Client is installed.
Step 2 Choose Start > Programs > iGateway Bill V300 Client > iGWB Client.
Step 3 In the Login dialog box, type the user name (admin) and password, select IGWB_CLUSTER
in Office Name, and then click OK to log in to the iGWB Client.
NOTE
If the The Version number is mismatched. Please be cautious in using. message is displayed, uninstall
the current iGWB Client and then re-install a correct version.
Step 4 On the iGWB Client, click . In the displayed dialog box, click Yes to exit the iGWB Client.
Step 5 Choose Start > Programs > iGateway Bill V300 Client > Parameter Configuration.
Step 6 In the User Logindialog box, type the user name (Config) and password, select IGWB0 in
Office and then click OK to log in to the iGWB Parameter Config Console.
Through a fixed IP addresses, maintenance personnel can log in to the iGWB Parameter Config Console
of the primary and secondary iGWB server at the same time.
Step 9 On the iGWB Parameter Config Console, click . In the displayed dialog box, click Yes to
exit the iGWB Parameter Config Console.
----End
Procedure
Step 1 To check whether the required system patches are installed, choose Start > Settings > Control
Panel > Add or Remove Programs.
Step 2 Check whether the antivirus software specified in the system configuration file is installed and
whether the antivirus software runs normally.
Step 3 Scan the computer for viruses. If any virus is detected, quarantine or clean the virus.
Step 4 Check whether the system and files are infected. Repair the infected system and files.
----End
Postrequisite
For details about how to plan and install antivirus software, see the iGWB Installation Guide.
Context
The igwb.ini file is the parameter configuration file of the iGWB server. Maintenance personnel
can use the iGWB Parameter Config Console to modify the parameter settings in this file.
l Running log
l Operation log
l Security log
NOTE
In some versions, the runtime log or the security log is not provided. In this case, skip Step 13 or Step
14.
Procedure
Step 1 As Administrator, log in to the PC where the iGWB Client is installed.
Step 2 In the User Login dialog box, select IGWB0 in Office and then log in to the iGWB Parameter
Config Console of the primary iGWB server as the Config user.
Step 3 Choose Operation > Office:IGWB0 > Save The Current Config Info As.
Step 4 In the Save As dialog box, specify a path and save the igwb.ini file as
igwb0.ini_YYYYMMDDHHMMSS.ini.
YYYYMMDDHHMMSS indicates the date and time to save the file. For example, if a file name
is igwb.ini_20070923162759.ini, it indicates that the file was saved on September, 23 of 2007,
at 16:27:59.
Step 6 In the Add Login dialog box, select IGWB1 in Office and then log in to the iGWB Parameter
Config Console of the secondary iGWB server as the Config user.
Step 7 Choose Operation > Office:IGWB1 > Save The Current Config Info As.
Step 8 In the Save As dialog box, specify a path and save the igwb.ini file as
igwb1.ini_YYYYMMDDHHMMSS.ini.
Step 9 On the iGWB Parameter Config Console, click on the toolbar. In the displayed dialog box,
click Yes to exit the iGWB Parameter Config Console.
Step 10 Log in to the iGWB Client as admin. On the iGWB Client, choose Security > Log Browse.
Step 11 Click on the toolbar. In the Set Log Browse Property dialog box, select Running log in
LogType, specify the start time and end time, and then click OK to view the running log.
Step 12 Select a log record and then click on the toolbar. In the Save Log Information dialog box,
select the log records to save and specify the path and the file name. By default, save the log file
as a .txt file.
Step 13 Repeat Step 11 through Step 12 to view the operation log. Also note that you must select
Operation log in LogType.
Step 14 Repeat Step 11 through Step 12 to view the security log. Also note that you must select Security
log in LogType.
----End
5 Monthly Maintenance
Monthly maintenance includes tasks such as checking the system time on the iGWB server,
checking the function of sending alarms, checking the parameter settings, checking the functions
of processing CDR files, and cleaning the magnetic head of the tape drive.
Procedure
Step 1 Log in to the LMT of the softswitch and check the system time.
Step 2 As Administrator, perform the following steps on the primary and secondary iGWB servers.
CAUTION
In version 300R001C15 version or an earlier version, setting the system time may cause
abnormal CDR files. In this case, to correctly set the system time, contact Huawei by dialing the
customer service number provided in the title page.
Step 4 In the Time group box on the Date & Time tab, if the time on the iGWB server is not consistent
with that on the softswitch, change the time on the iGWB server. To change the time, double-
click the hour, minute, or second, and then click the arrows to increase or decrease the value.
Then click OK.
Step 5 Check whether the Windows Time service runs normally. If the service runs normally, it
indicates that the NTP process runs normally.
For more details, see 4.1.4 Checking the Services of the iGWB Server.
----End
Context
Procedure for sending alarms by the iGWB:
iGWB as a component of the softswitch, the iGWB does not send alarms to the NMC through
the SNMP protocol. The alarms generated by the iGWB are reported to the BAM in binary mode
and are then sent from the BAM to the NMC.
To perform this task, maintenance personnel must have the operation permissions of the NMC
and the BAM.
Procedure
Step 1 As Administrator, log in to the PC where the iGWB Client is installed.
Step 2 In the User Login dialog box of the iGWB Parameter Config Console, attempt to log in to the
iGWB Parameter Config Console by entering an incorrect user name or password for three times.
Step 3 Log in to the NMC to check the alarms generated by the iGWB.
Step 4 Log in to the BAM to check the alarms generated by the iGWB.
NOTE
If the function of sending alarms works normally, the NMC and the BAM can receive the alarms from the
iGWB.
----End
Procedure
Step 1 As Administrator, log in to the PC where the iGWB Client is installed.
Step 2 In the User Login dialog box of the iGWB Parameter Config Console, select IGWB0 in Office
Name and then log in to the iGWB Parameter Config Console of the primary iGWB server as
the Config user.
Step 4 In the Add Login dialog box, select IGWB1 in Office Name and then log in to the iGWB
Parameter Config Console of the secondary iGWB server as the Config user.
Step 5 In the main window of the iGWB Parameter Config Console, compare the parameter settings
of the primary and secondary iGWB servers.
Make sure that, except the following parameters, the settings of the other parameters of the two
iGWB servers are consistent.
l ServerNo in the Common section
l LocalIP and PeerIP in the Link%d section
l OrginalIP in the Resource%d section
l LocalIP in the NetBackup and BackupTask%d sections
NOTE
In different cases, the DestHostIP parameter in the NetBackup and BackupTask%d sections can be
consistent or not.
%d of the parameter sections can be any positive integer. For example, BackupTask1 and BackupTask2.
For details about the parameter settings, see the iGWB Configuration Guide.
----End
5.4.1 Checking the Receiving and Processing of the Original CDR Files
To make sure that the iGWB can correctly receive and store the original CDR files, check the
CDR files generated after a call.
5.4.2 Checking the Function of Sending Final CDRs
Maintenance personnel must check the final CDR files to ensure that these files can be
successfully sent to the BC.
Prerequisite
To perform the checking, maintenance personnel need to work with the softswitch operators.
Context
If the original CDRs from the CDR processing module contain errors (such as incorrect CDR
lengths, incorrect CDR types, and duplicate CDRs), or errors occur when the original CDRs are
coded or encoded, the iGWB generates the Abnormal iGWB CDR alarm.
Procedure
Step 1 Softswitch operators must configure two testing numbers, record the types of the generated CDR
files, and initiate a call.
Step 2 Log in to the iGWB Client as admin. Choose View > Refresh or press F5.
Step 3 In the navigation tree, expand the node of an original CDR file and then double-click a date
node.
For example, the 20070923 folder stores the CDR files that were generated on September 23,
2007.
Step 4 Double-click the CDR file that was lastly generated. In the Choose Bill Format For File
Brow dialog box, select the CDR type recorded in Step 1 and then click OK. In the displayed
dialog box, ensure that the CDR files generated in Step 1 are displayed.
Step 5 Double-click a CDR file. In the Bill Detailed Information dialog box, check whether the
relevant information is correct. The information include the caller, callee, call duration, and CDR
type.
Step 6 Click OK to close the Bill Detailed Information dialog box.
Step 7 In the Final Bill navigation tree, select the related channel. Double-click the date node to check
the largest CDR serial number.
For example, the channel names are detail. For details about how to configure a channel name,
see the iGWB Configuration Guide.
Step 8 On the iGWB Client, choose Operation > Trigger File Closing.
Step 9 In the Final Bill navigation tree, select the related channel. Double-click the date node to check
the largest CDR serial number.
If the CDR serial number is 1 larger than that obtained in Step 7, it indicates that a new final
CDR file is manually generated.
Some CDR files that are automatically generated may be blank CDR files, that is, the sizes of
these CDR files are 0 KB. The reasons of blank CDR files are:
l The iGWB is configured to generate final CDR files at a specified time.
l The iGWB is configured to generate final CDR files.
Step 10 Check the related information, including the caller, callee, call duration, and CDR type.
----End
Postrequisite
For details about how to handle alarms, see the iGWB Troubleshooting.
Prerequisite
To perform the checking, maintenance personnel need to work with the softswitch operators.
Context
If the BC does not fetch the CDR files from the monitoring directory for a long time, the
iGWB generates the Billing Center Not Fetch iGWB CDRs for a Long Time alarm.
Procedure
Step 1 Log in to the BC. Check whether the contents and number of the CDR files received on the BC
are consistent with those on the iGWB.
Step 2 Check whether the BC can parse the CDR files from the iGWB and generate the required final
CDR files.
----End
Postrequisite
For details about how to handle alarms, see the iGWB Troubleshooting.
Prerequisite
When the Clean indicator turns on, it indicates that you need to clean the magnetic head.
Context
If the magnetic head is covered with dust or scrap, the tape drive may not read or write data.
Therefore, you need to periodically clean the magnetic head.
Use the unused tape section to clean the magnetic head. Do not rewind the cleaning tape. A
cleaning tape can clean 30 tapes.
Procedure
Step 1 Press the Open button and take the tape out. Label both sides of the tape, for example, A and
B. Insert a cleaning tape.
CAUTION
l When the Tape indicator blinks, it indicates that the tape drive is reading or writing the tape.
Meanwhile, do not press the Open button. Otherwise, data loss may be induced.
l After you press the Open button, wait for a few seconds for the tape drive to open. While
waiting, do not power off the tape drive or the computer.
l Use recognized cleaning tapes only.
After inputting the cleaning tape, the tape drive automatically identifies the cleaning tape and
plays the cleaning tape to clean the magnetic head for 30 minutes. After the cleaning, the tape
drive ejects the cleaning tape.
Step 2 After cleaning the magnetic head, take out the cleaning tape and input the tape back to the tape
drive.
----End
6 Yearly Maintenance
Yearly maintenance includes tasks such as checking the switchover of the primary and secondary
iGWB servers, checking the restart of the devices, and checking the cable connections.
Context
The switchover function enables the primary iGWB server and the secondary iGWB server
switch over with each other. After the switchover, the original active iGWB server is in standby
state whereas the original standby iGWB server is in active state. Two switchover modes are
provided:
l In manual switchover mode, maintenance personnel have to manually switch the primary
and secondary iGWB servers. This mode is used during the process of maintenance or
version upgrade.
l In automatic switchover mode, when the primary iGWB server is faulty, the primary and
secondary iGWB servers are automatically switched.
NOTE
The primary iGWB server takes a higher priority over the secondary iGWB server. Therefore, when the
secondary iGWB server is restarted, the primary and secondary iGWB servers are switched over. However,
when the primary iGWB server is restarted, the primary and secondary iGWB servers are not switched
over.
When the maintenance personnel manually switch the primary and secondary iGWB servers,
the Manual Switchover of iGWB alarm is generated on the active iGWB server.
Procedure
Step 1 Log in to the primary iGWB server as Administrator. In the notification area, check the bulb.
iGWB0 refers to the primary iGWB server and iGWB1 refers to the secondary iGWB server.
If the bulb is on ( ), it indicates that the current iGWB server is in active state. If the bulb is
off ( ), it indicates that the current iGWB server is in standby state.
Step 2 As Administrator, log in to the PC where the iGWB Client is installed.
CAUTION
The switchover of the primary and secondary iGWB servers is risky. It is recommended to
perform the switchover when the traffic volume is low.
To check the automatic switchover of the primary and secondary iGWB servers, make sure to
restart the secondary iGWB server.
l When the primary iGWB server is in active state and the secondary iGWB server is in standby
state, perform the following steps.
l For the case where the secondary iGWB server is in active state and the primary iGWB server
is in standby state, switch Step 4 and Step 7.
Step 3 In the User Login dialog box, type the user name (admin) and password, select
IGWB_CLUSTER in Office, then click OK to log in to the iGWB Client on the primary iGWB.
Step 4 Choose Operation > Switch. In the displayed dialog box, click Yes to confirm the manual
switchover.
Step 5 In the status bar, ensure that the iGWB Client is disconnected.
Step 6 Click and then log in to the iGWB Client of the secondary iGWB server as admin.
Step 7 Choose Operation > Reset iGWB. In the displayed dialog box, click Yes to confirm the restart.
Step 8 In the status bar, ensure that the iGWB Client is disconnected.
Step 9 Click and then log in to the iGWB Client as admin. In the status bar, ensure that the iGWB
Client is connected.
Log in to the original active iGWB server to ensure that the two iGWB servers are switched to
original states.
----End
Context
CAUTION
Restarting the iGWB is risky. It is recommended to reduce the times of restart. It is also
recommended to restart the iGWB when the traffic volume is low.
During the restart of the iGWB, if either of the following cases is encountered, CDR serial
numbers may be inconsistent.
l No final CDR files are generated in E:\backsave\accesspoint\temp.
l The BC has not fetched the final CDR files from E:\backsave\Second\accesspoint.
After the iGWB is restarted and activated, the iGWB Reboot alarm is generated.
Procedure
Step 1 Log in to the standby iGWB server as Administrator and then choose Start > Settings >
Control Panel > Administrative Tools > Services .
Normally, the secondary iGWB server is in standby state. After switchover, the primary iGWB
server is in standby state.
Step 2 In the Services window, right-click Process Watch Dog Service and then choose Stop.
Step 3 To stop the iGWB Server, choose Start > Programs > iGateway Bill V300 Server > Stop
iGateway Bill.
Step 4 To restart the device, choose Start > Shut Down > Restart .
Step 5 After restart, press Ctrl+Alt+Del. In the Windows Security dialog box, click Task Manager.
On the Processes tab, ensure that the following processes are running normally:
l cls_proc.exe
l cfg_proc.exe
l PWD.exe
Step 6 Log in to the iGWB Client as admin. Then choose Operation > Switch . In the displayed dialog
box, click Yes to confirm the manual switchover.
Step 7 After restart, repeat Step 1 through Step 6.
Step 8 Check with the BC for any inconsistent CDR serial number.
----End
Postrequisite
For details about how CDR files are generated, see the iGWB Configuration Guide. For details
about how to handle alarms, see the iGWB Troubleshooting.
Procedure
Step 1 Ensure that the cables are intact and firmly connected to the iGWB.
Step 2 Ensure that the labels on the cables are clear.
----End
7 Appendix
This appendix provides useful information about routine maintenance, including the user types
of the iGWB, directory structures for storing CDR files on the iGWB server, directory structure
for the iGWB, important files, channel description, and maintenance records.
Normal iGWB user This is a normal user Configure the user Set the password in
of the iGWB Client. name in the the Operator
Operator Management
Management window on the
window on the iGWB Client.
iGWB Client.
Table 7-3 lists the commands used by the users of the iGWB on the iGWB Client.
l Add a user
l Query a user
l Modify user properties
Operator Management l Modify the permission of a user
l Modify the operation duration of a user
l Delete a user
l Disconnect a user connection
Category Description
l Query a log
l Save a log
Log browsing
l Print a log
l Clear the queried log information
NOTE
l The admin user of the iGWB possesses the permission of using these commands.
l A common user of the iGWB possesses the permission of using only part of or all of these commands.
date
...
date
...
Under D:\frontsave\, the original CDR files are stored in the corresponding date folders
contained in the access point folders.
The name of an original CDR file takes the format of b*.bil. The asterisk (*) indicates a CDR
serial number. The value ranges from 0000000001 to 9999999999. For example, D:\frontsave
\X3KF\20070923\b0000000009.bil is the 9th original CDR file generated for the X3KF access
point on September 9, 2007.
E:\backsave\
date channel 1
date channel 2
channel 2
The final CDR files are stored in two copies under E:\backsave\.
l Under E:\backsave\, the first copies of the final CDR files are stored in the corresponding
date folders contained in the channel folders of the access point folders.
l Under E:\backsave\Second\, the second copies of the final CDR files are stored in the
corresponding channel folders contained in access point folders.
The second copies of the final CDR files are open to the BC. After the BC fetches these files,
these files are immediately deleted from the folders under E:\backsave\Second\.
The name of a final CDR file takes the format of b*.dat. The asterisk (*) indicates a CDR serial
number. The value ranges from 0000000001 to 9999999999.
Table 7-4 shows the directory structure for the iGWB Server.
Table 7-5 lists the directory structures for the alarm files, log files, and status files.
Table 7-5 Directory structures for the alarm files, log files, and status files
Path Description
Path Description
File Description
Table 7-7 lists the directory structures for the alarm files, log files, and status files.
Table 7-7 Directory structures for the alarm files, log files, and status files
D:\other\log\*.log or D:\other\log\*.xml The log file of the iGWB. The log file is
suffixed with .log (default) or .xml. The log
file can be specified in the igwb.ini file.
The asterisk (*) indicates the date when the
log file was generated. For example,
20070923.log or 20070923.xml.
Channels
A channel refers to the path for storing final CDR files by category. Each channel can store only
one type of final CDR files.
Channel Description
in IN Bill
Exceptions
and solutions
Unfixed
issues
Exceptions and
solutions
Unfixed issues
Exceptions and
solutions
Unfixed issues
Exceptions and
solutions
Unfixed issues
Result:
Unsolved issues:
B
BAM Back Administration Module
BC Billing Center
C
CMOS Complementary Metal Oxide Semiconductor
CPU central processing unit
F
FTP File Transfer Protocol
I
ID identification/identity
IP Internet Protocol
K
KVMS Keyboard, video, mouse (KVM) switch
L
LAN local area network
M
MML Human-Machine Language
N
NTFS NT File System
NTP Network Time Protocol
P
PC personal computer
PID process ID
PWD Process Watch Dog
S
SCR Silicon Control Rectifier
T
TCP Transport Control Protocol
TTL Transistor-Transistor Logic