Reference record for OID 1.3.6.1.4.1.9.9.278.1.1.2

parent

1.3.6.1.4.1.9.9.278.1.1 (cippfIpFilterConfig)

node code

2

node name

cippfIfIpProfileTable

dot oid

1.3.6.1.4.1.9.9.278.1.1.2

type

OBJECT-TYPE

asn1 oid

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoIpProtocolMIB(278) ciscoIpProtocolFilterMIBObjects(1) cippfIpFilterConfig(1) cippfIfIpProfileTable(2)}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoIpProtocolMIB(278) ciscoIpProtocolFilterMIBObjects(1) cippfIpFilterConfig(1) cippfIfIpProfileTable(2)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoIpProtocolMIB(278) ciscoIpProtocolFilterMIBObjects(1) cippfIpFilterConfig(1) cippfIfIpProfileTable(2)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoIpProtocolMIB(278) ciscoIpProtocolFilterMIBObjects(1) cippfIpFilterConfig(1) cippfIfIpProfileTable(2)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoIpProtocolMIB(278) ciscoIpProtocolFilterMIBObjects(1) cippfIpFilterConfig(1) cippfIfIpProfileTable(2)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoIpProtocolMIB(278) ciscoIpProtocolFilterMIBObjects(1) cippfIpFilterConfig(1) cippfIfIpProfileTable(2)}

iri oid

/iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoIpProtocolMIB/ciscoIpProtocolFilterMIBObjects/cippfIpFilterConfig/cippfIfIpProfileTable

/iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoIpProtocolMIB/ciscoIpProtocolFilterMIBObjects/cippfIpFilterConfig/cippfIfIpProfileTable

/iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoIpProtocolMIB/ciscoIpProtocolFilterMIBObjects/cippfIpFilterConfig/cippfIfIpProfileTable

/iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoIpProtocolMIB/ciscoIpProtocolFilterMIBObjects/cippfIpFilterConfig/cippfIfIpProfileTable

/iso/iso-identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoIpProtocolMIB/ciscoIpProtocolFilterMIBObjects/cippfIpFilterConfig/cippfIfIpProfileTable

/iso/iso-identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoIpProtocolMIB/ciscoIpProtocolFilterMIBObjects/cippfIpFilterConfig/cippfIfIpProfileTable

iri by oid_info

/ISO/Identified-Organization/6/1/4/1/9/9/278/1/1/2

Description by circitor

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.

Parsed from file CISCO-IP-PROTOCOL-FILTER-MIB.mib
Module: CISCO-IP-PROTOCOL-FILTER-MIB

Description by cisco_v1

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.

Description by mibdepot

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.

Parsed from file CISCO-IP-PROTOCOL-FILTER-MIB.my.txt
Company: None
Module: CISCO-IP-PROTOCOL-FILTER-MIB

Description by cisco

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.

Information by circitor

cippfIfIpProfileTable OBJECT-TYPE
        SYNTAX     SEQUENCE OF CippfIfIpProfileEntry
        MAX-ACCESS not-accessible
        STATUS     current
        DESCRIPTION
                "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."
        ::= { cippfIpFilterConfig 2 }

Information by cisco_v1

cippfIfIpProfileTable OBJECT-TYPE
    SYNTAX SEQUENCE OF CippfIfIpProfileEntry
    ACCESS not-accessible
    STATUS mandatory
    DESCRIPTION
        "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."
    ::= { cippfIpFilterConfig 2 }

Information by oid_info

Vendor: Cisco
Module: CISCO-IP-PROTOCOL-FILTER-MIB

[Automatically extracted from oidview.com]

Information by mibdepot

cippfIfIpProfileTable OBJECT-TYPE
        SYNTAX     SEQUENCE OF CippfIfIpProfileEntry
        MAX-ACCESS not-accessible
        STATUS     current
        DESCRIPTION
                "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."
        ::= { cippfIpFilterConfig 2 }

Information by cisco

cippfIfIpProfileTable OBJECT-TYPE
        SYNTAX     SEQUENCE OF CippfIfIpProfileEntry
        MAX-ACCESS not-accessible
        STATUS     current
        DESCRIPTION
                "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."
        ::= { cippfIpFilterConfig 2 }

First Registration Authority (recovered by parent 1.3.6.1.4.1.9)

Greg Satz

Current Registration Authority (recovered by parent 1.3.6.1.4.1.9)

Cisco Systems, Inc.

Children (1)

Brothers (3)