I have updated my CSPM install and my sensors to the latest signature revision. Unfortunately, now CSPM is telling me that 3.0(2)S10 is not a supported version? Any idea what's going on? I know the same thing happened with 2.3.2i and 3.0(2)S9. What can I do (if anything) to fix this?
"Specified IDS Sensor Version 3.0(2)S10 is not an exact match to a supported
version. All features may not be supported."
How do you send the configuration to the sensor, because I can no longer use the "Approve Now" button to send the configs to the sensor?
Side Note: I can select every tab in the sensor window, but when I select the "Blocking" tab my application crashes and I receive a Dr. Watson error for cfmi.exe. Have you experienced this strange problem?
I wasn't aware of any problem with the Approve Now button.
The thing to keep in mind is that when the WARNING shows the Approve Button may not be selectable.
This is because the "Pending Commands" radial button has to be selected to push the Approve Button.
But the WARNING message shows up when another option is selected "Generation Status" if I remember correctly.
NOTE: The message about the version is just a WARNING and not an ERROR. It is just letting you know that new features in 3.0(2) aren't configurable in CSPM so only 3.0(1) features will be configured in the configuration files. Of course, this time around only bug fixes and no features were added in 3.0(2) so you can ignore the WARNING.
I also hadn't heard of any problem with the Device Management windows crashing. Have you called the TAC on that issue? I would recommend contacting the TAC if you haven't yet.
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...