added Ericsson_SAU-IP connector help

Author: joshualeeskyline

connector/doc/Ericsson_SAU-IP.md

@@ -0,0 +1,43 @@
+---
+uid: Connector_help_Ericsson_SAU-IP
+---
+
+# Ericsson SAU-IP
+
+This connector monitors the Ericsson Service Access Unit (SAU).
+
+## About
+
+### Key Features
+
+- **Monitoring of Connected Devices**: The connector discovers the devices and modules connected to the main Ericsson SAU and provides detailed information of each part.
+- **Inputs and Outputs Alarm Configuration**: Input and Output alarm settings can be changed directly from the connector, including; port configuration, alarm severity and specific name of the monitored port.
+- **Alarm Monitoring**: Alarms are collected on DataMiner and easily monitored from the alarm console.
+
+## Use Cases
+
+### Input and Output Alarm Configuration
+
+**Challenge**: Alarm monitoring can be complex on the **Ericsson SAU** as configuration is very versatile.
+
+**Solution**: The connector supports the user by supplying detailed information of each configurable setting and how they affect the subsequent alarming.
+Name of the alarm can be changed to provide more specific details of the issue, default configuration of the alarm can be set to either Normally Closed or Normally Opened for different purposes, and severity can be set from a dropdown menu all on one page.
+
+**Benefit**: Simple, straightforward way to configure alarming.
+
+### Source of Monitored Physical Entities
+
+**Challenge**: The monitored physical entities are available on a generic Physical Entities table from the MIB. Although the devices are on different hierarchical levels (parent and child relationship), they are stored on the same table making it confusing to track the entire hierarchy.
+
+**Solution**: The connector automatically traces the hierarchy of monitored physical entity and prefixes the hierarchy to the entity, making it clear which parent component it is connected to.
+
+**Benefit**: Reduce the need to manually trace physical entity hierarchy.
+
+## Prerequisites
+
+- **DataMiner version 10.2 or higher** is required.
+
+## Technical Information
+
+> [!NOTE]
+> For detailed technical information, refer to our [technical documentation](xref:Connector_help_Ericsson_SAU-IP_Technical).

connector/doc/Ericsson_SAU-IP_Technical.md

@@ -0,0 +1,71 @@
+---
+uid: Connector_help_Ericsson_SAU-IP
+---
+
+# Ericsson SAU-IP
+
+This connector monitors the Ericsson Service Access Unit (SAU).
+
+## About
+
+### Version Info
+
+| Range              | Key Features                                                                                      | Based on | System Impact |
+|--------------------|---------------------------------------------------------------------------------------------------|----------|---------------|
+| 1.0.0.x [SLC Main] | Initial version.                                                                                  | -        | -             |
+
+### Product Info
+
+| Range     | Supported Firmware     |
+|-----------|------------------------|
+| 1.0.0.x   | -		                 |
+
+### System Info
+
+| Range   | DCF Integration | Cassandra Compliant | Linked Components | Exported Components |
+|---------|-----------------|---------------------|-------------------|---------------------|
+| 1.0.0.x | No              | Yes                 | -                 | -                   |
+
+## Configuration
+
+### Connections
+
+#### SNMP Connection - [Name of the connection]
+
+This connector uses a Simple Network Management Protocol (SNMP) connection and requires the following input during element creation:
+
+SNMP CONNECTION:
+
+- **IP address/host**: [The polling IP or URL of the destination.]
+
+SNMP Settings:
+
+- **Port number**: [The port of the connected device, by default 161.]
+- **Get community string**: [The community string used when reading values from the device (default: *public*).]
+- **Set community string**: [The community string used when setting values on the device (default: *private*).]
+
+## How to use
+
+### Input Alarm Configuration
+These settings can be accessed on the Inputs page.
+- **Name**: This parameter can be set to provide a better description of what the sensor is monitoring.
+
+- **State**: This parameter toggles between enabling and disabling the alarm for the row item. Disabling an enabled alarm will also clear the existing alarm, if any.
+
+- **Configuration**: This parameter refers to the default state of the monitored Input; a Normally Closed Input will trigger an alarm when it opens and vice versa
+
+- **Severity**: This parameter is a configuration parameter that allows the user to set the severity of the resultant alarm for the associated Input.
+
+When an Input alarm is activated, it will be indicated as 'Active' in the **Status** column. This alarm will also be represented on the Alarms table.
+The user can choose which location (Alarm table or Inputs table) to alarm on, noting that alarming on both locations will result in duplicate alarms for the same incident.
+
+### Output Alarm Configuration
+These settings can be accessed on the Outputs page.
+- **Name**: This parameter can be set to provide a better description of what the sensor is monitoring.
+
+- **State**: This parameter toggles between enabling and disabling the alarm for the row item. Disabling an enabled alarm will also clear the existing alarm, if any.
+
+- **Severity**: This parameter is a configuration parameter that allows the user to set the severity of the resultant alarm for the associated Input.
+
+- **Status**: As an output parameter, the status can be manually toggled between Alarm and No Alarm states. To make a valid remote set from this connector/device to the sensor, the **State** should be Enabled and **Severity** should be Remote.
+