Skip to content

Commit

Permalink
Merge branch 'SkylineCommunications:main' into main
Browse files Browse the repository at this point in the history
  • Loading branch information
jwoSkyline authored Nov 7, 2024
2 parents eb83368 + 25c50c1 commit ac86fb5
Show file tree
Hide file tree
Showing 34 changed files with 1,542 additions and 214 deletions.
48 changes: 48 additions & 0 deletions connector/doc/Advantech_ADAM6050_SNMP.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,48 @@
---
uid: Connector_help_Advantech_ADAM6050_SNMP
---

# Advantech ADAM6050 SNMP

The Advantech ADAM6050 SNMP connector enables monitoring and management of digital and analog inputs and outputs from Advantech ADAM6050 devices. By leveraging SNMP, the connector provides real-time data access, facilitating efficient monitoring and control within the DataMiner platform.

## About

### Version Info

| Range | 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

This connector uses an SNMP connection to communicate with the Advantech ADAM6050 device. During element creation, configure the following SNMP settings:

- **IP address/host**: The polling IP or URL of the destination.
- **IP port**: The IP port of the destination.
- **Get community string**: Community string for reading device values (default: *public*).
- **Set community string**: Community string for writing values to the device (default: *private*).

### Web Interface

The web interface is accessible when the client machine has network access to the device.

## How to use

When an element has been created with this connector, you will be able to monitor and control input and output values for the Advantech ADAM6050 device in real time. The connector will retrieve device data over SNMP and display it in DataMiner, allowing you to manage device statuses effectively.
333 changes: 333 additions & 0 deletions connector/doc/Appear_X_Platform.md

Large diffs are not rendered by default.

58 changes: 58 additions & 0 deletions connector/doc/Asentria_SiteBoss_360.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,58 @@
---
uid: Connector_help_Asentria_SiteBoss_360
---

# Asentria SiteBoss 360

This connector allows you to monitor general parameters (e.g. system uptime, location, tech support details, etc.) as well as input and output interfaces such as contacts, relays, sensors, and analog inputs.

## About

### Version Info

| Range | Features | Based on | System Impact |
|--------------------|-----------------------------------|----------|---------------|
| 1.0.0.x [SLC Main] | - SNMP monitoring<br>- SNMP traps | - | - |

### 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

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.
- **IP port**: The IP port of the destination (default: *161*).
- **Bus address**: The bus address of the device.

SNMP Settings:

- **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

The connector is divided in three main parts:

- A single **General** page with standard device information.
- Several pages with information regarding data traffic: **Interface**, **Ports**, and **Ethernet**.
- The specific device functions, such as the **power**, **battery**, and **event sensor** information

All tables are polled over SNMP.

For event sensor information, information is updated whenever traps are received to ensure accurate alarm monitoring.
46 changes: 31 additions & 15 deletions connector/doc/Aviat_Networks_Provision.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,7 @@ In addition, the connector offers several possibilities for **alarm monitoring**
| 1.0.0.x | Initial version | No | Yes |
| 1.0.1.x | Adaptation to new SoW | No | Yes |
| 1.0.2.x | Primary key is based on rowkey from change request | No | Yes |
| 2.0.0.x | EPM compatible | No | Yes |

### Product Info

Expand All @@ -32,18 +33,19 @@ In addition, the connector offers several possibilities for **alarm monitoring**
| 1.0.0.x | 6.10 |
| 1.0.1.x | 6.10 |
| 1.0.2.x | |
| 2.0.0.x | 6.10 |

### Exported connectors
### Exported connectors - Range 1.0.2.x

| Exported Connector | Description |
|-----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Exported Connector | Description |
|--|--|
| Aviat Networks Provision - Device | Alarms of each device connected to the Aviat Networks Provision. A table with information related to the alarm (event ID, severity, location, etc.) is displayed. |

## Installation and configuration
## Configuration

### Creation
### Connections

#### SNMP Trap Input connection
#### SNMP Connection - Trap Input

This connector uses a Simple Network Management Protocol (SNMP) connection and requires the following input during element creation:

Expand All @@ -60,13 +62,13 @@ SNMP Settings:

## Usage (1.0.0.1)

### Traps
### Traps Page

SNMP traps received from the EMS are displayed in the **Traps Table**. The **Number of Traps** parameter displays how many rows are available in this table. You can remove specific rows by clicking the **Delete Trap** button (available in the last column of the table).

Additional configuration is available on the **Configuration page** (see below).

### Known IP Addresses
### Known IP Addresses Page

This page displays the **Devices Table**, which contains an overview of all the devices known by the connector. Note that every incoming trap has a source IP (see below) and this source IP address is used to match the trap to a specific device. Only traps with a source IP address known by the connector will be processed; any other traps will be discarded.

Expand All @@ -78,7 +80,7 @@ The **Number of Known IP Addresses** parameter at the top of this page displays

To manage the devices further, e.g. to delete multiple devices or create or delete all DVEs at once, refer to the Configuration page (see below).

### Configuration
### Configuration Page

This page consists of several sections, corresponding to different aspects of the configuration.

Expand Down Expand Up @@ -119,7 +121,7 @@ Please note the following:

This section also contains the **DVE Table** page button, which opens a subpage with a table that displays all DVEs created by the connector. The last column of this table contains a **Delete DVE** button, which can be used to erase DVEs one by one.

### Debug
### Debug Page

This page displays the **Deleted Traps Table**, which lists the stored deleted traps, ordered from young to old. Above the table, the **Number of Deleted Traps** parameter indicates the number of rows in the table. For more information on how to further manage the traps, delete multiple traps or configure the processing, refer to the **Configuration page**.

Expand All @@ -134,21 +136,21 @@ This page displays the **Deleted Traps Table**, which lists the stored deleted t

## Usage (1.0.1.1)

### Traps
### Traps Page

On this page, the **NorthBound Status** parameter will display an error if the Northbound Status Trap (heartbeat) is not received in time, i.e. within the heartbeat interval, which has to be the same as the value set in the **Heartbeat Time Interval** parameter.

The **display key** of the traps table is obtained by concatenating the **Service ID** and **Event Name** column parameters.

### Known IP Addresses
### Known IP Addresses Page

In last column of the Device Table, **Create DVE**, you can enable or disable the creation of a single Dynamic Virtual Element (DVE). If DVE creation is enabled, a new element with the same name as the Device Name will appear in the Surveyor in the view that corresponds to the Site Name.

### Service
### Service Page

This page displays the **Service Table**. Each entry in this table represents a known **Service ID**, which is linked to the respective Device Name. The page also displays the **DAC/Port** parameter, as the concatenation of these three parameters is used as the **Index** of the table.

### Configuration
### Configuration Page

This page consists of several sections, corresponding to different aspects of the configuration.

Expand All @@ -169,8 +171,22 @@ If a provision file is imported and a mismatch is detected between one of the en

## Usage (1.0.2.1)

### Traps
### Traps Page

On this page, the **NorthBound Status** parameter will display an error if the Northbound Status Trap (heartbeat) is not received in time, i.e. within the heartbeat interval, which has to be the same as the value set in the **Heartbeat Time Interval** parameter.

The **primary key** of the traps table is obtained by concatenating the **Service ID** and **Event Name** column parameters.

## Usage (2.0.0.X)

### Configuration Page

This page contains the following parameters:

- **Entity Import Directory**: Directory where the element will import the devices information from EPM.

- **Entity Export Directory**: Directory from which the element will export the devices inventory information to EPM.

- **System Username**: Username used to retrieve files from a remote directory.

- **System Password**: Password used to retrieve files from a remote directory.
12 changes: 6 additions & 6 deletions connector/doc/Cisco_CBR-8.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,13 +16,13 @@ The connector uses regular timers that trigger every 60 and 120 seconds, as well

| Range | Description | DCF Integration | Cassandra Compliant |
|--|--|--|--|
| 1.0.1.x | Initial version. | No | No |
| 1.0.2.x | Implemented changes on the Physical Upstream Channel Table and Upstream Bounding table. | No | No |
| 1.0.3.x | Index of the Measurement Upstream Channel table changed to the instance of the channel. | No | Yes |
| 1.0.4.x | DCF feature added. | Yes | Yes |
| 2.0.0.x | Connector review. Added CCAP parameters. | No | Yes |
| 1.0.1.x [Deprecated] | Initial version. | No | No |
| 1.0.2.x [Deprecated] | Implemented changes on the Physical Upstream Channel Table and Upstream Bounding table. | No | No |
| 1.0.3.x [Deprecated] | Index of the Measurement Upstream Channel table changed to the instance of the channel. | No | Yes |
| 1.0.4.x [DCF] | DCF feature added. | Yes | Yes |
| 2.0.0.x [Deprecated] | Connector review. Added CCAP parameters. | No | Yes |
| 2.0.1.x [SLC Main] | Split up MPEG table into 4 tables because of possibility of multiple programs per transport stream. | No | Yes |
| 3.0.0.x | Customer specific branch. | No | Yes |
| 3.0.0.x [Deprecated] | Customer-specific branch. | No | Yes |

### Product Info

Expand Down
9 changes: 6 additions & 3 deletions connector/doc/EVS_Neuron_NAP_-_COMPRESS.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,21 +10,24 @@ This connector is intended to be used with the Neuron COMPRESS, which provides t

### Version Info

| Range | Key Features | Based on | System Impact |
|----------------------|------------------|--------------|-------------------|
| 1.0.0.x [SLC Main] | Initial version. | - | - |
| Range | Key Features | Based on | System Impact |
|----------------------|------------------|--------------|----------------------------------------------------------|
| 1.0.0.x | Initial version. | - | - |
| 1.1.0.x [SLC Main] | Support v5.9.1 | 1.0.0.2 | Possible impact on alarms, trending, and Visual Overview |

### Product Info

| Range | Supported Firmware |
|-----------|------------------------|
| 1.0.0.x | 5.0.0 |
| 1.1.0.x | 5.9.1 |

### System Info

| Range | DCF Integration | Cassandra Compliant | Linked Components | Exported Components |
|-----------|---------------------|-------------------------|-----------------------|-------------------------|
| 1.0.0.x | No | Yes | - | - |
| 1.1.0.x | No | Yes | - | - |

## Configuration

Expand Down
2 changes: 1 addition & 1 deletion connector/doc/Harmonic_Proview_PVR8130.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ The connector is used to control and monitor the Harmonic Proview PVR8000.
| **Range** | **Description** | **DCF Integration** | **Cassandra Compliant** |
|----------------------|------------------------------------------------------------------|---------------------|-------------------------|
| 1.0.0.x | Initial version. | No | Yes |
| 1.0.1.x [SLC Main] | Combine DVB-S2 port receiver and carrier parameters into a table | No | Yes |
| 1.0.1.x [SLC Main] | Combine DVB-S2 port receiver and carrier parameters into a table | Yes | Yes |

### Product Info

Expand Down
10 changes: 5 additions & 5 deletions connector/doc/Harmonic_RD9000_Decoder.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,10 +12,10 @@ This SNMP connector contains different tables that allow the user to monitor and

### Version Info

| Range | Key Features | Based on | System Impact |
|--------------------|--------------------------------------------------------------------------------------------------|----------|--------------------------------------------------------|
| 1.0.0.x | - Monitoring. <br>- Configuration of both inputs and outputs. | - | - |
| 1.0.1.x [SLC Main] | - Renamed "Primary SRC" to "Primary Source" (same change applied to "Backup SRC"). <br>- Updated "Ts Bitrate" from bps to Mbps. <br>- Modified "Ts Sync" from "Lock Locked" to "Locked" and from "Lock Unlock" to "Unlock". <br>- Made "Primary Source" a dropdown, dependent on the "Label" column in the "Input Source" table. <br>- Updated display keys in the "Input Source" and "MPEG IP Receive" tables. | 1.0.0.4 | Display key updates and parameter name/value changes. |
| Range | Key Features | Based on | System Impact |
|--------------------|------------------------------------------------------------------------------------------------------------------------------|----------|--------------------------------------------------------|
| 1.0.0.x | - Monitoring. <br>- Configuration of both inputs and outputs. | - | - |
| 1.0.1.x [SLC Main] | - Renamed "Primary SRC" to "Primary Source" (same change applied to "Backup SRC"). <br>- Updated "Ts Bitrate" from bps to Mbps. <br>- Modified "Ts Sync" from "Lock Locked" to "Locked" and from "Lock Unlock" to "Unlock". <br>- Made "Primary Source" a dropdown box, dependent on the "Label" column in the "Input Source" table. <br>- Updated display keys in the "Input Source" and "MPEG IP Receive" tables. <br>- DCF interfaces added. | 1.0.0.4 | Display key updates and parameter name/value changes. |

### Product Info

Expand All @@ -29,7 +29,7 @@ This SNMP connector contains different tables that allow the user to monitor and
| Range | DCF Integration | Cassandra Compliant | Linked Components | Exported Components |
|-----------|---------------------|-------------------------|-----------------------|-------------------------|
| 1.0.0.x | No | Yes | - | - |
| 1.0.1.x | No | Yes | - | - |
| 1.0.1.x | Yes | Yes | - | - |

## Configuration

Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
uid: Connector_help_Icinga_2
uid: Connector_help_Icinga_Icinga_2
---

# Icinga 2
Expand Down
16 changes: 16 additions & 0 deletions connector/doc/Infoblox_NIOS_Platform.md
Original file line number Diff line number Diff line change
Expand Up @@ -67,3 +67,19 @@ The Infoblox NIOS Platform connector uses both SNMP and HTTP connections to gath
The HTTP connection provides access to important KPIs related to networks, members, and nodes, such as high-availability status and utilization metrics.

The connector also allows users to verify the license validity for the platform.

### Single Range Switching

In the **Network Ranges** table, you can switch a specific range to a different member. This is done through the **Member Name** column, which shows the currently active member for each range. Clicking on a member's name will open a dropdown list with all available members. To complete the switch, you only need to select a new member from the list.

### Bulk Range Switching

You can switch multiple ranges in bulk via the **Switch** subpage of the **Network Ranges** page.

On this subpage, select an **Active Member** and a **Switch Member** from their respective dropdown lists, which display all available members.

Once you click the **Switch** button, all ranges currently assigned to the selected **Active Member** will be reassigned to the specified **Switch Member**.

### Default Switching

You can reset all ranges to their default member, as listed in the **IBX DHCP Member** column of the **Network Ranges** table. To do this, navigate to the **Switch** subpage of the **Network Ranges** page and click the **Switch Default** button.
Loading

0 comments on commit ac86fb5

Please sign in to comment.