Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

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

2 REPLIES
Bronze

Re: upgrade IDSM2 from 4.1(5)S225 to 5.0 not going well

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.

New Member

Re: upgrade IDSM2 from 4.1(5)S225 to 5.0 not going well

done! Simply did application image for 5.1 worked great gprice

135
Views
0
Helpful
2
Replies
CreatePlease login to create content