[DKSF 48.2 IU] Manage device with SNMP v1
A device supports configuring parameters and management via an SNMP v1 protocol. You can find more information about an SNMP protocol on the links: OID supported by a device can be found in a MIB file DKSF 48.2.X.X MB, which is downloaded from the web site www.netping.ru A device supports: It is necessary to configure the following parameters using a web interface of a device to access a device via an SNMP v1 protocol: It is necessary to configure the following parameters using a web interface for a device to send TRAP messages via an SNMP v1 protocol: OID that are supported by a device can be found in a MIB file DKSF_48.2.3.A-1_MB.mib, which is on the page of a manufacturer's web site that describes a device. A description of the most often used OID, which are supported by a device, is represented in the table below: OID Name Type Access Description RFC1213 .1.3.6.1.2.1.1.1.0 sysDescr.0 OctetString READ A textual description of a device .1.3.6.1.2.1.1.2.0 sysObjectID.0 OID READ A number of a branch with device parameters is always .1.3.6.1.4.1.25728 .1.3.6.1.2.1.1.3.0 sysUpTime.0 TimeTicks READ Time from the moment of the last turning on a device in hundredths of a second .1.3.6.1.2.1.1.4.0 sysContact.0 OctetString READ/ WRITE Contact data, usually an administrator's email .1.3.6.1.2.1.1.5.0 sysName.0 OctetString READ/ WRITE A domain name of a device .1.3.6.1.2.1.1.6.0 sysLocation.0 OctetString READ/ WRITE A location of a device .1.3.6.1.2.1.1.7.0 sysServices.0 Integer READ A binary representation of this OID is a set of supported services. Always 72, a device is a destination host. .1.3.6.1.2.1.2.1.0 ifNumber.0 Integer READ Amount of network interfaces of a device .1.3.6.1.2.1.2.2.1.1.1 ifIndex.1 Integer .1.3.6.1.2.1.2.2.1.3.1 ifType.1 Integer READ A device network interface type .1.3.6.1.2.1.2.2.1.4.1 ifMtu.1 Integer READ A size of a package over a network interface. Always 1514 .1.3.6.1.2.1.2.2.1.5.1 ifSpeed.1 Integer READ A network interface speed. Always 100000000 .1.3.6.1.2.1.2.2.1.6.1 ifPhysAddress.1 OctetString READ МАС address of a device NetPing MIB .1.3.6.1.4.1.25728.911.1.0 npSoftReboot Integer READ/ Soft reset of a device when writing a value 1 .1.3.6.1.4.1.25728.911.2.0 npResetStack Integer READ/ Soft reset of a network interface when writing a value 1 .1.3.6.1.4.1.25728.911.3.0 npForceReboot Integer READ/ Fast forced software reboot of a device when writing a value 1 .1.3.6.1.4.1.25728.3800.1.1.0 npGsmFailed Integer READ A status of a built-in GSM modem. 0 – Ok 1 – Failed (no connection) 2 – FatalError (unrecoverable error, a modem is locked) .1.3.6.1.4.1.25728.3800.1.2.0 npGsmRegistration Integer READ A status of a connection to a GSM network 0 – impossible 1 – homeNetwork 2 – searching 3 – denied 4 – unknown 5 – roaming 255 – infoUpdate .1.3.6.1.4.1.25728.3800.1.3.0 npGsmStrength Integer READ A level of a GSM signal 0…31 = 0% … 100% 99 – unknown 255 – updating info .1.3.6.1.4.1.25728.5500.5.1.1.n nRelayN.n Integer READ Power supply channels index, where n – is a number from 1 to 8 .1.3.6.1.4.1.25728.5500.5.1.2.n npRelayMode.n Integer READ- An operation schedule of a power supply channel, where n – is a number of a channel, from 1 to 8. The following modes are available: 0 – Manually off; 4 – A channel is managed by logic. .1.3.6.1.4.1.25728.5500.5.1.3.n npRelayStartReset.n Integer READ- OID for a forced reset of a channel, where n – is a channel number. Write a value 1 to turn off a channel for 15 seconds. .1.3.6.1.4.1.25728.5500.5.1.6.n npRelayMemo.n DisplayString READ A memo of a power supply channel, where n – is a channel number. .1.3.6.1.4.1.25728.5500.5.1.15.n npRelayState.n Integer READ A current relay status, where n – is a channel number. 0 – A relay is turned off 1 – A relay is turned on .1.3.6.1.4.1.25728.5500.5.1.16.n npRelayPowered.n Integer READ Presence of a power suuply at a relay output, where n – is a channel number. 0 – No power supply (a relay is turned off or there is no power supply on the input) 1 – Power supply is available .1.3.6.1.4.1.25728.5800.3.1.1.n npPwrChannelN.n Integer READ Watchdog channels index, where n – is a number from 1 to 4 .1.3.6.1.4.1.25728.5800.3.1.2.n npPwrStartReset.n Integer READ- Outdated. It is not recommended to use Write «1» to reset a power supply channel 1. When reading, the following values n of a socket status are possible: 0 – normal status; .1.3.6.1.4.1.25728.5800.3.1.4.n npPwrResetsCounter.n Integer READ/ A counter of overloads of a Watchdog reboots, where n – is a channel number, from 1 to 4. To null a counter, there is a need to write 0. .1.3.6.1.4.1.25728.5800.3.1.5.n npPwrRepeatingResetsCounter.n Integer READ A counter of a continious resets of a Watchdog channel, where n – is a channel number, from 1 to 4. .1.3.6.1.4.1.25728.5800.3.1.6.n npPwrMemo.n OctetString READ A value of the field “Memo” of a Watchdog channel, where n – is a channel number. .1.3.6.1.4.1.25728.7900.1.1.0 npIrPlayCmd.0 Integer READ/ There is a need to write a number of an IR command to send an IR command. .1.3.6.1.4.1.25728.7900.1.2.0 npIrReset.0 Integer READ/ After resetting an IR transceiver write 1. After a reset, specify an IR command and check an IP status .1.3.6.1.4.1.25728.7900.1.3.0 npIrStatus.0 Integer READ An IR transceiver status .1.3.6.1.4.1.25728.8800.1.1.2.n npThermoValue.n Integer READ Reading a current temperature value on a temperature sensor n; possible values are n – 1..8 .1.3.6.1.4.1.25728.8800.1.1.3.n npThermoStatus.n Integer READ Reading a temperature sensor status value n; possible values are n – 1..8 .1.3.6.1.4.1.25728.8800.1.1.4.n npThermoLow.n Integer READ Reading a lower threshold of a temperature range of a temperature sensor n; possible values are n – 1..8 .1.3.6.1.4.1.25728.8800.1.1.5.n npThermoHigh.n Integer READ Reading an upper threshold of a temperature range of a temperature sensor n; possible values are n – 1..8 .1.3.6.1.4.1.25728.8800.1.1.6.n npThermoMemo.n DisplayString READ Reading values of a field "Memo” of a temperature sensor n; possible values are n – 1..8 .1.3.6.1.4.1.25728.8900.1.1.2.n npIoLevelIn.n Integer READ Reading a current status value of an input-output line n; possible values are n – 1..4 .1.3.6.1.4.1.25728.8900.1.1.3.n npIoLevelOut.n Integer READ/ Reading a current status value of an input-output line n in a mode “output”; possible values are n – 1..4 .1.3.6.1.4.1.25728.8900.1.1.6.n npIoMemo.n DisplayString READ Reading a value of a field "Memo” of an input-output line n; possible values are n – 1..4. .1.3.6.1.4.1.25728.8900.1.1.9.n npIoPulseCounter.n Counter32 READ/ Reading a value of an impulse counter on an input-output line n; possible values are n – 1..4. .1.3.6.1.4.1.25728.8900.1.1.12.n npIoSinglePulseDuration.n Integer READ/ Reading a value of duration of one impulse on an output of an input-output line n in an output mode (in milliseconds), possible values are n – 1..4. .1.3.6.1.4.1.25728.8900.1.1.13.n npIoSinglePulseStart.n Integer READ/ Issuing a single impulse on an output of an input-output line n in an output mode; possible values are – 1..4. To issue it, there is a need to write a value 1. A formal description of TRAPs can be found in a MIB file, attached to a firmware. TRAP is sent in a format SNMP v1, at the same time a description in a MIB file has a format SNMP v2c. An unambiguous identification of mutual correspondence of traps for v1 and v2c is described in RFC3584 “Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework”. Programs for processing SNMP notifications usually do a conversion between two formats easily. To send TRAPs, there is a need: NpIoTrap identification: SNMP v1 enterprise .1.3.6.1.4.1.25728.8900.2 SNMP v1 generic-trap enterpriseSpecific(6) SNMP v1 specific-trap 1 SNMP v2 snmpTrapOID .1.3.6.1.4.1.25728.8900.2.0.1 Variables in npIoTrap (varbind list) OID Data Type Description .1.3.6.1.4.1.25728.8900.2.1.0 Integer An IO line number (starting from 1), changing of which caused sending a TRAP .1.3.6.1.4.1.25728.8900.2.2.0 Integer A value of a logic level on IO line (0 or 1) .1.3.6.1.4.1.25728.8900.2.6.0 Octet String A memo (a textual description of a line, encoding win1251) .1.3.6.1.4.1.25728.90.1.0 OctetString Email where a message needs to be forwarded (for a Netping service of messages forwarding). NpThermoTrap identification SNMP v1 enterprise .1.3.6.1.4.1.25728.8800.2 SNMP v1 generic-trap enterpriseSpecific(6) SNMP v1 specific-trap 1 SNMP v2 snmpTrapOID .1.3.6.1.4.1.25728.8800.2.0.1 Variables in npThermoTrap (varbind list) OID Data Type Description .1.3.6.1.4.1.25728.8800.2.1.0 Integer A sensor number (1..8), changing status of which causes sending a TRAP .1.3.6.1.4.1.25728.8800.2.2.0 Integer A current temperature value, °C .1.3.6.1.4.1.25728.8800.2.3.0 Integer A sensor status: .1.3.6.1.4.1.25728.8800.2.4.0 Integer Lower limit of a norm, °C .1.3.6.1.4.1.25728.8800.2.5.0 Integer Upper limit of a norm, °C .1.3.6.1.4.1.25728.8800.2.6.0 Octet String A memo (a textual description of installation place of a temperature sensor, encoding win1251) .1.3.6.1.4.1.25728.90.1.0 OctetString Email where messages are forwarded using a Netping's messages forwarding service.SNMP Protocol Configuration
Supported OID
WRITE
WRITE
WRITE
WRIRE
1 – Manually on;
3 – A channel is managed by a watchdog and/or a schedule
WRITE
WRIRE
1 – reset status;
2 – pause status after a reset.
WRITE
WRITE
WRITE
WRITE
WRITE
A counter is incremented on a rising signal of an impulse after filtering short impulses.
For a forced counter nulling there is a need to write 0.
A value of a counter is nulled as well when a power supply is turned off.
WRITE
A range of duration values is from 100 ms to 25500 ms, a minimum step is 100 milliseconds.
WRITE
A duration of an impulse is specified in a field “An impulse duration” on the page of configuring an input-output line. SNMP Trap Support
SNMP TRAP when an Input IO Line Level is Changed
SNMP TRAP when a Temperature Sensor Status is Changed
0 - failure or a sensor disconnection,
1 - a temperature is below normal,
2 - a temperature is normal
3 - a temperature is above normal