ZTE-AN-SECURITY-CPUDEFEND-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › ZTE-AN-SECURITY-CPUDEFEND-MIB

Organization: ZTE Corporation

Last Updated: 2019-03-05

Category: Network Security, ZTE Access Node (ZTE-AN) Management

Description: Manages ZTE access node CPU protection policies to rate-limit protocol traffic and defend against DoS.

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.

What Is ZTE-AN-SECURITY-CPUDEFEND-MIB?

ZTE-AN-SECURITY-CPUDEFEND-MIB is part of ZTE's Access Node security feature set and implements CPU protection (control-plane policing) that rate-limits specific protocol or packet types via ACL-style classification to defend the management CPU from flood-style DoS conditions. It exposes rate-limit policy configuration per protocol/packet type and, where supported, counters tracking packets dropped or rate-limited by the defense policy. It is a control-plane/software health monitor: it reveals whether the device's CPU is being overwhelmed by broadcast storms, malformed packets, or protocol floods originating from subscriber CPE, and whether the configured defense policy is actually catching them. It builds on general ACL/QoS rate-limiting concepts and is typically deployed alongside ZTE's other AN security modules such as traffic isolation. It is typically deployed at the network edge to keep access node control planes stable under attack or misbehaving-device conditions. Engineers can download the ZTE-AN-SECURITY-CPUDEFEND-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in ZTE-AN-SECURITY-CPUDEFEND-MIB. 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.

Supported Devices

  • ZTE access node (DSLAM/OLT/Ethernet access switch)

Monitoring Examples

No specific object names were present in the source, so the following scenario is inferred from module_desc: an operator configures per-protocol CPU-defend rate limits (for example on ARP or DHCP traffic) and then polls the associated drop/rate-limit counters to detect an ongoing flood. A sudden spike in the drop count for a particular packet class would indicate an active attack or a misbehaving subscriber device overwhelming the control plane.

What Can Be Monitored

  • per-protocol CPU rate-limit configuration
  • dropped/rate-limited packet counters
  • control-plane traffic classification by protocol

This MIB depends on

Related MIBs

Imported Objects

From IF-MIB

ifIndexOBJECT-TYPE

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From SNMPv2-SMI

Counter32
Gauge32
Integer32
MODULE-IDENTITY
MacAddress
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

DateAndTime
RowStatus
TEXTUAL-CONVENTION

From ZTE-AN-IF-MIB

zxAnSubIfIndexOBJECT-TYPE

From ZTE-AN-SMI

zxAnServiceSecurityOBJECT-IDENTITY

From ZTE-AN-TC-MIB

VlanId

How to Use in IPNetwork Monitor

Example using zxAnSecCpuAclTcpPkts OID:

Select a ZTE access node (DSLAM/OLT/Ethernet access switch) (CPU-protection rate-limit/drop-counter status) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type zxAnSecCpuAclTcpPkts into the Find box to locate it in the OID tree, then select it and click OK. It reports the total number of TCP packets. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

ZTE Access Network SNMP MIB module for CPU defense security mechanisms, defining management objects to monitor and configure CPU load protection against denial-of-service attacks on ZTE routing and switching devices.

Start monitoring ZTE access node (DSLAM/OLT/Ethernet access switch) (CPU-protection rate-limit/drop-counter 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.

Download ZTE-AN-SECURITY-CPUDEFEND-MIB