Reference record for OID 1.3.6.1.4.1.9.9.519.1.1.1



parent
1.3.6.1.4.1.9.9.519.1.1 (ciscoLwappIdsConfig)
node code
1
node name
cLIdsIpsSensorConfigTable
dot oid
1.3.6.1.4.1.9.9.519.1.1.1
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappIdsMIB(519) ciscoLwappIdsMIBObjects(1) ciscoLwappIdsConfig(1) cLIdsIpsSensorConfigTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoLwappIdsMIB(519) ciscoLwappIdsMIBObjects(1) ciscoLwappIdsConfig(1) cLIdsIpsSensorConfigTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappIdsMIB(519) ciscoLwappIdsMIBObjects(1) ciscoLwappIdsConfig(1) cLIdsIpsSensorConfigTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoLwappIdsMIB(519) ciscoLwappIdsMIBObjects(1) ciscoLwappIdsConfig(1) cLIdsIpsSensorConfigTable(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappIdsMIB(519) ciscoLwappIdsMIBObjects(1) ciscoLwappIdsConfig(1) cLIdsIpsSensorConfigTable(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoLwappIdsMIB(519) ciscoLwappIdsMIBObjects(1) ciscoLwappIdsConfig(1) cLIdsIpsSensorConfigTable(1)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoLwappIdsMIB/ciscoLwappIdsMIBObjects/ciscoLwappIdsConfig/cLIdsIpsSensorConfigTable
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoLwappIdsMIB/ciscoLwappIdsMIBObjects/ciscoLwappIdsConfig/cLIdsIpsSensorConfigTable
  • /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoLwappIdsMIB/ciscoLwappIdsMIBObjects/ciscoLwappIdsConfig/cLIdsIpsSensorConfigTable
  • /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoLwappIdsMIB/ciscoLwappIdsMIBObjects/ciscoLwappIdsConfig/cLIdsIpsSensorConfigTable
  • /iso/iso-identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoLwappIdsMIB/ciscoLwappIdsMIBObjects/ciscoLwappIdsConfig/cLIdsIpsSensorConfigTable
  • /iso/iso-identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoLwappIdsMIB/ciscoLwappIdsMIBObjects/ciscoLwappIdsConfig/cLIdsIpsSensorConfigTable
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/9/9/519/1/1/1

    Description by circitor

    This table facilitates the configuration of a group
    of IPS sensors to which the LWAPP controller would
    subscribe to retrieve the IDS events from the
    respective sensors.

    IPS sensors are used to protect the network by helping
    to detect and report threats like worms, viruses etc.
    By subscribing to such a sensor, the LWAPP controller,
    through appropriate interfaces, can retrieve the
    events detected by the sensor and report the same
    to the NMS. The controller can accept the request, to
    block the packets from an IP address, from each Sensor
    configured through this table and block the data
    traffic originating from that particular source.

    Rows are added or deleted to the table by explicit
    management actions initiated by the user from a
    network management station. Information about each
    IPS sensor is uniquely identified by the network
    address of the respective sensor.

    Parsed from file CISCO-LWAPP-IDS-MIB.mib
    Module: CISCO-LWAPP-IDS-MIB

    Description by cisco_v1

    This table facilitates the configuration of a group
    of IPS sensors to which the LWAPP controller would
    subscribe to retrieve the IDS events from the
    respective sensors.

    IPS sensors are used to protect the network by helping
    to detect and report threats like worms, viruses etc.
    By subscribing to such a sensor, the LWAPP controller,
    through appropriate interfaces, can retrieve the
    events detected by the sensor and report the same
    to the NMS. The controller can accept the request, to
    block the packets from an IP address, from each Sensor
    configured through this table and block the data
    traffic originating from that particular source.

    Rows are added or deleted to the table by explicit
    management actions initiated by the user from a
    network management station. Information about each
    IPS sensor is uniquely identified by the network
    address of the respective sensor.

    Description by mibdepot

    This table facilitates the configuration of a group
    of IPS sensors to which the LWAPP controller would
    subscribe to retrieve the IDS events from the
    respective sensors.

    IPS sensors are used to protect the network by helping
    to detect and report threats like worms, viruses etc.
    By subscribing to such a sensor, the LWAPP controller,
    through appropriate interfaces, can retrieve the
    events detected by the sensor and report the same
    to the NMS. The controller can accept the request, to
    block the packets from an IP address, from each Sensor
    configured through this table and block the data
    traffic originating from that particular source.

    Rows are added or deleted to the table by explicit
    management actions initiated by the user from a
    network management station. Information about each
    IPS sensor is uniquely identified by the network
    address of the respective sensor.

    Parsed from file CISCO-LWAPP-IDS-MIB.my.txt
    Company: None
    Module: CISCO-LWAPP-IDS-MIB

    Description by cisco

    This table facilitates the configuration of a group
    of IPS sensors to which the LWAPP controller would
    subscribe to retrieve the IDS events from the
    respective sensors.

    IPS sensors are used to protect the network by helping
    to detect and report threats like worms, viruses etc.
    By subscribing to such a sensor, the LWAPP controller,
    through appropriate interfaces, can retrieve the
    events detected by the sensor and report the same
    to the NMS. The controller can accept the request, to
    block the packets from an IP address, from each Sensor
    configured through this table and block the data
    traffic originating from that particular source.

    Rows are added or deleted to the table by explicit
    management actions initiated by the user from a
    network management station. Information about each
    IPS sensor is uniquely identified by the network
    address of the respective sensor.

    Information by circitor

    cLIdsIpsSensorConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF CLIdsIpsSensorConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table facilitates the configuration of a group of IPS sensors to which the LWAPP controller would subscribe to retrieve the IDS events from the respective sensors. IPS sensors are used to protect the network by helping to detect and report threats like worms, viruses etc. By subscribing to such a sensor, the LWAPP controller, through appropriate interfaces, can retrieve the events detected by the sensor and report the same to the NMS. The controller can accept the request, to block the packets from an IP address, from each Sensor configured through this table and block the data traffic originating from that particular source. Rows are added or deleted to the table by explicit management actions initiated by the user from a network management station. Information about each IPS sensor is uniquely identified by the network address of the respective sensor. " ::= { ciscoLwappIdsConfig 1 }

    Information by cisco_v1

    cLIdsIpsSensorConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF CLIdsIpsSensorConfigEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This table facilitates the configuration of a group of IPS sensors to which the LWAPP controller would subscribe to retrieve the IDS events from the respective sensors. IPS sensors are used to protect the network by helping to detect and report threats like worms, viruses etc. By subscribing to such a sensor, the LWAPP controller, through appropriate interfaces, can retrieve the events detected by the sensor and report the same to the NMS. The controller can accept the request, to block the packets from an IP address, from each Sensor configured through this table and block the data traffic originating from that particular source. Rows are added or deleted to the table by explicit management actions initiated by the user from a network management station. Information about each IPS sensor is uniquely identified by the network address of the respective sensor. " ::= { ciscoLwappIdsConfig 1 }

    Information by oid_info

    Vendor: Cisco
    Module: CISCO-LWAPP-IDS-MIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    cLIdsIpsSensorConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF CLIdsIpsSensorConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table facilitates the configuration of a group of IPS sensors to which the LWAPP controller would subscribe to retrieve the IDS events from the respective sensors. IPS sensors are used to protect the network by helping to detect and report threats like worms, viruses etc. By subscribing to such a sensor, the LWAPP controller, through appropriate interfaces, can retrieve the events detected by the sensor and report the same to the NMS. The controller can accept the request, to block the packets from an IP address, from each Sensor configured through this table and block the data traffic originating from that particular source. Rows are added or deleted to the table by explicit management actions initiated by the user from a network management station. Information about each IPS sensor is uniquely identified by the network address of the respective sensor. " ::= { ciscoLwappIdsConfig 1 }

    Information by cisco

    cLIdsIpsSensorConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF CLIdsIpsSensorConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table facilitates the configuration of a group of IPS sensors to which the LWAPP controller would subscribe to retrieve the IDS events from the respective sensors. IPS sensors are used to protect the network by helping to detect and report threats like worms, viruses etc. By subscribing to such a sensor, the LWAPP controller, through appropriate interfaces, can retrieve the events detected by the sensor and report the same to the NMS. The controller can accept the request, to block the packets from an IP address, from each Sensor configured through this table and block the data traffic originating from that particular source. Rows are added or deleted to the table by explicit management actions initiated by the user from a network management station. Information about each IPS sensor is uniquely identified by the network address of the respective sensor. " ::= { ciscoLwappIdsConfig 1 }

    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)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.9.9.519.1.1.1.1 cLIdsIpsSensorConfigEntry 9 9 There is an entry in this table for each IPS sensor
    identified by cLIdsIpsSensorAddressType and
    cLIdsIpsSensorAddress from which …