Presentation overview

1
Presentation overview

• IMS introduction
• Col-CC subsystems
• Columbus network overview
• IMS monitoring and commanding capabilities
• IMS structure
• IMS configuration and troubleshooting tools

2
IMS

• IMS (Integrated Manager Subsystem)
• The IMS is designed to monitor, control and
  configure the whole
• Columbus ground center located in
  Oberpfaffenhofen, close to Munich, with
  distributed main sites in Germany, USA, France
  and Russia, and user operation centers all over
  Europe

3
IMS overview

• Main Tasks
• Unify subsystem management
• Provide unified monitoring
• Provide unified control
• Provide unified notification messages (Event
  handling)
• Data management tasks (archiving, reporting,
  processing)
• Provide automated and manual control
• Automatic/manual reaction to system events
• Automatic/manual reaction to data value changes
• time-based automation (timeline)
• Provide Unified Views via WEB interface
• Main Requirements
• Flexibility (adopt to changes in subsystems)
• Extendibility (allow to grow to multi-mission
  tool)

4
IMS Architecture

• Distributed Architecture
• Set of server-type applications, interconnected
  via custom protocol (referred to as MCC or EGMC²
  protocol)
• distribution consequence of network
  infrastructure and performance/reliability
  considerations
• Set of MMI Client applications
• Set of configuration tools
• Configuration
• File based configuration (XML files)
• Integrated configuration management
• Hardware
• 7 Servers in Prime Col-CC, 4 in Backup CC
• 6 Workstations (3 for OPS, 3 for DEV)
• Distributed software on third party hardware

5
IMS Monitoring and Control

• The IMS provides central management tasks for the
  COL-CC. This includes
• monitoring, trouble ticket management in a
  central location and partially
• control of the following subsystems
• DaSS, MVDS and MCS (TM/TC, via EM-Element
  Managers)
• SAN, NIS, IGS RN (infrastructure and network,
  via L1 servers)
• VOCS (Voice, via SNMP)
• WAN (indirectly monitoring, via L1)
• LDAP user authentication
• Export of Unified Views via Web Export

6
Subsystem explanation

• DaSS (Data service subsystem)
• MVDS (Mpeg2 video distribution subsystem)
• MCS (Monitoring and control subsystem, Columbus
  module)
• SAN (Storage area network)
• NIS (Network infrastructure subsystem)
• IGS RN (International ground subsystem relays
  and nodes)
• VOCS (Voice conferencing system)
• WAN (Wide area network)
• LDAP (Lightweight directory access protocol)
• Web Export (Internet browser using Applets to
  display the GUIs)

7
IMS overview
8
IMS Overview
9
Col-CC Ground Segment Overview
10
IGS Network
11
IMS top level
12
Video Overview in IMS
13
MVDS HOSC overview
14
MVDS Col-CC overview
By pressing on every box, a new window will be
open for monitoring By pressing the different
symbols on the left-hand side the monitoring
possibilities are open Clicking on the right
button of the mouse a very detailed monitoring
window will be open
15
Detailed video view

• Example of matrix configuration of the video
  system

16
HOSC IGS node in IMS
17
VoCS Overview in IMS
18
VoCS detailed view
19
Control room example in Col-CC
20
DaSS Element Manager
21
SAN Prime monitoring overview
22
SAN systems Rack overview
Detailed view of the backup servers in Col-CC
with the different subsystem and their status
23
ATV-CC Unified View
24
ISDN monitoring and control
Monitoring using colors indicating the
connection status Commanding Start/stop/check
buttons for independently control each ISDN
connection
25
IMS hardware monitoring
26
IMS hardware monitoring
Monitoring example of the IMS servers itself,
the memory, CPU and Hard disk usage are resumed
here. A very detailed information can be
obtained by pressing on the buttons
27
Hardware monitoring in IMS
28
System Message Display

• System Messages available at MCE or at local
  ports of applications
• Display shows messages in colorized table.
• Preferences can be set to give host and port to
  use.
• Supports generation of audible signals and
  triggering of Alarms.

29
IMS Overview
30
IMS data tree structure

• Hierarchical data structure available in
  server-type applications, complete tree held by
  MCE.
• Nodes are organized as shown.
• Leaves support common data types
  (byte,int,float,double,string and arrays of the
  same)
• Monitoring Service announces the top part of
  exported tree on IMS links.
• MCE announces colcc.data.realtime to clients
  (and other applications).
• Data transport is a push mechanism and is
  driven by data availability.

31
IMS data tree structure

• Detail of leaves on the information tree, the
  green checkmarks indicate available

32
MCE (monitoring control engine)

• Is the central IMS server process (IMS core).
• Unifies all data trees into the global tree.
• Unifies all messages in a global message pool.
• Routes all commands, applies authorization.
• Distributes data to all clients.
• Does processing for timeouts and limit
  violations.
• Polls the database for availability, also some
  TCP ports.
• Monitors the IMS-internal connections.
• Run in hot redundancy

33
MCE script interface

• For scripting, the MCE provides an Interface for
  external Scripts to connect (via XML-RPC
  protocol).
• Scripts use the complete scope of IMS commands
  and commands going to any of the subsystems.
• Scripts have complete access (read/write) to the
  data tree within the MCE
• Scripts have access to the message service (can
  generate messages)
• All scripting in IMS is done in Python.
• Scripts are easy to write ...

34
SNMP GW

• Used to connect SNMP-enabled subsystems.
  Translates between SNMP and MCC protocols.
• Translates VoCS Commands from MCC command format
  to SNMP-set.

35
The GADP

• Ground Ancillary Data Provider
• Provides DaSS-C Interface for reception of DaSS
  Processed Parameters
• Provides DaSS-S Interface for distribution of IMS
  data as DaSS Processed Parameters
• For example, the data required for driving the
  ATV-CC Unified Views is exported to DaSS (derived
  parameters).
• Received Data is available for display and
  processing within the IMS as all other IMS data.
• Data inserted in tree structured data pool
• no control or messaging interface
• GADP exchanges data (both directions) with MCE
  and DaSS.

36
The WE (Web export)

• Data is provided to ATV-CC and USOCs via HTTP
  using Java applets.
• Applets require Java version 1.4.1 or higher to
  be installed on the remote workstations.
• Applets are opened using a browser, (Linux or
  Windows Operating System). Then, the applets open
  a connection back to the IMS to retrieve data.
  This connection goes to the WE process. The WE
  must run on the same platform as the Web Server
  (Apache, security).
• The process run in external hardware (non IMS).
  The WE makes the communication with the MCE
• Data available at WE is a subset of total MCE
  data
• The process run in hot redundancy
• New applets can be generated/modified for
  different external partners

37
The SYSLOGGW

• Syslog file scanner (LOG-Agent)
• Runs on central Syslog server
• Col-CC uses syslog-ng (next generation) for
  centralized syslog files. Syslog-ng receives logs
  from all servers and pre-processes received
  messages into a set of files.
• The Log-Agent scans a selection of these files
  for regular expressions and generates IMS
  operator messages from the syslog messages.
  Generated messages are sent to MCE for further
  processing, triggering of commands and for
  archiving at HDB.

38
IMS DEV and DQM

• DEV
• Used to test new procedures or modules outside
  the MCE server.
• Setup ensures that no commands can be sent via
  DEV to MCE.
• Currently set up to test various requirements in
  non-operational environment
• DQM
• Used to process/collect data quality outside of
  the MCE

39
The IMS Proxy

• The Proxy distributes messages to consoles in the
  OPS/OPS-SUP network and control rooms
• Filters can be defined within the MCE and in
  addition within the PRX.
• Possible Filters
• include DaSS and MCS messages
• exclude all IMS related messages
• PRX runs on external (non-IMS) hardware.
• PRX forwards user information about connected
  consoles to MCE for display within the IMS.

40
IMS on line tools

• IMS Overview Monitor 185 displays
• MVDS Overview Monitor 59 displays
• Generic Monitoring Tools
• Generic Monitor (aka GenMon)
• Generic List Monitor (aka GenListMon)
• Generic Table Monitor (aka GenTableMon)
• Parameter Viewer
• System Message Display
• Generic Control Display

41
IMS off line tools

• GUI Builder
• to create new MMIs (GUIs) or edit existing ones
• Application Builder
• to create new server processes or edit existing
  ones
• Timeline Editor
• to edit the timeline
• System Editor
• to edit server configurations low-level
• MCC Editor
• to edit ICD configuration (monitoring, control,
  messages)
• CCM Client
• offline configuration control frontend

42
Generic monitoring client

• Applications export their data to a server port.
• GUI Client exists to display remote and local
  tree.
• Useful for debugging the configuration and for
  real-time data exploration.
• Usage
• enter host, port, path
• connect
• other configurations optional

43
IMS Redundancy

• Redundancy supported by Linux Heartbeat
• server process triggers heartbeat if peer seems
  down
• heartbeat triggers failover of IP and activates
  server process on standby machine
• This mechanism is used for
• MCE / SNMPGW / DQM (any one triggers the others)
• HDB (special handling of MySQL DB in heartbeat
  scripts)
• Redundancy through concurrency
• two server processes run concurrently, both serve
  the data if required
• This mechanism used for
• WE
• PRX
• LOGGW

44
IMS Modes

• IMS can run using the following modes
• OPS for monitoring/commanding the operational
  system
• SIM for monitoring/commanding the simulation
  mode
• DEV for monitoring/commanding the development
  environment
• All this modes can be combined in order to
  monitoring/commanding the subsystems running in
  different modes (e.g DaSS in test mode, MCS in
  SIM mode)
• All the configuration parameters are integrated
  in a single file and can be changed automatically
  using scripts
• The IMS core run on Linux servers, the clients
  can be installed on Linux or Windows operating
  systems

45
IMS
Thank you for your attention! Further
questions?