Template:Networking rutos manual snmp: Difference between revisions
m (→Trap Settings) |
Tag: Rollback |
||
| Line 254: | Line 254: | ||
<b>SNMP Traps</b> are used to send alert messages to a central collector, the “SNMP manager” when an important event happens. A benefit of using Traps for reporting alarms is that they trigger instantaneously, rather than waiting for a status request from the manager. | <b>SNMP Traps</b> are used to send alert messages to a central collector, the “SNMP manager” when an important event happens. A benefit of using Traps for reporting alarms is that they trigger instantaneously, rather than waiting for a status request from the manager. | ||
Trap settings page is divided in two sections - <b>Trap service settings</b> and <b>Trap rules</b>. Trap service settings lets you manage | Trap settings page is divided in two sections - <b>Trap service settings</b> and <b>Trap rules</b>. Trap service settings lets you manage hosts which will get configured alert messages, Trap rules lets you manage rules which when triggered will send alerts. | ||
===Trap Service Settings=== | ===Trap Service Settings=== | ||
---- | ---- | ||
The <b>Trap Service Settings</b> is used to manage | The <b>Trap Service Settings</b> is used to manage <b>hosts</b> which will be alerted when an SNMP trap is triggered. The host list is empty by default thus, to begin configuration you must first create at least one host. | ||
[[File: | Click the 'Add' button at the bottom-right side of the table to create a new host. | ||
[[File:Networking_rutos_manual_snmp_trap_settings_trap_service_settings_add_button.png|border|class=tlt-border]] | |||
The newly added Host configuration should look similar to this: | |||
[[File:Networking_rutos_manual_snmp_trap_settings_trap_service_settings_configuration.png|border|class=tlt-border]] | |||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
| Line 269: | Line 275: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Host/IP</td> | ||
<td>url | ip; default: <b>none</b></td> | <td>url | ip; default: <b>none</b></td> | ||
<td>Hostname or IP address to transfer SNMP traffic to.</td> | <td>Hostname or IP address to transfer SNMP traffic to.</td> | ||
| Line 280: | Line 281: | ||
<tr> | <tr> | ||
<td>Port</td> | <td>Port</td> | ||
<td>integer [ | <td>integer [0..65535]; default: <b>162</b></td> | ||
<td>Trap host's port number.</td> | <td>Trap host's port number.</td> | ||
</tr> | </tr> | ||
| Line 287: | Line 288: | ||
<td>string; default: <b>Public</b></td> | <td>string; default: <b>Public</b></td> | ||
<td>Name of the community to which the trap belongs.</td> | <td>Name of the community to which the trap belongs.</td> | ||
</tr> | |||
<tr> | |||
<td>Delete</td> | |||
<td>- (interactive button)</td> | |||
<td>Deletes the host next to the button.</td> | |||
</tr> | |||
<tr> | |||
<td>off/on slider</td> | |||
<td>off | on; default: <b>off</b></td> | |||
<td>Turns the host on or off. SNMP traffic is only sent to enabled hosts.</td> | |||
</tr> | </tr> | ||
</table> | </table> | ||
| Line 296: | Line 307: | ||
You can create a new trap rule by clicking the 'Add' button. | You can create a new trap rule by clicking the 'Add' button. | ||
[[File: | [[File:Networking_rutos_manual_snmp_trap_settings_trap_rules_add_button.png|border|class=tlt-border]] | ||
You should be redirected to the rule's configuration page which should look something like this: | You should be redirected to the rule's configuration page which should look something like this: | ||
[[File:Networking_rutos_manual_snmp_trap_settings_trap_rules_modify_trap_rule_mobile_{{{mobile}}} | [[File:Networking_rutos_manual_snmp_trap_settings_trap_rules_modify_trap_rule_mobile_{{{mobile}}}.png|border|class=tlt-border]] | ||
Above is an example of what rule configuration window looks like. Below is a table with detailed explanations on how to configure the rule and what each of the fields mean. | Above is an example of what rule configuration window looks like. Below is a table with detailed explanations on how to configure the rule and what each of the fields mean. | ||
To avoid redundancy, screenshots for the other rules will not be provided, since the structures, syntax and the overall look of the configuration windows for each rule are very similar. Instead, only tables containing information on how to edit each rule will be provided. | To avoid redundancy, screenshots for the other rules will not be provided, since the structures, syntax and the overall look of the configuration windows for each rule are very similar. Instead, only tables containing information on how to edit each rule will be provided. | ||
{{#ifeq: {{{mobile}}} | 1 | | {{#ifeq: {{{mobile}}} | 1 | | ||
==== | ====Signal strength==== | ||
---- | ---- | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
| Line 316: | Line 326: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Enable</td> | ||
<td> | <td>off <nowiki>|</nowiki> on; default: <b>off</b></td> | ||
<td> | <td>Enable or disable this rule.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Action</td> | ||
<td>Signal strength | <td>Signal strength trap</td> | ||
<td> | <td>Rule will be triggered if signal strength falls below specified number.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 343: | Line 342: | ||
</table> | </table> | ||
<br> | <br> | ||
====Connection type==== | |||
== | |||
---- | ---- | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
| Line 358: | Line 355: | ||
<td>Enable or disable this rule.</td> | <td>Enable or disable this rule.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Action</td> | ||
<td> | <td>Connection type trap</td> | ||
<td> | <td>Rule will be triggered when connection type will change.</td> | ||
</tr> | </tr> | ||
</table> | |||
<br>|}} | |||
====Input/Output==== | |||
---- | |||
<table class="nd-mantable"> | |||
<tr> | <tr> | ||
< | <th>field name</th> | ||
< | <th>value1</th> | ||
< | <th>description</th> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Enable</td> | ||
<td> | <td>off | on; default: <b>off</b></td> | ||
<td> | <td>Enable or disable this rule.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Action</td> | ||
<td> | <td>Input/Output trap</td> | ||
<td>Rule will be triggered when specified input or output state will change.</td> | |||
<td> | |||
</tr> | </tr> | ||
{{#switch:{{{series}}} | |||
|RUTX|RUTM = | |||
<tr> | <tr> | ||
<td> | <td>Input/Output type</td> | ||
<td>Input/Output; default: <b>Input/Output</b></td> | |||
<td> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | <td>Which type of Inputs and Outputs to use in this rule.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Input/Output name</td> | ||
<td>Output(4) {{!}} Input(3); default: <b>Output(4)</b></td> | |||
<td> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | <td>Which type of Inputs and Outputs to use in this rule.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>State change</td> | <td>State change</td> | ||
<td>High level {{!}} Low level {{!}} Both; default: <b | <td>High level {{!}} Low level {{!}} Both; default: <b>High level</b></td> | ||
<td>On which Input/Output state will this rule be triggered.</td> | <td>On which Input/Output state will this rule be triggered.</td> | ||
</tr> | </tr> | ||
|TRB2 = | |||
<tr> | <tr> | ||
<td> | <td>Input/Output type</td> | ||
<td><span style="color:blue">Input/Output</span> {{!}} <span style="color:red">ADC</span>; default: <b>Input/Output</b></td> | |||
<td><span style="color:blue"> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | <td>Which type of Inputs and Outputs to use in this rule.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td><span style="color:blue">Input/Output:</span> Input/Output name</td> | ||
<td>Configurable Input/Output([2..4]); default: <b>Configurable Input/Output(2)</b></td> | |||
<td> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | <td>Which type of Inputs and Outputs to use in this rule.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>State change</td> | <td><span style="color:blue">Input/Output:</span> State change</td> | ||
<td>High level {{!}} Low level {{!}} Both; default: <b>Both</b></td> | <td>High level {{!}} Low level {{!}} Both; default: <b>Both</b></td> | ||
<td>On which Input/Output state will this rule be triggered.</td> | <td>On which Input/Output state will this rule be triggered.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td><span style="color:red"> | <td><span style="color:red">ADC:</span> Input/Output name</td> | ||
<td>ADC; default: <b>ADC</b></td> | |||
<td> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | <td>Which type of Inputs and Outputs to use in this rule.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td><span style="color:red">ADC:</span> Voltage</td> | ||
<td> | <td>positive float [0..40]; default: <b>none</b></td> | ||
<td> | <td>At which voltage value will this rule be triggered.</td> | ||
</tr> | </tr> | ||
|TRB1 = | |||
{{#ifeq:{{{name}}}|TRB141| | |||
<tr> | |||
<td>Input/Output type</td> | |||
<td><span style="color:blue"><b>Input/Output</b></span> {{!}} <span style="color:dodgerblue"><b>Wet/Dry Input</b></span> {{!}} <span style="color:forestgreen"><b>Relay</b></span> {{!}} <span style="color:darkred"><b>4–20 mA Current Loop</b></span> {{!}} <span style="color:chocolate"><b>ADC</b></span>; default: <b>Input/Output</b></td> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | |||
</tr> | |||
<tr> | |||
<td><span style="color:blue">Input/Output:</span> Input/Output name</td> | |||
<td>Configurable Input/Output(3) {{!}} Configurable Input/Output(4); default: <b>Configurable Input/Output(3)</b></td> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | |||
</tr> | |||
<tr> | |||
<td><span style="color:blue">Input/Output:</span> State change</td> | |||
<td>High level {{!}} Low level {{!}} Both; default: <b>High level</b></td> | |||
<td>On which Input/Output state will this rule be triggered.</td> | |||
</tr> | |||
<tr> | |||
<td><span style="color:dodgerblue">Wet/Dry Input:</span> Input/Output name</td> | |||
<td>Wet/Dry Input(1) {{!}} Wet/Dry Input(2); default: <b>Wet/Dry Input(1)</b></td> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | |||
</tr> | |||
<tr> | |||
<td><span style="color:dodgerblue">Wet/Dry Input:</span> State change</td> | |||
<td>Rising {{!}} Falling {{!}} Both; default: <b>Rising</b></td> | |||
<td>On which Input/Output state will this rule be triggered.</td> | |||
</tr> | |||
<tr> | |||
<td><span style="color:forestgreen">Relay:</span> Input/Output name</td> | |||
<td>Relay(3,4,5) {{!}} Latching relay(11,12,13); default: <b>Relay(3,4,5)</b></td> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | |||
</tr> | |||
<tr> | |||
<td><span style="color:forestgreen">Relay:</span> State change</td> | |||
<td>Open {{!}} Closed {{!}} Both; default: <b>Open</b></td> | |||
<td>On which Input/Output state will this rule be triggered.</td> | |||
</tr> | |||
<tr> | |||
<td><span style="color:darkred">4–20 mA Current Loop:</span> Input/Output name</td> | |||
<td>4–20 mA Current Loop; default: <b>4–20 mA Current Loop</b></td> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | |||
</tr> | |||
<tr> | |||
<td><span style="color:darkred">4–20 mA Current Loop:</span> Voltage</td> | |||
<td>positive float [0..40]; default: <b>none</b></td> | |||
<td>At which voltage value will this rule be triggered.</td> | |||
</tr> | |||
<tr> | |||
<td><span style="color:chocolate">ADC:</span> Input/Output name</td> | |||
<td>ADC; default: <b>ADC</b></td> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | |||
</tr> | |||
<tr> | |||
<td><span style="color:chocolate">ADC:</span> Voltage</td> | |||
<td>positive float [0..40]; default: <b>none</b></td> | |||
<td>At which voltage value will this rule be triggered.</td> | |||
</tr> | |||
| | |||
<tr> | |||
<td>Input/Output type</td> | |||
<td>Input/Output; default: <b>Input/Output</b></td> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | |||
</tr> | |||
<tr> | |||
<td>Input/Output name</td> | |||
<td>Input(3) {{!}} Output(4); default: <b>Input(3)</b></td> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | |||
</tr> | |||
<tr> | |||
<td>State change</td> | |||
<td>High level {{!}} Low level {{!}} Both; default: <b>High level</b></td> | |||
<td>On which Input/Output state will this rule be triggered.</td> | |||
</tr>}} | |||
|RUT36X = | |||
<tr> | |||
<td>Input/Output type</td> | |||
<td>Input/Output; default: <b>Input/Output</b></td> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | |||
</tr> | |||
<tr> | |||
<td>Input/Output name</td> | |||
<td>Input(3) {{!}} Output(4); default: <b>Input(3)</b></td> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | |||
</tr> | |||
<tr> | |||
<td>State change</td> | |||
<td>High level {{!}} Low level {{!}} Both; default: <b>High level</b></td> | |||
<td>On which Input/Output state will this rule be triggered.</td> | |||
</tr> | |||
|RUT9 = | |||
{{#ifeq:{{{name}}}|RUT955| | |||
<tr> | |||
<td>Input/Output type</td> | |||
<td><span style="color:blue">Input/Output</span> {{!}} <span style="color:forestgreen"><b>Relay</b></span> {{!}} <span style="color:darkred"><b>4–20 mA Current Loop</b></span> {{!}} <span style="color:chocolate">ADC</span>; default: <b>Input/Output</b></td> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | |||
</tr> | |||
<tr> | |||
<td><span style="color:blue">Input/Output:</span> Input/Output name</td> | |||
<td>Input (3) {{!}} Input (1) {{!}} Output(4) {{!}} Isolated Output (3,4,8) {{!}} Isolate Input (2,7); default: <b>Input (3)</b></td> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | |||
</tr> | |||
<tr> | |||
<td><span style="color:blue">Input/Output:</span> State change</td> | |||
<td>High level {{!}} Low level {{!}} Both; default: <b>Both</b></td> | |||
<td>On which Input/Output state will this rule be triggered.</td> | |||
</tr> | |||
<tr> | |||
<td><span style="color:forestgreen">Relay:</span> Input/Output name</td> | |||
<td>Relay(5,10); default: <b>Relay(5,10)</b></td> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | |||
</tr> | |||
<tr> | |||
<td><span style="color:forestgreen">Relay:</span> State change</td> | |||
<td>Open {{!}} Closed {{!}} Both; default: <b>Open</b></td> | |||
<td>On which Input/Output state will this rule be triggered.</td> | |||
</tr> | |||
<tr> | |||
<td><span style="color:darkred">4–20 mA Current Loop:</span> Input/Output name</td> | |||
<td>Analog Current Loop (6,9); default: <b>Analog Current Loop (6,9)</b></td> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | |||
</tr> | |||
<tr> | |||
<td><span style="color:darkred">4–20 mA Current Loop:</span> Voltage</td> | |||
<td>positive float [0..40]; default: <b>none</b></td> | |||
<td>At which voltage value will this rule be triggered.</td> | |||
</tr> | |||
<tr> | |||
<td><span style="color:chocolate">ADC:</span> Input/Output name</td> | |||
<td>Analog Input (6,9); default: <b>Analog Input (6,9)</b></td> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | |||
</tr> | |||
<tr> | |||
<td><span style="color:chocolate">ADC:</span> Voltage</td> | |||
<td>positive float [0..40]; default: <b>none</b></td> | |||
<td>At which voltage value will this rule be triggered.</td> | |||
</tr> | |||
| | |||
<tr> | |||
<td>Input/Output type</td> | |||
<td>Input/Output; default: <b>Input/Output</b></td> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | |||
</tr> | |||
<tr> | |||
<td>Input/Output name</td> | |||
<td>Input(3) {{!}} Output(4); default: <b>Input(3)</b></td> | |||
<td>Which type of Inputs and Outputs to use in this rule.</td> | |||
</tr> | |||
<tr> | |||
<td>State change</td> | |||
<td>High level {{!}} Low level {{!}} Both; default: <b>Both</b></td> | |||
<td>On which Input/Output state will this rule be triggered.</td> | |||
</tr> | |||
|}} | |}} | ||
}} | }} | ||
</table> | </table> | ||
==SNMP variables list== | ==SNMP variables list== | ||
Revision as of 15:34, 27 March 2023
Template:Networking rutos manual fw disclosure
Summary
Simple Network Management Protocol (SNMP) is a network management protocol used for collecting information and configuring network devices. This page is an overview of the SNMP function in {{{name}}} devices.
Note: SNMP is additional software that can be installed from the Services → [[{{{name}}} Package Manager|Package Manager]] page.
If you're having trouble finding this page or some of the parameters described here on your device's WebUI, you should turn on "Advanced WebUI" mode. You can do that by clicking the "Advanced" button, located at the top of the WebUI.
SNMP settings
The SNMP settings page is used to configure SNMP accessibility and general SNMP information for your device.
SNMP agent settings
| Field | Value | Description |
|---|---|---|
| Enable SNMP service | off | on; default: off | Run SNMP service on system's startup. |
| Enable remote access | off | on; default: off | Open port in firewall so that SNMP service may be reached from WAN. |
| IP family | IPv4 | IPv6 | IPv4v6; default: IPv4 | IP family used by SNMP. |
| Port | integer [0..65535]; default: 161 | SNMP service's port. |
| SNMP v1 Mode | off | on; default: on | Enable/disable SNMP v1 Mode. |
| SNMP v2c Mode | off | on; default: on | Enable/disable SNMP v2c Mode. |
| SNMP v3 Mode | off | on; default: off | Enable/disable SNMP v3 Mode. |
SNMP System Summary
The SNMP System Summary section contains general information about SNMP on this device. You can also download this device's MIB file from this section.
| Field | Value | Description |
|---|---|---|
| MIB file | -(interactive button) | Downloads the device's MIB file. |
| System OID | 1.3.6.1.4.1.48690 | OID or Object Identifier, is an identifier used to name and point to an object in the MIB hierarchy. |
| Location | string; default: location | Trap named sysLocation. |
| Contact | string; default: [email protected] | Trap named sysContact. |
| Name | string; default: name | Trap named sysName. |
SNMP v3 users
The SNMP v3 users page is used to create and manage users, who can be authenticated using SNMP v3. To configure an SNMP user, you must first create it:
- Enter a custom name for the new user in the 'Name' field.
- Click the 'Add' button.
- Click the 'Edit' button next to the newly created user.
The SNMP user configuration window should look similar to this:
Note: this table has coloring scheme to indicate which fields can be seen with different configuration.
| Field | Value | Description |
|---|---|---|
| Enable | off | on; default: off | Turns this SNMP user on or off. |
| Username | string; default: none | Set username to access SNMP. |
| Security level | No authentication, no privacy | Authentication, no privacy | Authentication and privacy; default: No authentication, no privacy | A security level is an authentication strategy that is set up for the user.
No authentication, no privacy - authenticates with a username. Authentication - provides MD5 or SHA algorithms for authentication. Privacy - Provides DES or AES encryption. |
| Authentication, no privacy | Authentication and privacy: Authentication type | SHA | MD5; default: SHA | Set authentication type to use with SNMP v3. |
| Authentication, no privacy | Authentication and privacy: Authentication passphrase | string; default: none | Set authentication passpharse to generate key for SNMP v3. |
| Authentication and privacy: Privacy type | DES | AES; default: DES | Set privacy type to use with SNMP v3. |
| Authentication and privacy: Privacy passphrase | string; default: none | Set privacy passpharse to generate key for SNMP v3. |
| Access Mode | Read-Only | Read-Write; default: Read-Only | The access mode specifies the access the hosts in the community are allowed with respect to retrieving and modifying the MIB variables from a specific SNMP agent. |
| MIB subtree | string; default: none | Leave empty to access full MIB tree. |
Communities
The SNMP Community section is used to manage access rights. You can edit an SNMP community by clicking the 'Edit' button next to it:
This will redirect you to the community's configuration page.
| Field | Value | Description |
|---|---|---|
| Community name | string; default: none | Name of the community. |
| IP Address | ip; default: none | IP address of the community. |
| IP Mask | ip; default: none | Netmask for IP of the community. |
| Access Mode | Read-Only | Read-Write; default: Read-Only | Access mode for current community. |
SNMPv6 community configuration page:
| Field | Value | Description |
|---|---|---|
| Community name | string; default: public | Name of the community. |
| Source | ip6 | domain name; default: default | Source of the community. |
| Access Mode | Read-Only | Read-Write; default: Read-Only | Access mode for current community. |
Trap Settings
SNMP Traps are used to send alert messages to a central collector, the “SNMP manager” when an important event happens. A benefit of using Traps for reporting alarms is that they trigger instantaneously, rather than waiting for a status request from the manager.
Trap settings page is divided in two sections - Trap service settings and Trap rules. Trap service settings lets you manage hosts which will get configured alert messages, Trap rules lets you manage rules which when triggered will send alerts.
Trap Service Settings
The Trap Service Settings is used to manage hosts which will be alerted when an SNMP trap is triggered. The host list is empty by default thus, to begin configuration you must first create at least one host.
Click the 'Add' button at the bottom-right side of the table to create a new host.
The newly added Host configuration should look similar to this:
| Field | Value | Description |
|---|---|---|
| Host/IP | url | ip; default: none | Hostname or IP address to transfer SNMP traffic to. |
| Port | integer [0..65535]; default: 162 | Trap host's port number. |
| Community | string; default: Public | Name of the community to which the trap belongs. |
| Delete | - (interactive button) | Deletes the host next to the button. |
| off/on slider | off | on; default: off | Turns the host on or off. SNMP traffic is only sent to enabled hosts. |
Trap Rules
SNMP Trap Rules are alerts that trigger when certain user-specified events occur. When the trigger event happens, the trap will notify known SNMP hosts.
You can create a new trap rule by clicking the 'Add' button.
You should be redirected to the rule's configuration page which should look something like this:
[[File:Networking_rutos_manual_snmp_trap_settings_trap_rules_modify_trap_rule_mobile_{{{mobile}}}.png|border|class=tlt-border]]
Above is an example of what rule configuration window looks like. Below is a table with detailed explanations on how to configure the rule and what each of the fields mean.
To avoid redundancy, screenshots for the other rules will not be provided, since the structures, syntax and the overall look of the configuration windows for each rule are very similar. Instead, only tables containing information on how to edit each rule will be provided.
Input/Output
| field name | value1 | description |
|---|---|---|
| Enable | off | on; default: off | Enable or disable this rule. |
| Action | Input/Output trap | Rule will be triggered when specified input or output state will change. |
SNMP variables list
| Name | OID | Description |
|---|---|---|
| Device | ||
| serial | .1.3.6.1.4.1.48690.1.1.0 | Device serial number |
| routerName.0 | .1.3.6.1.4.1.48690.1.2.0 | Device name |
| productCode | .1.3.6.1.4.1.48690.1.3.0 | Device product (ordering) code |
| batchNumber | .1.3.6.1.4.1.48690.1.4.0 | Device batch number |
| hardwareRevision | .1.3.6.1.4.1.48690.1.5.0 | Device hardware revision |
| fwVersion | .1.3.6.1.4.1.48690.1.6.0 | Device RutOS firmware version |
[[Category:{{{name}}} Services section]]