tmnxDhcpSvrMsgTooLong
TIMETRA-DHCP-SERVER-MIB ·
.1.3.6.1.4.1.6527.3.1.3.47.0.6
Object
notification
The tmnxDhcpSvrMsgTooLong notification is generated when a DHCP
message is built, but the message size either exceeds the maximum DHCP
message size or the size provided by the client in the option maximum
DHCP message size. A reason can be that too many options are defined
on host, pool and subnet levels.
This notification is only generated for DHCP server instances with the
value of tmnxDhcpServerCfgAddrType set to 'ipv4(1)'.
Context
- MIB
- TIMETRA-DHCP-SERVER-MIB
- OID
.1.3.6.1.4.1.6527.3.1.3.47.0.6- Type
- notification
- Status
- current
- Parent
- tmnxDhcpServerNotifications
- Groups
- 1
Net-SNMP examples
How SNMP and these commands workNotifications are emitted by an agent; they cannot be read with snmpget or walked.
Inspect the notification definition
/usr/bin/snmptranslate -Pud -Ir -Td -m 'TIMETRA-DHCP-SERVER-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-DHCP-SERVER-MIB::tmnxDhcpSvrMsgTooLong'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'TIMETRA-DHCP-SERVER-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-DHCP-SERVER-MIB::tmnxDhcpSvrMsgTooLong'
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.
Conformance
Member of