9.217 ETL-Stingray-FO-Base

This page describes the ETL-Stingray-Base device driver and its device window. The ETL-Stingray-Base device driver monitors and controls the base unit features and alarms of one ETL Stingray FO chassis. Beside the possibility to reset the unit this driver works as read-only.

Beside this base unit multiple instances of the various functional elements may be configured in the sat-nms M&C to handle all features of the chassis. All devices referring to the same physical device must be configured at the same device thread / interface to ensure that SNMP requests to the device do not overlap.

The drivers was tested with the following equipment:

• Model: SRY-C201-2U (16-card/2RU model)
• SW version: e363 2V3

The different available fibre optical cards of the ETL stingray series are:

• ETL-Stingray-FO-TX monitors and controls one single or dual channel FO transmit card.
• ETL-Stingray-FO-RX monitors and controls one single or dual channel FO receive card. Th Base unit as well as the available cards are prepared to support up to 16 individual FO cards.

Device window pages

The following table shows which device window pages are available with this individual device type. Tool-bar functions not mentioned here are described at the general description of device windows .

• --- The faults page.
• --- The device info page.
• --- The maintenance page. The configuration parameters described below are set at this page.

Configuration parameters

At the maintenance page of the device window there are a couple of configuration parameters which must be set to make the software talk to the device.

• parameter --- description
• address --- The SNMP address specification for the device. The full address specification consists of the following fields:aaa.bbb.ccc.ddd:pppp read-community write-community
  • aaa.bbb.ccc.ddd --- The IP address of the device in 'dotted quad' notation. This field is mandatory.
  • pppp --- The IP port number where the device accepts SNMP requests. The port number may be omitted, the driver uses the standard port 161 in this case.
  • read-community --- The SNMP read community name. This must match the read community expected by the device.
  • write-community --- The SNMP write community name. This must match the write community expected by the device. The write community name may be omitted, the driver uses the read community name for both, read and write in this case. If both community names are missing, the driver uses 'public' as a default for read and write community.

Variables defined by this device driver