All MIBs › CISCO-IP-PROTOCOL-FILTER-MIB
Organization: Cisco System Inc.
Last Updated: 2005-04-20
Category: Cisco Devices, IP and Core Protocols
Description: Manages IP protocol-based packet filtering rules applied to network interfaces.
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 CISCO-IP-PROTOCOL-FILTER-MIB?
CISCO-IP-PROTOCOL-FILTER-MIB manages IP protocol-based packet filtering profiles applied to interfaces on Cisco routers and switches, belonging to the network security/access-control management area. It exposes configuration data for filter profiles (simple or extended usage types), their per-interface application and direction, and individual filter rule entries. This supports monitoring the configuration/security status of filtering policy on a device, since checking which cippfIfIpProfileName and cippfIfIpProfileDirection are applied to an interface reveals whether the intended access-control policy is actually in effect, and a missing or wrong profile assignment would indicate a security gap. It has no stated dependency on other MIBs beyond standard interface indexing. It is typically deployed in enterprise or service-provider edge devices enforcing protocol-based traffic filtering for security or policy compliance. Engineers can download the CISCO-IP-PROTOCOL-FILTER-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-IP-PROTOCOL-FILTER-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
- Cisco routers
- Cisco switches
Monitoring Examples
An administrator checks cippfIpProfileTable (cippfIpProfileEntry rows keyed by cippfIpProfileName) to confirm a filter profile's cippfIpProfileType (Simple or Extended) and cippfIpProfileStatus are correctly configured. Then cippfIfIpProfileTable (cippfIfIpProfileEntry) is checked to verify the profile is actually applied to the intended interface with the correct cippfIfIpProfileDirection (inbound/outbound). An interface missing its expected cippfIfIpProfileName entry would indicate the security filter was never applied or was removed.
What Can Be Monitored
- filter profile configuration
- profile usage type (simple/extended)
- interface-to-profile assignment
- filter direction
- filter profile status
- individual filter rules
This MIB depends on
Related MIBs
Imported Objects
| CfgFilterGroupName |
From CISCO-SMI
| ciscoMgmt | OBJECT-IDENTITY |
From CISCO-SYSLOG-MIB
| SyslogSeverity |
From IF-MIB
| ifIndex | OBJECT-TYPE |
From INET-ADDRESS-MIB
| InetAddress | |
| InetAddressType | |
| InetPortNumber |
From SNMP-FRAMEWORK-MIB
| SnmpAdminString |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Counter64 | |
| Integer32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| Unsigned32 |
From SNMPv2-TC
| RowStatus | |
| TEXTUAL-CONVENTION | |
| TruthValue |
How to Use in IPNetwork Monitor
Example using cippfIpFilterHits OID:
Select a Cisco router or switch (IP protocol filtering) 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 cippfIpFilterHits 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 specifies the number of packets that are matched the packet filter configuration in cippfIpFilterTable. 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 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
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| ciscoIpProtocolMIB | 1.3.6.1.4.1.9.9.278 | The MIB module is for management of information to support packet filtering on IP protocols. The cippfIpProfileTable allows users to create delete, and get information about filter profiles. Filter profiles are uniquely identified by the profile names. Filter profiles can either be of Simple or Extended usage types, and the usage type cannot be changed once it has been created. The cippfIfIpProfileTable applies the filtering profiles to device interfaces running IP. A filter profile can be applied to multiple interfaces. The cippfIpFilterTable contains ordered lists of IP filters for all the filtering profiles. Filters and profiles are related if they are of the same filter profile name. Filters can only be created if their associated filter profiles already exist in the cippfIpProfileTable. Filters of the same profile name belongs to a common profile. The cippfIfIpProfileTable can be configured with information independent from the other. However, if the name of a profile in the cippfIfIpProfileTable matches that of any profile in the cippfIpProfileTable and the profile name of any filter entry in the cippfIpFilterTable, the profile is 'active' and the filter entry is being applied to IP traffic passing through the attached device interfaces. Therefore, any change to the filters in the cippfIpFilterTable or the profile itself in the cippfIpProfileTable will affect all the attached interfaces. | ||
| ciscoIpProtocolFilterMIBNotifs | 1.3.6.1.4.1.9.9.278.0 | |||
| ciscoIpProtocolFilterMIBObjects | 1.3.6.1.4.1.9.9.278.1 | |||
| cippfIpFilterConfig | 1.3.6.1.4.1.9.9.278.1.1 | |||
| cippfIpProfileTable | 1.3.6.1.4.1.9.9.278.1.1.1 | not-accessible | This table lists all the existing IP protocol filter profiles. These filter profiles contain protocol filters used to filter IP traffic through the device interfaces. The IP protocol filters associated with these profiles are defined in the cippfIpFilterTable. For profiles to be associated with filters, the object value of the cippfIpProfileName of a profile must matches that of the cippfIpProfileName of a filter entry in the cippfIpFilterTable. Filters of the same profile name belong to a common filter profile and are of the same usage type of the profile. This table can only be used to create or delete filter profiles. Deleting any profile in this table will also delete all the associated filters in the cippfIpFilterTable and cause the state of the associated 'active' filter profile in the cippfIfIpProfileTable to be changed to 'notReady'. All of these deleted or changed entries are associated by virtue of the same profile name. | |
| cippfIpProfileEntry | 1.3.6.1.4.1.9.9.278.1.1.1.1 | not-accessible | Each entry defines the type, state, and the last object index assigned to a filter of the filter profile. | |
| CIP cippfIpProfileName | 1.3.6.1.4.1.9.9.278.1.1.1.1.1 | CippfIpFilterProfileName | not-accessible | This is the unique IP protocol filter profile identifier. If this value is the same as the cippfIpProfileName in the cippfIpFilterTable and the cippfIfIpProfileName in cippfIfIpFilterTable, they are all referring to the same filter profile. |
| INT cippfIpProfileType | 1.3.6.1.4.1.9.9.278.1.1.1.1.2 | INTEGER | read-create | This object determines the usage type this filter profile. This usage type cannot be changed after the profile has been created. The usage type simple(1) implies that the valid objects of each filter entry in the profile in the cippfIpFilterTable only include: cippfIpFilterIndex, cippfIpFilterOrderPosition, cippfIpFilterAction, cippfIpFilterAddressType, cippfIpFilterSrcAddress, cippfIpFilterSrcMask, cippfIpFilterLogEnabled, cippfIpFilterStatus. This means that only the above objects will be used to create the protocol filter, and all other objects will be ignored during filter creation. The usage extended(2) implies that all objects defined in the cippfIpFilterTable are valid for any filter entry in the corresponding profile. The usage extendedIPv6(3) implies that this is a IPv6 profile and all objects defined in the cippfIpFilterTable are valid for any filter entry in the corresponding profile. |
| U32 cippfIpProfileLastFilterIndex | 1.3.6.1.4.1.9.9.278.1.1.1.1.3 | Unsigned32 | read-only | This value is the same as the last cippfIpFilterIndex value assigned to a filter of this profile. |
| ROW cippfIpProfileStatus | 1.3.6.1.4.1.9.9.278.1.1.1.1.4 | RowStatus | read-create | This object controls and reflects the status of rows in this table. To create a filter profile of a particular usage type, the NMS must do a multivarbind set containing both cippfIpProfileStatus and cippfIpProfileType. Creation of rows must be done via 'createAndGo' for all profiles. When the agent successfully creates the filter profile, this object is set to 'active' by the agent. To delete a row, set this object value to 'destroy'. |
| cippfIfIpProfileTable | 1.3.6.1.4.1.9.9.278.1.1.2 | not-accessible | This table lists all the IP protocol filter profiles being applied to IP traffic on the device interfaces. An IP protocol filter profile can be shared by multiple interfaces. The filter profiles are defined in the cippfIpProfileTable, and filters of these profiles are defined in the cippfIpFilterTable. Protocol filter profiles and their associated filters can be 'attached to' or 'removed from' in-bound or out-bound interfaces. Both existing and non-existing protocol filter profiles can be 'attached to' the interfaces. However, the cippfIfIpProfileStatus will only become 'active' if the filter profile exists in the cippfIpProfileTable, and the filters will then be applied to the IP traffic through the interface. Modification of any filters associated with a shared profile will affect all interfaces sharing that profile. Each interface can only be attached with one protocol filter profile on the in-bound direction and one on the out-bound direction. | |
| cippfIfIpProfileEntry | 1.3.6.1.4.1.9.9.278.1.1.2.1 | not-accessible | Each entry attaches an IP traffic filter profile to a particular device interface and a specific traffic direction. The interface can be of any ifType supporting and running IP. | |
| INT cippfIfIpProfileDirection | 1.3.6.1.4.1.9.9.278.1.1.2.1.1 | INTEGER | not-accessible | This object determines whether this filter profile is applied to inbound or outbound traffic of a particular interface. The possible value(s) are: inbound - inbound traffic. outbound - outbound traffic. inboundIPv6 - IPv6 inbound traffic. outboundIPv6 - IPv6 outbound traffic. |
| CIP cippfIfIpProfileName | 1.3.6.1.4.1.9.9.278.1.1.2.1.2 | CippfIpFilterProfileName | read-create | This is the unique IP protocol filter profile identifier. This value must be the same as one of the existing cippfIpProfileName object values in the cippfIpProfileTable for this profile and the cippfIfIpProfileStatus of value 'createAndGo' to become 'active'. If this object value does not match any existing cippfIpProfileName, an entry of this table can only be created with cippfIfIpProfileStatus in 'createAndWait' state. The entry can only be made 'active' by the agent when the corresponding cippfIpProfileName is added to the cippfIpProfileTable. |
| ROW cippfIfIpProfileStatus | 1.3.6.1.4.1.9.9.278.1.1.2.1.3 | RowStatus | read-create | This object controls and reflects the status of rows in this table. To apply this filter profile or remove this filter profile, the NMS must do a multivarbind set containing both cippfIfIpProfileStatus and cippfIfIpProfileName. Creation of rows may be done via 'createAndGo' for profiles already exist in the cippfIpProfileTable, and the filter profile will only be effective when this object is set to 'active' by the agent. Creation of rows may also be done via 'createAndWait' for profiles do not exist in the cippfIpProfileTable. This object will be set by the agent to 'notReady', and the filter profile will not participate in IP filtering. This object will only be set to 'active' when there is a corresponding 'active' profile in the cippfIpProfileTable. To remove a row, set this object value to 'destroy'. |
| cippfIpFilterTable | 1.3.6.1.4.1.9.9.278.1.1.3 | not-accessible | This table contains ordered lists of filters for all the IP protocol filter profiles. Device traffic filtering system applies filters of a filter profile according to the filter order position. IP packets matching any filter will be processed according to the matching action specified by the filter or they will be discarded if they do not match any filters. Any IP packet through an interface can theoretically match multiple filters or rows of this table of the same filter profile. When applying a filter to a packet, the cippfIfIpProfileTable is used to first identify the filter profile to use, then this table is scanned according to filter profile name and filter order position. If the packet matches all criteria for that row, the action defined in the cippfIpFilterAction object of the row will be taken. If the action for the matching filter is deny(1), the packet is discarded and the processing is completed. If the action for the matching filter is permit(2), the packet is accepted and permitted to be processed by the bridging or routing logic. If the packet matches no filter in this table, the packet is always deny(1) and will be dropped. To create a filter, the cippfIpProfileName must already exists in the cippfIpProfileTable. No filter can be created without an existing filter in the cippfIpProfileTable. If the filter profile is deleted from the cippfIpProfileTable, all the associated filters in this table will also be deleted. | |
| cippfIpFilterEntry | 1.3.6.1.4.1.9.9.278.1.1.3.1 | not-accessible | Each entry is an IP Protocol traffic filter within an IP filter profile. Entries with the same cippfIpProfileName belong to the same IP filter profile. | |
| U32 cippfIpFilterIndex | 1.3.6.1.4.1.9.9.278.1.1.3.1.1 | Unsigned32 | not-accessible | This index uniquely identifies the IP protocol filters within this table and among all filter profiles. When a new filter is added and if this value is '0', the filter will be appended as the last entry for the corresponding profile in this table. For any set operation, the cippfIpFilterIndex value must match the index of an existing 'active' filter for the set operation to be successful. |
| U32 cippfIpFilterOrderPosition | 1.3.6.1.4.1.9.9.278.1.1.3.1.2 | Unsigned32 | read-create | This object is used to order the IP protocol filters within a filter profile. The filter with the lowest order position number is applied first, that is cippfIpFilterOrderPosition '1'. The order position number among all filters of a profile is always consecutive. The agent will automatically arrange the order position to a consecutive manner for the filter entries within the profile after each addition (when the created entry moves to 'active' state) and modification or deletion (when the active entry moves out from 'active' state) of any filter. For example, a new filter is added to an empty profile with the cippfIpFilterOrderPosition '2' , the filter will be actually positioned to cippfIpFilterOrderPosition '1' by the agent. Moreover, if there are 3 filters in the profile and their order positions are 1, 2, and 3. Adding a new filter with any cippfIpFilterOrderPosition greater than '3' will produce the same effect. The new filter will actually be in position '4' because the agent maintains the filters in consecutive order. When a filter is removed from a profile, the filters following this filter will be moved forward and decrement their order position numbers. For example, if there are 6 filters in the profile and their order positions are 1, 2, 3, 4, 5, 6. Deleting the filter of cippfIpFilterOrderPosition '4' will cause the existing filters of cippfIpFilterOrderPosition '5' and '6' to change to '4' and '5' respectively. When a filter is added to the order position of an existing filter of the same profile, the existing filter entry and all subsequent entries following it will increment their cippfIpFilterOrderPosition. This essentially move the existing filters towards the end of the filter profile. For example, if there are 6 filters in the profile, and their cippfIpFilterOrderPosition values are 1, 2, 3, 4, 5, 6. If the user would like to add a new one and specifies '4' to be the cippfIpFilterOrderPosition of the new filter, the existing filters of cippfIpFilterOrderPosition values 4, 5, 6 will become 5, 6, 7. The cippfIpFilterOrderPosition value '0' is a special number meaning to append the filter to the last filter of the profile. Continue with our previous example, if another new filter is added and the user specifies the cippfIpFilterOrderPosition to be '0'. The new filter will actually be created with cippfIpFilterOrderPosition equal to 8. Finally, moving a filter within a profile will have the same effect of first deleting and then adding the filter to the new position. For example, if the filter of cippfIpFilterOrderPosition 2 is moved to 4, the filters originally at the cippfIpFilterOrderPosition 3 and 4 will be moved forward to 2 and 3 respectively and filters of all other cippfIpFilterOrderPosition values will remain unchanged. |
| INT cippfIpFilterAction | 1.3.6.1.4.1.9.9.278.1.1.3.1.3 | INTEGER | read-create | If it is set to deny(1), all packets matching this filter will be discarded and scanning of the remainder of the filter list will be aborted. If it is set to permit(2), all packets matching this filter will be allowed for further bridging or routing processing. |
| IPt cippfIpFilterAddressType | 1.3.6.1.4.1.9.9.278.1.1.3.1.4 | InetAddressType | read-create | This is the IP address type of for the cippfIpFilterSrcAddress, cippfIpFilterSrcMask, cippfIpFilterDestAddress, and cippfIpFilterDestMask. |
| IP cippfIpFilterSrcAddress | 1.3.6.1.4.1.9.9.278.1.1.3.1.5 | InetAddress | read-create | The source IP address to be matched for this filter. A value of zero causes all source address to match. The object value has to be consistent with the type specified in cippfIpFilterAddressType. |
| IP cippfIpFilterSrcMask | 1.3.6.1.4.1.9.9.278.1.1.3.1.6 | InetAddress | read-create | This is the wildcard mask for the cippfIpFilterSrcAddress bits that must match. 0 bits in the mask indicate the corresponding bits in the cippfIpFilterSrcAddress must match in order for the matching to be successful, and 1 bits are don't care bits in the matching. A value of zero causes only IP packets of source address the same as cippfIpFilterSrcAddress to match. This object value has to be consistent with the type specified in cippfIpFilterAddressType. |
| IP cippfIpFilterDestAddress | 1.3.6.1.4.1.9.9.278.1.1.3.1.7 | InetAddress | read-create | The destination IP address to be matched for this filter. A value of zero causes all source address to match. The object value has to be consistent with the type specified in cippfIpFilterAddressType. |
| IP cippfIpFilterDestMask | 1.3.6.1.4.1.9.9.278.1.1.3.1.8 | InetAddress | read-create | This is the wildcard mask for the cippfIpFilterDestAddress bits that must match. 0 bits in the mask indicate the corresponding bits in the cippfIpFilterDestAddress must match in order for the matching to be successful, and 1 bits are don't care bits in the matching. A value of zero causes only IP packets of source address the same as cippfIpFilterSrcAddress to match. This object value has to be consistent with the type specified in cippfIpFilterAddressType. |
| I32 cippfIpFilterProtocol | 1.3.6.1.4.1.9.9.278.1.1.3.1.9 | Integer32 | read-create | This filter protocol object matches the Internet Protocol Number in the packets. These IP numbers are defined in the Network Working Group Request for Comments (RFC) documents. For example, Cisco commonly used protocol includes: 1 - Internet Control Message Protocol 2 - Internet Gateway Message Protocol 4 - IP in IP tunneling 6 - Transmission Control Protocol 9 - Cisco's IGRP routing protocol 17 - User Datagram Protocol 47 - Cisco's GRE tunneling 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 Setting this object to '-1' will make the filtering match any IP number. |
| INE cippfIpFilterSrcPortLow | 1.3.6.1.4.1.9.9.278.1.1.3.1.10 | InetPortNumber | read-create | If cippfIpFilterProtocol is udp or tcp, this is the inclusive lower bound of the transport-layer source port range that is to be matched, otherwise it is ignored during matching. This value must be equal to or less than the value specified for this entry in cippfIpFilterSrcPortHigh. |
| INE cippfIpFilterSrcPortHigh | 1.3.6.1.4.1.9.9.278.1.1.3.1.11 | InetPortNumber | read-create | If cippfIpFilterProtocol is udp or tcp, this is the inclusive upper bound of the transport-layer source port range that is to be matched, otherwise it is ignored during matching. This value must be equal to or greater than the value specified for this entry in cippfIpFilterSrcPortLow. If this value is '0', the udp or tcp port number is ignored during matching. |
| INE cippfIpFilterDestPortLow | 1.3.6.1.4.1.9.9.278.1.1.3.1.12 | InetPortNumber | read-create | If cippfIpFilterProtocol is udp or tcp, this is the inclusive lower bound of the transport-layer destination port range that is to be matched, otherwise it is ignored during matching. This value must be equal to or less than the value specified for this entry in cippfIpFilterDestPortHigh. |
| INE cippfIpFilterDestPortHigh | 1.3.6.1.4.1.9.9.278.1.1.3.1.13 | InetPortNumber | read-create | If cippfIpFilterProtocol is udp or tcp, this is the inclusive upper bound of the transport-layer destination port range that is to be matched, otherwise it is ignored during matching. This value must be equal to or greater than the value specified for this entry in cippfIpFilterDestPortLow. If this value is '0', the udp or tcp port number is ignored during matching. |
| INT cippfIpFilterPrecedence | 1.3.6.1.4.1.9.9.278.1.1.3.1.14 | INTEGER | read-create | The IP traffic precedence parameters in each packet are used to guide the selection of the actual service parameters when transmitting a datagram through a particular network. Most network treats high precedence traffic as more important than other traffic. The IP Precedence value ranges from '0' to '7', with '7' the highest precedence and '0' the lowest precedence. This object sets criteria for matching the IP packet precedence parameter. The object value '-1' means to match packets of any IP precedence. In other words, the IP precedence parameter will not to checked if this object is '-1'. The precedence level are: routine(0) - Routine traffic precedence priority(1) - Priority traffic precedence immediate(2) - Immediate traffic precedence flash(3) - Flash traffic precedence flashOverride(4) - Flash-override traffic precedence critical(5) - Critical precedence internet(6) - Internetwork control traffic precedence network(7) - Network control traffic precedence. |
| I32 cippfIpFilterTos | 1.3.6.1.4.1.9.9.278.1.1.3.1.15 | Integer32 | read-create | This is the value to match to the Type of Service (TOS) of the packet. The TOS values ranges from '0' to '15'. The value '-1' matches any TOS value. |
| T/F cippfIpFilterLogEnabled | 1.3.6.1.4.1.9.9.278.1.1.3.1.16 | TruthValue | read-create | This object specifies whether filtered packets will be logged by the filtering subsystem or not. If it is true(1), then all packets will be logged. If it is false(2), then no packet will be logged. |
| ROW cippfIpFilterStatus | 1.3.6.1.4.1.9.9.278.1.1.3.1.17 | RowStatus | read-create | This object controls and reflects the status of rows in this table. Creation of rows must be done via 'createAndGo' and this object will become 'active' if the NMS performs a multivarbind set containing this object and the cippfIpFilterOrderPosition. The default matching action of a new filter is deny(1). Any object in a row can be modified any time when the row is in the 'active' state. Removal of a row can be done via setting this object to 'destroy'. |
| I32 cippfIpFilterICMPType | 1.3.6.1.4.1.9.9.278.1.1.3.1.18 | Integer32 | read-create | This filter specifies the ICMP message type to be matched. Setting this object to '-1' will make the filtering match any ICMP message type. |
| T/F cippfIpFilterTCPEstablished | 1.3.6.1.4.1.9.9.278.1.1.3.1.19 | TruthValue | read-create | This filter if 'true' specifies that for TCP protocol, in an established connection, a match occurs if the TCP datagram has the ACK,FIN,PSH,RST,SYN or URG control bits set. If 'false' a match will occur for any TCP datagram. |
| T/F cippfIpFilterFragments | 1.3.6.1.4.1.9.9.278.1.1.3.1.20 | TruthValue | read-create | If 'true', this filter applies only to the second and further fragments of fragmented packets. If 'false', the filter will only match head fragments or unfragmented packets. Note: Second and subsequent fragments do not contain source or destination ports info, therefore cannot be filtered on that basis. |
| I32 cippfIpFilterICMPCode | 1.3.6.1.4.1.9.9.278.1.1.3.1.21 | Integer32 | read-create | This filter specifies the ICMP message code to be matched. Setting this object to '-1' will make the filtering match any ICMP code. |
| CFG cippfIpFilterSrcIPGroupName | 1.3.6.1.4.1.9.9.278.1.1.3.1.22 | CfgFilterGroupName | read-create | This object identifies the filter group containing information about source IP addresses and masks that need to be matched for this filter. This value must match an entry in cfgFilterGroupTable whose cfgFilterGroupType value is set to 'network' and must match an entry in cfgFilterNetworkGroupTable. This object cannot be set if any of the following objects are set: cippfIpFilterSrcAddress cippfIpFilterSrcMask. This object is not instantiated if not applicable. |
| CFG cippfIpFilterDstIPGroupName | 1.3.6.1.4.1.9.9.278.1.1.3.1.23 | CfgFilterGroupName | read-create | This object identifies the filter group containing information about destination IP addresses and masks that need to be matched for this filter. This value must match an entry in cfgFilterGroupTable whose cfgFilterGroupType value is set to 'network' and must match an entry in cfgFilterNetworkGroupTable. This object cannot be set if any of the following objects are set: cippfIpFilterDestAddress cippfIpFilterDestMask. This object is not instantiated if not applicable. |
| CFG cippfIpFilterProtocolGroupName | 1.3.6.1.4.1.9.9.278.1.1.3.1.24 | CfgFilterGroupName | read-create | This object identifies the filter group containing information about internet protocol numbers. This value must match an entry in cfgFilterGroupTable whose cfgFilterGroupType value is set to 'service' and must match an entry in cfgFilterServiceGroupTable. This object cannot be set if any of the following objects are set: cippfIpFilterProtocol. This object is not instantiated if not applicable. |
| CFG cippfIpFilterSrcServiceGroupName | 1.3.6.1.4.1.9.9.278.1.1.3.1.25 | CfgFilterGroupName | read-create | This object identifies the filter group containing information about port(TCP/UDP) numbers. This value must match an entry in cfgFilterGroupTable whose cfgFilterGroupType value is set to 'service' and must match an entry in cfgFilterServiceGroupTable. This object cannot be set if any of the following objects are set: cippfIpFilterSrcPortLow cippfIpFilterSrcPortHigh This object is not instantiated if not applicable. |
| CFG cippfIpFilterDstServiceGroupName | 1.3.6.1.4.1.9.9.278.1.1.3.1.26 | CfgFilterGroupName | read-create | This object identifies the filter group containing information about port(TCP/UDP) numbers. This value must match an entry in cfgFilterGroupTable whose cfgFilterGroupType value is set to 'service' and must match an entry in cfgFilterServiceGroupTable. This object cannot be set if any of the following objects are set: cippfIpFilterDestPortLow cippfIpFilterDestPortHigh This object is not instantiated if not applicable. |
| CFG cippfIpFilterICMPGroupName | 1.3.6.1.4.1.9.9.278.1.1.3.1.27 | CfgFilterGroupName | read-create | This object identifies the filter group containing information about ICMP message. This value must match an entry in cfgFilterGroupTable whose cfgFilterGroupType value is set to 'icmp' and must match an entry in cfgFilterICMPGroupTable. This object cannot be set if any of the following objects are set: cippfIpFilterICMPType cippfIpFilterICMPCode. This object is not instantiated if not applicable. |
| cippfIpFilterExtTable | 1.3.6.1.4.1.9.9.278.1.1.4 | not-accessible | This table is an extension to cippfIpFilterTable. This table is used for configuring the objects that are used for reporting the information about filters and reporting the logs. These objects do not change the match criteria for the filter but assist in troubleshooting the matched criteria. | |
| cippfIpFilterExtEntry | 1.3.6.1.4.1.9.9.278.1.1.4.1 | not-accessible | An entry in filter extension table. Each entry contains information on the description of the filter and logging related objects. | |
| STR cippfIpFilterExtDescription | 1.3.6.1.4.1.9.9.278.1.1.4.1.1 | SnmpAdminString | read-create | This object is used for configuring description of the filter. |
| SYS cippfIpFilterExtLogLevel | 1.3.6.1.4.1.9.9.278.1.1.4.1.2 | SyslogSeverity | read-create | This object is used for specifying the log level (severity) used in syslog for this filter. |
| U32 cippfIpFilterExtLogInterval | 1.3.6.1.4.1.9.9.278.1.1.4.1.3 | Unsigned32 | read-create | This object is used for configuring the time interval at which the syslog message for this filter to be generated. |
| cippfIpFilterStats | 1.3.6.1.4.1.9.9.278.1.2 | |||
| cippfIpFilterStatsTable | 1.3.6.1.4.1.9.9.278.1.2.1 | not-accessible | This table defines a set of statistics related to packet filter. The statistics related to matched filters are available here. | |
| cippfIpFilterStatsEntry | 1.3.6.1.4.1.9.9.278.1.2.1.1 | not-accessible | An entry in IP Filter stats table. An entry exists in this table for every entry in cippfIpFilterTable. | |
| C64 cippfIpFilterHitsEx | 1.3.6.1.4.1.9.9.278.1.2.1.1.1 | Counter64 | read-only | This object specifies the number of packets that are matched the packet filter configuration in cippfIpFilterTable. |
| ciscoIpProtocolFilterMIBConform | 1.3.6.1.4.1.9.9.278.2 | |||
| ciscoIpProtocolFilterMIBCompl | 1.3.6.1.4.1.9.9.278.2.1 | |||
| ciscoIpProtocolMIBCompliance | 1.3.6.1.4.1.9.9.278.2.1.1 | The compliance statement for entities implementing the Cisco IP Protocol Filter MIB. OBJECT cippfIpFilterAddressType SYNTAX InetAddressType { ipv4(1) } DESCRIPTION An implementation is only required to support IPv4 addresses. OBJECT cippfIpFilterSrcAddress SYNTAX InetAddress (SIZE(4)) DESCRIPTION An implementation is only required to support IPv4 addresses. OBJECT cippfIpFilterDestAddress SYNTAX InetAddress (SIZE(4)) DESCRIPTION An implementation is only required to support IPv4 addresses. | ||
| ciscoIpProtocolMIBComplianceRev1 | 1.3.6.1.4.1.9.9.278.2.1.2 | The compliance statement for entities implementing the Cisco IP Protocol Filter MIB. OBJECT cippfIpFilterAddressType SYNTAX InetAddressType { ipv4(1) } DESCRIPTION An implementation is only required to support IPv4 addresses. OBJECT cippfIpFilterSrcAddress SYNTAX InetAddress (SIZE(4)) DESCRIPTION An implementation is only required to support IPv4 addresses. OBJECT cippfIpFilterDestAddress SYNTAX InetAddress (SIZE(4)) DESCRIPTION An implementation is only required to support IPv4 addresses. OBJECT cippfIpFilterOrderPosition MIN-ACCESS read-only DESCRIPTION Write access is not required. OBJECT cippfIpProfileType MIN-ACCESS read-only DESCRIPTION Write access is not required. | ||
| ciscoIpProtocolMIBComplianceRev2 | 1.3.6.1.4.1.9.9.278.2.1.3 | The compliance statement for entities implementing the Cisco IP Protocol Filter MIB. | ||
| ciscoIpProtocolFilterMIBGroups | 1.3.6.1.4.1.9.9.278.2.2 | |||
| ciscoIpProtocolFilteringGroup | 1.3.6.1.4.1.9.9.278.2.2.1 | Configuration parameters for IP Protocol filters. | ||
| ciscoIpProtocolFilterGroup2 | 1.3.6.1.4.1.9.9.278.2.2.2 | Configuration parameters for IP Protocol filters. | ||
| ciscoIpProtocolFilterExtGroup | 1.3.6.1.4.1.9.9.278.2.2.4 | Configuration parameters for logging packet filters. | ||
| ciscoIpProtocolFilterObjectGroup | 1.3.6.1.4.1.9.9.278.2.2.5 | Configuration parameters for filter groups in a protocol filter. | ||
| ciscoIpProtocolFilterStatsGroup | 1.3.6.1.4.1.9.9.278.2.2.6 | This is a group containing objects related to packet filter. |
RFC description
Configures IP protocol packet filtering profiles and applies them to device interfaces.
Start monitoring Cisco routers and switches (IP protocol filtering) 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.