RADLAN-rndApplications

MIB Reference — IPNetwork Monitor

All MIBsRADLAN-rndApplications

Organization: Radlan Computer Communications Ltd.

Last Updated: 2004-06-01

Category: Vendor: RADLAN/Cisco SB

Description:

Manages application-level service settings and protocol configurations on Radlan devices.

Imported Objects

From IF-MIB

InterfaceIndex
InterfaceIndexOrZero
ifIndexOBJECT-TYPE

From RADLAN-MIB

rndOBJECT-IDENTITY

From SNMPv2-SMI

Counter32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION
TruthValue

From SNMPv2-TC-v1

DisplayString

What Is RADLAN-rndApplications?

RADLAN-rndApplications is a Radlan Computer Communications Ltd. proprietary MIB (an internal R&D applications MIB) implementing a generic self-monitoring/polling framework for arbitrary SNMP objects. Its objects cover a global alarm-enable and interval, a monitored-elements table (address, community, label, status), default polling interval/log file, and a monitoring table (per element: object instance label/name/identifier/instance/syntax, monitoring interval, alarm max/min threshold, log file, entry status, and integer-instance value), alongside a MIB-files table. As a configuration MIB it lets an administrator configure generic threshold-based polling of any OID on a monitored SNMP element. It is deployed on Radlan Computer Communications equipment used as an internal R&D monitoring tool. Engineers can download the RADLAN-rndApplications file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in RADLAN-rndApplications. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

What Can Be Monitored

  • generic OID polling and threshold-based alarming

Supported Devices

  • Radlan Computer Communications equipment (R&D monitoring)

Monitoring Examples

An administrator configures rndMonitoringTable to poll a specific OID on a remote element and alert via rndAlarmMaxTreshold on Radlan R&D monitoring equipment.

OIDs
OID symbolicOID numericTypeAccessDescription
rndApplications1.3.6.1.4.1.89.35The private MIB module definition for RND applications MIB.
rndMidLevelManagement1.3.6.1.4.1.89.35.2
rndAlarmOptions1.3.6.1.4.1.89.35.2.2
INT rndAlarmEnabling1.3.6.1.4.1.89.35.2.2.1INTEGERread-writeIndicates whether alarms should be issued to the high-level NMS
INT rndAlarmInterval1.3.6.1.4.1.89.35.2.2.2INTEGERread-writeIndicates the minimal period of time which must pass after issuing an alarm before issuing the same alarm again.
rndMonitoredElementsTable1.3.6.1.4.1.89.35.2.3not-accessibleThe table of monitored elements of the network
rndMonitoredElementEntry1.3.6.1.4.1.89.35.2.3.1not-accessibleThe row definition for this table.
IP rndMonitoredElementAddress1.3.6.1.4.1.89.35.2.3.1.1IpAddressread-onlyThe IP address of the monitored element
STR rndMonitoredElementCommunity1.3.6.1.4.1.89.35.2.3.1.2DisplayStringread-writeThe community of the monitored element
STR rndMonitoredElementLabel1.3.6.1.4.1.89.35.2.3.1.3DisplayStringread-writeThe label assigned by the network manager to the monitored element
INT rndDefaultPollingInterval1.3.6.1.4.1.89.35.2.3.1.4INTEGERread-writeThe 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 used
STR rndDefaultLogFile1.3.6.1.4.1.89.35.2.3.1.5DisplayStringread-writeThe 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.
ROW rndMonitoredElementStatus1.3.6.1.4.1.89.35.2.3.1.6RowStatusread-writeIt is used to manage the monitored elements table and indicates the current monitoring status of an element.
rndMonitoringTable1.3.6.1.4.1.89.35.2.4not-accessibleThe table of monitored object instances. Each monitored object instance belongs to a monitored element previously entered in the rndMonitoredElementsTable.
rndMonitoringEntry1.3.6.1.4.1.89.35.2.4.1not-accessibleThe row definition for this table.
STR rndMonitoredElement1.3.6.1.4.1.89.35.2.4.1.1DisplayStringread-onlyA 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 rndMonitoredElementLabel
STR rndMonitoredObjectInstanceLabel1.3.6.1.4.1.89.35.2.4.1.2DisplayStringread-onlyThe label assigned by the network manager to the monitored object instance
STR rndMonitoredObjectName1.3.6.1.4.1.89.35.2.4.1.3DisplayStringread-writeThe 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 : 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.
OID rndMonitoredObjectIdentifier1.3.6.1.4.1.89.35.2.4.1.4OBJECT IDENTIFIERread-writeThe 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.
OID rndMonitoredObjectInstance1.3.6.1.4.1.89.35.2.4.1.5OBJECT IDENTIFIERread-writeThe instance identifier (key) of the monitored object instance.
INT rndMonitoredObjectSyntax1.3.6.1.4.1.89.35.2.4.1.6INTEGERread-writeThe 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 value
INT rndMonitoringInterval1.3.6.1.4.1.89.35.2.4.1.7INTEGERread-writeThe period of time between two consecutive retrievals of the monitored object instance's value.
INT rndAlarmMaxTreshold1.3.6.1.4.1.89.35.2.4.1.8INTEGERread-writeThe value of the monitored object instance, the exceeding of which will cause the generation of an alarm to the high-level management station.
INT rndAlarmMinTreshold1.3.6.1.4.1.89.35.2.4.1.9INTEGERread-writeIf 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.
STR rndMonitoringLogfile1.3.6.1.4.1.89.35.2.4.1.10DisplayStringread-writeThe entire path of the file in which the results of the monitoring of this object instance should be recorded.
ROW rndMonitoringEntryStatus1.3.6.1.4.1.89.35.2.4.1.11RowStatusread-writeIt is used to manage the monitored object instances table and indicates the current monitoring status of an object instance.
INT rndMonitoredIntegerInstance1.3.6.1.4.1.89.35.2.4.1.12INTEGERread-write
rndMibFilesTable1.3.6.1.4.1.89.35.2.5not-accessibleThe table of monitored object instances. Each monitored object instance belongs to a monitored element previously entered in the rndMonitoredElementsTable.
rndMibFileEntry1.3.6.1.4.1.89.35.2.5.1not-accessibleThe row definition for this table.
INT rndMibFileIndex1.3.6.1.4.1.89.35.2.5.1.1INTEGERread-onlyThe 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.
STR rndMibFilePath1.3.6.1.4.1.89.35.2.5.1.2DisplayStringread-writeThe path of the MIB file in the MIB file server.
INT rndMibFileRefresh1.3.6.1.4.1.89.35.2.5.1.3INTEGERread-writeIndicates if the file should be fetched after setting this entry from the MIB file server.
ROW rndMibFileEntryStatus1.3.6.1.4.1.89.35.2.5.1.4RowStatusread-writeIt is used to manage the MIB files table.
T/F rndHardwareConfiguration1.3.6.1.4.1.89.35.2.6TruthValueread-writeIndicates 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.
INT rndEraseSimulatedConfiguration1.3.6.1.4.1.89.35.2.7INTEGERread-writeeraseSimulatedConfiguration 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.
rndDeleteValuesTable1.3.6.1.4.1.89.35.2.8not-accessibleThis 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.
rndDeleteValuesEntry1.3.6.1.4.1.89.35.2.8.1not-accessibleThe row definition for the rndDeleteValuesTable table.
STR rndRowStatusVariableName1.3.6.1.4.1.89.35.2.8.1.1DisplayStringread-writeThe 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.
OID rndRowStatusObjectId1.3.6.1.4.1.89.35.2.8.1.2OBJECT IDENTIFIERread-writeThe 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).
INT rndRowDeleteValue1.3.6.1.4.1.89.35.2.8.1.3INTEGERread-writeThe 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.
ROW rndDeleteValueEntryStatus1.3.6.1.4.1.89.35.2.8.1.4RowStatusread-writeIt is used to delete an entry from this table.
snmpTesting1.3.6.1.4.1.89.35.2.9
rndSimulatedVariablesTable1.3.6.1.4.1.89.35.2.9.1not-accessibleThis table indicates which MIB variables are simulated.
rndSimulatedVariablesEntry1.3.6.1.4.1.89.35.2.9.1.1not-accessibleThe row definition for the rndSimulatedVariablesTable table.
INT rndSimulatedVariableEntryIndex1.3.6.1.4.1.89.35.2.9.1.1.1INTEGERread-onlyThe index entry.
OID rndSimulatedVariableObjectId1.3.6.1.4.1.89.35.2.9.1.1.2OBJECT IDENTIFIERread-writeThe object id of the simulated variable. If the simulated variable belongs to a table entry, the entire entry is henceforth supported.
INT rndNotSupportedField1.3.6.1.4.1.89.35.2.9.1.1.3INTEGERread-onlyVariable for not supported simulation.
ROW rndSimulatedVariableEntryStatus1.3.6.1.4.1.89.35.2.9.1.1.4RowStatusread-writeIt is used to delete an entry from this table.
INT rndSnmpTestPassword1.3.6.1.4.1.89.35.2.9.2INTEGERread-writeThis variable enables the user supplying the correct code to use the SNMP test feature.
INT rndSnmpTests1.3.6.1.4.1.89.35.2.9.3INTEGERread-writeThis variable enables the authorized user to test various SNMP features.
INT rndSimulateUndo1.3.6.1.4.1.89.35.2.9.4INTEGERread-writeThis variable enables the authorized user to test the SNMP UNDO feature.
INT rlSnmpServTestRequest1.3.6.1.4.1.89.35.2.9.5INTEGERread-writeThis variable enables the authorized user to test the SNMP SERV package.
OCT rlSnmpServTestResponse1.3.6.1.4.1.89.35.2.9.6OCTET STRINGread-onlyThis variable enables the authorized user to retrieve the results of a the SNMP SERV package test.
INT rlSnmpServCreateTestPool1.3.6.1.4.1.89.35.2.9.7INTEGERread-writeThis variable enables the authorized user to indicate that after its reset the device should create a buffer pool for SNMPServ process PDU testing.
OID rlSnmpServITCbindClients1.3.6.1.4.1.89.35.2.9.8OBJECT IDENTIFIERread-writeThis 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.
rlSnmpTestSimulatedVariables1.3.6.1.4.1.89.35.2.9.9
rlTstBasicRateTable1.3.6.1.4.1.89.35.2.9.10not-accessibleTable for testing SNMP agent.
rlTstBasicRateEntry1.3.6.1.4.1.89.35.2.9.10.1not-accessibleAn entry in the rlTstBasicRateTable.
INT rlTstBasicRateIfType1.3.6.1.4.1.89.35.2.9.10.1.1INTEGERread-write
INT rlTstBasicRateLineTopology1.3.6.1.4.1.89.35.2.9.10.1.2INTEGERread-write
INT rlTstBasicRateIfMode1.3.6.1.4.1.89.35.2.9.10.1.3INTEGERread-write
INT rlTstBasicRateSignalMode1.3.6.1.4.1.89.35.2.9.10.1.4INTEGERread-write
rlMibTree1.3.6.1.4.1.89.35.2.10
rlMibTreeTable1.3.6.1.4.1.89.35.2.10.1not-accessibleThis reflects the MIB tree of the device.
rlMibTreeEntry1.3.6.1.4.1.89.35.2.10.1.1not-accessibleEach row shows a tree relationsship in the MIB.
STR rlMibTreeFather1.3.6.1.4.1.89.35.2.10.1.1.1DisplayStringnot-accessibleThe father in a tree relation ship.
INT rlMibTreeSonIndex1.3.6.1.4.1.89.35.2.10.1.1.2INTEGERnot-accessibleRunning index for this table.
STR rlMibTreeSon1.3.6.1.4.1.89.35.2.10.1.1.3DisplayStringread-onlyThe son in a tree relation ship.
OID rlMibTreeSonObjectId1.3.6.1.4.1.89.35.2.10.1.1.4OBJECT IDENTIFIERread-onlyThe object identifier of the son in a tree relation ship.
STR rlMibTreeGrandFather1.3.6.1.4.1.89.35.2.10.1.1.5DisplayStringread-onlyThe grand father (i.e father's father) in a tree relation ship.
rsPingMIB1.3.6.1.4.1.89.35.4
rsPingTable1.3.6.1.4.1.89.35.4.1not-accessibleA table of ping request entries.
rsPingEntry1.3.6.1.4.1.89.35.4.1.1not-accessibleA 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.
IP rsPingAddress1.3.6.1.4.1.89.35.4.1.1.1IpAddressread-writeThe address of the device to be pinged. Once an instance of this object is created, its value can not be changed.
INT rsPingPacketCount1.3.6.1.4.1.89.35.4.1.1.2INTEGERread-writeSpecifies the number of ping packets to send to the target in this sequence.
INT rsPingPacketSize1.3.6.1.4.1.89.35.4.1.1.3INTEGERread-writeSpecifies the size of ping packets to send to the target in this sequence. The lower and upper boundaries of this object are implementation dependent.
INT rsPingPacketTimeout1.3.6.1.4.1.89.35.4.1.1.4INTEGERread-writeSpecifies the amount of time to wait for a response to a transmitted packet before declaring the packet 'dropped.'
INT rsPingDelay1.3.6.1.4.1.89.35.4.1.1.5INTEGERread-writeSpecifies 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.
T/F rsPingTrapOnCompletion1.3.6.1.4.1.89.35.4.1.1.6TruthValueread-writeSpecifies 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.
C32 rsPingSentPackets1.3.6.1.4.1.89.35.4.1.1.7Counter32read-onlyThe number of ping packets that have been sent to the target in this sequence.
C32 rsPingReceivedPackets1.3.6.1.4.1.89.35.4.1.1.8Counter32read-onlyThe number of ping packets that have been received from the target in this sequence.
INT rsPingMinReturnTime1.3.6.1.4.1.89.35.4.1.1.9INTEGERread-onlyThe 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.
INT rsPingAvgReturnTime1.3.6.1.4.1.89.35.4.1.1.10INTEGERread-onlyThe 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.
INT rsPingMaxReturnTime1.3.6.1.4.1.89.35.4.1.1.11INTEGERread-onlyThe 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.
INT rsPingCompletionStatus1.3.6.1.4.1.89.35.4.1.1.12INTEGERread-onlyIf 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.
STR rsPingTimeStamp1.3.6.1.4.1.89.35.4.1.1.13DisplayStringread-onlyThe 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:ss
ROW rsPingEntryStatus1.3.6.1.4.1.89.35.4.1.1.14RowStatusread-writeThe status of this table entry.
rsPowerSupplyRedundacy1.3.6.1.4.1.89.35.5
rsPowerSupplyRedundacyTable1.3.6.1.4.1.89.35.5.1not-accessibleThe power supply redundancy table.
rsPowerSupplyRedundacyEntry1.3.6.1.4.1.89.35.5.1.1not-accessibleThe status of power supply redundancy for this table.
INT rsPowerSupplyRedundacyReNumber1.3.6.1.4.1.89.35.5.1.1.1INTEGERread-onlyThis number identifies the module backed up by power supply redundancy in the stack.
INT rsPowerSupplyRedundacyStatus1.3.6.1.4.1.89.35.5.1.1.2INTEGERread-onlyThe status of a power supply redundancy of the entry.
rsNvram1.3.6.1.4.1.89.35.6
STR rsEraseNvramAfterReset1.3.6.1.4.1.89.35.6.1DisplayStringread-writeThe name of NVRAM application that will be erased after reset or ALL if all NVRAM should be erased.
rsNvramApplTable1.3.6.1.4.1.89.35.6.2not-accessibleThe NVRAM application table.
rsNvramApplEntry1.3.6.1.4.1.89.35.6.2.1not-accessibleThe status of NVRAM application table.
INT rsNvramApplIndex1.3.6.1.4.1.89.35.6.2.1.1INTEGERread-onlyThe index of NVRAM application table.
STR rsNvramApplName1.3.6.1.4.1.89.35.6.2.1.2DisplayStringread-onlyThe name of application used NVRAM.

RFC description

Private MIB for RADLAN applications management including alarm options and monitored network elements.

Start monitoring Radlan Computer Communications equipment, R&D monitoring (generic threshold-based OID polling) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download RADLAN-rndApplications