56
EN
DIRIS Digiware D-50 & D-70 - 548088B - SOCOMEC
Annex I - 4. SNMP ports
The DIRIS Digiware D-50 / D-70 is configured with standard SNMP ports to receive requests and send notifications:
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
D-50/D-70
Digiware bus
Manager Port 161
Port 161 Response
Port 162 Traps
Annex I - 5.
Retrieving data using the DIRIS Digiware D-50 / D-70 MIB file
The DIRIS Digiware D-50 / D-70 is compliant with MIB-II defined by the MIB standard RFC 1213 which defines 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 define private branches including the MIB OIDs of their own products.
Data related to SOCOMEC metering devices is located under the SOCOMEC enterprise category identified 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 D-50 / D-70 creates a dynamic table which
depends on the products connected downstream compatible with the DIRIS Digiware D-50 / D-70 and the loads
configured on each product.
After adding/deleting a downstream device or a load, make sure to update the topology of the D-70 display. This can be
done either directly from the display or from Webview:
•
Add or delete a device
• Refresh the loads
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.
