Skip to content

Commit b90f433

Browse files
committed
Merge branch 'main' into pr/305
2 parents a4e6f5c + c10c3f5 commit b90f433

10 files changed

+439
-18
lines changed
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
---
2+
uid: Connector_help_Brandywine_Communications_FDU-160i
3+
---
4+
5+
# Brandywine Communications FDU-160i
6+
7+
This connector allows you to monitor and set different variables on the Brandywine FDU-160i device using SNMP.
8+
9+
The FDU-160i is a signal distribution amplifier contained in a compact 1U rack-mount chassis, which is among others used in secure communication systems, satellite ground stations, digital television broadcasting, and systems requiring highly reliable frequency outputs. The system accepts two frequency inputs (typically 10 MHz). It provides automatic changeover if one of the online source inputs fails, and each input is capable of driving all sixteen outputs. Manual source selection override is available on the front panel or through the Ethernet interface.
10+
11+
User control of the unit happens via a built-in web browser with graphical interface or directly through this connector via SNMP.
12+
13+
## About
14+
15+
### Version Info
16+
17+
| Range | Features | Based on | System Impact |
18+
|--------------------|-----------------|----------|---------------|
19+
| 1.0.0.x [SLC Main] | Initial version | - | - |
20+
21+
### Product Info
22+
23+
| Range | Supported Firmware |
24+
|---------|--------------------|
25+
| 1.0.0.x | - |
26+
27+
### System Info
28+
29+
| Range | DCF Integration | Cassandra Compliant | Linked Components | Exported Components |
30+
|---------|-----------------|---------------------|-------------------|---------------------|
31+
| 1.0.0.x | No | Yes | - | - |
32+
33+
## Configuration
34+
35+
### Connections
36+
37+
#### SNMP Connection - Main
38+
39+
This connector uses a Simple Network Management Protocol (SNMP) connection and requires the following input during element creation:
40+
41+
SNMP CONNECTION:
42+
43+
- **IP address/host**: The polling IP or URL of the destination.
44+
- **IP port**: The IP port of the destination.
45+
46+
SNMP Settings:
47+
48+
- **Get community string**: The community string used when reading values from the device (default: *public*).
49+
- **Set community string**: The community string used when setting values on the device (default: *private*).
50+
51+
### Web Interface
52+
53+
The web interface is only accessible when the client machine has network access to the product.
54+
55+
## How to use
56+
57+
### General
58+
59+
The General page contains information about the device: the Serial Number, Product Name, Version, and Location.
60+
61+
### Reference and Inputs
62+
63+
On this page, you can view and change the configuration of the reference data and input data, including the thresholds and volt unit selection.
64+
65+
### Output Status
66+
67+
This page displays status information for output data.
68+
69+
### Output Config
70+
71+
This page allows you to configure the different output ports (1-16) as well as their alarm thresholds.
72+
73+
### Traps
74+
75+
This page contains a table with the trap configuration.
76+
77+
### Offsets
78+
79+
This page allows the user to configure offsets based on time and units.
80+
81+
### Configuration
82+
83+
On this page, you can configure IP addresses and view the currently configured IP addresses.

connector/doc/EasyTools_Content_Management_Platform.md

+5-2
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ You can find more information about the data display pages of the connector belo
5656

5757
### General Page
5858

59-
This page displays the server **System ID, Version, Vendor, Time,** **Name**, and **IP Address** (which represents the polling IP), as well as the **Total Memory, Memory Cache, Free Memory**, and **Memory Buffers.**
59+
This page displays the server **System ID**, **Version**, **Vendor**, **Time**, **Name**, and **IP Address** (which represents the polling IP), as well as the **Total Memory, Memory Cache, Free Memory**, and **Memory Buffers.**
6060

6161
There are two page buttons:
6262

@@ -75,7 +75,10 @@ This page displays information regarding the **Configured Nodes**.
7575

7676
### Functions and Operations Page
7777

78-
This page displays information regarding the **Configured** **Functions,** **Configured Operations**, and **Operation Transcode AAC** that are created in the device.
78+
This page displays information regarding the **Configured Functions**, **Configured Operations**, and **Operation Transcode AAC** that are created in the device.
79+
80+
> [!NOTE]
81+
> If you want alarms to be triggered for datetime parameters such as the Last Up/Down columns, you will need to calculate the numeric value for a specific date and use that in the alarm template.
7982
8083
### Schedules and Jobs Page
8184

+29
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
uid: Connector_help_Generic_Virtual_Embedder
3+
---
4+
5+
# Generic Virtual Embedder
6+
7+
This is a virtual connector that initializes DCF connections at startup. It has no data pages.
8+
9+
## About
10+
11+
### Version Info
12+
13+
| Range | Features | Based on | System Impact |
14+
|--------------------|-----------------------------------------|----------|---------------|
15+
| 1.0.0.x [SLC Main] | Initializes DCF connections at startup. | - | - |
16+
17+
## Configuration
18+
19+
### Connections
20+
21+
#### Virtual Connection - Main
22+
23+
This connector uses a virtual connection and does not require any input during element creation.
24+
25+
## How to use
26+
27+
This is a virtual connector that initializes DCF connections at startup.
28+
29+
The connector does not have any data pages.

connector/doc/Nevion_Video_iPath.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,8 @@ This connector is used to retrieve all data information from the Nevion Video iP
2424
| 1.2.5.x [Obsolete] | Corrected Endpoints table to reflect the correct column names for Descriptor Description, Descriptor Label and FDescriptor Label data. | No | Yes |
2525
| 1.2.6.x | InterApp communication upgraded on QAction 9000000. All external integrations that communicate with this connector will need to upgrade their own InterApp communication. <br>Following methods need to be upgraded: <br>- Message.Send(); <br>- InterAppCallFactory.CreateFromRaw() | No | Yes |
2626
| 1.2.7.x [Obsolete] | InterApp code moved to NuGets. Minimum required DataMiner version: 10.0.10.x | No | Yes |
27-
| 1.2.8.x [SLC Main] | Performance improvements. General code review fixes. | No | Yes |
27+
| 1.2.8.x | Performance improvements. General code review fixes. | No | Yes |
28+
| 1.3.0.x [SLC Main] | Endpoint for authentication changed to endpoint api/_session for authentication in version 9.22. The endpoint cdb/_session is deprecated. | No | Yes |
2829

2930
### Product Info
3031

@@ -41,6 +42,7 @@ This connector is used to retrieve all data information from the Nevion Video iP
4142
| 1.2.6.x | 5.12.4 |
4243
| 1.2.7.x | 5.12.4 |
4344
| 1.2.8.x | 5.12.4 |
45+
| 1.3.0.x | 9.22 |
4446

4547
## Configuration
4648

connector/doc/Sencore_CRD_4900.md

+74
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
---
2+
uid: Connector_help_Sencore_CRD_4900
3+
---
4+
5+
# Sencore CRD 4900
6+
7+
Sencore CRD 4900 is a high-density modular frame designed to accommodate up to 20 cards of the openGear Multi-Definition product family.
8+
9+
This connector contains information about the frame and its overall status (temperature, power supply, buzzer, etc.).
10+
11+
No information about the specific cards can be retrieved through the Frame SNMP agent, nor is this provided in the MIB. Instead, individual elements representing the cards can be created if the appropriate connectors are available.
12+
13+
## About
14+
15+
### Version Info
16+
17+
| Range | Key Features | Based on | System Impact |
18+
|----------------------|------------------|--------------|-------------------|
19+
| 1.0.0.x [SLC Main] | Initial version | - | - |
20+
21+
### Product Info
22+
23+
| Range | Supported Firmware |
24+
|-----------|------------------------|
25+
| 1.0.0.x | CRD4900-1.1.0 |
26+
27+
### System Info
28+
29+
| Range | DCF Integration | Cassandra Compliant | Linked Components | Exported Components |
30+
|-----------|---------------------|-------------------------|-----------------------|-------------------------|
31+
| 1.0.0.x | No | Yes | - | - |
32+
33+
## Configuration
34+
35+
### Connections
36+
37+
#### SNMP Connection
38+
39+
This connector uses a Simple Network Management Protocol (SNMP) connection and requires the following input during element creation:
40+
41+
SNMP CONNECTION:
42+
43+
- **IP address/host**: The polling IP or URL of the destination.
44+
- **IP port**: The IP port of the destination (default: *161*).
45+
- **Bus address**: The bus address of the device (default: *byPassProxy*).
46+
47+
SNMP Settings:
48+
49+
- **Get community string**: The community string used when reading values from the device (default: *public*).
50+
- **Set community string**: The community string used when setting values on the device (default: *private*).
51+
52+
### Web Interface
53+
54+
The web interface is only accessible when the client machine has network access to the product.
55+
56+
## How to use
57+
58+
### General
59+
60+
This page displays general information about the frame, such as the **Version**, **Location**, **Contact**, etc.
61+
62+
It also displays status information such as the **Power Supply Status**, **Temperature**, **Buzzer Status**, **Front Door Status**, etc.
63+
64+
### Network
65+
66+
This page contains the network detail parameters, such as **IP Address**, **Gateway**, etc.
67+
68+
### Time
69+
70+
This page contains the time detail parameters, such as **NTP Server IP Address**, **Date Time Mode**, etc.
71+
72+
### Trap Config
73+
74+
This page contains the trap configuration events. Here you can configure whether a trap is sent out when a particular event happens.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,140 @@
1+
---
2+
uid: Connector_help_Skyline_Health_Check_Manager
3+
---
4+
5+
# Skyline Health Check Manager
6+
7+
DMA systems have some resources like Disk Space, Memory Management, Boot Time, and more, that require systematic checks to ensure that the system has no ongoing issues and its performance is not affected.
8+
9+
Skyline Health Check Manager helps with these checks, with features to schedule subscription- and script-based tests on system and element parameters.
10+
11+
## About
12+
13+
Skyline Health Check Manager helps users with system checks of resources in a single window pane, with predefined threshold, element, and index filtering. It includes the following features:
14+
15+
- Map standalone and table column parameters of any protocol and any protocol version to a subscription.
16+
- Add, edit, or delete tests based on Automation scripts or subscriptions, which need to meet certain thresholds based on a set of available operations.
17+
- View all test results in a single pane of information in a table with details about failures.
18+
- Configure a schedule to run the tests with daily, weekly, and monthly options.
19+
20+
### Version Info
21+
22+
| Range | Features | Based on | System Impact |
23+
|--------------------|------------------|----------|---------------|
24+
| 1.0.0.x [SLC Main] | Initial version. | - | - |
25+
26+
### System Info
27+
28+
| Range | DCF Integration | Cassandra Compliant | Linked Components | Exported Components |
29+
|---------|-----------------|---------------------|-------------------|---------------------|
30+
| 1.0.0.x | No | Yes | - | |
31+
32+
## Configuration
33+
34+
### Connections
35+
36+
#### Virtual Connection
37+
38+
This connector uses a virtual connection and does not require any input during element creation.
39+
40+
### Automation Scripts
41+
42+
Make sure the **HealthCheckTableManager** Automation script is available in the DMS.
43+
44+
## How to use
45+
46+
### General
47+
48+
This page displays an overview of the test results over time, including the **Total Number Of Tests**, **Failure Rates**, and **Last Tests Date**.
49+
50+
### Test Configuration
51+
52+
#### Test Configuration Table
53+
54+
In the Test Configuration Table, you can create tests based on **Automation scripts** or **subscriptions** based on the Parameter Subscription table:
55+
56+
1. Right-click the Test Configuration Table.
57+
58+
1. Select **Add Test** in the context menu.
59+
60+
1. In the pop-up window (which is an interactive Automation script), enter the following information:
61+
62+
- **Test Type**: Select if the test is a script-based test or a subscription-based test.
63+
64+
- **Name**: Select the test name from the available scripts or subscriptions (based on the Test Type selection).
65+
66+
- **Operator**: Select the operator from the available options:
67+
68+
- Equal To (==)
69+
70+
- Not Equal To (!=)
71+
72+
- Less Than (<)
73+
74+
- Less or Equal Than (<=)
75+
76+
- Greater Than (>)
77+
78+
- Greater or Equal Than (>=)
79+
80+
- Between (BETWEEN)
81+
82+
- Not Between (NOT BETWEEN)
83+
84+
- **Threshold**: Provide the expected value that will be compared using the selected operator.
85+
86+
- **Element Filter**: Provide the filter for the elements using wildcard filtering.
87+
88+
- **Display Key Filter**: Provide the filter for the index (if applicable) using wildcard filtering.
89+
90+
- **Status**: Select this option if you want the test to be included for the next test run, or clear the option if it should not be included.
91+
92+
You can also edit tests via the context menu.
93+
94+
To delete tests, click the **Delete** button in the last column.
95+
96+
#### Parameter Subscription Table
97+
98+
In the Parameter Subscription Table, you can create subscriptions based on standalone or column parameters of any element present in the DMS.
99+
100+
1. Right-click the Parameter Subscription Table.
101+
102+
1. Select **Add Subscription** in the context menu.
103+
104+
1. In the pop-up window (which is an interactive Automation script), enter the following information:
105+
106+
- **Subscription Name**: Provide the name the subscription will have, which will be displayed during test creation.
107+
108+
- **Protocol**: Select the protocol name from a list of all the available protocols in the DMS.
109+
110+
- **Protocol Version**: Provide the protocol version for this subscription. The provided version will affect which elements are checked during test runs.
111+
112+
- **Parameter Type**: Select the parameter type: *Standalone* or *Table Parameter*.
113+
114+
- **Table**: Only available if Parameter Type is set to *Table Parameter*. Select the table that contains the parameter that is going to be mapped.
115+
116+
- **Parameter**: Select the parameter to be mapped from the available parameters from the selected connector and, if applicable, the selected table.
117+
118+
You can also edit subscriptions via the context menu.
119+
120+
To delete subscriptions, click the **Delete** button in the last column.
121+
122+
### Results
123+
124+
When the tests run, all enabled tests will be displayed in this table, with some information like Test Name, Failure Rate, Success and Failure count, details about failed tests, and the time of the test.
125+
126+
This table will be cleaned up based on the auto-delete time configured at the top of the page.
127+
128+
You can also choose to clean all results from the table manually.
129+
130+
### Configuration
131+
132+
The connector contains settings to customize its behavior:
133+
134+
- **Email Addresses**: Allows you to provide a list of emails that will receive a report of the test run, similar to the results table.
135+
136+
- **Recurrence**: Allows you to view and edit the recurrence set for the scheduled test runs, with *Daily*, *Weekly*, and *Monthly* options. You can always see when the next test run is due.
137+
138+
- **Longer Duration Time**: Allows you to specify a duration during which tests will run and get information on their failure rate.
139+
140+
- **Execute Tests**: You can start the execution of any tests even if it is not the scheduled time for the next run. This option will run all enabled tests and send the report emails.

0 commit comments

Comments
 (0)