<?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 support</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-17T11:55:25+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:add_new_mdc_sync&amp;rev=1687445690&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:add_user_to_text_alerts&amp;rev=1663324250&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:alarm_sync_failures&amp;rev=1736357239&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:american_tower_-_brocade_and_mikrotik&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:american_tower_-_ruckus&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:atc_availability&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:atc_ticket_escalation_process&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:available_amchart_4_report_settings&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:backing_up_a_table&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:component_discovery&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:critical_text_management&amp;rev=1717078287&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:customercontact&amp;rev=1675027513&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:customer_wireguard_configuration&amp;rev=1712921805&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:daily_status_report&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:dealing_with_emails&amp;rev=1676474377&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:device_missing_alarm_handling&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:dig_portal&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:errigal_support_reports&amp;rev=1674948029&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:extenet&amp;rev=1676392376&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:extenet_-_mnet&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:extenet_approval_process_-_feb_2018&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:extenet_support_reports&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:fa_codes&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:form_creation&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:general_resolutions&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:guardian&amp;rev=1687943536&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:importantdistro&amp;rev=1676989789&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:information_radiator&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:introduction_to_scotty_pro&amp;rev=1669638826&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:jira_template&amp;rev=1670275622&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:kla_server&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:kla_ticket_escalation_process&amp;rev=1655289715&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:login_credentials_for_controllers&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:logs_backup_process&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:monthly_co-ordination_tickets_-_billing_reporting&amp;rev=1648810768&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:nova_threshold_alarms&amp;rev=1679673177&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:on_air_status&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:outage_process_backups&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:percona&amp;rev=1631694549&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:pm_of_poles_guideline&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:proxy_setup&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:rca_doc_guidelines&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:re-add_deleted_form_in_ticketer&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:re-insert_ticket_form&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:remote_ticket&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:remote_ticket_troubleshooting&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:reporting_manager&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:report_checklist&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:resolutions&amp;rev=1675028386&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:row&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:scottyprosupport_reports&amp;rev=1676392018&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:scottypro_architecture&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:scotty_main&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:scotty_pro_support_forms&amp;rev=1678188751&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:scotty_pro_support_workflows&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:scotty_pro_visibilities&amp;rev=1674829671&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:scotty_reporting&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:setup_open_vpn_2018_edition&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:site_tracker&amp;rev=1637082437&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:small_customer_offering_sco&amp;rev=1746782687&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:snmpmanager_configuration&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:snmp_manager&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:start&amp;rev=1739192106&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:support_and_watchdog_rota&amp;rev=1632741703&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:support_labels&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:support_process_overview&amp;rev=1676388285&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:support_process_overview_internal&amp;rev=1677691380&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:support_request_page&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:support_ticket_creation&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:technologyspecifictips&amp;rev=1675026981&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:ticketer&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:topology_sync_failures&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:transfer_script&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:troubleshootingtips&amp;rev=1709899839&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:tunneling&amp;rev=1628258902&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:usefuldocs&amp;rev=1687941939&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:user_creation_checklist&amp;rev=1624612196&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:weekly_reports&amp;rev=1699368009&amp;do=diff"/>
                <rdf:li rdf:resource="http://3.86.49.49/doku.php?id=support:what_is_escalated_priority&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=support:add_new_mdc_sync&amp;rev=1687445690&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-06-22T15:54:50+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:add_new_mdc_sync</title>
        <link>http://3.86.49.49/doku.php?id=support:add_new_mdc_sync&amp;rev=1687445690&amp;do=diff</link>
        <description>MDC Sync Setup Instructions

Author: Paddy Murphy

Overview

Performance and Configuration syncs need to be set up to populate widgets in EMS-Nova.
Instruction below are for a SEO environment where snmp port forwarding is used.
You will still need to verify the snmp settings are correct where port forwarding is not used.
Syncs are set up at the controller level.
Before you start you will need a connection to the rdf database.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:add_user_to_text_alerts&amp;rev=1663324250&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-09-16T11:30:50+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:add_user_to_text_alerts</title>
        <link>http://3.86.49.49/doku.php?id=support:add_user_to_text_alerts&amp;rev=1663324250&amp;do=diff</link>
        <description>Add New User to Text Alerts

Author: Eoin Hearne


Add to Watchdog Groovlet

Our watchdog system, running on cerberus server, is set up to send a text alert for critical alarms. This process is handled by a groovlet in the cerberus ticketer database.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:alarm_sync_failures&amp;rev=1736357239&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-01-08T17:27:19+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:alarm_sync_failures</title>
        <link>http://3.86.49.49/doku.php?id=support:alarm_sync_failures&amp;rev=1736357239&amp;do=diff</link>
        <description>Author: Paddy Murphy

This wiki was created to assist if you encounter issues with Alarm Sync.

Please note that an Alarm Severity Sync should be run before an Active Alarm Sync

Troubleshooting Checklist

	*  Verify that you can login into the Controller and successfully reach a landing page with data. Some Controllers can only be accessed through a</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:american_tower_-_brocade_and_mikrotik&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>support:american_tower_-_brocade_and_mikrotik</title>
        <link>http://3.86.49.49/doku.php?id=support:american_tower_-_brocade_and_mikrotik&amp;rev=1624612196&amp;do=diff</link>
        <description>Brocade and Mikrotik

Overview

These technologies represent Switches and Routers. When these systems were initially loaded into the IDMS, there were done so as child elements of the Ruckus CGWF controllers. The reason for this is because each Ruckus CGWF site is made up of a number of Access Points (AP&#039;s), Core Routers (CR&#039;s) and Core Switches (CS&#039;s), with the AP&#039;s being Wi-Fi and the CR&#039;s/CR&#039;s being routers and switches respectively.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:american_tower_-_ruckus&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>support:american_tower_-_ruckus</title>
        <link>http://3.86.49.49/doku.php?id=support:american_tower_-_ruckus&amp;rev=1624612196&amp;do=diff</link>
        <description>Ruckus Smart Zone

Overview

The implementation of the Ruckus technology on American Tower differs from the implementation of a traditional technology in several ways. Each Ruckus controller sends its traps to a single, centralised controller which then forwards the traps onto the Errigal. Because of this, all Ruckus traps are received from a single IP address which is the IP address of the centralised controller:</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:atc_availability&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>support:atc_availability</title>
        <link>http://3.86.49.49/doku.php?id=support:atc_availability&amp;rev=1624612196&amp;do=diff</link>
        <description>ATC Availability Reports

Reports

	*  Availability Raw Data
			*  .  BreakDown /List of Alarms – Quite Heavy, should only be run for  a specific site or for a short period (e.g. 2 days)

	*  Availability Report by Region - 1 report for the whole system, can be filtered by regions</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:atc_ticket_escalation_process&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>support:atc_ticket_escalation_process</title>
        <link>http://3.86.49.49/doku.php?id=support:atc_ticket_escalation_process&amp;rev=1624612196&amp;do=diff</link>
        <description>ATC Ticket Escalation Process

Introduction

ATC&#039;s technical support staff have a standard operational time of  7 AM to 8 PM 5 days a week, Monday to Friday. ATC need to ensure that service affecting outages and issues are still responded to appropriately and efficiently out of hours. ATC provide this cover by having a TSE(Technical Service Engineer) on-call. The TSE on call is rotated amongst the technical support staff in ATC each week.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:available_amchart_4_report_settings&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>support:available_amchart_4_report_settings</title>
        <link>http://3.86.49.49/doku.php?id=support:available_amchart_4_report_settings&amp;rev=1624612196&amp;do=diff</link>
        <description>Axis

Add new Axis


builder.addXAxis(new Axis())
builder.addYAxis(new Axis())


Axis Fields

	*  type
		*  AxisType.CategoryAxis
		*  AxisType.ValueAxis
		*  AxisType.DateAxis</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:backing_up_a_table&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>support:backing_up_a_table</title>
        <link>http://3.86.49.49/doku.php?id=support:backing_up_a_table&amp;rev=1624612196&amp;do=diff</link>
        <description>Backing Up A Table

Author: Michelle McCausland

	*  In the command line or in putty navigate to the home/scotty level of a database. (In this instance I am on Errigal QA - qadb2.err).
	*  It is important to back up tables on the slave system as opposed to the master to prevent any load/locking issues.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:component_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>support:component_discovery</title>
        <link>http://3.86.49.49/doku.php?id=support:component_discovery&amp;rev=1624612196&amp;do=diff</link>
        <description>A customer reports that a Controller is not visible in the Component Discovery drop down list.

The relevant fields to check are:

	*  http_session_manager_configuration_id
	*  remote_system_info_discovery_configuration_id

Find a controller with the same technology that appears in the Component Discovery drop down list and compare the fields listed above.
Update if values are null or are different from from the second Controller</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:critical_text_management&amp;rev=1717078287&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-30T15:11:27+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:critical_text_management</title>
        <link>http://3.86.49.49/doku.php?id=support:critical_text_management&amp;rev=1717078287&amp;do=diff</link>
        <description>[[support:Critical Text Management]]

Two forms of critical notifications exist

1. Critical@errigal.com

2. Watchdog Critical notifications.

A cross-team notification list maintained by &lt;https://www.world-text.com/&gt;. 

- Username is in ErrigalSupport, Password is in the IT Management pwSafe.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:customercontact&amp;rev=1675027513&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-01-29T21:25:13+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:customercontact</title>
        <link>http://3.86.49.49/doku.php?id=support:customercontact&amp;rev=1675027513&amp;do=diff</link>
        <description>Customer Contacts

	*  ATC
	*  ExteNet
	*  Netrio
	*  SCO
	*  KLA</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:customer_wireguard_configuration&amp;rev=1712921805&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-04-12T12:36:45+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:customer_wireguard_configuration</title>
        <link>http://3.86.49.49/doku.php?id=support:customer_wireguard_configuration&amp;rev=1712921805&amp;do=diff</link>
        <description>Configure Wiregaurd Client for Customers

Author: Eoin Hearne

Introduction

We have customers that cannot connect to their network through a public network. Customers that have an Errigal device (Edge) deployed in their network can utilise the wiregard network config to tunnel into their network.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:daily_status_report&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>support:daily_status_report</title>
        <link>http://3.86.49.49/doku.php?id=support:daily_status_report&amp;rev=1624612196&amp;do=diff</link>
        <description>Daily Applications Status Report

Author: Cathal O&#039;Keeffe

The Daily Applications Status Report is an email that is sent out from each of the application servers each day. It contains a list of exceptions that occurred in each application as well as data on potential trap parsing issues.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:dealing_with_emails&amp;rev=1676474377&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-02-15T15:19:37+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:dealing_with_emails</title>
        <link>http://3.86.49.49/doku.php?id=support:dealing_with_emails&amp;rev=1676474377&amp;do=diff</link>
        <description>Dealing With Emails

Author: Michelle McCausland

Updated: Loughlin Moore

Note: The below content was written before the Support Request App was introduced but is relevant for times we do have to respond or send an email to the customer. The section on content is valuable advice for updates added in the Ops tickets.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:device_missing_alarm_handling&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>support:device_missing_alarm_handling</title>
        <link>http://3.86.49.49/doku.php?id=support:device_missing_alarm_handling&amp;rev=1624612196&amp;do=diff</link>
        <description>Device Missing Alarm Handling

Author: Yanjun Wang

Device Missing Alarm

Device Missing Alarm from the IDMS is to alert users that a trap was received and processed which referenced an unknown child network element. Unknown meaning there is no such child element under the particular controller in the SNMP-Manager knowledgebase. (this alarm can be assigned to the controller level at this stage depending on the trap rule)</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:dig_portal&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>support:dig_portal</title>
        <link>http://3.86.49.49/doku.php?id=support:dig_portal&amp;rev=1624612196&amp;do=diff</link>
        <description>Dig Portal

	*  Restarting the Dig Portal
	*  Dig Portal Connection Guide</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:errigal_support_reports&amp;rev=1674948029&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-01-28T23:20:29+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:errigal_support_reports</title>
        <link>http://3.86.49.49/doku.php?id=support:errigal_support_reports&amp;rev=1674948029&amp;do=diff</link>
        <description>====== Errigal Support Reports ======
Author: Michelle McCausland

Updated: Loughlin Moore




NOTE: Report is now automated, I will add details on how to run report soon. The below information is no longer applicable  


===== Introduction =====



The Errigal support reports, or internal support reports, are used to provide an overview of the active tickets from the previous week eg. tickets opened, tickets closed, ticket aging, total backlog etc.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:extenet&amp;rev=1676392376&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-02-14T16:32:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:extenet</title>
        <link>http://3.86.49.49/doku.php?id=support:extenet&amp;rev=1676392376&amp;do=diff</link>
        <description>ExteNet

Time Zone - Central

Escalation Order

	*  ExteNet NOC: +1 866 892 5327
	*  Leo: +1 708 710 8012
	*  Lea: +1 708 870 0105
	*  Matt Simpson: +1 847 878 4320</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:extenet_-_mnet&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>support:extenet_-_mnet</title>
        <link>http://3.86.49.49/doku.php?id=support:extenet_-_mnet&amp;rev=1624612196&amp;do=diff</link>
        <description>mNET Technology

Author: Paddy Murphy

Overview

mNET is a system that allows 4G-LTE services to be provided to rural areas in the US, there is also a migration path for 5G. mNET can support standalone rural networks, private and virtual private wireless networks, network expansion and wireless roaming, integrated LTE and Wi-Fi networks and multi-carrier small cell networks.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:extenet_approval_process_-_feb_2018&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>support:extenet_approval_process_-_feb_2018</title>
        <link>http://3.86.49.49/doku.php?id=support:extenet_approval_process_-_feb_2018&amp;rev=1624612196&amp;do=diff</link>
        <description>ExteNet Approval Process</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:extenet_support_reports&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>support:extenet_support_reports</title>
        <link>http://3.86.49.49/doku.php?id=support:extenet_support_reports&amp;rev=1624612196&amp;do=diff</link>
        <description>Extenet Support Reports

Author: Michelle McCausland

Updated: Loughlin Moore 

NOTE: This report is no longer run, Keith runs the ExteNet Combined report each Friday for Mondays call

A delta report showing if any new ticket or ticket changes status is sent to Keith before the call on Monday so he can update his priority sheet.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:fa_codes&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>support:fa_codes</title>
        <link>http://3.86.49.49/doku.php?id=support:fa_codes&amp;rev=1624612196&amp;do=diff</link>
        <description>FA Code

	*  FA codes are used to identify equipment for traps forwarded to AT&amp;T.
	*  The FA code refers to the carrier_hub_id in the network_element table.
	*  FA codes are set at the Controller level

See trap forwarding for detailed information on this subject.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:form_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>support:form_creation</title>
        <link>http://3.86.49.49/doku.php?id=support:form_creation&amp;rev=1624612196&amp;do=diff</link>
        <description>Form Creation

Author: Michelle McCausland

Form Template Document

When a customer requests any work relating to forms i.e. form creation, form modification, it is necessary for them to fill in a form template document.

The aim of this document is to allow the customer to accurately convey requirements for form creation to us.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:general_resolutions&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>support:general_resolutions</title>
        <link>http://3.86.49.49/doku.php?id=support:general_resolutions&amp;rev=1624612196&amp;do=diff</link>
        <description>General Resolutions

General resolutions are a category of general tips/tricks or observations and how to resolve them ranging from server service tips to deployment hacks. The goal is to provide a findable category of problems which have been encountered before and can be resolved</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:guardian&amp;rev=1687943536&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-06-28T10:12:16+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:guardian</title>
        <link>http://3.86.49.49/doku.php?id=support:guardian&amp;rev=1687943536&amp;do=diff</link>
        <description>Guardian SNMP Traps

Link to latest version of Guardian Mib:
MIB

Query to return guardian traps
select * from trap where name_oid like &#039;.1.3.6.1.4.1.33582.200%&#039; order by id desc limit 10;

Query to return guardian trap rules.
select * from trap_rule where trap_oid  like &#039;.1.3.6.1.4.1.33582.200%&#039;;</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:importantdistro&amp;rev=1676989789&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-02-21T14:29:49+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:importantdistro</title>
        <link>http://3.86.49.49/doku.php?id=support:importantdistro&amp;rev=1676989789&amp;do=diff</link>
        <description>Important Groups/Addresses

	*  Support@errigal.com
	*  noreply@errigal.com
	*  fallbacknotification@errigal.com
	*  scofallback@errigal.com
	*  notifications@errigal.com
	*  errigalticketnotification@errigal.com
	*  dailyexceptions@errigal.com
	*</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:information_radiator&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>support:information_radiator</title>
        <link>http://3.86.49.49/doku.php?id=support:information_radiator&amp;rev=1624612196&amp;do=diff</link>
        <description>Information Radiator

PI Radiators

Author: Colm Carew

The information radiator is ran from the WiFi so it is in the 10.5.5.X range.

The IP is set statically to be 10.5.5.100 and the user is pi so to connect to it from a terminal

# Ensure you are connected to the WiFi
ssh pi@10.5.5.10</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:introduction_to_scotty_pro&amp;rev=1669638826&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-11-28T12:33:46+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:introduction_to_scotty_pro</title>
        <link>http://3.86.49.49/doku.php?id=support:introduction_to_scotty_pro&amp;rev=1669638826&amp;do=diff</link>
        <description>Introduction to ScottyPro

Author: Michelle McCausland

Updated: Loughlin Moore (July 2019)

ScottyPro Ticketer

ScottyPro is a version of the Ticketer IDMS application that is used for support ticketing.

The main difference between the IDMS Ticketer and ScottyPro is the use of the Kanban board view.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:jira_template&amp;rev=1670275622&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-12-05T21:27:02+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:jira_template</title>
        <link>http://3.86.49.49/doku.php?id=support:jira_template&amp;rev=1670275622&amp;do=diff</link>
        <description>Jira Templates - Standard format

Below are the details on how to use the chrome extension to apply a template when creating a Jira ticket. There will be less need to clone tickets going forward. 

Make sure you are using the latest version of the extension.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:kla_server&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>support:kla_server</title>
        <link>http://3.86.49.49/doku.php?id=support:kla_server&amp;rev=1624612196&amp;do=diff</link>
        <description>Public IP for sending traps to: 3.90.121.19

klaapps1.err
klapps2.err
klalb1.err

KLA has its own  RDF and is own their own aws account (Access details on PW SAFE) With EC2 Instances on 

Private IPs (Aws KLA)

lb1 172.31.69.130
ems 172.31.75.184
apps2 172.31.74.23
apps1 172.31.64.42
rdfesk 172.31.73.186
rdfoat2 172.31.64.90
rdfoat1 172.31.78.251
rdfrmq 172.31.73.47 (edited)</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:kla_ticket_escalation_process&amp;rev=1655289715&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-06-15T11:41:55+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:kla_ticket_escalation_process</title>
        <link>http://3.86.49.49/doku.php?id=support:kla_ticket_escalation_process&amp;rev=1655289715&amp;do=diff</link>
        <description>KLA Ticket Escalation Process

Introduction

KLA&#039;s technical support staff have an operation time of 24×7 at Ford and need a system that will automatically escalte untouched tickets to a primary and a secondary on-call staff member.

The escalation process is to be able to send a text and email to the primary on-call after 30 mins of a ticket&#039;s inactivity.
After an additional 30 minutes,</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:login_credentials_for_controllers&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>support:login_credentials_for_controllers</title>
        <link>http://3.86.49.49/doku.php?id=support:login_credentials_for_controllers&amp;rev=1624612196&amp;do=diff</link>
        <description>Login Credentials for Controllers

Author: Michelle McCausland

If you cant find the correct Login Credentials below they may be stored in the SnmpManager master_controller_login table.

Commscope


Username: factory
Password: ION4you2


Username: test
Password: test</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:logs_backup_process&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>support:logs_backup_process</title>
        <link>http://3.86.49.49/doku.php?id=support:logs_backup_process&amp;rev=1624612196&amp;do=diff</link>
        <description>Logs Backup Process

Author: Michelle McCausland

When an outage occurs it is important to run the outage scripts that we have in place. These outage scripts take a backup of all relevant logs, heap and thread dumps and store them in a secure location to be used for investigation later.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:monthly_co-ordination_tickets_-_billing_reporting&amp;rev=1648810768&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-04-01T11:59:28+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:monthly_co-ordination_tickets_-_billing_reporting</title>
        <link>http://3.86.49.49/doku.php?id=support:monthly_co-ordination_tickets_-_billing_reporting&amp;rev=1648810768&amp;do=diff</link>
        <description>Operations Co-ordination and Management - Monthly Tickets

Author: Dave

Updated By Stephanie

Updated By Loughlin Nov 2020

We have started creating “Operations Co-ordination and Management” tickets on our customers in an effort to try track unticketed support time to general tickets. We heard a lot of feedback about a lot of tasks that require &lt; 15 minutes not needing tickets. I think this could help.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:nova_threshold_alarms&amp;rev=1679673177&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-03-24T15:52:57+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:nova_threshold_alarms</title>
        <link>http://3.86.49.49/doku.php?id=support:nova_threshold_alarms&amp;rev=1679673177&amp;do=diff</link>
        <description>Nova Threshold Alarms

Author: Paddy Murphy

Overview

Threshold alarms allow a user to set a threshold on any Nova variable. If the threshold value is breached a ticket will be automatically generated.

Query to return all thresholds


select
	tr.id,
	e.entry_point_id,
	t.discovered_name,
	t.technology,
	e.technology_version,
	e.on_air,
	tr.operator ,
	tr. parameter_key,
	t.alarm_level,
	tr.value,
	tr.breached
from
	orchestrator.threshold_rule tr
join orchestrator.threshold t on
	t.simple_thres…</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:on_air_status&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>support:on_air_status</title>
        <link>http://3.86.49.49/doku.php?id=support:on_air_status&amp;rev=1624612196&amp;do=diff</link>
        <description>Remove On Air Status Values

Author: Paddy Murphy

Two ON Air status that were removed from ExteNet by Operations are re-populated every time the Snmp Manager is restarted as the values auto populated from the Bootstrap.groovy file.

List On Air Status Values</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:outage_process_backups&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>support:outage_process_backups</title>
        <link>http://3.86.49.49/doku.php?id=support:outage_process_backups&amp;rev=1624612196&amp;do=diff</link>
        <description>Outage Process Backups

Author: Colum Foskin, Edited by: Michelle McCausland

Summary

In the event of application outages it is necessary to run the outage scripts to gather data related at the time of the incident to refer back to at a later date.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:percona&amp;rev=1631694549&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-09-15T09:29:09+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:percona</title>
        <link>http://3.86.49.49/doku.php?id=support:percona&amp;rev=1631694549&amp;do=diff</link>
        <description>Percona

Percona is a tool that aids us in creating database backups. There is a playbook in the database-setup project that can install it on a target server and there is work ongoing to automate the backups.

Percona is useful for very large databases as it is much quicker than using standard mysqldump files to backup databases. One thing to make note of though is that you will need enough space on the disk to hold a complete backup or mirror of the mysql data directory.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:pm_of_poles_guideline&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>support:pm_of_poles_guideline</title>
        <link>http://3.86.49.49/doku.php?id=support:pm_of_poles_guideline&amp;rev=1624612196&amp;do=diff</link>
        <description>PM of Poles Guideline

Author: Yanjun Wang

ExteNet requested a Planned Maintenance process for their poles in CA which is different from their normal PM process. The information of these poles will be collected by their contractors and recorded in spreadsheets. We have developed an Import Tool mainly used for loading the pole info from spreadsheets and create tickets for poles in Ticketer (the pole info will be recorded in the forms of tickets). The infractions of each pole which collected in t…</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:proxy_setup&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>support:proxy_setup</title>
        <link>http://3.86.49.49/doku.php?id=support:proxy_setup&amp;rev=1624612196&amp;do=diff</link>
        <description>server {
      listen       80;
      server_name crcreports.errigal.com;
      rewrite ^/(.*) https://crcreports.errigal.com/$1 permanent;
      location / {
              proxy_pass http://10.91.100.138:80/;
      }
}

server {
      listen       80;
      server_name atcreports.errigal.com;
      rewrite ^/(.*) https://atcreports.errigal.com/$1 permanent;
      location / {
              proxy_pass http://10.91.100.138:80/;
      }</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:rca_doc_guidelines&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>support:rca_doc_guidelines</title>
        <link>http://3.86.49.49/doku.php?id=support:rca_doc_guidelines&amp;rev=1624612196&amp;do=diff</link>
        <description>RCA Document Guidelines

Author: Michelle McCausland

Root cause analysis documents or RCAs are requested by the customers following outages that may happen to applications. Once a formal RCA has been requested we are required to send this document to the customer within 20 business days of the incident being reported.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:re-add_deleted_form_in_ticketer&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>support:re-add_deleted_form_in_ticketer</title>
        <link>http://3.86.49.49/doku.php?id=support:re-add_deleted_form_in_ticketer&amp;rev=1624612196&amp;do=diff</link>
        <description>Re-Insert Ticket Form

A customer sometimes asks for a deleted NOC Form to be re-added to a ticket.

When a form is deleted an active boolean in the ticket_change table is set to false.  

The steps to re-add a form are:

	*  Find the relevant ticket_change ID using the ticket_id field and contents field to identity correct form.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:re-insert_ticket_form&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>support:re-insert_ticket_form</title>
        <link>http://3.86.49.49/doku.php?id=support:re-insert_ticket_form&amp;rev=1624612196&amp;do=diff</link>
        <description>Re-Insert Ticket Form

A customer sometimes asks for a deleted NOC Form to be re-added to a ticket.

When a form is deleted an active boolean in the ticket_change table is set to false.  

The steps to re-add a form are:

	*  Find the relevant ticket_change ID using the ticket_id field and contents field to identity correct form.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:remote_ticket&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>support:remote_ticket</title>
        <link>http://3.86.49.49/doku.php?id=support:remote_ticket&amp;rev=1624612196&amp;do=diff</link>
        <description>--- Anna Dowling 2020/03/27 06:11

Remote Ticket / Scheduler Information

Link to slidedeck from show and tell: &lt;https://docs.google.com/presentation/d/1r9n-maHimEtVwyA1oSzeOfzekUmlc-wF2lJ8oewe1qI/edit&gt;

Link to relevant queue on Rabbit: 

&lt;http://atclb1.atc:15672/#/queues/ems/remote.ticket.dead.letter.queue&gt;
&lt;http://extlb.ext:15672/#/queues/ems/remote.ticket.dead.letter.queue&gt;

	*  RemoteTicket Refactor Documentation: &lt;https://docs.google.com/document/d/1BQ_apl92w5VtSmreIdwMJslkMUiUuTT48r9BhUx3…</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:remote_ticket_troubleshooting&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>support:remote_ticket_troubleshooting</title>
        <link>http://3.86.49.49/doku.php?id=support:remote_ticket_troubleshooting&amp;rev=1624612196&amp;do=diff</link>
        <description>Remote Ticket Troubleshooting

 --- Anna Dowling 2019/01/25 02:12

This wiki was created to assist if you encounter issues with remote ticket creation, particularly after a database re-init of a QA environment.

Troubleshooting Checklist

	*  DNS suffix was not included in the reinit script / environment configuration host name is wrong.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:reporting_manager&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>support:reporting_manager</title>
        <link>http://3.86.49.49/doku.php?id=support:reporting_manager&amp;rev=1624612196&amp;do=diff</link>
        <description>Reporting Manager

	*   Report Writing Gotchas
	*   Report Code Block Comment</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:report_checklist&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>support:report_checklist</title>
        <link>http://3.86.49.49/doku.php?id=support:report_checklist&amp;rev=1624612196&amp;do=diff</link>
        <description>Report Creation

Author: Michelle McCausland

Report Template Document

When a customer requests any work relating to reports i.e. report creation, report modification, it is necessary for them to fill in a report template document. 

The aim of this document is to allow the customer to accurately convey requirements for report creation to us.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:resolutions&amp;rev=1675028386&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-01-29T21:39:46+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:resolutions</title>
        <link>http://3.86.49.49/doku.php?id=support:resolutions&amp;rev=1675028386&amp;do=diff</link>
        <description>See Resolution Area</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:row&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>support:row</title>
        <link>http://3.86.49.49/doku.php?id=support:row&amp;rev=1624612196&amp;do=diff</link>
        <description>ROW missing Cascade/ExteNet ID dropdown value

Author: Paddy Murphy

If a support request comes to investigate why a value is missing from the Cascade/ExteNet ID drop down list in the ROW(right of way) application check that the values listed below are assigned.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:scottyprosupport_reports&amp;rev=1676392018&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-02-14T16:26:58+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:scottyprosupport_reports</title>
        <link>http://3.86.49.49/doku.php?id=support:scottyprosupport_reports&amp;rev=1676392018&amp;do=diff</link>
        <description>coming soon</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:scottypro_architecture&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>support:scottypro_architecture</title>
        <link>http://3.86.49.49/doku.php?id=support:scottypro_architecture&amp;rev=1624612196&amp;do=diff</link>
        <description>ScottyPro Ticketer Environment

Author: Avi D&#039; Silva

The current ScottyPro Ticketer runs on an AWS instance, and it was being pointed to using an Iframe.

This entry documents all the changes that were done to move away from the Iframe approach and use the</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:scotty_main&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>support:scotty_main</title>
        <link>http://3.86.49.49/doku.php?id=support:scotty_main&amp;rev=1624612196&amp;do=diff</link>
        <description>*  Introduction to Scotty Pro 
		*  ScottyPro Support Forms
		*  Operations Ticket Summary
		*  ScottyPro Support Workflow
		*  Scotty Pro Reporting
		*  Scotty Pro QA</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:scotty_pro_support_forms&amp;rev=1678188751&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-03-07T11:32:31+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:scotty_pro_support_forms</title>
        <link>http://3.86.49.49/doku.php?id=support:scotty_pro_support_forms&amp;rev=1678188751&amp;do=diff</link>
        <description>ScottyPro Support Forms and Important Fields

Updated: Loughlin Moore

Introduction

This page contains details about the forms used on support tickets in ScottyPro. 

----------

Important Fields

	*  Summary
	*  Latest Update 
	*  Estimate 

Support Request Details Form</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:scotty_pro_support_workflows&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>support:scotty_pro_support_workflows</title>
        <link>http://3.86.49.49/doku.php?id=support:scotty_pro_support_workflows&amp;rev=1624612196&amp;do=diff</link>
        <description>ScottyPro Support Workflow

Author: Loughlin Moore (July 2019)
Updated: Loughlin Moore (February 2020)

Introduction

This page outlines the workflows used in the support process on ScottyPro. Each customer has its own workflow in Scotty Pro.

Current Workflows</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:scotty_pro_visibilities&amp;rev=1674829671&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-01-27T14:27:51+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:scotty_pro_visibilities</title>
        <link>http://3.86.49.49/doku.php?id=support:scotty_pro_visibilities&amp;rev=1674829671&amp;do=diff</link>
        <description>Scotty Pro Visibilities

Author: Michelle McCausland

Updated: Loughlin Moore

Introduction

This page outlines the support visibilities used in Scotty Pro.

----------

Support Visibilities

All of the support-related visibilities in Scotty Pro are contained under the Support visibility.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:scotty_reporting&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>support:scotty_reporting</title>
        <link>http://3.86.49.49/doku.php?id=support:scotty_reporting&amp;rev=1624612196&amp;do=diff</link>
        <description>Working in progress</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:setup_open_vpn_2018_edition&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>support:setup_open_vpn_2018_edition</title>
        <link>http://3.86.49.49/doku.php?id=support:setup_open_vpn_2018_edition&amp;rev=1624612196&amp;do=diff</link>
        <description>*  Download Google Authenticator iOS or Android
	*  Go to &lt;https://olympus.err:943/&gt;
	*  Login with admin login credentials
	*  Scan barcode by Google Authenticator
	*  Check new OpenVPN entry in your Google Authenticator with admin account name
	*  Click “I Scanned the QR code” button</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:site_tracker&amp;rev=1637082437&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-11-16T17:07:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:site_tracker</title>
        <link>http://3.86.49.49/doku.php?id=support:site_tracker&amp;rev=1637082437&amp;do=diff</link>
        <description>ExteNet Site Tracker

Important Tips

Database Query Example


SELECT 
    ne.id,
    ne.name,
    ne.jde_contract_id as &#039;Site Tracker Revenue Product Id&#039;,
    ne.circuit_id,
    stpc.identifier as &#039;Site Tracker Project Identifier&#039;,
    stpc.id as &#039;Site Tracker Project Id&#039;,
    stpc.name as &#039;Site Tracker Project Name&#039;,
    stsc.identifier as &#039;Site Tracker Site Identifier&#039;,
    stsc.name as &#039;Site Tracker Site Name&#039;,
    stpc.identifier as &#039;Site Tracker Program Name&#039;,
    stpc.name as &#039;Site Tracke…</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:small_customer_offering_sco&amp;rev=1746782687&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-05-09T10:24:47+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:small_customer_offering_sco</title>
        <link>http://3.86.49.49/doku.php?id=support:small_customer_offering_sco&amp;rev=1746782687&amp;do=diff</link>
        <description>The Small Customer Offering (SCO)environment, branded to customers as  MyNocInABox,   is Errigal&#039;s &#039;plug and play&#039; solution for attending smaller customers. 

Errigal takes care of the general system maintenance and multiple customers use the same system.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:snmpmanager_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>support:snmpmanager_configuration</title>
        <link>http://3.86.49.49/doku.php?id=support:snmpmanager_configuration&amp;rev=1624612196&amp;do=diff</link>
        <description>TrapCountThreshold runs as a Quartz job and can be seen via the controller (/SnmpManager/quartz/list) or as a config entry:


select * from snmp_manager.QRTZ_CLUSTER_TRIGGERS where JOB_NAME  = &#039;com.errigal.snmpmanager.jobs.TrapCountThresholdJob&#039;;

SCHED_NAME</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:snmp_manager&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>support:snmp_manager</title>
        <link>http://3.86.49.49/doku.php?id=support:snmp_manager&amp;rev=1624612196&amp;do=diff</link>
        <description>Snmp Manager

	*  How to Check Trap Fowarding
	*  Finding an alarm clear pair
	*  Login Credentials for Controllers</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:start&amp;rev=1739192106&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-10T12:55:06+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:start</title>
        <link>http://3.86.49.49/doku.php?id=support:start&amp;rev=1739192106&amp;do=diff</link>
        <description>Support Process

Ticket Management

	*  Support Request Application 
	*  ScottyPro
	*  Customer Ticket Management
	*  Internal Tickets  
	*  Jira Template
	*  Ops_Dev Process
	*  Support and Watchdog Rota
	*  Dealing With Emails
	*  Important email Groups/Addresses
	*  The Weekly Report

Process

	*  Logs Backup Process
	*  RCA Doc Guidelines
	*  Daily Applications Status Report
	*   Login credentials for controllers
	*  Co-ordination Tickets
	*  Available AmChart 4 Report Settings
	*   SCO
	*  …</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:support_and_watchdog_rota&amp;rev=1632741703&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-09-27T12:21:43+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:support_and_watchdog_rota</title>
        <link>http://3.86.49.49/doku.php?id=support:support_and_watchdog_rota&amp;rev=1632741703&amp;do=diff</link>
        <description>Support &amp; Watchdog Rota

Author: Michelle McCausland 

Updated: Loughlin Moore

Introduction

The support and watchdog rotas were created to ensure coverage of these tasks over the week. The Operations team are responsible for the support and watchdog rotas.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:support_labels&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>support:support_labels</title>
        <link>http://3.86.49.49/doku.php?id=support:support_labels&amp;rev=1624612196&amp;do=diff</link>
        <description>Support Labels

Author: Loughlin Moore

Current Ticket Labels

Admin

Customer Success

Development Required

Integration

Internal Request

On-site Visit

RCA Required 

----------

Author: Michelle McCausland

Old Ticket Labels

Labels are added to tickets to add extra detail and classification to them.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:support_process_overview&amp;rev=1676388285&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-02-14T15:24:45+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:support_process_overview</title>
        <link>http://3.86.49.49/doku.php?id=support:support_process_overview&amp;rev=1676388285&amp;do=diff</link>
        <description>See Ticket Management</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:support_process_overview_internal&amp;rev=1677691380&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-03-01T17:23:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:support_process_overview_internal</title>
        <link>http://3.86.49.49/doku.php?id=support:support_process_overview_internal&amp;rev=1677691380&amp;do=diff</link>
        <description>Internal Application Support Tickets ( Jira ) 

Internal ( Jira ) Application Support Tickets

Format: Context - Area Action/Type - Short Details

Although internal tickets don&#039;t have the Area and Action menus you should try and think of appropriate Area and Action choices where possible when creating tickets. There may be some exceptions to using Area/Action for some issues.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:support_request_page&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>support:support_request_page</title>
        <link>http://3.86.49.49/doku.php?id=support:support_request_page&amp;rev=1624612196&amp;do=diff</link>
        <description>-</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:support_ticket_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>support:support_ticket_creation</title>
        <link>http://3.86.49.49/doku.php?id=support:support_ticket_creation&amp;rev=1624612196&amp;do=diff</link>
        <description>ExteNet Support Ticket Creation Process

Author: Michelle McCausland

Updated: Loughlin Moore

ExteNet now use the Support Request Application Please see * Support Request Application

ExteNet Ticket Creation Guidelines

Ticket Creation

  * Tickets should be created for all emails. With the exception of those that are small questions that take less than 15 minutes to resolve.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:technologyspecifictips&amp;rev=1675026981&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-01-29T21:16:21+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:technologyspecifictips</title>
        <link>http://3.86.49.49/doku.php?id=support:technologyspecifictips&amp;rev=1675026981&amp;do=diff</link>
        <description>Technology Specific Tips

	*  American Tower - Ruckus
	*  American Tower - Brocade and Mikrotik
	*  ExteNet - mNET</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:ticketer&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>support:ticketer</title>
        <link>http://3.86.49.49/doku.php?id=support:ticketer&amp;rev=1624612196&amp;do=diff</link>
        <description>Ticketer

Troubleshooting Service Entitlements</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:topology_sync_failures&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>support:topology_sync_failures</title>
        <link>http://3.86.49.49/doku.php?id=support:topology_sync_failures&amp;rev=1624612196&amp;do=diff</link>
        <description>Topology Rediscovery Sync Failures

Author: Paddy Murphy

This wiki was created to assist if you encounter issues with Topology Rediscovery Sync.

Troubleshooting Checklist

Run the following query on the Controller been investigated.
  select id, name, technology, assigned_technology_id, ip_address, port, link_down, login_credentials_id, http_session_manager_configuration_id, remote_discovery_configuration_id, software_version from network_element where id = &lt;network  element id&gt;;</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:transfer_script&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>support:transfer_script</title>
        <link>http://3.86.49.49/doku.php?id=support:transfer_script&amp;rev=1624612196&amp;do=diff</link>
        <description>Transfer Script

 --- Yanjun Wang 2019/12/16 20:15

This wiki was created to introduce Transfer Script usually used during QA Reinit.

Purpose

	*  Transfer Script usually used during QA Reinit.
	*  It&#039;s running against DB. 
	*  To replace some of customer data with Errigal data, e.g. customer emails. To prevent some QA notifications send to customer to mess up with production info.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:troubleshootingtips&amp;rev=1709899839&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-03-08T12:10:39+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:troubleshootingtips</title>
        <link>http://3.86.49.49/doku.php?id=support:troubleshootingtips&amp;rev=1709899839&amp;do=diff</link>
        <description>Troubleshooting Tips

	*  Remote Ticket Troubleshooting
	*  Transfer Script
	*  Topology Sync Failures
	*  Alarm Sync Failures</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:tunneling&amp;rev=1628258902&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-08-06T15:08:22+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:tunneling</title>
        <link>http://3.86.49.49/doku.php?id=support:tunneling&amp;rev=1628258902&amp;do=diff</link>
        <description>How to tunnel from outside the office

Source:How to Tunnel in Firefox on Mac

Introduction

Many times it can be convenient to tunnel your web traffic through a proxy, particularly an encrypted one. This web page shows how to easily tunnel your traffic through an ssh-encrypted proxy on Mac</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:usefuldocs&amp;rev=1687941939&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-06-28T09:45:39+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:usefuldocs</title>
        <link>http://3.86.49.49/doku.php?id=support:usefuldocs&amp;rev=1687941939&amp;do=diff</link>
        <description>Useful Docs

	*  Information Radiator
	*  Form Creation
	*  Report Code Block Comment
	*  Report Creation
	*  Report Writing Gotchas
	*  User Creation
	*  ATC Ticket Escalation Process
	*  KLA Ticket Escalation Process
	*   Device Missing Alarm Handling
	*   Re-Add deleted form in Ticketer
	*   FA Code 
	*   Controller missing from Component Discovery 
	*   Remove Network Element ON Air Status 
	*   ROW value missing from Cascade/ExteNet ID dropdown 
	*   ATC Availability Breakdown 
	*   KLA Det…</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:user_creation_checklist&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>support:user_creation_checklist</title>
        <link>http://3.86.49.49/doku.php?id=support:user_creation_checklist&amp;rev=1624612196&amp;do=diff</link>
        <description>User Creation

Author: Michelle McCausland

User Template Document

When a customer requests any work relating to users i.e. user creation, user modification, it is necessary for them to fill in a user template document.

The aim of this document is to allow the customer to accurately convey requirements for user creation to us.</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:weekly_reports&amp;rev=1699368009&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-11-07T14:40:09+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>support:weekly_reports</title>
        <link>http://3.86.49.49/doku.php?id=support:weekly_reports&amp;rev=1699368009&amp;do=diff</link>
        <description>How To Run The Weekly Report

 Weekly Report 

Step 1: Export Ticket Data

ScottyPro Tickets

In the ScottyPro Reporting Manager run the Weekly Reports - All Support Tickets this will return all ScottyPro tickets required for the report.

Internal Tickets (Jira)

Bookmark this Jira filter. Export it with the</description>
    </item>
    <item rdf:about="http://3.86.49.49/doku.php?id=support:what_is_escalated_priority&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>support:what_is_escalated_priority</title>
        <link>http://3.86.49.49/doku.php?id=support:what_is_escalated_priority&amp;rev=1624612196&amp;do=diff</link>
        <description>What is Escalated Priority?

Author: Michelle McCausland
Updated: Loughlin

The below process no longer applies, We work from the Top of the Open queue. The Customer sets the preferences based on agreed processes. 

Support requests that require immediate attention are referred to as escalated priority items. 

To denote this, they should have the</description>
    </item>
</rdf:RDF>
