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.
Parsed from file CISCO-IP-PROTOCOL-FILTER-MIB.mib
Module: CISCO-IP-PROTOCOL-FILTER-MIB
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.
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.
Parsed from file CISCO-IP-PROTOCOL-FILTER-MIB.my.txt
Company: None
Module: CISCO-IP-PROTOCOL-FILTER-MIB
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.
cippfIpFilterTable OBJECT-TYPE SYNTAX SEQUENCE OF CippfIpFilterEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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." ::= { cippfIpFilterConfig 3 }
cippfIpFilterTable OBJECT-TYPE SYNTAX SEQUENCE OF CippfIpFilterEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "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." ::= { cippfIpFilterConfig 3 }
Vendor: Cisco
Module: CISCO-IP-PROTOCOL-FILTER-MIB
[Automatically extracted from oidview.com]
cippfIpFilterTable OBJECT-TYPE SYNTAX SEQUENCE OF CippfIpFilterEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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." ::= { cippfIpFilterConfig 3 }
cippfIpFilterTable OBJECT-TYPE SYNTAX SEQUENCE OF CippfIpFilterEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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." ::= { cippfIpFilterConfig 3 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.278.1.1.3.1 | cippfIpFilterEntry | 27 | 27 | Each entry is an IP Protocol traffic filter within an IP filter profile. Entries with the same cippfIpProfileName belong to the … |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.278.1.1.1 | cippfIpProfileTable | 1 | 5 | This table lists all the existing IP protocol filter profiles. These filter profiles contain protocol filters used to filter IP … |
| 1.3.6.1.4.1.9.9.278.1.1.2 | cippfIfIpProfileTable | 1 | 4 | This table lists all the IP protocol filter profiles being applied to IP traffic on the device interfaces. An IP protocol filter… |
| 1.3.6.1.4.1.9.9.278.1.1.4 | cippfIpFilterExtTable | 1 | 4 | This table is an extension to cippfIpFilterTable. This table is used for configuring the objects that are used for reporting the … |