arq egsdp. - nº egsdp architecture inteligent mobile network platform january 2009

. - ‹Nº›

EGSDP ARCHITECTURE

Inteligent Mobile Network Platform

January 2009

. - ‹Nº›

Model of ComponentsModel of Components

ArchitectureArchitecture

Data ModelData Model

MiscellaneousMiscellaneous

StatisticsStatistics

. - ‹Nº›

GENERIC CONFIGURATION 3N

BEBD11 BEBD1n BEBD21 BEBD2n

CLUSTER1 CLUSTER 2

FES1 FESn FED1 FEDn

Double Internal LAN

EGSDP MT (Management Terminal)

External simple Lan

BELS1 BELSn

. - ‹Nº›

GENERIC CONFIGURATION 3N (II)

CLSBD1 CLSBD2

FES1 FESn FED1 FEDn

Double Internal LAN

Simple external LAN

EGSDP MT (Management Terminal)

BEBD11 BEBD1n BEBD21 BEBD2n BELS1 BELSnER1

ERnCLSBD1 CLSBD2

FES1 FESn FED1 FEDn

Double Internal LAN

Simple external LAN

BEBD11 BEBD1n BEBD21 BEBD2n BELS1 BELSn

. - ‹Nº›

3N CONFIGURATION OF PRODUCTION

Vicalvaromvic1deg1

SDPES02mcon*

CONTR01mvic*

CONTR02mcon*

CORP02mcon*

SDPES01mvic*

CLSLS-SDPES01

CLSBD1-SDPES01

CLSBD2-SDPES01

CLSFED-SDPES01

CLSFES-SDPES01

. - ‹Nº›

3N CONFIGURATION OF PRODUCTION (II) SDPES01

mvic1dfes1_SDPES01....

CLSBD1-SDPES01

mvic1dbebd11_SDPES01

mvic1dbebd12_SDPES01mvic1dbebd13_SDPES01

mvic1dbels1_SDPES01

mvic1dbels2_SDPES01mvic1dbels3_SDPES01

mvic1dbels4_SDPES01

CLSLS-SDPES01

CLSFED-SDPES01

mvic1dfes1_SDPES01....

CLSFES-SDPES01

CLSBD2-SDPES01

mvic1dbebd21_SDPES01....

. - ‹Nº›

3N CONFIGURATION OF PRODUCTION (/etc/hosts) SDPES01

CLSBD1-SDPES01

mvic1dbels1_SDPES01

mvic1dbels2_SDPES01

mvic1dbels3_SDPES01

mvic1dbels4_SDPES01

CLSLS-SDPES01

CLSFES-SDPES01

mvic1dfes1_SDPES01

mvic1dfes2_SDPES01

mvic1dfes3_SDPES01

mvic1dfes4_SDPES01

CLSFED-SDPES01mvic1dfed1_SDPES01

mvic1dfed2_SDPES01

CONTR01

mvic1dbebd12_CONTR01

mvic1dbels1_CONTR01

mvic1dbels2_CONTR01

mvic1dbels3_CONTR01

mvic1dbels4_CONTR01

mvic1dfes1_CONTR01

mvic1dfes2_CONTR01

mvic1dfes3_CONTR01

mvic1dfes4_CONTR01

mvic1dfed1_CONTR01

mvic1dfed2_CONTR01

CLSBD1-CONTR01

CLSLS-CONTR01

CLSFES-CONTR01

CLSFED-CONTR01

mvic1dbebd11_CONTR0110.132.44.22310.132.44.22410.132.44.22510.132.44.226

10.132.44.23510.132.44.23610.132.44.23710.132.44.238

10.132.44.23910.132.44.243

10.132.44.23110.132.44.23210.132.44.23310.132.44.234

. - ‹Nº›

3N CONFIGURATION OF PRODUCTION (SNMP)

SDPES01

CONTR01

4500 -Listener port ASNMP ( Boot agent and A3_HOSTS): ONE FOR ENVIROMENT

SDPES02 4503

CONTR02 4504

CORP02 4505

-Traps listener port (demuxtraps.cnf y snmpd.cnf): UNIQUE 4501

-An EGSDP listens traps from different ASNMP of the same machine (multi-enviromment)• Every ASNMP informs of its logical name of machine<machine_enviroment>snmpd.cnf:trapsink mvic1deg1 ASNMP-SDP-trap:mvic1dbels1_SDPES014501

. - ‹Nº›

Service 1Service 1

SVSDPSVSDP

D0 ProcessCel 2

D1 ProcessCel 2

Proceso D1Cel 2

B0 ProcessCel 2

SVSDPSVSDP

D0 ProcessCel 1

D1 ProcessCel 1

D2 ProcessCel 1

Process B0Cel 1

A0 ProcessCel 0

SVSORSERVICESVSOR

SERVICE

Service 2Service 2

SVSDPSVSDP

D0 ProcessCel 1

D1 ProcessCel 1

D2 ProcessCel 1

Proceso B0Cel 1

A0 ProcessCel 0

SVSORSERVICESVSOR

SERVICE

Proceso F0Cel 0

SVSDPSVSDP

D0 ProcessCel 2

D1 ProcessCel 2

D2 ProcessCel 2

Proceso B0Cel 2

SVSDPSVSDP

D0 ProcessCel 3

D1 ProcessCel 3

D2 ProcessCel 3

Proceso B0Cel 3

cellcell cel2cel2 cel3cel3

cellcell cel2cel2

SUPERVISOR PLATFORM

serv 0

SUPERVISOR PLATFORM

serv 0

GEVENTOScel 0

ASNMPcel 0

PINGEGcel 0

TESTIPcel 0

CONSCRIPTScel 0

Service 0 (PLAT)Cell = 0

FuncSVSDP–Instance = 0

FuncGEVENTOS–Instance = 0

FuncASNMP–Instance = 0

…..Service 1 (PREP)

Cell 0Func SVSERV

–Instance = 0FuncA

–Instance = 0Cell 1

Func SVCSERV–Instance = 0

Func B–Instance = 0

Func D–Instance = 0–Instance = 1–Instance = 2

MODEL OF COMPONENTS

. - ‹Nº›

MODEL OF COMPONENTS

. - ‹Nº›

MODEL OF COMPONENTS

NETWORK ELEMENT: CLUSTER

HOST PLATFORM SERVICE A SERVICE

– CELL» FUNCTIONALITY

INSTANCE (process)

B SERVICE

MANAGEMENT ELEMENT Manager

. - ‹Nº›

DEMUXTRAPS

PRIMARY MANAGERS

GALARGMOD

GTRAPSGCONFGOPER

PROGCOMANDOS

BE1 BE2ASNMP ASNMP

G. INTERNOS

SVISOR

EGSDP ARCHITECTURE

INSTALLER

MANAGERSSUN

MANAGERSNEWNET

. - ‹Nº›

DEMUXTRAPS

PRIMARY MANAGERS

GALARGMOD

GTRAPSGCONFGOPER

PROGCOMANDOS

BE1 BE2ASNMP ASNMP

G. INTERNOS

SVISOR

INSTALADOR

MANAGERSSUN

MANAGERSNEWNET

EGSDP ARCHITECTURE

. - ‹Nº›

EGSDP ARCHITECTURE

DEMUXTRAPS

PRIMARY MANAGERS

GALARGMOD

GTRAPSGCONFGOPER

PROGCOMANDOS

BE1 BE2ASNMP ASNMP

G. INTERNOS

SVISOR

INSTALADOR

MANAGERSSUN

MANAGERSNEWNET

. - ‹Nº›

EGSDP ARCHITECTURE

DEMUXTRAPS

PRIMARY MANAGERS

GALARGMOD

GTRAPSGCONFGOPER

PROGCOMANDOS

BE1 BE2ASNMP ASNMP

G. INTERNOS

SVISOR

INSTALADOR

MANAGERSSUN

MANAGERSNEWNET

. - ‹Nº›

EGSDP ARCHITECTURE

Manager(java)

ActionServlet

Browser Web Server Server ofbusiness

JSP Page

Action

ActionServlet

Beans:Presentation

LogicBusiness

View, Controller Model

. - ‹Nº›

Communication Primary Managers - ASNMPEvents

CommandsConfiguration.

DEMUXTRAPS

PRIMARY MANAGERS

GTRAPSGCONFGOPER

BE1 BE2ASNMP ASNMP

. - ‹Nº›

Communication of Primary - GMOD-GALAR Managers

PRIMARY MANAGERS

GALARGMOD

GTRAPSGCONFGOPER

EventosCommandsConfiguration.

. - ‹Nº›

GMOD-GSEG-IGUS CommunicationEventosCommandsConfiguration.

PC IGUS PC IGUS

Connection

. - ‹Nº›

Alarms Generation

DEMUXTRAPS

PRIMARY MANAGERS

GALARGMOD

GTRAPSGCONFGOPER

PROGCOMANDOS

G. INTERNOS

DEFENSE

TrapsSucesos o Cambios de PropiedadAlarms:

Traps come from ASNMP agents of the NetworkElements machines.

The Traps Manager asks at the GCONF the translation of the SNMP identifier to an identifier of the model, andwith this identifier an event or change of propertyde Propiedad, dependiendo del tipo de trap recibido.

The Model Manager receives the event and it is sent toThe Alarms Manager. In addition, in case of receive aa Change of Property, it updates in the model the propertythat has changed in the component associated to the event

When the event arrives to the Alarms Manager, the necessary inference may occur, which could provoke the generation of new alarms as well as the stoppable of the others exiting already.The alarms and stoppable of alarms areenviados hacia el GSEG

When the alarms arrive to the Segurity Manager, they will be resend to each of the clients connected atthat moment (Web server). Previosly a filter of alarms is realized.Depending on the profile of each connected operator

Each web client receives the alarms and post them or not into the panelof Alarms ( Except if it exists a filter that conceals it)The Web interface periodically queries the web server The alarms

. - ‹Nº›

Alarms (instances) They belong to a Type of Alarm Each instance of alarm has a text associated The instance of alarm is associated to a model component Depending on the personal profile, which can be modified by the own

operator, can decide what alarms will be displayed into the panels. They are stored in history in a BBDD. It is allowed to the operators to delete them. Correlation and commentaries. They are automatically deleted after a configurable range. It is allow for an operator to recognize them, indicating that the operator is

taking charge solving the condition of alarm If it is possible to stop the type of alarm to which the instance belongs, it will

automatically be stopped when an event indicating the stop condition of the alarm is received

Tendency of Alarm

. - ‹Nº›

Commands Execution

DEMUXTRAPS

PRIMARY MANAGERS

GALARGMOD

GTRAPSGCONFGOPER

PROGCOMANDOS

G. INTERNOS

DEFENSE

CommandsSet SNMPTraps

The trap is received in the traps Demultiplexerof Traps

The Traps Manager checks the trap response, and sends it to the GOPERGOPER

The Manager Model does a specific processing of command which will send one ormore commands towards the group of managers.

When the response arrives to the Model of manager, it is resendtowards the GSEG, and if necessary, new subcommands may be sentto the GOPER, it will wait againto receive a response

The command is given an unique identifier in the Security Manager. and it generates an entry to the log of commands.

In a Web client the operator executes a commandon a Network Element component. Thiscommand is sent directly to the GSEG

The component on which runs the command is blocked in the Operations Manager and after a petition of translation to the GCONF, a SNMP operation is run over the SNMP agent of the implied machine

The SNMP agent sends the command to the right process of the Network Element, which will generate a response after the execution of the command, and willresend it to the SNMP agent which will generate a responsetrap towards the Management Element

The Operations Manager checks that the responsereceived is associated to a current command. If this is the case,it unblocks the associated component to the command andresends the response to the GMOD

The Segurity manager sends the response to the client that executes the command and updates in the commands log therelated information of the execution of the command.

The Web client receives the response and shows it to the operator

Answers

. - ‹Nº›

Platform Process

DEMUXTRAPS

PRIMARY MANAGERS

GALARGMOD

GTRAPSGCONFGOPER

PROGCOMANDOS

G. INTERNOS

SVISOR

INSTALADOR

MANAGERSSUN

MANAGERSNEWNET

GEVENTOS

EPINGEGTESTIP

GESTAD

GESTADJ

SESTAD

. - ‹Nº›

Monitorization of the Connections

DEMUXTRAPS

PRIMARY MANAGERS

GALARGMOD

GTRAPSGCONFGOPER

PROGCOMANDOS

G. INTERNOS

DEFENSE The TESTIP does periodically a ping to each machine of the Network Element

When the alarms arrive to the Security Manager, they will be resend to each of the clients connected atthat moment, having fulfilled previously a filtered of alarms depending on the profile of each connected operator

Each web client receives the alarms and posts them into the panel alarms.

GEVENTOS

EPINGEG

TESTIP

HOST1 Enviroment 01

HOST Enviroment ‘2

HOST n

In this case the ping was lost because the TESTIP process died (the platform stopped), the conection was lost or because the machine crashed.

When the time-out runs the TESTIP sendsan event towards the GEVENTOS, it informs the name of the machinethat is non-accessible

When the event arrives to the Alarm manager, the necessary inference may occur, which could provoke the generation of new alarms as well as the stop of the others exiting already.The alarms and the stop of alarms aresent towards the GSEG

The event arrives to GTRAPS and turns it into a Change of Property, that is send towards the GMOD, that willgenerate an alarm by the regular procedure. TheChange of Property is generated on the corresponding componentto the machine that doesn´t give a response

. - ‹Nº›

Administration (Types of Components)

. - ‹Nº›

Administration (Services)

AL_PASSSERVICIOS

AL_PASSSERVICIOS AL_A7_NUTNSNAMEAL_CDUSUARIOAL_CDPASSWORD

FK_AL_A0

A7_TNSNAMES

A7_NUTNSNAMEA7_CDNOMBREA7_A6_NUAGRUPACIONA7_CDUSUARIOA7_CDPASSWORD

FK_AL_A7

. - ‹Nº›

Administration (Functionalities )

. - ‹Nº›

Administration (Tasks )

AA_CDAYUDAAA_CDAYUDAAA_CDPARAM

. - ‹Nº›

Types of Alarms

It is necessary to differentiate between Alarms (instances) and Types of Alarms

It is identified by code and service They have associated a category and a type

Stoppable and non-Stoppable The instances are displayed in different panels. The Stoppable are eliminated when some events indicate the elimination of

the condition that produced the alarm. The Non-Stoppable won´t be eliminated when an event arrives.

They are filtered depending on the profile of the operator.

. - ‹Nº›

Types of Alarm

. - ‹Nº›

Group of Alarms

. - ‹Nº›

Actions to Perform in the Event of an Alarm

. - ‹Nº›

History of alarms

. - ‹Nº›

Commands History

. - ‹Nº›

Users and Profiles

A profile is associated to a user. This profile defines the permissions that possesses all the users belonging to this profile.

Four predefined profiles exist by installation: maintenance, statistics, operation and operation by query.

The profiles allow to filter the information received by the users. Filtering is realized by:

Components - Several types of components are filtered. Tasks - Some tasks may be filtered. The operator doesn´t have the

option to execute them. Alarms - Certain types of alarms are filtered

These filters are realized through the views of the alarm tables, components and tasks.

. - ‹Nº›

Users and Profiles

. - ‹Nº›

Users:

. - ‹Nº›

Profiles:

. - ‹Nº›

Table Views

. - ‹Nº›

Time Restrictions

. - ‹Nº›

EG FORMS

. - ‹Nº›

ER FORMS

DBConection Manager

. - ‹Nº›

ESTRUCTURE OF DIRECTORIES

b carg a /B a se de C a rga

d a to s/D ire c to rio s de e jecu c ion

d e los p roce sos

b in /E je cu ta b les

tra za s/D ire c to rio d e T ra zas

h tm l/D ire c to rio de h tm l

cg i/D ire c to rio d e cg i's

lib /C la ses ja va

sc rip ts /S c rip ts d e a ccio n es

a n te a la rm as

ve rs ion e sB DS crip ts d e b a se de da tos

$ E G S D P _ P A H TD ire c to rio p rin c ip a l

d e fe c to :/expo rt/e gsdpp a is:/e xp o rt/P A IS /eg sdp

. - ‹Nº›

Bin Directory

S E R V IC IO _ P L A T A F O R M A /

b in /D ire c to rio s de e jecu c ión

. - ‹Nº›

bcarga Directory

co m u n/

d e m u x tra p s/

g a la r/

g e sta d /

g id s/

g m o d/

g id s/

g m o d/

g seg /

in s ta la d o r/

in te rn o /

n e w n e t/

p rim a rio s/

su n /

E P IN G E G /

G E S T A D _ E G /

G E V E N T O S /

S E R V IC IO _ P L A T A F O R M A /

S E S T A D _ E G /

S E S T A D _ E G _ B E /

S E S T A D _E G _ F E D /

S E S T A D _ E G _ F E S /

T E S T IP /

b carg a /B a se de C a rga

(F ich ero s de C o nfig u ra c ió n)

. - ‹Nº›

SERVICIO_PLATAFORMA_HJ.cnf

It is found in $EGSDP_PATH/bcarga/SERVICIO_PLATAFORMA/ Indicates the processes that are launched when the supervisor is

launched , specifying all the launch parameters. The bin directory indicates too, the order in which they should launch

and the timeout between the processes.

. - ‹Nº›

EPINGEG_HOSTS.cnf

It is found in $EGSDP_PATH/bcarga/SERVICIO_PLATAFORMA/ It indicates the machines of the Network Element whose connection

state to the Management Element will be monitored One machine for each line of the file, using always the name to which

is known each environment in the EG. The IP is not used. Besides the name, it indicates the port to relate the information from the TESTIP that informs for the IP+Port.

. - ‹Nº›

IPs.cnf

It is found in $EGSDP_PATH/bcarga/SERVICIO_PLATAFORMA/ It indicates the machines of the Network Element whose connection

state to the Management Element will be monitored It has to be include the Management Element

From the EG point of view, there is one machine for each line of file, it´s to say, one environment for each line. Each environment is defined as IP+Port...

. - ‹Nº›

Managers of Configuration (I)

$EGSDP_PATH /bcarga/gseg/gseg.cnf gseg.acceso.maxaccesoserroneos=3 gseg.acceso.intervalobloqueo=24 // Time to unblock gseg.numeromaxsesiones=100 // Total number of sessions (all the users) puerto.firewall=3027

$EGSDP_PATH /bcarga/gmod/gmod.cnf gmod.nombre.sdp=SDP

$EGSDP_PATH /bcarga/galar/galar.cnf galar.max.num.alarmas=1000 galar.max.num.alarmas.componente=20 galar.num.alarmas.componente.borrar=10 galar.intervalo.borrado.temporizado.alarmas=600000

. - ‹Nº›

Managers of Configuration (II)

$EGSDP_PATH /bcarga/primarios/primarios.cnf administradores.primarios.goper.timeout.comando=540

$EGSDP_PATH /html/gestion.html min.puerto.firewall=3000 max.puerto.firewall=4000

. - ‹Nº›

REREADING

Forms modify the forms tables (Tablas _F) The processes read the process tables (without suffix) There are some backups tables to fall back the operation of rereading

(tablas_B) in case of failure. The copy of data from some tables to others is realized by a stored

procedure called rereading procedure The Management Element arranges the copy of data between tables

and later to the affected processes that read again the information from the processes tables.

. - ‹Nº›

REREADING

TABLA_F TABLE TABLA_B

REREADING FALL BACK

. - ‹Nº›

REREADING

Rereading Form

. - ‹Nº›

AUTOMATIC PROVISION

It allows to fill the tables of the service from files in a (txt o xml) format. It improves the changes and minimizes the human mistakes that an

operator can introduce when introducing changes in the forms It allows to do changes in a way that if one change fails it doens´t

allow to do the rest. In the file is defined the inserts, modifications or deletes of the records

for each of the tables_F. The command checks the file and validates the changes that have to

be done. If everything is fine it applicates the changes in the tables. As with the forms, in order to work it is necessary to do a later

rereading.

. - ‹Nº›

AUTOMATIC PROVISION

. - ‹Nº›

FEDs BEs AESTAD AESTAD

SESTAD_BE

DBGESTAD

SESTAD_FED SESTAD_FES

FESs AESTAD

Web Server

PagesJSP

Architecture PC

. - ‹Nº›

Elementof Network AESTAD

Component N

Component 1

Files of Counters

----------------------------------------------------------------------------------------------------------------

SESTAD

Files of Counters

----------------------------------------------------------------------------------------------------------------

Transfering information to the Management Element

. - ‹Nº›

Insertion in the Database

GESTAD

Files of Counters

----------------------------------------------------------------------------------------------------------------

. - ‹Nº›

Acummulation in the Database

DBESTADESTAD_MESES

ESTAD_DIAS

ESTAD_HORAS

ESTAD_MINUTOS

GESTADJ

ACUM_ESTAD

ExecutionChecking

ESTADCONTMINUTOS

. - ‹Nº›

Information Access

DB ESTAD_MESES

ESTAD_DIAS

ESTAD_HORAS

ESTAD_MINUTOS

Web Server

PagesJSP

. - ‹Nº›

Access to information (Selection)

. - ‹Nº›

Access to information (Report)

. - ‹Nº›

Data Model

. - ‹Nº›

File of configuration AESTAD.cnf-1GENERAL FILE OF CONFIGURATION TO THE STATISTICS AGENT OF CNTs..

# Number of componets of the service that generate counters.

# - ETIQUETA_COMPO_x.

# ID of component x ( Functionality in text)

# - PARAMETRO_COMPO_x.

# Parameter of component x, it indicates the action to realize with the files of the component. Values:

# copy - copy the files in the remote machine, if they exist already, it deletes them. Option by default.

# concat - it concatenates the file if it exists. If the file doesn´t exist, it will be created

# To any other value the default value will be used .

# It is mandatory to have a parameter for each component, if it is not the case, it will fail

# - MAQ_DESTINO

# The Management Element is the target machine of the counters files.

# - PATH_REMOTO.

# Remote machine Path. The path can be absolute or relative. The relative path is extracted from the $EXPORT_SDP_PATH varible. In a multi-enviroment, the path must be absolute because the root path of different machines may be different to the EG than to the default EG (/export/egsdp),

# - DIR_DATOS_LOCAL

# Initial directory of data in the local machine. (CNT)

. - ‹Nº›

File of configuration AESTAD.cnf-2# - SEGUNDOS_TRANSFERENCIA.

# Seconds to activathe the transference of files to the Management Element

# - NUM_INTENTOS_TRANSF.

# Attemptsnumber in the transference of files. In case of successive failures it is deleted

# - NOM_SESTAD.

# Name of the statistics server ( actually it can be SESTAD_EG_BE, SESTAD_EG_FED,

# SESTAD_EG_FES)

. - ‹Nº›

Directory Structure

NETWORK ELEMENT:

Data Directory for Counters:

/export/sdp/<nombre de servicio>/datos/CNT

Directories of components:

/export/sdp/<nombre de servicio>/datos/CNT/Componente 1

/export/sdp/<nombre de servicio>/datos/CNT/Componente 2

/export/sdp/<nombre de servicio>/datos/CNT/Componente N

. - ‹Nº›

Structure of directories

MANAGEMENT ELEMENT:

Data directory for counters:

$EGSDP_PATH/datos/CNT

Directories of components:$EGSDP_PATH/datos/CNT/<servicio><máquina1>/Componente 1...$EGSDP_PATH/datos/CNT/<servicio><máquina1>/Componente N

$EGSDP_PATH/datos/CNT/<servicio><máquinaN>/Componente 1...$EGSDP_PATH/datos/CNT/<servicio><máquinaN>/Componente N

. - ‹Nº›

File of configuration GESTADJ.cnf-1# GENERAL FILE OF CONFIGURATION TO THE STATISTICS AGENT OF CNTs.

# - NUM_COMPO.

# Number of the service components that generate counters.

# - COMPO_x.

# Component ID x.

# - NUM_MAQUINAS.

# Number of machines that generate counters.

# - MAQUI_x

# ID machine x. (name)

# - SEGUNDOS_INSERTABD

# Seconds between inserts in the database

# - BASE_DATOS.

# Name of the database to be configured.

# - USUARIO_BASE_DATOS.

# User of the database to be configurated.

# - PASSWORD_BASE_DATOS.

# Password of the database to be configurated.

# - SID

# SID of the statistics database.

. - ‹Nº›

File of configuration GESTADJ.cnf-2# - USUARIOBD.

# Database user of the statistics management element

# - PASSWDBD

# Database password of the statistics management element

. - ‹Nº›

File of configuration GESTADJ.cnf-1#------------------------------------# Threads wait between executions (in milliseconds)#initial minute for the execution#------------------------------------gestad.tiempo.espera=3600000 // 1 hourgestad.tiempo.espera.acumulador=360000 // 6 minutesgestad.tiempo.espera.gestion.particiones=86400000 // 24 hours

#Dimentions for the statistics tables#Maximum dimensions allowed for the statistics tablesgestad.numero.particiones.minutos=6gestad.numero.particiones.horas=7gestad.numero.particiones.meses=12gestad.numero.particiones.dias=14gestad.max.filas.estad=10000gestad.max.particiones.tabla.minutos=50 // alarmsgestad.max.particiones.tabla.horas=50gestad.max.particiones.tabla.dias=50gestad.max.particiones.tabla.meses=50gestad.min.particiones.tabla.minutos=2gestad.min.particiones.tabla.horas=2gestad.min.particiones.tabla.horas=2gestad.min.particiones.tabla.meses=2

. - ‹Nº›

File of configuration GESTADJ.cnf-2#directory of statistics files#Maximun number of files in the directory#------------------------------------gestad.directorio.ficheros= <egsdp_path>/datos/CNTgestad.max.ficheros.estad=1000

. - ‹Nº›

EGSDP ARCHITECTURE

Inteligent Mobile Network Platform

January 2009

arq egsdp. - nº egsdp architecture inteligent mobile network platform january 2009

arq egsdp

n service

sdpes01 mvic1dbels1

sdpes01 mvic1dbels2

sdpes01 mvic1dbebd14

sdpes01 mvic1dbels4

sdpes01 mvic1dbels3

sdpes01 mvic1dbebd12

Documents

rezultate fii inteligent cluj

sa actionam inteligent

edificios inteligent es expo

maketing inteligent

caietul inteligent 1-90

brochure inteligent movil hospitals

test very inteligent- hazlo

traieste sanatos, mananca inteligent

bebelusul inbebelusul inteligent

autovehiculele si controlul inteligent

inteligent load ils

27325347 design inteligent

optimismul inteligent preview304

managementul inteligent al informaȚiei

controlul inteligent

sistemul inteligent

an inteligent parking system

emotional inteligent leadership

inteligent pack

inteligent catalogue final