ZTE-AN-DHCP-L2-RELAY-AGENT-MIB

Description: Manages ZTE access node DHCP Layer 2 relay agent configuration including Option 82 insertion.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) 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.

ZTE-AN-DHCP-L2-RELAY-AGENT-MIB is a vendor-specific SNMP module for ZTE access-node equipment such as DSLAM/OLT-class broadband access platforms, defining managed objects for the device's DHCP Layer-2 Relay Agent function, which inserts Option 82 (circuit ID/remote ID) information into subscriber DHCP requests for identification and security purposes at the access edge. Only this instance's conformance section (compliance and object-group definitions) was captured in the sampled objects, so the underlying data/configuration tables -- which per the module's stated purpose would cover relay-agent enable state and Option 82 insertion parameters -- are not directly visible here. Where present, such objects would primarily support configuration/software-feature status monitoring: confirming the DHCP L2 relay agent is enabled and correctly inserting Option 82 data is important for diagnosing subscribers who fail to obtain a DHCP lease or whose sessions can't be traced back to a physical port. It depends on the general DHCP relay agent (Option 82) concept standardized in RFC 3046 and on ZTE's broader access-node enterprise MIB structure for interface indexing. It is deployed on ZTE access nodes in broadband/FTTx access networks where subscriber DHCP sessions are relayed and tagged for identification, and a ZTE-AN-DHCP-L2-RELAY-AGENT-MIB download supplies the object definitions operators need to confirm that Option 82 tagging is active per interface.

The sampled objects for this MIB (zxAnDhcpL2RAConformance, zxAnDhcpL2RACompliances, zxAnDhcpL2RAGroups) are conformance/compliance declarations rather than pollable data objects, so a concrete polling scenario can't be grounded in what was sampled here. Based on the module's stated purpose, an operator would expect to check per-interface DHCP L2 relay agent enable status and Option 82 insertion configuration to confirm subscriber DHCP requests are correctly tagged with circuit/remote ID before troubleshooting a subscriber lease failure.

DHCP Layer-2 Relay Agent management for ZTE access nodes. Handles both DHCPv4 and DHCPv6 L2 relay configuration and VLAN processing.