DHCP-V4-RELAY-MIB: View SNMP OID List / Download MIB
VENDOR: MICROSOFT
| Home | MIB: DHCP-V4-RELAY-MIB | |||
|---|---|---|---|---|
| Download as: |
Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
|
|||
| Object Name | OID | Type | Access | Info |
| dhcpv4Relay | 1.3.6.1.4.1.311.1.3.3 |
The MIB module for entities implementing the Relay Agent part of the Bootstrap Protocol (BOOTP) and the Dynamic Host Configuration protocol (DHCP) for Internet Protocol version 4(IPv4). Copyright (C) The Internet Society (2004). This version of this MIB module is part of RFC xxxx; see the RFC itself for full legal notices. |
||
| dhcpv4RelayObjects | 1.3.6.1.4.1.311.1.3.3.1 |
DHCP Relay MIB identification objects are all defined in this branch. |
||
| dhcpv4RelaySystem | 1.3.6.1.4.1.311.1.3.3.1.1 |
Group of objects that are related to the overall system. |
||
| dhcpv4RelaySystemDescr | 1.3.6.1.4.1.311.1.3.3.1.1.1 |
A textual description of the relay. This value should have the FQDN name. |
||
| dhcpv4RelaySystemObjectID | 1.3.6.1.4.1.311.1.3.3.1.1.2 |
The vendors authoritative identification of the network management subsystem contained in this entity. This value is allocated within the SMI enterprise subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determining what kind of relay is being managed. For example, if vendor Ohso Soft, Inc. is assigned the subtree 1.3.6.1.4.1.4242, it may assign the identifier 1.3.6.1.4.1.4242.1.1 to its Ursa DHCP Relay. |
||
| maxHopCountAllowed | 1.3.6.1.4.1.311.1.3.3.1.1.3 |
The maximum hop count that a DHCP/BOOTP packet can have to pass through the relay |
||
| dhcpv4RelayandServer | 1.3.6.1.4.1.311.1.3.3.1.1.4 |
The type of the Relay. The types are: (1) Acts only as DHCP Relay. (2) Acts as both as DHCP Relay and Server for independent networks |
||
| seconds | 1.3.6.1.4.1.311.1.3.3.1.1.5 |
The time interval for which the relay chooses a server. In the subsequent seconds interval the relay chooses the next server in the list for relaying the packets from the clients. |
||
| relaySubnettoServerMapTable | 1.3.6.1.4.1.311.1.3.3.1.1.6 |
The list of subnets that the relay manages. This table maps the subnets with a list of servers serving them along with the maximum seconds value the BOOTP/DHCP packet can have to make the relay to choose a server, beyond which the relay chooses the next server in the list. The server list will be an ordered list of preference. |
||
| 1.3.6.1.4.1.311.1.3.3.1.1.6.1 |
A logical row in the relaySubnettoServerMapEntry. |
|||
| clientSubnetID | 1.3.6.1.4.1.311.1.3.3.1.1.6.1.1 |
The subnet address of the link on which the client resides |
||
| serverAddress | 1.3.6.1.4.1.311.1.3.3.1.1.6.1.2 |
The address of the DHCP/BOOTP server. |
||
| relayNetToSerMapStatus | 1.3.6.1.4.1.311.1.3.3.1.1.6.1.3 |
The status column used for creating, modifying, and deleting instances of the columnar objects in the relaySubnettoServerMapEntry table. |
||
| relayCounters | 1.3.6.1.4.1.311.1.3.3.1.2 |
Group of objects that count various BOOTP Relay events. |
||
| relayToServerCount | 1.3.6.1.4.1.311.1.3.3.1.2.1 |
The number of BOOTREQUEST packets that are relayed to the servers. |
||
| relayToClientCount | 1.3.6.1.4.1.311.1.3.3.1.2.2 |
The number of BOOTREPLY packets that are relayed back to the clients |
||
| relayCountInvalids | 1.3.6.1.4.1.311.1.3.3.1.2.3 |
The number of BOOTP packets dropped by the relay without forwarding (e.g., hop count exceeded the limit). |
||
| giaddrSpoofCount | 1.3.6.1.4.1.311.1.3.3.1.2.4 |
Number of DHCP packets arrived with giaddr spoofed the relays address |
||
| dhcpv4RAIFObjects | 1.3.6.1.4.1.311.1.3.3.1.3 |
Objects that are associated with Relay Agent Information Option |
||
| dhcpv4RAIFOption | 1.3.6.1.4.1.311.1.3.3.1.3.1 |
Enables/Disables addition of RAIF Option by the Relay. The values are: (1) Enables addition of RAIF Option by the Relay. (2) Disables addition of RAIF Option by the Relay. |
||
| maxPktSizeWithRAIFOption | 1.3.6.1.4.1.311.1.3.3.1.3.2 |
Maximux size of a DHCP packet after including RAIF Option that is allowed to pass through the Relay |
||
| dhcpv4RAIFCounterObject | 1.3.6.1.4.1.311.1.3.3.1.3.3 | |||
| sizeWithRAIFExceedLimitCount | 1.3.6.1.4.1.311.1.3.3.1.3.3.1 |
Number of DHCP packets exceeded the maximum size after including RAIF Option. |
||
| relayOptionAddedCount | 1.3.6.1.4.1.311.1.3.3.1.3.3.2 |
Number of RAIF Option added by the relay while forwarding to the servers |
||
| relayOptionRemovedCount | 1.3.6.1.4.1.311.1.3.3.1.3.3.3 |
Number of RAIF Option removed by the relay while forwarding to the clients |
||
| incorrectRAIFOptionCount | 1.3.6.1.4.1.311.1.3.3.1.3.3.4 |
Number of incorrect RAIF Option in DHCP packet received by the relay |
||
| docsisDCISubOptionAddedCount | 1.3.6.1.4.1.311.1.3.3.1.3.3.5 |
Number of DOCSIS-DCI SubOption added by the relay while forwarding to the servers |
||
| docsisDCISubOptionRemoved | 1.3.6.1.4.1.311.1.3.3.1.3.3.6 |
Number of DOCSIS-DCI SubOption removed by the relay while forwarding to the servers |
||
| linkSelSubOptionAddedCount | 1.3.6.1.4.1.311.1.3.3.1.3.3.7 |
Number of Link Selection SubOption added by the relay while forwarding to the servers |
||
| linkSelSubOptionRemovedCount | 1.3.6.1.4.1.311.1.3.3.1.3.3.8 |
Number of Link Selection SubOption removed by the relay while forwarding to the servers |
||