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/2WCOM_IP-8e.md
+29-22
Original file line number
Diff line number
Diff line change
@@ -12,55 +12,62 @@ The 2WCOM IP-8e is a point-to-point or point-to-multipoint audio encoder using I
12
12
13
13
| Range | Key Features | Based on | System Impact |
14
14
|--|--|--|--|
15
-
| 1.0.0.x [SLC Main]| Initial version. | - | - |
16
-
| 1.0.1.x | - DataMiner Connectivity Framework (DCF) integration added. <br>- Redundant polling added. | 1.0.0.1 | - DCF can cause an additional load on the system. <br>- Existing elements need to be reconfigured to use the redundant connection. |
15
+
| 1.0.0.x | Initial version. | - | - |
16
+
| 1.0.1.x [Obsolete]| - DataMiner Connectivity Framework (DCF) integration added. <br>- Redundant polling added. | 1.0.0.1 | - DCF can cause an additional load on the system. <br>- Existing elements need to be reconfigured to use the redundant connection. |
17
+
| 2.0.0.x [Main range]| Conversion of connector from SNMP to HTTP connection. | 1.0.1.1 | Existing elements need to be reconfigured to use HTTP connection instead of SNMP. |
This connector uses HTTP connections and requires the input detailed below during element creation.
37
40
38
-
This connector uses a Simple Network Management Protocol (SNMP) connection and requires the following input during element creation:
39
-
40
-
SNMP CONNECTION:
41
+
### HTTP Connection - Primary
41
42
42
43
-**IP address/host**: The polling IP or URL of the destination.
43
-
-**IP port**: The IP port of the destination (default: *161*).
44
+
-**IP port**: The IP port of the destination (default: 80).
45
+
-**Device address**: The bus address of the device. If the proxy server has to be bypassed, specify *BypassProxy*.
44
46
45
-
SNMP Settings:
47
+
### HTTP Connection - Secondary
46
48
47
-
-**Get community string**: The community string used when reading values from the device (default: *public*).
48
-
-**Set community string**: The community string used when setting values on the device (default: *private*).
49
+
-**IP address/host**: The polling IP or URL of the destination.
50
+
-**IP port**: The IP port of the destination (default: 80).
51
+
-**Device address**: The bus address of the device. If the proxy server has to be bypassed, specify *BypassProxy*.
49
52
50
-
#### SNM Connection - Redundancy (range 1.0.1.x or higher)
53
+
###Initialization
51
54
52
-
From range 1.0.1.x onwards, a redundant SNMP connection needs to be configured. It requires the same configuration as the main SNMP connection.
55
+
On the **Login** page, log in using the same credentials as for the web interface of the device.
53
56
54
57
### Web Interface
55
58
56
59
The web interface is only accessible when the client machine has network access to the product.
57
60
61
+
### Redundancy
62
+
63
+
The element is configured with a redundant connection. When the primary connection is no longer responding (i.e. a timeout occurs on this connection), DataMiner will automatically switch to the secondary connection (and vice versa).
64
+
58
65
## How to use
59
66
60
-
This connector uses SNMP parameters to access and modify the device parameters.
67
+
This connector uses HTTP parameters to access and modify the device parameters.
61
68
62
69
The connector uses a UI structure similar to the web interface of the device. You can also control the parameters in a similar way.
63
70
64
-
To add new multiplexers, you will need to use the web interface of the device (available on a page of the element). These will then be accessible through the parameters of the connector. Multiplexer serves and payloads can also not be added or removed directly with the parameters of the connector.
71
+
To add new multiplexers, you will need to use the web interface of the device (available on a page of the element). These will then be accessible only through the web interface of the device.
65
72
66
73
The connector does not provide access to sensitive information such as the User, Storage, or Log pages of the web interface.
This connector uses a virtual connection and does not require any input during element creation.
36
+
37
+
### Initialization
38
+
39
+
No additional configuration of parameters is necessary in a newly created element.
40
+
41
+
## How to use
42
+
43
+
On the **General** page, the **Encoders** table provides an overview of all available Elemental Live encoder elements in the system. When you configure each encoder with details such as Location, Event Name Filter, and Booking Name Format, new rows will be generated in the **Channel Overview** table.
44
+
45
+
When a regular expression is entered in the **Event Name Filter** field, the system will utilize the content matching the first capturing group of the regular expression. The channel name that should be extracted needs to be placed within the parentheses of the first capturing group in a regex pattern (see [Examples](#examples)).
46
+
47
+
When a format is entered in the **Booking Name Format** field, placeholder {0} must be used, and it will be replaced with the channel name. You can add any desired text before or after the placeholder to customize the booking name (see [Examples](#examples)).
48
+
49
+
When you right-click the Encoders table, the **Encoder Swap** option is available in the context menu. This enables swapping encoding events from one encoder to another.
50
+
51
+
The **Live Events** page provides an overview of all live events from each encoder available in the system.
52
+
53
+
### Examples
54
+
55
+
Example of an Event Name Filter configuration:
56
+
57
+
- Event Name Filter: `[0-9]* - (.\*) - \w*`
58
+
- Live Event Name: `78 - IPsky Nick Toons SD - Main`
59
+
- Result (Channel Name): `IPsky Nick Toons SD`
60
+
61
+
Example of a Booking Name Format configuration:
62
+
63
+
- Booking Name Format: `{0}_CH`
64
+
- Channel Name: `IPsky Nick Toons SD`
65
+
- Result (SRM Booking CH): `IPsky Nick Toons SD_CH`
Copy file name to clipboardexpand all lines: connector/doc/CISCO_CBR-8_CCAP_Platform.md
+14
Original file line number
Diff line number
Diff line change
@@ -86,6 +86,20 @@ In addition, in range **1.0.0.x**, configure the following settings:
86
86
87
87
There is no redundancy defined.
88
88
89
+
### Threshold Table
90
+
91
+
In the threshold table, you can define limits for each polled modulation. The available Key Performance Indicators (KPIs) for setting thresholds are:
92
+
93
+
-**Maximum Timing Offset Level**: Range from 0 to 2000 µs.
94
+
-**Minimum Rx Power Level**: Range from -12 to 12 dBmV.
95
+
-**Maximum Rx Power Level**: Range from -12 to 12 dBmV.
96
+
-**Minimum SNR Level**: Range from 10 to 60 dB.
97
+
-**Post-FEC Maximum Uncorrectable Error Ratio Level**: Range from 0 to 30000 ppm.
98
+
99
+
When you click the **Apply** button, the status of the specified Key Performance Indicators (KPIs) in the CM table will be updated.
100
+
101
+
The minimum value for the Rx threshold cannot exceed the maximum boundary; the connector will restrict attempts to set such values.
102
+
89
103
## How to use
90
104
91
105
Once the initial setup is done, the connector can function without further configuration. However, you can perform the following actions on the **Configuration** page:
The CPI KHPA Gen IV Series MITEC Controller Version connector uses a **serial** connection to communicate with the CPI KHPA Gen IV amplifier and monitor it through a MITEC controller.
8
+
9
+
This connector is designed to communicate with the MITEC controller via a terminal server proxy (serial-to-Ethernet (IP) converter).
10
+
11
+
## About
12
+
13
+
### Version Info
14
+
15
+
| Range | Key Features | Based on | System Impact |
This connector uses a serial connection over TCP/IP and requires the following input during element creation:
38
+
39
+
SERIAL CONNECTION:
40
+
41
+
-**IP address/host**: The terminal server that the KHPA device is connected to, e.g. 10.10.11.1.
42
+
-**IP port**: The corresponding port on the terminal server configured to relay messages to the TMS4 device, e.g. 4003.
43
+
-**Bus address**: This field is used to specify the "Address Byte" configured on the KHPA device. The KHPA device supports values 48 to 111 (base 10) corresponding to a printable ASCII character (e.g. 53).
44
+
45
+
## How to Use
46
+
47
+
### General
48
+
49
+
This page displays general status information about the device.
50
+
51
+
### System
52
+
53
+
This page displays all software versions of software components as well as the time value.
54
+
55
+
### Measurements/Inhibit
56
+
57
+
This page displays information related to the meter readings/measurements of the device (e.g. current, voltage, and other power information) and inhibit states.
58
+
59
+
### Trip Points
60
+
61
+
On this page, alarm/fault trip points can be set.
62
+
63
+
### Miscellaneous
64
+
65
+
This page contains a variety of configuration settings.
66
+
67
+
## Notes
68
+
69
+
This connector currently only supports the following:
70
+
71
+
- Printable ASCII as header and ending bytes. STX/ETX not yet supported.
72
+
- Checksum as check byte. Longitudinal parity not yet supported.
73
+
74
+
The parameter "RF Limits" does not represent the actual value, because it is not possible to retrieve this from the device. The value is determined by the last RF Limits set command executed by a DataMiner user.
0 commit comments