UBQS-CONFIG-MIB
The UBQS-CONFIG-MIB enables remote management of SNMP entity parameters on Ubiquiti Networks (UBNT) devices, specifically allowing administrators to modify agent configuration settings such as community strings, trap destinations, and access control lists via SNMP SET operations.
Imported Objects
Objects
21 total| Object Name |
|---|
ubiConfigMIBThis MIB module defines MIB objects which provide
mechanisms to remotely configure the parameters
used by an SNMP entity. MODULE-IDENTITY .1.3.6.1.4.1.7800.100.18 |
ubiConfigMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.7800.100.18.1 |
ubiConfigInfoTableThe table of configuration file list
that consists of image and config SEQUENCE OF UbiConfigInfoEntry .1.3.6.1.4.1.7800.100.18.1.1 |
ubiConfigInfoEntryThe entry representing one element of configuration file list UbiConfigInfoEntry .1.3.6.1.4.1.7800.100.18.1.1.1 |
ubiConfigNameConfiguration file name or image namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.7800.100.18.1.1.1.1 |
ubiConfigTypeConfiguration type
config : configuration file
image : image file
other : other type filero Enumeration .1.3.6.1.4.1.7800.100.18.1.1.1.2 |
ubiConfigCurrentStatusCurrent configuration file statusro Enumeration .1.3.6.1.4.1.7800.100.18.1.1.1.3 |
ubiConfigNextStatusNext configuration file statusrw Enumeration .1.3.6.1.4.1.7800.100.18.1.1.1.4 |
ubiConfigErase OBJECT IDENTIFIER .1.3.6.1.4.1.7800.100.18.1.2 |
ubiConfigEraseModeThe type of object to be erased.
To erase a file, value must be 1, 2 or 3.
fileInFlash means config and image file at system flash and
fileInUsbFlash means config and image file at USB flash.rw Enumeration .1.3.6.1.4.1.7800.100.18.1.2.1 |
ubiConfigEraseFileNameIf mode is 'configFile', configuration file name to be erased.
startupConfig doesn't need this objectrw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.7800.100.18.1.2.2 |
ubiConfigEraseOperateExcute to erase configurationrw Enumeration .1.3.6.1.4.1.7800.100.18.1.2.3 |
ubiConfigEraseUsbPartNumThe number of USB flash partition which has a file to be erase.
This object is only for when ubiConfigEraseMode is 'fileInUsbFlash'.rw Integer32 .1.3.6.1.4.1.7800.100.18.1.2.4 |
ubiConfigCopy OBJECT IDENTIFIER .1.3.6.1.4.1.7800.100.18.1.3 |
ubiConfigSourceMethodconfiguration source control method
Represents 'copy <source> <destination>'.
each source method has possible destination methods.
The mapping list below:
source | destination
===================================================
startup-config | running-config
| ftp
| tftp
running-config | startup-config
| ftp
| tftp
| flash
| usbflash
ftp | startup-config
| running-config
| flash
| config-file
tftp | startup-config
| running-config
| flash
| config-file
flash | ftp
| tftp
| flash
| usbflash
usbflash | flash
| usbflashrw ConfigMethodType .1.3.6.1.4.1.7800.100.18.1.3.1 |
ubiConfigSourceFileNameIf not startup or running, source file namerw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.7800.100.18.1.3.2 |
ubiConfigSourceIpAddressIf tftp or ftp, ip address to be connectedrw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.7800.100.18.1.3.3 |
ubiConfigSouceUserIdIf ftp, server user idrw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.7800.100.18.1.3.4 |
ubiConfigSourceUserPasswordIf ftp, server user passwordrw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.7800.100.18.1.3.5 |
ubiConfigSourcePartNumIf usbflash, system partition numberrw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.7800.100.18.1.3.6 |
ubiConfigDestinationMethodconfiguration destination control method
Represents 'copy <source> <destination>'.
each source method has possible destination methods.
The mapping list below:
source | destination
===================================================
startup-config | running-config
| ftp
| tftp
running-config | startup-config
| ftp
| tftp
| flash
| usbflash
ftp | startup-config
| running-config
| flash
tftp | startup-config
| running-config
| flash
flash | ftp
| tftp
| flash
| usbflash
usbflash | flash
| usbflash
::= { ubiConfigCopy 7 }
ubiConfigDestinationFileName OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-write
STATUS current
DESCRIPTIONrw ConfigMethodType .ubiConfigMonMIBGroups.2 |
More MIBs from Ubiquoss
Browse all UbiquossMIBs →The UBIQUOSS-EPON-PON-PROFILE-GROUP-MIB manages Quality of Service (QoS) profile configurations and parameters for EPON (Ethernet Passive Optical Network) PON interfaces on Ubiquoss optical line terminal (OLT) hardware. It enables the definition, monitoring, and enforcement of traffic shaping, priority queuing, and bandwidth allocation policies across specific PON port groups.
The UBIQUOSS-10GEPON-PON-PROFILE-GROUP-MIB manages Quality of Service (QoS) profile configurations and parameters for Ubiquiti 10G-EPON Optical Line Terminals (OLTs). It enables the definition and monitoring of traffic shaping rules, bandwidth limits, and priority queues applied to specific PON profile groups within the access network.
The UBIQUOSS-EPON-PM-GROUP-MIB module enables monitoring of performance metrics for Ubiquiti EPON (Ethernet Passive Optical Network) interfaces, specifically tracking traffic counters, error statistics, and link utilization data for optical line terminals and optical network units.
The UBIQUOSS-EPON-PON-MAC-GROUP-MIB module provides management interfaces for monitoring and configuring MAC-layer parameters, including subscriber MAC addresses, VLAN mappings, and traffic statistics, within Ubiquiti's EPON (Ethernet Passive Optical Network) access network infrastructure.
The UBIQUOSS-10GEPON-PM-GROUP-MIB module enables performance monitoring of Ubiquiti 10G-EPON optical line terminals and optical network units by exposing traffic counters, error statistics, and link utilization metrics. It facilitates the collection of physical layer and data link layer performance data, including bit error rates, packet drops, and interface throughput, for network capacity planning and fault isolation.
The UBIQUOSS-10GEPON-PON-MAC-GROUP-MIB module enables monitoring and management of MAC layer statistics, session states, and interface counters for Ubiquiti 10G Ethernet Passive Optical Network (EPON) optical line terminals and optical network units. It provides specific visibility into 10G-EPON MAC protocol operations, including port status, traffic counters, and subscriber link metrics required for provisioning and fault isolation.