<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="http://3.86.49.49/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://3.86.49.49/feed.php">
        <title>Internal Errigal Collaboration Wiki ems</title>
        <description></description>
        <link>http://3.86.49.49/</link>
        <image rdf:resource="http://3.86.49.49/lib/tpl/docnavwiki/images/favicon.ico" />
       <dc:date>2026-04-17T13:14:29+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=ems:alarm_auditor_configuration&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=ems:alarm_sync_setting&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=ems:config_sync_setting&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=ems:discovered_trap_configuration&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=ems:http_session_manager_configuration&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=ems:performance_and_config_sync_creation&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=ems:performance_discovery_setting&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=ems:performance_sync&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=ems:remote_discovery_configuration&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=ems:remote_discovery_scripts&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=ems:remote_system_info_discovery_configuration&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=ems:technology_discovery&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=ems:topology_discovery&amp;rev=1624612196&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://3.86.49.49/lib/tpl/docnavwiki/images/favicon.ico">
        <title>Internal Errigal Collaboration Wiki</title>
        <link>http://3.86.49.49/</link>
        <url>http://3.86.49.49/lib/tpl/docnavwiki/images/favicon.ico</url>
    </image>
    <item rdf:about="http://3.86.49.49/doku.php?id=ems:alarm_auditor_configuration&amp;rev=1624612196&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-06-25T10:09:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ems:alarm_auditor_configuration</title>
        <link>http://3.86.49.49/doku.php?id=ems:alarm_auditor_configuration&amp;rev=1624612196&amp;do=diff</link>
        <description>Alarm Auditor Scripts

Author: Eoin Joy



The Alarm Auditor scripts are used during the alarm sync process to compare the discovered alarms to the set of alarms we currently have in the system.

Matches Method

This script is used to compare a single DiscoveredAlarm against a single ActiveAlarm to determine if they match. Should this return true for any such DiscoveredAlarm, it will not be called to create a new alarm.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=ems:alarm_sync_setting&amp;rev=1624612196&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-06-25T10:09:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ems:alarm_sync_setting</title>
        <link>http://3.86.49.49/doku.php?id=ems:alarm_sync_setting&amp;rev=1624612196&amp;do=diff</link>
        <description>Alarm Sync Scripts

Author: Eoin Joy


The Alarm Sync scripts are contained in the AlarmSyncSetting domain. They are also stored with some metadata about how they should be executed.

The purpose of these scripts is to retrieve both active and disabled alarms from the target controller in a two-step process:</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=ems:config_sync_setting&amp;rev=1624612196&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-06-25T10:09:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ems:config_sync_setting</title>
        <link>http://3.86.49.49/doku.php?id=ems:config_sync_setting&amp;rev=1624612196&amp;do=diff</link>
        <description>Config Sync Scripts

Author: Eoin Joy


These scripts operate in a similar way to Alarm Sync Scripts and Performance Discovery Scripts in that they perform the same kind of two-step process, with the first step being the data retrieval.

In this case the second step is creating a list of configuration settings that were discovered from the controller and its children.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=ems:discovered_trap_configuration&amp;rev=1624612196&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-06-25T10:09:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ems:discovered_trap_configuration</title>
        <link>http://3.86.49.49/doku.php?id=ems:discovered_trap_configuration&amp;rev=1624612196&amp;do=diff</link>
        <description>Discovered Trap Scripts

Author: Eoin Joy


These scripts are designed with the purpose of turning an alarm discovered during an alarm sync into a trap to be processed by the normal trap handling process.

Trap Knowledge

This script takes the discovered alarm we have determined we wish to create a local alarm for and finds the trap knowledge that would apply to it.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=ems:http_session_manager_configuration&amp;rev=1624612196&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-06-25T10:09:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ems:http_session_manager_configuration</title>
        <link>http://3.86.49.49/doku.php?id=ems:http_session_manager_configuration&amp;rev=1624612196&amp;do=diff</link>
        <description>HTTP Session Manager Scripts

Author: Eoin Joy


These scripts are used to interact with a controller via its web interface, to perform tasks like logging in or posting data.

Object Store JSON

String – This object holds a string of JSON that represents some part of the postData that should always be present, such as what the name of the parameter that holds the cookie is. This naturally is different on a per interface basis.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=ems:performance_and_config_sync_creation&amp;rev=1624612196&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-06-25T10:09:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ems:performance_and_config_sync_creation</title>
        <link>http://3.86.49.49/doku.php?id=ems:performance_and_config_sync_creation&amp;rev=1624612196&amp;do=diff</link>
        <description>Performance and Configuration Sync Creation

Author: Eoin Hearne.

Date: 18-Jun-20.

Sync Summary



Configuration and performance syncs can be performed manually through the EMS or on a schedule. Syncs can be started on on-air, show in monitor controllers that are set up to perform these syncs. These syncs use either SNMP or HTTP to gather information from a controller regarding the status of various settings for itself and any children connected to it.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=ems:performance_discovery_setting&amp;rev=1624612196&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-06-25T10:09:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ems:performance_discovery_setting</title>
        <link>http://3.86.49.49/doku.php?id=ems:performance_discovery_setting&amp;rev=1624612196&amp;do=diff</link>
        <description>Performance Discovery Scripts

Author: Eoin Joy


These scripts are used to discover and parse the performance metrics from network elements in the system with the intent to store a certain number of them for trend analysis purposes.

Additional Configuration</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=ems:performance_sync&amp;rev=1624612196&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-06-25T10:09:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ems:performance_sync</title>
        <link>http://3.86.49.49/doku.php?id=ems:performance_sync&amp;rev=1624612196&amp;do=diff</link>
        <description>Performance and Configuration Sync Creation

Author: Eoin Hearne.

Date: 18-Jun-20.

Sync Summary



Configuration and performance syncs can be performed manually through the EMS or on a schedule. Syncs can be started on on-air, show in monitor controllers that are set up to perform these syncs. These syncs use either SNMP or HTTP to gather information from a controller regarding the status of various settings for itself and any children connected to it.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=ems:remote_discovery_configuration&amp;rev=1624612196&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-06-25T10:09:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ems:remote_discovery_configuration</title>
        <link>http://3.86.49.49/doku.php?id=ems:remote_discovery_configuration&amp;rev=1624612196&amp;do=diff</link>
        <description>Remote Discovery Configuration Scripts

Author: Eoin Joy


The scripts contained in the RemoteDiscoveryConfiguration are used in some of the basic EMS widgets like Config and Performance view, as well as the remote Alarm History. It also contains the entirely defunct active alarm and disabled alarm scripts which can be ignored.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=ems:remote_discovery_scripts&amp;rev=1624612196&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-06-25T10:09:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ems:remote_discovery_scripts</title>
        <link>http://3.86.49.49/doku.php?id=ems:remote_discovery_scripts&amp;rev=1624612196&amp;do=diff</link>
        <description>Remote Discovery Scripts

Author: Eoin Joy


Lots of functionality in the EMS is achieved with the use of runtime configurable groovy scripts, which are stored in the domain of RemoteDiscoveryScript.

These scripts are run as groovy shells and are passed in various bindings determined by where in concrete code they are executed.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=ems:remote_system_info_discovery_configuration&amp;rev=1624612196&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-06-25T10:09:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ems:remote_system_info_discovery_configuration</title>
        <link>http://3.86.49.49/doku.php?id=ems:remote_system_info_discovery_configuration&amp;rev=1624612196&amp;do=diff</link>
        <description>Component Discovery Scripts

Author: Eoin Joy


These scripts are used to poll a controller for the possibly neutral host components attached to its various child elements.

This is executed currently in two places: 1) After a Topology Discovery; 2) On Demand from the RemoteSystemInfoDiscovery controller.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=ems:technology_discovery&amp;rev=1624612196&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-06-25T10:09:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ems:technology_discovery</title>
        <link>http://3.86.49.49/doku.php?id=ems:technology_discovery&amp;rev=1624612196&amp;do=diff</link>
        <description>Technology Discovery Scripts

Author: Eoin Joy


For the process of discovering the topology of a system to create in the SNMP Manager database, first we must know what kind of system we are looking at.

These scripts determine what kind of system it is we are looking at, and lets the user know this after the initial data from the site has been obtained, but before constructing the whole system.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=ems:topology_discovery&amp;rev=1624612196&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-06-25T10:09:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ems:topology_discovery</title>
        <link>http://3.86.49.49/doku.php?id=ems:topology_discovery&amp;rev=1624612196&amp;do=diff</link>
        <description>Topology Discovery Scripts

Author: Eoin Joy


When the discovery process is initiated in the EMS, two scripts are needed per technology or user interface to fully create the new system in the IDMS.

These scripts together are the Topology Discovery Scripts.</description>
    </item>
</rdf:RDF>
