RADLAN-rndApplications
AI MIB Summary
The RADLAN-rndApplications private MIB module enables monitoring of application-specific performance metrics and operational states on RND (Ruckus Wireless) LAN infrastructure devices. It provides visibility into application-level traffic statistics, session counts, and service health indicators specific to Ruckus's proprietary management extensions.
The private MIB module definition for RND applications MIB.
Main OID:
rndApplications.1.3.6.1.4.1.89.35
98
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
98 total| Object Name |
|---|
rndApplicationsThe private MIB module definition for RND applications MIB. MODULE-IDENTITY .1.3.6.1.4.1.89.35 |
rndMidLevelManagement OBJECT IDENTIFIER .1.3.6.1.4.1.89.35.2 |
rndAlarmOptions OBJECT IDENTIFIER .1.3.6.1.4.1.89.35.2.2 |
rndAlarmEnablingIndicates whether alarms should be issued to the high-level
NMSrw Enumeration .1.3.6.1.4.1.89.35.2.2.1 |
rndAlarmIntervalIndicates the minimal period of time which must pass after issuing
an alarm before issuing the same alarm again.rw INTEGER .1.3.6.1.4.1.89.35.2.2.2 |
rndMonitoredElementsTableThe table of monitored elements of the network SEQUENCE OF RndMonitoredElementEntry .1.3.6.1.4.1.89.35.2.3 |
rndMonitoredElementEntryThe row definition for this table. RndMonitoredElementEntry .1.3.6.1.4.1.89.35.2.3.1 |
rndMonitoredElementAddressThe IP address of the monitored elementro IpAddress .1.3.6.1.4.1.89.35.2.3.1.1 |
rndMonitoredElementCommunityThe community of the monitored elementrw DisplayString .1.3.6.1.4.1.89.35.2.3.1.2 |
rndMonitoredElementLabelThe label assigned by the network manager to the monitored elementrw DisplayString .1.3.6.1.4.1.89.35.2.3.1.3 |
rndDefaultPollingIntervalThe default period of time between two consecutive pollings of the
monitored element for the value of an object instance. If no other polling
interval is specifically assigned to the monitored object instance, this
one will be usedrw INTEGER .1.3.6.1.4.1.89.35.2.3.1.4 |
rndDefaultLogFileThe default file path of the log-file which will contain the polling
results for the monitored element. If no other file path is specifically
assigned to the monitored object instance, this log-file will be used.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.89.35.2.3.1.5 |
rndMonitoredElementStatusIt is used to manage the monitored elements table and indicates
the current monitoring status of an element.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.89.35.2.3.1.6 |
rndMonitoringTableThe table of monitored object instances. Each monitored object instance
belongs to a monitored element previously entered in the
rndMonitoredElementsTable. SEQUENCE OF RndMonitoringEntry .1.3.6.1.4.1.89.35.2.4 |
rndMonitoringEntryThe row definition for this table. RndMonitoringEntry .1.3.6.1.4.1.89.35.2.4.1 |
rndMonitoredElementA label assigned by the network manager to a monitored element to
which this monitored object instance belongs. This label must have
been previously entered in an instance of rndMonitoredElementLabelro DisplayString .1.3.6.1.4.1.89.35.2.4.1.1 |
rndMonitoredObjectInstanceLabelThe label assigned by the network manager to the monitored object instancero DisplayString .1.3.6.1.4.1.89.35.2.4.1.2 |
rndMonitoredObjectNameThe symbolic object type name of the object to which the monitored object
instance belongs (as it appears the MIB module definition). In case of
ambiguity the <MIB module name> : <object type name> format should be used.
An instance of rndMonitoredObjectName need not be assigned any value, if
the corresponding instance of rndMonitoredObjectIdentifier is assigned a
value, since any one of these, together with the object instance
identifier, suffices to unambigously identify the monitored object
instance.rw DisplayString .1.3.6.1.4.1.89.35.2.4.1.3 |
rndMonitoredObjectIdentifierThe object identifier of the object to which the monitored object
instance belongs.
An instance of rndMonitoredObjectIdentifier need not be assigned any value, if
the corresponding instance of rndMonitoredObjectName is assigned a value,
since any one of these, together with the object instance identifier,
suffices to unambigously identify the monitored object instance.rw OBJECT IDENTIFIER .1.3.6.1.4.1.89.35.2.4.1.4 |
rndMonitoredObjectInstanceThe instance identifier (key) of the monitored object instance.rw OBJECT IDENTIFIER .1.3.6.1.4.1.89.35.2.4.1.5 |
rndMonitoredObjectSyntaxThe syntax of the monitored object instance (i.e., the syntax of the object
type of the object to which the monitored instance belongs).
Need not be assigned any value if the corresponding instance of
rndMonitoredObjectName has been assigned a valuerw Enumeration .1.3.6.1.4.1.89.35.2.4.1.6 |
rndMonitoringIntervalThe period of time between two consecutive retrievals of the monitored
object instance's value.rw INTEGER .1.3.6.1.4.1.89.35.2.4.1.7 |
rndAlarmMaxTresholdThe value of the monitored object instance, the exceeding of which
will cause the generation of an alarm to the high-level management
station.rw INTEGER .1.3.6.1.4.1.89.35.2.4.1.8 |
rndAlarmMinTresholdIf the value of the monitored object instance falls below the value
assigned to rndAlarmMinTreshold, an alarm to the high-level management
station will be issued.rw INTEGER .1.3.6.1.4.1.89.35.2.4.1.9 |
rndMonitoringLogfileThe entire path of the file in which the results of the monitoring
of this object instance should be recorded.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.89.35.2.4.1.10 |
rndMonitoringEntryStatusIt is used to manage the monitored object instances table and
indicates the current monitoring status of an object instance.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.89.35.2.4.1.11 |
rndMonitoredIntegerInstancerw INTEGER .1.3.6.1.4.1.89.35.2.4.1.12 |
rndMibFilesTableThe table of monitored object instances. Each monitored object instance
belongs to a monitored element previously entered in the
rndMonitoredElementsTable. SEQUENCE OF RndMibFileEntry .1.3.6.1.4.1.89.35.2.5 |
rndMibFileEntryThe row definition for this table. RndMibFileEntry .1.3.6.1.4.1.89.35.2.5.1 |
rndMibFileIndexThe number of the MIB file in the list MIB files supported by the
Mid-Level management station. The order of the MIB files in this
list must reflect the the IMPORT relation between the MIBS contained
in the MIB files, i.e., if MIB A IMPORTS FROM MIB B, the file containing
MIB A must have a lesser index in this table than the file containing
MIB B.ro INTEGER .1.3.6.1.4.1.89.35.2.5.1.1 |
rndMibFilePathThe path of the MIB file in the MIB file server.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.89.35.2.5.1.2 |
rndMibFileRefreshIndicates if the file should be fetched after setting this entry from the
MIB file server.rw Enumeration .1.3.6.1.4.1.89.35.2.5.1.3 |
rndMibFileEntryStatusIt is used to manage the MIB files table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.89.35.2.5.1.4 |
rndHardwareConfigurationIndicates whether the current SET SNMP PDU contains hardware
configuration (i.e., normally read-only variables). SET of such
variables in the Mid-level management station will be allowed only
if this variable is included in the SNMP PDU and its value is true.
Its value as returned in a GET SNMP PDU will always be false.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.89.35.2.6 |
rndEraseSimulatedConfigurationeraseSimulatedConfiguration instructs the MLNMS to erase all the
simulated configuration from its configuration data-base (CDB). This
the only accepted value for SNMP SET statements and will never be
returned in SNMP GET statements.
simulatedConfigurationPresent indicates that the MLNMS currently has
a simulated configuration.
simulatedConfigurationErased indicates that the MLNMS currently has
no simulated configuration.rw Enumeration .1.3.6.1.4.1.89.35.2.7 |
rndDeleteValuesTableThis table indicates which MIB variables are row status fields which
control the status of the entry to which they belong. This table also
indicates which (integer!) value of these MIB variables will cause, if
present in a SNMP SET PDU, the deletion of the conceptual row instance
to which the SET MIB variable instance belongs. SEQUENCE OF RndDeleteValuesEntry .1.3.6.1.4.1.89.35.2.8 |
rndDeleteValuesEntryThe row definition for the rndDeleteValuesTable table. RndDeleteValuesEntry .1.3.6.1.4.1.89.35.2.8.1 |
rndRowStatusVariableNameThe name of the row status field. This name may not necessarily be any
name which is present in the MIBs loaded into the MLNMS station.rw DisplayString .1.3.6.1.4.1.89.35.2.8.1.1 |
rndRowStatusObjectIdThe object id of the row status field. If the rndRowStatusVariableName is
a name present in the MIBs loaded into the MLNMS, this MIB
variable is not required, but if given, it must match the object id known
to the MLNMS.
The variable identified by rndRowStatusVariableName and/or rndRowStatusObjectId
must be a read-write MIB variable of type INTEGER which belongs to an
entry (i.e, is a child of a MIB variable of type SEQUENCE).rw OBJECT IDENTIFIER .1.3.6.1.4.1.89.35.2.8.1.2 |
rndRowDeleteValueThe value of the variable identified by rndRowStatusVariableName and/or
rndRowStatusObjectId, which, if present in a SNMP SET PDU, will cause
the deletion of the conceptual row instance which the SET MIB variable
instance belongs.rw INTEGER .1.3.6.1.4.1.89.35.2.8.1.3 |
rndDeleteValueEntryStatusIt is used to delete an entry from this table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.89.35.2.8.1.4 |
snmpTesting OBJECT IDENTIFIER .1.3.6.1.4.1.89.35.2.9 |
rndSimulatedVariablesTableThis table indicates which MIB variables are simulated. SEQUENCE OF RndSimulatedVariablesEntry .1.3.6.1.4.1.89.35.2.9.1 |
rndSimulatedVariablesEntryThe row definition for the rndSimulatedVariablesTable table. RndSimulatedVariablesEntry .1.3.6.1.4.1.89.35.2.9.1.1 |
rndSimulatedVariableEntryIndexThe index entry.ro INTEGER .1.3.6.1.4.1.89.35.2.9.1.1.1 |
rndSimulatedVariableObjectIdThe object id of the simulated variable. If the simulated variable belongs
to a table entry, the entire entry is henceforth supported.rw OBJECT IDENTIFIER .1.3.6.1.4.1.89.35.2.9.1.1.2 |
rndNotSupportedFieldVariable for not supported simulation.ro INTEGER .1.3.6.1.4.1.89.35.2.9.1.1.3 |
rndSimulatedVariableEntryStatusIt is used to delete an entry from this table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.89.35.2.9.1.1.4 |
rndSnmpTestPasswordThis variable enables the user supplying the correct code to use the
SNMP test feature.rw INTEGER .1.3.6.1.4.1.89.35.2.9.2 |
rndSnmpTestsThis variable enables the authorized user to test various SNMP features.rw Enumeration .1.3.6.1.4.1.89.35.2.9.3 |
rndSimulateUndoThis variable enables the authorized user to test the SNMP UNDO feature.rw INTEGER .1.3.6.1.4.1.89.35.2.9.4 |
rlSnmpServTestRequestThis variable enables the authorized user to test the SNMP SERV package.rw INTEGER .1.3.6.1.4.1.89.35.2.9.5 |
rlSnmpServTestResponseThis variable enables the authorized user to retrieve the results of
a the SNMP SERV package test.ro OCTET STRING .1.3.6.1.4.1.89.35.2.9.6 |
rlSnmpServCreateTestPoolThis variable enables the authorized user to indicate that after its reset
the device should create a buffer pool for SNMPServ process PDU
testing.rw Enumeration .1.3.6.1.4.1.89.35.2.9.7 |
rlSnmpServITCbindClientsThis variable enables the authorized user to to indicate that after
its reset the device should create ITC clients for SnmpServ data
requests clients.
The semantics of this variable is as follows:
subidentifier 2*n indicates whether the client n is synchronous(1) or
asynchronous(2)
subidentifier 2*n+1 indicates the number of simulatneous requests
expected by client n.rw OBJECT IDENTIFIER .1.3.6.1.4.1.89.35.2.9.8 |
rlSnmpTestSimulatedVariables OBJECT IDENTIFIER .1.3.6.1.4.1.89.35.2.9.9 |
rlTstBasicRateTableTable for testing SNMP agent. SEQUENCE OF RlTstBasicRateEntry .1.3.6.1.4.1.89.35.2.9.10 |
rlTstBasicRateEntryAn entry in the rlTstBasicRateTable. RlTstBasicRateEntry .1.3.6.1.4.1.89.35.2.9.10.1 |
rlTstBasicRateIfTyperw Enumeration .1.3.6.1.4.1.89.35.2.9.10.1.1 |
rlTstBasicRateLineTopologyrw Enumeration .1.3.6.1.4.1.89.35.2.9.10.1.2 |
rlTstBasicRateIfModerw Enumeration .1.3.6.1.4.1.89.35.2.9.10.1.3 |
rlTstBasicRateSignalModerw Enumeration .1.3.6.1.4.1.89.35.2.9.10.1.4 |
rlMibTree OBJECT IDENTIFIER .1.3.6.1.4.1.89.35.2.10 |
rlMibTreeTableThis reflects the MIB tree of the device. SEQUENCE OF RlMibTreeEntry .1.3.6.1.4.1.89.35.2.10.1 |
rlMibTreeEntryEach row shows a tree relationsship in the MIB. RlMibTreeEntry .1.3.6.1.4.1.89.35.2.10.1.1 |
rlMibTreeFatherThe father in a tree relation ship. DisplayString (SNMPv2-TC) .1.3.6.1.4.1.89.35.2.10.1.1.1 |
rlMibTreeSonIndexRunning index for this table. INTEGER .1.3.6.1.4.1.89.35.2.10.1.1.2 |
rlMibTreeSonThe son in a tree relation ship.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.89.35.2.10.1.1.3 |
rlMibTreeSonObjectIdThe object identifier of the son in a tree relation ship.ro OBJECT IDENTIFIER .1.3.6.1.4.1.89.35.2.10.1.1.4 |
rlMibTreeGrandFatherThe grand father (i.e father's father) in a tree relation ship.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.89.35.2.10.1.1.5 |
rsPingMIB OBJECT IDENTIFIER .1.3.6.1.4.1.89.35.4 |
rsPingTableA table of ping request entries. SEQUENCE OF RsPingEntry .1.3.6.1.4.1.89.35.4.1 |
rsPingEntryA ping request entry.
A management station wishing to create an entry should
first generate a pseudo-random serial number to be used
as the index to this sparse table. It must also create in the same
PDU the associated instance of the address object. It should also
modify in the same PDU the default values for the other configuration
objects if the defaults are not appropriate.
Once the sequence completes, the management station should
retrieve the values of the status objects of interest, and
should then delete the entry. In order to prevent old
entries from clogging the table, entries will be aged out,
but an entry will never be deleted within 5 minutes of
completing. RsPingEntry .1.3.6.1.4.1.89.35.4.1.1 |
rsPingAddressThe address of the device to be pinged.
Once an instance of this object is created, its
value can not be changed.rw IpAddress -- Rsyntax OCTET STRING .1.3.6.1.4.1.89.35.4.1.1.1 |
rsPingPacketCountSpecifies the number of ping packets to send to the target
in this sequence.rw INTEGER .1.3.6.1.4.1.89.35.4.1.1.2 |
rsPingPacketSizeSpecifies the size of ping packets to send to the target
in this sequence. The lower and upper boundaries of this
object are implementation dependent.rw INTEGER .1.3.6.1.4.1.89.35.4.1.1.3 |
rsPingPacketTimeoutSpecifies the amount of time to wait for a response to a
transmitted packet before declaring the packet 'dropped.'rw INTEGER .1.3.6.1.4.1.89.35.4.1.1.4 |
rsPingDelaySpecifies the minimum amount of time to wait before sending
the next packet in a sequence after receiving a response.
The actual delay may be greater due to internal task scheduling.rw INTEGER .1.3.6.1.4.1.89.35.4.1.1.5 |
rsPingTrapOnCompletionSpecifies whether or not a rsPingCompletion trap should
be issued on completion of the sequence of pings. If such a
trap is desired, the NMS should ensure that the community table
contains an instance specified by the NMSs IP address with
rndCommunityTrapsEnable = trapsEnable.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.89.35.4.1.1.6 |
rsPingSentPacketsThe number of ping packets that have been sent to the target
in this sequence.ro Counter32 .1.3.6.1.4.1.89.35.4.1.1.7 |
rsPingReceivedPacketsThe number of ping packets that have been received from the
target in this sequence.ro Counter32 .1.3.6.1.4.1.89.35.4.1.1.8 |
rsPingMinReturnTimeThe minimum round trip time of all the packets that have
been sent in this sequence. The value returned to a GET request
is meaningless if no ping response in a sequence has been received
yet.ro INTEGER -- Units -- milliseconds .1.3.6.1.4.1.89.35.4.1.1.9 |
rsPingAvgReturnTimeThe average round trip time of all the packets that have
been sent in this sequence.The value returned to a GET request
is meaningless if no ping response in a sequence has been received
yet.ro INTEGER -- Units -- milliseconds .1.3.6.1.4.1.89.35.4.1.1.10 |
rsPingMaxReturnTimeThe maximum round trip time of all the packets that have
been sent in this sequence.The value returned to a GET request
is meaningless if no ping response in a sequence has been received
yet.ro INTEGER -- Units -- milliseconds .1.3.6.1.4.1.89.35.4.1.1.11 |
rsPingCompletionStatusIf all the echo request packets in this sequence have been
responded by valid echo responses, this object is set to ok.
Otherwise this status indicates the problem. bad-reply-data indicates
that the reply data is not equal to the response data.ro Enumeration .1.3.6.1.4.1.89.35.4.1.1.12 |
rsPingTimeStampThe time-stamp indicating the time and date of creation or last
update of this request. The format of the time-stamp is
dd/mm/yyyy hh:mm:ssro DisplayString .1.3.6.1.4.1.89.35.4.1.1.13 |
rsPingEntryStatusThe status of this table entry.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.89.35.4.1.1.14 |
rsPowerSupplyRedundacy OBJECT IDENTIFIER .1.3.6.1.4.1.89.35.5 |
rsPowerSupplyRedundacyTableThe power supply redundancy table. SEQUENCE OF RsPowerSupplyRedundacyEntry .1.3.6.1.4.1.89.35.5.1 |
rsPowerSupplyRedundacyEntryThe status of power supply redundancy for this table. RsPowerSupplyRedundacyEntry .1.3.6.1.4.1.89.35.5.1.1 |
rsPowerSupplyRedundacyReNumberThis number identifies the module backed up
by power supply redundancy in the stack.ro INTEGER .1.3.6.1.4.1.89.35.5.1.1.1 |
rsPowerSupplyRedundacyStatusThe status of a power supply redundancy of the entry.ro Enumeration .1.3.6.1.4.1.89.35.5.1.1.2 |
rsNvram OBJECT IDENTIFIER .1.3.6.1.4.1.89.35.6 |
rsEraseNvramAfterResetThe name of NVRAM application that will be erased
after reset or ALL if all NVRAM should be erased.rw DisplayString .1.3.6.1.4.1.89.35.6.1 |
rsNvramApplTableThe NVRAM application table. SEQUENCE OF RsNvramApplEntry .1.3.6.1.4.1.89.35.6.2 |
rsNvramApplEntryThe status of NVRAM application table. RsNvramApplEntry .1.3.6.1.4.1.89.35.6.2.1 |
rsNvramApplIndexThe index of NVRAM application table.ro INTEGER .1.3.6.1.4.1.89.35.6.2.1.1 |
rsNvramApplNameThe name of application used NVRAM.ro DisplayString .1.3.6.1.4.1.89.35.6.2.1.2 |