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
- Numeric OID
- 1.3.6.1.4.1.9.9.519.1.1.1
- URN notation
- urn:oid:1.3.6.1.4.1.9.9.519.1.1.1
- Type
- OBJECT-TYPE
- ASN.1 notation
-
{1 3 6 1 4 1 9 9 519 1 1 1}
- {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) enterprise(1) me1200(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) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoMgmt(9) ciscoLwappIdsMIB(519) ciscoLwappIdsMIBObjects(1) ciscoLwappIdsConfig(1) cLIdsIpsSensorConfigTable(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-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) ldap-enterprise(1) me1200(9) ciscoMgmt(9) ciscoLwappIdsMIB(519) ciscoLwappIdsMIBObjects(1) ciscoLwappIdsConfig(1) cLIdsIpsSensorConfigTable(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoLwappIdsMIB(519) ciscoLwappIdsMIBObjects(1) ciscoLwappIdsConfig(1) cLIdsIpsSensorConfigTable(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) me1200(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) enterprise(1) me1200(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) org(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoMgmt(9) ciscoLwappIdsMIB(519) ciscoLwappIdsMIBObjects(1) ciscoLwappIdsConfig(1) cLIdsIpsSensorConfigTable(1)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoLwappIdsMIB(519) ciscoLwappIdsMIBObjects(1) ciscoLwappIdsConfig(1) cLIdsIpsSensorConfigTable(1)}
- {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) me1200(9) ciscoMgmt(9) ciscoLwappIdsMIB(519) ciscoLwappIdsMIBObjects(1) ciscoLwappIdsConfig(1) cLIdsIpsSensorConfigTable(1)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoLwappIdsMIB(519) ciscoLwappIdsMIBObjects(1) ciscoLwappIdsConfig(1) cLIdsIpsSensorConfigTable(1)}
- {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) me1200(9) ciscoMgmt(9) ciscoLwappIdsMIB(519) ciscoLwappIdsMIBObjects(1) ciscoLwappIdsConfig(1) cLIdsIpsSensorConfigTable(1)}
- Additional combinations skipped.
- OID-IRI notation
- /1/3/6/1/4/1/9/9/519/1/1/1
- /ISO/Identified-Organization/6/1/4/1/9/9/519/1/1/1
- /ISO/3/6/1/4/1/9/9/519/1/1/1
- Named path variants
- /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoLwappIdsMIB/ciscoLwappIdsMIBObjects/ciscoLwappIdsConfig/cLIdsIpsSensorConfigTable
- /iso/identified-organization/dod/internet/private/enterprise/me1200/ciscoMgmt/ciscoLwappIdsMIB/ciscoLwappIdsMIBObjects/ciscoLwappIdsConfig/cLIdsIpsSensorConfigTable
- /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/identified-organization/dod/internet/private/enterprises/me1200/ciscoMgmt/ciscoLwappIdsMIB/ciscoLwappIdsMIBObjects/ciscoLwappIdsConfig/cLIdsIpsSensorConfigTable
- /iso/identified-organization/dod/internet/private/enterprises/Cisco/ciscoMgmt/ciscoLwappIdsMIB/ciscoLwappIdsMIBObjects/ciscoLwappIdsConfig/cLIdsIpsSensorConfigTable
- /iso/identified-organization/dod/internet/private/ldap-enterprise/cisco/ciscoMgmt/ciscoLwappIdsMIB/ciscoLwappIdsMIBObjects/ciscoLwappIdsConfig/cLIdsIpsSensorConfigTable
- /iso/identified-organization/dod/internet/private/ldap-enterprise/me1200/ciscoMgmt/ciscoLwappIdsMIB/ciscoLwappIdsMIBObjects/ciscoLwappIdsConfig/cLIdsIpsSensorConfigTable
- /iso/identified-organization/dod/internet/private/ldap-enterprise/Cisco/ciscoMgmt/ciscoLwappIdsMIB/ciscoLwappIdsMIBObjects/ciscoLwappIdsConfig/cLIdsIpsSensorConfigTable
- /iso/identified-organization/dod/internet/private/vendor-objects/cisco/ciscoMgmt/ciscoLwappIdsMIB/ciscoLwappIdsMIBObjects/ciscoLwappIdsConfig/cLIdsIpsSensorConfigTable
- /iso/identified-organization/dod/internet/private/vendor-objects/me1200/ciscoMgmt/ciscoLwappIdsMIB/ciscoLwappIdsMIBObjects/ciscoLwappIdsConfig/cLIdsIpsSensorConfigTable
- /iso/identified-organization/dod/internet/private/vendor-objects/Cisco/ciscoMgmt/ciscoLwappIdsMIB/ciscoLwappIdsMIBObjects/ciscoLwappIdsConfig/cLIdsIpsSensorConfigTable
- /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoLwappIdsMIB/ciscoLwappIdsMIBObjects/ciscoLwappIdsConfig/cLIdsIpsSensorConfigTable
- /iso/org/dod/internet/private/enterprise/me1200/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
- Additional combinations skipped.
Descriptions
Descriptions may differ between sources. The primary description is shown first.
Primary description: 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
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
Source file: Download CISCO-LWAPP-IDS-MIB.mib
Publisher path: Mibs; 24,707 bytes
Alternative description: 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.
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.
Source file: Download CISCO-LWAPP-IDS-MIB.my · Publisher's file
Copy from Netdisco; File: cisco/CISCO-LWAPP-IDS-MIB.my; 24,129 bytes
Vendor MIB copy from the Netdisco archive.
Related source files and packages:
- Netdisco archive revision metadata (not a manufacturer release date)File: repos/netdisco/netdisco-mibs/commits/master; 15,422 bytes
- Netdisco MIB distribution at the selected archive revision38.9 MiB
Source file: Download CISCO-LWAPP-IDS-MIB · Publisher's file
Copy from Observium Community; File: cisco/CISCO-LWAPP-IDS-MIB; 24,129 bytes
Vendor MIB copy from the Observium Community archive. Cisco support.
Related source files and packages:
- Observium Community original distribution archivePublisher Last-Modified: Tue, 05 May 2026 13:47:48 GMT; 127.4 MiB
Source file: Download CISCO-LWAPP-IDS-MIB.my · Publisher's file
Publisher path: cisco/cisco-mibs/main/v2/CISCO-LWAPP-IDS-MIB.my; 24,129 bytes
Alternative description: Cisco SMIv1
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.
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.
Source file: Download CISCO-LWAPP-IDS-MIB-V1SMI.my · Publisher's file
Publisher path: cisco/cisco-mibs/main/v1/CISCO-LWAPP-IDS-MIB-V1SMI.my; 20,673 bytes
Source file: Download CISCO-LWAPP-IDS-MIB-V1SMI.my.txt
File: cisco/CISCO-LWAPP-IDS-MIB-V1SMI.my.txt; 21,250 bytes
Alternative description: 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.
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.
Source file: Download CISCO-LWAPP-IDS-MIB.my.txt
File: cisco/CISCO-LWAPP-IDS-MIB.my.txt; 24,707 bytes
Information from 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 from Cisco SMIv1
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 from OID Repository
Information from 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 from 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 (inferred from ancestor 1.3.6.1.4.1.9)
Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)
Direct children (1)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 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 … |