User Instructions
45EN
DIRIS Digiware M-50 & M-70 - 548751C - SOCOMEC
15.4. SNMP ports
The DIRIS Digiware M-50 / M-70 is congured with standard SNMP ports to receive requests and send notications:
Port Description
161 Used to send and receive requests from the manager.
162 Used by the manager to receive notifications from the agent
Manager
U-30
@3
I-30
@4
I-30
@5
M-50/M-70
Digiware bus
Manager Port 161
Port 161 Response
Port 162 Traps
15.5. Retrieving data using the DIRIS Digiware M-50 / M-70 MIB le
The DIRIS Digiware M-50 / M-70 is compliant with MIB-II dened by the MIB standard RFC 1213 which denes the
following structure:
Root
OID Tree Example
iso (1)
org (3)
dod (6)
Internet (1)
directory (1)
mib-2 (1)
interfaces (2) ip (4)system (1)
mgm (2) experimental (3) private (4)
enterprise (1)
vendor X (2) vendor Y (9) SOCOMEC (4555)
The standard branches are under the same parent branch structure: 1.3.6.1.4.1
The “Private (4)” group enables vendors to dene private branches including the MIB OIDs of their own products.
Data related to SOCOMEC metering devices is located under the SOCOMEC enterprise category identied by OID
1.3.6.1.4.1.4555. This implies that all queries from a manager to SOCOMEC agents will start by the base path
1.3.6.1.4.1.4555.
Because the DIRIS Digiware is a multi-circuit system, the DIRIS Digiware M-50 / M-70 creates a dynamic table which
depends on the products connected downstream compatible with the DIRIS Digiware M-50 / M-70 and the loads
congured on each product.
After adding/deleting a downstream device or a load, make sure to update the topology of the M-50/M-70 gateway.
This
must be from the webserver via the “Devices” menu.
Example: The OID for “Current Inst I1” will return a value for all I-xx, B-xx, DIRIS A etc.. On the contrary, the OID for
“THD Inst I1” will return “0” for an I-30 or an I-31 module.
This implies that each OID can be associated with several products and several loads.