Hss workshop

Scope and objectives

Objectives

After completing this module the

student will be able to effectively
understand, configure, integrate
and troubleshoot the HSS node.

GEP2-E1/T1
GEP2-E1/T1
GEP2-SAS

GEP2-SAS
Scope

GEP2
GEP2
GEP2
GEP2

GEP2
GEP2
MXB

GED

GED

MXB
› Overview
› HW Overview
› User Interface
› Configuration
› Integration
› Troubleshooting
Overview
 What is HSS & SLF?
› The Home Subscriber Server (HSS) is a logical entity defined in 3GPP Release 8 as:
“The HSS is the master database for a given user. It is the entity containing the
subscription related information to support the network entities actually
handling calls/sessions”.
› The Subscription Locator Function (SLF) is a logical entity defined in 3GPP Release
8 as:
The entity which “is queried by 3GPP AAA server, I-CSCF or Application server to
get the name of the HSS containing the required subscriber specific data. The
SLF is not required in a single HSS environment.”
 Types of HSS
• Classic depoyment
• Front-End Deployment
 Ericsson HSS/SLF overview
Applications &
CUDB
Services
Sh or Dh
LDAP SOAP Sh

Identification handling Application support

Diameter redirect

Diameter proxy
HSS Service provisioning Mobility management
Radius proxy SLF
User authentication Access authorization Load balancer

For IMS, EPC, WLAN/WiMAX domains SLF DB Manager

Wa/Wm S6a D’/Gr’ Cx Cx or Dx

IMS
WLAN/WiMAX EPC and LTE Broadband and
Access network GSM/WCDMA
access network core systems Mobile accesses
 Packaging, commercial view
HSS/SLF 11

HSS/SLF 11 SW application
IMS Sales:
ISM ESM WSM SDA AVG SLF
ISM (+SDA) (+AVG) (+SLF)

EPC Sales:
ESM (+SDA) (+AVG) (+SLF)
TSP 6.0 platform
WLAN/WiMAX Sales:
HW: NSP 5.0 (for upgrades only)
HW: NSP 6.0 (for all packages) WSM (+SDA) (+AVG)

Note: Modules highlighted within parenthesis e.g. (+SDA) are optional modules applicable within identified domain.
 IMS Subscription Manager (ISM)
This Module provides a variety of functionalities
and procedures related to e.g. subscription
management, mobility management
procedures, session establishment control, user
authentication, and access authorization in the
IMS network.
 Subscription Data Access (SDA)
This Module provides the application layer with
user-related data within a network. Moreover, it
acts as repository for application servers profile
data managed as transparent data in HSS server.
 EPC Subscription Manager (ESM)
This Module provides the handling of
subscriptions, authentication, authorization,
user traffic protection and mobility
management in the EPC domain.
 WLAN Subscription Manager (WSM)
This Module provides subscription
management, authentication, authorization and
user traffic protection in the context of WLAN
accesses.
 Authentication Vector Generator
(AVG)
This function performs the algorithms relevant
for the generation of authentication vector in
association with ISIMand USIM-based
authentication for IMS, USIM-based
authentication for EPC or USIM-based
authentication for WLAN.
 Subscription Locator Function (SLF)
module
When multiple and separately addressable HSS
nodes are deployed in the network, the SLF
routes HSS traffic towards the proper HSS
instance, based on the configured SLF traffic
distribution mode (proxy or redirect).
 HSS/SLF Modules and Interfaces System Performance management
Provisioning Provisioning notifications Fault management OSS-RC
System Configuration management
HSS Provisioning SOAP
System SW management
LDAP

PSM ESM
GGSN/AAA IMS SSO
Roaming awareness Evolved Packet Core MME
Packet
Gi S6a
Session Manager SAE Subscription
module
AAA Inter-working IP Works
CSCF
HSS SIH SWx

Subscription Data
(AAA)

IP Multimedia System

SDA
Access

ISM
Application Server
Cx Sh
(e.g. MTAS)
XCAP Server Subscription Data
XCAP Authentication IMS Subscription
Support, module Access module
XCAP
Aggregation Zx
-5 Proxy

retrieval from the HLR at any time

D’/Gr’ Generic Access Network
WSM GAN
Controller (GANC)
Security Gateway
WLAN Subscription Wm, Wa
Authentication vectors retrieval module
HLR/AUC
D’/Gr’

AVG SLF
Authentication Vector Subscription Locator • Dx, Dh (Redirect)
LDAP Generator module Function • Cx, Sh, Zh, S6a (proxy)

CUDB TSP6/NSP6.0 or TSP6/NSP5.0

platform
 HSS Modules and Interfaces
EPC solution System Performance management
Provisioning Provisioning notifications Fault management OSS-RC
System Configuration management
HSS Provisioning SOAP
System SW management
LDAP

Support to: ESM Evolved Packet Core

S6a
MME

MME, S6a SAE Subscription

module
AAA (non-3GPP access), Swx AAA Inter-working IP Works

HSS SWx (AAA)

Subscription Data
Security:
SDA
Access

EPS-AKA 12A
Application Server
Sh
(e.g. MTAS)
Subscription Data
Access module MSP /EAP-AKA
BSF
GAA/GBA support Multi Service Proxy
Zh Server
Boot Strapping Function
Mobility Mgt

D’/Gr’

Authentication vectors retrieval

HLR/AUC
D’/Gr’
Mobility Coordination:
AVG E-UTRAN  2G/3G
Authentication Vector
LDAP Generator module
CUDB TSP6/NSP6.0 or TSP6/NSP5.0
platform
 HSS KEY REQUIREMeNTS
• Persistent Storage of Data
– No data loss
• High availability
– No server -no service for those users
• Smooth upgrade
– Do not need for reprovision
– No down time
• High Capacity
– Number of users
• TPSs
• Data Storage
• Backward compatibility
– Provisioning interfaces
– Traffic interfaces
 EPC Subscription Management (ESM)

• S6a reference point

• EPC subscription management EPC
SubscriptionMa
• Configured profiles support nager
Module
• EPC access authorization
• LTE mobility management S6a
• EPC AKA user authentication (USIM)
• Operator controlled barring
MME
• On-line download of user profile
• IRAT mobility LTE  2G/3G accesses
Ericsson Internal | 2010-04-
16 | Page 17
 SLF Subscription Locator Function
• SLF Subscription Locator Function
• Scalability when more than one HSS server is used
• Data management
• Scalability
• Network redundant configuration
• Public service identifiers (PSI)
• Wildcard PSI
• Domain distributed location
• Individual locator Function
• Wildcard locator function
• Dynamic load balancer
• Diameter redirect support
• Diameter proxy
• RADIUS proxy
 SLF Modes
• The SLF module, depending on the selected operational option, can work
as a 3GPP Subscription Locator Function (SLF) or as a 3GPP Diameter
Proxy/Redirect Agent in the HSS classic servers deployed for IMS, or as
load balancer along with HSS Front-End servers deployed for LTE/EPS and
IMS.
• We’ll focus on Load Balancer function for LTE/EPS solutions.
• HSS SLF module supports a dynamic load balancing mechanism based on
pre-configured weighted load balancing mechanism improved by
dynamically adapting the traffic flow to each HSS/SLF FE according to their
load.
Hardware overview
 Telecom Server Platform (TSP)
• HSS/SLF is based on Ericsson TSP platform.
• TSP characteristics include:
 High system availability
 Duplicated HW for fault tolerance
 Scalability: addition of processor boards increases capacity
linearly
 Use of standardized HW components
 Support for SW upgrades during operation
 Support for geographical network redundancy
 Real-time performance
 NSP 6.0 modularity for a TSP node

TSP-node
capacity and function G G G G D
expansion E
P
E
P
E E U
P D M
Add as needed! 2
-
2
-
2 M
- Y
1 E S
2 1
Appl. processor G SS7 processor T File server A
S
Dummy
GEP2 12GB B
GEP2 4GB 1
PIU

TSP-node G G G G
G G G G
mandatory E
P
E
P
E
P
E
P
E E E E
P D P D
2 2 2 2
2 2
- - - -
2 Loaders 1 1 2 Node 1 1 2 I/O processors, - -
S S
GEP2 12GB 2
G
2
G
Management 2
G
2
G
with Disks A A
S S
B B GEP2 12GB B B

Mandatory
for each
M M
subrack X X
B B

2 Switches
 TSP subrack and Infrastr. boards

M M
X X
B B

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

G G G G G
G G G
E E E E E
E E E
P P P P P
P D D
2 2 2 2 2
2
- - - - -
-
S 1 1 1 1
S
A 2 2 2 2
A
S G G G G
S
B B B B

2 I/O Processors with disks 2 Loaders 2 Node Management

TSP Disk processor board TSP Processor board TSP Processor board
TSP Disk board GEP2 12GB GEP2 12GB
 TSP Infrastructure
G G G G
G G G G
E E E E
E E E E
P P P P
M P D P D M
2 2 2 2
2 2
X - - - -
- - X
B 1 1 1 1 B
S S
2 2 2 2
A A
G G G G
S S
B B B B

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

G G G G G
G G G
E E E E E
E E E
P P P P P
P D D
2 2 2 2 2
2
- - - - -
-
S 1 1 1 1
S
A 2 2 2 2
A
S G G G G
S
B B B B

2 I/O Processors with disks 2 Loaders 2 Node Management

TSP Disk processor board TSP Processor board TSP Processor board
TSP Disk board GEP2 12GB GEP2 12GB
 TSP Node – Minimal configuration
G
E
G G G G G G P
G G G G
E E E E E E 2
E E E E
P P P P P P -
M P D P D M
2 2 2 2 2 2 1
2 2
X - - - -
- -
- - X 2
B 1 1 1 1 1 1 B G
S S
2 2 2 2 2 2 B
A A
G G G G G G
S S
B B B B B B
Application processors
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
TSP Processor board
GEP2 12GB

G G G G G
G G G
E E E E E
E E E
P P P P P
P D D
2 2 2 2 2
2
- - - - -
-
S 1 1 1 1
S
A 2 2 2 2
A
S G G G G
S
B B B B

2 I/O Processors with disks 2 Loaders 2 Node Management

TSP Disk processor board TSP Processor board TSP Processor board
TSP Disk board GEP2 12GB GEP2 12GB
 TSP 6 cabinet – example
• One TSP node
maximum HW configuration 0
M
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
G G G G G G G G G G G G
25
M

in a fully equipped cab X

B
E
P
2
-
E
P
2
-
E
P
2
-
E
P
2
-
E
P
2
-
E
P
2
-
E
P
2
-
E
P
2
-
E
P
2
-
E
P
2
-
E
P
2
-
E
P
2
-
X
B
12 12 12 12 12 12 12 12 12 12 12 12
G G G G G G G G G G G G
B B B B B B B B B B B B

28 boards for application processing Cab le s helf

here: 20 TSP Processor boards 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

(GEP2)
M G G G G G G G G G G G G M
E E E E E E
X E E
P P P P
E E E E X
P D P D P P P P
B 2 2 2 2 B

4 TSP SS7 Processor boards

2 2 - - - - 2 2 2 2
- - 12 12 12 12 - - - -
S S G G G G E E E E
B B B B
A A 1 1 1 1

2 File Servers (GEP2-SAS + GED) S S

Cab le s helf
T
1
T
1
T
1
T
1

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

• One TSP node M

X
B
G
E
P
2
G
E
P
2
G
E
P
2
G
E
P
2
G
E
P
G
E
D
G
E
P
G
E
D
G
E
P
2
G
E
P
2
G
E
P
2
G
E
P
2
M
X
B

minimal HW configuration - - - - 2 2 - - - -
12 12 12 12 - - 12 12 12 12
G G G G S S G G G G
B B B B B B B B
A A
S S

Cab le s helf

TSP infra structure plus 2 TSP

Processor boards for application traffic
processing.
TSP infra structure: 2 I/Os, Application Processors
2 Node Management and 2 loaders
HSS/SLF on EBS HW platform

HSS/SLF
 HSS/SLF on Ericsson Blade HW
HSS on Ericsson Blades (BYB 501 Cabinet)
supporting:
• TSP 6.0 on NSP 6.0 hardware. GEP2 blades
on EGEM subracks.
• TSP 6.0 on NSP 6.1 Ericsson Blade Server
(EBS) hardware. GEP3 blades on EGEM2
subracks. 1800 mm
• Excellent & seamless scalability
• From 2 to 28 HSS blades in TSP 6.0 / NSP
6.0
• From 2 to 30 HSS blades in TSP 6.0 / NSP
6.1
Excellent Capacity/Footprint Ratio 400 mm
600 mm
High Availability (HW and SW redundancy)

NSP 6.1
 TSP Architecture

Node Application External

Management Interfaces Communication

TelORB Clusterware
TSP Clusterware
O&M
DICOS
DICOS LINUX

NSP
TSPHardware
Hardware

Ericsson Internal | 2010-04-

16 | Page 30
 TSP hardware and external connections

Node Management

Traffic and/or
O&M Network
Signaling Network
(IP)
(IP)
Intranet

VIP VIP

IO1 IO2 TP TP TP TP TP TP

TSP Cluster
Internal
Network 0
Internal
Network 1

Linux OS Dicos OS Linux OS

Ericsson Internal | 2010-04-
16 | Page 31
 EPC HSS/SLF Management Components

HSS/SLF modules Shared Applications

HSS_ESM DIA

O&M HSS_AVG PmApplication

SLF tspPM

Ericsson Internal | 2010-04-

16 | Page 32
User Interface
 Control plane for s6a
3GPP TS 23.401 v8.7.0

PDN GW
MME HSS
S5
Diameter Diameter
Serving GW PDSN

SCTP SCTP

IP IP
S1-U
Data link layer Data link layer

eNodeB
Physical layer Physical layer
X2
E-UTRAN

S6a
 S6a interface enables transfer of subscriber related data between MME and HSS
 The S6a interface is based on the Diameter Base protocol and offers a subset of procedures
 Diameter over Stream Control Transmission Protocol is used between the MME and HSS
 General flows
3GPP TS 23.401 v8.7.0
 HSS Command codes
3GPP TS 23.401 v8.7.0

Command-Name Source Destination Abbreviation Code

Update-Location-Request MME HSS ULR 316
Update-Location-Answer HSS MME ULA 316
Cancel-Location-Request HSS MME CLR 317
Cancel-Location-Answer MME HSS CLA 317
Authentication-Information-Request MME HSS AIR 318
Authentication-Information-Answer HSS MME AIA 318
Insert-Subscriber-Data-Request HSS MME IDR 319
Insert-Subscriber-Data-Answer MME HSS IDA 319
Purge-UE-Request MME HSS PUR 321
Purge-UE-Answer HSS MME PUA 321
Notify-Request MME HSS NOR 323
Notify-Answer HSS MME NOA 323
Reset-Request HSS MME RSR 322
Reset-Answer MME HSS RSA 322

ESM = HSS
 S6a Interface – diameter sctp
IMSI Initial Attach Procedure

MME HSS

AIR (Auth Info)

AIA

ULR (Update Location)

ULA

1) During the subscriber attach, MME sends the Authentication-Information-Request (AIR) message to
HSS.

1) HSS analyzes the IMSI A4key/OP information and if it matches, it sends the Authentication-
Information-Answer (AIA) message back to MME.

1) After authenticating, MME sends the User-Location-Request (ULR) message to HSS.

1) HSS changes the search for IMSI table, change its status from UNKNOWN to LOCATED, stores the
MME Address and send the User-Location-Answer (ULA) back to MME.
 S6a Interface – diameter sctp
IMSI Detach Procedure

HSS MME Operator

Ldap delete IMSI

CLR (Cancel Loc)

CLA

1) The Operator deletes an attached IMSI in HSS database

1) The HSS sends the Cancel-Location-Request (CLR) message to MME

1) The MME disconnects the IMSI and sends the Cancel-Location-Answer (CLA) message
back to HSS
 S6a Interface – diameter sctp
Insert Subscriber Data Procedure

HSS MME Operator

Ldap Modify

IDR (Insert Subscriber Data)

IDA

1) The Operator modifies the profile of an attached IMSI in HSS database.

1) The HSS sends the Insert-SubscriberData-Request (IDR) message to MME

1) The MME updates the IMSI profile and sends the Insert-SubscriberData-Answer (IDA)
message back to HSS
Configuration
USER interface: TSP Node
Management Toolbox

Includes user interfaces for

Inventory, Upgrades,
Backups and platform
specific configuration tasks

Is used to perform CSCF,

HSS and SLF Configuration
Management
 JXplorer – Opening LDAP Connection

TSP application VIP

address

Name of the application for

the connection

Preconfigured unique
name of the node

User Name
 CM Browser JXplorer: View for EPC HSS
Connect/disconnect to/from Directory System Agent

Tree view Entry Data

JXplorer’s Table Editor: View for EPC HSS
Login to the HSS_ESM application
ESM Configuration Object Class
Model
 Configuration

ESM Node Configuration

HSS_ESM Node Configuration

See also CPI “ESM LDAP Interface Description”

ESM Configuration Parameters

See also CPI “ESM LDAP Interface Description”

 Configuration

ESM Service Configuration

ESM APNs

See also CPI “ESM LDAP Interface Description”

ESM Contexts

See also CPI “ESM LDAP Interface Description”

ESM Profiles

See also CPI “ESM LDAP Interface Description”

ESM PLMNs

See also CPI “ESM LDAP Interface Description”

Configuration Management

ESM Provisioned Data

ESM Provisioning Object Class Model
ESM Subscription Data

See also CPI “ESM LDAP Interface Description”

ESM User Data
Integration
Login to the DIA application
 S6a Diameter Interface – Own Node

CPI: Diameter Parameter List

 S6a Diameter Interface – Peer Node

CPI: Diameter Parameter List

 S6a Diameter Interface – Connection

CPI: Diameter Parameter List

S6a Diameter Interface – Routing

CPI: Diameter Parameter List

Troubleshooting
TELORB Manager

Backup Handling
 HSS Backup
DBN and IO Processor
DBN Backup
Backup

TSP HSS CONFIG

DATA

co-located TSP
External Backup
applications Media

OS

IO-Filesystem

CONFIG Configuration data and software of the node

DBN: The TSP Cluster Data Base
DATA Dynamic data for subscribers, services etc.
 HSS Backup
Considerations
Backup Interval Daily : DBN backup using scheduled backup.
Weekly : IO processor backup to central backup media
using scheduled backup.
Amount of DBN data The amount of data differ between operators since it is
dependent on site data like amount of users, used
features, and so on. The values must be calculated for
each site.
Example:
HSS application: 4.2 MB.
User data: For 500k users: 467 MB. The user data is
compressed in the backup and the level of compression
depends on data size (the compression factor is
estimated to be 10)
Data consistency The backup must be synchronized with other nodes.

Service impact Small.

How to perform manual DBN
backup

See also CPI “Backup and Restore User Guide”

DBN Backup Notification

See also CPI “Backup and Restore User Guide”

DBN Backup Verification

See also CPI “Backup and Restore User Guide”

Periodic Scheduled DBN Backup - configuring
the scheduler

See also CPI “Backup and Restore User Guide”

Periodic Scheduled DBN Backup – enabling the
scheduler

See also CPI “Backup and Restore User Guide”

IO Backup – configuring the
archiver

See also CPI “Backup and Restore User Guide”

IO Backup – starting the
archiver

See also CPI “Backup and Restore User Guide”

IO Backup – archiving in
progress

See also CPI “Backup and Restore User Guide”

IO Backup Verification (2/2)

See also CPI “Backup and Restore User Guide”

 HSS Restore
DBN and IO Processor
DBN Restore
Restore

TSP HSS CONFIG

DATA

co-located TSP
External Backup
applications Media

OS

IO-Filesystem

CONFIG Configuration data and software of the node

DBN: The TSP Cluster Data Base
DATA Dynamic data for subscribers, services etc.
DBN Restore – Backup
”activation”

See also CPI “Backup and Restore User Guide”

DBN Restore – Zone Reload

See also CPI “Backup and Restore User Guide”

 IO Processors Restore
In the case of a single IO crash the OPI ”Replacing IO
Processor” should be followed. No IO Backup is then
needed to restore a single IO. IO1 can be restored
from IO2 and vice versa.

In the case of simultaneous IO crashes the OPI

”Restoring IO from an Archive Server” (or ”Restoring
IO from Tape”) is to be followed. Both IOs are
restored from a backup. The procedure involves a
zone reload.
Performing health
check in HSS
 BENEFITS
Health checks are an important part
of preventive maintenance

Reduce the risk of system failures

and their consequences

Preparation for system interventions

Creates a professional approach

 zone state

2
1

3
ALARMS
 ALARMS - Generic concepts
An alarm is a message which informs the user that an event has taken place
which is categorized as a “fault”.

An alarm requires intervention from the administrator!

Automatically Automatically
Detected and Detected and
Automatically Manually Cleared
There are two types of faults: Cleared (ADAC) (ADMC)
 LISTING ALARMS
Listing alarms in HSS can be done through:

Node Management Toolbox (Graphical User Interface)

TelORB shell (Command Line Interface)

Proc_m0_s13$ telnet <1st LOADER Processor> 8000

$ /> cd CLI/AlarmsAndNotifications/
$ /CLI/AlarmsAndNotifications> printalarms
Alarm Viewer – Alarm
Information

By clicking on the magnifying

lens, it is possible to find
additional info on the alarm
Alarm Viewer – Event HELP

The relevant alarm OPI

is displayed in a
separate browser
 Alarm Viewer –
Acknowledgment

This icon indicates that a

new alarm has been
raised.

› Click on the icon in order to

acknowledge the alarm. The
icon will change to the
acknowledged alarm icon.
Alarm Viewer – Severity

WARNING › The severity level

MINOR specifies how urgently
MAJOR the intervention is
CRITICAL needed.
INDETERMINATE
 Alarm Viewer – Type

COMMUNICATIONS
› The type of alarm is
QUALITY OF SERVICE
according to ITU-T
PROCESSING ERROR
Recommendation
EQUIPMENT
X.733, Alarm Reporting ENVIRONMENTAL
Function.
Alarm Viewer – Object Type

› Object Type represents a

class name reflecting the
object that triggered the
alarm
Alarm Viewer – Instance

› Identifier for the managed

object that triggered the
alarm. The device, resource,
file, functionality or smallest
replaceable unit
Alarm Viewer – FAULT ID

› Identifies the alarm

within the Object Type
and the Instance.
Alarm Viewer – CAUSE

› Provides a tag for

the problem that
caused the alarm
Alarm handling
 Types of alarms
Application specific Traffic or
issues communication
issues
HSS alarms are related
to:

Node Application External

Management Interfaces Communication

TelORB Clusterware
TSP Clusterware
TSP software failures O&M
DICOS LINUX

NSP
TSP Hardware
Hardware

Hardware issues

TSP
 Main Hardware related
alarms
Failure on power A1
Fan Unit, Power Failure
Fan unit 1: Temperature > 65*C
Hardware configuration is changed
HDD fault detected
Processor Board, Power Failure
Processor Board, Temperature Threshold Crossed
Processor Disabled
Switch Board, Power Failure
Switch Board, Temperature Threshold Crossed
 Main TSP Software and
communication related
alarms
› DBN Database, Scheduled Backup Failed
› DBN Database, Scheduled Backup Archiving Failed
› DBN Disk Logged Data not Accessible
› DBN Disk Log Incomplete
› Diameter, Link Disabled
› Diameter, Link Failure
› Diameter, Own Node Disabled
› Diameter, Peer Node Disabled
› Disk Storage Shortage
› File Transfer Utility, Outgoing File Transfer Not Successful
› IO, Scheduled Archiving Failed
› License Management, Connection Lost with Primary License Server
› Maximum backup interval exceeded
› Memory Usage Limit Exceeded
› Zone Reloaded From Backup
 APPLICATIONS specific
alarms
ESM related:

Installation, Application Failed to Start in ESM

Administrative State, Shutting down in Progress for ESM
Administrative State, Manually Locking for ESM
Performance, TotalNumberOfEpsUsersStored in ESM
AVG related:
› Installation, Application Failed to Start in AVG
 The alarm Log
After an alarm is cleared, a relevant log is created in:

/opt/mirror/tsp/applog/applog.Alarm.*

The log contains info to identify the alarm, the severity, the probable cause, etc.

Please refer to document “Fault Management User Guide”, section 3 (The Alarm Log)
for a detailed description of each field.

Info about the acknowledgement time (ackTime) and the ID of the user who acknowledged
the alarm (ackUserId) is also logged.

The alarm log database can also be seen by using the Log Query Tool.

See slides related to Log Query Tool for more info

Notifications
 NOTIFICATIONS - Generic
concepts
Notifications are generated to report particular events of network
entities, containing information about how far a given operation
has progressed and whether it has succeeded or failed.

Notifications do not require intervention from the user

 LISTING notifications
Listing notifications in HSS can be done through:
Node Management Toolbox (Graphical User Interface)

TelORB shell (Command Line Interface)

Proc_m0_s13$ telnet <1st LOADER Processor> 8000

$ /> cd CLI/AlarmsAndNotifications/
$ /CLI/AlarmsAndNotifications> printnotifications
 Notification Viewer –
Notification Information

By clicking on the
magnifying glass, it is
possible to find
additional info on the
notification
Notification Viewer – Event
HELP

The relevant notification OPI is displayed in a separate browser

 The Notification Log
Whenever a notification is issued, a relevant log is created in:

/opt/mirror/tsp/applog/applog.Notification.*

The log contains info to identify the notification:

objectType; eventTime; attributeList; notificationType; notificationId;

instance

The notification log database can also be seen by using the Log Query Tool.

See slides related to Log Query Tool for more info

 APPLICATION LOGS
Alarms and Notifications logs are part of the “Application Logs”

Application logs are stored in the following folder:

/opt/mirror/tsp/applog/

Relevant logs subgroups in a typical HSS deployment for EPC:

Alarm
Notification
CMF (JIM could also be found for legacy support)
FTU
OAM_Avg_Log_Message
OAM_Esm_Log_Message
Security_Avg_Log_Message
Security_Esm_Log_Message
Services_Avg_Log_Message
Services_Esm_Log_Message
 Activation of ESM logs
In order to enable ESM related logs, set the following
parameters to TRUE:
HSS-EsmOAMLogStatus
HSS-EsmServicesLogStatus
HSS-EsmSecurityAuditLogStatus
 Activation of AVG logs
In order to enable AVG related logs, set the following
parameters to TRUE:
HSS-AvgOAMLogStatus
HSS-AvgServicesLogStatus
HSS-AvgSecurityAuditLogStatus (not showed in the picture below)
 The Logging Query Tool
› Application Logs can easily be viewed using the Log Query tool

See also CPI “Logging Query Tool User Guide”

 Database Selection

See also CPI “Logging Query Tool User Guide”

Select Application

Note: only some of the

entries are relevant for an
HSS deployment for EPC
Set search criteria
 Logging configuration
Logging configuration is defined in the following file:

/opt/telorb/axe/loadingGroup01_1/mirrored/config/NM/logging/config/logging.conf

The following parameters are configurable:

Number of days the log will be stored before archiving

Time of the day to archive
Debug level
Default max result
TriggerOfTheLongTableSize (alternative to Number of days and Time of day parameters; check
CPI document Logging User Guide)
 Logging configuration file
example
Here comes an example of the configuration file:
# VIP
LoggingHost platform-vip
LoggingDatabase logging
LoggingDatabaseBackup backup
LoggingDBUserName mysql
LogggingDBPassword mysql
LogDirectory /data/applog
DataDirectory /data/NM/Logging/data
##LoggingArchiver
#nb of the days the log message will be last in database
nbOfDaysBeforeArchive 4
#The time archiving will be executed
HourTimeArchive 00
MinuteTimeArchive 00
## LoggingDBWriter
#The sleeptime the LoggingDBWriter reread the ApplogClient files in ms
LoggingDBWriterSleepTime 1000
#The amount of bytes read in one period.
BufferSize 16384
#The value is between 0 and 9
DebugLevel 0
## QueryTool
#Default row displayed on each search result pages
DefaultMaxResults 5
Different types of Error Logs
The error logs used for trouble-shooting in a TSP cluster are:

Linux “syslog”
DicosSyslog
DicosApplog
Console logs

The only use for the error logs is for trouble-shooting by Ericsson service
personnel.

The logs are stored as files on the IO machines

Where you can find error
logs
Type of log Contents of the log file Location on the IO
Standard Linux system logs. The
syslogs from the Traffic Processors
Linux system log,
are merged together in the IO. Syslog /var/log/messages
syslog
is compressed and archived every
day.

Dicos system log, /opt/telorb/axe/tsp/

This log is used by the TSP platform
DicosSyslog syslog

Dicos application log, /opt/telorb/axe/tsp/

This log is used by the applications
DicosApplog applog.default

Traffic processors’ The data stream from each processor /opt/telorb/axe/tsp/

console logs, is dumped into size-limited console log consolelogs
Proc_mX_sX files.
 Error dumps
If there is a crash or a failure in a processor or a process, error dump files are
generated. These error dump files make it easier to locate the reason for the
failure.

Beside the error dump files, notifications are also generated.

If a processor crashes, the notification Processor Reload
Started is issued
If a process crashes, the notification Capsule Abortion is
issued

Whatever caused the error dump may well have resulted in alarms and notifications
in addition.

An error dump will be stored for 30 days before it is removed

 crashcollectors
Dump files are collected, compressed and stored in Crashcollector files with format:

Crashcollector_<DATETIME>_<PROCESSOR>.tar.gz

Where:
- DATETIME is the date and time of the creation of the file
- PROCESSOR is the name of the IO that writes the collector to disk

A Crashcollector file contains dump files, error logs and system configuration. Examples of such data
are:
Error dump files
Linux and Dicos syslogs
Processors configuration data (kernel and boot load table)

If you cannot see what has caused the dump, you should send the crashcollector files to the next level

of support for analysis.

 LOCATION of dumps and
Crashcollectors
Type of info Contents Location in the IO

Error Dumps Error dump files are generated If /var/log/dumps

Ex: DicosCapsuleText.. there is a crash or a failure in a
..Dump.172.16.0.9-1 processor or a process.
Crashcollector, Due to the creation of error dump /opt/telorb/axe/tsp/
crashcollector_<date>_ the following files are collected crashcollector/
<time>.. and “tarred” into the
.._Proc_mX_sX.tar.gz crashcollector file: error dump(s),
syslog, traffic processors’ console
logs and traffic processors’ kernel
configuration.
ALARM examples
How to clear some alarms

1. Diameter, Own Node Disabled

2. Maximum Backup Interval Exceeded

3. Zone Reloaded From Backup

4. Administrative State, Manually Locking for ESM

 ALARM 1

1. Diameter, Own Node Disabled

› To clear the alarm:
– Connect to the DIA application using JXplorer
– In the HSS_ESM container, go to DIA-CFG-OwnNodeConfig Object Class
– Change the attribute “enabled” to TRUE
 ALARM 2

2. Maximum Backup Interval Exceeded

› To clear the alarm:

– On TelORB Manager, go to
Scheduler tab
– Schedule backups with less
than 8 hours of difference
 ALARM 3

3. Zone Reloaded From Backup

› To clear the alarm:

– On TelORB Manager, go to
Processors tab
– Click on Clear Zone Reload
Alarm
 ALARM 4

4. Administrative State, Manually Locking for ESM

› To clear the alarm:
– Connect to the HSS_ESM application using JXplorer
– Go to HSS-EsmConfigurationData Object Class
– Change the attribute “HSS-EsmAdministrativeState” to Unlocked
 Network
Redundancy
 network redundancy
If the node is configured with Geographical Network Redundancy, follow the steps to check
the status:

1. Start the Redundancy GUI by clicking on its label in the leftmost browser pane of
the Node Management Toolbox.
2. Check if the TelORB Mode of both zones is Netshared.
3. Check if the TelORB State is InUse for the zone with Primary ZoneStatus.
4. Check if the TelORB State is Ready for the zone with Standby ZoneStatus.
IO synchronization
 IO synchronization
Execute the following command on any of the IO processors:
cat /proc/drbd
The synchronization is not completed if the printout includes a progress-bar. If this is the case,
then an estimated time until completion (finish) is also included in the printout. Wait this
period and try again. Expected result:
• cs (connection state) is Connected;
• st (state) is Primary/Secondary on the primary IO and Secondary/Primary on
the secondary IO;
Software version
 TSP software version
To determine the TSP SW version:
• Compare the IDP versions listed in the Inventory tab of TelORB Manager to the ones listed in the
latest TSP release note. Note: To speed up IDP version check, select the IDPs that most often change,
like Dicos or VipDicos.
In the TSP release note for TSP6101:

In the TSP release note for TSP6110: