1 / 77

EGSDP ARCHITECTURE

This architecture model presents components for an intelligent mobile network platform. It includes data models, statistics, and configurations for a complex network setup.

dahlc
Download Presentation

EGSDP ARCHITECTURE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EGSDP ARCHITECTURE Inteligent Mobile Network Platform January 2009

  2. INDEX Model of Components Architecture Data Model Miscellaneous Statistics

  3. BEBD11 BEBD1n BEBD21 BEBD2n GENERIC CONFIGURATION 3N MT (Management Terminal) EGSDP External simple Lan BELS1 BELSn CLUSTER1 CLUSTER 2 Double Internal LAN FES1 FESn FED1 FEDn

  4. BELS1 BELS1 BELSn BELSn BEBD2n BEBD1n BEBD1n BEBD2n BEBD21 BEBD11 BEBD11 BEBD21 GENERIC CONFIGURATION 3N (II) Simple external LAN ER1 CLSBD1 CLSBD2 Double Internal LAN FES1 FESn FED1 FEDn EGSDP MT (Management Terminal) Simple external LAN ERn CLSBD1 CLSBD2 Double Internal LAN FES1 FESn FED1 FEDn

  5. 3N CONFIGURATION OF PRODUCTION Vicalvaro mvic1deg1 CONTR02 mcon* SDPES02 mcon* SDPES01 mvic* CLSBD1- SDPES01 CLSLS- SDPES01 CLSBD2- SDPES01 CORP02 mcon* CONTR01 mvic* CLSFED- SDPES01 CLSFES- SDPES01

  6. 3N CONFIGURATION OF PRODUCTION (II) SDPES01 CLSBD1-SDPES01 CLSLS-SDPES01 CLSBD2-SDPES01 mvic1dbebd11_SDPES01 mvic1dbels1_SDPES01 mvic1dbebd21_SDPES01 .... mvic1dbebd12_SDPES01 mvic1dbels2_SDPES01 mvic1dbebd13_SDPES01 mvic1dbels3_SDPES01 mvic1dbebd14_SDPES01 mvic1dbels4_SDPES01 CLSFES-SDPES01 CLSFED-SDPES01 mvic1dfes1_SDPES01 .... mvic1dfes1_SDPES01 ....

  7. 3N CONFIGURATION OF PRODUCTION (/etc/hosts) CONTR01 SDPES01 mvic1dbels1_CONTR01 mvic1dbels1_SDPES01 10.132.44.231 10.132.44.232 10.132.44.233 10.132.44.234 mvic1dbels2_CONTR01 mvic1dbels2_SDPES01 CLSLS-CONTR01 CLSLS-SDPES01 mvic1dbels3_CONTR01 mvic1dbels3_SDPES01 mvic1dbels4_CONTR01 mvic1dbels4_SDPES01 10.132.44.223 mvic1dbebd11_CONTR01 mvic1dbebd11_SDPES01 10.132.44.224 10.132.44.225 10.132.44.226 mvic1dbebd12_CONTR01 mvic1dbebd12_SDPES01 CLSBD1-CONTR01 CLSBD1-SDPES01 mvic1dbebd13_CONTR01 mvic1dbebd13_SDPES01 mvic1dbebd14_CONTR01 mvic1dbebd14_SDPES01 mvic1dfes1_CONTR01 mvic1dfes1_SDPES01 10.132.44.235 10.132.44.236 10.132.44.237 10.132.44.238 mvic1dfes2_CONTR01 mvic1dfes2_SDPES01 CLSFES-CONTR01 CLSFES-SDPES01 mvic1dfes3_CONTR01 mvic1dfes3_SDPES01 mvic1dfes4_CONTR01 mvic1dfes4_SDPES01 10.132.44.239 10.132.44.243 mvic1dfed1_CONTR01 mvic1dfed1_SDPES01 CLSFED-CONTR01 CLSFED-SDPES01 mvic1dfed2_CONTR01 mvic1dfed2_SDPES01

  8. 3N CONFIGURATION OF PRODUCTION (SNMP) -Listener port ASNMP ( Boot agent and A3_HOSTS): ONE FOR ENVIROMENT SDPES01 4501 CONTR01 4503 SDPES02 4504 CONTR02 4505 CORP02 4501 -Traps listener port (demuxtraps.cnf y snmpd.cnf): UNIQUE • -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

  9. INDEX Model of Components Architecture Data Model Miscellaneous Statistics

  10. Service 0 (PLAT) Cell = 0 FuncSVSDP Instance = 0 FuncGEVENTOS Instance = 0 FuncASNMP Instance = 0 ….. Service 1 (PREP) Cell 0 Func SVSERV Instance = 0 FuncA Instance = 0 Cell 1 Func SVCSERV Instance = 0 Func B Instance = 0 Func D Instance = 0 Instance = 1 Instance = 2 SUPERVISOR PLATFORM serv 0 Service 1 SVSOR SERVICE GEVENTOS cel 0 CONSCRIPTS cel 0 ASNMP cel 0 TESTIP cel 0 SVSDP cell cel2 SVSDP PINGEG cel 0 B0 Process Cel 2 Process B0 Cel 1 Service 2 SVSOR SERVICE Proceso D1 Cel 2 D0 Process Cel 2 D1 Process Cel 2 D2 Process Cel 1 D0 Process Cel 1 D1 Process Cel 1 SVSDP SVSDP SVSDP Proceso B0 Cel 1 Proceso B0 Cel 2 Proceso B0 Cel 3 A0 Process Cel 0 D2 Process Cel 1 D2 Process Cel 2 D2 Process Cel 3 D0 Process Cel 1 D1 Process Cel 1 D0 Process Cel 2 D1 Process Cel 2 D0 Process Cel 3 D1 Process Cel 3 cell cel2 cel3 A0 Process Cel 0 Proceso F0 Cel 0 MODEL OF COMPONENTS

  11. MODEL OF COMPONENTS

  12. MODEL OF COMPONENTS NETWORK ELEMENT: • CLUSTER • HOST • PLATFORM SERVICE • A SERVICE • CELL • FUNCTIONALITY INSTANCE (process) • B SERVICE MANAGEMENT ELEMENT • Manager

  13. INDEX Model of Components Architecture Data Model Miscellaneous Statistics

  14. PC PC EGSDP ARCHITECTURE EGSDP GSEG PROGCOMANDOS GIDS MANAGERS SUN GMOD GALAR INSTALLER MANAGERS NEWNET G. INTERNOS PRIMARY MANAGERS GTRAPS GOPER GCONF SVISOR DEMUXTRAPS SNMP BE1 BE2 ASNMP ASNMP

  15. PC PC EGSDP ARCHITECTURE EGSDP GSEG PROGCOMANDOS GIDS MANAGERS SUN GMOD GALAR INSTALADOR MANAGERS NEWNET G. INTERNOS PRIMARY MANAGERS GTRAPS GOPER GCONF SVISOR DEMUXTRAPS SNMP BE1 BE2 ASNMP ASNMP

  16. PC PC EGSDP ARCHITECTURE EGSDP GSEG PROGCOMANDOS GIDS MANAGERS SUN GMOD GALAR INSTALADOR MANAGERS NEWNET G. INTERNOS PRIMARY MANAGERS GTRAPS GOPER GCONF SVISOR DEMUXTRAPS SNMP BE1 BE2 ASNMP ASNMP

  17. PC PC EGSDP ARCHITECTURE EGSDP GSEG PROGCOMANDOS GIDS MANAGERS SUN GMOD GALAR INSTALADOR MANAGERS NEWNET G. INTERNOS PRIMARY MANAGERS GTRAPS GOPER GCONF SVISOR DEMUXTRAPS SNMP BE1 BE2 ASNMP ASNMP

  18. DB EGSDP ARCHITECTURE EG Server of business Web Server Browser Action Logic Business ActionServlet ActionServlet Manager (java) JSP Page Beans: Presentation Model View, Controller

  19. PRIMARY MANAGERS GTRAPS GOPER GCONF DEMUXTRAPS SNMP BE1 BE2 ASNMP ASNMP Communication Primary Managers - ASNMP Events Commands Configuration.

  20. GMOD GALAR PRIMARY MANAGERS GTRAPS GOPER GCONF Communication of Primary - GMOD-GALAR Managers Eventos Commands Configuration.

  21. GMOD-GSEG-IGUS Communication Eventos PC IGUS PC IGUS Commands Configuration. Connection GSEG GALAR GMOD

  22. Alarms Generation Each web client receives the alarms and post them or not into the panel of Alarms ( Except if it exists a filter that conceals it) The Web interface periodically queries the web server The alarms PC PC Traps Sucesos o Cambios de Propiedad Alarms: When the alarms arrive to the Segurity Manager, they will be resend to each of the clients connected at that moment (Web server). Previosly a filter of alarms is realized. Depending on the profile of each connected operator EGSDP GSEG PROGCOMANDOS GIDS 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 are enviados hacia el GSEG GMOD GALAR The Model Manager receives the event and it is sent to The Alarms Manager. In addition, in case of receive a a Change of Property, it updates in the model the propertythat has changed in the component associated to the event G. INTERNOS PRIMARY MANAGERS The Traps Manager asks at the GCONF the translation of the SNMP identifier to an identifier of the model, and with this identifier an event or change of property de Propiedad, dependiendo del tipo de trap recibido. GTRAPS GOPER GCONF DEFENSE DEMUXTRAPS Traps come from ASNMP agents of the Network Elements machines.

  23. 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

  24. Commands Execution The Web client receives the response and shows it to the operator PC PC Commands In a Web client the operator executes a command on a Network Element component. This command is sent directly to the GSEG Set SNMP Traps Answers The command is given an unique identifier in the Security Manager. and it generates an entry to the log of commands. EGSDP GSEG PROGCOMANDOS The Segurity manager sends the response to the client that executes the command and updates in the commands log the related information of the execution of the command. GIDS When the response arrives to the Model of manager, it is resend towards the GSEG, and if necessary, new subcommands may be sent to the GOPER, it will wait again toreceive a response GMOD GALAR The Manager Model does a specific processing of command which will send one or more commands towards the group of managers. G. INTERNOS PRIMARY MANAGERS The Operations Manager checks that the response received is associated to a current command. If this is the case, it unblocks the associated component to the command and resends the response to the GMOD The Traps Manager checks the trap response, and sends it to the GOPER GOPER GTRAPS GOPER GCONF 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 DEFENSE The trap is received in the traps Demultiplexer of Traps DEMUXTRAPS 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 will resend it to the SNMP agent which will generate a response trap towards the Management Element

  25. Platform Process EGSDP GSEG PROGCOMANDOS GIDS MANAGERS SUN GMOD GALAR INSTALADOR MANAGERS NEWNET GESTAD G. INTERNOS SESTAD PRIMARY MANAGERS GTRAPS GOPER GCONF GESTADJ DEMUXTRAPS GEVENTOS SVISOR EPINGEG TESTIP

  26. Monitorization of the Connections PC PC Each web client receives the alarms and posts them into the panel alarms. When the alarms arrive to the Security Manager, they will be resend to each of the clients connected at that moment, having fulfilled previously a filtered of alarms depending on the profile of each connected operator EGSDP GSEG PROGCOMANDOS HOST1 Enviroment 01 GIDS GMOD 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 are sent towards the GSEG GALAR The event arrives to GTRAPS and turns it into a Change of Property, that is send towards the GMOD, that will generate an alarm by the regular procedure. The Change of Property is generated on the corresponding component to the machine that doesn´t give a response G. INTERNOS EPINGEG PRIMARY MANAGERS When the time-out runs the TESTIP sends an event towards the GEVENTOS, it informs the name of the machine that is non-accessible GEVENTOS HOST Enviroment ‘2 GTRAPS GOPER GCONF DEFENSE TESTIP DEMUXTRAPS The TESTIP does periodically a ping to each machine of the Network Element In this case the ping was lost because the TESTIP process died (the platform stopped), the conection was lost or because the machine crashed. HOST n

  27. INDEX Model of Components Architecture Data Model Miscellaneous Statistics

  28. Administration (Types of Components)

  29. AL_PASSSERVICIOS A7_TNSNAMES AL_PASSSERVICIOS AL_A7_NUTNSNAME AL_CDUSUARIO AL_CDPASSWORD A7_NUTNSNAME A7_CDNOMBRE A7_A6_NUAGRUPACION A7_CDUSUARIO A7_CDPASSWORD Administration (Services) FK_AL_A0 FK_AL_A7

  30. Administration (Functionalities )

  31. Administration (Tasks ) AA_CDAYUDA AA_CDAYUDA AA_CDPARAM

  32. 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.

  33. Types of Alarm

  34. Group of Alarms

  35. Actions to Perform in the Event of an Alarm

  36. History of alarms

  37. Commands History

  38. 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.

  39. Users and Profiles obsolete obsolete obsolete obsolete obsolete

  40. Users:

  41. Profiles:

  42. Table Views

  43. Time Restrictions

  44. INDEX Model of Components Architecture Data Model Miscellaneous Statistics

  45. EG FORMS EG DB

  46. ER FORMS EG ER Conection Manager CMAN DB

  47. ESTRUCTURE OF DIRECTORIES

  48. Bin Directory

  49. bcarga Directory

  50. 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.

More Related