自定义通用物联网网关的MIB结构的参考

news/2024/11/24 7:34:01/

文章目录

  • 说明
  • 参考代码
  • 开源项目地址

说明

  • 由于时间有限，本人精力有限，所以给出的网关MIB结构，并非完美！
  • 本文网关MIB结构的结构定义构思在使用MIB builder自定义物联网网关的MIB结构
  • 欢迎小伙伴，点赞、关注和评论！

参考代码

--
-- IOTGATEWAY-MIB.my
-- MIB generated by MG-SOFT Visual MIB Builder Version 6.0  Build 88
-- Tuesday, December 19, 2023 at 20:04:38
--IOTGATEWAY-MIB DEFINITIONS ::= BEGINIMPORTSOBJECT-GROUP, NOTIFICATION-GROUP			FROM SNMPv2-CONF			enterprises, TimeTicks, IpAddress, Integer32, Gauge32, Counter32, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-IDENTITY, NOTIFICATION-TYPE			FROM SNMPv2-SMI;-- 1.3.6.1.4.1.99999.1.1iotGateway MODULE-IDENTITY LAST-UPDATED "202312061422Z"		-- December 06, 2023 at 14:22 GMTORGANIZATION "yangzhou"CONTACT-INFO "Contact Information"DESCRIPTION "MIB for managing IoT Gateway devices."REVISION "202312061425Z"		-- December 06, 2023 at 14:25 GMTDESCRIPTION "Initial version."::= { iotGatewayMIB 1 }--
-- Node definitions
---- 1.3.6.1.4.1.99999yangzhouzhang OBJECT IDENTIFIER ::= { enterprises 99999 }-- 1.3.6.1.4.1.99999.1iotGatewayMIB OBJECT IDENTIFIER ::= { yangzhouzhang 1 }-- 1.3.6.1.4.1.99999.1.3deviceInfoGroup OBJECT IDENTIFIER ::= { iotGatewayMIB 3 }-- 1.3.6.1.4.1.99999.1.3.1deviceModel OBJECT-TYPESYNTAX OCTET STRINGMAX-ACCESS read-onlySTATUS currentDESCRIPTION"The model identifier for the IoT Gateway."::= { deviceInfoGroup 1 }-- 1.3.6.1.4.1.99999.1.3.2deviceName OBJECT-TYPESYNTAX OCTET STRING (SIZE (0..255))MAX-ACCESS read-writeSTATUS currentDESCRIPTION"Name of the gateway device"::= { deviceInfoGroup 2 }-- 1.3.6.1.4.1.99999.1.3.4serialNumber OBJECT-TYPESYNTAX OCTET STRINGMAX-ACCESS read-onlySTATUS currentDESCRIPTION"The serial number of the IoT Gateway."::= { deviceInfoGroup 4 }-- 1.3.6.1.4.1.99999.1.3.5firmwareVersion OBJECT-TYPESYNTAX OCTET STRINGMAX-ACCESS read-onlySTATUS currentDESCRIPTION"Description."::= { deviceInfoGroup 5 }-- 1.3.6.1.4.1.99999.1.3.6uptime OBJECT-TYPESYNTAX TimeTicksMAX-ACCESS read-onlySTATUS currentDESCRIPTION"The time since the IoT Gateway last restarted."::= { deviceInfoGroup 6 }-- 1.3.6.1.4.1.99999.1.3.7devInfoGroup OBJECT-GROUPOBJECTS { deviceModel, deviceName, serialNumber, firmwareVersion, uptime}STATUS currentDESCRIPTION "Description."::= { deviceInfoGroup 7 }-- 1.3.6.1.4.1.99999.1.5networkConfigGroup OBJECT IDENTIFIER ::= { iotGatewayMIB 5 }-- 1.3.6.1.4.1.99999.1.5.1ipAddress OBJECT-TYPESYNTAX IpAddressMAX-ACCESS read-writeSTATUS currentDESCRIPTION"IP address of the gateway"::= { networkConfigGroup 1 }-- 1.3.6.1.4.1.99999.1.5.2subnetMask OBJECT-TYPESYNTAX IpAddressMAX-ACCESS read-writeSTATUS currentDESCRIPTION"Subnet mask of the gateway"::= { networkConfigGroup 2 }-- 1.3.6.1.4.1.99999.1.5.3defaultGateway OBJECT-TYPESYNTAX IpAddressMAX-ACCESS read-writeSTATUS currentDESCRIPTION"Default gateway IP address"::= { networkConfigGroup 3 }-- 1.3.6.1.4.1.99999.1.5.4dnsServers OBJECT-TYPESYNTAX OCTET STRING (SIZE (0..255))MAX-ACCESS read-writeSTATUS currentDESCRIPTION"List of DNS server IP addresses"::= { networkConfigGroup 4 }-- 1.3.6.1.4.1.99999.1.5.5ntpServer OBJECT-TYPESYNTAX IpAddressMAX-ACCESS read-writeSTATUS currentDESCRIPTION"NTP server IP address"::= { networkConfigGroup 5 }-- 1.3.6.1.4.1.99999.1.5.6netConfigGroup OBJECT-GROUPOBJECTS { ipAddress, subnetMask, defaultGateway, dnsServers, ntpServer}STATUS currentDESCRIPTION "Description."::= { networkConfigGroup 6 }-- 1.3.6.1.4.1.99999.1.8devicePerformanceGroup OBJECT IDENTIFIER ::= { iotGatewayMIB 8 }-- 1.3.6.1.4.1.99999.1.8.1dataThroughput OBJECT-TYPESYNTAX Integer32MAX-ACCESS read-onlySTATUS currentDESCRIPTION"Data throughput in bytes per second"::= { devicePerformanceGroup 1 }-- 1.3.6.1.4.1.99999.1.8.2packetLossRate OBJECT-TYPESYNTAX Integer32 (0..100)MAX-ACCESS read-onlySTATUS currentDESCRIPTION"Packet loss rate in percentage"::= { devicePerformanceGroup 2 }-- 1.3.6.1.4.1.99999.1.8.3responseTime OBJECT-TYPESYNTAX Integer32UNITS "milliseconds"MAX-ACCESS read-onlySTATUS currentDESCRIPTION"Response time in milliseconds"::= { devicePerformanceGroup 3 }-- 1.3.6.1.4.1.99999.1.8.4deviceTemperature OBJECT-TYPESYNTAX Integer32 (-50..100)UNITS "degrees Celsiu"MAX-ACCESS read-onlySTATUS currentDESCRIPTION"Device temperature in degrees Celsius"::= { devicePerformanceGroup 4 }-- 1.3.6.1.4.1.99999.1.8.5devPerformanceGroup OBJECT-GROUPOBJECTS { dataThroughput, packetLossRate, responseTime, deviceTemperature }STATUS currentDESCRIPTION "Description."::= { devicePerformanceGroup 5 }-- 1.3.6.1.4.1.99999.1.11eventsAndAlarmsGroup OBJECT IDENTIFIER ::= { iotGatewayMIB 11 }-- 1.3.6.1.4.1.99999.1.11.2currentActiveAlarms OBJECT-TYPESYNTAX Gauge32MAX-ACCESS read-onlySTATUS currentDESCRIPTION"Number of current active alarms"::= { eventsAndAlarmsGroup 2 }-- 1.3.6.1.4.1.99999.1.11.3historicalAlarmsRecord OBJECT-TYPESYNTAX OCTET STRINGMAX-ACCESS read-onlySTATUS currentDESCRIPTION"Historical alarms record"::= { eventsAndAlarmsGroup 3 }-- 1.3.6.1.4.1.99999.1.11.4eventLog OBJECT-TYPESYNTAX OCTET STRINGMAX-ACCESS read-onlySTATUS currentDESCRIPTION"Event log"::= { eventsAndAlarmsGroup 4 }-- 1.3.6.1.4.1.99999.1.11.5evAndAlaGroup OBJECT-GROUPOBJECTS { eventLog, historicalAlarmsRecord, currentActiveAlarms }STATUS currentDESCRIPTION "Description."::= { eventsAndAlarmsGroup 5 }-- 1.3.6.1.4.1.99999.1.12connectedDevicesGroup OBJECT IDENTIFIER ::= { iotGatewayMIB 12 }-- 1.3.6.1.4.1.99999.1.12.1connectedDevicesTable OBJECT-TYPESYNTAX SEQUENCE OF ConnectedDevicesEntryMAX-ACCESS not-accessibleSTATUS currentDESCRIPTION"Table of connected devices information"::= { connectedDevicesGroup 1 }-- 1.3.6.1.4.1.99999.1.12.1.1connectedDevicesEntry OBJECT-TYPESYNTAX ConnectedDevicesEntryMAX-ACCESS not-accessibleSTATUS currentDESCRIPTION"Connected device entry"INDEX { deviceId }::= { connectedDevicesTable 1 }ConnectedDevicesEntry ::=SEQUENCE { connectedDevicesCountCounter32,deviceIdInteger32,deviceStatusOCTET STRING,networkStatsOCTET STRING}-- 1.3.6.1.4.1.99999.1.12.1.1.1connectedDevicesCount OBJECT-TYPESYNTAX Counter32MAX-ACCESS read-onlySTATUS currentDESCRIPTION"Description."::= { connectedDevicesEntry 1 }-- 1.3.6.1.4.1.99999.1.12.1.1.2deviceId OBJECT-TYPESYNTAX Integer32 (1..25535)MAX-ACCESS read-onlySTATUS currentDESCRIPTION"Device ID"::= { connectedDevicesEntry 2 }-- 1.3.6.1.4.1.99999.1.12.1.1.3deviceStatus OBJECT-TYPESYNTAX OCTET STRING (SIZE (0..255))MAX-ACCESS read-onlySTATUS currentDESCRIPTION"Device status information"::= { connectedDevicesEntry 3 }-- 1.3.6.1.4.1.99999.1.12.1.1.4networkStats OBJECT-TYPESYNTAX OCTET STRINGMAX-ACCESS read-onlySTATUS currentDESCRIPTION"Description."::= { connectedDevicesEntry 4 }-- 1.3.6.1.4.1.99999.1.12.2connDevicesGrouup OBJECT-GROUPOBJECTS { connectedDevicesCount, deviceId, deviceStatus, networkStats }STATUS currentDESCRIPTION "Description."::= { connectedDevicesGroup 2 }-- 1.3.6.1.4.1.99999.1.13deviceStatusGroup OBJECT IDENTIFIER ::= { iotGatewayMIB 13 }-- 1.3.6.1.4.1.99999.1.13.1deviceStatusTable OBJECT-TYPESYNTAX SEQUENCE OF DeviceStatusEntryMAX-ACCESS not-accessibleSTATUS currentDESCRIPTION"Table of device status information"::= { deviceStatusGroup 1 }-- 1.3.6.1.4.1.99999.1.13.1.1deviceStatusEntry OBJECT-TYPESYNTAX DeviceStatusEntryMAX-ACCESS not-accessibleSTATUS currentDESCRIPTION"Device status entry"INDEX { deviceStatusIndex }::= { deviceStatusTable 1 }DeviceStatusEntry ::=SEQUENCE { deviceStatusIndexInteger32,cpuUtilizationInteger32,memoryUtilizationInteger32,storageUtilizationInteger32,statusDescriptionOCTET STRING}-- 1.3.6.1.4.1.99999.1.13.1.1.1deviceStatusIndex OBJECT-TYPESYNTAX Integer32 (1..100)MAX-ACCESS read-onlySTATUS currentDESCRIPTION"Index for device status entry"::= { deviceStatusEntry 1 }-- 1.3.6.1.4.1.99999.1.13.1.1.2cpuUtilization OBJECT-TYPESYNTAX Integer32 (0..100)MAX-ACCESS read-onlySTATUS currentDESCRIPTION"CPU utilization percentage"::= { deviceStatusEntry 2 }-- 1.3.6.1.4.1.99999.1.13.1.1.3memoryUtilization OBJECT-TYPESYNTAX Integer32 (0..100)MAX-ACCESS read-onlySTATUS currentDESCRIPTION"Memory utilization percentage"::= { deviceStatusEntry 3 }-- 1.3.6.1.4.1.99999.1.13.1.1.4storageUtilization OBJECT-TYPESYNTAX Integer32 (0..100)MAX-ACCESS read-onlySTATUS currentDESCRIPTION"Storage utilization percentage"::= { deviceStatusEntry 4 }-- 1.3.6.1.4.1.99999.1.13.1.1.6statusDescription OBJECT-TYPESYNTAX OCTET STRING (SIZE (0..255))MAX-ACCESS read-onlySTATUS currentDESCRIPTION"Description of the device status"::= { deviceStatusEntry 6 }-- 1.3.6.1.4.1.99999.1.13.2devStatusGroup OBJECT-GROUPOBJECTS { cpuUtilization, memoryUtilization, storageUtilization, statusDescription, deviceStatusIndex}STATUS currentDESCRIPTION "Description."::= { deviceStatusGroup 2 }-- 1.3.6.1.4.1.99999.1.14iotGatewayTrapGroup OBJECT IDENTIFIER ::= { iotGatewayMIB 14 }-- 1.3.6.1.4.1.99999.1.14.1iotGatewayTraps OBJECT-IDENTITYSTATUS currentDESCRIPTION "Description."::= { iotGatewayTrapGroup 1 }-- 1.3.6.1.4.1.99999.1.14.1.1iotGatewayHighCpuUsage NOTIFICATION-TYPEOBJECTS { cpuUtilization }STATUS currentDESCRIPTION "This trap is sent when the CPU usage exceeds a predefined threshold."::= { iotGatewayTraps 1 }-- 1.3.6.1.4.1.99999.1.14.3iotTrapGroup NOTIFICATION-GROUPNOTIFICATIONS { iotGatewayHighCpuUsage }STATUS currentDESCRIPTION "Description."::= { iotGatewayTrapGroup 3 }END--
-- IOTGATEWAY-MIB.my
--

开源项目地址

  • IotGatewayMIB

http://www.ppmy.cn/news/1278836.html

相关文章

vue-内网，离线使用百度地图（地图瓦片图下载静态资源展示定位）

vue-内网，离线使用百度地图（地图瓦片图下载静态资源展示定位）

前言 最近发现很多小伙伴都在问内网怎么使用百度地图，或者是断网情况下能使用百度地图吗 后面经过一番研究，主要难点是，正常情况下我们是访问公网百度图片，数据，才能使用 内网时访问不了百度地图资源时就会使用不了&…
阅读更多...
AI“百模大战”现状：向垂直、B端谋场景，算力仍是主要制约因素

AI“百模大战”现状：向垂直、B端谋场景，算力仍是主要制约因素

文章目录 每日一句正能量前言AI（人工智能）大模型正“飞入”百姓家和行业中。向垂直、B端谋场景算力仍是主要制约因素构建“数据-模型-应用”飞轮后记 每日一句正能量 我们必须在失败中寻找胜利，在绝望中寻求希望。 前言 在当前快速发展的人工…
阅读更多...
uniapp中使用封装步骤条组件

uniapp中使用封装步骤条组件

针对步骤条封装完终于清清楚楚啦 先看效果&#xff1a; 附上代码&#xff1a;使用可直接复用&#xff1a;数据是写在了当前组件中&#xff0c;如有必须&#xff0c;可以使用其中的props传值stepInfos传递相应的数据&#xff0c;根据steps步数就可以控制走到哪一步啦 <temp…
阅读更多...
深入理解Mysql索引及其物理存储

深入理解Mysql索引及其物理存储

深入理解Mysql索引及其物理存储 数据库基础 最上层用于连接、线程处理&#xff1b;第二层中包含了大多数的核心服务&#xff0c;包括了对 SQL 的解析、分析、优化和缓存等功能&#xff0c;存储过程、触发器和视图都是在这里实现的&#xff1b;而第三层就是真正负责数据的存储…
阅读更多...
分布式任务调度QuartZ框架使用(通过注解使用quartz)

分布式任务调度QuartZ框架使用(通过注解使用quartz)

1、Quartz概述 quartz官网文档&#xff1a;http://www.quartz-scheduler.org/ quartz是一个定时调度的框架&#xff0c;属于比较早期的产品&#xff0c;现在市面上流行的xxl-Job&#xff0c;elastic-Job分布式调度框架都是基于该产品。虽然很多人说quartz的使用不是很方便&am…
阅读更多...
【Mysql】哪些sql无法使用到索引

【Mysql】哪些sql无法使用到索引

目录 1.使用 OR 连接多个条件&#xff1a; 2.使用 LIKE 通配符 % 作为前缀&#xff1a; 3.使用 BETWEEN 范围查询&#xff1a; 4.使用 ! 或 <> 操作符&#xff1a; 5.使用 DISTINCT 关键字&#xff1a; 6.使用 FUNCTION() 或 EXPRESSION 包含列&#xff1a; 7.使用…
阅读更多...
什么是数据仪表板？数据可视化仪表盘怎么制作？

什么是数据仪表板？数据可视化仪表盘怎么制作？

在数据经济时代&#xff0c;分析数据是每个企业做出最佳决策的关键。但是&#xff0c;手动分析和解释大量数据是不可行的。数据可视化对于分析数据中存在的各种有价值信息至关重要&#xff0c;包括可见趋势和隐藏趋势等。仪表盘显示可视化趋势和信息&#xff0c;例如 KPI、趋势…
阅读更多...
rich.sql

rich.sql

1、 CURRENT_TIMESTAMP 2、like concat (%,#{},%) 3、var num 2.446242342; num num.toFixed(2); // 输出结果为 2.45 4、left (case when hour(create_time) < 7 then DATE_ADD(create_time,INTERVAL -1 DAY) else create_time end ,10) as date 5、service mysqld …
阅读更多...
最新文章

Copyright @ 2022~2023