Generic SNMP Parameter Controllable Device

Driver Maturity

Production

Recommended for normal production use.

Caution

Compatibility Note: This information is a general guide and may be incomplete, may not match a specific project implementation, and is subject to change as supported products and versions evolve. Confirm the exact implementation and requirements for each project with Riedel and the relevant equipment vendor, then validate the required functions end to end in the target environment before deployment.

Minimum hi Version: v2.7.5

Overview

The Generic SNMP integration reads and writes SNMPv2c objects described by imported MIB files. Pinned values are polled at the configured interval.

Network Requirements

Connection Model: hi sends SNMP requests to the configured agent.
Multicast / Unicast: Unicast only.
VLAN / IGMP: No multicast configuration is required.
Bandwidth: Polled management traffic only.
IP Version: IPv4.
Firewall: Permit outbound UDP 161 from hi and the agent responses, and ICMP echo request and reply between hi and the device. hi treats a device that does not answer ICMP echo as offline.

Standards Conformance

Standard	Conformance	Notes
SNMP (IETF)	SNMPv2c	Community-based management over UDP

Operator Workflow

UI Surface in hi: Topology, Inventory, and Parameter Control
Parameter Semantics: Imported MIB objects can be browsed and pinned as hi parameters.

Connection Details

Property	Value
Protocol	SNMPv2c
Transport	UDP
Default Port	161
Authentication	Separate SNMPv2c read and write community strings
Encryption in Transit	None - SNMPv2c community strings and payloads are not encrypted
Connection Model	UDP request and response with polling
Required License	hiBase
Traffic Flow	Outbound requests with inbound responses

Required Configuration

Parameter	Description	Default
Host / IP Address	IPv4 address of the SNMP device	-
Port	SNMP UDP port	161
Read Community String	Community used for read operations. Replace the default.	public
Write Community String	Community used for write operations. Replace the default.	private
MIB file	MIB definition used to build the parameter tree. Upload it after the Node is created.	-
Polling Interval (ms)	Interval for reading pinned values	5,000 ms
Wait Between Request (ms)	Delay between parameter-value requests	50 ms

Device-Side Setup

Follow Generic SNMP Parameter Controllable Device Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Feature	Access	Exposed Operation and Scope
Imported MIB Objects	Per-parameter access	Read accessible OIDs and write only OIDs the imported MIB describes as writable. Read-only OIDs are presented as read-only.

Known Limitations

The imported MIB objects must match the connected device.
SNMPv2c community strings and payloads are sent in plaintext. Isolate access to trusted management networks.
Objects are addressed by OID and typed by the SNMP data type that the MIB declares. A MIB that does not match the firmware of the device can show objects that the agent does not implement.
An agent answers only for the objects and views that its community string allows. A community can read an object that it cannot write.
If reads succeed but writes fail, confirm that the OID is writable and that the configured write community has permission.
hi reads values with an SNMPv1 Get request using the read community, and falls back to an SNMPv2c Get-Next request. Writes use SNMPv2c Set with the write community. Configure the agent to accept both SNMPv1 and SNMPv2c requests from hi.
hi sends writes as INTEGER for integer and enumerated objects, and as OCTET STRING for all other object types.
hi presents an object as read-only when its MIB MAX-ACCESS value contains "not" or "only", for example read-only or not-accessible.

What's Not Supported

SNMPv3 USM authentication and privacy.
SNMP traps or informs.
Firmware updates, base network configuration, and MIB authoring.

Trademarks

Note

SNMP is an IETF standard.

All product names, logos, and brands are property of their respective owners. Copyright in third-party software and materials remains with the respective owners. Use of these names does not imply endorsement.