Upgrading IDS4.0 to IPS

Can I upgrade IDS 4.0 to IPS. If so, pls tell me what procedure i have to follow.

Following page shows the list of supported sensors that can be upgrated to IPS5.1:
http://www.cisco.com/en/US/customer/products/hw/vpndevc/ps4077/products_installation_guide_chapter09186a008055fc77.html#wp498739
The upgrade procedure to upgrade from IPS 4.1 to 5.x is given here:
http://www.cisco.com/en/US/customer/products/hw/vpndevc/ps4077/products_installation_guide_chapter09186a008055fc78.html#wp1032104

Similar Messages

Activate the license and upgrade signature of AIS IPS on ASA

Hi,
I alreay have smartnet contract for my IPS. Now, I need to do auto upgrade my IPS signature
While i was doing, it ask me to activate license key. How to get the license key for my IPS?
Regards, CT

You can grab your license here:
http://cisco.com/go/license
and install it with these instructions:
http://www.cisco.com/en/US/docs/security/ips/7.0/configuration/guide/cli/cli_setup.html#wp1046739
- Bob

Upgrading a 4215 to IPS

I would like an explanation of the upgrade process from a Cisco 4215 IDS sensor to the IPS 5.0 capabilities. Does it require extra hardware?

If you do not have the 4FE card installed, you will need to purchase/install one in order to create inline pairs on a 4215 with IPS 5.0 software. In a future release, you will be able to take advantage of the inline capabilities with a single sensing interface.
Regarding the upgrade process, this can be found in the readme file for the 5.0 Major Upgrade (to maintain current settings) or the 5.0(2) system image (for clean system image). Both of these install files, as well as the associated readmes, can be found on the software download page on CCO:
http://www.cisco.com/kobayashi/sw-center/ciscosecure/ids/crypto/
-Rusty

Upgrade from IDS 4235 to IPS 5.0 license

Dear sirs. I have several 4235 sensors and SMARTnet 8x5xNBD contracts on each of them.
Have I upgrade their software to IPS v5.0 within this contracts or I should get licenses for the IPS?

Some one is feeding you a line of crap.
The main announcement for Cisco IDS version 5.0 has this 'fine print' at the bottom of the page:
"*Cisco IPS Sensor Software Version 5.0 is supported on the Cisco IDS 4215, IDS 4235, IPS 4240, IPS 4255, and IPS 4250-XL appliances and on the IDSM-2. It is supported in the promiscuous-based IDS mode only, for the IDS 4210 and the Cisco IDS Network Module (NM-CIDS).
Inline IPS services require more than one monitoring interface on Cisco IPS 4200 Series sensors."
This is posted at the following URL:
http://www.cisco.com/en/US/products/hw/vpndevc/ps4077/prod_bulletin0900aecd801e65b9.html
Also, Cisco has stated the same thing in the 'Read Me' file that accompanies the software update:
"You can apply the IPS-K9-maj-5.0-1-S149.rpm.pkg major update to the following IDS & IPS version 4.1 sensors:
- IPS-42xx Cisco Intrusion Prevention System (IPS) sensors
- IDS-42xx Cisco Intrusion Detection System (IDS) sensors (except for the IDS-4220 and the IDS-4230 series)
- WS-SVC-IDSM2 series Intrusion Detection System Module (IDSM2)
- NM-CIDS IDS Network Module for Cisco 26xx, 3660, and 37xx Router Families
It is not compatible with the IDS-4220 and IDS-4230 series IDS sensors, the NRS-xx series IDS sensors, or the WS-X6381-IDS series Intrusion Detection System Module (IDSM)."
I hope this helps,
Alex Arndt

Idsm-2 problem: sensor upgrade from 4.1 to 5 or higher

Hi all,
I have a problem with my IDSM-2 module. I'm trying to sensor upgrade from IDS to IPS software (from 4.1 version to 5.x or higher).
If I do this from sensor under "admin user" and use major patch - IPS-K9-maj-5.0-1e-S149.rpm.pkg then I receive error:
"Error: idsPackageMgr: digital signature of the update file was not valid, use CCO to replace corrupted file ".
But file "IPS-K9-maj-5.0-1e-S149.rpm.pkg" is NOT corrupted. I cheked it under "service user" with md5sum utility - checksum is correct.
If I try to upgrade from maintance mode (ie re-image with wipe all information in application partition) then I receive:
"Application image upgrade complete. You can boot the image now.
Partition upgraded successfully"
Next, I'm reboot IDSM-2 module and receive:
"000133: Sep 7 15:10:18.622 MSK/MDD: %HA_EM-6-LOG: Mandatory.go_bootup.tcl: GOLD EEM TCL policy for boot up diagnostic
000134: Sep 7 15:10:18.290 MSK/MDD: %DIAG-SP-3-MAJOR: Module 4: Online Diagnostics detected a Major Error. Please use 'show diagnostic result <target>' to see test results.
000135: Sep 7 15:10:18.294 MSK/MDD: %CONST_DIAG-SP-3-BOOTUP_TEST_FAIL: Module 4: TestPCLoopback failed on port(s) 3-4
000136: Sep 7 15:10:19.170 MSK/MDD: %OIR-SP-3-LC_FAILURE: Module 4 has Major online diagnostic failure, Card will be reset to re-run diagnostic. Please check sup-bootflash diaginfo file for previous detailed diagnostic result.
000137: Sep 7 15:10:19.170 MSK/MDD: %OIR-SP-3-PWRCYCLE: Card in module 4, is being power-cycled 'off (Diagnostic Failure)'
000138: Sep 7 15:10:19.170 MSK/MDD: %C6KPWR-SP-4-DISABLED: power to module in slot 4 set off (Diagnostic Failure)"
ie module go to the "PwrDown" state.
I try to upgrade for next firmware:
IPS-K9-maj-5.0-1e-S149.rpm.pkg
IPS-IDSM2-K9-sys-1.1-a-7.0-5a-E4.bin.gz
IPS-K9-7.0-5a-E4.pkg
IPS-K9-maj-5.0-1e-S149.rpm.pkg
WS-SVC-IDSM2-K9-sys-1.1-a-5.0-1.bin.gz
and did not get success
chassis - 6509-e, sup - VS-S720-10G + VS-F6K-PFC3C, ios - s72033-adventerprisek9_wan-mz.122-33.SXI6.bin
maintance software for IDSM-2 module - 3.4(2)m
Could you please help me? Thanks in advance!

I have a problem with my IDSM-2 module. I'm trying to sensor upgrade from IDS to IPS software (from 4.1 version to 5.x or higher). If I do this from sensor under "admin user" and use major patch - IPS-K9-maj-5.0-1e-S149.rpm.pkg then I receive error: "Error: idsPackageMgr: digital signature of the update file was not valid, use CCO to replace corrupted file ". But file "IPS-K9-maj-5.0-1e-S149.rpm.pkg" is NOT corrupted. I cheked it under "service user" with md5sum utility - checksum is correct.
It has been a long time since I've seen a sensor running 4.1 or an upgrade to 5.0(1e) . If I recall correctly, there were some issues with upgrading if you were running a release from the 4.1 train earlier than 4.1(4). Additionally, the upgrade from 4.1 -> 5.0 includes a configuration conversion (due to differences between the software trains), which was prone to failure depending on the presence of certain configuration options.
Unless you absolutely need to keep the existing configuration, you would save yourself time and effort by simply re-imaging the sensor directly to the desired release. Modern (supported) releases would be either 7.0(5a)E4 or 6.2(3)E4.
Next, I'm reboot IDSM-2 module and receive:"000133: Sep 7 15:10:18.622 MSK/MDD: %HA_EM-6-LOG: Mandatory.go_bootup.tcl: GOLD EEM TCL policy for boot up diagnostic000134: Sep 7 15:10:18.290 MSK/MDD: %DIAG-SP-3-MAJOR: Module 4: Online Diagnostics detected a Major Error. Please use 'show diagnostic result ' to see test results.000135: Sep 7 15:10:18.294 MSK/MDD: %CONST_DIAG-SP-3-BOOTUP_TEST_FAIL: Module 4: TestPCLoopback failed on port(s) 3-4000136: Sep 7 15:10:19.170 MSK/MDD: %OIR-SP-3-LC_FAILURE: Module 4 has Major online diagnostic failure, Card will be reset to re-run diagnostic. Please check sup-bootflash diaginfo file for previous detailed diagnostic result.000137: Sep 7 15:10:19.170 MSK/MDD: %OIR-SP-3-PWRCYCLE: Card in module 4, is being power-cycled 'off (Diagnostic Failure)'000138: Sep 7 15:10:19.170 MSK/MDD: %C6KPWR-SP-4-DISABLED: power to module in slot 4 set off (Diagnostic Failure)"
I would try re-imaging the sensor once more using the IPS-IDSM2-K9-sys-1.1-a-7.0-5a-E4.bin.gz System Recovery Image file found here, following the procedure described here. If the module still fails to boot after that (still citing a Diagnostic Failure), try moving it to another slot in the chassis (if possible).
What color is the IDSM-2 Status LED (on front of module) when it is in this state? An RMA may be necessary to resolve this.

Upgrade IDSM2 from 4.1(5)S225 to 5.0 not going well

UPGRADING FROM 4.1 to 5.1. I know I have to got to 5.0 before I go to 5.1
I have tried to upgrade from 4.1 to 5.0 and am failing. I upgraded the Maintenance Partition to 2.1(2) as you can see from the show ver command output.
When I go to upgrade using the file IPS-K9-maj-5.0-1-S149.rpm.pkg i get the error messages to the console. they are included in the command line dump that follows..........
Cisco Systems Intrusion Detection Sensor, Version 4.1(5)S225
OS Version 2.4.18-5-phoenix
Platform: WS-SVC-IDSM2-BUN
Using 970657792 out of 1979682816 bytes of available memory (49% usage)
Using 5.1G out of 17G bytes of available disk space (32% usage)
MainApp 2005_Sep_01_21.30 (Release) 2005-09-01T21:30:35-0500 Running
AnalysisEngine 2005_Sep_01_21.30 (Release) 2005-09-01T21:30:35-0500 Running
Authentication 2005_Sep_01_21.30 (Release) 2005-09-01T21:30:35-0500 Running
Logger 2005_Sep_01_21.30 (Release) 2005-09-01T21:30:35-0500 Running
NetworkAccess 2005_Sep_01_21.30 (Release) 2005-09-01T21:30:35-0500 Running
TransactionSource 2005_Sep_01_21.30 (Release) 2005-09-01T21:30:35-0500 Running
WebServer 2005_Sep_01_21.30 (Release) 2005-09-01T21:30:35-0500 Running
CLI 2005_Aug_02_10.53 (Release) 2005-08-02T10:25:35-0500
Upgrade History:
IDS-sig-4.1-5-S225.rpm.pkg 14:40:27 UTC Thu Apr 20 2006
Maintenance Partition Version 2.1(2)
THESE ARE THE ERROS I AM GETTING DURING THE UPGRADE WHICH FAILES.
/signatures/[sig-id=11027,subsig-id=0]/engine/ -- the union does not have a member selected
/signatures/[sig-id=11211,subsig-id=1]/engine/ -- the union does not have a member selected
/signatures/[sig-id=11245,subsig-id=0]/engine/ -- the union does not have a member selected
/signatures/[sig-id=11245,subsig-id=1]/engine/ -- the union does not have a member selected
/signatures/[sig-id=11246,subsig-id=0]/engine/ -- the union does not have a member selected
/signatures/[sig-id=11247,subsig-id=0]/engine/ -- the union does not have a member selected
/signatures/[sig-id=11248,subsig-id=0]/engine/ -- the union does not have a member selected
/signatures/[sig-id=11249,subsig-id=0]/engine/ -- the union does not have a member selected
/signatures/[sig-id=11250,subsig-id=0]/engine/ -- the union does not have a member selected
/signatures/[sig-id=11251,subsig-id=0]/engine/ -- the union does not have a member selected
/signatures/[sig-id=12024,subsig-id=0]/engine/ -- the union does not have a member selected
/signatures/[sig-id=12025,subsig-id=0]/engine/ -- the union does not have a member selected
/signatures/[sig-id=12025,subsig-id=1]/engine/ -- the union does not have a member selected
/signatures/[sig-id=12026,subsig-id=0]/engine/ -- the union does not have a member selected
/signatures/[sig-id=12027,subsig-id=0]/engine/ -- the union does not have a member selected
Any help would be great!
gary price

The combination of tcp-reset on some UDP signatures in 4.x. was not invalidated. 5.0 is stricter and enforces this. It might be the best to disable reset for all signatures and then proceed with the upgrade.

25bw IPS monitor

Never again will I buy a HP monitor. 2 1/2 months after the warranty expires, a red line appears on the right side of the screen going straight down. Called up the tech support and they try to sell me the same one for "a reasonable price". Why would I buy the same monitor that malfunctions a couple months after the warranty is gone. No thank you. I've had my IPS monitor for over 2 years, not a dang thing wrong with it. Of course I upgraded to an ASUS IPS 27"...which I'm now forced to use because I refuse to use a defected monitor...but yeah. Way to go HP. You just lost yourself a customer.

I just sent you a private message. If you are not sure how to check your forum messages, this post has instructions.
Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
Dunidar
I work on behalf of HP
Find out a bit more about me by checking out my profile!
"Customers don’t expect you to be perfect. They do expect you to fix things when they go wrong." ~ Donald Porter

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.

SSM-20 Can not upgrade software on the sensor

Hi,
I am trying to upgrade a sensor on IPS-SSM-20 and have "errInUse-An Upgrade is already in progroess" error.
Can I do anything to fix that or my only way out is to reboot a module ?
P.S. Two modules are instaled on ASA-5520 - HA pair with multiple context.
Thanks,
Vlad

Hello,
I don't have option "debug module". Only debug option is to " debug module-boot"
This is SSM-20 on ASA 5520.
I forgot to mention that whole problem started when I acidentaly tried to upgrade sensor on a diferent module with a sign. version that already exist on the sensor. Erros was like"can not upgrade because version already exist on the sensor"
After that I was not able to "kill" that process.
Thanks,
Vladimir

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

Completely unsolvable: Cannot change screen brightness after I upgraded my ThinkPad's display.

I have a ThinkPad X240 which came with a 1366x768 TN panel, I hated it and so after a while I upgraded it to an IPS 1080p display. It works great and looks fantastic except it's stuck on max brightness inside of Windows 8.1. I cannot change the brightness inside of Intel HD graphics settings or inside of programs like Display Tuner. It doesn't work in Windows 10 either. The weird thing is, I can change the brightness just fine inside of Ubuntu. I've tried uninstalling the Intel HD drivers and reinstalling them, I've tried switching the drivers to the Microsoft Basic Display Adapter, and none has worked. I feel like I've installed every single version of Intel's Graphics Drivers and that I've done everything and it still won't change the bloody brightness. NOTHING has worked except to just use Ubuntu, which is not an adequate solution. I've even gone as far as to update my BIOS and reset it to defaults, I've even pulled the CMOS battery. I've tried the version of the Intel HD driver from Lenovo for the X240 and I've installed the monitor.ini files. I've also just learned that during the Windows Boot Logo, the FN keys WILL change the brightness, but as soon as Windows is done booting, it stops working. This, coupled with the fact that brightness control works in Ubuntu means that this must be something related to Windows right? Brightness control works in BIOS. I've even gone so far as to try and change the brightness through CMD using powercfg according to this post. http://superuser.com/questions/472081/can-i-force-a-greater-screen-brightness-from-windows-command-prompt I'm really starting to lose patience now as it has been like this for 3 weeks and I can't be using Ubuntu all of the time, I honestly do not know what to do, it seems like this problem is completely unsolvable. Edit: I even got so frustrated that I switched off the laptop, installed the old screen, booted up Windows, and the brightness worked. Then (I know this is a bad idea) WHILE IT WAS ON, I pulled the old display and put connected the new one. And lo and behold, the brightness **bleep**ING worked in windows on the new display.

try change drivers
Moderator comment: Post edited to conform with the Community Rules guidelines.
"No posts or signatures with intent to promote or advertise
Any way of personal blogs/ websites/ pages/ affiliated websites/ resources are not allowed."

Upgrade ASA-SSM-10 via FTP

Hi all,
I am trying to upgrade an ASA-SSM-10 running version 5.1 software.
I have set up an FTP server using Serv-u and can connect to it successfully.
When I attempt to upgrade using the following command, I get the error below.
sensor(config)# upgrade ftp://[email protected]//IPS/IPS-K9-6.0-3-E1.pkg
The filename IPS-K9-6.0-3-E1.pkg is not a valid upgrade file type.
Continue with upgrade? []: yes
Error: execUpgradeSoftware : Connect failed
I have tried 2 FTP servers and receive the same error I have tried 4 upgrade packages and receive the same error.
Does anyone have any advice on how to fix this issue.
Thank you
Greg

Your upgrade commands look correct. http://www.cisco.com/en/US/docs/security/ips/6.0/configuration/guide/cli/cliImage.html#wp1243115
I've had some problems with Serv-U in the past year or so. I had to switch to FileZilla to perform my last upgrade.
http://filezilla-project.org/
- Bob

Cisco IPS SSM 10 Sensor can't update signature file from ASA 5510

Cisco ASA 5510 IPS Firewall with ASA-SSM-10 Module. I am trying to do a manual update of the signature file and get the following error:
Error: execUpgradeSoftware : couldn't connect to host
I have confirmed that I can ping the ftp server successfully from the ASA and the command I am trying to use from the configure terminal of the module is:
upgrade ftp://[email protected]//IPS-sig-S813-req-E4.pkg
I have also tried via http and it does not work as well. Any thoughts?

to connect to ftp there should be username usually anonymous and password whitch can be any. check in ftp server
aip_ssm_card# copy ftp://192.168.15.12/JAF1308ARNJ_20131009032200919.lic license-key
User: anonymous
Password: *********
the username and/or the password are incorrect
aip_ssm_card# copy ftp://192.168.15.12/JAF1308ARNJ_20131009032200919.lic license-key
User: 123
Password: ***
File opening error
I made special user 123 on ftp server with password 123
aip_ssm_card# copy ftp://192.168.15.12/JAF1308ARNJ_20131009032200919.lic license-key
User: 123
Password: ***
aip_ssm_card#
and dont forget to rate post

CSM to update IPS AIP -SSM

Hi all,
I need some help. I am configuring my CSM 3.1 to apply update on my IPS AIP-SSM.
I went to the apply IPS Tab and choose to update from cisco.com. But it is always like processing for a long time.
I tried to enter my username and password for the sensors or the CCO account but still no improvement. Does anyone knows how to configure this. I tried reading the user guide there is no examples.
Thanks

The IPS-engine-E2-req-5.1-7.pkg Engine Update file is just to upgrade an existing 5.1(7)E1 sensor to 5.1(7)E2.
It only changes the "engine" features of the sensor that are necessary for installing signature updates requiring E2. It does not change other files on the sensor.
The IPS-K9-5.1-8-E2.pkg Service Pack file is for upgrading the entire image to the next service pack level as well as upgrading the "engine" features. So you get all of the latest bug fixes.
So which to use?
If you are running 5.1(7)E1 then you will eventually want to get to 5.1(8)E2. But the upgrade to 5.1(8)E2 WILL require a reboot and so if running in an inline mode it should only be done during a scheduled network downtime. For most networks this could be a week or even a month before the downtime can be scheduled to do this type of upgrade. So the IPS-engine-E2-5.1-7.pkg file is a short term solution to get you to the E2 level required for signature updates, until you can schedule the upgrade to 5.1(8)E2.
The IPS-engine... file will NOT reboot the sensor. It will temporarilly stop analysis and if Software ByPass is set to auto then traffic will be allowed to pass through the sensor unanalyzed while the engine update takes place. Because the traffic will continue to flow with Software ByPass most companies will allow an Engine update to be installed without having to schedule network downtime.
Of course, the above discussion was really only applicable when E2 was the latest Engine release. Now that E3 is out, the discussion really becomes how to get to E3.
There is Not an IPS-engine-E3-req-5.1-7.pkg engine update file.
So you must get to 5.1(8)E3 if you want to keep getting recent signature updates.
So then it just depends on your current IPS version.
If you are running 5.1(7)E2 or earlier version then you must schedule a downtime and install the IPS-K9-5.1-8-E3.pkg file in order to install the latest E3 required signature updates.
If you are running 5.1(8)E2 already, then you need to install the IPS-engine-E3-req-5.1-8.pkg file because the only thing needing to be upgraded is the Engine level to E3.
General Rules of Thumb:
Always ensure you are at the latest Service Pack level for the major/minor version train you are using. (5.1(8) in this case)
If you are running the latest Service Pack then you will be able to simply install an Engine Update when the next Engine Update comes out without having to schedule downtime.
If you are not at the latest Service Pack level then you will want to schedule a network downtime to do that upgrade within 60 days of the Service Pack being released.
If an Engine Update comes out before you get a chance to upgrade to the next Service Pack, then install the Engine Update for the prior Service Pack (that you should at least be at) as a temporary measure to keep getting signature updates. And schedule a Service Pack upgrade as soon as possible.
Why 60 days?
If a new Engine Update is released within 60 of a Service Pack release, then the Engine Update will be released for both the latest Service Pack AND the one prior. But if the new Engine Update is longer than 60 days after the latest Service Pack, then an Engine Update will be created only for the latest Service Pack and not for the prior. This is why E3 was only released for 5.1(8). E3 was released more than 60 days after 5.1(8) so there was not an E3 for the prior 5.1(7).
So you see that an Engine Update for a prior Service Pack should be considered a temporary measure until you can get the next Service Pack installed.
If you wait too long another Engine Update might come out, and you might be forced into an immediate network downtime to get to the latest Service Pack.
As for do you HAVE to install IPS-engine-E2-req-5.1-7.pkg before installing IPS-K9-5.1-8-E2.pkg (or more importantly IPS-K9-5.1-8-E3.pkg).
The answer is NO.
You can go directly from any 5.0 or 5.1 version directly to IPS-K9-5.1-8-E3.pkg.

T440P screen upgrade

Hi,
I currently have the stock 1600x900 TN panel in my T440p. I really want to upgrade to an IPS panel. Can I? Can I upgrade to a fullHD IPS panel?
I'd like to buy in Europe, because I don't want to pay customs and such tolls. Any suggestions?
Help appreciated!
Regards

Hi Galu,
Welcome to Lenovo Community!
As per the query we understood that you are looking for FHD Display panel for your ThinkPad T440p.
Here is the some of the FRU part number which is suitable for your system, you can lookout for same FRU to match with your system.
04X0592 - LGD 14.0"HD+ AG
04X0626 - LGD 14.0"FHD AG LGD LP140WF1-SPK1
04X5023 - Inolux 14.0"HD+ AG panel Inolux N140FGE-EA2
04X0394 - AUO 14.0"HD+ AG panel AUO B140RTN02.3
04X0436 - AUO 14.0"FHD AG panel AUO B140HAN01.2
Please click here to visit the link where you can get the list of support contact numbers, select the respective region and give a call.
Hope this helps.
Best regards,
Hemanth Kumar
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

Upgrading IDS4.0 to IPS

Similar Messages

Maybe you are looking for