AAA V200R002C11LSD002 Network Management Operation Guide 19 (M2000)

AAA
V200R002C11
Network Management Operation

Guide(M2000)
Issue 19
Date 2014-10-31
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2014. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 19 (2014-10-31) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
AAA
Network Management Operation Guide(M2000) About This Document
About This Document
Purpose
This document describes how to use the M2000 to manage the AAA.
Intended Audience
The intended audiences of this document are:
l Network planning engineers

l Installation and commissioning engineers
l On-site maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates an imminently hazardous situation which, if not

avoided, will result in death or serious injury.
DANGER
Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.
WARNING

avoided, may result in minor or moderate injury.

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to
personal injury.
Issue 19 (2014-10-31) Huawei Proprietary and Confidential ii

AAA
Symbol Description
Calls attention to important information, best practices and

tips.
NOTE is used to address information not related to
personal injury, equipment damage, and environment
deterioration.
Update History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Updates in Issue 19 (2014-10-31)

2.2.7 285011075 is added.

The Auth password and Priv password in 1.2.3 M2000 Configurations in SMP SNMPv3
mode are updated.

l 2.2.5 285011069 is added.
l 2.2.6 285011071 is added.
l 1.2.1 Configurations in the AAA is updated.

l 2.1.18 285011059 is added.
l 2.2.3 285011033 is added.
l 2.2.4 285011035 is added.

l 2.1.16 285000441 is added.
l The value of Alarm Level in 2.1.14 285000433 is updated.
Issue 19 (2014-10-31) Huawei Proprietary and Confidential iii

AAA

l 2.1.10 285000427 is updated.
l 2.1.11 285000429 is updated.
l 2.1.12 285000431 is updated.
l 2.1.13 285000432 is updated.
l 2.1.14 285000433 is updated.
l 2.1.15 285000434 is updated.

l 2.3.1.1 285000501 is added.
l 2.3.1.2 285000502 is added.
l The value of Alarm Category in 2.3.1.3 285000503 is updated.
l 2.3.1.4 285000504 is added.
l 2.3.1.5 285000505 is added.
l 2.3.1.6 285000506 is added.

The product version V200R002 is changed to R002C10.

Modify test questions.
Alarm 285000425 is added to report the failure of the connection between the SCP and the
external data sources.

The alarm information about the SCP is added.

The product name infoX AAA is changed to HUAWEI AAA.
Issue 19 (2014-10-31) Huawei Proprietary and Confidential iv

AAA

l The OIDs of performance Indexes are added.
l The SNMP port in the snmp.cfg configure file differs for different version of M2000. We
mark it up in this issue.

Modify test questions.

Alarm 285000415 is added to report the failure of the connection between the FEP and HLR.
The product name infoX-AAA is changed to infoX AAA.

The fifth commercial release.

The forth commercial release.
The structure of the document is consolidated. Certain contents are added or modified.

Third commercial release.
Part 02 "M2000 Network Management System" is added.
Part 03 "Alarm Reference" is added.
Part 04 "Performance Indexes Reference" is added.

Second commercial release.
The path of the snmp.cfg file is modified.
Issue 19 (2014-10-31) Huawei Proprietary and Confidential v

AAA

Initial commercial release.
Issue 19 (2014-10-31) Huawei Proprietary and Confidential vi

AAA
Network Management Operation Guide(M2000) Contents
Contents
About This Document.....................................................................................................................ii

1 Connecting to the M2000..............................................................................................................1
1.1 EMS Overview...............................................................................................................................................................2
1.1.1 M2000 Overview.........................................................................................................................................................2
1.1.2 Networking Between the AAA and the EMS..............................................................................................................2
1.2 Configuring the EMS......................................................................................................................................................2
1.2.1 Configurations in the AAA..........................................................................................................................................3
1.2.2 M2000 Configurations in SMP SNMPv2 mode..........................................................................................................7
1.2.3 M2000 Configurations in SMP SNMPv3 mode........................................................................................................10
1.3 Managing the AAA......................................................................................................................................................15
1.3.1 Alarm Management...................................................................................................................................................15
1.3.2 Statistics Management...............................................................................................................................................17
1.4 Common Problems.......................................................................................................................................................18
1.4.1 Displaying xxxxCONNECTxxxx Repeatedly..........................................................................................................18
1.4.2 Alarm Information Cannot Be Reported...................................................................................................................18
2 Alarm Reference..........................................................................................................................20
2.1 Description of iSCC Alarm Information......................................................................................................................21
2.1.1 285000001.................................................................................................................................................................21
2.1.2 285000009.................................................................................................................................................................22
2.1.3 285000011.................................................................................................................................................................22
2.1.4 285000415.................................................................................................................................................................23
2.1.5 285000417.................................................................................................................................................................24
2.1.6 285000419.................................................................................................................................................................24
2.1.7 285000421.................................................................................................................................................................25
2.1.8 285000423.................................................................................................................................................................25
2.1.9 285000425.................................................................................................................................................................26
2.1.10 285000427...............................................................................................................................................................26
2.1.11 285000429...............................................................................................................................................................27
2.1.12 285000431...............................................................................................................................................................27
2.1.13 285000432...............................................................................................................................................................28
2.1.14 285000433...............................................................................................................................................................28
2.1.15 285000434...............................................................................................................................................................29
Issue 19 (2014-10-31) Huawei Proprietary and Confidential vii

AAA
2.1.16 285000441...............................................................................................................................................................29
2.1.17 285011053...............................................................................................................................................................30
2.1.18 285011059...............................................................................................................................................................31
2.2 Description of Alarm Information in the SMP.............................................................................................................31
2.2.1 285000402.................................................................................................................................................................32
2.2.2 285000403.................................................................................................................................................................32
2.2.3 285011033.................................................................................................................................................................33
2.2.4 285011035.................................................................................................................................................................34
2.2.5 285011069.................................................................................................................................................................34
2.2.6 285011071.................................................................................................................................................................35
2.2.7 285011075.................................................................................................................................................................36
2.3 Description of Alarm Information in the System.........................................................................................................36
2.3.1 Description of Fault Alarm Information in the System.............................................................................................37
2.3.1.1 285000501..............................................................................................................................................................37
2.3.1.2 285000502..............................................................................................................................................................38
2.3.1.3 285000503..............................................................................................................................................................38
2.3.1.4 285000504..............................................................................................................................................................39
2.3.1.5 285000505..............................................................................................................................................................39
2.3.1.6 285000506..............................................................................................................................................................40
2.3.2 Description of Event Alarm Information in the System............................................................................................40
2.3.2.1 285000405..............................................................................................................................................................40
2.3.2.2 285000407..............................................................................................................................................................41
2.3.2.3 285000410..............................................................................................................................................................41
3 Performance Indexes Reference................................................................................................43

3.1 Statistics of the Authentication Performance of the Proxy AAA.................................................................................44
3.1.1 IP Address of the Home Authentication Server........................................................................................................44
3.1.2 Authentication Port Number......................................................................................................................................45
3.1.3 Number of Forwarded Authentication Request Messages........................................................................................46
3.1.4 Number of Forwarded Authentication Success Messages.........................................................................................46
3.1.5 Number of Forwarded Authentication Denial Messages...........................................................................................47
3.2 Statistics of the Accounting Performance of the Proxy AAA......................................................................................48
3.2.1 IP Address of the Home Accounting Server.............................................................................................................48
3.2.2 Accounting Port Number...........................................................................................................................................49
3.2.3 Number of Forwarded Accounting Request Messages.............................................................................................50
3.2.4 Number of Forwarded Accounting Response Messages...........................................................................................50
3.3 Statistics of the Authentication Performance of the Local AAA.................................................................................51
3.3.1 Number of Received Authentication Request Messages...........................................................................................52
3.3.2 Number of Sent Authentication Success Messages...................................................................................................52
3.3.3 Number of Sent Authentication Denial Messages.....................................................................................................53
3.4 Statistics of the Accounting Performance of the Local AAA.......................................................................................54
3.4.1 Number of Received Accounting Request Messages................................................................................................54
Issue 19 (2014-10-31) Huawei Proprietary and Confidential viii

AAA
3.4.2 Number of Sent Accounting Response Messages.....................................................................................................55
4 FAQ................................................................................................................................................57
4.1 Changing Encrypted Passwords...................................................................................................................................58
A Performance Terms....................................................................................................................59
B Acronyms and Abbreviations...................................................................................................61
Issue 19 (2014-10-31) Huawei Proprietary and Confidential ix

AAA
Network Management Operation Guide(M2000) 1 Connecting to the M2000
1 Connecting to the M2000
About This Chapter
This chapter describes how to connect the AAA to the M2000 and how to manage the AAA
through the element management system (EMS).
1.1 EMS Overview

This section describes the networking between the EMS and the AAA.
1.2 Configuring the EMS

This section describes the basic configurations for the AAA to connect with the EMS.
1.3 Managing the AAA

This section describes the management functions of the EMS for the AAA.
1.4 Common Problems

This section describes the common problems when the AAA connects to the EMS and solutions
to the problems.
Issue 19 (2014-10-31) Huawei Proprietary and Confidential 1

AAA
1.1 EMS Overview

This section describes the networking between the EMS and the AAA.
1.1.1 M2000 Overview
This section describes the function, architecture and environment of the M2000.
1.1.2 Networking Between the AAA and the EMS
This section describes the networking between the AAA and the EMS.
1.1.1 M2000 Overview

This section describes the function, architecture and environment of the M2000.
The M2000 element management system is network element (NE) management software in the
wireless network. The M2000 provides unified NE management.
The M2000 helps to maintain Huawei mobile products and provides centralized and unified
network management of mobile NEs. The M2000 provides basic network management functions
and various optional functions, including configuration management, performance management,
fault management, security management, log management, topology management, software
management, and system management.
1.1.2 Networking Between the AAA and the EMS

This section describes the networking between the AAA and the EMS.
Figure 1-1 shows the networking between the AAA and the EMS.
Figure 1-1 Networking diagram between the AAA and the EMS
The EMS communicates with the Service Management Point (SMP) of the AAA through the
Simple Network Management Protocol (SNMP). The SMP obtains the required information
from the iSCC and the MML of AAA. Then the SMP sends the information to the EMS.
1.2 Configuring the EMS

This section describes the basic configurations for the AAA to connect with the EMS.
1.2.1 Configurations in the AAA

AAA
This topic describes AAA configurations that must be completed before the AAA connects to
the M2000.
1.2.2 M2000 Configurations in SMP SNMPv2 mode

This topic describes M2000 configurations that must be completed before the M2000 connects
to the AAA in SMP SNMPv2 mode.

1.2.1 Configurations in the AAA

This topic describes AAA configurations that must be completed before the AAA connects to
the M2000.
Prerequisites
The AAA has been installed and is running properly.
Procedure
Step 1 Configure M2000 information in the snmp.cfg file.
1. Log in to the AAA server as the smp user.
2. Open the $HOME/smp_run/cfg/snmp.cfg file.
vi $HOME/smp_run/cfg/snmp.cfg
[MANAGER]
IPADDR = 10.137.161.5
PORT = 10163
[AGENT]
IPADDR = itellin156
PORT = 1888
READCOMMUNITY = private
WRITECOMMUNITY = private
//The security user name of the mib

SECURITYUSER = smp
//The context name that is used to access the mib objects of AAA
CONTEXTNAME = NULL
//Authentication protocol, 1-None, 2-MD5, 3-SHA
AUTHENCRYPT = 2
//Authentication password that NMS M2000 uses to log in to AAA
AUTHPASSWORD = D63CB0574268EB08053CF4729BA5A736
//Privacy protocol, 1-None, 2-DES
PRIVACYENCRYPT = 1
//Privacy password that NMS M2000 uses to log in to AAA
PRIVPASSWORD = D63CB0574268EB08053CF4729BA5A736
……
[MESSAGE_STATISTICS]
//whether query by nodeID,0-no,1-yes
MessageQueryByNodeID = 0
//message statistics intervalue,min,[5,1440]
MessageOutputInterval = 30
//message statistics output path
MessageOutputPath = smp_run/log/report/msgRpt
//message statistics report name
MessageOutputName = msgReportFromSCP

AAA
NOTE
The default home directory of the smp user is /export/home/smp.
3. Modify the $HOME/smp_run/cfg/snmp.cfg file based on the site requirements.
Table 1-1 lists parameters in the snmp.cfg file.
Table 1-1 Parameters in the snmp.cfg file
Configu Parameter Description Example

ration
Item
MANAG IPADDR IP address of the M2000. 10.137.161.5

ER
PORT Trap port of the M2000. 10163
AGENT IPADDR AAA IP address. 192.9.169.9

NOTE
When the AAA is deployed in two-
node cluster mode, set this parameter
to the floating IP address of the iSMS.
PORT SNMP listening port. The AAA 1888

NE port configured in the M2000
must be the same as this parameter
value.
READCOMM Read community name. private

UNITY NOTE
By default, do not use
public as community
name, this
configuration
requires AAA
consistent with
M2000.
WRITECOM Write community name. private

MUNITY NOTE
By default, do not use
public as community
name, this
configuration
requires AAA
consistent with
M2000.
SECURITYU SNMP security user name. This smp

SER parameter is a string of a
maximum of 20 characters. Retain
the default value smp.

AAA

ration
Item
CONTEXTN Context name that is required to NULL

AME access the MIB object on the
SMP. This parameter is a string of
a maximum of 20 characters.
Retain the default value NULL.
AUTHENCR Authentication protocol. 2

YPT The options are as follows:
l 1: no encryption
l 2: message digest algorithm 5
(MD5)
l 3: secure hash algorithm
(SHA)
The default value is 2
You are advised to set this
parameter to 3.
AUTHPASS Encrypted authentication D63CB0574268EB

WORD password used by the M2000 to 08053CF4729BA5
log in to the AAA in the SNMP A736
communication.
NOTE
To ensure the system security,
periodically update all encrypted
passwords in this document. For
details on how to change encrypted
passwords, see 4.1 Changing
Encrypted Passwords.
PRIVACYEN Encryption algorithm used in the 1

CRYPT SNMP communication.
The options are as follows:
l 1: no encryption
l 2: Data Encryption Standard
(DES)
You are advised to set this
parameter to 2.

AAA

ration
Item
PRIVPASSW Private key used by the M2000 to D63CB0574268EB

ORD log in to the AAA in the SNMP 08053CF4729BA5
communication. A736
NOTE
To ensure the system security,
periodically update all encrypted
passwords in this document. For
details on how to change encrypted
passwords, see 4.1 Changing
Encrypted Passwords.
MESSA MessageQuery Statistics the messages. 0

GE_STA ByNodeID The options are as follows:
TISTICS
l 0: Simple statistics.
l 1: Statistics the messages by
node.
4. Save the snmp.cfg file and exit.
Step 2 Set the SNMP_AGENT environment variable in the .cshrc file.

1. Log in to the AAA server as the smp user.
2. Open the environment variable configuration file.
vi $HOME/.cshrc
3. Modify the following configuration item:
#use snmp agent yes or no
setenv SNMP_AGENT yes
The SNMP_AGENT default value is yes, indicating that the SNMP agent is used.
4. Save the .cshrc file and exit.
5. Run the following command in the $HOME directory for the modification to take effect:
source .cshrc
Step 3 Restart the SMP and verify that the SMP processes are normal.
1. Run the following command:
l In the single-node system:
restart.sh
l In the SUN Cluster (two-node cluster):
scswitch -n -j app_isms
scswitch -e -j app_isms
l In the VCS two-node cluster:
hares -offline app_isms -sys itellin1 itellin2

AAA
hares -online app_isms -sys itellin1

2. Run the p command to verify that all SMP processes have started properly.
Ensure that the following processes have started properly:
smp 20334 20333 3 01:52:44 ? 7:40 /export/home/smp/smp_run/bin/commmain /
kernum=3
smp 20335 20333 0 01:52:47 ? 0:04 /export/home/smp/smp_run/bin/smpker 0 0
----End

Prerequisites
l The M2000 server mapping the AAA has been installed and is running properly.
l The M2000 client has been installed and is running properly.
NOTE
The version number of the M2000 client must be the same as that of the M2000 server.
Context
Basic M2000 configurations are completed by using the M2000 client to add AAA NEs to the
M2000.
Procedure
Step 1 Log in to the M2000 client.
Enter the user name, password, and IP address of the M2000 server, as shown in Figure 1-2.
Figure 1-2 Login to the M2000 client

AAA
Step 2 Choose Topology > Main Topology, as shown in Figure 1-3.
Figure 1-3 Choosing Main Topology
Step 3 Select Physical Root from the Current View drop-down list box, as shown in Figure 1-4.
Figure 1-4 Selecting Physical Root
Step 4 Create AAA NEs.

1. Right-click the blank space of the Main Topology page, and choose New > Create Topo
Object, as shown in Figure 1-5.
Figure 1-5 Choosing “Create Topo Object”

AAA
2. On the Create Topo Object page, click AAA under Core Network Series in the navigation
tree, and set AAA-related parameters, as shown in Figure 1-6.
Figure 1-6 Configuring AAA NEs
The following table lists AAA main parameters.
Table 1-2 AAA parameters
Paramet Description Setting

er
Name NE name. Enter a unique NE name in the text box.

The value contains 1 to 54 characters.
IP IP address used by the AAA Enter a value in the text box.

Address to provide services for Set this parameter to the IP address of the
external systems. node where the AAA is located.
Protocol SNMP version supported in Set this parameter to SNMPV2.

Version the connection between the
AAA and M2000.

AAA

er
Port Port number used by the Enter a value in the text box.
AAA to communicate with The value is an integer ranging from 5000
the M2000. to 32765.
This parameter value must be consistent
with the value of [AGENT]PORT in the
$HOME/cfg/snmp.cfg file in the AAA.
Set this parameter based on the site
requirements, for example, 1888.
3. Click OK.
----End

Prerequisites
l The M2000 server mapping the AAA has been installed and is running properly.
l The M2000 client has been installed and is running properly.
NOTE
The version number of the M2000 client must be the same as that of the M2000 server.
Context
Basic M2000 configurations are completed by using the M2000 client to add AAA NEs to the
M2000.
Procedure
Step 1 Log in to the M2000 client.
Enter the user name, password, and IP address of the M2000 server, as shown in Figure 1-7.

AAA
Figure 1-7 Login to the M2000 client
Step 2 Choose Topology > Main Topology, as shown in Figure 1-8.
Figure 1-8 Choosing Main Topology
Step 3 Select Physical Root from the Current View drop-down list box, as shown in Figure 1-9.

AAA
Figure 1-9 Selecting Physical Root
Step 4 Create AAA NEs.

1. Right-click the blank space of the Main Topology page, and choose New > Create Topo
Object, as shown in Figure 1-10.
Figure 1-10 Choosing Create Topo Object
2. On the Create Topo Object page, click AAA under Core Network Series in the navigation
tree, and set AAA-related parameters, as shown in Figure 1-11:

AAA
Figure 1-11 Configuring AAA NEs
The following table lists AAA main parameters.
Table 1-3 AAA parameters

er
Name NE name. Enter a unique NE name in the text box.

The value contains 1 to 54 characters.
IP IP address used by the AAA Enter a value in the text box.

Address to provide services for Set this parameter to the IP address of the
external systems. node where the AAA is located.
Protocol SNMP version supported in Set this parameter to SNMPV3.

Version the connection between the
AAA and M2000.
Security Security name required by Enter a value in the text box.

User SNMP. This parameter value must be consistent
Name with the value of SECURITYUSER in the
requirements, for example, smp.

AAA

er
Port Port number used by the Enter a value in the text box.
AAA to communicate with The value is an integer ranging from 5000
the I2000. to 32765.
This parameter value must be consistent
with the value of [AGENT]PORT in the
requirements, for example, 1888.
Authentic Authentication protocol. Select an option from the drop-down list

ation box.
Protocol This parameter value must be consistent
with the value of AUTHENCRYPT in the
l If the value of AUTHENCRYPT is 1,
set this parameter to None.
set this parameter to MD5.
set this parameter to SHA.
You are advised to set this parameter to
SHA.
Authentic Password of the Enter a value in the text box.

ation authentication protocol. This parameter value must be consistent
Protocol with the value of AUTHPASSWORD in
Password the $HOME/cfg/snmp.cfg file in the AAA.
NOTE
For details about how to obtain the plaintext, see
chapter 6.4 How to Use the AES Tool in the AAA
Password Change Guide.
Privacy Privacy authentication This parameter value must be consistent

Protocol protocol, which is defined in with the value of PRIVACYENCRYPT in
the AAA. the $HOME/cfg/snmp.cfg file in the AAA.
The options are as follows:
l None
l DES
You are advised to set this parameter to
DES.

AAA

er
Privacy Password of the privacy Enter a value in the text box.

Protocol authentication protocol. This parameter value must be consistent
Password with the value of PRIVPASSWORD in the
NOTE
For details about how to obtain the plaintext, see
chapter 6.4 How to Use the AES Tool in the AAA
Password Change Guide.
3. Click OK.
----End
1.3 Managing the AAA

This section describes the management functions of the EMS for the AAA.
1.3.1 Alarm Management

This section describes the alarm management function of the EMS and how to configure alarms
on the AAA side.
1.3.2 Statistics Management

This section describes the statistics management function of the EMS.
1.3.1 Alarm Management

This section describes the alarm management function of the EMS and how to configure alarms
on the AAA side.
Alarm Overview
The alarm information is classified into the following types:
l Event alarm
An event alarm is caused by an event that happens accidentally during the running of the
device. The alarm state is instant, which means that the device is in the alarm state only at
the current time. Certain event alarms are sent in real time. The event alarms need not be
recovered.
l Fault alarm
A fault alarm is an alarm caused by faults in the device or exceptions in the important
functions of the device. The fault alarms should be recovered. When a fault occurs, the NE
system transmits a fault alarm.
The fault alarm is classified into two types: current fault alarm and history fault alarm.
After generating the alarm information, the HUAWEI AAA actively transmits the alarm t. The
EMS receives, displays, shields, dumps, records statistics, and analyzes the alarm. For details
about the alarm management operations, refer to the manuals of the EMS.

AAA
Manually Configuring Alarms on the AAA Side

You can modify system configuration files on the AAA side to generate alarms.
l Modify the threshold.

Decrease the threshold in the alarm configuration file of the AAA to make the system to
be overloaded. Then alarms are generated. For details on the alarm configuration file, see
Table 1-4.
Table 1-4 Alarm configuration files
Configuration Configuration File Configuration File Path

File Description
CPU.cfg Alarm configuration file of ~/AAATools/warn/cfgfile/

the CPU. NOTE
~ indicates the installation path of
MEM.cfg Alarm configuration file of the AAA software.
the memory.
DBSpace.cfg Alarm configuration file of

the database space.
DISK.cfg Alarm configuration file of

the disk space.
DRException.cfg Alarm configuration file of

the disaster recovery.
LogicLog.cfg Configuration file of the

logical log.
l Modify the cycle that the SMP detects alarms.

In the ~/AAATools/warn/cfgfile/maincfg.cfg file, you can set the cycle that the SMP
detects the alarm on the AAA server. The unit of the alarm detection cycle is second.
Table 1-5 lists the parameters that you need to set.
Table 1-5 Settings of the alarm detection cycle
Parameter Description Default Remarks

Alarm
Detection
Cycle (s)
CPU System CPU. 600 The SMP monitors each

component and detects alarms
MEM System memory. 600 every cycle. If any exception
DBSPACE Database space. 600 occurs, the SMP generates an
alarm.
DISK Disk space. 600

AAA
Parameter Description Default Remarks

Alarm
Detection
Cycle (s)
VVR Veritas volume 600

replicator.
LOGICLOG logical log. 600
NOTICE
After modifying the configuration file, you need to restart the monitoring server in csh mode to
validate new settings. To restart the monitoring server, run the following commands:
csh
~/AAATools/warn/bin/stop_monitor
~/AAATools/warn/bin/start_monitor
~ indicates the installation path of the AAA software.
If the value of IFRECOVER in the ~/AAATools/warn/cfgfile/maincfg.cfg file is 0, the system

sends CPU, memory, and disk alarm. And the value of Alarm Category is Event alarm. If the
value of IFRECOVER is 1, the system sends CPU, memory, and disk alarms. And the value of
Alarm Category is Fault alarm. The default value of IFRECOVER is 1.
Viewing Alarms on the EMS Side

You can view the alarm information reported by the AAA server through the M2000 client. For
details, refer to the manuals related to the M2000.
1.3.2 Statistics Management

This section describes the statistics management function of the EMS.
Statistics Overview
The information such as the number of alarms and the number of messages is collected in real
time according to the NE name and alarm level. The results are displayed in a table.
The M2000 records statistics about the following messages of the AAA NE:
l Access-Request
l Access-Accept
l Access-Reject
l Accounting-Request
l Accounting-Response
l Proxy Access-Request
l Proxy Access-Accept

AAA
l Proxy Access-Reject
l Proxy Accounting-Request
l Proxy Accounting-Response
Viewing the Statistical Information on the EMS Side

Through the M2000 client, you can view the information collected by the M2000 system about
the RADIUS messages generated in the AAA. For details, refer to the manuals related to the
EMS.
1.4 Common Problems

This section describes the common problems when the AAA connects to the EMS and solutions
to the problems.
1.4.1 Displaying xxxxCONNECTxxxx Repeatedly

This section describes how to analyze and rectify the fault that xxxxCONNECTxxxx is
displayed repeatedly after the SMP is restarted on the AAA server.
1.4.2 Alarm Information Cannot Be Reported

This section describes how to analyze and rectify the fault that the alarm information cannot be
reported.
1.4.1 Displaying xxxxCONNECTxxxx Repeatedly

This section describes how to analyze and rectify the fault that xxxxCONNECTxxxx is
displayed repeatedly after the SMP is restarted on the AAA server.
Symptom
On the AAA server, restart the SMP. Then the AAA server displays xxxxCONNECTxxxx
repeatedly.
Cause
The database is in abnormal state.
Solution
To rectify the fault, do as follows:
1. Start the database and make sure that the database is in online state.
2. Restart the SMP and make sure that the commmain process is started.
3. Restart the monitoring server in csh mode.
----End
1.4.2 Alarm Information Cannot Be Reported

This section describes how to analyze and rectify the fault that the alarm information cannot be
reported.

AAA
Symptom
When the AAA works normally, the M2000 cannot receive the alarm information transmitted
by the AAA.
Cause
The possible causes are as follows:
l In the EMS, the IP address of the AAA is incorrect.
l In the AAA, the EMS information is incorrect.
l On the AAA server, the AAA applications do not work normally.
l On the AAA server, the database does not work normally.
Solution
To identify the fault cause and rectify the fault, do as follows:
l On the EMS client, check whether the IP address of the AAA is correct. For details, see
the configurations on the EMS side.
l On the AAA server, check whether the values of configurations items related t in the
configuration file are correct. For details, see the configurations on the AAA side.
l On the AAA server, check whether the AAA application is started normally. For details,
refer to the HUAWEI AAA Installation Guide - SUN.
l On the AAA server, check whether the database is started normally. For details, refer to
the HUAWEI AAA Installation Guide - SUN.
NOTE
If the fault persists, contact Huawei engineers.

AAA
Network Management Operation Guide(M2000) 2 Alarm Reference
2 Alarm Reference
About This Chapter
This chapter describes types of the alarms that the AAA generates.
2.1 Description of iSCC Alarm Information

This section describes the alarm information that the iSCC generates and the solution to the fault.
2.2 Description of Alarm Information in the SMP

This section describes the alarm information that the SMP generates and the solution to the fault.
2.3 Description of Alarm Information in the System

This section describes the alarm information generated because of system errors about the data
space, disk space, disk mirroring and database. In addition, this section describes the solution
to the errors.

AAA
2.1 Description of iSCC Alarm Information

This section describes the alarm information that the iSCC generates and the solution to the fault.
2.1.1 285000001
2.1.2 285000009
2.1.3 285000011
2.1.4 285000415
2.1.5 285000417
2.1.6 285000419
2.1.7 285000421
2.1.8 285000423
2.1.9 285000425
2.1.10 285000427
2.1.11 285000429
2.1.12 285000431
2.1.13 285000432
2.1.14 285000433
2.1.15 285000434
2.1.16 285000441
2.1.17 285011053
2.1.18 285011059
2.1.1 285000001
Alarm Cause
The system CPU is overloaded.
Basic Alarm Information

Alarm ID Alarm Category Alarm Type Alarm Level
0285000001 Fault alarm Hardware alarm Warning alarm
Effect on the System

The system performance decreases so dramatically that the service is affected.

AAA
Related Alarm
Null.
Alarm Processing
1. Check the CPU status of the system in which iSSC2 resides.
Make sure that the rate of the free CPU is more than 30%.
2. If the CPU occupation remains high for long time, adjust the overloading control parameters
of iSCC2
Modify the MaxAccess parameter in the ~/iscc2/config/SCPCFG.INI file.
NOTE
~ indicates the home directory of the AAA.
2.1.2 285000009
Alarm Cause
The SCP fails to connect to the database.

0285000009 Fault alarm Communications Major alarm

alarm

The user cannot access the network normally.
Related Alarm
0285000010: The SCP connects to the database successfully.
Alarm Processing
1. Check and recover the fault of network connection between the SCP and remote database.
2. If the network connection is normal, check the status of the database.
2.1.3 285000011
Alarm Cause
The SCP is overloaded.

AAA

0285000011 Fault alarm Quality of service alarm Major alarm

The access to the network of the user is affected. The service cannot be processed in time.
Related Alarm
0285000012: The load of the SCP is normal.
Alarm Processing
Contact Huawei engineers to reduce the number of users connected to the SCP per second.
2.1.4 285000415
Alarm Cause
The connection between the FEP and the HLR fails.

0285000415 Fault alarm Communication Major alarm

alarm

The services cannot be processed and users cannot access the Internet.
Related Alarm
0285000416:The connection between the FEP and the HLR recovers.
Alarm Processing
l Check the physical connection between the AAA and the HLR.
l Check and ensure that the signaling point is set correctly on the AAA and the HLR.
l Check and ensure that the link status of the Signaling System Number 7 (SS7) card of the
Signalware is correct.

AAA
2.1.5 285000417
Alarm Cause
The SCP is busy.

0285000417 Event alarm Software alarm Minor alarm

Related Alarm
None.
Alarm Processing
Check the running status of AAA.
2.1.6 285000419
Alarm Cause
The SCP and Diameter peer is disconnected.

0285000419 Event alarm Communications alarm Major alarm

Related Alarm
None.
Alarm Processing
Check the connection status between AAA and Diameter peer.

AAA
2.1.7 285000421
Alarm Cause
The response from outer entity with SCP connected is overtime.
NOTE
This alarm is generated only when the SCP interacts with an external entity through the Diameter CCR or
Diameter CCA message.

0285000421 Event alarm Communications alarm Minor alarm

Related Alarm
None.
Alarm Processing
l Check the connection status between AAA and Diameter peer.
l Check the processing message capability of Diameter peer.
2.1.8 285000423
Alarm Cause
The SCP is disconnected from the FEP.


alarm

The system cannot be used normally.

AAA
Related Alarm
0285000424: The SCP reconnects to the FEP.
Alarm Processing
Check the TCP connection between the AAA and the FEP.
NOTE
l When RcommFlag in the configuration file /export/home/iscc2/config/SCPCFG.INI is set to 1, the SCP

detects the connection and disconnection with the FEP.
l This alarm will not be triggered when the scf server is restarted.
2.1.9 285000425
Alarm Cause
In ExternalUser mode, The connection between the SCP and the external data sources fails.


alarm

Related Alarm
0285000426: The SCP reconnects to the external data sources.
Alarm Processing
Check the network connection between the AAA and the external data sources.
2.1.10 285000427
Alarm Cause
The IP address pool usage exceeds the maximum.

285000427 Event alarm Software alarm Minor alarm

AAA

Subscribers cannot access the Internet normally.
Related Alarm
None.
Alarm Processing
Free up unused IP addresses.
2.1.11 285000429
Alarm Cause
The number of records in the memory table exceeds the maximum.

285000429 Event alarm Device alarm Critical alarm

Some services cannot be processed normally, and users cannot access the Internet properly.
Related Alarm
None.
Alarm Processing
Change the maximum number of records in the memory table to a value larger than the actual
record number.
2.1.12 285000431
Alarm Cause
Used Dialog exceed 85%.

AAA

285000431 Fault alarm Quality of service Major alarm

alarm

Null.
Related Alarm
285000432.
Alarm Processing
Increase the maximum dialog number.
2.1.13 285000432
Alarm Cause
Used Dialog less than 85%.

285000432 Recover alarm Service alarm Major alarm

Null.
Related Alarm
None.
Alarm Processing
Null.
2.1.14 285000433
Alarm Cause
No Idle Dialog Index.

AAA

285000433 Fault alarm Quality of service Critical alarm

alarm

User Cannot access the Internet.
Related Alarm
285000434.
Alarm Processing
Increase the maximum dialog number.
2.1.15 285000434
Alarm Cause
Have idle Dialog Index.

285000434 Recover alarm Service alarm Fatal alarm

Null.
Related Alarm
None.
Alarm Processing
Null.
2.1.16 285000441
Alarm Cause
Communication Subsystem Failure.

AAA
Alarm Name
The child process is restarted.

Alarm ID Alarm Category Alarm Type Alarm Severity
285000441 Event alarm Communications Minor alarm

alarm

Impacts the efficiency of business within a short time, after being pulled ,system will back to
normal.
Related Alarm
None.
Alarm Processing
Confirm the log file. If there is a log aboute restarting ,please please contact with HUAWEI
AAA R&D to analysis the restarting reason.
2.1.17 285011053
Alarm Cause
The application interface is faulty.
Alarm Name
HLR Response Abnormally.


alarm

The HLR authentication fails.

AAA
Related Alarm
285011054: Clear alarm reported when HLR becomes normal.
Alarm Processing
Check the HLR status.
2.1.18 285011059
Alarm Cause
Resource at or Nearing Capacity.
Alarm Name
The occupancy ratio of SCP inode exceeds the threshold value.
NOTE
This alarm is customized for alarm, the default does not provide.


alarm

No idle disk inode will result in the application system can not provide services.
Related Alarm
285011060: The occupancy ratio of SCP disk inode is less than the threshold value.
Alarm Processing
Confirm the occupancy ratio of SCP disk inode.Please check wether Billproc is abnormal and
can't get file from SCP.
2.2 Description of Alarm Information in the SMP

This section describes the alarm information that the SMP generates and the solution to the fault.
2.2.1 285000402
2.2.2 285000403
2.2.3 285011033

AAA
2.2.4 285011035
2.2.5 285011069
2.2.6 285011071
2.2.7 285011075
2.2.1 285000402
Alarm Cause
The alarm client fails to connect to the SMP.

0285000402 Event alarm Communications Warning alarm

alarm

The system functions improperly.
Related Alarm
Null.
Alarm Processing
1. Check and recover the fault of network between the SMP and the alarm client.
2. If the network is in good connection, check the statuses of application processes on the
alarm client and SMP.
2.2.2 285000403
Alarm Cause
The SMP is disconnected from the SCP.


alarm

AAA

The system service functions improperly.
Related Alarm
0285000404: The SMP connects to the SCP successfully.
Alarm Processing
1. Check and recover the fault of network connection between the SMP and the SCP.
2. If the network is in good connection, check the statuses of application processes on the
SMP and SCP.
2.2.3 285011033
Alarm Cause
System resources is overload.
Alarm Name
No Idle License.
NOTE

Alarm ID Alarm Alarm Type Alarm Severity
Category
285011033 Fault alarm Quality of service alarm Major alarm

The number that New user can not be develop is limited.
Related Alarm
285011034: License exhaust fault recover alarm.
Alarm Processing
Please apply a new License.

AAA
2.2.4 285011035
Alarm Cause
Alarm Name
Used License exceeds the threshold value.
NOTE

285011035 Fault alarm Quality of service alarm Minor alarm

The number that New user can not be develop is limited.
Related Alarm
285011036: Used License is less than the threshold value.
Alarm Processing
Please apply a new License for business development in feature.
2.2.5 285011069
Alarm Cause
Alarm Name
License file will be invalide after trial days.
NOTE

AAA

285011069 Fault alarm Quality of service Minor alarm

alarm

The license file will be invalidated.
Related Alarm
None.
Alarm Processing
Please apply a new License file.
2.2.6 285011071
Alarm Cause
Alarm Name
License file is invalide.
NOTE


alarm

The license file will be invalidated and new user can not be added.
Related Alarm
None.

AAA
Alarm Processing
Please apply a new License file.
2.2.7 285011075
Alarm Cause
Alarm Name
The number of active users exceeds the threshold value.

285011075 Fault alarm Quality of service Minor alarm

alarm

The number that New user can be develop is limited.
Related Alarm
285011076: The number of active users is enough.
NOTE
The ID of recover alarm is 285011076.
Alarm Processing
Expand the number of active users.
2.3 Description of Alarm Information in the System

This section describes the alarm information generated because of system errors about the data
space, disk space, disk mirroring and database. In addition, this section describes the solution
to the errors.
The default value of IFRECOVER is 1, that is, the system sends CPU, memory, and disk alarms.
And the value of Alarm Category is Fault alarm. But when the value of IFRECOVER is 0
the system sends CPU, memory, and disk alarm. And the value of Alarm Category is Event
alarm. The IFRECOVER parameter is saved in $HOME/AAATools/warn/cfgfile/
maincfg.cfg file.

AAA
To start monitoring the alarms, execute the $HOME/AAATools/warn/bin/start_monitor

script. To stop monitoring the alarms, execute the $HOME/AAATools/warn/bin/
stop_monitor script.
NOTE
In the preceding information, $HOME indicates the directory for installing the AAA, and the default
directory is export/home.
2.3.1 Description of Fault Alarm Information in the System

This section describes the fault alarm information generated because of system errors when the
value of IFRECOVER is 1. In addition, this section describes the solution to the errors.
2.3.2 Description of Event Alarm Information in the System

This section describes the event alarm information generated because of system errors when the
2.3.1 Description of Fault Alarm Information in the System

This section describes the fault alarm information generated because of system errors when the
2.3.1.1 285000501
2.3.1.2 285000502
2.3.1.3 285000503
2.3.1.4 285000504
2.3.1.5 285000505
2.3.1.6 285000506
2.3.1.1 285000501
Alarm Cause
The CPU usage exceeds the maximum.

285000501 Fault alarm Device alarm Major alarm

Services cannot be used or modules fail to be started.
Related Alarm
285000502: The CPU usage is changed back to the normal value.

AAA
Alarm Processing
Check for errors in the CPU communication logs.
2.3.1.2 285000502
Alarm Cause
The CPU usage is changed back to the normal value.

Alarm ID Alarm Category Alarm Typ Alarm Level
285000502 Recover alarm Device alarm Major alarm

Null.
Related Alarm
None.
Alarm Processing
Null.
2.3.1.3 285000503
Alarm Cause
The utilization of the disk space exceeds the maximum.

285000503 Fault alarm Hardware alarm Warning alarm

Services cannot be used normally or the module startup is abnormal.
Related Alarm
285000504: The utilization of the disk space is changed back to the normal value.

AAA
Alarm Processing
After files are backed up, delete certain files.
2.3.1.4 285000504
Alarm Cause
The utilization of the disk space is changed back to the normal value.


Null.
Related Alarm
None.
Alarm Processing
Null.
2.3.1.5 285000505
Alarm Cause
The memory usage exceeds the maximum.

285000505 Fault alarm Device alarm Major alarm

Related Alarm
285000506: The memory usage is changed back to the normal value.

AAA
Alarm Processing
Check for errors in the memory communication logs.
2.3.1.6 285000506
Alarm Cause
The memory usage is changed back to the normal value.


Null.
Related Alarm
None.
Alarm Processing
Null.
2.3.2 Description of Event Alarm Information in the System

This section describes the event alarm information generated because of system errors when the
2.3.2.1 285000405
2.3.2.2 285000407
2.3.2.3 285000410
2.3.2.1 285000405
Alarm Cause
The CPU usage exceeds the maximum.

285000405 Event alarm Device alarm Major alarm

AAA

Related Alarm
None.
Alarm Processing
Check for errors in the CPU communication logs.
2.3.2.2 285000407
Alarm Cause
The utilization of the disk space exceeds the maximum.

285000407 Event alarm Hardware alarm Warning alarm

Services cannot be used normally or the module startup is abnormal.
Related Alarm
None.
Alarm Processing
After files are backed up, delete certain files.
2.3.2.3 285000410
Alarm Cause
The memory usage exceeds the maximum.

AAA

285000410 Event alarm Device alarm Major alarm

Related Alarm
None.
Alarm Processing
Check for errors in the memory communication logs.

AAA
Network Management Operation Guide(M2000) 3 Performance Indexes Reference
3 Performance Indexes Reference
About This Chapter
This chapter describes all the performance indexes provided by the AAA for the EMS.
3.1 Statistics of the Authentication Performance of the Proxy AAA

This section describes the measurement unit of the proxy authentication performance and
corresponding measurement indexes.
3.2 Statistics of the Accounting Performance of the Proxy AAA

This section describes the measurement unit of the proxy accounting performance and
3.3 Statistics of the Authentication Performance of the Local AAA

This section describes the measurement unit of the local authentication performance and
3.4 Statistics of the Accounting Performance of the Local AAA

This section describes the measurement unit of the local accounting performance and

AAA
3.1 Statistics of the Authentication Performance of the Proxy

AAA
This section describes the measurement unit of the proxy authentication performance and
Description
The EMS takes statistics of the authentication performance of the AAA that functions as a proxy
RADIUS server.
Measurement Object
SCP module of the proxy AAA.
Granularity Period
The recommended granularity period is 30 minutes.
Sampling Interval
The sampling interval depends on the measurement index. The sampling interval can be 1, 2, 3,
5, 15, or 30 minutes.
3.1.1 IP Address of the Home Authentication Server
3.1.2 Authentication Port Number
3.1.3 Number of Forwarded Authentication Request Messages
3.1.4 Number of Forwarded Authentication Success Messages
3.1.5 Number of Forwarded Authentication Denial Messages
3.1.1 IP Address of the Home Authentication Server
OID
1.3.6.1.2.1.67.1.2.1.1.3.1.2
Description
The IP address of the home authentication server that matches with the proxy authentication
AAA.
Unit
None.

AAA
Measurement Point
Collecting data at a specified time.
Formula
None.
The value is an instant IP address at a certain time.
Related Notes
l Reference value of the normal measurement index range
None.
l Whether to set the alarm threshold in the EMS
No.
l Troubleshooting of the measurement index
None.
3.1.2 Authentication Port Number
OID
1.3.6.1.2.1.67.1.2.1.1.3.1.3
Description
The number of the User Datagram Protocol (UDP) port through which the proxy AAA sends
authentication request messages to the home authentication server.
Unit
None.
Measurement Point
Formula
None.
The value is an instant port number at a certain time.
Related Notes
None.

AAA
No.
None.
3.1.3 Number of Forwarded Authentication Request Messages

OID
1.3.6.1.2.1.67.1.2.1.1.3.1.5
Description
The EMS counts the total number of authentication request messages forwarded to a specified
home authentication server. The number of resent authentication request messages is not
counted.
Unit
None.
Measurement Point
Collecting data at specified sampling intervals.
Formula
None.
The value is the total number of authentication request messages forwarded during a sampling
interval.
Related Notes
None.
No.
None.
3.1.4 Number of Forwarded Authentication Success Messages

OID
1.3.6.1.2.1.67.1.2.1.1.3.1.7
Description
The EMS counts the total number of authentication success messages forwarded to a specified
home authentication server.

AAA
Unit
None.
Measurement Point
Formula
None.
interval.
Related Notes
None.
No.
None.
3.1.5 Number of Forwarded Authentication Denial Messages
OID
1.3.6.1.2.1.67.1.2.1.1.3.1.8
Description
The EMS counts the total number of authentication denial messages forwarded to a specified
home authentication server.
Unit
None.
Measurement Point
Formula
None.
interval.

AAA
Related Notes
None.
No.
None.
3.2 Statistics of the Accounting Performance of the Proxy

AAA
This section describes the measurement unit of the proxy accounting performance and
Description
The EMS takes statistics of the accounting performance of the AAA that functions as a proxy
RADIUS server.
Measurement Object
SCP module of the proxy accounting AAA.
Granularity Period
Sampling Interval
3.2.1 IP Address of the Home Accounting Server
3.2.2 Accounting Port Number
3.2.3 Number of Forwarded Accounting Request Messages
3.2.4 Number of Forwarded Accounting Response Messages
3.2.1 IP Address of the Home Accounting Server

OID
1.3.6.1.2.1.67.2.2.1.1.3.1.2
Description
The IP address of the home accounting server that matches with the proxy accounting AAA.

AAA
Unit
None.
Measurement Point
Formula
None.
The value is an instant IP address at a certain time.
Related Notes
None.
No.
None.
3.2.2 Accounting Port Number
OID
1.3.6.1.2.1.67.2.2.1.1.3.1.3
Description
The number of the UDP port through which the proxy accounting AAA sends accounting
requests to the home accounting server.
Unit
None.
Measurement Point
Formula
None.
The value is an instant port number at a certain time.

AAA
Related Notes
None.
No.
None.
3.2.3 Number of Forwarded Accounting Request Messages

OID
1.3.6.1.2.1.67.2.2.1.1.3.1.5
Description
The EMS counts the total number of accounting request messages forwarded to a specified home
accounting server.
Unit
None.
Measurement Point
Formula
None.
interval.
Related Notes
None.
No.
None.
3.2.4 Number of Forwarded Accounting Response Messages

OID
1.3.6.1.2.1.67.2.2.1.1.3.1.7

AAA
Description
The EMS counts the total number of accounting response messages forwarded to a specified
home accounting server.
Unit
None.
Measurement Point
Formula
None.
interval.
Related Notes
None.
No.
None.
3.3 Statistics of the Authentication Performance of the Local

AAA
This section describes the measurement unit of the local authentication performance and
Description
The EMS takes statistics of the authentication performance of the AAA that functions as a local
RADIUS server. The statistics can be used by the EMS in the maintenance of the AAA. The
statistics can also help to analyze the cause of low authentication success rate and to enhance
the control capability of the EMS.
Measurement Object
SCP module of the AAA that functions as a RADIUS authentication server.
Granularity Period

AAA
Sampling Interval
3.3.1 Number of Received Authentication Request Messages
3.3.2 Number of Sent Authentication Success Messages
3.3.3 Number of Sent Authentication Denial Messages
3.3.1 Number of Received Authentication Request Messages
OID
1.3.6.1.2.1.67.1.1.1.1.5
Description
The EMS counts the total number of authentication request messages received by the RADIUS
authentication server.
Unit
None.
Measurement Point
Formula
None.
interval.
Related Notes
None.
No.
None.
3.3.2 Number of Sent Authentication Success Messages
OID
1.3.6.1.2.1.67.1.1.1.1.8

AAA
Description
The EMS counts the total number of authentication success messages sent by the RADIUS
Unit
None.
Measurement Point
Formula
None.
interval.
Related Notes
None.
No.
None.
3.3.3 Number of Sent Authentication Denial Messages

OID
1.3.6.1.2.1.67.1.1.1.1.9
Description
The EMS counts the total number of authentication denial messages sent by the RADIUS
Unit
None.
Measurement Point
Formula
None.

AAA
interval.
Related Notes
None.
No.
None.
3.4 Statistics of the Accounting Performance of the Local

AAA
This section describes the measurement unit of the local accounting performance and
Description
The EMS takes statistics of the accounting performance of the AAA that functions as a local
RADIUS accounting server. The statistics can be used by the EMS in the maintenance of the
AAA.
Measurement Object
SCP module of the AAA that functions as a RADIUS accounting server.
Granularity Period
Sampling Interval
3.4.1 Number of Received Accounting Request Messages
3.4.2 Number of Sent Accounting Response Messages
3.4.1 Number of Received Accounting Request Messages
OID
1.3.6.1.2.1.67.2.1.1.1.5

AAA
Description
The EMS counts the total number of accounting request messages received by the RADIUS
accounting server.
Unit
None.
Measurement Point
Formula
None.
interval.
Related Notes
None.
No.
None.
3.4.2 Number of Sent Accounting Response Messages

OID
1.3.6.1.2.1.67.2.1.1.1.8
Description
The EMS counts the total number of accounting response messages sent by the RADIUS
accounting server.
Unit
None.
Measurement Point
Formula
None.

AAA
interval.
Related Notes
None.
No.
None.

AAA
Network Management Operation Guide(M2000) 4 FAQ
4 FAQ
About This Chapter
4.1 Changing Encrypted Passwords

AAA
Network Management Operation Guide(M2000) 4 FAQ
4.1 Changing Encrypted Passwords

Procedure
Step 1 Log in to the AAA server as the smp user.
Step 2 Open the $HOME/smp_run/cfg/snmp.cfg file.

vi $HOME/smp_run/cfg/snmp.cfg
Step 3 Search for encrypted password-related configuration items and modify them.
Passwords must be encrypted before being stored. For details about how to obtain the plaintext,
see chapter How to Use the AES Tool in the AAA Password Change Guide.
----End

AAA
Network Management Operation Guide(M2000) A Performance Terms
A Performance Terms
Measurement Index
The measurement index defines what to measure.
The measurement index is referred to as measurement entity in Huawei Technologies Co., Ltd
(hereafter referred to as Huawei) Man Machine Language (MML) specification.
The measurement index consists of the name and unit of the measurement index.
One measurement index can belong to only one measurement unit.
Measurement Unit
For managing a large amount of measurement indexes of the system, the measurement types
can be classified into multiple measurement units. Each measurement unit contains multiple
measurement indexes related to one system function.
Measurement Object
The measurement object defines what to measure.
In the performance management, the measurement object refers to the entity or combination of
the physical or logical resource, such as the service key in an intelligent network and office
direction.
Granularity Period
The granularity period refers to the interval between two rounds of performance data collection
by the EMS from the network element (NE).
The granularity period is referred to as measurement period in Huawei MML specification.
The granularity period is calculated in minutes.
Sampling Interval
Certain measurement indexes need to be collected at a specified rate within a granularity period.
The time interval between two rounds of collection is referred to as sampling interval.

AAA
Network Management Operation Guide(M2000) A Performance Terms
The sampling interval refers to the interval for collecting the performance data on the internal
NEs. The sampling interval is equal to or less than the granularity period and is the divisor of
the granularity period.
For example, for the measurement of the CPU average usage rate, the granularity period is five
minutes, and the sampling period is one minute, which indicates that the system collects the
CUP usage every one minute. Thus, the average usage rate of the CPU is the average of the five
values of CPU usage in five minutes.
Threshold Alarm
If the alarm threshold is set in the EMS, an alarm is generated when the measurement index
exceeds the threshold.

AAA
Network Management Operation Guide(M2000) B Acronyms and Abbreviations
B Acronyms and Abbreviations
AAA Authentication, Authorization and Accounting
CAA Client Access Agent
CMC Call Management Center
CPU Credit Control Answer
DB Database
DCM Data Change Map
iSAP Integrated Service Application Platform
iSCC Integrated Service Control Center
iSMS Integrated Service Management System
SID System Identifier
SMAP Service Management Access Point
SMP Service Management Point
SRL Storage Replicator Log
UPS Uninterrupted Power Supply

AAA
Network Management Operation Guide(M2000) B Acronyms and Abbreviations
VVR VERITAS Volume Replicator
WMAS Web Management Access System


AAA V200R002C11LSD002 Network Management Operation Guide 19 (M2000)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AAA V200R002C11LSD002 Network Management Operation Guide 19 (M2000)

Uploaded by

Copyright:

Available Formats

AAA

Network Management Operation

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 19 (2014-10-31) Huawei Proprietary and Confidential i

About This Document

l Network planning engineers

Indicates an imminently hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Issue 19 (2014-10-31) Huawei Proprietary and Confidential ii

Calls attention to important information, best practices and

Updates in Issue 19 (2014-10-31)

Updates in Issue 18 (2013-09-14)

Updates in Issue 17 (2013-03-15)

Updates in Issue 16 (2013-01-30)

Updates in Issue 15 (2011-12-31)

Issue 19 (2014-10-31) Huawei Proprietary and Confidential iii

Updates in Issue 14 (2011-10-31)

Updates in Issue 13 (2011-08-31)

Updates in Issue 12 (2010-03-31)

Updates in Issue 11 (2009-12-31)

Updates in Issue 10 (2009-10-31)

Updates in Issue 09 (2009-09-30)

Issue 19 (2014-10-31) Huawei Proprietary and Confidential iv

Updates in Issue 08 (2009-05-30)

Updates in Issue 07 (2009-03-31)

Updates in Issue 06 (2009-01-09)

The product name infoX-AAA is changed to infoX AAA.

Updates in Issue 05 (2008-12-10)

Updates in Issue 04 (2008-06-20)

Updates in Issue 03 (2008-03-31)

Part 02 "M2000 Network Management System" is added.

Part 03 "Alarm Reference" is added.

Part 04 "Performance Indexes Reference" is added.

Updates in Issue 02 (2007-12-31)

The path of the snmp.cfg file is modified.

Issue 19 (2014-10-31) Huawei Proprietary and Confidential v

Updates in Issue 01 (2007-07-31)

Issue 19 (2014-10-31) Huawei Proprietary and Confidential vi

About This Document.....................................................................................................................ii

Issue 19 (2014-10-31) Huawei Proprietary and Confidential vii

3 Performance Indexes Reference................................................................................................43

Issue 19 (2014-10-31) Huawei Proprietary and Confidential viii

3.4.2 Number of Sent Accounting Response Messages.....................................................................................................55

Issue 19 (2014-10-31) Huawei Proprietary and Confidential ix

1 Connecting to the M2000

About This Chapter

1.1 EMS Overview

1.2 Configuring the EMS

1.3 Managing the AAA

1.4 Common Problems

Issue 19 (2014-10-31) Huawei Proprietary and Confidential 1

1.1 EMS Overview

1.1.1 M2000 Overview

1.1.2 Networking Between the AAA and the EMS

1.2 Configuring the EMS

Issue 19 (2014-10-31) Huawei Proprietary and Confidential 2

1.2.2 M2000 Configurations in SMP SNMPv2 mode

1.2.3 M2000 Configurations in SMP SNMPv3 mode

1.2.1 Configurations in the AAA

//The security user name of the mib