CISCO-FILTER-GROUP-MIB :: cfgFilterIpProtocolNumber

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-FILTER-GROUP-MIBcfgFilterIpProtocolNumber

cfgFilterIpProtocolNumber

Module: CISCO-FILTER-GROUP-MIB

OID (symbolic): CISCO-FILTER-GROUP-MIB::cfgFilterIpProtocolNumber

OID (numeric): 1.3.6.1.4.1.9.9.474.1.1.3.1.2

Node type: OBJECT-TYPE

Type: CiscoIpProtocol

Access: read-write

Description: This object identifies the internet protocol number in the packets. These IP protocol numbers are defined in the Network Group Request For Comments(RFC) documents. For example, Cisco commonly used protocol includes: 1 - Internet Control Message Protocol (ICMP) 2 - Internet Gateway Message Protocol (IGMP) 4 - IP in IP tunneling 6 - Transmission Control Protocol (TCP) 9 - Cisco's IGRP routing protocol (IGRP) 17 - User Datagram Protocol (UDP) 47 - Cisco's GRE tunneling (GRE) 50 - Encapsulation Security Payload 51 - Authentication Header Protocol 88 - Cisco's EIGRP routing protocol 89 - OSPF routing protocol 94 - KA9Q NOS compatible IP over IP tunneling 103 - Protocol Independent Multicast 108 - Payload Compression Protocol.

What is cfgFilterIpProtocolNumber?

This specifies the IP protocol number this filter entry matches against, using the standard RFC-assigned protocol numbers, with Cisco's own listed examples including ICMP(1), IGMP(2), IP-in-IP(4), TCP(6), and Cisco's own IGRP(9). Because these numbers correspond to well-known protocols, getting this value wrong, for example confusing protocol 6/TCP with protocol 17/UDP, would cause the filter to silently match or exclude entirely the wrong kind of traffic without any obvious error. A filter group intended to specifically block ICMP-based reconnaissance traffic, like ping sweeps, would need this object set to 1, not, say, 6 for TCP, or the filter would fail to catch the ICMP traffic it was actually meant to block.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.474.1.1.3.1.2
snmpwalk -v2c -c public <target> CISCO-FILTER-GROUP-MIB::cfgFilterIpProtocolNumber

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.474.1.1.3.1.2.1
snmpget -v2c -c public <target> CISCO-FILTER-GROUP-MIB::cfgFilterIpProtocolNumber.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.9.9.474.1.1.3.1.2.1 s <value>

Start monitoring Cisco IOS routers/switches (object-group-based ACLs) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-FILTER-GROUP-MIB::cfgFilterIpProtocolNumber OID value, configure state conditions and alerts, and monitor any Cisco IOS routers/switches (object-group-based ACLs) from a single console.

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.474ciscoFilterGroupMIBCISCO-FILTER-GROUP-MIB
1.3.6.1.4.1.9.9.474.1ciscoFilterGroupMIBObjectsCISCO-FILTER-GROUP-MIB
1.3.6.1.4.1.9.9.474.1.1cfgFilterConfigCISCO-FILTER-GROUP-MIB
1.3.6.1.4.1.9.9.474.1.1.3cfgFilterIpProtocolGroupTableCISCO-FILTER-GROUP-MIB
1.3.6.1.4.1.9.9.474.1.1.3.1cfgFilterIpProtocolGroupEntryCISCO-FILTER-GROUP-MIB
1.3.6.1.4.1.9.9.474.1.1.3.1.2cfgFilterIpProtocolNumberCISCO-FILTER-GROUP-MIB