You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: connector/doc/Ericsson_SAU-IP.md
+7-8
Original file line number
Diff line number
Diff line change
@@ -10,26 +10,25 @@ This connector monitors the Ericsson Service Access Unit (SAU).
10
10
11
11
### Key Features
12
12
13
-
-**Monitoring of Connected Devices**: The connector discovers the devices and modules connected to the main Ericsson SAU and provides detailed information of each part.
14
-
-**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.
15
-
-**Alarm Monitoring**: Alarms are collected on DataMiner and easily monitored from the alarm console.
13
+
-**Monitoring of connected devices**: The connector discovers the devices and modules connected to the main Ericsson SAU and provides detailed information for each part.
14
+
-**Inputs and outputs alarm configuration**: Input and output alarm settings can be changed directly from the connector, including port configuration, alarm severity, and the specific name of the monitored port.
15
+
-**Alarm monitoring**: Alarms are collected in DataMiner and easily monitored from the Alarm Console.
16
16
17
17
## Use Cases
18
18
19
19
### Input and Output Alarm Configuration
20
20
21
-
**Challenge**: Alarm monitoring can be complex on the **Ericsson SAU** as configuration is very versatile.
21
+
**Challenge**: Alarm monitoring can be complex on the Ericsson SAU as its configuration is very versatile.
22
22
23
-
**Solution**: The connector supports the user by supplying detailed information of each configurable setting and how they affect the subsequent alarming.
24
-
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.
23
+
**Solution**: The connector allows you to supply detailed information about each configurable setting and how it affects the subsequent alarming. You can change the name of an alarm to provide more specific details about the issue, set the default configuration of the alarm to either *Normally Closed* or *Normally Opened* for different purposes, and set the severity from a dropdown menu, all on one page.
25
24
26
25
**Benefit**: Simple, straightforward way to configure alarming.
27
26
28
27
### Source of Monitored Physical Entities
29
28
30
-
**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.
29
+
**Challenge**: The monitored physical entities are available in 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.
31
30
32
-
**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.
31
+
**Solution**: The connector automatically traces the hierarchy of each monitored physical entity and prefixes the hierarchy to the entity, making it clear which parent component it is connected to.
33
32
34
33
**Benefit**: Reduce the need to manually trace physical entity hierarchy.
This connector monitors the Ericsson Service Access Unit (SAU).
28
10
29
11
## Configuration
30
12
31
13
### Connections
32
14
33
-
#### SNMP Connection - [Name of the connection]
15
+
#### SNMP Connection - Main
34
16
35
17
This connector uses a Simple Network Management Protocol (SNMP) connection and requires the following input during element creation:
36
18
37
19
SNMP CONNECTION:
38
20
39
-
-**IP address/host**: [The polling IP or URL of the destination.]
21
+
-**IP address/host**: The polling IP or URL of the destination.
40
22
41
23
SNMP Settings:
42
24
43
-
-**Port number**: [The port of the connected device, by default 161.]
44
-
-**Get community string**: [The community string used when reading values from the device (default: *public*).]
45
-
-**Set community string**: [The community string used when setting values on the device (default: *private*).]
25
+
-**Port number**: The port of the connected device, by default 161.
26
+
-**Get community string**: The community string used when reading values from the device (default: *public*).
27
+
-**Set community string**: The community string used when setting values on the device (default: *private*).
46
28
47
29
## How to use
48
30
49
31
### Input Alarm Configuration
50
-
These settings can be accessed on the Inputs page.
32
+
33
+
These settings can be accessed on the **Inputs** page.
34
+
51
35
-**Name**: This parameter can be set to provide a better description of what the sensor is monitoring.
52
36
53
37
-**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.
54
38
55
-
-**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
39
+
-**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.
56
40
57
-
-**Severity**: This parameter is a configuration parameter that allows the user to set the severity of the resultant alarm for the associated Input.
41
+
-**Severity**: This configuration parameter allows you to set the severity of the resulting alarm for the associated input.
58
42
59
43
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.
60
44
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.
61
45
62
46
### Output Alarm Configuration
63
-
These settings can be accessed on the Outputs page.
47
+
48
+
These settings can be accessed on the **Outputs** page.
49
+
64
50
-**Name**: This parameter can be set to provide a better description of what the sensor is monitoring.
65
51
66
52
-**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.
67
53
68
-
-**Severity**: This parameter is a configuration parameter that allows the user to set the severity of the resultant alarm for the associated Input.
69
-
70
-
-**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.
54
+
-**Severity**: This configuration parameter allows you to set the severity of the resulting alarm for the associated output.
71
55
56
+
-**Status**: For an output parameter, you can manually toggle the status between *Alarm* and *No Alarm*. To make a valid remote set from this connector to the sensor, the **State** has to be set to *Enabled* and the **Severity** has to be set to *Remote*.
0 commit comments