Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I have a licensed IDSM-2 sensor running: Cisco Intrusion Prevention System, Version 5.0(5p1)S211.0 Maintenance Partition Version 2.1(2)Recovery Partition Version 1.1 - 5.0(1)S149 When I try to upgrade to 5.1.1a I get the following messag...
Using the IPS Management Center 2.1 I can create a never block entry 9.xxx.0.0/255.255.128.0 for an IDS4 sensor, but when I do this with an IPS5 sensor (both IDSM-2s) I get the error message: ErrorObject update failed. Validation exception during obj...
I am having a problem configuring promiscuous mode with an IDSM-2 running 5.0(3)S181.0 in a 6509 with Sup 720 running IOS 12.2(18)SXD4. I am running router interfaces without VLANs so I have created an extended access list with a 'permit ip any any'...
When I install signature 171 to IDSM2's using VMS 2.3 I get: An error occurred while running the update script on the sensor named IDS-C1-B. Detail = An error occurred at the sensor during the update, sensor message = idsPackageMgr: digital signature...
I am running VMS 2.2 with FW, SecMon and IDS applications. Because I am moving to new server hardware I installed VMS 2.3 on the new hardware thinking that I could backup my MC databases under 2.2 and restore them under 2.3, but that doesn't seem to...
Thanks for the info. I need the 5.0(5p1) patch, otherwise the sensors hang when installing signatures. I assume that the patch will be available someday in 5.1.1x. Will I still not be able to install 5.1.1x, or do you think that they will fix the ...
I am testing a similar situation with IDSM-2, IPS 5, and dual core IOS. If you currently have parallel equal cost routes it is important to engineer your traffic such that the IDSM-2 sees all session data over one interface (maybe with OSPF cost, if...
Yes, I have a similar problem with a couple of IDSM-2s running IPS-K9-sp-5.0-4. With the previous version I also received the NotRunning error, with the current version I now get Stopping. The last time this happened to me was after upgrading to si...
Thanks for the Tip!, using your suggestion I also reinstalled on top of the nonfunctioning 2.0 install, this time without upgrading the database, and now after reimporting all the devices in IDSMC and SM, everything seems to work. I had opened a TAC...
Yes, they are on different switches. I have a 3 x 1GB trunk/channel between them dedicated to the 'failover' and 'stateful' vlans. When I failover to the secondary, I get the messages from the new standby.
