IPS Engine Upgrade

Hi all
I have an IPS running 6.1(1) image with E1 engine.I want to upgrade this to E3.Is to possible to upgrade directly to E3?.What are the things to consider for upgrading the Engine(i want to upgrade manually)? Is there any advange on E3 over E2 or E1?
Thanks In Advance

Yes, you can go directly from 6.1(1)E1 to 6.1(1)E3.
Go to this link, select your model sensor, select the IPS System Upgrades link, and select All Releases->E3->6.1->6.1(1)E3.
http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=278875311
Download the IPS-engine-E3-req-6.1-1.pkg file, and install it on your sensor.
The "engine" upgrade changes just the E level of the sensor.
HOWEVER, I recommend that on your next scheduled network downtime that you upgrade all the way to 6.1(2)E3.
Instead of selecting 6.1(1)E3 you would instead select 6.1(2)E3 on that download page.
You can then download IPS-K9-6.1-2-E3.pkg file (name might differ for the AIM and NME platforms).
Installing this file will upgrade not only the Engine level from E1 to E3, but will also upgrade you to the next Service Pack level (2).
Why should you upgrade to E3 instead of E2?
All new signature updates are only released for E3. Signatures stopped being developed for E2 as soon as E3 was released. You always need to stay at the latest E level to get the latest signature updates.
Why should you upgrade all the way to 6.1(2)E3 instead of just 6.1(1)E3?
You get additional bug fixes by going to 6.1(2)E3.
In addition you need to keep in mind that there will at some point be an E4, and there are rules as to which versions E4 will be available for.
The next Engine Update (in this case E4) will be available for the latest service pack of each Major.Minor version. With 6.1 that latest Service Pack is 6.1(2). It will not be available for the prior Service Pack level unless the most recent service pack has been released less than 60 days ago.
Explanation:
6.1(2)E3 was released on Dec 19, 2008.
If E4 has been released any time between Dec 19, 2008 and Feb 19, 2009; then we would have released both an E4 for 6.1(2) AS WELL AS 6.1(1). After Feb 19, 2009 Cisco will no longer release an Engine Update for 6.1(1). So E4 will be released for 6.1(2), and NOT 6.1(1).
So to be prepared for E4 you need to be running 6.1(2)E3 right now.
Any time a new Service Pack is released you should be scheduling to upgrade to that next Service Pack within 60 days if you want to be sure you are always able to install the latest signature and engine updates.

Similar Messages

IPS engine upgrade with failover ASA, now they don't match?

We recently added a failover 5520 with the ASA-SSM-20, which matches the primary ASA/IPS. My question is I just upgraded the primary IPS to 5.1(5)-E1. It went fine, except now the failover IPS is still on 5.0(2). How do I update the failover IPS to match what's on the primary?
Shouldn't this happen automatically since it is setup in a failover scenario? I have it cabled via a cross-over cable to the primary ASA.

The SSM modules are managed completely separately from the firewalls; you need to upgrade & manage both of them individually, as well as apply the same configurations to each either separately, or via a group in either CSM or VMS...
If the second SSM module hasn't been given its own IP, you can "session" into it from the standby firewall console and then give it it's own IP..
If this helped, please rate the post :-)
Thanks!
...Nick

Upgrading IPS Engine to 7.0(4) E4

Hi All,
I am running an 6500 Series IDSM-2 Module with Engine Version 7.0(2) E3 and Signature pack S479. Can i directly update to the latest Engine Version 7.0(4) E4 or not. Please do let me know.
Regards
Kiran

Hi Kiran,
Yes, you can upgrade directly to the 7.0.4e4 package. This will allow you to use the latest signature updates.
Best Regards,
Justin

Ips 4215 Upgrade to version 6

Hi there, I got a IPS 4215 on Ebay, then I want to upgrade it to 6.XX versions of IPS Software (currently I run 5.0.1).
I downloaded the following files:
IPS-4215-K9-sys-1.1-a-6.0-6-E3.img
IPS-4215-K9-sys-1.1-a-6.0-5-E3.img
But when I flash using them under rommon, everything goes fine, It restart, flash the partition, reboot, then I goot kernel panic : not enough memmory and no killable processes. I added a 512Mb of ram, which bring the IPS to a total of 768Mbps...
ANyone did have this issue ?
I successfully upgraded to 5.1 image, but then I can't upgrade to a 6x image using the upgrade command, it tells me I need a version 1 or earlier of the engine.
Did anyone upgraded its IDS4215 to a IPS 6.X image ? If so, could you please give me image name(s)/procedures ?
THanks.

So it sounds like I can just import them from that folder into the current version of palm 6.2. Or is it better to go back to the previous version? The only issue I had with the previous version was difficulty in hotsyncing a program called Thomson clinical xpert, it would allow it to expire.
Post relates to: Tungsten E2

Location to download IPS software upgrade Version 7.1(5)E4

Hi,
In last month I found latest released IPS software version 7.1(5)E4 for IPS appliance 4260 on cisco site.
However it is no more available over there now can I have exact download location of the software upgrade as I want to upgrade my device with the latest release.
Regards,
Tanvirsinh Padheriya

Cisco announced there are some problem (lockup, crash, etc) in ver. 7.1.5 today.
They have halted downloads of 7.1.5
see more info. the below page
http://tools.cisco.com/security/center/viewBulletin.x?bId=475&year=2012
best regards,
Roy Lee

ASA SSM IPS module upgrade won't work

Hello all,
I'm trying to upgrade the IPS sig's on an ASA5520 with a SSM IPS module. I'm trying to upgrade the system to 5.1.1 to further upgrade the device with no luck.
I followed these steps provided by Cisco.com:
1. Log in to the ASA.
2. Enter enable mode:
asa# enable
3. Configure the recovery settings for ASA-SSM:
asa (enable)# hw-module module 1 recover configure
NOTE: If you make an error in the recovery configuration, use the
hw-module module 1 recover stop command to stop the system reimaging
and then you can correct the configuration.
4. Specify the TFTP URL for the system image:
Image URL [tftp://0.0.0.0/]:
Example:
Image URL [tftp://0.0.0.0/]: tftp://10.20.30.40/IPS-SSM-K9-sys-1.1-a-5.1-1.img
5. Specify the command and control interface of ASA-SSM:
Port IP Address [0.0.0.0]:
Example:
Port IP Address [0.0.0.0]: 11.21.31.41
6. Leave the VLAN ID at 0.
VLAN ID [0]:
7. Specify the default gateway of the ASA-SSM:
Gateway IP Address [0.0.0.0]:
Example:
Gateway IP Address [0.0.0.0]: 11.22.33.44
8. Execute the recovery:
asa# hw-module module 1 recover boot
9. Periodically check the recovery until it is complete.
NOTE: The status reads "Recovery" during recovery and reads "Up" when
reimaging is complete.
AFter #8 it just goes back to the enable prompt. A 'sh module' lists the device as 'recover' and hangs FOREVER.... I tested the TFTP server which the new image resides on, and the TFTP is working fine. I don't see any attempts or downloads from the TFTP server for over an hour.
I opened a Ciscop TAC on this and not receiving alot of help...
Please help!!!:)
Thanks
Chris Serafin
[email protected]

The recovery using this method can takes upwards of 30 minutes, and in some cases even longer.
How long have you left the SSM in the "recovery" state?
There may be something wrong in the config you entered. when that happens the SSM can go into a continuous reboot cycle trying to do the recovery.
Execute "debug module-boot" on the console of the ASA.
The debug output will show you the ROMMON output of the SSM itself. (The SSM has it's own ROMMON. The recovery boot command sends the settings made during the recover configure command to the SSM's ROMMON).
If the ROMMON is experiencing a problem in trying to download the tftp image you should now see that ROMMON error message.
Some typical problems I have seen:
1) Wrong IP given for the sensor.
2) Wrong IP given for the gateway (the gateway must exist on the same network as the sensor) this problem usually happens when using a non-standard netmasked network.
3) Not having the sensor's command and control port plugged into the right network. The external port of the SSM itself is where the IP is being applied. You need to ensure that the extenral port of the SSM is plugged into the right network for that IP.
4) The tftp server is not reachable from the network where the sensor's command and control port is attached. Some users think that if the ASA itself can reach the tftp server that the SSM will also be able to. This is not always the case. It is best to use a tftp server on the same network as the IP provided to the SSM. Or to test the tftp server from another machine on the same network as the SSM.
5) The file name is wrong. Check the captialization especially.
6) The file is not in the default directory on the tftp server. If the file is in a subdirectory you will need to add that subdirectory to the URL:
tftp://10.20.30.40/subdirectoryname/filename
7) The tftp is timing out.
There are 2 things that can cause this:
a) The tftp server is remote, and it takes too long to download the file. The ROMMON does have limits on the number of retries and per packet timeouts (but they are not user configurable). Try using a tftp server local to the SSM.
b) The switch that the SSM connects to has spanning-tree running and spanning-tree does not complete before the SSM ROMMON times out for the tftp attempt. The tftp attempt happens immediately upon ROMMON startup and link up. But with a switch the switch port may be in a "Listen" or "Learn" state for 40 seconds before the box can actually talk on the network. In some cases the tftp download attempts started as soon as link up, and may timeout even before the spanning-tree completes. To work around this configure "spanning-tree portfast" on the switchport. Spanning-tree will connect the port into the vlan immediately rather than 40 seconds later.
If it was a config problem when configuring the recovery settings, then there is a "recover stop" command on the ASA.
It will stop the reboot cycle from happening.
Let the module come up with the old image.
Then correct your "recover configure" settings, and try the "recover boot" again.
Another alternative:
Stop the recovery "recover stop"
Let it boot into the old image.
If it was a 5.0 version, then you can actually upgrade to 5.1 using the sensor's own CLI "upgrade" command. It is actually the preferred method.
The "recover" from the ASA will wipe the box clean and load a fresh image.
The "upgrade" from the sensor will convert your 5.0 config into a 5.1 config while installing 5.1.
5.1 upgrade file:
IPS-K9-min-5.1-1g.pkg
http://www.cisco.com/cgi-bin/tablebuild.pl/ips5
It can be applied through the sensor's CLI upgrade command, or pushed directly through IDM, or applied by CSM.
The "recover" should be limited to disaster recovery. When you can't access the SSM at all, or the files on the SSM have been corrupted.
For normal upgrades you want to use "upgrade" files done through the sensor itelf (CLI, IDM, or CSM).

IPS 4240 upgrade

hi,
i am running version 6.2 on ips 4240. could please someone let me have the procedure to upgrade the OS to 7.1.8 please? is this upgrade same as cisco IOS using tftp ?
what is the procedure to upgrade ? is it first os and then sensor ? cold you please post the commands ?
Thanks

Get the 7.18 upgrade pkg file from here:
http://software.cisco.com/download/release.html?mdfid=283674966&flowid=24482&softwareid=282549759&release=7.1(8)E4&relind=AVAILABLE&rellifecycle=&reltype=latest
The readme is available from the same link.
In order to apply 7.1(8), the minimum required running version is 6.0(6) on 42xx series sensors, which you have, so you can simply apply the upgrade pkg. Apply it via IDM is probably the easiest way - or check the readme for CLI instructions.
7.1(8) is packaged with signature level s735 - if you have a more recent level, that will be preserved, if not, you will end up @ s735. Then you can update the signature package to the most current level from here:
http://software.cisco.com/download/type.html?mdfid=283674966&flowid=24482

Y510p IPS panel upgrade?

My y510p is over a year old now and the 1080p TN panel just doesn't cut it. I've watched a hundred people swap them on the Y50 for LG IPS panels with great results. Does the Y510p have the same connections that I can just use the Y50 tutorial or is this a no go? Or is there an adapter i could use.

Ah, that's a shame. I was hoping to do that myself. Thanks for posting your findings.
Y510p - i7 4700MQ (Overclocked to 3.6GHz), SLI GT755M, Corsair Vengeance 16GB 2133MHz, Samsung 850 Pro 256GB, MyDigitalSSD SuperBoot 128GB, Intel Wireless-AC 7260, Windows 7 Home Premium (SP1)

Upgrade AIP SSM with Signature Engine 4 file

When I tried to upload Signature Engine 4 file (IPS-engine-E4-req-7.0-2.pkg), using FTP server both by CLI and IDM, to new AIP SSM sensor, I got the following error message:
Cannot upgrade software on the sensor - socket error:110.
When I tried to do the same by using these steps: IDM --> Configuration --> Sensor Management --> Update Sensor --> choose Update is located on this client --> choose the "IPS-K9-7.0-2-E4.pkg" file --> hit the "Update Sensor" button, I got the following error message
The current signature level is S480.The current signature level must be less than s480 for this package to install.
Here is the output for sh ver command
AIP_SSM# sh version
Application Partition:
Cisco Intrusion Prevention System, Version 7.0(2)E4
Host:
    Realm Keys          key1.0
Signature Definition:
    Signature Update    S480.0                   2010-03-24
OS Version:             2.4.30-IDS-smp-bigphys
Platform:               ASA-SSM-10
Serial Number:          JAF1514BAHS
Licensed, expires:      07-Jun-2012 UTC
Sensor up-time is 21 days.
Using 695943168 out of 1032495104 bytes of available memory (67% usage)
system is using 17.4M out of 38.5M bytes of available disk space (45% usage)
application-data is using 45.4M out of 166.8M bytes of available disk space (29% usage)
boot is using 41.6M out of 68.6M bytes of available disk space (64% usage)
application-log is using 123.5M out of 513.0M bytes of available disk space (24% usage)
MainApp            B-BEAU_2009_OCT_15_08_07_7_0_1_111   (Ipsbuild)   2009-10-15T08:09:06-0500   Running
AnalysisEngine     BE-BEAU_E4_2010_MAR_25_02_09_7_0_2   (Ipsbuild)   2010-03-25T02:11:05-0500   Running
CollaborationApp   B-BEAU_2009_OCT_15_08_07_7_0_1_111   (Ipsbuild)   2009-10-15T08:09:06-0500   Running
CLI                B-BEAU_2009_OCT_15_08_07_7_0_1_111   (Ipsbuild)   2009-10-15T08:09:06-0500
Upgrade History:
IPS-K9-7.0-2-E4   02:00:07 UTC Thu Mar 25 2010
Recovery Partition Version 1.1 - 7.0(2)E4
Host Certificate Valid from: 30-May-2011 to 30-May-2013
Any idea what could be the problem?
Regards,

Based on your show version, you already have E4, what is it that you are trying to do?
Mike

Active-Standby SSM-IPS upgrade question

I have 2 ASA 5510's with ASA-SSM-10 IPS modules. The IPS's were running version 5.0.2, and I noticed this will not be supported for SIGS so I started to upgrade to version 5.1.1g. I got one unit upgraded and it seems to be fine, but the second still says it is running 5.0.2 and it will not let me login to it via CLI. When I for a failover the IPS always seems to be with the upgraded unit, so I can never get to my other IPS to upgrade it.
What did I do wrong?
Thanks,
Dan

When you say it will not let you login via CLI, what method of connection are you attempting? Are you telneting directly to the management IP of the second SSM, or sshing directly to the management IP of the second SSM, or sessioning through the console of the second ASA into the second SSM?
What if any errors are you seeing when trying to login?
When you say that you failover the IPS you can't get to the other IPS, to what are you referring?
The SSMs don't failover to each other. They do not share configuration, and should not share IP Addresses for their management IP. If you have configured the same IP for both SSMs, then you have a bad configuration. Each SSM needs their own independant IP Address. The SSMs should be managed as independant sensors.

IDSM-2 upgrade process questions.

Hello,
I started a new job and have been tasked with looking into what we can do with the IDSM-2 module we have in our 6509. The company has not been using the module so it hasn't been updating in a few years. I do not have a current license so I know I cannot install new signature updates, but what I would like to do is upgrade the software to version 7.0(5a)E4. Once I have it upgraded I would like to configure it in our environment and then see about getting a signature license.
I have a few questions regarding the upgrade process, and could use some assistance.
First the IDSM is currently running version 5.1(3)S256.0. From what I have read I don't believe I can go directly to 7.0(5a)E4 so my Planned Upgrade Path is: 5.1(3)S256.0 -> 5.1(8)E3 -> 7.0(5a)E4.
Am I able to upgrade this way or is there another recommended way that I should do this upgrade?
The files I have for this are below, will they be enough or am I missing any?
Do I apply them in the order listed?
Can I apply all of these files from the IDM GUI?
IPS-K9-5.1-8-E3.pkg
IPS-engine-E3-req-5.1-8.pkg <--- Is this included in the above file?
IPS-K9-r-1.1-a-5.1-8-E3.pkg
IPS-K9-7.0-5a-E4.pkg
IPS-K9-r-1.1-a-7.0-5a-E4.pkg
I plan on backing up my configuration first just in case, but should this process have any affect on the configuration?
I also saw that the upgrade will convert the configuration, so should I back it up a second time between the 5.1(8)E3 and 7.0(5a)E4 step?
Will there be any effect on network traffic or downtime during this process?
Is there any thing else I need to be aware of or that I'm missing?
Thanks in advance,
Will

Hi Will. Since you indicated that this sensor has not been in-use, it would be quickest/easiest to simply re-image it directly to the desired version (7.0(5a)E4). Additional benefits of doing this are that the sensor's filesystem will be created clean, OS/binaries cleanly installed, no potential config conversion issues, etc.
Step-by-step instructions for doing this can be found here.
And, the System Recovery Image file you will need ('IPS-IDSM2-K9-sys-1.1-a-7.0-5a-E4.bin.gz') can be downloaded here.
Will there be any effect on network traffic or downtime during this process?
That depends on whether the sensor is configured in Promiscuous Mode or Inline [VLAN Pair] Mode. You can determine this from the Catalyst config. If the sensor is installed in Inline [VLAN Pair] Mode, then certainly the re-image (and even just upgrade) could be traffic-impacting (if there is no alternative/backup path for traffic to take), as in both scenarios, the sensor is rebooted and not available for ~10 minutes (during which time, it would not be forwarding traffic (if it were installed Inline)). Additionally, since re-imaging results in a clean/default config, if the sensor were configured Inline, that portion of the config would have to be re-input post-reimage so that the sensor would know to forward traffic accordingly again. Details about the modes can be found here.

AIP-SSM Upgrade Procedure

Hi everybody!
I have ASA5520 version 8.2(1) with AIP-SSM-20 module
and I want to upgrade AIP-SSM-20 software from version 6.1(3)E3 to 7.0(2)E4
I go to the download site and see the following list:
Intrusion Prevention System (IPS) Recovery Software:
IPS-K9-r-1.1-a-7.0-2-E4.pkg
        Release Date: 29/Mar/2010
        IPS Recovery Image File
Intrusion Prevention System (IPS) Signature Updates:
IPS-sig-S481-req-E4.pkg
        Release Date: 31/Mar/2010
        E4 Signature Update S481
Intrusion Prevention System (IPS) System Software:
IPS-SSM_20-K9-sys-1.1-a-7.0-2-E4.img
        Release Date: 29/Mar/2010
        IPS-SSM_20 System Image File
Intrusion Prevention System (IPS) System Upgrades
IPS-K9-7.0-2-E4.pkg
        Release Date: 29/Mar/2010
        IPS 7.0 Major Upgrade File (All Supported Platforms Except AIM-IPS and NME-IPS)
IPS-engine-E4-req-7.0-2.pkg
        Release Date: 29/Mar/2010
        IPS E4 Engine Update
I am somewhat confused by the number of files and want to ask what the procedure/sequence I should follow to upgrade?

This is the file that you would like to use to upgrade it:
Intrusion Prevention System (IPS) System Upgrades
IPS-K9-7.0-2-E4.pkg
To upgrade:
1) Upload the "IPS-K9-7.0-2-E4.pkg" file through IDM
2) IDM --> Configuration --> Sensor Management --> Update Sensor --> choose Update is located on this client --> choose the "IPS-K9-7.0-2-E4.pkg" file --> hit the "Update Sensor" button.
It will take a while (around 20 minutes) to upgrade the sensor, so don't panic if it doesn't come back up in "UP" status straight away.
Hope that helps.

Upgrade AIP-SSM-10 to E4

Hello, I am trying to upgrade from e3 to e4 and then upgrade my software...
here is a show version
Cisco Intrusion Prevention System, Version 6.2(2)E3
Host:
    Realm Keys          key1.0
Signature Definition:
    Signature Update    S479.0                   2010-03-19
    Virus Update        V1.4                     2007-03-02
OS Version:             2.4.30-IDS-smp-bigphys
Platform:               ASA-SSM-10
Serial Number:
Licensed, expires:
Sensor up-time is 171 days.
Using 674635776 out of 1032499200 bytes of available memory (65% usage)
application-data is using 43.5M out of 166.8M bytes of available disk space (28% usage)
boot is using 40.1M out of 68.6M bytes of available disk space (62% usage)
MainApp          E-ECLIPSE_2009_SEP_14_13_21_6_2_1_119   (Ipsbuild)   2009-09-14T13:22:32-0500   Running
AnalysisEngine   E-ECLIPSE_2009_SEP_14_13_21_6_2_1_119   (Ipsbuild)   2009-09-14T13:22:32-0500   Running
CLI              E-ECLIPSE_2009_SEP_14_13_21_6_2_1_119   (Ipsbuild)   2009-09-14T13:22:32-0500
Upgrade History:
* IPS-K9-6.2-2-E3           10:33:06 UTC Tue Sep 22 2009
IPS-sig-S479-req-E3.pkg   12:17:09 UTC Tue Jun 22 2010
Recovery Partition Version 1.1 - 6.2(2)E3
Host Certificate Valid from: 15-Jun-2010 to 15-Jun-2012
I understood that I can upgrade to IPS-engine-E4-req-7.0-2.pkg but when I try this from the asdm or from the cli, here is the output from the cli:
IPS-1(config)# upgrade ftp://N****@***.**.**.**//IPSengine-E4-req-7.0-2.pkg
Password: ********
The filename IPSengine-E4-req-7.0-2.pkg is not a valid upgrade file type.
Continue with upgrade? []: no
IPS-1(config)# upgrade ftp://N****@***.**.**.**//IPSengine-E4-req-6.2-2.pkg
Password: ********
The filename IPSengine-E4-req-6.2-2.pkg is not a valid upgrade file type.
Continue with upgrade? []: no
IPS-1(config)# end
do I want to just go ahead with the upgrade? even though it is telling me its not a valid upgrade type?
thanks for any help...

You can only upgrade using the IPS-engine-E4-req-7.0-2.pkg file if you are already running the latest version on that major version: 7.02(E3).
So since you are running version 6.2.2(E3) at the moment, I would suggest that you upgrade the module to the latest E4 directly using this upgrade file:
IPS-K9-7.0-4-E4.pkg
Here is the readme file for 7.0.4(E4):
http://www.cisco.com/web/software/282549709/35783/IPS-7_0-4-E4_readme.txt
Hope that helps.

Engine E2 Question

Dear Sir/Madam,
I manage four Cisco IPS sensors SSM-20. I am currently running 6.0(3) E1 and do not particularly want to upgrade to 6.0(4) because of the following;
CSCsm60273 AIP-SSM stays in Unresponsive state after ASA5500's bootup
I have a number of power downs this year but need to continue to install signature updates but will be unable to if I do not upgrade to 6.0(4) E2 as per your comment below,
Warning: After E2 is released, your sensors must be running release 5.1(7)E2 or 6.0(4)E2 to continue to install signature updates.
I would prefer to stay on 6.0(3) and upgrade to E2 (as this version is eligibale for engine upgrade) and wait until caveat CSCsm60273 is resolved - hopefully in 6.0(5)but I then will not be able to apply the signature updates.
Please can you assist me?
Thanks in advance for your time.
Rich,

Understand that CSCsm60273 is not specific to 6.0(4). It can also happen with the 6.0(3) you are already running and likely earlier versions as well.
It will also not be fixed in 6.0(5).
Instead it has been determined to be a bug in the ASA/Rommon and not in the IPS image.
So it can not be fixed in 6.0(5), and instead needs a new ASA and/or Rommon to get the fix.
So this bug should not affect your decision on whether or not to upgrade to 6.0(4).
As for E2 understand that 6.0(3) is NOT elligible for upgrade to E2. E2 will only be created for 6.0(4).
The 6.0(3) elligibility for E2 ran out at the end of April.
The signature policy states "b) Signature update support for service packs of currently supported major and minor software releases will be supported for at least sixty (60) days following the introduction of a new service pack."
So 6.0(3) was fully supported for signature updates (and therefore engine updates) for 60 days after 6.0(4) released.
6.0(4) released at the end of February so 6.0(3) support was only guaranteed for 60 days which was the end of April.
Now in May there is no longer any guarantee of signature support (or engine updates) for 6.0(3).
So long as E2 has not released you can still install the E1 signature updates on any E1 sensor (including 6.0(3)E1). But when E2 is released it will only support 6.0(4). It will not support 6.0(3) because when E2 releases it will have been more than 60 days since 6.0(4) was released.
NOTE: E2 will also support the latest service pack on the 5.1 train which is 5.1(7).

Upgrade from 6.2(1) E3 to 7.0(4) E4

Hi all,
i want to upgrade my IDSM-2 from 6.2(1) to 7.0(4).
my interface is promiscuous mode and inline highrisk Deny packet Inline is enable on it.
i want to know while upgrading process,
what will happen to packet flow?
is it gonna stop or go normal.
Bypass mode is Auto
Thanks,
Charanjit Singh

yeah i got what u mean,
but in our organization we can't make changes without knowing the full rollback procedure.
and one last question,
when i go to cisco to download files
IPS Manager Express (IME) Software
Intrusion Detection System (IDS) Recovery Software
Intrusion Detection System (IDS) Signature Updates
Intrusion Detection System (IDS) System Software
Intrusion Detection System (IDS) System Upgrades
Intrusion Prevention System (IPS) Recovery Software
Intrusion Prevention System (IPS) Signature Updates
Intrusion Prevention System (IPS) System Software
Intrusion Prevention System (IPS) System Upgrades
please correct me if i am wrong.
System software are system images.
sytem upgrades are like engine upgrades,
Signature updates are normal singnature update on specific engine.
What is the difference between IPS and IDS files.
and where and when we use recovery software
TIA

IPS Engine Upgrade

Similar Messages

Maybe you are looking for