CISCO-HARDWARE-IP-VERIFY-MIB :: chivIpVerifyPacketsDropped

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-HARDWARE-IP-VERIFY-MIB › chivIpVerifyPacketsDropped

chivIpVerifyPacketsDropped

Module: CISCO-HARDWARE-IP-VERIFY-MIB

OID (symbolic): CISCO-HARDWARE-IP-VERIFY-MIB::chivIpVerifyPacketsDropped

OID (numeric): 1.3.6.1.4.1.9.9.804.1.1.1.4

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: This object indicates the number of packets which has been dropped.

What is chivIpVerifyPacketsDropped?

Reports the number of packets that have been dropped by the hardware IP verification (IDS) check.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.804.1.1.1.4
snmpwalk -v2c -c public <target> CISCO-HARDWARE-IP-VERIFY-MIB::chivIpVerifyPacketsDropped

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.804.1.1.1.4.1
snmpget -v2c -c public <target> CISCO-HARDWARE-IP-VERIFY-MIB::chivIpVerifyPacketsDropped.1

Start monitoring Cisco router or switch with hardware-based IP source verification (uRPF) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-HARDWARE-IP-VERIFY-MIB::chivIpVerifyPacketsDropped OID value, configure state conditions and alerts, and monitor any Cisco router or switch with hardware-based IP source verification (uRPF) from a single console.

How to Use in IPNetwork Monitor

Select a Cisco router or switch with hardware-based IP source verification (uRPF) 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 chivIpVerifyPacketsDropped into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. This object indicates the number of packets which has been dropped. 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 Counter64-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.9.804ciscoHardwareIpVerifyMIBCISCO-HARDWARE-IP-VERIFY-MIB
1.3.6.1.4.1.9.9.804.1ciscoHardwareIpVerifyMIBObjectsCISCO-HARDWARE-IP-VERIFY-MIB
1.3.6.1.4.1.9.9.804.1.1chivIpVerifyTableCISCO-HARDWARE-IP-VERIFY-MIB
1.3.6.1.4.1.9.9.804.1.1.1chivIpVerifyEntryCISCO-HARDWARE-IP-VERIFY-MIB
1.3.6.1.4.1.9.9.804.1.1.1.4chivIpVerifyPacketsDroppedCISCO-HARDWARE-IP-VERIFY-MIB