Because the IDS software is sold as a complete disk image (complete OS, and IDS application all together) and not as an application applied to an OS that the user has installed themselves, there is no specific externally accessible document that says what operating system is running on each version of the sensor.
The user does not load Solaris or Linux and then load the IDS software.
Instead the user purchases a Cisco IDS sensor appliance or module, which includes the associated IDS image.
The image will install a complete operating system and IDS specific daemons and configurations. The image is either installed from CD or through specific remote re-imaging processes that differ depending on the type of sensor being used.
The upgrades to the sensor will in general contain both the modifications to the IDS specific files, as well as patches and changes to the underlying OS.
The one excecption was the upgrade from 3.x to 4.x which required that the user order an Upgrade CD. When the sensor booted to the CD, the harddrive of the sensor is reformated and a new OS and new IDS files were loaded on the harddrive. This was necesary because we changed the OS from Solaris to Linux when we went from version 3.x to 4.x.
In version 4.x, we've included a CLI that has similarities to an IOS router's CLI. All user interaction should ocurr through the CLI or web server interfaces, and so there is no need for the user to even know that the underlying OS is Linux. In 4.x we even restrict access to the underlying OS by requiring the user of a special "service" account that should only be used under direction of the TAC.
Unlike some other IDS vendors the Cisco IDS Sensor software is not an application that you can install on your own system with an operating system that you have installed. Instead it is a complete Operating System image that is built specifically for the Cisco IDS sensor appliances and modules.
Image files (and CDs) for the sensor contain all of the operating system files, and IDS files all packaged together.
Upgrades include changes to the IDS specific files, as well as patches and fixes to the underlying OS.
This eliminates the need for users to patch and manage the underlying OS themselves. We take care of keeping the patches uptodate and securing the operating system through the normal IDS upgrade methods.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...