Home/Catalog/DLINK-3100-SNMP-MIB

DLINK-3100-SNMP-MIB

Private MIB module for SNMP support in DLINK-3100 devices.
Main OID:
rlSNMP.1.3.6.1.4.1.171.10.94.89.89.98
57
Objects
Active
Status
5
Dependencies

Imported Objects

Objects

57 total
Object Name
rlSNMPPrivate MIB module for SNMP support in DLINK-3100 devices.
MODULE-IDENTITY
.1.3.6.1.4.1.171.10.94.89.89.98
rlSNMPv3
OBJECT IDENTIFIER
.1.3.6.1.4.1.171.10.94.89.89.98.1
rlTargetParamsTestingLevelThe level of the tests done when configuring an entry in the snmpTargetParamsTable.rw
Enumeration
.1.3.6.1.4.1.171.10.94.89.89.98.1.1
rlNotifyFilterTestingLevelThe level of the tests done when configuring an entry in the snmpNotifyFilterTable.rw
Enumeration
.1.3.6.1.4.1.171.10.94.89.89.98.1.2
rlSnmpEngineIDA variable for setting the router's local engineID value. Setting this variable will effect the value of snmpEngineID. Setting this variable to the value '00 00 00 00 00'H will cause snmpEngineID to get an automatically created value based on the device basic MAC address. This method of setting the agent's engineID is recommended for stand-alone systems. Setting this variable to any other (valid) value will set snmpEngineID to this value. Setting this variable to all 'ff'H or all zeros is not allowed, with the exception of the value '00 00 00 00 00'H. The last method is recommended for stackable system, in order for the engineID to be unique within an administrative domain. Setting this value (to a value different then the default value) is required before configuring users data in usmUserTable and vacmSecurityToGroupTable. Changing the value of this variable has 2 side-effects: - All user data will be deleted, including: all usmUserTable configured entries and vacmSecurityToGroupTable entries where vacmSecurityModel = 3. - All snmpCommunityTable entries with snmpCommunityContextEngineID value equal to old rlSnmpEngineID value, will be updated with the new rlSnmpEngineID value.rw
OCTET STRING
.1.3.6.1.4.1.171.10.94.89.89.98.1.3
rlSNMPv3IpAddrToIndexTableThis table maps ip addresses to indices. The output index is used as a component in some SNMPv3 tables fields (for example: snmpTargetAddrName). Ipv4 addresses are not supported by this table. Note: in getNext operations on this table, only mappings which are in use in snmpTargetAddrTable (using rlTargetAddrMagicUsedInIndex) will be retreived. The mapped index does not include delimiters which are forbidden in SNMPv3 tag values (and thus can be used in tag fields).
SEQUENCE OF RlSNMPv3IpAddrToIndexEntry
.1.3.6.1.4.1.171.10.94.89.89.98.1.4
rlSNMPv3IpAddrToIndexEntryThe row definition for this table.
RlSNMPv3IpAddrToIndexEntry
.1.3.6.1.4.1.171.10.94.89.89.98.1.4.1
rlSNMPv3IpAddrToIndexAddrTypeType of NMS IP address.
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.171.10.94.89.89.98.1.4.1.1
rlSNMPv3IpAddrToIndexAddrNMS IP address.
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.171.10.94.89.89.98.1.4.1.2
rlSNMPv3IpAddrToIndexMappedIndexThe index mapped for this row ip address.ro
OCTET STRING
.1.3.6.1.4.1.171.10.94.89.89.98.1.4.1.3
rlTargetAddrExtTableThis table extends rlTargetAddrExtEntry.
SEQUENCE OF RlTargetAddrExtEntry
.1.3.6.1.4.1.171.10.94.89.89.98.1.5
rlTargetAddrExtEntryThe row definition for this table.
RlTargetAddrExtEntry
.1.3.6.1.4.1.171.10.94.89.89.98.1.5.1
rlTargetAddrMagicUsedInIndexSetting this field to a 4 octets length value means that ip mapping (using rlSNMPv3IpAddrToIndexTable) is used for this row. If such a mapping is not used, a 0-length octet string value should be used for this field (this is also the default). This field value is determined only once, upon creation of an entry in the snmpTargetAddrTable. A change in its value while updating an existing entry is ignored. Prior to creating a snmpTargetAddrTable entry with a 4 octets length value for this field, the rlSNMPv3IpAddrToIndexTable must be used in order to retrieve this value.rw
OCTET STRING
.1.3.6.1.4.1.171.10.94.89.89.98.1.5.1.1
rlSNMPDomains
OBJECT IDENTIFIER
.1.3.6.1.4.1.171.10.94.89.89.98.2
rlSnmpUDPMridDomainThe SNMPv2 over UDP transport domain, used when Multi-Instance Router is supported (more than one MIR instance exist). The corresponding transport address is of type RlSnmpUDPMridAddress.
OBJECT IDENTIFIER
.1.3.6.1.4.1.171.10.94.89.89.98.2.1
rlSnmpUdpIpv6MridDomainThe SNMPv2 over UDP over IPv6 transport domain, used when Multi-Instance Router is supported (more than one MIR instance exist). The corresponding transport address is of type RlSnmpUDPIpv6MridAddress for global IPv6 addresses.
OBJECT IDENTIFIER
.1.3.6.1.4.1.171.10.94.89.89.98.2.2
rlSnmpUdpIpv6zMridDomainThe SNMPv2 over UDP over IPv6 transport domain, used when Multi-Instance Router is supported (more than one MIR instance exist). The corresponding transport address is of type RlSnmpUDPIpv6zMridAddress for scoped IPv6 addresses with a zone index.
OBJECT IDENTIFIER
.1.3.6.1.4.1.171.10.94.89.89.98.2.3
rlSnmpRequestMridTableA table for determining the Mrid for the current SNMP request.
SEQUENCE OF RlSnmpRequestMridEntry
.1.3.6.1.4.1.171.10.94.89.89.98.3
rlSnmpRequestMridEntryThe row definition for this table.
RlSnmpRequestMridEntry
.1.3.6.1.4.1.171.10.94.89.89.98.3.1
rlSnmpRequestManagedMridThe router instance the NMS wants to manage in the current SNMP request. The value of this object, when attaching a variable instance of the rlSnmpRequestManagedMridTable to an SNMP request, will determine the managed Mrid for this request. It is important to mention that the variable insance must be attached as the first variable in the PDU in order to influence all variables.ro
INTEGER
.1.3.6.1.4.1.171.10.94.89.89.98.3.1.1
rlSnmpRequestMridStatusThe status of this entry.rw
Enumeration
.1.3.6.1.4.1.171.10.94.89.89.98.3.1.2
rlSNMPenableEnables or disables SNMP.rw
Enumeration
.1.3.6.1.4.1.171.10.94.89.89.98.4
rndCommunityInetTableThe community table of the agent
SEQUENCE OF RndCommunityInetEntry
.1.3.6.1.4.1.171.10.94.89.89.98.5
rndCommunityInetEntryThe row definition for this table.
RndCommunityInetEntry
.1.3.6.1.4.1.171.10.94.89.89.98.5.1
rndCommunityInetMngStationAddrTypeAddress type of the management station that will be allowed to communicate with the agent IP address
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.171.10.94.89.89.98.5.1.1
rndCommunityInetMngStationAddrAddress of the management station that will be allowed to communicate with the agent IP address
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.171.10.94.89.89.98.5.1.2
rndCommunityInetStringThe community string with which the management station will communicate with the agent
DisplayString
.1.3.6.1.4.1.171.10.94.89.89.98.5.1.3
rndCommunityInetAccessThe allowed access to this management stationrw
Enumeration
.1.3.6.1.4.1.171.10.94.89.89.98.5.1.4
rndCommunityInetTrapsEnableShould the agent send traps to the management station, and what version is requiredrw
Enumeration
.1.3.6.1.4.1.171.10.94.89.89.98.5.1.5
rndCommunityInetStatusThe status of this entry. If the status is invalid the community entry will be deletedrw
Enumeration
.1.3.6.1.4.1.171.10.94.89.89.98.5.1.6
rndCommunityInetPortSecurityIf enabled the device will only receive SNMP messages from the port, through which this NMS is reachable from the device.rw
Enumeration
.1.3.6.1.4.1.171.10.94.89.89.98.5.1.7
rndCommunityInetOwnerThe owner of this communityrw
DisplayString
.1.3.6.1.4.1.171.10.94.89.89.98.5.1.8
rndCommunityInetTrapDestPortThe transport protocol (usually UDP) port to which traps to the management station represebted by this entry will be sent. The default is the well-known IANA assigned port number for SNMP traps. This object is relevant only if rndCommunityInetTrapsEnable has a value different from trapsDisable.rw
INTEGER
.1.3.6.1.4.1.171.10.94.89.89.98.5.1.9
rndCommunityInetAltAddrTypeFor testing purposesrw
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.171.10.94.89.89.98.5.1.10
rndCommunityInetAltAddrFor testing purposesrw
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.171.10.94.89.89.98.5.1.11
rlMridInetTableThe MRID related configurations table of the agent
SEQUENCE OF RlMridInetEntry
.1.3.6.1.4.1.171.10.94.89.89.98.6
rlMridInetEntryThe row definition for this table.
RlMridInetEntry
.1.3.6.1.4.1.171.10.94.89.89.98.6.1
rlMridInetConnectionThe router instance connecting the NMS who accessed the agent through the community table entry corresponding to the keys of this entry.rw
INTEGER
.1.3.6.1.4.1.171.10.94.89.89.98.6.1.1
rlInetManagedMridThe router instance currently managed by the NMS who accessed the agent through the community table entry corresponding to the keys of this entryrw
INTEGER
.1.3.6.1.4.1.171.10.94.89.89.98.6.1.2
rlEvents
OBJECT IDENTIFIER
.1.3.6.1.4.1.171.10.94.89.89.98.7
rlEventsPollerIdThe rlEventsPollerId is the 1st key in all the rlEvents tables. Each poller must first GET from this object his Id. The agent will ensure uniqueness.ro
INTEGER
.1.3.6.1.4.1.171.10.94.89.89.98.7.1
rlEventsDefaultPollingIntervalThe default polling time. Will be used to detrermined whether the events configured by a poller in rlEventsTable can be destroyed, in absence of an entry for this poller in the rlEventsPollingControlTable.rw
TimeTicks
.1.3.6.1.4.1.171.10.94.89.89.98.7.2
rlEventsDeleteEventsSETting a id of an active poller will cause all the rows of this poller in the rlEventsTable to be destroyed. This is equivalent to SETting rlEventsStatus of each row of this poller to 'destroy'. GET operation on this variable is meaningless, and the value 0 will be returned in this case (actual pollers start from 1).rw
INTEGER
.1.3.6.1.4.1.171.10.94.89.89.98.7.3
rlEventsMaskTableThe table showing the events mask for each client.
SEQUENCE OF RlEventsMaskEntry
.1.3.6.1.4.1.171.10.94.89.89.98.7.4
rlEventsMaskEntryThe row definition for this table.
RlEventsMaskEntry
.1.3.6.1.4.1.171.10.94.89.89.98.7.4.1
rlEventsMaskPollerIdThe poller id whose events are shown in this table
INTEGER
.1.3.6.1.4.1.171.10.94.89.89.98.7.4.1.1
rlEventsMaskMaskThe semantics of the rlEventsMask is an array of timestamps (each 4 octets containing one time stamp). Each timestamp is in TimeTicks units encoded in network order. Thus the mask can contain up to 40 timestamps. If a place in the array is empty it will contain 0. Each timestamp shows the time of the last occurrence of the event whose rlEventIndexKey in the rlEventsTable for this client id is the same as its index in the array. Each for bytes of the rlEventsMask will contain the timestamp in TimeTicks units encoded in network order of the last time the eventro
OCTET STRING
.1.3.6.1.4.1.171.10.94.89.89.98.7.4.1.2
rlEventsTableThe table relating the events recorded to the indices in the rlEventsMask.
SEQUENCE OF RlEventsEntry
.1.3.6.1.4.1.171.10.94.89.89.98.7.5
rlEventsEntryThe row definition for this table.
RlEventsEntry
.1.3.6.1.4.1.171.10.94.89.89.98.7.5.1
rlEventsPollerThe poller id whose event definitions are shown in this table.
INTEGER
.1.3.6.1.4.1.171.10.94.89.89.98.7.5.1.1
rlEventIdThe event id of the polled event. This is the notification object identifier (in case of a SNMPV2 notification) or the translation to SNMPv2 notation of an SNMPv1 trap according to the RFC 3584 (SNMP versions coexistence).
OBJECT IDENTIFIER
.1.3.6.1.4.1.171.10.94.89.89.98.7.5.1.2
rlEventIndexInMaskIndex in the rlEventsMaskMask of this poller id that has been allocated for this event by the device.ro
INTEGER
.1.3.6.1.4.1.171.10.94.89.89.98.7.5.1.3
rlEventsStatusRowStatus for this table. Note that the device may refuse for resource shortage reasons to honour a create request for this poller even if apparently there still is room in his rlEventsMaskMask (i.e. the poller has requested monitoring of less than 40 events).rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.171.10.94.89.89.98.7.5.1.4
rlEventsPollingControlTableThe polling control table for a poller. Currently contain only the polling interval.
SEQUENCE OF RlEventsPollingControlEntry
.1.3.6.1.4.1.171.10.94.89.89.98.7.6
rlEventsPollingControlEntryThe row definition for this table.
RlEventsPollingControlEntry
.1.3.6.1.4.1.171.10.94.89.89.98.7.6.1
rlEventsPollingControlPollerIdThe poller id whose polling controls are shown in this table.
INTEGER
.1.3.6.1.4.1.171.10.94.89.89.98.7.6.1.1
rlEventsPollingControlPollingIntervalThe desired polling interval for this poller. If the device has determined that the poller has not polled the device for 3 times this polling interval it may destroy all the data related to this poller in the rlevents databaserw
TimeTicks
.1.3.6.1.4.1.171.10.94.89.89.98.7.6.1.2
DLINK-3100-SNMP-MIB - SNMP MIB Reference | MIBs Explorer