All MIBs › CHECKPOINT-MIB-2 › ipFragOKs
ipFragOKs
Module: CHECKPOINT-MIB-2
OID (symbolic): CHECKPOINT-MIB-2::ipFragOKs
OID (numeric): 1.3.6.1.2.1.4.17
Node type: OBJECT-TYPE
Type: Counter
Access: read-only
Description: The number of IP datagrams that have been successfully fragmented at this entity.
What is ipFragOKs?
Counts IP datagrams this device successfully fragmented before forwarding them onward. Seeing this counter increase at all on a firewall usually means outbound packets exceed the next hop's MTU, such as a VPN tunnel with encapsulation overhead, so a rise on tunnel interfaces is expected, but a rise on a plain LAN-to-LAN path suggests an MTU mismatch worth fixing rather than living with the fragmentation overhead. Example: ipFragOKs climbing specifically on tunnel interfaces after enabling a new encryption suite that adds header overhead explains new fragmentation that wasn't happening before.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.4.17 snmpwalk -v2c -c public <target> CHECKPOINT-MIB-2::ipFragOKs
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.4.17.1 snmpget -v2c -c public <target> CHECKPOINT-MIB-2::ipFragOKs.1
Start monitoring Check Point security gateway/firewall appliances with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CHECKPOINT-MIB-2::ipFragOKs OID value, configure state conditions and alerts, and monitor any Check Point security gateway/firewall appliances from a single console.
OID Breakdown
Upper-level ancestors (6 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.2 | mgmt | AXON-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.4 | ip | CHECKPOINT-MIB-2 |
| 1.3.6.1.2.1.4.17 | ipFragOKs | CHECKPOINT-MIB-2 |