System Components
MainApp
Cisco Intrusion Detection System Appliance and Module Installation and Configuration Guide Version 4.1
A-8
Authenticating Users, page A-12
•
•
LogApp, page A-15
NAC, page A-16
•
•
TransactionSource, page A-28
WebServer, page A-29
•
CLI, page A-29
•
•
EventStore, page A-36
MainApp has the following responsibilities:
•
Initialize and start all IDS components and applications.
MainApp is started by the operating system. It starts the applications in the
following sequence:
Read and validate contents of dynamic and static configurations.
1.
2.
Write dynamic configuration data to system files to make sure the two
representations of data are in sync (for example, the IP address in the
dynamic configuration must match the system network files).
Create the shared system components—EventStore and IDAPI.
3.
4.
Open status event subscription.
5.
Start the IDS applications (the order is specified in the static
configuration).
6.
Wait for an initialization status event from each application.
If after waiting 60 seconds all status events have not been received,
MainApp generates an error event identifying all applications that did not
start.
7.
Close status event subscription.
Start the upgrade scheduler.
8.
9.
Register for control transaction requests, and service them as received.
Appendix A
Intrusion Detection System Architecture
78-15597-02
Need help?
Do you have a question about the IDS-4230-FE - Intrusion Detection Sys Fast Ethernet Sensor and is the answer not in the manual?
Questions and answers