Huawei CG9812
Huawei CG9812
Huawei CG9812
i
1-1
1-1
1-1
1-1
1-3
1-4
2-1
2-1
2-1
2-1
2-1
2-1
2-1
2-2
2-2
3-1
3-1
3-1
3-1
3-2
3-3
3-5
3-5
3-7
3-8
3-9
3-9
3-9
3-9
3-9
3-11
3-11
4-1
4-1
4-1
4-1
4-1
4-1
4-1
4-3
4-3
5-1
5-1
5-1
5-1
5-2
5-2
5-2
5-3
6-1
6-1
6-1
6-1
6-1
6-2
6-2
6-2
6-2
6-2
6-3
6-3
6-3
6-3
6-3
6-3
6-4
7-1
7-1
7-1
7-1
7-1
7-2
7-2
7-2
7-2
7-3
7-3
7-5
7-7
i
1-1
1-1
1-1
1-1
1-2
1-3
1-3
1-4
1-6
1-6
1-7
1-8
2-1
2-1
2-1
2-3
2-3
2-5
2-6
2-7
2-7
2-8
2-8
2-10
2-15
3-1
3-1
3-1
3-1
3-1
3-4
4-1
4-1
4-1
4-1
4-2
4-7
4-7
4-10
4-10
4-11
4-12
4-13
4-13
4-14
4-15
4-15
4-15
4-16
4-16
4-16
4-17
4-17
4-17
4-17
5-1
5-1
5-1
5-1
5-3
5-3
5-3
5-3
5-3
5-10
5-13
5-14
5-15
5-15
5-16
5-17
5-17
5-18
5-18
5-18
5-19
5-19
5-19
5-20
5-21
5-24
5-25
5-26
5-26
6-1
6-1
6-1
6-1
6-1
6-3
6-4
6-11
6-14
7-1
7-1
7-1
7-1
7-1
7-4
7-6
7-7
7-9
7-9
7-11
7-13
8-1
8-1
8-1
8-6
8-8
i
1-1
1-1
1-1
1-1
1-2
1-3
1-3
1-5
1-6
1-6
1-7
1-8
2-1
2-1
2-1
2-2
2-2
2-5
2-6
2-7
2-7
2-7
2-8
2-8
2-11
2-14
3-1
3-1
3-1
3-1
3-1
3-2
3-26
4-1
4-1
4-1
4-1
4-1
4-9
4-9
4-12
4-12
4-13
4-14
4-15
4-15
4-16
4-17
4-17
4-17
4-17
4-18
4-18
4-18
4-18
4-19
5-1
5-1
5-1
5-1
5-2
5-3
5-3
5-3
5-3
5-7
5-9
5-10
5-11
5-12
5-12
5-13
5-14
5-14
5-14
5-15
5-15
5-16
5-16
5-16
5-17
5-22
5-22
5-23
5-23
6-1
6-1
6-1
6-1
6-1
6-2
6-3
6-10
6-13
7-1
7-1
7-1
7-1
7-1
7-4
7-6
7-7
7-9
7-9
7-11
7-13
8-1
8-1
8-1
8-6
8-8
i
1-1
1-1
1-6
1-6
1-9
1-9
1-10
1-11
1-11
1-12
1-13
1-15
1-16
1-17
1-18
1-19
1-19
1-20
1-20
1-21
1-22
1-23
1-23
1-24
1-26
1-28
1-28
1-29
1-31
1-31
1-32
1-34
1-37
1-38
1-39
1-39
1-41
1-42
1-42
1-43
1-44
1-45
1-46
1-46
1-47
1-48
1-49
1-49
1-50
1-51
2-1
2-1
2-1
2-2
2-2
3-1
3-1
3-1
3-1
3-2
3-2
3-3
3-3
3-3
3-3
i
1-1
1-1
1-1
1-2
1-6
2-1
2-1
2-1
2-3
2-3
2-4
2-4
2-6
2-6
2-8
2-8
2-10
2-10
2-11
2-12
2-13
2-13
2-14
2-15
2-15
2-18
2-20
2-22
2-22
2-23
2-25
2-27
2-28
2-29
2-29
2-32
2-34
2-34
2-35
2-36
2-37
2-38
2-39
2-40
2-41
2-42
2-44
2-45
2-46
2-46
2-47
2-48
2-49
i
1-1
1-1
1-1
1-1
1-1
1-3
1-5
1-6
2-1
2-1
2-1
2-2
2-3
3-1
3-1
3-1
3-3
3-4
3-5
3-5
3-5
3-5
3-6
3-6
3-6
3-7
3-7
3-7
3-7
3-8
3-8
3-8
3-9
3-9
3-9
3-9
4-1
4-1
4-1
4-2
4-2
4-3
4-4
4-4
4-5
4-5
4-6
4-7
4-7
4-8
4-8
4-9
4-10
5-1
5-1
5-2
5-2
5-3
5-3
5-4
5-4
5-5
5-5
5-5
5-6
5-6
5-7
5-7
5-7
5-8
5-8
5-9
5-9
5-10
5-10
5-11
5-11
5-11
5-12
Appendix
Table of Contents .........................................................................................
Appendix A Common UNIX Commands ......................................................
A.1 Introduction to the Chapter ...............................................................
A.2 Common Operations in UNIX System ..............................................
i
A-1
A-1
A-1
Index ................................................................................................
A-6
A-6
A-7
A-7
B-1
HUAWEI
System Description
System Installation (Netra 240)
System Installation (Netra 20)
Parameter Configuration and System
Commissioning
Basic Operations
System Maintenance
Appendix
HUAWEI CG9812
User Manual
V200R002
HUAWEI CG9812
User Manual
Manual Version
T2-030187-20050728-C-2.23
Product Version
V200R002
BOM
31013387
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support
and service. Please feel free to contact our local office or company headquarters.
Trademarks
Notice
All other trademarks mentioned in this manual are the property of their respective
holders.
The information in this manual is subject to change without notice. Every effort has
been made in the preparation of this manual to ensure accuracy of the contents, but
all statements, information, and recommendations in this manual do not constitute
the warranty of any kind, express or implied.
Part II System Installation (Netra 240) details the installation and configuration
of the CG9812 when SUN Netra 240 is used as the server of the CG9812.
Part II System Installation (Netra 20) details the installation and configuration of
the CG9812 when SUN Netra 20 is used as the server of the CG9812.
Appendix B Abbreviations lists the full names of the acronyms and abbreviated
used in the manual.
Intended Readers
The manual is intended for the following readers:
z
Installation engineers
Conventions
The manual uses the following conventions:
I. General conventions
Convention
Description
Arial
Arial Narrow
Terminal Display
Description
<>
[]
Window names, menu items, data table and field names are
inside square brackets. For example, pop up the [New User]
window.
Description
<Key>
Press the key with the key name inside angle brackets. For
example, <Enter>, <Tab>, <Backspace>, or <A>.
<Key1+Key2>
IV. Symbols
Eye-catching symbols are also used in this document to highlight the points worthy of
special attention during the operation. They are defined as follows:
Environmental Protection
This product has been designed to comply with the requirements on environmental
protection. For the proper storage, use and disposal of this product, national laws and
regulations must be observed.
HUAWEI
HUAWEI CG9812
User Manual
Table of Contents
Table of Contents
Chapter 1 Introduction to the CG9812......................................................................................... 1-1
1.1 Orientation ......................................................................................................................... 1-1
1.2 Position of CG9812 in UMTS/GPRS Network ................................................................... 1-1
1.2.1 Network Architecture............................................................................................... 1-1
1.2.2 External Interfaces .................................................................................................. 1-3
1.3 CG9812 Networking Implementation................................................................................. 1-4
Chapter 2 Key Benefits ................................................................................................................. 2-1
2.1 Introduction to the Chapter ................................................................................................ 2-1
2.2 System Features................................................................................................................ 2-1
2.2.1 Multi-access ............................................................................................................ 2-1
2.2.2 Flexible CDR Format Conversion ........................................................................... 2-1
2.2.3 Large Capacity and Powerful Processing Capability .............................................. 2-1
2.2.4 High Reliability......................................................................................................... 2-1
2.2.5 Scalability ................................................................................................................ 2-2
2.3 Networking Capability ........................................................................................................ 2-2
Chapter 3 System Architecture.................................................................................................... 3-1
3.1 Introduction to the Chapter ................................................................................................ 3-1
3.2 Hardware Architecture ....................................................................................................... 3-1
3.2.1 Appearance of CG9812 Cabinet ............................................................................. 3-1
3.2.2 Cabinet Configuration ............................................................................................. 3-2
3.2.3 Typical Configuration .............................................................................................. 3-3
3.3 Functional Architecture ...................................................................................................... 3-5
3.3.1 Logical Architecture................................................................................................. 3-5
3.3.2 CG9812 Network Adapters ..................................................................................... 3-7
3.3.3 Communicating with the GSN ................................................................................. 3-8
3.3.4 Communicating with the Billing Center ................................................................... 3-9
3.3.5 Communicating with the LMT and the NMS ........................................................... 3-9
3.3.6 Heartbeat Path ........................................................................................................ 3-9
3.4 Software Architecture ........................................................................................................ 3-9
3.4.1 Key Terminologies................................................................................................... 3-9
3.4.2 Overall Architecture............................................................................................... 3-11
3.4.3 Service Processes ................................................................................................ 3-11
Chapter 4 Services and Functions .............................................................................................. 4-1
4.1 Introduction to the Chapter ................................................................................................ 4-1
4.2 Network Functions ............................................................................................................. 4-1
4.2.1 Interface to GSN...................................................................................................... 4-1
4.2.2 Interface to Billing Center........................................................................................ 4-1
Huawei Technologies Proprietary
i
Table of Contents
Table of Contents
GGSN
WAN
CG server
DDN/E1/X.25
TCP/IP
Ga
Billing center
FTP/FTAM
R
MML
SGSN
Ga
CDR collector
MML
NM center
Equipment room
NM center
I. GSN
The CG9812 is interconnected with the GSN through LAN or WAN. A separate
10M/100M network adapter is provided on the CG9812 for this purpose.
The CG9812 supports the simultaneous accesses from the GSN (GGSN/SGSN) with
different versions. The GSN transfers CDRs in real time to the CG9812. Then the
CG9812 processes the CDRs and generates the final ones which will be transferred to
the billing center.
In the case of FTP, the CG9812 supports two modes, that is, the PULL mode and
the PUSH mode. In the PULL mode, the CG9812 acts as the server, and the CDR
collector as the client. The CDR collector collects the CDR file from the CG9812.
Huawei Technologies Proprietary
1-2
In the PUSH mode, the CG9812 acts as the client, and the CDR collector acts as
the server. The CG9812 sends the CDR file to the billing center.
z
In the case of FTAM, the CG9812 supports the PULL mode. It acts as the
responder, and the CDR collector acts as the initiator in a way similar to FTP
communication. The CDR collector collects the CDR file from the CG9812.
OSS
FTP/FTAM
MML
M2000
BC
Core Network
Ga
GSN(GGSN/SGSN)
CG9812
Interface name
Applied protocol
GSN(GGSN/SGSN)CG
Ga
GTP
CGBilling Center
FTP/FTAM
CGNMS
O&M Interface
System Features
Networking Capability
The storage device is highly secured with 1+1 backup, each of which adopts
RAID5 plus hotspare.
Key interface/Path redundancy for the Ga interface and CG-BC interface. For
reliable communication, the CG9812 can connect to a SGSN, GGSN and BC
respectively by two redundancy links.
The CDRs can be transferred in real time to multiple remote workstations for
backup and reserved there for a pre-defined or configured period before being
deleted automatically. When required by the billing center, these CDRs can be
reopened to the billing center.
At least two copies of system data are kept in separate locations for redundancy
and in case of any accident. These copies of system data will be loaded and
validated against each other automatically by the restoration or recovering
process.
The whole system can be backed up to the tape drive regularly. In this case, you
can recover the system if a fault occurs.
2.2.5 Scalability
The CG9812 employs a modular structure. It is convenient and flexible in capacity and
function expansion, for which new modules can be added to import new functions and
technologies and to extend application areas.
When the capacity of the CG9812 need to be expanded to satisfy the requirement of
increased system capacity, the following measures can be considered, including
adding CPU and memory, adding hard disks, and so on.
Hardware Architecture
Functional Architecture
Software Architecture
If Netra 240 minicomputer is employed for the UNIX platform, the internal
configuration of the cabinet is shown in Figure 3-2.
CG9812 Cabinet
Power distribution frame (2U)
Quidway 3528G-1 (1U)
Cabling frame1U
Quidway 3528G-0 (1U)
Cabling frame (1U)
Dummy panel (3U)
Dummy panel (3U)
Dummy panel (3U)
Dummy panel (3U)
Dummy panel (3U)
46U
Figure 3-2 Configuration of cabinet (with Netra 240 plus StorEdge 3310)
2)
CG9812 Cabinet
Power distribution frame (2U)
Dummy panel (3U)
Dummy panel (3U)
Dummy panel (3U)
Dummy panel (3U)
Dummy panel (3U)
Dummy panel (3U)
Non-standard dummy panel (1U)
Quidway 3526-1 (1U)
Cabling frame (1U)
Quidway 3526-0 (1U)
Cabling frame (1U)
Non-standard dummy panel (1U)
TC (Perle LOLAN) (1U)
SUN StorEdge 3310-1 (2U)
Non-standard dummy panel (1U)
SUN StorEdge 3310-0 (2U)
Non-standard dummy panel (1U)
SUN Netra 20-1 (4U)
Non-standard dummy panel (1U)
SUN Netra 20-0 (4U)
Components
Vendor/Model
Quantity
Description
Each Sun Netra 240
configuration:
z
Mini computer
2 PCS
z
z
z
Sun StorEdge
3310
Disk array
LAN switch
Huawei
Quidway
S3528G
2 PCS
SCSI card: 2*
bi-channel SCSI card
Hard disk: 5*73 GB
NA
Components
Vendor/Model
Quantity
Description
Each Sun Netra 20
configuration:
z
z
Mini computer
Sun Netra 20
2 PCS
z
z
z
Sun StorEdge
3310
Disk array
Terminal
concentrator
Perle LOLAN or
others
1 PCS
NA
LAN switch
Huawei
Quidway S3526
2 PCS
NA
SCSI card: 2*
bi-channel SCSI card
Hard disk: 5*73 GB
Note:
Because minicomputer might be updated, the minicomputer module might be different
from the actually delivered model.
Logical Architecture
Heartbeat Path
To BC
float IP
float IP
LAN
LAN
LAN
Maintenance terminal
NAFO
NET Mgt
NAFO
NET Mgt
bge0,bge1,bge2,bge3
Netra 240-0
bge0,bge1,bge2,bge3
ce0
Private network
ce0
Netra 240-1
Heartbeat
Mirror
ce1
ce1
SCSI card
Mirror
SCSI card
3310-0
Mirror
3310-1
To GSN
To BC
float IP
float IP
LAN
LAN
LAN
TC 1 2 3 4
NAFO
NAFO
ttya
ttya
qfe0,qfe1qfe2,qfe3
qfe0,qfe1,qfe2,qfe3
eri0
Netra 20-0
Private network
eri0
Netra 20-1
Heartbeat
Mirror
hme0
hme0
SCSI card
Mirror
SCSI card
3310-0
Mirror
3310-1
Network
adapters of
Netra 20
bge0
qfe0
bge1/bge2
qfe1/qfe2
bge3
qfe3
ce0
eri0
Heartbeat link 1.
ce1
hme0
Heartbeat link 2.
No.
Function
The bge1 (qfe1 for Netra 20) of the active/standby CG9812 server connects with
the LAN Switch-0 and forms the active plane.
The bge2 (qfe2 for Netra 20) of the active/standby CG9812 server connects with
the LAN Switch-1 and forms the standby plane.
The two core LAN Switches are interconnected via the cascade cables.
I. Access Point
To access the GSNs of different release versions, access point is used in the design
of the CG9812. Based on the parameter configuration and operation maintenance, one
access point is associated with one ap_proc process. This process realizes the
modules that communicate with the GSNs and the modules that store and convert the
CDRs.
II. Channel
Channel is a logical concept. A channel refers to the CDR processing modes and
storage directories that match a certain distinguishing condition. Simply speaking, one
channel is associated with one CDR storage path. Only the back save disk has the
channel.
V. Format Library
The format library is the core that the CG9812 converts the CDRs. It is associated with
one format conversion module (dynamic link library) and a series of format
configuration files. The format library is designed to make the CDR format dynamically
configurable, but not hard-coded.
VI. Active/Standby
Active/standby is a pair of basic concepts for a cluster system. In a cluster system, if a
node provides external services, its state is called active. If a node currently does not
provide external services, its state is called standby.
VII. Primary/Secondary
Primary/secondary is a basic concept for a cluster system. In a cluster system, two
nodes may be peered or not peered. If they are not peered, then they can be defined as
primary or secondary. In this case, one node will be set with higher priority. If this node
runs normally, it has the priority to control the resources of the cluster system.
VIII. Resources
The physical equipment and logical equipment that are shared by the nodes of the
cluster system are called resources, such as shared storage media, and float IP
address.
GSN
Access
point
process
Kernel process
Operation &
maintenance
process
iGWB
Client
Parameter
configuration
process
CG9812 Server
I. Kernel Process
The kernel process is the core of the whole software. It acts as the Transmission
Control Protocol/Internet Protocol (TCP/IP) server for the other processes. It is
responsible for starting, stopping, and monitoring the access point process and the
operation and maintenance process.
GSN
Generates and
transmits bills
FTP/FTAM
Billing
center
Network functions and service functions are described in this chapter. Operation &
maintenance functions are described in Chapter 5 Operation and Maintenance.
I. Collecting CDRs
The CG collects CDRs from SGSN/GGSN. Currently, the supported CDR formats
include S-CDR, G-CDR, M-CDR, S-SMO-CDR, S-SMT-CDR, LCS-MT-CDR,
LCS-MO-CDR, and LCS-NI-CDR. The last three types of CDRs are only available in
R4 or later versions.
Consolidating CDRs
Sorting CDRs
The CG raises the concept of channel. The CG stores the collected CDRs to different
channels according to some sorting condition. The sorting conditions are configurable.
Currently, the supported modes include sorting by CDR type and by billing feature.
3)
The CG supports CDR validity confirmation. The CG decodes the collected CDRs. The
error CDRs, possibly caused by SGSN/GGSN or network errors, cannot be decoded by
CG and cannot be sent to the billing center.
The CDR collected from SGSN/GGSN system and not processed by CG is called an
original CDR.
The CG supports original CDR storage. The original CDRs are stored in physical media
for some days (configurable) before they are deleted.
2)
The CDR processed by CG is called a final CDR, which will be transferred to the billing
center.
The CG supports final CDR storage. The final CDRs are stored in physical media for
some days (configurable) before they are deleted.
V. Auto-backup CDRs
The CG supports auto-backup of original and final CDRs. After proper configuration,
the CDRs can be backed up to local or remote disks or other storage media.
OMC Networking
LMT
LAN/
WAN
LAN
iManager
M2000
GGSN/SGSN
WAN
Billing Center
CG9812
Security Management
Configuration Management
Performance Management
Fault Management
Heartbeat
CPU usage
System Self-Test
Alarm Management
Maintenance Management
Trace Management
Detect and report in real time any fault or abnormity of the equipment
Generate audio and visual alarm signals through the alarm box
Including
Equipment state query
Tracking diameter message
CDRs Management
CDRs Statistics
Printing CDRs
Including
Setting software parameters, and so on
V. Trace Management
The CG9812 trace management function supports to trace protocol messages and
workflow messages. The protocol message means messages exchanged between the
CG9812 and the GSN. The workflow message means internal workflow messages
exchanged between the thread service modules and/or processes. The tracing
messages can be output and displayed in real-time on LMT. This function helps to
locate and fix the network or communication problems.
Chapter 6 Reliability
Chapter 6 Reliability
6.1 Introduction to the Chapter
CG9812 is a bill handling and cache device. Its reliability design covers system,
hardware and software.
This chapter contains the following sections:
z
System Reliability
Hardware Reliability
Software Reliability
Feature
Servers
Chapter 6 Reliability
The LMT, developed as a friendly GUI tool with abundant O&M functions, is
convenient and practical for the O&M of the CG9812.
The servers support automatic or manual switchover, and the disk arrays can be
hot-pluggable.
Adopting distributed power supply scheme, and supplying power by the redundant
high-frequency DC. This scheme features high efficiency and excellent stability.
Adopting N+1 backup design to ensure the reliability of the power system.
The storage device is highly secured with 1+1 backup, each of which adopts
RAID5 plus hotspare.
Chapter 6 Reliability
Task monitoring
Storage protection
Data check
Chapter 6 Reliability
Isolation
Overload control
System Performance
Mechanical Data
Environmental Requirements
Specification
Standard configuration: 219 GB
Hardware capacity
3000 CDRs/second
Specification
99.999%
System MTBF
10 years
DOWN duration
<3 mins/year
Performance specification
Hardware platform
Cabinet
dimensions
600 mm
Depth
800 mm
Height
2,200 mm
46 U (1 U = 44.45 mm)
7.3.2 Weight
Table 7-4 Cabinet weight of the CG9812
Item
Performance specification
Cabinet weight
310 kg
450 kg/m
Performance specification
Rated voltage
48V DC
Voltage fluctuations
57V40V
SUN platform
1.5 kW
Range
5,000 m
Atmospheric pressure
Temperature
40C to +70C
1C/min
Relative humidity
10% to 100%
Solar radiation
1,120 W/s
Heat radiation
600 W/s
Wind speed
30 m/s
Unit
Content
Suspending dust
mg/m
5.00
Precipitable dust
mg/mh
20.0
Sand
mg/m
300
Note:
1) Suspending dust: diameter 75 m
2) Precipitable dust: 75 m diameter 150 m
3) Sand: 150 m diameter 1,000 m
The density of chemically active materials shall comply with the requirements listed in
Table 7-8.
Table 7-8 Density requirements for chemically active materials
Chemically active material
Unit
Content
SO2
mg/m
0.30 to 1.00
H2S
mg/m
0.10 to 0.50
NO2
mg/m
0.50 to 1.00
NH3
mg/m
1.00 to 3.00
Cl2
mg/m
0.10 to 0.30
HCl
mg/m
0.10 to 0.50
HF
mg/m
0.01 to 0.03
O3
mg/m
0.05 to 0.10
Sinusoidal vibration
Non-stable impulse
Sub-item
Range
Offset
7.0 mm
Accelerated speed
20.0 m/s
Frequency range
2 Hz to 9 Hz
9 Hz to 200 Hz
Impulse
spectrum II
250 m/s
response
5 kPa
Payload
Note:
Range
5,000 m
Atmospheric pressure
Temperature
40C to +70C
3C/min
Relative humidity
10% to 100%
Solar radiation
1,120 W/s
Heat radiation
600 W/s
Wind speed
30 m/s
Rain
6 mm/min
Unit
Content
Suspending dust
mg/m
No requirement
Precipitable dust
mg/mh
3.0
Sand
mg/m
100
Note:
1) Suspending dust: diameter 75 m
2) Precipitable dust: 75 m diameter 150 m
3) Sand: 150 m diameter 1,000 m
The density of chemically active materials shall comply with the requirements listed in
Table 7-12.
Table 7-12 Density requirements for chemically active materials
Chemically active material
Unit
Content
SO2
mg/m
1.00
H2S
mg/m
0.50
NO2
mg/m
1.00
NH3
mg/m
3.00
Cl2
mg/m
0.30
HCl
mg/m
0.05
HF
mg/m
0.03
O3
mg/m
0.10
Sinusoidal
vibration
Random vibration
Non-stable
impulse
Sub-item
Range
Offset
7.5 mm
Accelerated speed
20.0
m/s
40.0 m/s
Frequency range
2 Hz to 9
Hz
9 Hz to
200 Hz
200 Hz to 500
Hz
Spectrum density of
accelerated speed
10 m/s
3 m/s
1 m/s
Frequency range
2 Hz to 9
Hz
9 Hz to
200 Hz
200 Hz to 500
Hz
Impulse response
spectrum II
300 m/s
Payload
10 kPa
Note:
1) Impulse response spectrum: It refers to the maximum accelerated speed
response curve generated by the equipment under the specified impulse motivation.
Impulse response spectrum II means that the duration of half-sine impulse response
spectrum is 6 ms.
2) Payload: It refers to the bearable pressure from the upper piled equipment with
package in prescribed piling mode.
Temperature
+5 C to +45 C
5 C to +55 C
Relative humidity
5% to 85%
5% to 95%
Note:
1) The measurement points of temperature and humidity of the CG9812 refer to the
values measured 1.5 meters above the floor and 0.4 meter away from the front of the
CG9812 shelf when there are no protection panels in the front and back of the
CG9812 shelf.
2) Short term means that the consecutive working duration is not more than 48 hours
and that the accumulated working duration of a year is not more than 15 days.
Range
4,000 m
Atmospheric pressure
5 C/h
Solar radiation
700 W/s
Heat radiation
600 W/s
Wind speed
1 m/s
IP level
IP50
Unit
Content
Dust particle
particle/m
3 10
Suspending dust
mg/m
0.2
Precipitable dust
mg/mh
1.5
Sand
mg/m
30
Note:
1) Dust particle: diameter 5 m
2) Suspending dust: diameter 75 m
3) Precipitable dust: 75 m diameter 150 m
4) Sand: 150 m diameter 1,000 m
The density of chemically active materials should comply with the requirements
Unit
Content
SO2
mg/m
0.30 to 1.00
H2S
mg/m
0.10 to 0.50
NO2
mg/m
0.50 to 1.00
NH3
mg/m
1.00 to 3.00
Cl2
mg/m
0.10 to 0.30
HCl
mg/m
0.10 to 0.50
HF
mg/m
0.01 to 0.03
O3
mg/m
0.05 to 0.10
CO
mg/m
5.0
Sinusoidal vibration
Sub-item
Range
Offset
5.0 mm
Accelerated speed
2.0 m/s
Frequency range
5 Hz to 62 Hz
62 Hz to 200 Hz
Item
Non-stable impulse
Sub-item
Range
Impulse response
spectrum II
50 m/s
Payload
Note:
1) Impulse response spectrum: It refers to the maximum accelerated speed
response curve generated by the equipment under the specified impulse motivation.
Impulse response spectrum II means that the duration of half-sine impulse response
spectrum is 6 ms.
2) Payload: It refers to the bearable pressure from the upper piled equipment with
package in prescribed piling mode.
HUAWEI
HUAWEI CG9812
User Manual
Table of Contents
Table of Contents
Chapter 1 Installation Overview................................................................................................... 1-1
1.1 Introduction to the Chapter ................................................................................................ 1-1
1.2 Installation Flow ................................................................................................................. 1-1
1.2.1 Installation Flow Chart............................................................................................. 1-1
1.2.2 Installation Time Planning ....................................................................................... 1-2
1.3 Installation Preparations .................................................................................................... 1-3
1.3.1 Hardware Preparations ........................................................................................... 1-3
1.3.2 Software Preparations............................................................................................. 1-4
1.4 Resource Planning ............................................................................................................ 1-6
1.4.1 HA System Planning ............................................................................................... 1-6
1.4.2 IP Address Planning................................................................................................ 1-7
1.4.3 Disk Space Planning ............................................................................................... 1-8
Chapter 2 Installing and Configuring Hardware......................................................................... 2-1
2.1 Introduction to the Chapter ................................................................................................ 2-1
2.2 Cabinet Configuration ........................................................................................................ 2-1
2.3 Hardware Description ........................................................................................................ 2-3
2.3.1 Introduction to Sun Netra 240 ................................................................................. 2-3
2.3.2 Introduction to SUN StorEdge 3310 Disk Array ...................................................... 2-5
2.3.3 Introduction to Quidway S3528G LAN Switch ........................................................ 2-6
2.4 Hardware Connections ...................................................................................................... 2-7
2.4.1 Host Hardware Planning ......................................................................................... 2-7
2.4.2 Disk Array Hardware Planning ................................................................................ 2-8
2.4.3 Hardware Connections............................................................................................ 2-8
2.4.4 Description for Cable Connections........................................................................ 2-10
2.4.5 Hardware Power-on .............................................................................................. 2-15
Chapter 3 Configuring SC and Disk Array.................................................................................. 3-1
3.1 Introduction to the Chapter ................................................................................................ 3-1
3.2 Configuring SC................................................................................................................... 3-1
3.2.1 Introduction to SC ................................................................................................... 3-1
3.2.2 Configuring SC ........................................................................................................ 3-1
3.3 Configuring Disk Array....................................................................................................... 3-4
Chapter 4 Installing and Configuring Solaris ............................................................................. 4-1
4.1 Introduction to the Chapter ................................................................................................ 4-1
4.2 Installing Solaris 8.............................................................................................................. 4-1
4.2.1 Connecting Consoles of Netra 240 ......................................................................... 4-1
4.2.2 Installing Solaris 8 ................................................................................................... 4-2
Table of Contents
Table of Contents
Installation Flow
Installation Preparations
Resource Planning
Begin Installation
Install Hardware
Check installation
Finish installation
Task description
Estimated time(hour)
Installing hardware
0.5
0.5
1.5
0.5
0.5
Installing VxVM
Configuring VxVM
0.4
10
Checking installation
0.2
Configuration
CPU
2*1.28 GHz
Memory
2 GB
Hard disk
2*73 GB
Item
Configuration
Network
Adapter
StorEdge 3310
disk array
S3528G LAN
switch
1)
2)
3)
DVD-ROM
Tape drive
None
Power
supply
Capacity
5*73 GB or higher
SCSI port
Power
supply
Network
port
24
Power
supply
item
configuration
Solaris 8 (02/04 SPARC Platform)
OS
System
software
Solaris Patch
Cluster software
Volume manager
Billing interface
software (optional)
Applications
CG9812 applications
igwb1
igwb2
SUN OS
SUN OS
SUN Cluster
SUN Cluster
Volume Manager
Volume Manager
FTP/FTAM(optional)
FTP/FTAM(optional)
CG9812 Server
CG 9812 Server
3310-0
Mirroring
3310-1
HA System Planning
IP Address Planning
Primary node
Secondary node
Cluster name
sc-igwb
sc-igwb
Cluster node
igwb1
igwb2
Transport path 1
ce0
ce0
Transport path 2
ce1
ce1
NAFO Group 0
bge0
bge0
NAFO Group 1
bge1/bge2
bge1/bge2
NAFO Group 2
bge3
bge3
Item
Primary node
Secondary node
Quorum devices
d4
d4
Root Password
root
root
In configuration, the Netra 240 is provided with a 4-port built-in network adapter,
which is used to connect the public network for application purposes. The four
ports are bge0, bge1, bge2, and bge3. bge1 and bge2 serve as the NAFO links.
Also, the Netra 240 has an external 2-port network adapter. The two ports are ce0
and ce1, which serve as the heartbeat links.
The floating IPs and the fixed IPs are set in the same network segment.
Below is an example of the IP configuration. See Table 1-5 and Table 1-6.
Table 1-5 IP address planning
Device
Floating IP (logical
host name)
Description
bge0
129.1.1.1(igwb1)
129.1.1.2(igwb2)
129.1.1.3(ha-igwb)
bge1
129.2.1.1(igwb11)
129.2.1.2(igwb21)
129.2.1.3(ha-igwb1)
bge3
129.3.1.1(igwb13)
129.3.1.2(igwb23)
129.3.1.3(ha-igwb3)
ce0
Not required
Not required
Heartbeat link 1.
ce1
Not required
Not required
Heartbeat link 2.
Description
PC
Maintenance
terminal
129.1.1. 4(admin)
igwb1 SC IP
129.1.1.11(igwb1-sc)
SC IP of igwb1.
Igwb2 SC IP
129.1.1.12( igwb2-sc)
SC IP of igwb2.
3310-0
129.1.1.13
Manageable IP of 3310-0.
3310-1
129.1.1.14
Manageable IP of 3310-1.
Root Directory
Allocate sufficient space to the root directory since its size cannot be changed with the
UNIX commands. The type of the root file system is User File System (UFS).
2)
SWAP
The required disk space for SWAP depends on the size of the host memory and the
expected maximum memory size. In short, the space of SWAP and the host memory
decides the maximum available memory. The size of SWAP shall be at least 1.5 times
larger than the physical memory. According to the disk capacity and its expansion
requirements, the SWAP is set to 10GB.
3)
/globaldevices
This is the global devices partition with 500 MB. It is used by the VxVM.
The recommended system planning is shown in Table 1-7.
mount point
size
Description
c1t0d0s0
57 GB
Root.
c1t0d0s1
swap
10 GB
SWAP.
68.35 GB
c1t0d0s2
Overlap
c1t0d0s3
c1t0d0s4
c1t0d0s5
c1t0d0s6
/globaldevices
512 MB
c1t0d0s7
Allocated hard
disk
hotspare hard
disk
Host
Description
Rootdg
None
igwb1
Rootdg of SC1
Rootdg
None
Igwb2
Rootdg of SC2
igwbdg
LUN1 on 3310
None
igwb1/igwb2
Shared disk
group
2)
disk (disk
used for
mirror)
Logical
volume
name
Logical
volume
size
igwbdg-stat
log-alarm
igwbdg
Mount point
512MB
4096MB
Fixed size.
/var/other
Fixed size.
This volume
stores logs
and alarms.
/var/frontsave
The actual
size. This
volume
stores
original bills.
/var/backsave
The actual
size. This
volume
stores final
bills.
c2t0d1
c3t0d1
front
101376MB
back
101376MB
Remarks
Figure 1-3 shows the hard disks in the 3310 disk arrays.
3310-1
7
8
9
10
11
12
c2t8d0
c2t9d0
c2t10d0
c2t11d0
c2t12d0
3310-2
7
8
9
10
11
12
c3t8d0
c3t9d0
c3t10d0
c3t11d0
c3t12d0
Cabinet Configuration
Hardware Description
Hardware Connections
CG9812 Cabinet
Power distribution frame (2U)
Quidway 3528G-1 (1U)
Cabling frame1U
Quidway 3528G-0 (1U)
Cabling frame (1U)
Dummy panel (3U)
Dummy panel (3U)
Dummy panel (3U)
Dummy panel (3U)
46U
Value
CPU
Memory
2 GB
Hard disk
2*73 GB
Ambient index
parameter
Power
supply
temperature
AC
DC
Running
Storage
Humidity
value
Running
Storage
Value
Height
Width
425.0 mm (16.73in)
Depth
508.0 mm (21in)
Weight
One 4-port 10/100/1000M integrated network adapter with their ports set to bge0,
bge1, bge2, and bge3 from left to right, where bge1 and bge2 serves as NAFO
links.
Two PCI Ultra SCSI HostAdapter cards, which are used to connect with the 3310
disk arrays.
ce0 and ce1 of host1 and ce0 and ce1 of host2 are used to connect with the
private networks with the crossover cables. Netra 240 includes one DB9 serial port
Huawei Technologies Proprietary
2-4
(Serial Mgt Port). The ALOM card is the standard alarm card for the Netra 240.
The Netra 240 minicomputer can monitor CPU, fan, and temperature. Besides
these functions, it also supports serial port connections and network connections.
Specifically, it connects with the PC hyper terminal by a DB9<->RJ45 cable, with
the disk arrays by the SCSI cables, and with the LAN Switches by the straight-thru
cables.
Redundant components.
Note:
Typically, five hard disks are inserted into the slots 7, 8, 9, 10, and 11 for each disk array.
To add more disks, insert one into slot 12 first, and then slots 1, 2, 3, 4, 5, and 6
sequentially.
(3) (4)
(2)
(5)
(6)
(7)
10
12
14
16
18
20
22
24
11
13
15
17
19
21
23
Note:
For more information about LAN Switch, refer to Quidway S3528 Series LAN Switch
Installation Manual.
Netra 240(DC)
Purchase No.
Description
XRA-SC1N2-73G15K
2 GB memory
2* 73 GB local hard disks
Purchase No.
Description
X4422A
X6758A
X6758A
3310(J-DC)
Jumper switch
description
Hard disk
slots:
Purchase No.
711
XTA-3310-73GB-15K
Disk array
name
3310-0 3310-1
PN No.
Description
540-5522
Source
device
Source device
port
Destination
device port
Remark
01
1G Ethernet
host 1
bge0 in slot0 of
PCI1
NMS and
LMT
Public
network
02
1G Ethernet
Host 1
bge1 in slot1 of
PCI1
GSN
LAN
Switch-0
Public
network
03
1G Ethernet
host 1
bge2 in slot2 of
PCI1
GSN
LAN
Switch-1
Public
network
04
1G Ethernet
host 1
bge3 in slot3 of
PCI1
Billing center
(BC)
Public
network
05
1G Ethernet
host 2
bge0 in slot0 of
PCI1
NMS and
LMT
Public
network
06
1G Ethernet
host 2
bge1 in slot1 of
PCI1
GSN
LAN
Switch-0
Public
network
07
1G Ethernet
host 2
bge2 in slot1 of
PCI1
GSN
LAN
Switch-1
Public
network
08
1G Ethernet
host 2
bge3 in slot3 of
PCI1
BC
Public
network
No.
Destination
device
Connection
type
Source
device
Source device
port
Destination
device port
Remark
09
1G Ethernet
(crossover)
host 1
ce0
Host2
ce0
Private
network
10
1G Ethernet
(crossover)
host 1
ce1
Host2
ce1
Private
network
11
SCSI
host 1
SCSI 1 inPCI2
slot
3310-0
CH1 port
12
SCSI
host 1
SCSI 1 inPCI1
slot
3310-1
CH1 port
13
SCSI
host 2
SCSI 1 inPCI2
slot
3310-0
CH3 port
14
SCSI
host 2
SCSI 1 inPCI1
slot
3310-1
CH3 port
15
SCSI
3310-0
CH0 port
3310-0
Single
port
Bus
16
SCSI
3310-1
CH0 port
3310-1
Single
port
Bus
17
100M
Ethernet
host 1
ALOM port
Maintenance
terminal
Manage
ment
18
100M
Ethernet
host 2
ALOM port
Maintenance
terminal
Manage
ment
19/20
100M
Ethernet
3310-0
Two controller
ports
Manage
ment
21/22
100M
Ethernet
3310-1
Two controller
ports
Manage
ment
No.
Destination
device
3310 -0
3310 -1
Netra 240-0
LMT
BC
GSN
GSN
public net
public net
GSN
LMT
public net
GSN
BC
private net
HeartBeat
Netra 240-1
ALOM
bge1 bge3
Net Mgt Serial
Port Mgt Port bge0 bge2
ce0
ce1
Figure 2-7 Connections between Sun Netra 240 and Sun StorEdge 3310
Netra 240 does not include an external terminal concentrator (TC). The built-in system
controller (SC) is provided, which can be connected through the Net Mgt Port shown in
Figure 2-7:
z
In early stage of the deployment, because the LAN Switches to the NMS and the BC
are not installed, the bge0 and bge3 ports of the HA system are connected to the LAN
Switches in the cabinet of the CG9812. Figure 2-8 shows the cable connections with
the LAN Switches.
igw b1
bge1,bge2
igw b1
bge0
(3)
(2)
(1)
(1)
igw b2
bge0
(2)
(4)
igw b1
SC
igw b1
bge3
(2)
igw b2
bge1,bge2
(3)
(4)
igw b2
bge3
igw b2
SC
(2)
Cable (1). Two LAN Switch ports are coupled for subtending.
Caution:
Dangling cables must be prohibited.
II. Connections between the primary server and the secondary server
Connect the external ce0 port of the primary server with ce0 of the secondary server.
Connect ce1 of the primary server with ce1 of the secondary server. These two
connections serve as heartbeat links between the primary server and the secondary
server. All cables in use are straight-thru cables (crossover cables).
Connect the PGND bar of the DC distribution cabinet securely with the nearest
PGND bar provided by the equipment buyer through the PGND bus. The PGND
Huawei Technologies Proprietary
2-12
cables are yellow-green plastic insulated copper wires with the same core
diameter as that of the power cables.
z
For Netra 240, connect the power cables and ground cables for the internal devices in
the CG9812 cabinet as indicated in Figure 2-10.
Figure 2-10 Connections of power/ground cables for devices in the CG9812 cabinet
(Netra 240)
Caution:
z
For the minicomputers and disk arrays, sudden power-off is prohibited on the
CG9812 server. Because after UNIX is suddenly powered off, it must be manually
maintained before it can run.
It is recommended to power on the minicomputers after the disk arrays are powered
on for three minutes.
Configuring SC
3.2 Configuring SC
This section introduces how to configure the SC.
3.2.1 Introduction to SC
Netra 240 does not include a video adapter or a display. Those minicomputers in earlier
versions are configured with a TC to transfer the control signals from the two hosts and
display them on the monitor console.
In Netra 240, a SC is integrated on the main board. The SC functions as the TC.
Different from the TC, the SC of each minicomputer is configured with a separate IP
address. To access the IP address of an SC, run the command below:
#telnet <sc_ip>
The SC provides a Net Mgt Port and a Serial Mgt Port. See Figure 3-1.
3.2.2 Configuring SC
Configure the SCs on igwb1 and igwb2. The SCs are only required to be configured
once. To configure the SC, follow the steps below:
Stop bit: 1
Figure 3-2 Parameter settings for serial port of the maintenance terminal
III. Log in to SC
The SC starts to work when the power supply is connected. You can log in to the SC
through the maintenance terminal.
1)
Use a DB9<->RJ45 cable to connect the serial port of the SC with a serial port of
the maintenance terminal.
2)
Start the hyper terminal program to connect and log in to the SC.
3)
Note:
If Solaris is not installed, SC> is displayed. Otherwise, press Ctrl+Pause to display the
OK system prompt. Then type #. to display SC>.
SC>resetsc
The settings are enabled.
(access igwb1)
#telnet 129.1.1.12
(access igwb2)
Enter the user name and password again. To access the Console, enter the command
below:
SC>console
To return to SC>, enter #..
Note:
z
The IP address of the Net Mgt Port is 129.1.1.11. To access this port by Telnet, set
the IP address of the PC to 129.1.1.4.
To change the user password, run SC>password. Remember the password for
later use.
Note:
z
Name the two StorEdge 3310 disk arrays 3310-0 and 3310-1. Both of them need to
be configured.
The numbers given in the following figure is for example purpose, for example, the
disk space of a disk array is 35 GB. The actual capacity is 73 GB by default.
Log in to 3310-0 (3310-1 for the secondary node) through the PC hyper terminal.
Press Enter, and then press ESC three times. Select Terminal (VT100 Mode)
from the menu, and then press Enter to open the main menu.
2)
Enter the IP address: 129.1.1.13 (IP of 3310-0), 129.1.1.14 (IP of 3310-1); Subnet
mask: 255.255.0.0; And gateway IP address: not set, See Figure 3-5. Note that
the given values are for example purposes only.
4)
Press ESC. Click Yes to set the IP address. Then, click Yes to reset the controller.
5)
#telnet xxx (xxx for IP address of the Disk Array, such as 129.1.1.13 or 129.1.1.14)
Trying xxx (xxx for IP address of disk array)
Connected to xxx (xxx for IP address of disk array)
Escape character is ^].
Press ESC. Select Terminal (VT100 Mode) from the menu, and then press Enter
to open the main menu.
2)
On the main menu, select view and edit SCSI channels. Configure the SCSI
channels as indicated in Figure 3-6. Set CHL1 and CHL3 to Host, that is, the
Primary Controllers.
3)
Press Esc to return to the main menu. Click Yes to reset the controller.
#telnet xxx (xxx for IP address of the disk array, for example, 129.1.1.13 or 129.1.1.14)
Trying xxx (xxx for IP address of disk array)
Connected to xxx (xxx for IP address of disk array)
Escape character is ^].
Select Terminal (VT100 Mode) from the menu, and then press Enter to open the
main menu.
Huawei Technologies Proprietary
3-6
2)
On the main menu, select view and edit Logical drives, and then press Enter to
configure the logical drives. See Figure 3-7.
Caution:
For a new disk, no logical disk is created. See Figure 3-7. Delete the existing logical
disks, if any. If LUN is mapped, you may fail to delete the logical disks. Unmap the host
LUN before you delete the logical disks.
Select the first row, and then press Enter. The system prompts Create Logical
Drive. Click Yes, and then press Enter to continue. The following interface is
displayed. See Figure 3-8.
Select RAID5, and then press Enter. Select the first four disks as RAID5 mirror
disks. In the Slot column, an asterisk (*) is marked if a disk is selected. See
Figure 3-9.
Press Esc to confirm your selection. The following interface is displayed. See
Figure 3-10
Huawei Technologies Proprietary
3-8
Select Assign Spare Drives, and then press Enter to select the HotSpare disks.
The following interface is displayed. See Figure 3-11.
Select all the rest disks as HotSpare drives. In the Slot column, an asterisk (*) is
marked if a disk is selected. Press Esc to confirm your selection. The following
interface is displayed. See Figure 3-12.
Huawei Technologies Proprietary
3-9
Caution:
If N (4) hard disks are configured on StorEdge 3310, select one for HotSpare, and
others for RAID5.
8)
Click Yes, and then press Enter to create the logical drive. See Figure 3-13.The
process will take about 80 minutes. You can check the process (%) from the upper
left corner. Do not perform any other operation during the process. After the RAID5
disk is created, go on with the next step.
After RAID5 is finished initialization, press Esc twice. The following interface is
displayed. See Figure 3-14.
Select Partition logical drive, and then press Enter to partition the logical disk.
The system then prompts Continue Partition Logical Drive? See Figure 3-16.
Click Yes, and then press Enter.
2)
Enter 200 for partition0 in Partition Size (MB), and then press Enter. See
Figure 3-17.
The following interface is displayed. See Figure 3-18. Click Yes, and then press
Enter.
4)
Move to the second row, and then press Enter to allocate space for partition1.
Enter 209053 in Partition Size (MB), and then press Enter. See Figure 3-19. The
value is given for example purpose only.
The following interface is displayed. See Figure 3-20. Click Yes, and then press
Enter to complete the partition.
Press Esc twice to return to the main menu. On the main menu, select view and
edit Host LUNs, and then press Enter. See Figure 3-21.
Select CHL 1 ID 0 (Primary Controller), and then press Enter. See Figure 3-22.
Caution:
Make sure CHL 1 is set to Primary Controller. If CHL1 ID 0 (Secondary Controller) is
displayed, delete this channel, and then add CHL 1 ID 0 (Primary Controller).
3)
Select Logical Drive, and then press Enter. See Figure 3-23.
Select row 0, and then press Enter to map the first LUN. See Figure 3-24.
Select the RAID5 logical drive, and then press Enter. See Figure 3-26.
In Figure 3-28, select Map Host LUN, and then press Enter.
The following interface is displayed. See Figure 3-29. Click Yes, and then press
Enter.
Installing Solaris 8
Configuring Solaris
Installing Utilities
Note:
z
During the setup process, press ESC+2 to go to the next step, press Up or Down to
locate an option, and press Space or Enter to select the selection.
Description
On the maintenance terminal console, log in to igwb1 and igwb2 with the
commands below:
#telnet 129.1.1.11
#telnet 129.1.1.12
Step
Description
Connect the consoles with the commands below:
sc>break
sc>console -f
Description
Method 1: If the workstation is not installed with UNIX, press Ctrl+] on the
console, type Send brk, and press Enter to show the ok prompt.
Method 2: If Solaris is installed, type halt as the user root to show the ok
prompt.
Boot the host from the CD-ROM. Type boot cdrom after the OK prompt:
ok boot cdrom
Select English as installation language. See below:
Select a Language
0. English
1. French
9. Traditional Chinese
Please make a choice (0 - 9), or press h or ? for help: 0
Select a Locale
0. English (C - 7-bit ASCII)
1. Albania (ISO8859-2)
Step
Description
Select the terminal type. Select DEC VT100. Because no monitor is
configured in the HA system, the installer cannot identify the terminal type. To
select the terminal type, follow the steps below:
Esc-6_Help
Networked
[X] Yes
[ ] No
Use DHCP
[ ] Yes
[X] No
11
Enter the host name. Enter igwb1 for the primary node, and igwb2 for the
secondary node. See below:
Host name:igwb1
12
14
Step
Description
Determine whether to enable IPv6. Select No. see below:
15
Enable IPv6
[ ] Yes
[X] No
16
Networked: Yes
Use DHCP: No
Primary network interface: bge0
Host name: igwb1 (igwb2 for igwb2)
IP address: 129.1.1.1 (129.1.1.2 for igwb2)
System part of a subnet: Yes
Netmask: 255.255.0.0
Enable IPv6: No
Configure
[ ] Yes
[X] No
Kerberos Security
Name
[ ]
[ ]
[ ]
[ ]
[X]
service
NIS+
NIS
DNS
LDAP
None
Select the Geographic Region, for example, Asia, Eastern. See below:
19
Regions
[X] Asia, Eestern
[ ] United States
Select Time Zone. Select the local time zone, such as Hong Kong. See
below:
20
Time zones
[ ] HongKong
22
23
Initialize the setup process. Press ESC + 4 to select Initial. See below:
F2_Upgrade
F4_Initial
F5_Exit
F6_Help
Step
24
Description
Press ESC + 2 to select the standard installation.
Esc-2_Standard
F3_Go Back
Esc-4_Flash
F5_Exit
F6_Help
Select the following character sets from the Geographic Region menu.
25
26
[/] Asia
[ ] PC Kanji (ja_JP.PCK)
[X]
Simplified Chinese EUC
[X]
Simplified Chinese GBK
[X]
Simplified Chinese UTF-8
[/] North America
[ ]
Canada-English (ISO8859-1)
[X]
U.S.A. (en_US.ISO8859-1)
Select
Select the components. Select Entire Distribution Plus OEM support for
full install. See below:
27
28
72538 MB
(F4 to edit)
Determine whether to preserve the existing data on the hard disk. Press ESC
+ 2 to select continue to overwrite the data. See below:
29
30
Do you want to preserve existing data? At least one of the disks you've
selected for installing Solaris software has file systems or unnamed
slices that you may want to save.
F2_Continue
F3_Go Back
F4_Preserve
F5_Exit
F6_Help
Determine whether to lay out the file system automatically. Press ESC + 4 to
select Manual Layout.
F2_Auto Layout
F3_Go Back
F4_Manual Layout
F5_Exit
F6_Help
31
The system displays the current hard disk (overlap). Select Continue to
confirm.
32
Partition the hard disk as indicated in Table 1-7, and then select Continue.
Press ESC + 2 to confirm the partition.
33
Step
34
Description
Determine whether to mount software from a remote file server. Pres ESC+2
to select Continue.
Do you want to mount software from a remote file server? This may be
necessary if you had to remove software because of disk space problems.
F2_Continue
F3_Go Back
F4_Remote Mounts
F5_Exit F6_Help
35
36
37
38
39
Start the setup process, and the setup progress is displayed. The setup
process takes about 40 minutes. After installation, the system will reboot
automatically.
After Solaris is restarted, the system prompts to enter and confirm the
password of root. Remember the password. See below
Root password:******
Press Return to continue.
Re-enter your root password: ******
When the following message appears, select 1, and then press Enter. See
below:
40
Media:
1. CD/DVD
2. Network File System
3. Skip
Media [1]:<Enter>
Insert the Solaris 8 Software 2 of 2 CD, and then press Enter. See below,
41
Step
Description
Determine whether to display the installation details. Select 2 to continue.
See below:
42
Installation details:
Product
Result
More Info
1. Solaris 8 packages (part 2) Installed Available
2. Done
Enter the number corresponding to the desired selection for more
information, or enter 2 to continue [2]:<Enter>
When the following message appears, select 1, and then press Enter. See
below:
43
Media:
1. CD/DVD
2. Network File System
3. Skip
Media [1]:<Enter>
Insert the CD for Solaris 8 Languages and press Enter. See below:
44
Please insert the CD/DVD for Solaris 8 Languages (2/02 SPARC Platform
Edition).
After you insert the disc, please press Enter: <Enter>.
45
Description
Insert the patch tools CD into the CD-ROM of the corresponding host or
workstation console.
Step
Description
Install the patch tools as root.
2*
# cd /cdrom/cdrom0/sun/install/
# sh ./setup-standard.sh
Enter the base directory of the package. To select the default /opt/CTEact
directory, press Enter.
enter base directory for install (Default /opt/CTEact) [?,q]<Enter>
10
11
12
Decide whether to install the CTEact package. Press Enter to select the
default value y.
Install the explorer package.
13
14
15
16
17
Step
18
Description
Enter Contact Name. Press Enter.
Contact name []:
19
20
21
22
23
24
25
26
Select the geographic region where the local SUN branch is located. For
example. Select APAC: Asia, Pacific. Press Enter.
27
Geographic Region
1 - AMERICAS - North and South America
2 - EMEA
- Europe, Middle-east and Africa
3 - APAC
- Asia, Pacific
[]: 3
29
30
Enter the return address for analysis result. Enter - for none.
The settings are displayed. Select y to confirm or select n to reset the
information.
31
32
Step
Description
33
34
35
The following information is displayed. Select yes, and then press Enter.
Do you with the installation of <SUNWexplo> [y,n,?] y
36
Description
# cd /cdrom/cdrom0/sun/patch/8
# unpatck-patches
Run the command below to begin the setup process. This process may take
a long time. Please wait.
# cd /tmp/8; /install_all_patches
Restart the computer after the installation is complete.
# sync;sync;sync
# reboot
Description
# cd /cdrom/cdrom0/sun/patch/SAN
# unpack-patches
Are you ready to unpack patches into /tmp/SAN? [y/n]: y
#cd /tmp/SAN
#./install_patches
Are you ready to continue with install? [y/n]: y
#cd cdrom/cdrom0/sun/patch/SAN/8
#unpack-patches
Are you ready to unpack patches into /tmp/8? [y/n]: y
Target for unpacking patches /tmp/8 exists!
May I delete /tmp/8? [y/n] y
#cd /tmp/8
#./install_patches
Are you ready to continue with install? [y/n]: y
Description
Step
Description
Run the commands below to install the SCSI card driver:
#mkdir -p /export/home/software/scsi
#cd /cdrom/cdrom0/sun/progs/SUNWqus/8
#cp SUNWqus_8_all.tar.gz /export/home/software/scsi/
#cd /export/home/software/scsi
#gunzip SUNWqus_8_all.tar.gz
#tar xvf SUNWqus_8_all.tar
#pkgadd d.
Select yes if prompted during the setup process.
Description
Log in as root, and then go to /cdrom/cdrom0/sun/patch/SUNWqus/8.
Run the commands below:
#cd /cdrom/cdrom0/sun/patch/SUNWqus/8
#unpack-patches
#cd /tmp/8
#./install_patches
Are you ready to continue with install? [y/n] y
# sync;sync;sync
# reboot -- -r
Use the format command to view all the hard disks on the disk array.
Caution:
Make sure the above software packages are installed in the above sequence. Restart
the computer after a package is installed. The computer can automatically detect the
disk array status during the restart process.
localhost
129.1.1.1
igwb1
129.2.1.1
igwb11
129.3.1.1
igwb13
129.1.1.2
igwb2
129.2.1.2
igwb21
129.3.1.2
igwb23
129.1.1.3
ha-igwb
129.2.1.3
ha-igwb1
129.3.1.3
ha-igwb3
129.1.1.11
igwb1-sc
129.1.1.12
igwb2-sc
129.1.1.13
3310-0
129.1.1.14
3310-1
igwb1.huawei.com loghost
127.0.0.1
localhost
129.1.1.2
igwb2
129.2.1.2
igwb21
129.3.1.2
igwb23
129.1.1.1
igwb1
129.2.1.1
igwb11
129.3.1.1
igwb13
129.1.1.3
ha-igwb
129.2.1.3
ha-igwb1
129.3.1.3
ha-igwb3
129.1.1.11
igwb1-sc
129.1.1.12
igwb2-sc
129.1.1.13
3310-0
129.1.1.14
3310-1
igwb2.huawei.com loghost
Note:
z
The /etc/hosts file records the IP addresses of the local nodes and all the nodes in
the HA system. 129.1.1.1 is the IP address of the primary node, and 129.1.1.2 is the
IP address of the secondary node. For a specific IP address, enter as indicated in
the IP planning table.
In the file, a tab not a space is set between 129.1.1.1 and igwb1.
Create hostname.bge3
# vi /etc/hostname.bge3
Add the line below:
igwb13
Create hostname.bge3
# vi /etc/hostname.bge3
Add the line below:
igwb23
Add a comment on this line. Then the user root can log in to the host by Telnet.
Note:
This line is added because Sun Cluster 3.0 does not support the Loopback file system.
For details, refer to Sun Cluster 3.0 Release Notes.
255.255.0.0
129.2.1.0
255.255.0.0
129.3.1.0
255.255.0.0
Description
Insert the TOP software CD into the CD-ROM.
Log in to igwb1 or igwb2 as root, and then go to the setup directory.
# cd /cdrom/cdrom0
# cd sun/tools/top
# cd /tmp
# gzcat -d top.3.5b8.SPARC.64bit.Solaris.8.pkg.tgz|tar xvfInstall the package.
# pkgadd -d .top
Do you want to install these as setuid/setgid files [y,n,?,q] y
Description
Insert the VTS software CD into the CD-ROM.
Step
Description
Log in to igwb1 or igwb2 as root, and then go to the following directory.
#cd /cdrom/cdrom0/SunVTS-5.1
SUNWvtsmn
SUNWvtsx
#cd 8
In this directory, you can find the files below:
SUNWlxml
SUNWlxmlx install-s8xmlpkgs.sh
#cd ..
#pkgadd -d .
This is an interactive installation process. You need to select the following
parameters:
Insert the patch CD into the CD-ROM, and then go to the setup directory.
#cd /cdrom/cdrom0/sun/patch/SunVTS/5.1
Unpack the package.
# unpack-patches
Are you ready to unpack patches into /tmp/5.1? [y/n]: y
# cd /tmp/5.1
Add the patch.
# patchadd 112336-02
8
Installation Preparations
Logical hosts
The HA system uses the names of the network adapters for communication purposes,
so the /etc/hosts file must provide all the related information.
Check whether the /etc/hosts file contains the same contents below. If not, modify it.
I. On igwb1
#
# Internet host table
#
127.0.0.1
localhost
129.1.1.1
igwb1
129.2.1.1
igwb11
129.3.1.1
igwb13
igwb1.huawei.com loghost
129.1.1.2
igwb2
129.2.1.2
igwb21
129.3.1.2
igwb23
129.1.1.3
ha-igwb
129.2.1.3
ha-igwb1
129.3.1.3
ha-igwb3
129.1.1.11
igwb1-sc
129.1.1.12
igwb2-sc
129.1.1.13
3310-0
129.1.1.14
3310-1
II. On igwb2
#
# Internet host table
#
127.0.0.1
localhost
129.1.1.2
igwb2
129.2.1.2
igwb21
129.3.1.2
igwb23
129.1.1.1
igwb1
129.2.1.1
igwb11
129.3.1.1
igwb13
129.1.1.3
ha-igwb
129.2.1.3
ha-igwb1
129.3.1.3
ha-igwb3
129.1.1.11
igwb1-sc
129.1.1.12
igwb2-sc
129.1.1.13
3310-0
129.1.1.14
3310-1
igwb2.huawei.com loghost
Note:
Only the value of loghost is different between the two hosts.
II. On igwb2
For /etc/hostname.bge1, it is set to igwb21.
For /etc/hostname.bge3, it is set to igwb23.
Edit ftp.conf.cluster
Insert the SUN Cluster 3.0 installation CD into the CD-ROM. Run the command
below:
root@igwb1#cd /cdrom/cdrom0/SunCluster_3.0/Tools
The current directory contains the following files:
Upgrade
2)
defaults
lib
scinstall
root@igwb1#./scinstall
The following information is displayed:
*** Main Menu ***
* 1) Establish a new cluster using this machine as the first node
* 2) Add this machine as a node in an established cluster
3) Configure a cluster to be JumpStarted from this install server
4) Add support for new data services to this cluster node
5) Print release information for this cluster node
* ?) Help with menu options
* q) Quit
Note:
z
On igwb1, select 1) Establish a new cluster using this machine as the first
node.
Press Ctrl+D to return to the main menu during the setup process.
3)
y
y
SUNWscu.....done
SUNWscdev...done
SUNWscgds...done
SUNWscman...done
SUNWscsal...done
SUNWscsam...done
SUNWscvm....done
SUNWmdm.....done
SUNWscva....done
SUNWscvr....done
SUNWscvw....done
Hit ENTER to continue:
Note:
z
Because SUN Cluster 3.0 is not upgraded, it cannot identify those four 1000M
network adapters bge0, bge1, bge2, and bge3.
The installation must be stopped, otherwise, you will fail to configure the private
network.
2)
root@igwb1#cp -r /cdrom/cdrom0/sun/patch/SunCluster/3.0
/install/SC3.0-5_8-cluster
3)
root@igwb1#cd /install/SC3.0-5_8-cluster/common
root@igwb1#unpack-patches
Are you ready to unpack patches into /tmp/common? [y/n]: y
4)
root@igwb1#cd /tmp/common;./install_patches
Insert SUN Cluster 3.0 into the CD-ROM, and unpack the installation package.
root@igwb1#cd /cdrom/cdrom0/SunCluster_3.0/Tools
The current directory contains the following files:
Upgrade
defaults
lib
scinstall
root@igwb1# ./scinstall
Note:
To continue the setup process, refer to 5.3.2 Installing SUN Cluster 3.0 on igwb2.
2)
Note:
z
On igwb1, select 1) Establish a new cluster using this machine as the first
node.
You may press Ctrl+D to return to the main menu during the setup process.
y
y
scinstall: WARNING: but, the installed version is not the expected version!
Skipping "SUNWscdev" - already installed
scinstall: WARNING: but, the installed version is not the expected version!
Skipping "SUNWscgds" - already installed
Skipping "SUNWscman" - already installed
scinstall: WARNING: but, the installed version is not the expected version!
Skipping "SUNWscsal" - already installed
scinstall: WARNING: but, the installed version is not the expected version!
Skipping "SUNWscsam" - already installed
scinstall: WARNING: but, the installed version is not the expected version!
Skipping "SUNWscvm" - already installed
scinstall: WARNING: but, the installed version is not the expected version!
Skipping "SUNWmdm" - already installed
Skipping "SUNWscva" - already installed
scinstall: WARNING: but, the installed version is not the expected version!
Skipping "SUNWscvr" - already installed
Skipping "SUNWscvw" - already installed
scinstall: WARNING: but, the installed version is not the expected version!
What is the name of the cluster you want to establish?
hwhlr
Please list the names of the other nodes planned for the initial
cluster configuration. List one node name per line. When finished,type
Control-D:
Node name:igwb2
Node name (Ctrl-D to finish):^D
Note:
On igwb2, the following information is displayed: What is the name of the sponsoring
node? igwb1
3)
All the nodes defined in the cluster are displayed. If the information is correct,
enter y. Otherwise, enter n to modify it.
<Enter>
Note:
The default network address is 172.16.0.0 and the default netmask is 255.255.0.0.
Change the values if necessary.
4)
Select ce0 as the primary private network adapter, and ce1 as the secondary one.
Select the first cluster transport adapter to use:
1) bge1
2) ce0
3) ce1
4) bge2
5) bge3
6) Other
Option:2
1) bge1
2) ce1
3) bge2
4) bge3
5) Other
no
Note:
The parameters you configure are displayed. If they are correct, select yes to continue,
or select no to reset the parameters.
5)
Solaris starts to configure SUN Cluster 3.0. Then, enter q to close the main menu.
root@igwb1#vi /etc/inet/ntp.cluster
peer clusternode3-priv
peer clusternode4-priv
peer clusternode5-priv
peer clusternode6-priv
peer clusternode7-priv
peer clusternode8-priv
2)
2)
Log in as root and run the commands below to copy the installation package to the
/install directory:
root@igwb1#cd /cdrom/cdrom/sun/progs/SunCluster/3.0
root@igwb1#cd /install
root@igwb1#gzcat SUNWscdtk_u3_s8.tar.gz| tar xvf 4)
Run the command below to add the SUNWscdtk diagnosis tool package.
root@igwb1#pkgadd -d . SUNWscdtk
The following information is displayed.
Installation of <SUNWscdtk> was successful.
igwb1
Status
Online
Edit ftp.conf.cluster
2)
defaults
lib
scinstall
root@igwb2# ./scinstall
The following information is displayed:
*** Main Menu ***
* 1) Establish a new cluster using this machine as the first node
* 2) Add this machine as a node in an established cluster
3) Configure a cluster to be JumpStarted from this install server
4) Add support for new data services to this cluster node
5) Print release information for this cluster node
* ?) Help with menu options
* q) Quit
Option:2
igwb1
sc-igwb
(press Enter)
(press Enter)
switch1
igwb2:ce0
igwb1:ce1
switch2
igwb2:ce1
3)
Solaris starts to configure SUN Cluster 3.0. Then, enter q to close the main menu
Insert the SUN Patch4.0.2 CD into the CD-ROM. Log in as root and run the
commands below
root@igwb2#cd /cdrom/cdrom/sun/progs/SunCluster/3.0
root@igwb2#cp SUNWscdtk_u3_s8.tar.gz /install
root@igwb2#cd /install
root@igwb2#gzcat SUNWscdtk_u3_s8.tar.gz| tar xvf root@igwb2#pkgadd -d . SUNWscdtk
2)
Run the command below to add the SUNWscdtk diagnosis tool package.
root@igwb1#pkgadd -d . SUNWscdtk
The following information is displayed.
Installation of <SUNWscdtk> was successful.
Note:
Configure the quorum device on igwb1 only.
1)
root@igwb1#scdidadm -L
Specify a hard disk on the disk array for the Quorum device. Here, select d4.
For example:
igwb1>scdidadm -L
1
igwb1:/dev/rdsk/c0t0d0
/dev/did/rdsk/d1
igwb1:/dev/rdsk/c1t0d0
/dev/did/rdsk/d2
igwb1:/dev/rdsk/c1t1d0
/dev/did/rdsk/d3
igwb2:/dev/rdsk/c2t0d0
/dev/did/rdsk/d4
igwb1:/dev/rdsk/c2t1d0
/dev/did/rdsk/d4
igwb2:/dev/rdsk/c3t0d0
/dev/did/rdsk/d5
igwb1:/dev/rdsk/c3t1d0
/dev/did/rdsk/d5
igwb1:/dev/rdsk/c2t1d1
/dev/did/rdsk/d6
igwb2:/dev/rdsk/c2t0d1
/dev/did/rdsk/d6
igwb1:/dev/rdsk/c3t1d1
/dev/did/rdsk/d7
igwb2:/dev/rdsk/c3t0d1
/dev/did/rdsk/d7
igwb2:/dev/rdsk/c0t0d0
/dev/did/rdsk/d8
igwb2:/dev/rdsk/c1t0d0
/dev/did/rdsk/d9
10
igwb2:/dev/rdsk/c1t1d0
/dev/did/rdsk/d10
Note:
z
From above, you can see the disks d4, d5, d6 and d7 are shared by the primary and
secondary nodes.d4 and d6 are on LUN0, and d5 and d7 are on LUN1. Here, d4 is
used as the Quorum device.
2)
root@igwb1#scconf -a -q globaldev=d4
root@igwb1#scconf -c -q reset
Huawei Technologies Proprietary
5-13
root@igwb1#scconf -a -T node=.
Status
---------
------
Cluster node:
igwb1
Online
Cluster node:
igwb2
Online
Endpoint
Status
--------
--------
------
igwb2:ce1
Path online
igwb2:ce0
Path online
---------
Node votes:
igwb1
Online
Node votes:
igwb2
Online
Device votes:
Device Name
-----------
/dev/did/rdsk/d3s2
Online
Primary
------------
Secondary
-------
---------
Device Group
Status
------------
------
------------------------------------------------------------------
2)
Log in as root.
#cd /cdrom/cdrom0/sun-internal/progs/veritas-vm
#cd 3.5
The current directory contains the foundationproduct3.4sunw.tar.gz installation
package.
3)
#scvxinstall
Do you want Volume Manager to encapsulate root [no]?
Where is the Volume Manager cdrom?
6)
/install/foundationproduct3.4sunw
Please
enter
Volume
Manager
license
rrpu-ypr6-wp69-204k-6ppp-6ppr-pp)
key
[none]:xxx
(for
example,
Note:
z
Enter the temporary License key before you get the permanent one. Make sure you
apply for a permanent License and install it. If not, after the temporary License
expires, the volume manager cannot be reset if a system failure occurs.
To apply for a permanent License, fill in your hostid in the application form provided
with the product by fax or email to Sun Microsystems Inc. Before it is granted, ask
for a temporary License with Sun Microsystems Inc.
2)
Log in as root.
#cd /cdrom/cdrom/sun/patch/veritas-vm
#cd 3.5
#ls
You can find the files below in the current directory:
112392-07.zip 113203-03.zip
3)
113595-05.zip
113596-04.zip
#unpack-patches
Are you ready to unpack patches into /tmp/3.5? [y/n]: y
Cleaning out /tmp/3.5...
Unpacking.....
Patch 112392-06
Patch 113203-03
Patch 113595-05
Patch 113596-03
4)
Caution:
Make sure you have the latest patches on hand. If not, contact Sun Microsystems for
technical support.
Log in as root, and then execute the command below to disable the DMP function:
#vxdiskadm
The following information is displayed:
Select an operation to perform:17
devices from VxVM's view
#sync
#sync
#init 6
2)
3)
20
0 19:42:32 ?
Note:
Enter the respective licenses on igwb1 and igwb2.
Caution:
The hostids are different for the two minicomputers.
License Key
= R8CE-FR26-NSNN-R4O4-OZNP-PPP6-PPPP-OL
Product Name
License Type
= DEMO
OEM ID
= 4095
Features :=
VxVM
= Enabled
CPU Count
= Not Restricted
The information indicates that no permanent License is entered for the product. Note
that the letters in bold indicate the expiry date of the temporary license. After the date,
enter a permanent license.
Configuring NAFO
Note:
Unless otherwise specified, all the operations in this section shall be performed on
igwb1 and igwb2.
sliced
rootdisk_1
rootdg
online
c1t0d0s2
c1t1d0s2
sliced
error
c1t1d0s2
c3t1d0s2
sliced
error
c3t1d0s2
c3t1d1s2
sliced
error
c3t1d1s2
c4t1d0s2
sliced
error
c4t1d0s2
c4t1d1s2
sliced
error
c4t1d1s2
Select the second local disk as the mirrored disk of the root disk. The disk c1t1d0s2 is
selected in this example. Select the root disk based on the actual configurations.
Caution:
Rootdisk 1 is the local disk obtained with #vxdisk command.
Note:
Unless otherwise specified, perform the operations in this section only on igwb1.
TYPE
DISK
GROUP
STATUS
c1t0d0s2
sliced
rootdisk_1
online
c1t0d0s2
c1t1d0s2
sliced
mirrordisk_1
rootdg
error
c1t1d0s2
c3t1d0s2
sliced
error
c3t1d0s2
c3t1d1s2
sliced
c4t1d0s2
sliced
c4t1d1s2
sliced
rootdg
error
error
error
c3t1d1s2
c4t1d0s2
c4t1d1s2
Select c3t1d1 and c4t1d1 as the disks of the igwbdg disk group. c3t1d0 and c4t1d0
are selected as LUN0 in 200 MB. This LUN is set for system maintenance purpose.
Note:
The drive letter varies with the devices. Select based on the actual configurations.
Caution:
z
c3t0d1 in the script below should be the actual disk array number. View the numbers
with the format command. For example, the letters in blue (four disks) is the
required disk array numbers. Note that the number in red is the local disk of igwb 1
only.
root@igwb1#format
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1c,600000/scsi@2/sd@0,0
1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1c,600000/scsi@2/sd@1,0
2. c3t1d0 <SUN-StorEdge3310-0325 cyl 198 alt 2 hd 64 sec 32>
/pci@1e,600000/pci@2/scsi@4/sd@1,0
3. c3t1d1 <SUN-StorEdge3310-0325 cyl 51198 alt 2 hd 64 sec 64>
/pci@1e,600000/pci@2/scsi@4/sd@1,1
4. c4t1d0 <SUN-StorEdge3310-0325 cyl 198 alt 2 hd 64 sec 32>
/pci@1e,600000/pci@2/scsi@5/sd@1,0
5. c4t1d1 <SUN-StorEdge3310-0325 cyl 51198 alt 2 hd 64 sec 64>
/pci@1e,600000/pci@2/scsi@5/sd@1,1
Caution:
z
igwbdg01 and igwbdg02 in the script below is set for LUN1 on the StorEdge 3310.
The space of the front disk and the back disk shall be changed based on the actual
capacity of LUN1.
Partition the disk into four partitions, front, back, log-alarm, and igwbdg-stat.
igwbdg-stat is used by the system. Calculate each partition as indicated below: The
total space is the space of LUN1, 101,376 MB. Allocate 512 MB to igwbdg-stat,
4,096 MB to log-alarm, and the rest 103,228 MB are fifty-fifty for the front disk and
the back disk. It is recommended that the allocated space for the front disk and the
back disk be set to integral times of 512 to avoid insufficient available space.
1)
/usr/lib/vxvm/bin/vxdisksetup -i c3t1d1
/usr/lib/vxvm/bin/vxdisksetup -i c4t1d1
vxdg init igwbdg igwbdg01=c3t1d1
vxdg -g igwbdg adddisk igwbdg02=c4t1d1
vxassist -g igwbdg -U fsgen make igwbdg-stat 512m layout=nolog igwbdg01
vxassist -g igwbdg -U fsgen make log-alarm 4096m layout=nolog igwbdg01
vxassist -g igwbdg -U fsgen make front 101376m layout=nolog igwbdg01
vxassist -g igwbdg -U fsgen make back 101376m layout=nolog igwbdg01
vxassist -g igwbdg mirror igwbdg-stat layout=nolog igwbdg02
vxassist -g igwbdg mirror log-alarm layout=nolog igwbdg02
vxassist -g igwbdg mirror front layout=nolog igwbdg02
vxassist -g igwbdg mirror back layout=nolog igwbdg02
2)
preferenced=true
#newfs /dev/vx/dsk/igwbdg/back
The similar information below is displayed when the above commands are executed.
newfs: construct a new file system /dev/vx/rdsk/igwbdg/ igwbdg-stat : (y/n)?
y
Enter y.
Run the commands below on igwb1 and igwb2 to create the mount points.
#cd /var
#mkdir frontsave
#mkdir backsave
#mkdir other
Then, three mount points /var/frontsave, /var/backsave, and /var/other are created on
igwb1 and igwb2.
2)
Modify the /etc/vfstab file on igwb1 and igwb2, and then add the contents below:
/dev/vx/dsk/igwbdg/front
no
/dev/vx/rdsk/igwbdg/front
/var/frontsave ufs
logging
/dev/vx/dsk/igwbdg/back
/dev/vx/rdsk/igwbdg/back
/var/backsave ufs 2 no
logging
/dev/vx/dsk/igwbdg/log-alarm
ufs
no
/dev/vx/rdsk/igwbdg/log-alarm
/var/other
logging
Note:
Perform this operation on igwb1 and igwb2. Below is an example on igwb1.
root@igwb1#pnmset
The following information is displayed. The letters in bold should be entered.
In the following, you will be prompted to do configuration for network adapter
failover
Do you want to continue ... [y/n]: y
How many NAFO groups to configure [1]: 1
Note:
Unless otherwise specified, perform this operation on igwb1 only.
sc30_script.tar
To use the FTAM interface, you need to install and configure the FTAM software.
The FTP software is installed during the UNIX setup process. To use the FTP
interface, you need to configure the FTP server.
It is recommended to transfer the bill files between the CG9812 and the billing center by
FTP.
Solstice OSI 9.0, the OSI protocol stack of FTAM, contains the following packages:
SUNWcorpc
SUNWcosiA
SUNWcosia
SUNWcosib
SUNWcosic
SUNWcosid
SUNWosiax
SUNWosicx
SUNWosidx
SUNWlicsw
SUNWlit
SUNWcosip
2)
Solstice FTAM 9.0, the application layer software of FTAM (containing RFC 1006
protocol stack package), contains the following packages.
SUNWftama
SUNWftamb
SUNWftabx
SUNWrk6
SUNWrk6x
SUNWftamp
SUNWlicsw
SUNWlit
Caution:
z
SUNWlicsw is the License monitor process package, and SUNWlit is the License
management toolkit. They are only required to be installed during the FTAM or OSI
setup process. In other words, if the two packages are installed during the OSI setup
process, you do not need to install them during the FTAM setup process.
II. Decide the underlying communication protocol with the FTAM peer
Before installation, decide the underlying communication protocol with the FTAM peer
end, such as the billing center, you may select the RFC1006 protocol or the OSI
protocol. If the protocol cannot be decided, you probably cannot continue with the
FTAM setup process in a later section.
Note:
Unless otherwise specified, in the later sections, the letters in bold represent the
information you need to enter, and the letters in italic represent the installer prompts.
Insert the OSI protocol stack CD into the CD-ROM. If the Volume Manager is installed,
the CD-ROM is automatically mounted to the /cdrom/osi_9_0 file system. To check
whether Volume Manager is installed, run the ps -ef | grep vold command. Usually,
Solaris is installed with the Volume Manager, if not, mount it manually with the
commands below:
#mkdir /cdrom/osi_9_0
#mount -rF hsfs /dev/dsk/c0t6d0s0/cdrom/osi_9_0
2)
#cd /cdrom/osi_9_0
#pkgadd -d
The installer prompts the message below:
The following software packages are available:
1
SUNWcorpc
SUNWcosiA
SUNWcosia
SUNWcosib
SUNWcosic
SUNWcosid
(sparc) 9.0
7
SUNWcosip
SUNWlicsw
SUNWlit
10
SUNWosiax
SUNWosicx
12
SUNWosidx
Select the package you want to install (or select all to install all
packages).
(default: all) [?,??,q]: <Enter>
Select the packages, or install all the packages by default. Press Enter. Enter y if
prompted during the setup process. For example,
Do you want to continue to install SUNWcorpc?y (Press Enter)
Caution:
Install the OSI Core Stack Configuration Files package of SUNWcosib before other
packages are installed.
After all the packages are installed, the installer prompts the message below:
1
SUNWcorpc
SUNWcosiA
SUNWcosia
SUNWcosib
SUNWcosic
SUNWcosid
SUNWcosip
SUNWlicsw
SUNWlit
10
SUNWosiax
SUNWosicx
12
SUNWosidx
Select the package you want to execute (or select all to execute all
packages).
(default: all) [?,??,q]:q <Enter>
Enter q to exit.
3)
#cd /etc/opt/licenses
#./lit_tty
The license installation interface prompts the message below:
Select Product
[x] Solstice OSI (Stack) 9.0 for SPARC
[ ] Solstice CMIP 9.0 for SPARC
[ ] Solstice FTAM
p=Previous Page
Select Solstice OSI (Stack) 9.0 for SPARC, and then the information below is
displayed:
Servers: [x] 1 [ ] 3 [ ] 5
SERVER NAME
HOSTID
1: igwb2
80c7dff7
(+1) 800-872-4786
Expiration Date:18-dec-2001
Rights to Use:1
Data Checksum: d5
Password: 07BCAA07173858526A52B
Password Checksum: 77
** x=select/deselect
Return=next field **
Enter the Expiration Date, Rights to Use and Password of the License. The installer
prompts the settings are successful, and then displays the information below:
Select Product
[*] Solstice OSI (Stack) 9.0 for SPARC
[ ] Solstice CMIP 9.0 for SPARC
[ ] Solstice FTAM
p=Previous Page
#pachadd 111344-01
Check installed patches...
#sync;sync;sync;reboot
6)
Insert the FTAM protocol stack CD into the CD-ROM. If the Volume Manager is installed,
the CD-ROM is automatically mounted to the /cdrom/osi_9_0 file system. To check
whether Volume Manager is installed, run the ps -ef | grep vold command. Usually,
Solaris is installed with the Volume Manager, if not,mount it manually with the
commands below:
#mkdir /cdrom/ftam_9_0
#mount -rF hsfs /dev/dsk/c0t6d0s0/cdrom/ftam_9_0
2)
#cd /cdrom/ftam_9_0
#pkgadd -d
The installer shows the prompts below.
The following software packages are available:
1 SUNWftabx
SUNWftama
SUNWftamb
SUNWftamp
SUNWlicsw
SUNWlit
SUNWrk6
SUNWrk6x
Select the package you want to execute (or select all to execute all
packages).
In this step, if the OSI protocol stack is installed, select packages 16 only and do not
install the RFC1006 packages, including SUNWrk6 and SUNWrk6x. Otherwise, press
Enter to install all the packages. Then, enter y if prompted. For example,
Do you want to continue to install SUNWftabx? y<Enter>
SUNWftama
SUNWftamb
SUNWftamp
SUNWlicsw
SUNWlit
SUNWrk6
SUNWrk6x
Select the package you want to execute (or select all to execute all
packages).
(default: all) [?,??,q]:q<Enter>
Enter q to exit.
3)
#cd /etc/opt/licenses
#./lit_tty
The installer shows the following information.
Select Product
p=Previous Page
Select Solstice FTAM 9.0 for SPARC and the message is displayed as below:
Solstice FTAM
9.0 for SPARC
Servers: [x] 1 [ ] 3 [ ] 5
SERVER NAME
HOSTID
1: igwb2
80c7dff7
Data Checksum: d5
Password: 07BCAA07173858526A52B
Password Checksum: 77
** x=select/deselect
Return=next field **
Enter the Expiration Date, Rights to Use and Password of the License. The installer
prompts the settings are successful, and then displays the information below:
Select Product
p=Previous Page
#sync;sync;sync;reboot
5)
If the OSI protocol stack is installed, the four processes osinetd, osiftamd, osiftrd -164,
and osiftrd -264 are displayed.
If the RFC1006 protocol stack is installed, the three processes osiftamd, osiftrd -164,
and osiftrd -264 are displayed. Also, check whether the rk6d process is running by
using the ps -ef | grep rk6d command.
NSAP
The NSAP represents the network service access point. The FTAM client (Initiator)
finds the FTAM server (Responder) through the NSAP and set up connection with the
server.
The NSAP consists of five parts. See Figure 6-1.
AFI
IDI
SI
NSEL
PA
3)
Partner
The FTAM runs in Initiator/Responder mode. To initiate the connection with the
Responder, the Initiators must know the parameters like NSAP of Responder. Typically,
a Partner is used to represent the FTAM Responder.
#cd /opt/SUNWconn/ftam/bin
Huawei Technologies Proprietary
6-12
#./osiftam
osiftam>rdb add entry1 -n H4980ed0f2d01 -p Cftr -s CPtr
z
-t CFTAM -z 1
-n is followed by the NSAP of the FTAM peer entry1, H indicates the NSAP format
is hexadecimal, and 80ed0f2d is the hostid of FTAM peer.
SNPASubnetworkPoint of Attachment
#cd /opt/SUNWconn/osinet/bin
#./osi_ping -n 4980ed0f2d01
If the peer end is accessible, 4980ed0f2d01 is alive is displayed. 4980ed0f2d01 is the
NSAP of the FTAM peer. Make sure the computer where 4980ed0f2d01 is located is
started and FTAM is running normally when you run the command.
3)
#cd /opt/SUNWconn/ftam/bin
#./osiftam
osiftam>open entry1 -n username -p password
After login is successful, you can use the commands like dir, get, and put to test
whether you can interact with the FTAM Partner. For usage of the commands, refer to
6.3.5 Introduction to Solstice FTAM 9.0.
Note:
Solstice FTAM 9.0 provides you with a graphical tool, ftamtool, to configure the FTAM
parameters. The functions provided by this tool are the same as those of the rdb
command in osiftam. The user usually logs in to a UNIX workstation by Telnet to set the
parameters, and the ftamtool is not always usable, so the ftamtool usage is not
introduced in this section.
#/opt/SUNWconn/ftam/bin/osiftam
osiftam>open entry -n username -p password
In this command, entry is the FTAM Partner name created with the rdb add command.
2)
osiftam>dir remotedir
Huawei Technologies Proprietary
6-14
Note:
Use the open command to connect with the peer end before this command is
executed.
3)
Note:
Use the open command to connect with the peer end before this command is
executed.
4)
osiftam>rdb list
Note:
Do not connect with any Partner if this command is executed.
5)
Installation Preparations
Upgrading Server
Note:
For parameter configuration, refer to Part III Parameter Configuration and System
Commissioning.
Note:
This section applies to the first installation of the server software. For upgrade
operations, skip this step.
After Solaris is started, you can log in to the two hosts from the COM ports of other
terminals or SCs. For Netra 240, you can log in to its COM port by the PC hyper
terminal.
2)
After Solaris is started, you can log in as root by FTP or Telnet.You can log in to
the hosts by the telnet igwb1 or igwb2. The default IP addresses are set in the
/etc/hosts file. For details, see Figure 7-1.
129.1.1.1 igwb1
129.1.1.2 igwb11
129.1.1.3 igwb13
igwb1 default IP address
129.1.1.2 igwb2
129.2.1.2 igwb21
129.2.1.3 igwb23
igwb2 default IP
129.1.1.3 ha-igwb
129.2.1.3 ha-igwb1
129.3.1.3 ha-igwb3
CG9812 default floating IP
Logical
host
127.0.0.1
localhost
129.1.1.1
igwb1
Description
Remarks
IP
address
Logical
host
Description
Remarks
129.2.1.1
igwb11
129.3.1.1
igwb13
Local IP of bge3.
129.1.1.2
igwb2
129.2.1.2
igwb21
129.3.1.2
igwb23
Local IP of bge3.
129.1.1.3
ha-igwb
129.2.1.3
ha-igwb1
129.3.1.3
ha-igwb3
129.1.1.1
1
igwb1-sc
129.1.1.1
2
igwb2-sc
129.1.1.1
3
3310-0
129.1.1.1
4
3310-1
The
three
IP
addresses
are
external floating IP
factory defaults.
II. Check if the two nodes can be switched over each other
For SUN Cluster3.0, to check whether the primary node and the secondary node can
be switched over each other, follow the steps below.
1)
Log in to igwb1 or igwb2, run scstat | more to view the SC information, and you
may get the information below:
Status
--------Cluster node:
------
igwb1
is a cluster member)
Cluster node:
igwb2
is a cluster member)
2)
3)
You can only access the disk arrays on igwb1 or igwb2. Make sure the attached
directories for the disk arrays are correct.
Log in to igwb1 or igwb2 through the SC or by Telnet, and run df -k command to view
the output information. Only on one of the two hosts, you can check the volume of the
disk array, including /var/frontsave, /var/backsave, /var/other, and /ha-igwb.
4)
Run the command below on the host where you can view the volume of the disk
array:
Caution:
z
After you modify the hosts files, make sure you also modify the IP addresses set in
the igwb.ini files. Otherwise, the CG9812 server cannot be started. The default
installation path for igwb.ini is /opt/igwb/config/ini.
1)
For the floating IP addresses, modify them based on your actual configurations. If
the floating IP addresses are not in the same network segment, change the subnet
masks for igwb1 and igwb2 in the /etc/netmasks files. Restart the hosts to enable
the settings.
2)
3)
For other IP factory defaults of igwb1 and igwb2, if they are not in conflict with the
IP addresses configured in the current LAN, keep the factory defaults. Record if an
IP address needs to be modified.
4)
bge1 and bge2 are mutually backed up, sharing the same floating IP. If bge1 is
disabled, bge2 is enabled; if bge2 is disabled, bge1 is enabled.
Default
floating
IP
Onsite
floating IP
Function
bge0
129.1.1.3
10.11.5.30
bge1
129.2.1.3
202.11.6.20
Connect with
SGSN or GGSN
bge3
129.3.1.3
5.16.17.18
1)
Remarks
129.1.1.1 igwb1
(This IP is for maintenance purpose. It can be changed into 10.11.5.1, which is in the sanme network
129.1.1.2 igwb2
(This IP is for maintenance purpose. It can be changed into 10.11.5.2, which is in the sanme network
(If it is not in conflict with the IPs set in the LAN, do not change it.)
129.2.1.3 igwb23
(If it is not in conflict with the IPs set in the LAN, do not change it.)
Caution:
The last three IP addresses are the external service floating IP addresses set by default.
They are configured with same values on igwb1 and igwb2. The floating IP addresses
will not be enabled untill the SC is started.
129.1.1.2 igwb2
(This IP is for maintenance purpose. It can be changed into 10.11.5.2, which is in the sanme network
129.1.1.2 igwb1
(This IP is for maintenance purpose. It can be changed into 10.11.5.1, which is in the sanme network
(If it is not in conflict with the IPs set in the LAN, do not change it.)
129.1.1.3 igwb13
(If it is not in conflict with the IPs set in the LAN, do not change it.)
I. Consolidation
Two or more partial bills are created when the GSN process a PDP call. Consolidation
is to consolidate these partial bills into one or more bills.
II. Sort
Sort the bills on the back disk. Two or more bill formats may be included in a bill
package. Currently, bills can be sorted based on the conditions below:
z
For R98 770, this bill format is compatible with R98 760 and can be only sorted by
RecordType.
For R99 3a0, this format is compatible with R99 390 and R99 360, and can be
ChargingCharacteristics.
For RecordType, bills can be sorted by S-CDR, G-CDR, M-CDR, SMO-CDR, or
SMT-CDR.
For ChargingCharacteristics, bills can be sorted by Hot billing, Flat rate, Prepaid
igwb_install.tar.gz
Binary
sc30_script.tar
Binary
igwb_install.sh
ASCII
igwb_rollback.sh
ASCII
S99CGCfgMonito
ASCII
2)
3)
# cd /etc/rc3.d
# chmod 755 *
4)
Go to the /opt directory and run the command below to begin the setup process.
# cd /opt
# sh ./igwb_install.sh
z
The following information is displayed. Enter c for Chinese, and e for English.
V4.4.0
5)
Go to the /opt/igwb/config/ini directory. Open and configure the igwb.ini file with
the vi tool.
#cd /opt/igwb/config/ini
#vi igwb.ini
Note:
For parameter configurations in igwb.ini, refer to Part III Parameter Configuration and
System Commissioning. Save the igwb.ini file after you finish. Close the vi program.
6)
7)
Run the commands below on igwb1 and igwb2 to start the igwbapp service and
run the related program.
#scswitch -e -j igwbapp
8)
Then, run the commands below on igwb1 and igwb2 to backup the version of the
server application:
# cd
/opt
Huawei Technologies Proprietary
7-8
# sh ./igwb_rollback.sh
Then the following information will appear:
0) Exit
1) Backup
version backup
2) Rollback
version rollback
Select 1 to backup software release. When release backup is finished the following
information will appear:
Backup now ! Please wait ..
Backup complete !
General upgrade. Bill formats and product version are not essentially changed.
Special upgrade. Bill formats and product version are essentially changed
2)
Run the commands below to back up product version on igwb1 and igwb2.
# cd
/opt
# sh ./igwb_rollback.sh
The following information is displayed:
0) Exit
1) Backup
version backup
2) Rollback
version rollback
3)
# cp /opt/igwb/config/ini/igwb.ini /opt/igwb.bak
4)
binary mode) and igwb_install.sh (in ASCII mode) to the destination /opt
directory on igwb1 and igwb2.
5)
Run the command below to check the resources are controlled by igwb1 or igwb2.
Check if the processes are started, including cls_proc, om_proc, knl_proc, and
ap_proc.
7)
If the above processes are started, then the related node controls the resources
and is activated to provide the application services.
8)
Suppose igwb1 controls the resources. On igwb2, perform the operations below:
# cd /opt
# sh ./igwb_install.sh
z
The following information is displayed. Enter c for Chinese, and enter e for English.
Select the language to be installed ( Chinese or English ), [c/e]:
V4.4.0
9)
Run the command below on igwb1 or igwb2 or the client to switch the server from
the primary node to the secondary node.
# scswitch
-S
10) After a few minutes, check if the processes runs properly on the upgraded node
(igwb2).
11) Run the ps -ef | grep _proc command on igwb2. You may see the similar
information displayed below:
root
2188
2182
0 09:27:33 ?
0:01 ./cls_proc
root
2195
2188
0 09:27:34 ?
0:02 knl_proc
root
2196
2195
0 09:27:35 ?
0:01 ./om_proc
root
2197
2195
1 09:27:35 ?
11:30 ./ap_proc 1
Note:
z
If the installation is successful, go on with the steps below. If not, stop the upgrade
process, and then ask for technical support. If the problem cannot be solved, make
sure to roll back to the last version. For details, refer to 7.5 Rolling Back to Last
Version.
12) Run the commands below to back up the product version on igwb1 and igwb2.
# cd
/opt
# sh ./igwb_rollback.sh
The following information is displayed:
0) Exit
1) Backup
version backup
2) Rollback
version rollback
Note:
For auxiliary upgrade on the client, refer to Part IV. You can continue the upgrade
process only if the auxiliary upgrade is executed successfully.
2)
Run the command below on igwb1 or igwb2 to stop the igwbapp service and
related application.
# scswitch -n -j igwbapp
Caution:
The following steps 3)6) must be performed on igwb1 and igwb2, and only if these
steps are finished, you can continue the upgrade process.
3)
# cd /opt/igwb/config/ini
# cp igwb.ini /opt/igwb.bak
Caution:
You may need to reset igwb.ini.
4)
5)
Run the commands below to install the software on igwb1 and igwb2.
# cd /opt
# sh ./igwb_install.sh
6)
7)
Go to the /opt/igwb/config/ini directory to restore the igwb.ini file you back up.
# cd /opt/igwb/config/ini
# cp /opt/igwb.bak igwb.ini
8)
Run the command below on igwb1 or igwb2 to start the igwbapp service.
# scswitch
9)
-e -j igwbapp
After a few minutes, check if the processes run properly on the upgraded node.
Run the ps -ef | grep _proc command on igwb1 and igwb2. You may see the
similar information below is only displayed on one node.
root
2188
2182
0 09:27:33 ?
0:01 ./cls_proc
root
2195
2188
0 09:27:34 ?
0:02 knl_proc
root
2196
2195
0 09:27:35 ?
0:01 ./om_proc
root
2197
2195
1 09:27:35 ?
11:30 ./ap_proc 1
Run the command below on igwb1 or igwb1 to stop the igwbapp and the related
application.
#scswitch -n -j igwbapp
2)
# cd
Run the commands below on igwb1 and igwb2 to roll back the last version:
/opt
# sh ./igwb_rollback.sh
The following information is displayed:
0) Exit
1) Backup
version backup
2) Rollback
version rollback
3)
Run the command below on igwb1 or igwb1 to start the igwbapp service and the
related application.
#scswitch -e -j igwbapp
Upgrading Client
Copy the Client setup directory in the installation CD to a directory on the client.
Double-click \Client\SETUP.EXE. The Choose Setup Language dialog box is
displayed. See Figure 8-1.
Select your desired language, and then click OK. Then, the Welcome dialog box
is displayed. See Figure 8-2.
Click Next. The Software License Agreement dialog box is displayed. See
Figure 8-3.
4)
Click Yes to accept all the terms in the agreement. The User Information dialog
box is displayed. See Figure 8-4.
Enter the user name and company, and then click Next. The Select Program
Folder dialog box is displayed. See Figure 8-5.
Click Next. The Choose Destination Location dialog box is displayed. See
Figure 8-6.
7)
Click Next to copy files. Then, the Setup Complete dialog box is displayed. See
Figure 8-8.
2)
3)
Click Yes. The Remove Programs From Your Computer dialog box is displayed.
See Figure 8-9.
Click OK.
6)
7)
Overwrite the uiconfig.ini file in the system directory with the backup one.
Help
iGWB Client
Uninstall System
HUAWEI
HUAWEI CG9812
User Manual
Table of Contents
Table of Contents
Chapter 1 Installation Overview................................................................................................... 1-1
1.1 Introduction to the Chapter ................................................................................................ 1-1
1.2 Installation Flow ................................................................................................................. 1-1
1.2.1 Installation Flow Chart............................................................................................. 1-1
1.2.2 Installation Time Planning ....................................................................................... 1-2
1.3 Installation Preparations .................................................................................................... 1-3
1.3.1 Hardware Preparations ........................................................................................... 1-3
1.3.2 Software Preparations............................................................................................. 1-5
1.4 Resource Planning ............................................................................................................ 1-6
1.4.1 HA System Planning ............................................................................................... 1-6
1.4.2 IP Address Planning................................................................................................ 1-7
1.4.3 Disk Space Planning ............................................................................................... 1-8
Chapter 2 Installing Hardware...................................................................................................... 2-1
2.1 Introduction to the Chapter ................................................................................................ 2-1
2.2 Cabinet Configuration ........................................................................................................ 2-1
2.3 Hardware Description ........................................................................................................ 2-2
2.3.1 Introduction to Sun Netra 20 ................................................................................... 2-2
2.3.2 Introduction to Sun StorEdge 3310 Disk Array ....................................................... 2-5
2.3.3 Introduction to TC.................................................................................................... 2-6
2.3.4 Introduction to Quidway S3526 LAN Switch ........................................................... 2-7
2.4 Hardware Connections ...................................................................................................... 2-7
2.4.1 Host Hardware Planning ......................................................................................... 2-7
2.4.2 Disk Array Hardware Planning ................................................................................ 2-8
2.4.3 Hardware Connections............................................................................................ 2-8
2.4.4 Description for Cable Connections........................................................................ 2-11
2.4.5 Hardware Power-on .............................................................................................. 2-14
Chapter 3 Configuring TC, Disk Array, and Netra 20................................................................. 3-1
3.1 Introduction to the Chapter ................................................................................................ 3-1
3.2 Configuring TC................................................................................................................... 3-1
3.2.1 Introduction to TC.................................................................................................... 3-1
3.2.2 Configuring TC ........................................................................................................ 3-1
3.3 Configuring Disk Array....................................................................................................... 3-2
3.4 Configuring Netra 20........................................................................................................ 3-26
Chapter 4 Installing and Configuring Solaris ............................................................................. 4-1
4.1 Introduction to the Chapter ................................................................................................ 4-1
4.2 Installing Solaris 8.............................................................................................................. 4-1
4.2.1 Connecting Consoles of Host.................................................................................. 4-1
Huawei Technologies Proprietary
i
Table of Contents
Table of Contents
Installation Flow
Installation Preparations
Resource Planning
Begin Installation
Install Hardware
Check installation
Finish installation
Task description
Estimated time(hour)
Installing hardware
0.5
0.5
1.5
0.5
0.5
Installing VxVM
Configuring VxVM
0.4
10
Checking installation
0.2
Configuration
CPU
2*1.20 GHz
Memory
2 GB
Hard disk
2*73 GB
1)
Netra 20
minicomputer
public
network
for
application
Network Adapter
links.
2)
3)
DVD-ROM
Tape drive
None
Power supply
Capacity
5*36 GB
SCSI port
2.
Power supply
Ethernet port
Serial port
4*Serial port(RJ-45)
Console port
Power supply
Quidway S3526
Ethernet port
24
LAN Switch
Power supply
TC
Item
Configuration
Solaris 8 (02/04 SPARC Platform)
Operating system
Solaris Patch
System
software
Cluster software
Disk management
software
Billing interface
Vertel
UTS-FTAM
software (optional)
(Solaris version)
installation
software
Applications
CG9812 applications
igwb1
igwb2
SUN OS
SUN OS
SUN Cluster
SUN Cluster
Volume Manager
Volume Manager
FTP/FTAM(optional)
FTP/FTAM(optional)
CG9812 Server
CG 9812 Server
3310-0
Mirroring
3310-1
HA System Planning
IP Address Planning
Primary node
Secondary node
Cluster Name
sc-igwb
sc-igwb
Cluster Node
igwb1
igwb2
Transport path 1
hme0
hme0
Transport path 2
eri0
eri0
NAFO Group 0
qfe0
qfe0
NAFO Group 1
qfe1/qfe2
qfe1/qfe2
Item
Primary node
Secondary node
NAFO Group 2
qfe3
qfe3
Quorum Device
d4
d4
The float IPs and the fixed IPs are set in the same network segment.
Below is an example of the IP configuration. See Table 1-5 and Table 1-6.
Table 1-5 IP address planning
Device
primary node
secondary node
Float IP (logical
host name)
Description
129.1.1.1(igwb1)
129.1.1.2
129.1.1.3
NMS
(igwb2)
(ha-igwb)
maintenance
and
the
console.
qfe1/qfe2
129.2.1.1(igwb11)
qfe3
129.3.1.1(igwb12)
eri0
Not required
129.2.1.2
129.2.1.3
(igwb21)
(ha-igwb1)
129.3.1.2
129.3.1.3
(igwb22)
(ha-igwb2)
billing center.
Not required
Heartbeat link 1.
SGSN
or
the
GGSN.
primary node
secondary node
Device
hme0
Not required
Not required
Float IP (logical
host name)
-
Description
Heartbeat link 2.
PC
function
Connect with the TC COM
Maintenance
129.1.1.4(admin)
terminal
TC
129.1.1.5
IP of TC.
3310-0
129.1.1.6
Manageable IP of 3310-0.
3310-1
129.1.1.7
Manageable IP of 3310-1.
Root Directory
Allocate sufficient disk space to the root directory since its size cannot be changed
with the UNIX commands. The type of the root file system is User File System (UFS).
2)
SWAP
The required disk space for SWAP depends on the size of the host memory and the
expected maximum memory size. In short, the space of SWAP and the host memory
decides the maximum available memory. The size of SWAP shall be at least 1.5 times
larger than the physical memory. According to the disk capacity and its expansion
requirements, the SWAP is set to 10 GB.
3)
/globaldevices
This is the global device partition with 500 MB. It is used by the VxVM.
Mount point
Size
Description
c1t0d0s0
57 GB
Root.
c1t0d0s1
swap
10 GB
SWAP.
The size of the whole hard disk,
c1t0d0s2
Overlap
68.35GB
c1t0d0s3
Volume Manager.
Note: This partition must be
reserved.
This is reserved to encapsulate the
c1t0d0s4
Volume Manager.
Note: This partition must be
reserved.
c1t0d0s5
c1t0d0s6
c1t0d0s7
/globaldevice
s
-
512MB
1)
Allocated hard
Hotspare hard
name
disk
disk
Host
Description
rootdg
None
igwb1
Rootdg of igwb1
rootdg
None
igwb2
Rootdg of igwb2
igwbdg
LUN1 in 3310
None
igwb1/igwb2
2)
Shared disk
group
(disk
group
used for
Logical
Logical
volume
volume
name
size
igwbdg-stat
100MB
mirror)
Mount point
Function
Fixed size.
Fixed size. This
c2t0d1
igwbdg
log-alarm
4GB
/var/other
volume is used to
store the log and
alarm data.
c3t0d1
48GB
/var/frontsave
10
11
12
c2t8d0
c2t9d0
c2t10d0
c2t11d0
c2t12d0
3310-1
7
8
9
10
11
12
c3t8d0
c3t9d0
c3t10d0
c3t11d0
c3t12d0
Cabinet Configuration
Hardware Description
Hardware Connections
CG9812 Cabinet
Power distribution frame (2U)
Dummy panel (3U)
Dummy panel (3U)
Dummy panel (3U)
Dummy panel (3U)
Dummy panel (3U)
Dummy panel (3U)
Non-standard dummy panel (1U)
Quidway S3526-1 (1U)
Cabling frame (1U)
Quidway S3526-0 (1U)
Cabling frame (1U)
Non-standard dummy panel (1U)
TC (1U)
SUN StorEdge 3310-1 (2U)
Non-standard dummy panel (1U)
SUN StorEdge 3310-0 (2U)
Non-standard dummy panel (1U)
42U
Value
CPU
Memory
2 GB
Hard disk
2*73 GB
Ambient index
value
parameter
AC
Power
supply
DC
(DC).
Running
temperature
Storage
Running
Humidity
Storage
Value
Height
Width
425.0 mm (16.73in)
Depth
508.0 mm (21in)
Weight
One 4-port external network adapter. The four ports are qfe0, qfe 1, qfe 2 and qfe
3. This adapter is used to connect with the public network for application
purposes. qfe1 and qfe2 serve as Network Adapter Failover (NAFO) links.
Two PCI Ultra SCSI HostAdapter cards, which are used to connect with the 3310
disk arrays.
Redundant components.
Note:
Typically, five hard disks are inserted into the slots 7, 8, 9, 10, and 11 for each disk
array. To add more disks, insert one into slot 12 first, and then slots 1, 2, 3, 4, 5, and 6
sequentially.
2.3.3 Introduction to TC
I. The front view of TC
The front view of TC is shown in Figure 2-6.
Note:
This is the front view and back view of AlterPath ACS4. For the actual TC, refer to the
packing list came with the product.
Qu d
i way S3 526
Console Interface
10
12
14
16
18
20
22
24
11
13
15
17
19
21
23
Note:
For more information about LAN Switch, refer to Quidway S3528 Series LAN Switch
Installation Manual.
Netra 20(DC)
I/O slot
Purchase No.
PN No.
X1034A
501-5406
X6758A
375-3057
X6758A
375-3057
X1033A
501-5019
switch
description
Disk array
3310(J-DC)
Purchase No.
XTA-3310-36GB-10K
3310-0 3310-1
name
-
PN No.
540-5522
Description
36G 3310 hard disk
No.
01
Connectio
Source
n type
device
100M
Ethernet
Source
device
port
qfe0 in
host 1
slot0 of
PCI1
Destination
device
NMS and
LMT
Destinati
on device
Remark
port
Public
network
No.
02
03
04
05
06
07
08
Connectio
Source
n type
device
100M
Ethernet
100M
Ethernet
100M
Ethernet
100M
Ethernet
100M
Ethernet
100M
Ethernet
100M
Ethernet
Source
device
port
Destination
device
qfe1 in
Host 1
slot1 of
GSN
PCI1
qfe2 in
host 1
slot2 of
GSN
PCI1
qfe3 in
host 1
slot3 of
PCI1
qfe0 in
host 2
slot0 of
PCI1
Billing
center (BC)
NMS
LMT
qfe1 in
host 2
slot1 of
GSN
PCI1
qfe2 in
host 2
slot1 of
GSN
PCI1
10
Ethernet
on device
host 2
slot3 of
BC
LAN
Public
Switch-0
network
LAN
Public
Switch-1
network
Host2
LAN
Public
Switch-1
network
built-in
100M
Port in
hme0
Host2
(crossover)
slot0 of
PCI4
11
SCSI
host 1
12
SCSI
host 1
SCSI1 in
PCI3
SCSI1 in
PCI2
Public
network
Private
network
Private
network
3310-0
CH1 port
3310-1
CH1 port
network
network
port
host 1
Public
Switch-0
(crossover)
Ethernet
network
Public
100M
eri0
Public
LAN
PCI1
host 1
Remark
port
qfe3 in
100M
09
and
Destinati
No.
Source
n type
device
Source
device
Destination
device
port
SCSI1 in
13
SCSI
host 2
14
SCSI
host 2
15
SCSI
3310-0
CH0 port
3310-0
16
SCSI
3310-1
CH0 port
3310-1
17
18
19/20
21/22
Connectio
COM port
cable
COM port
cable
100M
Ethernet
100M
Ethernet
host 1
host 2
PCI3
SCSI1 in
PCI2
COM port
A
COM port
A
Destinati
on device
3310-0
CH3 port
3310-1
CH3 port
Single
Bus port
Single
Bus port
TC
2# port
TC
3# port
Two
3310-0
controller
ports
Two
3310-1
controller
ports
Note:
Remark
port
Manage
ment
Manage
ment
Manage
ment
Manage
ment
3310-0
qfe0
3310-1
qfe1
To LMT
and NMS
qfe2
qfe3
To GSN
To GSN
To BC
To TC
igwb1
Private
network
Private
network
To LMT
and NMS
qfe1
To GSN
qfe0
qfe2
qfe3
To GSN
To BC
To TC
igwb2
eri0
Figure 2-9 Connections between Sun Netra 20 and Sun StorEdge 3310
Quidway S3526
(1)
(2)
(3)
igwb2
qfe0
(4)
igwb1\igwb2
qfe2
(5)
igwb2
qfe3
LAN Switch-1
Quidway S3526
(3)
igwb1
qfe0
(4)
igwb1\igwb2
qfe1
(5)
igwb1
qfe3
LAN Switch-0
Cable (1) and cable (2) are used to couple two LAN Switches for subtending.
Caution:
Dangling cables must be prohibited.
III. Connections between the primary server and the secondary server
Connect the external eri0 port of the primary server with eri0 of the secondary server.
Connect hme0 of the primary server with hme0 of the secondary server. These two
connections serve as heartbeat links between the primary server and the secondary
server. All cables in use are straight-thru cables (crossover cables).
Connect the PGND bar of the DC distribution cabinet securely with the nearest
PGND bar provided by the equipment buyer through the PGND bus. The PGND
cables are yellow-green plastic insulated copper wires with the same core
diameter as that of the power cables.
For Netra 20, connect the power cables and ground cables for the internal devices in
the CG9812 cabinet as indicated in Figure 2-12.
LAN Switch-1
LAN Switch-0
TC
3310-1
3310-0
Netra 20-1
Netra 20-0
Figure 2-12 Connections of power/ground cables for devices in the CG9812 cabinet
(Netra 20)
Caution:
z
For the minicomputers and disk arrays, sudden power-off is prohibited on the
CG9812 server. Because after UNIX is suddenly powered off, it must be manually
maintained before it can run.
Configuring TC
Configuring Netra 20
3.2 Configuring TC
3.2.1 Introduction to TC
The HA system does not include a video adapter or a display. It is configured with a TC
to transfer the control signals from the two hosts and display them on the monitor
console.
3.2.2 Configuring TC
I. Connect the TC with the console
Your console and your TC must be on the same physical LAN. You can connect one
RJ-45 cable from the Ethernet port of the TC to a spare port from the LAN Switch-0,
and another cable from another spare port of LAN Switch-0 to the console used to
manage the TC.
Example: if the console has IP address 192.168.160.1 the command would be:
route add 192.168.160.10 mask 255.255.255.0 192.168.160.1
III. Log in to TC
From the console issue the telnet command to log in to the TC. Enter root as the user
name and tslinux as password.
A Configuration Wizard screen is displayed. You can set the parameters of the TC.
*********************************************
**C O N F I G U R A T I O N
W I Z A R D**
*********************************************
INSTRUCTIONS for using the Wizard:
You can:
1)
Enter the appropriate information for your system and press ENTER or
2)
Press ENTER if you are satisfied with the value within the brackets
3)
Note:
Name the two StorEdge 3310 disk arrays 3310-0 and 3310-1. Both of them need to be
configured.
Power on StorEdge 3310, and tip to the disk array from the console.
#tip s3310
2)
Press Ctrl + L to refresh the screen. The following information is displayed. see
Figure 3-2.
Select Terminal (VT100 Mode) from the menu, and then press Enter to open the
main menu. See Figure 3-3.
Enter the IP address: 129.1.1.6 (3310-0), 129.1.1.7 (3310-1), and subnet mask:
255.255.0.0, and then press ESC. Note that the given values are for example
purposes only. See Figure 3-5.
Click Yes to set the IP address. The following information is displayed. See
Figure 3-6.
Note:
To set the IP addresses of StorEdge 3310, refer to Table 1-6, that is, set 3310-0 to
129.1.1.6, and 3310-1 to 129.1.1.7.
8)
Select Terminal (VT100 Mode) from the menu, and then press Enter to open the
main menu.
3)
Select view and edit SCSI channels from the main menu. Configure the SCSI
channels as indicated in Figure 3-8. Press Esc to return to the main menu. Then,
click Yes to reset the controller.
Select Terminal (VT100 Mode) from the menu, and then press Enter to open the
main menu. See Figure 3-10.
Select view and edit Logical drives from the main menu, and then press Enter
to configure the logical drive. See Figure 3-11.
Caution:
For a new disk, no logical disk is created. See Figure 3-11. Delete the existing logical
disks, if any. If LUN is mapped, you may fail to delete the logical disks. Unmap the
host LUN before you delete the logical disks.
Select LG0, and then press Enter to continue. See Figure 3-12.
Click Yes, and then press Enter to continue. The following interface is displayed.
See Figure 3-13.
Select RAID5, and press Enter to continue. Select the first four drives as RAID5
mirror disks. In the Slot column, an asterisk (*) is marked if a disk is selected. See
Figure 3-14
Select Assign Spare Drives, and then press Enter to select the HotSpare disks.
The following interface is displayed. See Figure 3-16.
Select all the rest disks as HotSpare drives. In the Slot column, an asterisk (*) is
marked if a disk is selected. Press Esc to confirm your selection. The following
interface is displayed. See Figure 3-17.
Select Partition logical drive, and then press Enter to partition the logical disk.
2)
The system then prompts Continue Partition Logical Drive? See Figure 3-22.
Click Yes, and then press Enter.
Enter 200 for partition0 in Partition Size (MB), and then press Enter. See
Figure 3-24.
The following interface is displayed. See Figure 3-25. Click Yes, and then press
Enter.
Move to the second row, and then press Enter to allocate space for partition1.
7)
Enter 103,228 in Partition Size (MB), and then press Enter. See Figure 3-26.
The following interface is displayed. See Figure 3-27. Click Yes, and then press
Enter to complete the partition.
Press Esc twice to return to the main menu. On the main menu, select view and
edit Host LUNs, and then press Enter. See Figure 3-28.
Caution:
Make sure CHL 1 is set to Primary Controller. If CHL1 ID 0 (Secondary Controller) is
displayed, delete this channel, and then add CHL 1 ID 0 (Primary Controller).
3)
Select Logical Drive, and then press Enter. See Figure 3-30.
Select row 0, and then press Enter to map the first LUN. See Figure 3-31.
Select the RAID5 logical drive, and then press Enter. See Figure 3-33.
In Figure 3-35, select Map Host LUN, and then press Enter.
The following interface is displayed. See Figure 3-36. Click Yes, and then press
Enter.
Note:
Map host LUN for CH3 in the same way.
16) Then, press Esc till the following interface is displayed. See Figure 3-42.
Huawei Technologies Proprietary
3-25
Note:
I. Use a RJ45-DB25 serial port cable to connect the monitor console with Netra
20.
Note:
<LOM> is displayed if Netra 20 is powered off. In this case, power on Netra 20, and
then the Ok prompt appears in about three minutes.
2)
3)
V. Restart Netra 20
ok reset-all
Note:
For hardware installation in a later section, Netra 20 must use ttya (not ttyb) to
connect with the TC. Otherwise, no output information is displayed when you log in to
Netra 20 from the TC.
Installing Solaris 8
Configuring Solaris
Installing Utilities
Note:
During the setup process, press ESC+2 to go to the next step, press Up or Down
to locate an option, and press Space or Enter to select the selection.
hosts (igwb1 and igwb2) concurrently. Make sure that the same parameters are
configured for the two hosts.
Description
Insert the Solaris 8 System Software 1 of 2 CD into the CD-ROM of the
console.
Enter the OK state.
Method 1: If the workstation is not installed with UNIX, press Ctrl+] on the
console, type Send brk, and press Enter to show the ok prompt.
Method 2: If Solaris is installed, type halt as the user root to show the ok
prompt.
Boot the host from the CD-ROM. Type boot cdrom after the OK prompt:
ok boot cdrom
1. French
9. Traditional Chinese
Please make a choice (0 - 9), or press h or ? for help: 0
1. Albania (ISO8859-2)
Step
Description
Select the terminal type. Select DEC VT100. Because no monitor is
configured in the HA system, the installer cannot identify the terminal type.
To select he terminal type, follow the steps below:
Press Return to show more choices.
Please make a choice (0 - 51), or press h or ? for help: 0
Esc-6_Help
Networked
[X] Yes
[ ] No
Use DHCP
[ ] Yes
[X] No
10
[X] qfe0
[ ] qfe1
[ ] qfe2
[ ] qfe3
Enter the host name. Enter igwb1 for the primary node, and igwb2 for the
11
Step
Description
Enter the IP addresses. The IP address of igwb1 is 129.1.1.1, and that of
12
14
Enable IPv6
[ ] Yes
[X] No
16
Configure
Kerberos Security
[ ] Yes
[X] No
18
[ ] NIS
[ ] DNS
[ ] LDAP
[X] None
Step
Description
Select the Geographic Region, for example, Asia, Eastern. See below:
19
Regions
[X] Asia, Eastern
[ ] United States
Select Time Zone. Select the local time zone, such as Hong Kong. See
below:
20
Time zones
[ ] Hong Kong
21
(4 digits) :
2004
Month (1-12)
02
Day
(1-31)
03
Hour
(0-23)
09
Minute (0-59)
00
23
Initialize the setup process. Press ESC + 4 to select Initial. See below:
F2_Upgrade
24
F4_Initial
F5_Exit
F6_Help
F3_Go Back
Esc-4_Flash
F5_Exit
F6_Help
Step
Description
Select the following character sets from the Geographic Region menu.
Select the geographic regions for which support should be installed.
[ ] Eastern Europe
[/] Asia
[ ] PC Kanji (ja_JP.PCK)
25
[X]
[X]
[X]
Canada-English (ISO8859-1)
[X]
26
U.S.A. (en_US.ISO8859-1)
Select
Select the components. Select Entire Distribution Plus OEM support for
full install. See below:
27
support 64-bit
1587.00 MB
[X] c1t0d0
[ ] c1t1d0
(72538 MB)72538 MB
Determine whether to preserve the existing data on the hard disk. Press
ESC + 2 to select continue to overwrite the data. See below:
29
Do you want to preserve existing data? At least one of the disks you've
selected for installing Solaris software has file systems or unnamed
slices that you may want to save.
F2_Continue
F3_Go Back
F4_Preserve
F5_Exit
F6_Help
Determine whether to lay out the file system automatically. Press ESC + 4 to
30
F5_Exit F6_Help
31
32
Partition the hard disk as indicated in 1.4.3 I. 3), and then select Continue.
Step
Description
Press ESC + 2 to confirm the partition.
File system/Mount point
Disk/Slice
Size
=============================================================
33
c1t0d0s0
57GB
swap
c1t0d0s1
10GB
overlap
c1t0d0s2
68.35GB
/globaldevices
c1t0d0s6
512MB
problems.
F2_Continue
F3_Go Back
F4_Remote Mounts
F5_Exit
F6_Help
35
c1t0d0s0
57 GB
swap
c1t0d0s1
10 GB
/globaldevices
c1t0d0s6
512 MB
=================================================================
F2_Continue
F4_Change
F5_Exit
F6_Help
Esc-2_OK
Installation?
F5_CancelqReboot
After
Step
Description
Determine whether to reboot the computer automatically after installation.
37
Start the setup process, and the setup progress is displayed. The setup
38
process takes about 40 minutes. After installation, the system will reboot
automatically.
After Solaris is restarted, the system prompts to enter and confirm the
password of root. Remember the password. See below
39
Root password:******
Press Return to continue.
Re-enter your root password: ******
When the following message appears, select 1, and then press Enter. See
below:
Media:
40
1. CD/DVD
2. Network File System
3. Skip
Media [1]:<Enter>
Insert the Solaris 8 Software 2 of 2 CD, and then press Enter. See below,
41
42
Product
Result
More Info
Step
Description
When the following message appears, select 1, and then press Enter. See
below:
Media:
43
1. CD/DVD
2. Network File System
3. Skip
Media [1]:<Enter>
Insert the CD for Solaris 8 Languages and press Enter. See below:
44
Please insert the CD/DVD for Solaris 8 Languages (2/02 SPARC Platform
Edition).
After you insert the disc, please press Enter: <Enter>.
45
Description
Insert the patch CD into the CD-ROM of the corresponding host or
workstation console.
Step
Description
Install the patch as root.
2*
# cd /cdrom/cdrom0/sun/install/
# sh ./setup-standard.sh
directory by default.
Where should this package be installed? [/opt/SUNWexplo]:
10
11
12
13
14
15
Step
16
Description
Enter your address (line 1). Press Enter.
Address (line 1) []:
17
18
19
20
24
Select the geographic region where the local SUN branch is located. For
22
24
25
26
information.
Are these values okay? [y,n] y
27
28
29
Step
Description
The following information is displayed. Select yes, and then press Enter.
30
Description
Insert the patch CD into the CD-ROM of the corresponding host or
workstation console.
Log in as root, and then run the commands below:
# cd /cdrom/cdrom0/sun/patch/8
# unpack-patches
Run the command below to begin the setup process. This process may
# sync;sync;sync
# reboot
Description
Insert the SAN software installation CD into the CD-ROM of the
corresponding host or workstation console.
Step
Description
Log in as root, and then run the commands below:
# cd /cdrom/cdrom0/sun/patch/SAN
# unpack-patches
Are you ready to unpack patches into /tmp/SAN? [y/n]:
#cd /tmp/SAN
#./install_patches
Are you ready to continue with install? [y/n]: y
#unpack-patches
Are you ready to unpack patches into /tmp/8? [y/n]: y
Target for unpacking patches /tmp/8 exists!
May I delete /tmp/8? [y/n] y
#cd /tmp/8
#./install_patches
Are you ready to continue with install? [y/n]: y
Description
Insert the driver CD into the CD-ROM of the corresponding host or
workstation console.
Step
Description
Run the commands below to install the SCSI card driver:
#mkdir -p /export/home/software/scsi
#cd /cdrom/cdrom0/sun/progs/SUNWqus/8
#cp SUNWqus_8_all.tar.gz
/export/home/software/scsi/
#cd /export/home/software/scsi
#gunzip SUNWqus_8_all.tar.gz
#tar xvf SUNWqus_8_all.tar
#pkgadd d .
3
4
5
Description
Log in as root, and then go to /cdrom/cdrom0/sun/patch/SUNWqus/8.
Run the commands below:
#cd /cdrom/cdrom0/sun/patch/SUNWqus/8
#unpack-patches
#cd /tmp/8
#./install_patches
Are you ready to continue with install? <y/n> y
Step
Description
Restart the computer after installation.
# sync;sync;sync
# reboot -- -r
Use the format command to view all the hard disks on the disk array.
Caution:
Make sure the above software packages are installed in the above sequence. Restart
the computer after a package is installed. The computer can automatically detect the
disk array status during the restart process.
loghost igwb1.net
129.2.1.1 igwb11
129.3.1.1 igwb12
129.1.1.2 igwb2
129.2.1.2 igwb21
129.3.1.2 igwb22
129.1.1.3 ha-igwb
129.2.1.3 ha-igwb1
129.3.1.3 ha-igwb2
loghost igwb2.net
129.2.1.2 igwb21
129.3.1.2 igwb22
129.1.1.1 igwb1
129.2.1.1 igwb11
129.3.1.1 igwb12
129.1.1.3 ha-igwb
129.2.1.3 ha-igwb1
129.3.1.3 ha-igwb2
Note:
The /etc/hosts records the IP addresses of the local nodes and all the nodes in the
dual system. 129.1.1.1 is the IP address of the primary node, and 129.1.1.2 is the IP
address of the secondary node. For a specific IP address, enter as indicated in the IP
planning table.
Create hostname.qfe3
# vi /etc/hostname.qfe3
Create hostname.qfe3
# vi /etc/hostname.qfe3
Add a comment on this line. Then the user root can log in to the host by Telnet.
target=2 lun=1;
name="sd" class="scsi"
target=3 lun=1;
name="sd" class="scsi"
target=4 lun=1;
name="sd" class="scsi"
target=5 lun=1;
Note:
This line is added because Sun Cluster 3.0 does not support the Loopback file system.
For details, refer to Sun Cluster 3.0 Release Notes.
Description
Insert the TOP software CD into the CD-ROM.
Log in to igwb1 or igwb2 as root, and then go to the setup directory.
# cd /cdrom/cdrom0
# cd sun/tools/top
Step
3
Description
Copy the installation package to the temp directory.
# cp top.3.5b8.SPARC.64bit.Solaris.8.pkg.tgz /tmp
Unpack the software package
# cd /tmp
# gzcat -d top.3.5b8.SPARC.64bit.Solaris.8.pkg.tgz|tar xvfInstall the package.
# pkgadd -d .top
Description
Insert the VTS software CD into the CD-ROM.
Log in to igwb1 or igwb2 as root, and then go to the following directories.
#cd /cdrom/cdrom0/SunVTS-5.1
In this directory, you can find the files below:
SUNWvts
SUNWvtsmn
SUNWvtsx
#cd 8
In this directory, you can find the files below:
SUNWlxml SUNWlxmlx install-s8xmlpkgs.sh
## Installing part 1 of 1.
/usr/lib/sparcv9/libxml2.so <symbolic link>
/usr/lib/sparcv9/libxml2.so.2
[ verifying class <none> ]
Installation of <SUNWlxmlx> was successful.
Step
Description
Run the commands below:
#cd ..
#pkgadd -d .
This is interactive installation process. It is required to select the following
parameters:
Select package(s) you wish to process (or 'all' to process
Insert the patch CD into the CD-ROM, and then go to the setup directory.
#cd /cdrom/cdrom0/sun/patch/SunVTS/5.1
Unpack the package.
# unpack-patches
Are you ready to unpack patches into /tmp/5.1? [y/n]: y
# cd /tmp/5.1
Add the patch.
# patchadd 112336-02
If the installation is successful, the following information is displayed on the
8
screen:
Patch packages installed:
SUNWvts
SUNWvtsx
Installation Preparations
Logical hosts
The HA system uses the names of the network adapters for communication purposes,
so the /etc/hosts file must provide all the related information.
Check whether the /etc/hosts file contains the same contents below. If not, modify it.
I. On igwb1
#
# Internet host table
#
127.0.0.1 localhost
129.1.1.1 igwb1
loghost igwb1.net
129.2.1.1 igwb11
129.3.1.1 igwb12
129.1.1.2 igwb2
129.2.1.2 igwb21
129.3.1.2 igwb22
129.1.1.3 ha-igwb
129.2.1.3 ha-igwb1
129.3.1.3 ha-igwb2
II. On igwb2
#
# Internet host table
#
127.0.0.1
localhost
129.1.1.2
igwb2 igwb2.huawei.com
129.2.1.2
igwb21
129.3.1.2
igwb22
129.1.1.1
igwb1
129.2.1.1
igwb11
129.3.1.1
igwb12
129.1.1.3
ha-igwb
129.2.1.3
ha-igwb1
129.3.1.3
ha-igwb2
loghost
Note:
On igwb1
On igwb2
Restart igwb1
Go to the Sun Cluster 3.0 setup directory with the commands below:
#cd /cdrom/cdrom0/sun-internal/progs/SunCluster/3.0/
#cd Sun_Cluster_3.0_Update3_GA
#telnet igwb1
root@igwb1#cd /install
root@igwb1#gzcat suncluster_3_0_u3_solaris8.tar.gz|tar xvf
root@igwb1#cd suncluster_3_0_u3_solaris8/SunCluster_3.0
root@igwb1#cd tools
This directory includes the files below:
Upgrade
2)
defaults
lib
scinstall
root@igwb1 # ./scinstall
3)
Note:
On igwb1, select 1) Establish a new cluster using this machine as the first
node.
Press Ctrl+D to return to the main menu during the setup process.
Note:
4)
igwb1.
If the names of the two nodes in the Cluster are correct, type y; if not, enter n to reset
them.
Do you need to use DES authentication (yes/no) [no]? <Enter>
Is it okay to accept the default network address (yes/no) [yes]?
Is it okay to accept the default netmask (yes/no) [yes]?
Note:
The default network address is 172.16.0.0, and the default netmask is 255.255.0.0.
Set these addresses based on your actual configurations.
Select eri0 as the primary private network adapter, and hme0 as the secondary
private network adapter.
Select the first cluster transport adapter to use:
1) eri0
2) hme0
3) Other
Option: 1
Note:
Note:
Note:
Your settings are displayed. If the parameters are correct, select yes to continue with
the setup process; if not, select no to reset them.
Continue to configure the Cluster. Then, select q to close the Main Menu.
Insert the patch CD into the CD-ROM, and run the commands below as root.
root@igwb1#cp -r /cdrom/cdrom0/sun/patch/SunCluster/3.0
/install/sc3.0_8
root@igwb1# cd /install/SC3.0-5_8-cluster
root@igwb1#unpack-patches
Are you ready to unpack patches into /install/SC3.0-5_8-cluster? [y/n]: y
2)
root@igwb1#cd /install/SC3.0-5_8-cluster/*Cluster
root@igwb1#./sc_install_cluster
Are you ready to continue with install? [y/n]: y
Use '/usr/bin/showrev -p' to verify installed patch-ids.
Refer to individual patch README files for more patch detail.
Rebooting the system is usually necessary after installation.
/etc/inet/ntp.conf.cluster
V. Restart igwb1
root@hwhlr-ph1 # sync
root@hwhlr-ph1 # sync
root@hwhlr-ph1 # init 6
Cluster node:
Node name
Status
igwb1
Online
Restart igwb2
#telnet igwb2
root@igwb2# cd /install
root@igwb2#gzcat suncluster_3_0_u3_solaris8.tar.gz|tar xvf
root@igwb2#cd suncluster_3_0_u3_solaris8/SunCluster_3.0
root@igwb2#cd /tools
The current directory contains the following files:
Upgrade
2)
defaults
lib
scinstall
root@igwb2 # ./scinstall
The following information is displayed:
*** Main Menu ***
Option:2
Add this machine as a node in an established cluster.
3)
Continue to configure SUN Cluster 3.0. Then, enter q to close the Main Menu
/etc/inet/ntp.conf.cluster
Note:
1)
root@igwb1#scdidadm -L
Specify a hard disk on the disk array for the Quorum device. Here, select d4.
For example:
igwb1>scdidadm -L
1
igwb1:/dev/rdsk/c0t0d0
/dev/did/rdsk/d1
igwb1:/dev/rdsk/c1t0d0
/dev/did/rdsk/d2
igwb1:/dev/rdsk/c1t1d0
/dev/did/rdsk/d3
igwb2:/dev/rdsk/c2t0d0
/dev/did/rdsk/d4
igwb1:/dev/rdsk/c2t1d0
/dev/did/rdsk/d4
igwb2:/dev/rdsk/c3t0d0
/dev/did/rdsk/d5
igwb1:/dev/rdsk/c3t1d0
/dev/did/rdsk/d5
igwb1:/dev/rdsk/c2t1d1
/dev/did/rdsk/d6
igwb2:/dev/rdsk/c2t0d1
/dev/did/rdsk/d6
igwb1:/dev/rdsk/c3t1d1
/dev/did/rdsk/d7
igwb2:/dev/rdsk/c3t0d1
/dev/did/rdsk/d7
igwb2:/dev/rdsk/c0t0d0
/dev/did/rdsk/d8
igwb2:/dev/rdsk/c1t0d0
/dev/did/rdsk/d9
10
igwb2:/dev/rdsk/c1t1d0
/dev/did/rdsk/d10
Note:
From above, you can see the disks d4, d5, d6 and d7 are shared by the primary
and secondary nodes. d4 and d6 are on LUN0, and d5 and d7 are on LUN1. Here,
d4 is used as the Quorum device.
2)
root@igwb1#scconf -a -q globaldev=d4
root@igwb1#scconf -c -q reset
root@igwb1#scconf -a -T node=.
Status
---------
------
Cluster node:
igwb1
Online
Cluster node:
igwb2
Online
Endpoint
--------
Status
--------
------
igwb2:eri0
Path online
igwb2:hme0
Path online
---------
Node votes:
igwb1
Online
Node votes:
igwb2
Online
-----------
Online
Primary
Secondary
------------
-------
---------
Status
------------
------
------------------------------------------------------------------
2)
Log in as root.
#cd /cdrom/cdrom0/sun-internal/progs/veritas-vm
#cd 3.5
The current directory contains the foundationproduct3.4sunw.tar.gz installation
package.
3)
#scvxinstall
Do you want Volume Manager to encapsulate root [no]? y
Where is the Volume Manager cdrom? /install/foundationproduct3.4sunw
6)
Please
enter
Volume
Manager
license
key
[none]:xxx
(for
example,
rrpu-ypr6-wp69-204k-6ppp-6ppr-pp)
Note:
Enter the temporary License key before you get the permanent one. Make sure you
apply for a permanent License and install it. If not, after the temporary License
expires, the volume manager cannot be reset if a system failure occurs.
To apply for a permanent License, fill in your hostid in the application form provided
with the product by fax or email to Sun Microsystems Inc. Before it is granted, ask
for a temporary License with Sun Microsystems Inc
2)
Log in as root.
#cd /cdrom/cdrom/sun/patch/veritas-vm
#cd 3.5
#ls
You can find the files below in the current directory:
112392-07.zip 113203-03.zip 113595-05.zip 113596-04.zip
3)
#unpack-patches
Are you ready to unpack patches into /tmp/3.5? [y/n]: y
Cleaning out /tmp/3.5...
Unpacking.....
Patch 112392-06
Patch 113203-03
Patch 113595-05
Patch 113596-03
4)
Caution:
Make sure you have the latest patches on hand. If not, contact Sun Microsystems for
technical support.
Log in as root, and then execute the command below to disable the DMP
function:
Huawei Technologies Proprietary
5-13
#vxdiskadm
The following information is displayed:
Select an operation to perform:17
on a controller by VxVM)
Enter a controller name [<ctlr-name>,all,list,list-exclude,q,?] all
Continue operation? [y,n,q,?] (default: n) y
#sync
#sync
#init 6
2)
3)
20
1 0 19:42:32 ?
Note:
8301aad5
Caution:
The hostids are different for the two minicomputers.
= R8CE-FR26-NSNN-R4O4-OZNP-PPP6-PPPP-OL
Product Name
License Type
= DEMO
OEM ID
Demo End Date
= 4095
= Fri Jul 23 00:00:00 2004
(60.3 days from now).
Features :=
VxVM
CPU Count
= Enabled
= Not Restricted
The information indicates that no permanent License is entered for the product. Note
that the letters in bold indicate the expiry date of the temporary license. After the date,
enter a permanent license.
Configuring NAFO
Note:
Unless otherwise specified, all the operations in this section shall be performed on
igwb1 and igwb2.
TYPE
DISK
GROUP
STATUS
c1t0d0s2
sliced
rootdisk_1
c1t1d0s2
sliced
online
c3t0d0s2
sliced
error
c3t0d1s2
sliced
error
c4t0d0s2
sliced
error
c4t0d1s2
sliced
error
rootdg
online
Choose the second disk as the mirroring disk of the local hard disk, for example, the
c1t1d0s2 in this example. You can select the disk according to actual conditions.
TYPE
DISK
GROUP
STATUS
c1t0d0s2
sliced
rootdisk_1
rootdg
online
c1t1d0s2
sliced
online
c3t0d0s2
sliced
error
c3t0d1s2
sliced
error
c4t0d0s2
sliced
error
c4t0d1s2
sliced
error
Caution:
rootdisk_1 is the local disk obtained with #vxdisk command.
Note:
Unless otherwise specified, perform the operations in this section only on igwb1.
TYPE
DISK
GROUP
STATUS
c1t0d0s2
sliced
rootdisk_1
c1t1d0s2
sliced
online
c3t0d0s2
sliced
error
rootdg
online
c3t0d1s2
sliced
error
c4t0d0s2
sliced
error
c4t0d1s2
sliced
error
Select c3t1d1 and c4t1d1 as the disks of the igwbdg disk group. c3t1d0 and c4t1d0
are selected as LUN0 in 200 MB. This LUN is set for system maintenance purpose.
Note:
The drive letter varies with the devices. Select based on the actual configurations.
Caution:
z
c3t0d1 in the script below should be the actual disk array number. View the
numbers with the format command. For example, the letters in blue (four disks) is
the required disk array numbers. Note that the number in red is the local disk of
igwb 1 only.
root@igwb1#format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w21000004cfc33819,0
1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w21000004cfac4524,0
2. c3t0d0 <SUN-StorEdge3310-0325 cyl 198 alt 2 hd 64 sec 32>
/pci@8,700000/pci@2/scsi@4/sd@0,0
3. c3t0d1 <SUN-StorEdge3310-0325 cyl 40958 alt 2 hd 64 sec 32>
/pci@8,700000/pci@2/scsi@4/sd@0,1
4. c4t0d0 <SUN-StorEdge3310-0325 cyl 198 alt 2 hd 64 sec 32>
/pci@8,700000/pci@2/scsi@5/sd@0,0
5. c4t0d1 <SUN-StorEdge3310-0325 cyl 40958 alt 2 hd 64 sec 32>
/pci@8,700000/pci@2/scsi@5/sd@0,1
Caution:
gwbdg01 and igwbdg02 in the script below is set for LUN1 on the StorEdge 3310.
The space of the front disk and the back disk shall be changed based on the actual
capacity of LUN1.
Partition the disk into four partitions, front, back, log-alarm, and igwbdg-stat.
igwbdg-stat is used by the system. Calculate each partition as indicated below: The
total space is the space of LUN1,101,376 MB. Allocate 512 MB to igwbdg-stat,
4,096 MB to log-alarm, and the rest 103,228 MB are fifty-fifty for the front disk and
the back disk. It is recommended that the allocated space for the front disk and the
back disk be set to integral times of 512 to avoid insufficient available space.
1)
/usr/lib/vxvm/bin/vxdisksetup -i c3t0d1
/usr/lib/vxvm/bin/vxdisksetup -i c4t0d1
igwbdg01=c3t0d1
512m
layout=nolog
igwbdg01
4096m
layout=nolog
igwbdg01
48000m
48000m
layout=nolog
layout=nolog
igwbdg02
igwbdg02
2)
layout=nolog
layout=nolog
layout=nolog
root@igwb1 # scsetup
*** Main Menu ***
igwbdg01
igwbdg01
igwbdg02
igwbdg02
2) Resource groups
3) Cluster interconnect
4) Device groups and volumes
5) Private hostnames
6) New nodes
7) Other cluster properties
?) Help with menu options
q) Quit
Option: 4
*** Device Groups Menu ***
Please select from one of the following options:
1) Register a VxVM disk group as a device group
2) Synchronize volume information for a VxVM device group
3) Unregister a VxVM device group
4) Add a node to a VxVM device group
5) Remove a node from a VxVM device group
6) Change key properties of a device group
?) Help
q) Return to the Main Menu
Option: 1
>>> Register a VxVM Disk Group as a Device Group <<<
VERITAS Volume Manager disk groups are always managed by the cluster
as cluster device groups. This option is used to register a VxVM disk
group with the cluster as a cluster device group.
Is it okay to continue (yes/no) <yes>? <Enter>
Name of the VxVM disk group you want to register? igwbdg
Primary ownership of a device group is determined by either
specifying or not specifying a preferred ordering of the nodes that
can own the device group. If an order is specified, this will be the
order in which nodes will attempt to establish ownership. If an order
is not specified, the first node that attempts to access a disk in
the device group becomes the owner.
Do you want to configure a preferred ordering (yes/no) <yes>? <Enter>
Are both nodes attached to all disks in this group (yes/no) <yes>? <Enter>
Which node is the preferred primary for this device group? igwb1
Enable "failback" for this disk device group (yes/no) <no>? no
Is it okay to proceed with the update (yes/no) <yes>? <Enter>
scconf -a -D type=vxvm,name=igwbdg,nodelist=igwb1:igwb2,preferenced=true
Command completed successfully.
Hit ENTER to continue: <Enter>
*** Device Groups Menu ***
Please select from one of the following options:
1) Register a VxVM disk group as a device group
The similar information below is displayed when the above commands are executed.
newfs: construct a new file system /dev/vx/rdsk/igwbdg/ igwbdg-stat : (y/n)?
y
Enter y.
Run the commands below on igwb1 and igwb2 to create the mount points
#cd /var
#mkdir frontsave
#mkdir backsave
Huawei Technologies Proprietary
5-21
#mkdir other
Then, three mount points /var/frontsave, /var/backsave, and /var/other are created on
igwb1 and igwb2.
2)
Modify the /etc/vfstab file on igwb1 and igwb2, and then add the contents below:
no logging
/dev/vx/dsk/igwbdg/back
/dev/vx/rdsk/igwbdg/back
/var/backsave
ufs
no logging
/dev/vx/dsk/igwbdg/log-alarm /dev/vx/rdsk/igwbdg/log-alarm /var/other ufs
2 no logging
Note:
root@igwb1#pnmset
The following information is displayed. The letters in bold should be entered.
In the following, you will be prompted to do configuration for network adapter
failover
Do you want to continue ... [y/n]: y
How many NAFO groups to configure [1]: 1
Enter NAFO group number [0]: 0
Enter space-separated list of adapters in nafo0: qfe1 qfe2
Checking configuration of nafo0:
Testing active adapter qfe1...
Testing adapter qfe2...
NAFO configuration completed
Note:
root@igwb1 # scsetup
Huawei Technologies Proprietary
5-22
/opt
#tar
xvf
sc30_script.tar
To use the FTAM interface, you need to install and configure the FTAM software.
The FTP software is installed during the UNIX setup process. To use the FTP
interface, you need to configure the FTP server.
It is recommended to transfer the bill files between the CG9812 and the billing center
by FTP.
Solstice OSI 9.0, the OSI protocol stack of FTAM, contains the following
packages.
SUNWcorpc
SUNWcosiA
SUNWcosia
SUNWcosib
SUNWcosic
SUNWcosid
SUNWosiax
SUNWosicx
SUNWosidx
SUNWlicsw
SUNWlit
SUNWcosip
2)
Solstice FTAM 9.0, the application layer software of FTAM (containing RFC 1006
protocol stack package), contains the following packages.
SUNWftama
SUNWftamb
SUNWftabx
SUNWrk6
SUNWrk6x
SUNWftamp
SUNWlicsw
SUNWlit
Caution:
z
SUNWrk6 and SUNWrk6x are the packages of the RFC1006 protocol stack,
SUNWrk6 supports the 32-bit OS while SUNWrk6x supports the 64-bit OS. The
RFC1006 protocol stack cannot exist in the same system with the OSI protocol
stack. In other words, if the RFC1006 protocol stack is installed, the OSI protocol
stack cannot be installed on the same computer.
SUNWlicsw is the License monitor process package, and SUNWlit is the License
management toolkit. They are only required to be installed during the FTAM or OSI
setup process. In other words, if the two packages are installed during the OSI
setup process, you do not need to install them during the FTAM setup process.
#hostid
Then, you may get:.
80e63680
II. Decide the underlying communication protocol with the FTAM peer
Before installation, decide the underlying communication protocol with the FTAM peer
end, such as the billing center, you may select the RFC1006 protocol or the OSI
protocol. If the protocol cannot be decided, you probably cannot continue with the
FTAM setup process in a later section.
Note:
Unless otherwise specified, in the later sections, the letters in bold represent the
information you need to enter, and the letters in italic represent the installer
prompts.
<Enter> indicates to press Enter.
Insert the OSI protocol stack CD into the CD-ROM. If the Volume Manager is installed,
the CD-ROM is automatically mounted to the /cdrom/osi_9_0 file system. To check
whether Volume Manager is installed, run the ps -ef | grep vold command. Usually,
Solaris is installed with the Volume Manager, if not, mount it manually with the
commands below:
#mkdir /cdrom/osi_9_0
#mount -rF hsfs /dev/dsk/c0t6d0s0/cdrom/osi_9_0
2)
#cd /cdrom/osi_9_0
#pkgadd -d
The installer prompts the message below:
The following software packages are available:
1 SUNWcorpc
3 SUNWcosia
4 SUNWcosib
5 SUNWcosic
6 SUNWcosid
7 SUNWcosip
8 SUNWlicsw
9 SUNWlit
10 SUNWosiax
12 SUNWosidx
Select the package you want to install (or select all to install all packages).
(default: all) [?,??,q]: <Enter>
Select the packages, or install all the packages by default. Press Enter. Enter y if
prompted during the setup process. For example,
Do you want to continue to install SUNWcorpc?y (Press Enter)
Caution:
Install the OSI Core Stack Configuration Files package of SUNWcosib before other
packages are installed.
After all the packages are installed, the installer gives prompts again.
1 SUNWcorpc
2 SUNWcosiA
3 SUNWcosia
4 SUNWcosib
5 SUNWcosic
6 SUNWcosid
7 SUNWcosip
8 SUNWlicsw
9 SUNWlit
(sparc) 6.1
(sparc) 4.1
10 SUNWosiax
12 SUNWosidx
Select the package you want to execute (or select all to execute all packages).
(default: all) [?,??,q]:q <Enter>
Enter q to exit.
3)
#cd /etc/opt/licenses
#./lit_tty
The license installation interface prompts the message below:
Select Product
[x] Solstice OSI (Stack) 9.0 for SPARC
p=Previous Page
Select Solstice OSI (Stack) 9.0 for SPARC, and then the information below is
displayed:
Servers: [x] 1 [ ] 3 [ ] 5
SERVER NAME
HOSTID
1: igwb2
80c7dff7
(+1) 800-872-4786
Expiration Date:18-dec-2001
Rights to Use:1
Data Checksum: d5
Password: 07BCAA07173858526A52B
Password Checksum: 77
** x=select/deselect
Return=next field **
Enter the Expiration Date, Rights to Use and Password of the License. The installer
prompts the settings are successful, and then displays the information below:
Select Product
[*] Solstice OSI (Stack) 9.0 for SPARC
[ ] Solstice CMIP 9.0 for SPARC
[ ] Solstice FTAM 9.0 for SPARC
p=Previous Page
#pachadd 111344-01
Huawei Technologies Proprietary
6-6
#sync;sync;sync;reboot
6)
Insert the FTAM protocol stack CD into the CD-ROM. If the Volume Manager is
installed, the CD-ROM is automatically mounted to the /cdrom/osi_9_0 file system. To
check whether Volume Manager is installed, run the ps -ef | grep vold command.
Usually, Solaris is installed with the Volume Manager, if not, mount it manually with the
commands below:
#mkdir /cdrom/ftam_9_0
#mount -rF hsfs /dev/dsk/c0t6d0s0/cdrom/ftam_9_0
2)
#cd /cdrom/ftam_9_0
#pkgadd -d .
The installer shows the prompt below.
The following software packages are available:
1 SUNWftabx
2 SUNWftama
3 SUNWftamb
4 SUNWftamp
5 SUNWlicsw
6 SUNWlit
7 SUNWrk6
8 SUNWrk6x
Select the package you want to execute (or select all to execute all packages).
(default: all) [?,??,q]: <Enter>
In this step, if the OSI protocol stack is installed, select packages 16 only and do not
install the RFC1006 packages, including SUNWrk6 and SUNWrk6x. Otherwise, press
Enter to install all the packages. Then, enter y if prompted. For example,
Do you want to continue to install SUNWftabx? Y <Enter>
2 SUNWftama
3 SUNWftamb
4 SUNWftamp
5 SUNWlicsw
6 SUNWlit
7 SUNWrk6
8 SUNWrk6x
Select the package you want to execute (or select all to execute all packages).
(default: all) [?,??,q]:q <Enter>
Enter q to exit.
3)
#cd /etc/opt/licenses
#./lit_tty
The installer shows the following information.
Select Product
p=Previous Page
Select Solstice FTAM 9.0 for SPARC and the message below is displayed:
Solstice FTAM
9.0 for SPARC
Servers: [x] 1 [ ] 3 [ ] 5
SERVER NAME
HOSTID
1: igwb2
80c7dff7
(+1) 800-872-4786
Expiration Date:18-dec-2001
Rights to Use:1
Data Checksum: d5
Password: 07BCAA07173858526A52B
Password Checksum: 77
** x=select/deselect
Return=next field **
Enter the Expiration Date, Rights to Use and Password of the License. The installer
prompts the settings are successful, and then displays the information below:
Select Product
p=Previous Page
#sync;sync;sync;reboot
5)
If the OSI protocol stack is installed, the four processes osinetd, osiftamd, osiftrd -164,
and osiftrd -264 are displayed.
If the RFC1006 protocol stack is installed, the three processes osiftamd, osiftrd -164,
and osiftrd -264 are displayed. Also, check whether the rk6d process is running by
using the ps -ef | grep rk6d command.
NSAP
The NSAP represents the network service access point. The FTAM client (Initiator)
finds the FTAM server (Responder) through the NSAP and set up connection with the
server.
The NSAP consists of five parts. See Figure 6-1
AFI
IDI
SI
PA
NSEL
3)
Partner
The FTAM runs in Initiator/Responder mode. To initiate the connection with the
Responder, the Initiators must know the parameters like NSAP of Responder. Typically,
a Partner is used to represent the FTAM Responder.
#cd /opt/SUNWconn/ftam/bin
#./osiftam
osiftam>rdb add entry1 -n H4980ed0f2d01 -p Cftr -s CPtr -t CFTAM -z 1
z
-n is followed by the NSAP of the FTAM peer entry1, H indicates the NSAP format
is hexadecimal, and 80ed0f2d is the hostid of FTAM peer.
SNPASubnetworkPoint of Attachment
#cd /opt/SUNWconn/osinet/bin
#./osi_ping -n 4980ed0f2d01
If the peer end is accessible, 4980ed0f2d01 is alive is displayed. 4980ed0f2d01 is the
NSAP of the FTAM peer. Make sure the computer where 4980ed0f2d01 is located is
started and FTAM is running normally when you run the command.
3)
#cd /opt/SUNWconn/ftam/bin
#./osiftam
osiftam>open entry1 -n username -p password
Here,
z
After login is successful, you can use the commands like dir, get, and put to test
whether you can interact with the FTAM Partner. For usage of the commands, refer to
6.3.5 Introduction to Solstice FTAM 9.0 Commands.
Note:
Solstice FTAM 9.0 provides you with a graphical tool, ftamtool, to configure the FTAM
parameters. The functions provided by this tool are the same as those of the rdb
command in osiftam. The user usually logs in to a UNIX workstation by Telnet to set
the parameters, and the ftamtool is not always usable, so the ftamtool usage is not
introduced in this section.
#/opt/SUNWconn/ftam/bin/osiftam
osiftam>open entry -n username -p password
In this command, entry is the FTAM Partner name created with the rdb add
command.
2)
osiftam>dir remotedir
Note:
Use the open command to connect with the peer end before this command is
executed.
3)
Note:
Use the open command to connect with the peer end before this command is
executed.
4)
osiftam>rdb list
Note:
5)
Installation Preparations
Upgrading Server
Note:
For parameter configuration, refer to Part III Parameter Configuration and System
Commissioning.
Note:
This section applies to the first installation of the server software. For upgrade
operations, skip this step.
1)
After Solaris is started, you can log in to the two hosts from the COM ports of
other terminals or the TC. For the DC TC, you can telnet (TCP/IP) and then select
7002 port to log in to igwb1 and select 7003 port to log in to igwb2. Note that the
default IP of the TC is set to 192.168.160.10.
2)
After Solaris is started, you can log in as root by FTP or Telnet. You can log in to
the hosts by Telnet. The default IP addresses are set in the /etc/hosts file. For
details, see Figure 7-1.
129.1.1.1 igwb1
129.1.1.2 igwb11
129.1.1.3 igwb12
igwb1 default IP address
129.1.1.2 igwb2
129.2.1.2 igwb21
129.2.1.3 igwb22
igwb2 default IP
129.1.1.3 ha-igwb
129.2.1.3 ha-igwb1
129.3.1.3 ha-igwb2
CG9812 default floating IP
Logical host
127.0.0.1
localhost
129.1.1.1
igwb1
Description
Remarks
IP factory default
maintenance purpose.
for igwb1
IP address
Logical host
Description
Remarks
igwb11
are
mutually
backed
up,
igwb12
129.1.1.2
igwb2
129.2.1.2
Local IP of qfe3
Local IP of qfe0 for
maintenance purpose.
igwb21
IP factory default
are
for igwb2.
mutually
backed
up,
129.1.1.3
igwb22
ha-igwb
Local IP of qfe3.
The floating IP of qfe0. It is
The three IP
addresses are
external floating IP
129.3.1.3
ha-igwb1
ha-igwb2
factory defaults.
Note: The three
floating IPs are the
center
started.
II. Check if the two nodes can be switched over each other
For SUN Cluster3.0, to check whether the primary node and the secondary node can
be switched over each other, follow the steps below.
1)
Log in to igwb1 or igwb2, run scstat | more to view the SC information. You may
get the information below:
Status
------
igwb1
igwb2
cluster member)
Cluster node:
cluster member)
2)
3)
You can only access the disk arrays on igwb1 or igwb2. Make sure the attached
directories for the disk arrays are correct.
Log in to igwb1 or igwb2 through the TC or by Telnet, and run df -k command to view
the output information. Only on one of the two hosts, you can check the volume of the
disk array, including /var/frontsave, /var/backsave, /var/other, and /ha-igwb.
4)
Run the command below on the host where you can view the volume of the disk
array:
Caution:
z
After you modify the hosts files, make sure you also modify the iP addresses set in
the igwb.ini files. Otherwise, the CG9812 server cannot be started. The default
installation path for igwb.ini is /opt/igwb/config/ini.
For
details
on
parameter
configurations,
refer
to
Part
III.
Parameter
Configurations.
You can modify the /etc/hosts on igwb1 and igwb2 to reset the IP addresses.
1)
For the floating IP addresses, modify them based on your actual configurations. If
the floating IP addresses are not in the same network segment, change the
subnet masks for igwb1 and igwb2 in the /etc/netmasks files. Restart the hosts
to enable the settings.
2)
3)
For other IP factory defaults of igwb1 and igwb2, if they are not in conflict with the
IP addresses configured in the current LAN, keep the factory defaults. Record if
an IP address needs to be modified.
4)
qfe1 and qfe2 are mutually backed up, sharing the same floating IP. If qfe1 is
disabled, qfe2 is enabled; if qfe2 is disabled, qfe1 is enabled.
Default
Onsite
adapter
floating IP
floating IP
Function
Remarks
129.1.1.3
10.11.5.30
console
qfe1
qfe3
1)
129.2.1.3
129.3.1.3
202.11.6.20
5.16.17.18
Connect with
SGSN or GGSN
Connect with the
billing center
129.1.1.1
igwb1
(This IP is for maintenance purpose. It can be changed into 10.11.5.1, which is in the sanme
igwb11
(If it is not in conflict with the IPs set in the LAN, do not change it.)
129.1.1.3
igwb12
(If it is not in conflict with the IPs set in the LAN, do not change it.)
129.1.1.2
igwb2
(This IP is for maintenance purpose. It can be changed into 10.11.5.2, which is in the sanme
igwb21
(If it is not in conflict with the IPs set in the LAN, do not change it.)
129.2.1.3
igwb22
(If it is not in conflict with the IPs set in the LAN, do not change it.)
129.1.1.3
ha-igwb
129.2.1.3
ha-igwb1
129.3.1.3
ha-igwb3
Caution:
The last three IP addresses are the external service floating IP addresses set by
default. They are configured with same values on igwb1 and igwb2. The floating IP
addresses will not be enabled untill the SC is started.
129.1.1.2
igwb2
(This IP is for maintenance purpose. It can be changed into 10.11.5.2, which is in the sanme
igwb21
(If it is not in conflict with the IPs set in the LAN, do not change it.)
129.2.1.3
igwb22
(If it is not in conflict with the IPs set in the LAN, do not change it.)
129.1.1.2
igwb1
(This IP is for maintenance purpose. It can be changed into 10.11.5.1, which is in the sanme
igwb11
(If it is not in conflict with the IPs set in the LAN, do not change it.)
129.1.1.3
igwb12
(If it is not in conflict with the IPs set in the LAN, do not change it.)
129.1.1.3
ha-igwb
129.2.1.3
ha-igwb1
129.3.1.3
ha-igwb2
I. Consolidation
Two or more partial bills are created when the GSN process a PDP call. Consolidation
is to consolidate these partial bills into one or more bills.
II. Sort
Sort the bills on the back disk. Two or more bill formats may be included in a bill
package. Currently, bills can be sorted based on the conditions below:
z
For R98 770, this bill format is compatible with R98 760 and can be only sorted by
RecordType.
For R99 3a0, it is compatible with R99 390 and R99 360, and can be sorted by
RecordType and ChargingCharacteristics.
SMT-CDR.
For ChargingCharacteristics, bills can be sorted by Hot billing, Flat rate, Prepaid
igwb_install.tar.gz
Binary
sc30_script.tar
Binary
igwb_install.sh
ASCII
igwb2
igwb_rollback.sh
ASCII
S99CGCfgMonito
ASCII
The
/etc/rc3.d
directory
on
2)
3)
# cd/etc/rc3.d
# chmod 755 S99CGCfgMonitor
4)
Go to the /opt directory and run the command below to begin the setup process.
# cd /opt
# sh ./igwb_install.sh
The following information is displayed. Select the bill protocol version:
1) --- R98 V7.7.0
2) --- R99 V3.a.0
3) --- R4 V4.4.0
Please select the installed product :
5)
#cd /opt/igwb/config/ini
#vi igwb.ini
Note:
For parameter configurations in igwb.ini, refer to Chapter 3. Save the igwb.ini file
after you finish. Close the vi program.
6)
7)
#cd /opt
#tar xvf sc30_script.tar
#cd /opt/hwigwb/util
#ksh ./register.ksh
8)
Run the commands below on igwb1 or igwb2 to start the igwbapp service and
run the related program.
#scswitch -e -j igwbapp
Caution:
Make sure no files or directories are under /var/frontsave, /var/backsave, and
/var/other.
9)
Then, run the commands below on igwb1 and igwb2 to backup the version of the
server application:
# cd /opt
# sh ./igwb_rollback.sh
Then the following information will appear:
0) Exit
1) Backup
version backup
2) Rollback
version rollback
Select 1 to back up the software version. Backup is finished if the information below is
displayed:
Backup now ! Please wait ...
Backup complete !
2)
Run the commands below to back up the product version on igwb1 and igwb2.
# cd /opt
# sh /igwb_rollback.sh
The following information is displayed:
0) Exit
1) Backup
version backup
2) Rollback
version rollback
3)
# cp /opt/igwb/config/ini/igwb.ini /opt/igwb.bak
4)
5)
Run the command below to check the resources are controlled by igwb1 or
igwb2.
Check if the processes are started, including cls_proc, om_proc, knl_proc, and
ap_proc.
7)
If the above processes are started, then the related node controls the resources
and is activated to provide the application services.
8)
Suppose igwb1 controls the resources. On igwb2, perform the operations below:
# cd /opt
# sh ./igwb_install.sh
z
The following information is displayed. Enter c for Chinese, and enter e for English.
Select the language to be installed (Chinese or English), <c/e>:
9)
Run the command below on igwb1 or igwb2 or the client to switch the server from
the primary node to the secondary node
0:01 ./cls_proc
0:02 knl_proc
0:01 ./om_proc
11:30 ./ap_proc 1
Note:
If the installation is successful, go on with the steps below. If not, stop the upgrade
process, and then ask for technical support. If the problem cannot be solved, make
sure to roll back to the last version. For details, refer to7.4.1
General Upgrade.
12) Run the commands below to back up the product version on igwb1 and igwb2.
# cd /opt
# sh ./igwb_rollback.sh
The following information is displayed:
0) Exit
1) Backup
version backup
2) Rollback
version rollback
Caution:
z
For auxiliary upgrade on the client, refer to Part IV. You can continue the upgrade
process only if the auxiliary upgrade is executed successfully.
For upgrade installation, if the version type is changed, you need to rest the
igwb.ini file.
2)
Run the command below on igwb1 or igwb2 to stop the igwbapp service and
related application.
# scswitch
-n -j
igwbapp
Caution:
The following steps 3)7) must be performed on igwb1 and igwb2, and only if these
steps are finished, you can continue the upgrade process.
3)
# cd /opt/igwb/config/ini
# cp igwb.ini /opt/igwb.bak
Caution:
You may need to reset igwb.ini.
4)
5)
# cd
# sh ./ igwb_install.sh
6)
7)
Go to the /opt/igwb/config/ini directory to restore the igwb.ini file you back up.
# cd /opt/igwb/config/ini
# cp /opt/igwb.bak
8)
igwb.ini
Run the command below on igwb1 or igwb2 to start the igwbapp service.
# scswitch
-e
-j
igwbapp
After a few minutes, check if the processes run properly on the upgraded node. Run
the ps -ef | grep _proc command on igwb1 and igwb2. You may see the similar
information below is only displayed on one node.
root 2188 2182 0 09:27:33 ?
0:01 ./cls_proc
0:02 knl_proc
0:01 ./om_proc
11:30 ./ap_proc 1
Run the command below on igwb1 or igwb1 to stop the igwbapp and the related
application:
#scswitch
2)
-n
-j
igwbapp
Run the commands below on igwb1 and igwb2 to roll back the last version:
# cd /opt
# sh ./igwb_rollback.sh
The following information is displayed:
0) Exit
1) Backup
version backup
2) Rollback
version rollback
3)
un the command below on igwb1 or igwb1 to start the igwbapp service and the
related application.
#scswitch
-e
-j
igwbapp
Upgrading Client
Copy the Client setup directory in the installation CD to a directory on the client.
Double-click \Client\SETUP.EXE. The Choose Setup Language dialog box is
displayed. See Figure 8-1.
Select your desired language, and then click OK. Then, the Welcome dialog box
is displayed. See Figure 8-2.
Click Next. The Software License Agreement dialog box is displayed. See
Figure 8-3.
4)
Click Yes to accept all the terms in the agreement. The User Information dialog
box is displayed. See Figure 8-4.
Enter the user name and company, and then click Next. The Select Program
Folder dialog box is displayed. See Figure 8-5.
Click Next. The Choose Destination Location dialog box is displayed. See
Figure 8-6.
7)
Click Next to copy files. Then, the Setup Complete dialog box is displayed. See
Figure 8-8.
2)
3)
Click Yes. The Remove Programs From Your Computer dialog box is
displayed. See Figure 8-9.
5)
6)
7)
Overwrite the uiconfig.ini file in the system directory with the backup one.
Help
iGWB Client
Uninstall System
HUAWEI
HUAWEI CG9812
User Manual
Table of Contents
Table of Contents
Chapter 1 Parameter Configuration............................................................................................. 1-1
1.1 Introduction to Parameter Configuration Console ............................................................. 1-1
1.2 Common Operations.......................................................................................................... 1-6
1.2.1 Logging in to Parameter Configuration Console ..................................................... 1-6
1.2.2 Locking System ....................................................................................................... 1-9
1.2.3 Adding Login ........................................................................................................... 1-9
1.2.4 Logging out Office ................................................................................................. 1-10
1.2.5 Changing Password .............................................................................................. 1-11
1.2.6 Closing Parameter Configuration Console............................................................ 1-11
1.2.7 Viewing igwb.ini Parameter File ............................................................................ 1-12
1.2.8 Adding Parameter Sections .................................................................................. 1-13
1.2.9 Deleting Parameter Sections ................................................................................ 1-15
1.2.10 Adding Parameters ............................................................................................. 1-16
1.2.11 Deleting Parameters ........................................................................................... 1-17
1.2.12 Modifying Parameter Value................................................................................. 1-18
1.2.13 Comparing Parameters of Different Offices ........................................................ 1-19
1.2.14 Saving the Configuration..................................................................................... 1-19
1.2.15 Loading the Parameter Configuration File .......................................................... 1-20
1.2.16 Obtaining the Configuration Information ............................................................. 1-20
1.2.17 Customized Setting ............................................................................................. 1-21
1.3 Configuring the igwb.ini File............................................................................................. 1-22
1.3.1 Common Parameters ............................................................................................ 1-23
1.3.2 Cluster Parameters ............................................................................................... 1-23
1.3.3 Access Point Parameters...................................................................................... 1-24
1.3.4 MML Server Parameters ....................................................................................... 1-26
1.3.5 Log Parameters..................................................................................................... 1-28
1.3.6 Disk and File Control Parameters ......................................................................... 1-28
1.3.7 Network Backup Parameters ................................................................................ 1-29
1.4 CG9812 Dual-System Configuration Instance................................................................. 1-31
1.4.1 Networking Diagram.............................................................................................. 1-31
1.4.2 Configuration of IP Addresses of Network Adapters............................................. 1-32
1.4.3 Content of the igwb.ini Configuration Files ........................................................... 1-34
1.5 Port Usage ....................................................................................................................... 1-37
1.6 Modifying Client Settings ................................................................................................. 1-38
1.7 Network Backup Configuration Instance ......................................................................... 1-39
1.7.1 Network Backup Instance ..................................................................................... 1-39
1.7.2 Simplest Backup Configuration ............................................................................. 1-41
Table of Contents
Chapter 1 Parameter
Configuration
Common Operations
Port Usage
Chapter 1 Parameter
Configuration
6
1.Main window
4.Navigation tree
2.Menu bar
5.Sub-window
3.Toolbar
6.Status bar
I. Main Window
The main window includes all elements, such as the topic, menu bar, navigation tree,
toolbar, and status bar.
Sub-menu
Function
Relogin
Addlogin
LogoutOffice:office
name
1's
Menu
Sub-menu
Function
LogoutOffice:office 2's
name
Lock System
Change Password
Exit
View
info
View
Chapter 1 Parameter
Configuration
parameter
config
configuration
ToolBar
StatusBar
Split Windows
Shrink
Expand
TreeNode
Operation
Office:
office 1's
name
Office:
office 2's
name
Save
the
current
config info
Save
the
current
config info
as
Load config
info
from
local file
Get office1parameter
from the local disk.
Get
the
current info
again
Get
the
delivery
config info
Save
the
current
config info
configuration
Menu
Sub-menu
Chapter 1 Parameter
Configuration
Function
Save
the
current info
as
Load current
config info
from
local
file
Get
the
current info
again
Get
the
delivery
config info
Save All
Help Topics
About ParaCfg
Help
III. Toolbar
The toolbar contains some shortcut icons for the frequently used menus shown in
Table 1-2.
Table 1-2 Shortcut buttons of the parameter configuration console
Shortcut
Function
Relogin
AddLogin
Save All
Logout 1
Logout 2
Shortcut
Chapter 1 Parameter
Configuration
Function
Lock System
Expand
Shrink
Exit
Exit the
console.
Help
parameter
configuration
Figure 1-2 Structure of the navigation tree of the parameter configuration console
V. Sub-windows
Sub-windows include:
Chapter 1 Parameter
Configuration
The sub-window on the upper right corner: the sub-window displayed after you
select the parameter section in the navigation tree and showing the parameter
values under the selected node
The sub-window on the lower right corner: the sub-window displayed after you
select the parameter domain in the navigation tree and showing the details of the
selected parameter
II. Prerequisite
The parameter configuration process cfg_proc.exe of the CG9812 server is started.
The default setup folder of cfg_proc.exe is /opt/igwb.
Chapter 1 Parameter
Configuration
Operation Description
Double-click
in the Bin directory of the CG9812 client, or choose
Start > Programs > iGateway Bill V200 Client > Parameter Configuration
to start the parameter configuration console. The User Login dialog is
displayed.
Enter the correct user name and password. Select the office to be managed.
Click OK to log in to the parameter configuration console.
See Figure 1-1.
Chapter 1 Parameter
Configuration
Description
Example
User name
admin
Password
Office
Shenzhen
IP address
129.2.1.3
Gateway
Gateway IP
129.2.1.15
Description
Example
Office
Beijing
IP
Mandatory.
For
the
parameter
configuration console, the office IP address
can be configured to the actual IP address
of any network adapter on the CG9812
server. When the CG9812 client and the
server are installed on the same server, you
can configure the IP address to 127.0.0.1.
129.2.1.3
Type
iGWB
Chapter 1 Parameter
Configuration
II. Prerequisite
None.
Operation Description
On the main interface, choose System > Lock System, or click
toolbar, or press F2.
in the
If you want to return to the current system, enter the original password in the
Lock System dialog and click OK.
If you want to log in to the system again, click Relogin in the Lock System
dialog and click OK in the popup confirmation dialog.
II. Prerequisite
You log in to the parameter configuration console of office 1. Before logging in to the
parameter configuration console of another office, you must configure another office.
Chapter 1 Parameter
Configuration
Operation Description
On the main interface, choose System > AddLogin, or click
toolbar.
on the
Enter the correct user name and password, select the office to be managed,
and click OK.
Then, you can log in to the parameter configuration console of the other
office.
II. Prerequisite
None.
Operation Description
On the main interface, choose System > LogoutOffice: office name, or
click
and
After confirmation, the system will close all windows of the current office.
Huawei Technologies Proprietary
1-10
Chapter 1 Parameter
Configuration
II. Prerequisite
Log in as admin or the config operator.
Operation Description
On the main interface, choose System > Change Password and the
Password dialog is displayed.
Enter a new password in New Password and Confirm Password. Click OK.
Note:
You can only change the config password of the current office.
II. Prerequisite
None.
Chapter 1 Parameter
Configuration
Operation Description
. A dialog is
II. Prerequisite
None.
Operation Description
No.
Chapter 1 Parameter
Configuration
Operation Description
Select different parameters on the left navigation tree.
Then, the current configuration is displayed on the right view window in real
time.
The upper right pane is open when you select a corresponding parameter
section on the left navigation tree. This pane displays the value information
for the parameter under the selected node on the tree.
The lower-right pane is open when you select a parameter domain on the left
navigation tree. This lower pane displays the details of the selected current
parameter for your reference.
Note:
For the details of the igwb.ini parameter configurtion, see section 1.3 Configuring the
igwb.ini File. For more detailed parameter information, see Parameter Configuration
Console > Parameter Configuration Management > Browse igwb.ini Parameter of
the help system.
Chapter 1 Parameter
Configuration
II. Prerequisite
Log in as admin or the config operator.
Operation Description
On the main interface, right-click the igwb.ini node or a node in the second
layer. Select Add Section.
Select the parameter section you want to add, and click OK. After
confirmation, the added parameter section appears in the navigation tree as
a node.
For example, if the default configuration file igwb.ini has the parameter
section [BackupTask1], you need to add the parameter section
[BackupTask2] to configure two backup tasks
No.
Chapter 1 Parameter
Configuration
Operation Description
Choose Operation > Office: office name > Save the Current Config Info.
Note:
After modifying igwb.ini, you can restart the server by choosing Operation/Reset
iGWB on the CDR console or using the command # cd /opt/igwb and # ./killigwb.
You can validate the parameter setting by restarting the server process.
Description
AccessPoint
AgentAlarm
Alarm
BackupTask
CdrStat
Channel-
DiskFile
Kernel
Kernel parameter
License
Link
Log
OM
O&M parameter
Perf
Resource
Chapter 1 Parameter
Configuration
II. Prerequisite
Log in as admin or the config operator.
Operation Description
On the main interface, right-click the igwb.ini node or a node in second layer.
Select Delete Section. In the popup dialog, click Yes to confirm the deletion.
2
3
Choose Operation > Office: office name > Save the Current Config Info.
The current parameter configuration information is submitted to the server.
Restart the CG9812 server to validate the deletion.
II. Prerequisite
Log in as admin or the config operator.
Operation Description
On the main interface, right-click the node in second layer or in third layer.
Select Add Parameter.
No.
Chapter 1 Parameter
Configuration
Operation Description
The Add Parameter dialog is displayed.
Select the parameter you want to add, and click OK. After confirmation, the
added parameter appears in the navigation tree as a node.
For example, add the parameter AlarmBoxUsingMode under the parameter
section [Backup Task2].
3
4
Choose Operation > Office: office name > Save the Current Config Info.
The current parameter configuration is submitted to the server.
Restart the CG9812 server to validate the addition.
II. Prerequisite
Log in as admin or the config operator.
Operation Description
On the main interface, right-click the node in second layer or in third layer.
Select Delete Parameter. In the popup dialog, click Yes to confirm the
deletion. The selected parameter node is deleted.
No.
2
3
Chapter 1 Parameter
Configuration
Operation Description
Choose Operation > Office: office name > Save the Current Config Info.
The current parameter configuration is submitted to the server.
Restart the CG9812 server to validate the deletion.
II. Prerequisite
Log in as admin or the config operator.
Operation Description
On the main interface, select the parameter node in the third layer you want
to modify. The upper right sub-window shows the parameter values under
your selected node.
Double-click the parameter value, and you can select or edit the parameter
values of your login office, such as the ServerNo under Common. The right
lower sub-window displays the detailed description of this parameter.
Choose Operation > Office: office name > Save the Current Config Info.
The current parameter configuration is submitted to the server.
No.
4
Chapter 1 Parameter
Configuration
Operation Description
Restart the CG9812 server to validate the change.
Note:
The parameters in igwb.ini are very important and cannot be changed at will.
II. Prerequisite
Log in as admin or the config operator.
Operation Description
Log in to the parameter configuration console of the first office. Then, log in to
office 1.
See section 1.2.1 Logging in to Parameter Configuration Console.
Log in to the parameter configuration console of the second office. Then, log
in to office 2.
See section 1.2.3 Adding Login.
Chapter 1 Parameter
Configuration
II. Prerequisite
Log in as admin or the config operator.
Operation Description
On the main interface, choose Operation > Office: office name > Save The
Current Config Info As.
In the popup dialog, select the path and file name, and click Save.
II. Prerequisite
None.
Operation Description
On the main interface, choose Operation > Office: office name > Load
Config Info From Local File.
Chapter 1 Parameter
Configuration
II. Prerequisite
None.
No.
Operation Description
On the main interface, choose Operation > Office: office name > Get The
Current Config Info Again.
2)
No.
Operation Description
On the main interface, choose Operation > Office: office name > Get The
Last Config Info.
Obtain the configuration information submitted last time from the server.
3)
No.
Operation Description
On the main interface, choose Operation > Office: office name > Get The
Base Config Info.
After confirmation, obtain the delivery configuration file igwb.ini from the
server.
II. Prerequisite
None.
Chapter 1 Parameter
Configuration
Operation Description
On the parameter configuration console, select View, and then
z
z
1
z
Note:
You can save common settings for next time use. In this case, you need not reset after
re-login.
For the optional configuration item, you can use the default value without
modifications in general cases.
The mandatory configuration items must exist in the configuration file or must be
modified based on actual conditions.
Chapter 1 Parameter
Configuration
Configuration description
Recommende
d value
APCount
ServerNO
ClusterMode
Caution:
For the GSN, If multiple SGSNs or GGSNs access in the same process, APCount is 1
rather than the actual number of GSNs.This parameter usually uses the default value 1.
Chapter 1 Parameter
Configuration
Recommended
value
Configuration description
Mandatory. Version number of Sun
Cluster.
3.0
Note:
The CG9812 HA system server consists two minicomputers of SUN Netra and the SCs.
The related parameters are already configured before delivery and should not be
modified.
Configuration description
Recommended
value
APType
APName
Release
Configuration
item
Configuration description
Chapter 1 Parameter
Configuration
Recommended
value
Use the default
installation value
usually.
FmtDll
SaveSecond
LocalIpToEx
LocalPortToEx
3386
BackSavePatc
hName
FinalFileMaxSi
ze
1024
OrigFileMaxSiz
e
3072
Configure based
on
actual
conditions.
1
The
default
value
is
129.2.1.3.
Configure based
on
actual
conditions.
Chapter 1 Parameter
Configuration
Configuration
item
Configuration description
Recommended
value
FinalFileMaxTi
me
1800
MustMerge
RedirAddress
0.0.0.0
Note:
The IP address of LocalIpToEx should be the same as the IP address of ha-igwb1 in the
/etc/hosts file of igwb1 and igwb2. This IP address is the float IP address used to
connect with GSN.
For the configuration of the /etc/hosts file, see Part II System Installation.
Chapter 1 Parameter
Configuration
Configuration description
Recommended value
LocalIpToMMLClient
MaxConnectUserNu
mber
10
PersistUser
/var/other/mml
LocalPortToCM
6000
LocalPortToAR
6001
LocalPortToRD
6007
LocalPortToSynConf
6099
MaxUserNumber
Optional.
The
maximum
number of users allowed by
CG9812, ranging from 1 to 30.
If the setting is beyond the
range, select the maximum
value.
30
MaxConnectUserNu
mber
10
Chapter 1 Parameter
Configuration
Note:
The IP address of LocalIpToMMLClient should be the same as the IP address of
ha-igwb in the /etc/hosts file of igwb1 and igwb2. This IP address is the float IP
address used to connect the NMS and the maintenance console.
For the configuration of the /etc/hosts file, refer to Part II System Installation.
Recommended
value
Configuration description
LogRootDir
/var/other/log
ArchiveDir
/var/other/log_archive
ArchiveTime
Configure based on
actual conditions.
LogSaveDays
30
Configuration description
MinDiskAlarmRoom
Recomm
ended
value
5
Chapter 1 Parameter
Configuration
Recomm
ended
value
Configuration item
Configuration description
MinDiskHandoverR
oom
500
FrontSaveRootDir
/var/front
save
BackSaveRootDir
/var/back
save
FetchFileTimeOut
UserName
Configuration description
Recommend
ed value
Configure
based on
actual
conditions.
Configuration
item
Chapter 1 Parameter
Configuration
Configuration description
Recommend
ed value
DestHostIP
Configure
based on
actual
conditions.
LocalIP
Billing centers
IP address is
recommended
BeforeEncode
Password
BackupTaskCo
unt
It depends.
SourceDir
/var/frontsave
DestDir
/frontsave/bac
kup
ReConnectInter
val
300
SearchFilesInte
rval
300
DelAfterBak
DestFilesSave
Days
BakeupLastFile
File
Configuration
item
FileSaveDays
Chapter 1 Parameter
Configuration
Configuration description
Optional. Indicating the save days of source
files (0-Default; Maximum days=180). 0 means
Not delete.
Recommend
ed value
0
Note:
z
When the network backup mode is adopted, the password is set in plain text for the
first time, and it will be automatically encrypted into password after the program
runs.
If SUN Netra 240 minicomputer is employed, the networking in cluster mode of the
CG9812 is shown in Figure 1-3.
Chapter 1 Parameter
Configuration
bge2
bge0
igwb2
LAN Switch-1
To Office LAN
To BC
bge1
bge3
bge2
bge0
GSN
LAN Switch-0
igwb1
bge1
To Office LAN
To BC
bge3
qfe0
igwb2
LAN Switch-1
To Office LAN
To BC
qfe1
qfe3
qfe2
qfe0
GSN
LAN Switch-0
igwb1
qfe1
To Office LAN
To BC
qfe3
Chapter 1 Parameter
Configuration
Primary
node
Secondary
node
2)
Name
igwb1
igwb2
Network
identific
ation
Peer
device
Fixed IP
Default
virtual
IP
Actual
virtual IP
bge0
For NMS
and LMT
connection
129.1.1.1
129.1.1.
3
10.11.5.30
bge1/
bge2
For GSN
connection
129.2.1.1
129.2.1.
3
202.11.6.2
0
bge3
For billing
center
connection
129.3.1.1
129.3.1.
3
5.16.17.18
bge0
For NMS
and LMT
connection
129.1.1.2
129.1.1.
3
10.11.5.30
bge1/
bge2
For GSN
connection
129.2.1.2
129.2.1.
3
202.11.6.2
0
bge3
For billing
center
connection
129.3.1.2
129.3.1.
3
5.16.17.18
Primary
node
Secondary
node
Name
igwb1
igwb2
Network
identific
ation
Peer
device
Fixed IP
Default
virtual
IP
Actual
virtual IP
qfe0
For NMS
and LMT
connection.
129.1.1.
1
129.1.1.
3
10.11.5.3
0
qfe1/
qfe2
For GSN
connection.
129.2.1.
1
129.2.1.
3
202.11.6.
20
qfe3
For billing
center
connection.
129.3.1.
1
129.3.1.
3
5.16.17.1
8
qfe0
For NMS
and LMT
connection.
129.1.1.
2
129.1.1.
3
10.11.5.3
0
qfe1/
qfe2
For GSN
connection.
129.2.1.
2
129.2.1.
3
202.11.6.
20
qfe3
For billing
center
connection.
129.3.1.
2
129.3.1.
3
5.16.17.1
8
Chapter 1 Parameter
Configuration
Note:
z
The network adapter naming mode of the services provided by Netra 240 and Netra
20 are different. The naming mode of Netra 240 is bge0 bge3. The naming mode
of Netra 20 is qfe0 qfe3.
The float IP address providing services by the CG9812 need to be modified based
on actual conditions. The IP address listed here is just an example.
/*Accesspoint count*/
ServerNo = 0
ClusterMode = 1
/*Flag
of
cluster
or
not,
1-cluster
mode,
0-single-host mode */
[Cluster]
CLUSTVER=3.0
[AccessPoint1]
APType = 4
release is R4*/
APName = R4
Release = R4
LocalIpToEx = 129.2.1.3
virtual IP 202.11.6.20*/
LocalPortToEx = 3386
MustMerge = 1
SaveSecond = 1
/*Save two shares for each final CDR file (0: Not
need; 1: Need)*/
RedirAddress = 0.0.0.0
[MML]
LocalIpToMMLClient =129.1.1.3
[NetBackup]
Chapter 1 Parameter
Configuration
DestHostIP=5.16.17.20
condition*/
LocalIP=129.3.1.3
virtual IP 5.16.17.18*/
Password=*****
BeforeEncode=1
condition */
[BackupTask1]
SourceDir=/var/backsave/R4
DestDir=/home/huawei /R4
/* Destination directory*/
Note:
After the server software is installed, the parameters in bold in the configuration
instance must be modified:
z
For LocalIpToEx under [AccessPoint1], its float IP address connecting with GSN
should be set based on actual conditions, and should be the same as the IP address
of ha-igwb1 in the /etc/hosts file.
For LocalIpToMMLClient under [MML], its float IP address connecting with NMS
should be set based on actual conditions, and should be the same as the IP address
of ha-igwb in the /etc/hosts file.
/*Accesspoint count*/
ServerNo = 1
ClusterMode = 1
/*Flag
of
cluster
or
not,
1-cluster
mode,
0-single-host mode */
[Cluster]
CLUSTVER=3.0
[AccessPoint1]
Chapter 1 Parameter
Configuration
release is R4*/
APName = R4
Release = R4
LocalIpToEx = 129.2.1.3
virtual IP 202.11.6.20*/
LocalPortToEx = 3386
MustMerge = 1
SaveSecond = 1
/*Save two shares for each final CDR file (0: Not
need; 1: Need)*/
RedirAddress = 0.0.0.0
[MML]
LocalIpToMMLClient =129.1.1.3
[NetBackup]
UserName=administrator
DestHostIP=5.16.17.20
condition*/
LocalIP=129.3.1.3
IP 5.16.17.18*/
Password=*****
BeforeEncode=1
condition*/
[BackupTask1]
SourceDir=/var/backsave/R4
DestDir=/home/huawei /R4
/*Destination directory*/
Chapter 1 Parameter
Configuration
Note:
After the server software is installed, the parameters in bold in the configuration
instance must be modified:
z
For LocalIpToEx under [AccessPoint1], set the float IP address connecting with
GSN based on actual conditions, and ensure that it is the same as the IP address of
ha-igwb1 in the /etc/hosts file.
For LocalIpToMMLClient under [MML], set the float IP address connecting with
NMS based on actual conditions, and ensure that it is the same as the IP address of
ha-igwb in the /etc/hosts file.
Type
Function
21
TCP
20
TCP
23
TCP
telnet server
137
UDP
138
UDP
161
UDP
SNMP
162
UDP
SNMP
Chapter 1 Parameter
Configuration
Type
Parameters modified in
the configuration file
Function
6000
TCP
[MML] LocalPortToCM
6001
TCP
[MML] LocalPortToAR
6002
TCP
[MML] LocalPortToPF
6007
TCP
[MML] LocalPortToRD
6099
TCP
The
synchronization
configuration port open to the
NMS
[MML] LocalPortToSynConf
6100
TCP
[MML]
LocalPortToAlarmBox
3386
UDP
[AccessPoint%d]
LocalPortToEx
LocalPortToExBak
9999
TCP
the
[Common] LocalPortToMsg
Chapter 1 Parameter
Configuration
Note:
MAINTAINPORT is the configuration item of the maintenance port. DEBUGPORT is
that of the corresponding port of the server. For server configuration, refer to the
value of LocalPortToCM under [MML] in the igwb.ini configuration file.
Backup precautions
No.
Operation Steps
Click New FTP Site Guide to configure the parameters. The IP address is
configured with the local IP address. TCP port is 21. Then, set the FTP main
directory to read & write.
After the FTP is created, configure other parameters in the Open Site
Property window. Disable anonymous connection. Add an FTP user
account. Select UNIX for catalog list style. Use the default values for other
options.
After the configuration is complete, log in to the FTP site. Check if the site
can be logged in, written, accessed, and operated by the added user
account.
If login is successful, the site is writable, and files and catalog can be
accessed, then the FTP server is set up successfully.
Huawei Technologies Proprietary
1-39
2)
Chapter 1 Parameter
Configuration
Modify the igwb.ini file by using the vi editor and configure the network backup
parameters.
No.
Operation Steps
Use the following command to log in to the active and standby nodes of the
CG9812, for example, igwb1.
# telnet igwb1
Enter the correct user name and password to log in to igwb1, and the
following prompt is displayed: root@igwb1#.
Go to the directory /opt/igwb/config/ini, and edit the igwb.ini file by using
the vi editor.
root@igwb1#cd /opt/igwb/config/ini
root@igwb1#vi igwb.ini
UserName= administrator
DestHostIP=10.70.141.160
; Backup destination IP
LocalIP=10.70.141.170
; Backup local IP
Password=******
sensitive)
BeforeEncode=1
; 1 is set for the first time. The CG9812
encodes the password after started. Then, the value becomes 0. If the
password is changed, set it to 1 and reset the CG9812.
BackupTaskCount=1
[BackupTask1]
SourceDir=/var/backsave/R4
DestDir=/home/huawei /R4
(Optional) If there are two or more backup tasks, you can add the parameter
section [BackUpTaskN] (N for sequence number of the backup task) to the
parameter configuration console. Then add and configure SourceDir and
DestDir based on the actual conditions.
Chapter 1 Parameter
Configuration
Note:
When the billing center works in UNIX, the users opened to the CG9812 are not the
root users in general cases, so directories must be configured with full names.
For the usage of vi commands, refer to common vi commands in Appendix A
3)
No.
Operation steps
Run the CG9812 server process, and then log in to the CDR console.
Double-click Frame.exe in the Bin directory on the CG9812 client or click
Start/Programs/iGateway Bill V200 Client/iGWB Client to open the CDR
console interface.
On the main interface of the CDR console, choose Operation > Reset
iGWB.
In the popup dialog, click Yes to reset the CG9812 server process.
4)
Open the debugging console to view the network backup process of a single task.
No.
Operation Steps
Make sure the debugging process runs normally on the CG9812 Client
before login. Double-click debugws.exe in the installation directory Bin of
the CG9812 or choose Operation > Debug on the main interface of the
CG9812 Client to open the Login dialog.
Enter the correct user name and password. Select the office to be managed.
Click OK to log in to the debugging console.
5)
Chapter 1 Parameter
Configuration
DestHostIP=10.70.141.160
LocalIP=10.70.141.170
Password=
BeforeEncode=1
[BackupTask1]
SourceDir=/var/backsave/R4
DestDir=/home/huawei/R4
[BackupTask1]
SourceDir=/var/backsave/R4
DestDir=/home/huawei/R4
[BackupTask2]
SourceDir=/var/backsave/Second/R4
DestDir=/home/huawei/R4
1.7.4 Configuring Two Backup Tasks with Different User Names and
Passwords
I. Task Description
Configure two backup tasks with different user names and passwords.
Huawei Technologies Proprietary
1-42
Chapter 1 Parameter
Configuration
[BackupTask1]
UserName=root
DestHostIP=10.70.141.180
LocalIP=10.70.141.170
Password= BeforeEncode=1
the password after it is started. Then, the value becomes 0. If the password
is changed, set it to 1 and reset the CG9812.
SourceDir=/var/backsave/R4
DestDir=/home/huawei/R4
[BackupTask2]
UserName=administrator
DestHostIP=10.70.141.160
LocalIP=10.70.141.170
Password=
BeforeEncode=1
Note:
Both 1.7.2 Simplest Backup Configuration and 1.7.4 Configuring Two Backup Tasks
with Different User Names and Passwords belong to the configuration of different
auto-backup modes.
Chapter 1 Parameter
Configuration
SearchFilesInterval =300; The search interval (in seconds) when the backup module
backs up the files
ReConnectInterval = 300; The time interval (by second) when the FTP Server is
reconnected
is reconnected
[BackupTask1]
SourceDir=/var/backsave/R4
DestDir=/home/huawei/R4
Chapter 1 Parameter
Configuration
[BackupTask1]
backup_list_time=HH:MM:SS,HH:MM:SS
; Hour:minute:second
SourceDir=/var/backsave/R4
DestDir=/home/huawei/R4
the password after it is started. Then, the value becomes 0. if the password
is changed, set it to 1 and reset the CG9812.
BackupTaskCount=1 ; Total number of backup tasks
[BackupTask1]
backup_begin_time=00:00
backup_end_time = 23:59
SourceDir=/var/backsave/R4
DestDir=/home/huawei/R4
Chapter 1 Parameter
Configuration
[BackupTask1]
hour:minute:second.
SourceDir=/var/backsave/R4
DestDir=/home/huawei/R4
Chapter 1 Parameter
Configuration
[BackupTask1]
SourceDir=/var/backsave/R4
DestDir=/home/huawei/R4
BackupLastFile = 0
[BackupTask1]
SourceDir=/var/backsave/R4
DestDir=/home/huawei/R4
Chapter 1 Parameter
Configuration
1-yes)
1.7.11 Configuring the Deletion of the Second Bill Copy without Date
Directory after Backup
I. Task Description
Delete the files in the second directory of the back save disk (UNIX /var/backsave).
The configuration is controlled by the following parameter:
FileSaveDays = 0 ;#ave days for the source file (0-Default; Max.=180). 0 means Not
delete.
Caution:
z
This parameter is only applicable to the second bill copy without date directories. In
addition, only the files in the directory are deleted, but the directory is not deleted.
This parameter can be used together with other parameters. In addition, SourceDir
must be in the directory of Second.
[BackupTask1]
SourceDir=/var/backsave/R4
DestDir=/home/huawei/R4
Chapter 1 Parameter
Configuration
1.7.12 Configuring the Save Days for Files under the Destination Path
I. Task Description
Delete the files in the specific directory of DestDir. The configuration is controlled by
the following parameter:
DestFilesSaveDays = 0 ; save days for the files under the destination path. If it is
configured with more than 365 days, the value is 365; if it is configured with 0, then the
files should not be deleted.
This parameter can be used together with other parameters.
[BackupTask1]
SourceDir=/var/backsave/R4
DestDir=/home/huawei/R4
DestFilesSaveDays = 0
If it is configured with more than 365 days, the value is 365; if it is configured
with 0, then the files should not be deleted.
Chapter 1 Parameter
Configuration
[BackupTask1]
SourceDir=/var/backsave/R4
DestDir=/home/huawei/R4
StatusBackupSrcDir= /var/other/StatusFile/Status
[BackupTask1]
SourceDir=/var/backsave/R4
DestDir=/home/huawei/R4
Chapter 1 Parameter
Configuration
3)
The SC system starts the cluster process (cls_proc) by using the ha scripts.
4)
5)
The Kernel process sequentially starts the operation and maintenance process
(om_proc) and access point process (ap_proc).
Note:
Execute steps 3) - 5) sequentially. Any failure in these steps may lead to the CG9812
startup failure and active/standby switchover.
2)
The cluster process sends the exit command to the Kernel process (knl_proc).
3)
The Kernel process receives the exit command and sends the exit command to
operation and maintenance process (om_proc) and access point process
(ap_proc).
4)
The operation and maintenance process (om_proc) and access point process
(ap_proc) exit after receiving the command.
5)
6)
The CG9812 server uses the dual-system. On the UNIX platform, the active node
(active server) runs a cls_proc, a knl_proc, an om_proc, and one or multiple ap_proc
processes according to the access point number. These processes cannot run on the
standby node (standby server). You can use the command ps -ef | grep _proc on two
nodes respectively to view the running status of processes.
Note:
For the directory structure and system manitenance of the CG9812, refer to Part V
System Maintenance".
I. Operation Procedure
To start the bill console, do as follows:
1)
Ensure that processes of the active CG9812 server are already started. Log in to
the active CG9812 server and use the command ps -ef | grep _proc to see
whether the cls_proc, knl_proc, om_proc, and ap_proc processes are started.
2)
On the CG9812 client, choose Start > Programs > iGateway Bill V200 Client >
iGWB Client, or double-click Frame.exe in the Bin directory under the installation
directory of the CG9812 Client. Then the User Login dialog is displayed, as
shown in Figure 2-1.
Operation
Example
User name
admin
User Pwd
Office
Shenzhen
Office IP
129.3.1.1,
modify it
based on
actual
condition.
Use Gateway
129.1.1.8,
modify it
based on
actual
condition.
Gateway IP
Note:
z
The default user name and password of the CG9812 client are admin and null
respectively. You need to change the password of the administrator immediately.
2)
Operation
Example
Office
Beijing
IP
10.70.141.11
Type
iGWB
Chapter 3 System
Commissioning
OSS
MML
FTP/FTAM
M2000
BC
Core Network
Ga
GSN(GGSN/SGSN)
CG9812
Chapter 3 System
Commissioning
The network between the CG9812 and GSN are connected normally.
The bill protocols of the sender (GSN) and the receiver (the CG9812) are the
same. For example, the bill protocols are all in the form of R98, or R99, or R4.
The Ga interface settings are the same and the IP address and port in GSN for
sending bills are the same as those in the CG9812.
The root user logs in to the CG9812 server with disk array (active CG9812
server).
2)
3)
Set a password for the bs user: #passwd bs. Enter the password and confirm it.
4)
Check the settings and log in to the CG9812 server as the bs user to validate
whether CDRs can be taken or deleted successfully.
#cd /etc/rc3.d
2)
#vi
3)
4)
5)
S99CGENV
/*S is in capital*/
local IP address/subnet mask
S99CGENV
Ensure that the network between the CG9812 and NMS are normal.
Chapter 3 System
Commissioning
Note:
The maintenance port of the CG9812 does not need to be reset without special
requirpements or changes.
When you need to reset it, see 1.6 Modifying Client Settings.
On the CG9812 client, log in to the CG9812 with an incorrect password for three
times sequentially.
2)
3)
HUAWEI
HUAWEI CG9812
User Manual
Table of Contents
Table of Contents
Chapter 1 Quick Start.................................................................................................................... 1-1
1.1 Introduction to the Chapter ................................................................................................ 1-1
1.2 Introduction to CG9812 Client ........................................................................................... 1-1
1.3 GUI of the CDR Console ................................................................................................... 1-2
1.4 GUI of the Debugging Console.......................................................................................... 1-6
Chapter 2 Common Operations ................................................................................................... 2-1
2.1 Introduction to the Chapter ................................................................................................ 2-1
2.2 Logging in to the CDR Console ......................................................................................... 2-1
2.3 Locking CDR Console ....................................................................................................... 2-3
2.4 Logging out of the CDR Console ....................................................................................... 2-3
2.5 Closing the CDR Console.................................................................................................. 2-4
2.6 Customizing the Layout ..................................................................................................... 2-4
2.7 Managing Operators .......................................................................................................... 2-6
2.7.1 Adding an Operator................................................................................................. 2-6
2.7.2 Deleting an Operator............................................................................................... 2-8
2.7.3 Modifying an Operator............................................................................................. 2-8
2.8 Managing Offices ............................................................................................................. 2-10
2.8.1 Adding an Office.................................................................................................... 2-10
2.8.2 Deleting an Office.................................................................................................. 2-11
2.8.3 Modifying an Office ............................................................................................... 2-12
2.9 Customizing the System .................................................................................................. 2-13
2.9.1 Customizing Timeout Setting ................................................................................ 2-13
2.9.2 Customizing Lock Time......................................................................................... 2-14
2.10 Managing CDRs............................................................................................................. 2-15
2.10.1 Browsing CDRs by Type ..................................................................................... 2-15
2.10.2 Browsing CDRs by Format.................................................................................. 2-18
2.10.3 Browsing CDRs by Multiple Conditions .............................................................. 2-20
2.10.4 Saving CDR Information ..................................................................................... 2-22
2.10.5 Printing a CDR .................................................................................................... 2-22
2.11 Managing Performance ................................................................................................. 2-23
2.11.1 Querying System Performance Status................................................................ 2-25
2.11.2 Setting State Query Properties ........................................................................... 2-27
2.11.3 Clearing State Information .................................................................................. 2-28
2.12 Managing Logs .............................................................................................................. 2-29
2.12.1 Browsing Logs..................................................................................................... 2-29
2.12.2 Saving Logs......................................................................................................... 2-32
2.12.3 Clearing Logs ...................................................................................................... 2-34
Huawei Technologies Proprietary
i
Table of Contents
CDR console
System debugging
console
Parameter
configuration
console
Function
Description
Through the
parameter
configuration console,
you can remotely
modify and maintain
the configuration file
igwb.ini of the server
and compare the
system parameters of
different offices to help
users in O&M.
No.
Entry 1
Entry 2
CDR console
System debugging
console
Parameter
configuration
console
Double-click
Frame.exe in the Bin
directory under the
installation directory
of the CG9812 Client.
Double-click
debugws.exe in the
Bin directory under
the installation
directory of the
CG9812 Client.
Double-click
ParaCfg.exe in the
Bin directory under
the installation
directory of the iGWB
Client.
On the main
interface of the CDR
console, select
Services/Debug, or
Select
Start/Programs/iGat
eway Bill V200
Client/Parameter
Configuration
Console.
Select
Start/Programs/iGat
eway Bill V200
Client/CDR
Console.
click the
shortcut
button in the toolbar.
Note:
This chapter covers the basic operations of the CDR console and the system
debugging console only. Part III introduces the operation of the parameter configuation
console.
2
3
4
5
1. Main window
4. Navigator tree
2. Menu bar
5. Sub-window
3. Toolbar
6. Status bar
I. Main window
The main window contains all elements of the CDR console interface, including the title,
menu bar, toolbar, navigator tree, and status bar.
Sub-menu
Function
Relogin
Logout
Lock System
Menu
View
Operation
Security
Window
Help
Sub-menu
Function
Office Management
System Customization
Exit
Navigator Tree
Toolbar
Status Bar
Refresh
Debug
State Query
Switch
Upgrade
Operator
Management
Log Browse
Cascade
Tile
Arrange Icons
Close All
Help Topics
About iGWB
III. Toolbar
The toolbar provides shortcuts to the basic operations. On the toolbar, the shortcut
icons vary with the current mode. Table 1-3 lists the shortcut icons on the toolbar.
Table 1-3 Toolbar on the CDR console GUI
Shortcut
Related menu
option
Relogin
Function
To log out and log in as another user.
Shortcut
Related menu
option
Function
Office Management
Logout
Lock System
Navigator Tree
Debug
Help Topics
Under Original Bill, the CDRs are displayed by date. The corresponding CDR file
is *.bil.
2)
Under Final Bill, the bill types (also called channel) supported by the system are
displayed. Under each channel node, the final bills are displayed by date. The
corresponding CDR file is *.dat. The channels are determined by the format
library.
Name
Original Bill
Date
Final Bill
Channel
Date
1#Access
Point
2#Access
Point
For the SGSN, the channels are S-CDR, M-CDR, S-SMO-CDR, S-SMT-CD,
LCS-MO-CDR, LCS-MT-CDR and LCS-NI-CDR. The bill formats include:
z
For the GGSN, the channel is G-CDR. The bill format is:
G-CDR: The PDP context bills.
Note:
z
The final bill channel is determined by the distribution type selected by the user
while installing the server.
V. Sub-window
The sub-window is displayed after you select a menu or click a shortcut icon. It
implements the specific function.
2
3
1. Main window
4. Sub-window
2. Menu bar
5. Status bar
3. Toolbar
-
I. Main window
Main window includes all the elements on the debugging console GUI: title, menu bar,
toolbar, and status bar.
System
View
Sub-menu
Function
Relogin
Exit
Toolbar
Menu
Sub-menu
Status bar
Debug
Mask
Level
Protocol
Function
List Mask
Level
Set Mask
Level
Browse Protocol
Message
Browse Workflow
Message
Cascade
Tile Horizontally
Tile Vertically
Arrange Icons
Minimize All
Clear
Clear All
Close
Close All
About iGWB
Workflow
Window
Help
III. Toolbar
The toolbar provides shortcuts to the frequently performed operations. Table 1-5 lists
the shortcut icons on the toolbar.
Function
Relogin
Browse Workflow
Message
Exit
IV. Sub-window
The sub-window is displayed after you select a menu or click a shortcut icon, to
implement the specific function.
V. Status bar
The status bar shows the IP address and network connection status of the CG9812
server connected with the client.
II. Prerequisites
The CG9812 server process is running, run #ps -ef|grep _proc on active node,
Operation description
Double-click Frame.exe in the Bin directory under the installation directory of
the CG9812 Client, or select Start\Programs\iGateway Bill V200
Client\iGWB Client. Then the Login dialog box is displayed.
No.
Operation description
In the Login dialog box, enter the correct user name, password, and set the
office to be managed. Then click OK. If the login is successful, the main
interface of the CDR console is displayed.
Description
Example
User name
admin
Password
Office name
Shenzhen
Office IP
address
10.70.141.111
Use
Gateway
Gateway IP
10.70.141.133
Note:
z
The default user name and password of the CG9812 client are admin and null
respectively. You need to change the password of the administrator immediately.
II. Prerequisites
None.
Operation description
On the main interface of the CDR console, select System/Lock System or
click
box.
on the toolbar (or press F12) to display the Lock System dialog
To return to the current system, enter your password in the Lock System
dialog box, and then click OK.
To re-log in to the system, click Relogin in the Lock System dialog box.
In the dialog box that pops up, click OK to confirm your operation.
II. Prerequisites
None.
Operation description
On the main interface of the CDR console, select System/Log Out or click
on the toolbar. Then the system asks you to confirm.
After you confirm your operation, the system closes all windows of the CDR
console.
Operation description
On the main interface of the CDR console, select System/Exit. A dialog box
is displayed, prompting you to confirm your operation.
II. Prerequisites
None.
Operation description
On the CDR console, select View. Then select
Navigator Tree (or press F2) to show or hide the navigator tree.
No.
Operation description
On the CDR Console, select Window. Then select
z
Note:
Once you customize the layout of the CDR console, the layout will be saved and you
need not customize it again.
Task
description
Operator
Managemen
t Interface
Adding an Operator
Deleting an Operator
Modifying an Operator
After the Client software is installed, the system automatically creates the administrator
named admin. It is the only administrator in the system and cannot be deleted. Other
operators are added manually.
II. Prerequisites
You have logged in as the administrator or an operator authorized to create new
operators.
Operation description
Enter values in all fields, and then click OK. View the Operator Management
window, and you can find that the new operator has been added.
Description
Example
Name
Zhangshan
Description
Operator
Authority
Normal User
Password
Z123456
Parameter
Description
Mandatory Enter the login password of the
operator again.
Confirm
Example
Z123456
II. Prerequisites
You have logged in as the administrator or an operator authorized to delete operators.
Operation description
2
3
Select the operator to be deleted in the list. Select User/Delete or click the
button in the Operator Management window.
to refresh the user list. You
Click Yes in the popup dialog box, and click
can find that the selected operator has been deleted.
II. Prerequisites
z
The administrator can modify the description and password of itself or any
operator.
Operation description
The administrator and Operator can modify all information except the name.
After modification, click OK.
Entry
Office
Manageme
nt Interface
Adding an Office
Deleting an Office
Modifying an Office
II. Prerequisites
None.
Operation description
Obtain the IP address of the office to be added, that is, the IP address used
by the CG9812 server to connect with the CG9812 client (or the NMS), and
define the office name.
Click Set, and then the office information will be listed in the list box. After
confirmation, click Save to add the office.
on the
Description
Example
Office
Beijing
IP
10.70.141.11
Type
iGWB
Caution:
You must set an office when you run the client for the first time. Otherwise, the client
cannot connect with the CG9812 server. Specifically, when the User Login dialog box
is displayed in the CDR console, click Office Management to set the office in the
Office Management dialog box before you log in.
II. Prerequisites
None.
Operation description
Select the office to be deleted, and then click Delete. After confirmation, click
Save to delete the office.
on the
II. Prerequisites
None.
Operation description
Select the office to be modified in the list box and enter the new office
information in the dialog box.
Click Set, and then the new office information is listed in the list box. After
confirmation, click Save to modify the office information.
on the
Customize the timeout time and lock time of the CG9812 Client.
In the CDR console, click System/System Customize to display the
System Customize dialog box.
System
Customize
Interface
II. Prerequisites
None.
Operation description
Select the checkbox before Timeout Setting (20 600s). Enter the time
value, and then click OK.
Note:
The timeout value ranges from 20 seconds to 600 seconds.
II. Prerequisites
None.
Operation description
Set the idle time (in minutes) before the system is locked and click OK. The
value ranges from 0 to 1440 minutes. If it is set to 0, the system will never be
locked.
Entry
Log in to the CDR console. The left pane shows the navigator tree
that is divided into several tab pages based on access points (for
example, the CG node shown in the following figure). The navigator
tree displays the CDR storage mode in the server.
CDR
operation
interface
Printing a CDR
II. Prerequisites
You have logged in as the administrator or an operator authorized to browse CDRs.
Operation description
Log in to the CDR console. The left pane shows the navigator tree that is
divided into several Tab pages based on access points (for example, the
CG node shown in the following figure.), The navigator tree displays the
CDR storage mode in the server.
Right-click the sub-window and you will see the following options on the
shortcut menu:
Select Refresh to obtain the latest CDR information from the CG9812
server.
Select Find to set the specified querying conditions, such as name, type
or size to find the CDRs.
Select Bill Browse or click a CDR file to display the Choose Bill Format for
File Browsing dialog box.
No.
Operation description
Click OK and the Bill Info menu is added to the menu bar of the CDR
console. The Browse Original Bill window pops up and displays all bills in
this format.
If the bills are displayed on more than one page, right-click the current page
and select Next page/Previous page or click
pages. Each page displays 50 records.
and
to view other
No.
Operation description
z
Click
Click
The bill detailed information varies with the CDR types. Click OK to close the
dialog box.
Note:
The example only describes the operations against CDRs. The operations against final
bills are similar.
II. Prerequisites
You have logged in as the administrator or an operator authorized to browse CDRs.
Operation description
Select the bill format to be queried and then click Next to display the Set
Query Condition dialog box.
The query conditions displayed will vary with the CDR formats. Set the query
conditions, and click OK to display the Bill Query window.
No.
Operation description
If the bills are displayed on more than one page, right-click the current page
and select Next page/Previous page or click
pages. Each page displays 50 records.
z
Click
Click
and
to view other
Note:
The example only describes the operations against CDRs. The operations against final
bills are similar.
II. Prerequisites
You have logged in as the administrator or an operator authorized to browse
CDRs.
Only CDRs in the CDR list can be browsed.
Operation description
Enter the search type in Field, including Name, Type, Size, Modifying Date,
and Creating Date.
Enter the filed matching condition in Matching, including Entire Filed, Field
Head, and Part of Field.
Click Find First to display the first CDR matching the conditions:
z
6
z
If the first CDR is found, you can click Find Next to display the next CDR
matching the conditions.
If no CDR is found, a dialog box is displayed, prompting Cannot find the
searching string. After confirmation, lick OK to return to the Find dialog
box
Note:
The example only describes the operations against CDRs. The operations against final
bills are similar.
II. Prerequisites
You have logged in as the administrator or an operator authorized to manage CDRs.
Operation description
Browse or find the CDRs as required.
On the main interface of the CDR console, select Bill Info/Save, or click
in the Bill Browse or Bill Query window. Then the Save Bill Information
dialog box is displayed.
Select Save bills of the current page or Only save selected bills as
required. Enter the name and the path of the destination file, or select an
existing path by clicking Browse. Click OK to save the CDRs.
II. Prerequisites
You have logged in as the administrator or an operator authorized to manage CDRs.
Operation description
Browse or query the CDRs as required.
In the CDR list window, select the CDRs to be printed. Then select Bill
Info/Print or click
Print window.
Note:
Select Bill Info/Print Preview to preview the CDRs before printing. Select Bill
Info/Print Setting to set the font of the CDRs to be printed.
Entry
State
Query
Interface
Description
Primary/Secondary
State
Heartbeat State
Indicates the storage space for CDRs. There are two values
displayed in the "n/m" format. Where, m indicates the total
space of the disk in MB, and n indicates the available space in
MB.
Indicates the storage space for final bills. There are two
values displayed in the "n/m" format. Where, m indicates the
total space of the disk in MB, and n indicates the available
space in MB.
Physical MEM
(MB)
II. Prerequisites
You have logged in as the administrator or an operator authorized to query system
information.
Operation description
The state information for the current server is displayed in the State Query
dialog box.
No.
Operation description
Double-click a record to display the State Detailed Information dialog box.
You can see all the detailed information in real time.
Description
Physical MEM
Primary/Secondary
State
Heartbeat State
Indicate the working state of the heartbeat links. There are two
indicators -- total and active.
Parameter
Back Disk Space
Description
Indicate the final bill storage space, including two indicators
total and available.
II. Prerequisites
You have logged in as the administrator or an operator authorized to query system
information.
Operation description
Set the two parameters (Save Status and Time Span) as required.
Description
Example
Save
Status
Open
Time Span
II. Prerequisites
You have logged in as the administrator or an operator authorized to query system
information.
Operation description
The system provides both operation logs and system logs to help
you locate problems. One log file is created daily, named as the date
plus log as its extension. Each log file is saved for one month and
then deleted.
Entry
Log View
Interface
Browsing Log
Saving Log
Clearing Log
Printing Log
II. Prerequisites
You have logged in as the administrator or an operator authorized to browse logs.
z
The administrator can browse the system log and the operation logs of all the
operators.
Huawei Technologies Proprietary
2-29
The operators with log browsing authority can browse their own operation logs, but
Operation description
Enter the log browse conditions. Select the user name and log type, and set
the start time and end time for log browsing. Then, click OK. The logs
meeting the conditions are displayed in the LogView window.
No.
Operation description
Double-click a log entry, or select it and press Enter, to view the detailed
information of it.
In the Detailed Information of Log window, click Next to view the next log
entry, and click Previous to view the previous log entry.
Description
User name
All users
LogType
Operation Log
Start/End
Example
Start:
2005-01-22-18:00:50
End:
2005-01-24-18:00:50
Description
Example
admin
2005-01-22
18:00:50
Operation
Place
10.70.141.132
Log Source
For a system
log, the
operation
command is "-".
Operation
Command
Command
Detail
Query
the
information of
an operator.
Operation
Result
SUC
LogType
OPRT
For an operation
log, the
operation
command is the
actual
operation, such
as LST OP.
II. Prerequisites
z
Only the administrator can save the system logs and the operation logs for all
operators.
The operators with log operation authority can browse their own operation logs but
Operation description
Select Save All Log Record or Only Save Selected Log Record as
required. Enter the destination file name to save the log records, or select an
existing path by clicking Browse. Click OK to save the log records
Description
Example
Only
Save
Selected Log
Record
Path
If you enter
20040702.txt, then the
log is saved in the
C:\iGWB_Client\Bin\20
040702.txt file.
Note:
The CG9812 system creates the log files everyday. The logs created are saved in the
D:\other\log directory of the CG9812 server.
II. Prerequisites
The administrator can clear the system logs and the operation logs for all
operators.
The operators with log operation authority can only clear their own operation logs
Operation description
II. Prerequisites
z
The administrator can print the system logs and the operation logs for all
operators.
The operators with log operation authority can only print their own operation logs
but cannot print the system logs.
Operation description
The Print dialog box is displayed. Set the print parameters as required and
click OK to print the logs.
Note:
Click
II. Prerequisites
You have logged in as the administrator or an operator authorized to perform
switchover manually.
Operation description
A confirmation dialog box pops up. Click Yes to check the status of the bulb
icon in the status bar. The standby server is activated, and executes #ps
-ef|grep _proc, ensure that cls_proc, knl_proc, ap_proc and om_proc are
running.
Caution:
If the switchover is successful, the server will be disconnected with the CDR console.
Therefore, perform this operation with caution.
II. Prerequisites
You have logged in as the administrator.
Operation description
Click Yes in the popup dialog box to start auxiliary upgrade for the CG9812
server.
Caution:
z
After you perform auxiliary upgrade, the system no longer receives CDRs, which
may cause CDR loss. Therefore, perform this operation with caution. In case of
indeliberate operation, restart the CG9812 program.
In auxiliary upgrade, determine whether to delete the system state files according to
the installation guide to the specific version.
II. Prerequisites
The CG9812 server process is running normally.
Operation description
Double-click the debugws.exe file in the Bin directory of the CG9812 client
to display the User Login Dialog box.
Enter the user name, password, and the office to be managed. Then the
debugging console GUI is displayed.
Note:
z
You can also select Operation/Debug on the main interface of the CDR console or
click
II. Prerequisites
None.
Operation description
. A dialog box is displayed, asking you for
Click Yes, and you can exit the debugging console immediately.
Entry
on the toolbar.
Select Debug/Browse Debug Message, or click
The DebugInfo window appears, displaying the debugging
messages in real time.
CG9812
Debuginfo
GUI
Description
Example
Debug
Content
Debug
Level
Major
Debug
Information
MT_FRONTSAVE
II. Prerequisites
None.
Operation description
Select Debug/Browse Debug Message, or click
on the toolbar. The
DebugInfo window pops up, displaying the debugging messages in real
time. The debugging messages are displayed in different colors according to
different levels.
No.
Operation description
Right-click in the debugging information window and select:
z
z
II. Prerequisites
None.
Operation description
Select Debug/Save Debug Message to enable the save function (then you
can see a mark before Save Debug Message. The Please select save
path dialog box is displayed.
II. Prerequisites
You have logged in as the administrator.
No.
1
Operation description
Select Debug/Mask Level/List Mask Level.
The Result of Query window pops up, displaying the mask level.
2)
No.
1
Operation description
Select Debug/Mask Level/Set Mask Level.
No.
Operation description
The Add Mask Conditions dialog box pops up.
3)
No.
1
Operation description
Select Debug/Mask Level/List Mask Level.
The Result of Query window is displayed.
3
z
II. Prerequisites
None.
Operation description
Select System/Set Debug Colors, or click
dialog box is displayed.
Set the color for each level. Click Restore to Default if you want to restore to
the default settings. Click OK to finish setting.
Entry
ProtocolTra
ce GUI
Description
Example
Msg
Sender
CG9812
Msg
Receiver
Module 1
Sequence
Number
Msg Type
Saving CDRs.
Protocol
Trace
Content
II. Prerequisites
You have logged in as the administrator.
Operation description
2
z
Refresh to clear all information in the window. Then the system will
display new debugging information.
No Scrolling to stop scrolling the messages in the window. In this case,
is activated, and you can print the messages.
II. Prerequisites
You have logged in as the administrator.
Operation description
Entry
Workflow
GUI
Description
Each process of the CG9812 server has a
process ID (PID). The workflow message
contains the PID of the sender.
Example
PT_OM
Parameter
Description
Example
Sender
MID
MT_COLAGENT
Receiver
PID
PT_KERNEL
Receiver
MID
MT_LICENSEMANGE
R
APP Type
MML
Client No.
MML
Client IP
0.0.0.0
CMD Code
220
Len of
Data
II. Prerequisites
You have logged in as the administrator.
Operation description
. The Workflow
Select Workflow/Browse Workflow Message, or click
window pops up, displaying the workflow information in real time.
Right-click in the Workflow window and select:
Refresh to clear all the information in the window. Then the system
displays new workflow trace messages.
No Scrolling to stop scrolling the messages in the window. In this case,
is activated, and you can print the messages.
II. Prerequisites
You have logged in as the administrator.
Operation description
HUAWEI
HUAWEI CG9812
User Manual
Table of Contents
Table of Contents
Chapter 1 System Overview ......................................................................................................... 1-1
1.1 Introduction to the Chapter ................................................................................................ 1-1
1.2 Types of System Users...................................................................................................... 1-1
1.3 System Directory and Main Files ....................................................................................... 1-1
1.3.1 Directory structure and main files of the server ...................................................... 1-1
1.3.2 CDR storage directory and main files ..................................................................... 1-3
1.3.3 Common directory structure and main files ............................................................ 1-5
1.4 Directory Structure of the CG9812 Client .......................................................................... 1-6
Chapter 2 Routine Maintenance................................................................................................... 2-1
2.1 Introduction to the Chapter ................................................................................................ 2-1
2.2 System Running................................................................................................................. 2-1
2.3 Hard Disk Detection ........................................................................................................... 2-2
2.4 Operation Maintenance ..................................................................................................... 2-3
Chapter 3 Troubleshooting .......................................................................................................... 3-1
3.1 Introduction to the Chapter ................................................................................................ 3-1
3.2 Fault Positioning Information on the CG9812.................................................................... 3-1
3.3 Fault positioning information on OS................................................................................... 3-3
3.4 Collection of Fault Positioning Information ........................................................................ 3-4
3.5 Trace Information and Maintenance .................................................................................. 3-5
3.5.1 Usable Front Disk Space Insufficient for the Minimum Alarming Space................. 3-5
3.5.2 Usable Back Disk Space Insufficient for the Minimum Alarming Space ................. 3-5
3.5.3 Usable Backup Medium Space Insufficient for the Minimum Alarming Space ....... 3-5
3.5.4 Usable Front Disk Space Insufficient for the Minimum Switchover Space ............. 3-6
3.5.5 Usable Back Disk Space Insufficient for the Minimum Switchover Space.............. 3-6
3.5.6 Access Point Type, Access Point Type Being %d .................................................. 3-6
3.5.7 Failure of Reading IP Address from MML Server (Default Value %s) .................... 3-7
3.5.8 Error Code %d Returned in Socket Registration When Connecting Kernel Process3-7
3.5.9 Kernel Process Not Running................................................................................... 3-7
3.5.10 Failure of Opening Listening Port with Error Code %d ......................................... 3-7
3.5.11 Activation Failure of Asynchronous Resource ...................................................... 3-8
3.5.12 Dual-System Activation Failure ............................................................................. 3-8
3.5.13 Switchover............................................................................................................. 3-8
3.5.14 Switchover Failure................................................................................................. 3-9
3.5.15 Operation Failure at Failover Response End........................................................ 3-9
3.5.16 Starting to Perform Handover Operation .............................................................. 3-9
3.5.17 Multiple Failed Activation Attempts at Local Node and can Never be Activated
Unless Heartbeat is Interrupted ....................................................................................... 3-9
Huawei Technologies Proprietary
i
Table of Contents
Table of Contents
Description
Administrator
Normal user
Description
/opt/igwb
/opt/igwb/config
/opt/igwb/config/alarm
/opt/igwb/config/format
/opt/igwb/config/ini
File path
Description
/opt/igwb/config/mml
/opt/igwb/config/resource
/opt/igwb/config/specailformat
/opt/igwb/trace
Description
/opt/igwb/cls_proc
/opt/igwb/ap_proc
/opt/igwb/knl_proc
/opt/igwb/om_proc
/opt/igwb/libformat.so
/opt/igwb/config/ini/igwb.ini
/opt/igwb/config/resource/resource.
dat
/opt/igwb/config/mml/*.dat
/opt/igwb/config/alarm/alarmconfig.
cfg
/opt/igwb/trace/ap_procN_trace.txt
/opt/igwb/trace/cls_proc_trace.txt
/opt/igwb/trace/knl_proc_trace.txt
/opt/igwb/trace/om_proc_trace.txt
operation
and
Description
/var/frontsave
The root directory of the front disk, namely the directory storing
original CDRs. The original CDRs are stored by access point (for
example, R4), and then by date, see Figure 1-1.
/var/backsave
The root directory of the back disk, namely the directory storing
final CDRs , usually in two copies, see Figure 1-2.
1) The final CDRs are stored in
var/backsave/AccessPointName/PathName/Date. In other words,
the final CDRs are stored by access point, by path and then by
date.
2) The backup of the final CDRs is stored in
var/backsave/Second/AccessPointName/PathName. Different
from the storage structure of the final CDRs, their backup is not
stored by date. This directory is open to the billing center to fetch
CDRs. The billing center is required to delete the CDRs once they
are fetched. Consequently, the CDRs will not be accumulated in
this directory.
/var/frontsave
Access
PointName
Date
Original CDRs
Original CDRs
Date
Original CDRs
Original CDRs
Figure 1-1 Storage directory of original CDRs
/var/backsave
Second
AccessPointName
AccessPointName
Patch 1
Patch 1
Date
Final CDRs
Final CDRs
Final CDRs
Patch N
Date
Final CDRs
Final CDRs
Final CDRs
Final CDRs
Final CDRs
Patch N
Date
Final CDRs
Final CDRs
Date
Final CDRs
Final CDRs
Description
/var/frontsave/Acc
essPointName/Dat
e/b*.bil
File path
Description
When generating an original CDR, CG9812 converts the
received CDR information and generates a final CDR file with
the information until the size of the file exceeds a specified
value (1 MB usually). Then, CG9812 replaces another CDR
file and repeats the preceding operations.
/var/backsave/Acc
essPointName/Pat
hName/ Date
/b*.dat
Note:
z
z
Description
/var/other
/var/other/alarm
/var/other/log
/var/other/mml
/var/other/perf
/var/other/master
/var/other/querybr
owse
/var/other/cdrstat
/var/other/log_arch
ive
Stores the packed logs. On UNIX, logs are packed and saved
automatically.
File path
Description
/var/other/statusfil
es
/var/frontsave/Acc
essPoint
/var/frontsave/Acc
essPoint/netowrk
/var/frontsave/Acc
essPoint/save
Stores status files of the access point regarding front and back
disks.
Description
/var/other/log/*.log
Log files. The prefix represents the date when the log
file is generated, for example, 20040420.log.
/var/other/statusfiles/backup
_status.bsf
/var/frontsave/AccessPoint/
netowrk/status.dat
/var/frontsave/AccessPoint/
save/R4_FS_MAIN.stf
/var/frontsave/AccessPoint/
save/R4_BS_*_MAIN.stf
Description
C:\iGWB_Client\bin
C:\iGWB_Client\data
Description
C:\WINNT\UICONFIG.ini
C:\iGWB_Client\bin\Frame.exe
C:\iGWB_Client\bin\debugws.exe
System Running
Operation Maintenance
Checking
Process
Running
Status
Checking
Dual-System
Heartbeat
State
Checking the
CDR receiving
status of the
CG9812 from
the switch
Operation guide
Reference standard
For an active dual-system node, all
processes are running. For an
inactive node, all processes are not
running.
The number of the ap_proc
processes on an active node should
be the same as the settings of the
[Common]/APCount item in the
igwb.ini file.
This operation task is available only
to dual-system hardware
configuration, not to single-system
office( the heartbeat state display
0/0 ) .
In the heartbeat state display 2/2,
the denominator indicates the total
number of the heartbeat links and
the numerator indicates the number
of the currently available heartbeat
links. The two numbers should be
equal.
The CG9812 can receive the CDR
generated for this call from the
switch. You can browse this CDR on
the CDR console.
The CDR data is correct without loss
or duplicate.
Maintenance
task
Operation guide
Checking CDR
Collection of
Billing Center
Checking the
bill backup
status
Reference standard
For "AccessPointName", refer to the
settings of
[AccessPoint%d]/APName in the
igwb.ini file. If there are several
access points, check them one by
one.
"PathName" refers to the other
folders except "default" in the
/var/backsave/second/AccessPoint
Name directory, corresponding to
different types of final CDRs. There
might be one or several folders.
Check them one by one.
Operation guide
Reference standard
On the [State Query] interface, disk space is
expressed as "n/m", in which m represents the
total capacity in MBs, and the numerator n
indicates the usable space in MBs.
Checking
Hard Disk
Space
Item
Operation guide
Reference standard
Checking
Hard Disk
Fault
Browsing
CDRs
Checking
trace
information
Operation guide
Start the CDR
console. View the
CDRs to check
whether there are
incorrect CDRs.
Reference standard
Log in to the
CG9812. Check
whether the latest
contents of the files
in the Trace folder
all indicate normal.
1)
2)
Checking
debugging
information
and
checking
exception
alarm
3)
Item
Operation guide
Reference standard
Open the CDR console, and select
[Operation/Manually Switch] to manual
switch over the CG9812 server.
Switchover
test
In dual-system
environments, test
whether the active
and standby node
can be switched
normally.
Chapter 3 Troubleshooting
Chapter 3 Troubleshooting
3.1 Introduction to the Chapter
Generally, troubleshooting undergoes the process of information collection -> fault
location -> fault removal.
Fault positioning information about the CG9812 falls into the following types:
z
Device maintenance and fault positioning interfaces provided in the design of the
CG9812 software, such as trace information, parameter configuration, and log.
Trace contents
Trace records are significant debugging information for the running of the system.
Trace is not equal to abnormality. Usually a large number of trace records are
generated when the system is started or shut down. A few trace records are generated
when the system is operating normally.
The CG9812 application has five types of processes, see Table 3-1.
Table 3-1 Processes of CG9812 server
File path
Description
/opt/igwb/cls_proc
cls_proc_trace.txt
/opt/igwb/knl_proc
knl_proc_trace.txt
/opt/igwb/ap_proc
/opt/igwb/om_proc
om_proc_trace.txt
In the actual running, the dual-system process, kernel process, and operation and
maintenance processes have only one respective process instance, but the access
point process can start one or more process instances depending on the parameter
configuration. Each process instance of the CG9812 creates a trace file. Each trace file
has a size limit of 6 MB. When this limit is reached, the application changes the
filename suffix of the trace file txt to tmp, and then creates a new trace file.
Huawei Technologies Proprietary
3-1
Chapter 3 Troubleshooting
Original CDR: the CDR that the CG9812 collects from the switch.
Final CDR: the CDR with the information converted after being received.
IV. Log
Log records the operations performed on the device through the maintenance console.
Log is helpful in positioning faults.
Log files are stored in /var/other. The system creates a log file every day. The
generation date is used as the file name. .log is the extension of the file. Log file of the
CG9812 is stored for one month by default. After expiration, the log file will be deleted
automatically. Usually the hardware failure is recorded in the log.
V. State Query
The CG9812 provides the state query function to facilitate routine maintenance, but the
function is not very helpful in positioning faults.
You can query the current running state of the CG9812 through the debugging console.
To query the state, follow the steps below:
1)
2)
In the State Query window, click the Setting Properties shortcut icon. The
Setting Properties dialog box is displayed.
3)
Set the Save Status to Open, and the status information will be saved in the
StatsInfo.txt file under the installation directory of the maintenance terminal.
Description
0 represents the active node, and 1 represents the standby
node.
Huawei Technologies Proprietary
3-2
Chapter 3 Troubleshooting
State
Heartbeat State
Description
Heartbeat state is expressed as "n/m", in which the
denominator m indicates the total number of the heartbeat
links and the numerator n indicates the number of the
currently normal heartbeat links. Usually two heartbeat links
are configured, that is, m is equal to 2.
If n is not equal to 0 and m is not equal to n, it indicates that
part of the heartbeat links is faulty.
To ensure the reliable running of the system, check the
heartbeat links and restore the faulty link.
Currently you can query the total space and available space
of the front disk and back disk, which is expressed as "n/m".
Here, the denominator m indicates the total space of the
disk in MBs, and the numerator n indicates the usable
space in MBs.
To dump the outputs for future reference, Execute #netstat na>*.txt to dump the
output results for later query and transfer. It is recommended to name the dumping
file the operation date. For example, 20040805 indicates that operation was
performed on Aug 5th, 2004.
Chapter 3 Troubleshooting
processes of cls_proc, knl_proc, om_proc and ap_proc run. Only when these
processes are activated, you can log in to the parameter configuration console.
CDR format configuration files (All files in the default directory \config\format).
Original and final CDR files containing the exceptional billing information
CDR format configuration files (All files in the default directory \config\format).
Chapter 3 Troubleshooting
3.5.1 Usable Front Disk Space Insufficient for the Minimum Alarming Space
Open the /opt/igwb/config/ini/igwb.ini file. Check the FrontSaveRootDir and excute
#df -k
Check the available space of the file system. If the available disk space is insufficient,
consider reducing the value in [DiskFile]/DeadLineOfAutoDel or delete unnecessary
CDR files.
If they are not configured, the default values for FrontSaveRootDir and
MinDiskAlarmRoom are /var/frontsave and 15% of the total disk capacity
respectively.
3.5.2 Usable Back Disk Space Insufficient for the Minimum Alarming Space
Open the /opt/igwb/config/ini/igwb.ini file. Check the FrontSaveRootDir and
MinDiskAlarmRoom configuration parameters under [DiskFile]. Confirm the disk
storing the final CDRs (back disk CDRs) and the size of the minimum alarming space.
Check the available space of the corresponding disk. Execute the following command
on the server.
#df -k
Check the available space of the file system. If the available disk space is insufficient,
consider
reducing
the
value
in
[DiskFile]/DeadLineOfAutoDel
or
deleting
3.5.3 Usable Backup Medium Space Insufficient for the Minimum Alarming
Space
Open the /opt/igwb/config/ini/igwb.ini file. Check MinBakDeviceRoom under
[NetBackup] and [BackupTask*]. Here, the question mark "*" represents the specific
backup task number. Execute the following command on the server.
#df -k
Check the available space of the disk. If the space is really insufficient, and
Chapter 3 Troubleshooting
the backup medium is a tape, consider changing a new medium, and ensure that
MinBakDeviceRoom is 50 MB.
the backup medium is the local hard disk or network storage, consider moving the
backup data to other place, so as to make available more space in the medium.
3.5.4 Usable Front Disk Space Insufficient for the Minimum Switchover
Space
Open
the
/opt/igwb/config/igwb.ini
file.
Check
the
FrontSaveRootDir
and
3.5.5 Usable Back Disk Space Insufficient for the Minimum Switchover
Space
Open the /opt/igwb/config/ini/igwb.ini file. Check the FrontSaveRootDir and
MinDiskHandoverRoom configuration parameters under [DiskFile]. Confirm the disk
storing the final CDRs (back disk CDRs) and the size of the minimum handover space.
Then, execute the following command on the server.
#df -k
Check the available space of the file system. If the available disk space is insufficient,
consider to reduce the value in [DiskFile]/DeadLineOfAutoDel or delete unnecessary
CDR files.
If they are not configured, the default values for them are 5% of /var/backsave.
Chapter 3 Troubleshooting
3.5.7 Failure of Reading IP Address from MML Server (Default Value %s)
Open the /opt/igwb/config/ini/igwb.ini file. Check whether the LocalIpToMMLClient
parameter under [MML] is correct. If not correct, correct the setting of the parameter.
LocalIpToMMLClient refers to the local IP address of the MML server for the
connection to the MML CG9812 client, that is, the IP address for the CG9812 to
connect the network management system.
Chapter 3 Troubleshooting
3.5.13 Switchover
This information indicates that because the local end of the CG9812 becomes faulty, it
must be switched to the peer.
Table 3-3 Switchover cause table
Switchover
cause code
Explanation
Insufficient front disk space, which means that the size of the
available space of the disk storing the original CDRs is less than the
minimum switchover space (5% by default).
Insufficient back disk space, which means that the size of the
available space of the disk storing the final CDRs is less than the
minimum switchover space (5% by default).
Chapter 3 Troubleshooting
One is the failure of the local CG9812, in which the local CG9812 detects the
interruption of all heartbeats.
The other is the activation failure when the peer attempts to activate itself upon
reception of the failover command.
Such a fault is generated by the local CG9812. In this case, confirm that the peer is
running, and remove the faults at the peer.
The local CG9812 receives a manual switchover command from the CG9812
LMT.
3.5.17 Multiple Failed Activation Attempts at Local Node and can Never be
Activated Unless Heartbeat is Interrupted
The local end continuously performs activation attempts (three times by default), but all
fail. In this case, the local end stops the activation operation, and enters the
FAILDOWN state. After one hour, the local end restores to the normal state, and starts
the activation operation again. The local end repeats the same until the heartbeat links
are restored to be normal.
Description
Severity level
Related fault
None
Problem description
3)
Description
Severity level
Related fault
None
Execute ps -ef | grep _proc on the SUN Solaris workstation
with CG9812 installed, and you may find the ap_proc,
cls_proc, knl_proc, and om_proc processes are not
running. Check /opt/igwb/config/ini/igwb.ini, and no
parameter errors are found. Check the files in the
/opt/igwb/trace directory, and you find the TRACE file of
the om_proc contains some abnormal records.
Problem description
Description
Severity level
Related fault
None
Problem description
Title
Description
Description
Severity level
Related fault
None
While installing the CG9812 on Solaris, execute
sh ./igwb_install.sh script. The script works abnormally.
Some prompts appear.
Problem description
Description
Severity level
Related fault
Problem description
None
SUN mini computers work as the CG9812 server, the
sequence of powering on dual systems is as follow.
1)
2)
3)
Description
Severity level
Related fault
Problem description
None
SUN mini computers work as the CG9812 server, the
sequence of powering off dual systems is as follow.
1)
2)
3)
Description
Severity level
Related fault
None
Problem description
Description
Severity level
Related fault
None
Problem description
Title
Description
Description
Severity level
Related fault
Problem description
In this case, the login user should not log out, and the login
user who does not login as the root user should switch to
the root user using su command. Otherwise, the user can
login as the root user from the console.
Then, use the command of df -k to check the / partition or
/var partition are completely or nearly used up. Delete the
unnecessary files in the partition. Usually, the files in the
/var/adm directory, such as messages.0, and messages.1,
are the backup log files, which can be deleted. Note that
the /var/adm/messages files cannot be deleted directly,
use the following command instead.
# > /var/adm/messages
Description
Severity level
Related fault
Problem description
With
long-term
running
of
the
system,
the
/var/adm/wtmpx file occupies more and more space.
Consequently, the system may reject user login.
Execute the following command.
# > /var/adm/wtmpx
This command is only to clear the content of the file. In this
case, the file length becomes 0 byte, but the file still exists
and file authority is kept unchanged.
Description
Severity level
Related fault
None
Problem description
After making one or two calls, you find that an original CDR
file of 3MB in the CG9812 server, but you only find one or
two CDRs through the CG9812 LMT.
Description
Severity level
Related fault
None
The alarm box always sends the alarm for "network
connection fail". The alarm cannot be removed. The setting
of the ftp server is correct, but the backup cannot be made.
The backup data in igwb.ini are as follows.
[NetBackup]
DestHostIP = 10.66.151.74 ;Destination host IP
address
LocalIP = 10.66.153.11
;Local host IP address
UserName=administrator
Password=admin
BeforeEncode=0
BackupTaskCount=1
;Total number of backup
tasks
Problem description
Description
Severity level
Related fault
None
Problem description
The office requires that all SCDR files on the CG9812 are
in a format of GGfileXX.YYYY. Here, GGfile is fixed; XX
values 01-99, representing different SGSN; YYYY is the
postfix, representing the sequence number. Note that the
sequence number of CDRs values 0001-9999, and
recycles from 0001 after 9999 is numbered.
Title
Description
You can modify configuration in igwb.ini to meet the office's
requirements.
Add the following information under [AccessPoint] in the
igwb.ini files of the active and standby servers of CG9812.
CsnLen=4
Prefix=GGfileXX.
Postfix=
Description
Severity level
Related fault
Problem description
Description
Severity level
Related fault
Problem description
Title
Description
To solve this problem, follow the steps below:
1)
2)
In the igwb1:
>Health Check Summary Information
>A1000-1:
Failed Module
>A1000-2:
Optimal
>
>healthck succeeded!
>---------------------------------------------------------------------A1000-1:
single-controller
Active controller a (c1t5d0)
units: 0 1
/usr/sbin/osa/rdacutil succeeded!
A1000-2:
single-controller
Active controller a (1T31878248) units: none
/usr/sbin/osa/rdacutil succeeded!
In the igwb2:
A1000-1:
single-controller
Active controller a (1T30354225) units: none
/usr/sbin/osa/rdacutil succeeded!
A1000-2:
single-controller
Active controller a (c2t5d0)
units: 0 1
/usr/sbin/osa/rdacutil succeeded!
Alarm
type
Alarm
Alarm
level
NMS category
ALM-0001
Fault
Critical
Software system
ALM-0003
Fault
Major
Software system
ALM-0005
Heartbeat Interruption
Fault
Critical
Software system
ALM-0007
Cluster Switchover
Fault
Critical
Software system
ALM-0009
Private
Interruption
Fault
Critical
Software system
ALM-0013
IP Resource Failure
Fault
Critical
Software system
ALM-0015
Volume
Failure
Fault
Critical
Software system
ALM-0017
Fault
Critical
Software system
ALM-0019
Event
Critical
Software system
ALM-0021
Abnormal CDR
Event
Critical
Software system
ALM-0023
Event
Critical
Software system
ALM-0025
Backup Connection
Failure
Fault
Critical
Software system
ALM-0027
CPU Busy
Fault
Critical
Software system
ALM-0029
Insufficient Available
Memory
Fault
Critical
Software system
ALM-0031
Unauthorized Client
Login
Event
Major
Software system
ALM-0033
License Notice
Event
Major
Software system
ALM-0035
Cluster Handover
Event
Major
Software system
ALM-0037
Hardware Failure
Fault
Critical
Software system
Network
Resource
Alarm
type
Alarm
level
Index
Alarm
NMS category
ALM-0039
Software Reset
Event
Major
Software system
ALM-0051
Alarm Box
Disconnection
Event
Major
Software system
ALM-0053
User Information
Change
Event
Major
Software system
ALM-0055
Fault
Major
Software system
ALM-0057
Insufficient Available
Memory (major)
Fault
Major
Software system
ALM-0059
No GSN Response
Fault
Major
Software system
Description
Alarm description
The disk space for storing CDRs, final bills, or backup files
is lower than the minimum space.
Alarm parameter
Impact on system
System response
Correlative alarms
None
z
z
Possible cause
Solution
Description
Alarm description
The billing center has not fetched the bills for long.
Alarm parameter
Impact on system
None
Title
System response
Correlative alarms
Possible cause
Description
None
z
z
Solution
z
z
Description
Alarm description
Alarm parameter
None
Impact on system
None
System response
None
Correlative alarms
Possible cause
z
z
Solution
z
Description
Alarm description
Alarm parameter
None
Impact on system
None
System response
None
Title
Correlative alarms
Description
z
z
Possible cause
Solution
Description
Alarm description
Alarm parameter
Impact on system
System response
None
Correlative alarms
Possible cause
z
z
Solution
Description
Alarm description
Alarm parameter
Impact on system
System response
None
Correlative alarms
z
z
Possible cause
Solution
Description
Alarm description
Alarm parameter
Impact on system
System response
None
Correlative alarms
z
z
Possible cause
Solution
Description
Alarm description
Alarm parameter
Impact on system
System response
None
Correlative alarms
z
z
Possible cause
Solution
Description
The CG9812 cannot store CDRs, final bills or backup bills.
Bill type: 0-CDR; 1-Final; 2-Backup
Alarm parameter
File name: Channel ID, the name of the bill file failed to be
stored
Impact on system
System response
None
Huawei Technologies Proprietary
5-5
Title
Correlative alarms
Description
z
z
Possible cause
Solution
Description
Alarm description
Alarm parameter
Impact on system
None
System response
None
Correlative alarms
z
z
Possible cause
Solution
Description
Alarm description
Alarm parameter
Impact on system
None
System response
None
Correlative alarms
z
z
z
Possible cause
z
z
Solution
Description
Alarm description
Alarm parameter
Impact on system
None
System response
None
Correlative alarms
Possible cause
z
z
Solution
Description
Alarm description
Alarm parameter
None
Impact on system
None
System response
None
Correlative alarms
z
z
Possible cause
Solution
Description
Alarm description
Alarm parameter
None
Impact on system
None
System response
None
Correlative alarms
z
z
Title
Description
Possible cause
Solution
Description
The Client attempted unauthorized login for several times.
z
Alarm parameter
z
Impact on system
None
System response
None
Correlative alarms
z
z
z
Possible cause
Solution
Description
Alarm description
Alarm parameter
Impact on system
System response
Correlative alarms
z
z
z
Possible cause
Solution
Description
Alarm description
Alarm parameter
None
Impact on system
None
System response
Correlative alarms
z
z
Possible cause
Solution
None
Description
Alarm description
Alarm parameter
Impact on system
System response
Correlative alarms
Possible cause
z
z
z
Title
Description
z
Solution
Description
The CG9812 is restarted.
z
Alarm parameter
Cause
value:
0-System-triggered
switchover;
1-Operator-made switchover.
Operator: The operator that resets the CG9812 is _
by default.
Impact on system
None
System response
None
Correlative alarms
z
z
z
Possible cause
z
z
Solution
None
Description
Alarm description
The CG9812 does not receive the correct data from the
alarm box in 30 seconds.
Alarm parameter
None
Impact on system
System response
None
Correlative alarms
z
z
z
Possible cause
z
Solution
Check the serial port cable, and reset the alarm box.
Description
The operator adds, deletes, or modifies the user
information.
z
Alarm parameter
Impact on system
None
System response
None
Correlative alarms
z
z
Possible cause
None
Solution
None
Description
Alarm description
The disk space for storing CDRs, final bills or backup bills
is lower than the minimum value.
Alarm parameter
Impact on system
System response
None
Correlative alarms
z
z
Possible cause
Solution
Description
Alarm description
Alarm parameter
None
Impact on system
None
Title
System response
Correlative alarms
Description
None
z
z
Possible cause
Solution
Description
The GSN does not respond to the system.
z
z
Parameter 1:0-GTP.
Parameter 2:IP address of GSN.
Impact on system
System response
Correlative alarms
Possible cause
Solution
z
z
z
z
HUAWEI
HUAWEI CG9812
User Manual
Appendix
Table of Contents
Table of Contents
Appendix A Common UNIX Commands......................................................................................A-1
A.1 Introduction to the Chapter................................................................................................A-1
A.2 Common Operations in UNIX System...............................................................................A-1
A.3 Common Commands for UNIX User Management...........................................................A-6
A.4 UNIX Utility Commands and Programs.............................................................................A-6
A.5 UNIX System Resource Commands .................................................................................A-7
A.6 UNIX Network Communication Commands ......................................................................A-7
Appendix B Abbreviations ...........................................................................................................B-1
Function
pwd
cd [Directory]
mkdir [Directory]
Create a directory.
rmdir [Directory]
Delete a directory.
Function
Copy a file
mv File 1 File 2
rm [Option] File
Delete a file
Function
clear
Clear screen
IV. vi Command
Usage: # vi filename
Remarks: vi is a full-screen editor. In case of the command followed by several file
names, the second file is automatically opened when the first one is closed, and so on.
You must master vi for UNIX development.
The vi works in either command mode or input mode. In the input mode, all inputs are
inserted into the buffer area being edited currently as text. In the command mode, input
characters are translated into commands.
In the input mode, you can press <ESC> to enter the command mode.
1)
Function
Insert text to the end of the line where the cursor is placed.
cw
Add new text into the place where the cursor resides
2)
Function
h, <Left>, backspace
j, <Down>
K, <Up>
l, <Right>, space
0 (digit)
b, B
w, W
Move the cursor to the first character of the word after the
original one (C for ignoring punctuations)
[[
]]
Command/Usage
Function
Move the cursor to the first line of the current buffer area
Move the cursor to the last line of the current buffer area
3)
Function
^B
^U
^F
^D
4)
Go to Line N
Function
:n
Go to line n
nG
Go to line n
1G
5)
Modify Command
Function
6)
Function
7)
Delete Text
Function
dd
dnd
dG
:line1, line2d
:line1, $ d
Delete all lines from line1 to the end of the file ($ for
the end of the file)
8)
Function
:w
:w!
:w file
:w! file
:r file
:r ! command
:q
Quit editing
:q!
Force quit
:e file name
:e !
Command/Usage
Function
:sh
:! command
:n
Function
Delete a user
Function
pack/unpack File
Command/Usage
Function
Calculator
bc
Function
ps [Option]
who [Option]
which command
uname [Option]
ifconfig [Option]
Function
ping IP address
Command/Usage
Function
netstat [Option]
route [Option]
Appendix B Abbreviations
Appendix B Abbreviations
A
ASCII
ASN.1
B
BIOS
BOM
Bill of Material
BC
Billing Center
BS
Billing system
C
CDMA
CDR
CG
Charging Gateway
F
FDDI
FTAM
FTP
G
G-CDR
GGSN-CDR
GGSN
GPRS
GSN
GTP
I
IP
Internet Protocol
L
LAN
M
MML
MO
Magneto-Optical
MSC
Appendix B Abbreviations
MTBF
MTTR
M-CDR
Mobility Management-CDR
N
NE
Network Element
NFS
NM
Network Management
NMC
NSAP
O
OEM
OMC
QoS
Quality of Service
OSI
P
PC
Personal Computer
PCI
PID
Process Identification
PSTN
R
RAM
random-access memory
RFC
S
SGSN
S-CDR
SGSN-CDR
S-SMO-CDR
S-SMT-CDR
T
TCP
U
UDP
UI
User Interface
W
WAN
WCDMA
Appendix B Abbreviations
User Manual
HUAWEI CG9812
Index
Index
SC and LAN switch, 2-12
CDR
browse, 3-9
AP name, 1-3
print, 3-9
AP type, 1-3
quary, 3-9
save, 3-9
localport, 1-4
CDRs
release, 1-3
browsing, 2-15
printing, 2-22
backup precautions
set the backup FTP, 1-30
querying, 2-16
saving, 2-22
CG fault information
billing interfaces
FTAM interface, 6-1
configuration, 3-2
channel, 1-4
cabinet
appearance, 3-1
backup, 2-2
collecting, 2-2
receiving, 2-1
clent software
cable connection
between between netra 20 and TC, 2-12
2-12
client consists
help, 8-8
User Manual
HUAWEI CG9812
Index
backup last file, 1-25
cluster parameters
common operation
closing, 2-4
close, 2-2
locking, 2-3
common parameters
access point count, 1-2
bge3, 4-15
configuration
User Manual
HUAWEI CG9812
Index
qfe1, 4-16
qfe3, 4-16
directory structure
CDR storage, 1-3
client, 1-6
common, 1-5
system, 1-1
disk
free space
disk partioning
disk group partitioning, 1-9, 1-10
funcation
dual-system
environmental requirement
FAQ
fault, 2-3
space, 2-2
hardware preparations
User Manual
HUAWEI CG9812
Index
the VTS software, 4-17, 4-19
hardware reliability
haredware preparations
3310 disk arrary, 1-4
netra20 minicomputer, 1-4
TC, 1-4
key terminologies
heartbeat links
ce0, 2-11
ce1, 2-11
consolidation, 7-6
eri0, 2-12
sort, 7-6
home0, 2-12
LMT, 1-3
lock system
relogin, 2-3
log parameters
install CG server
praparations, 7-1
logs
installing HA system
browsing, 2-29
clearing, 2-34
printing, 2-34
saving, 2-32
LUN, 1-9
preparations, 5-1
main hardware
installing utilities
User Manual
HUAWEI CG9812
Index
netra 20 description, 2-2
manager license
checking correctness, 5-19, 5-16
configuration, 2-3
configuration, 2-3
saving, 2-46
check, 1-20
managing offices
adding, 2-10
deleting, 2-11
modifying, 2-12
managing operator
adding, 2-6
deleting, 2-8
modifying, 2-8
NMS, 1-2
O&M function
office
IP, 2-11
name, 2-11
type, 2-11
modifying files
operation maintenance
N68-22, 3-1
exiting, 2-38
User Manual
HUAWEI CG9812
Index
startup, 2-1
logging, 2-37
protocol message
browsing, 2-46
RAID, 1-8
authority, 2-7
related parameters
confirm, 2-8
description, 2-7
name, 2-7
password, 2-7
parameters in log
reliability
date, 2-32
root disk
planning
port usage
routine maintenance
SC, 3-1
security management
processing CDRs
collecting, 4-1
service process
User Manual
HUAWEI CG9812
Index
backsave, 1-3
service processes
frontsave, 1-3
sub-window, 1-6
configuring, 5-6
software configuration
application, 1-5
application software, 1-5
SWAP, 1-8
system alarming
abnormal CDR, 5-6
software reliability
error tolerance, 6-3
solaris patches
patch tools, 4-7, 4-9
sorting CDRs
consolidates, 3-8
saves, 3-8
standard protocal
FTAM, 1-3
FTP, 1-2
heartbeat, 3-3
physical MEM, 3-3
primary/secondary, 3-2
capability, 2-1
storage environment
scalability, 2-2
simultaneous accesses, 2-1
system information
system parameters
User Manual
HUAWEI CG9812
Index
primary/secondary, 3-10
resiyrces, 3-10
querying, 2-25
setting, 2-27
system reliability
component selection, 6-1
relogin, 1-4
relogout, 1-4
toolbar on the debugging console
system software
billing gateway software, 1-5
exit, 1-8
CG application, 1-5
cluster, 1-5
relogin, 1-8
OS, 1-5
troubleshooting process
fault location, 3-1
system user
administrator, 1-1
two types of IP
TC, 3-1
TC description, 2-6
Administrator, 2-6
technical specification
operator, 2-6
type of fault information
reliability, 7-1
weight, 7-2
terminologies
active/standby, 3-10
channel, 3-10
UFS, 1-8
upgrade server
User Manual
HUAWEI CG9812
Index
installing, 5-15, 5-12
workflow messgae
browsing, 2-48
volume manage
saving, 2-49
i.