Upgrade to 5.1(5)-E1

Answered Question
Apr 27th, 2007
User Badges:

Anybody tried to upgrade to 5.1(5)-E1 yet. A real treat. Please let me know your experience.

Correct Answer by attmidsteam about 10 years 3 months ago

We pushed this update through the Ciscoworks VMS IDS MC console. We never apply updates directly via the sensor GUI or CLI.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
attmidsteam Fri, 04/27/2007 - 12:39
User Badges:
  • Silver, 250 points or more

No difference seen so far from 5.1(5) for stability (good or bad) however VMS was annoying (as usual) and we had to re-import about 25 sensors. This was because E1 applied to the sensors but VMS refused to update its DB and believed they were on plain 5.1(5). Note that on busy & slower sensors, E1 can take 10-15 minutes to apply.

hendetl Fri, 04/27/2007 - 12:50
User Badges:

Thank you for your response. Would you mind telling me if you performed the E1 upgrade through the CLI or GUI? We are failing through the GUI and have a TAC opened. Thanks

Correct Answer
attmidsteam Mon, 04/30/2007 - 04:03
User Badges:
  • Silver, 250 points or more

We pushed this update through the Ciscoworks VMS IDS MC console. We never apply updates directly via the sensor GUI or CLI.

hendetl Mon, 04/30/2007 - 04:18
User Badges:

Thanks again. We did the same and got the failure. TAC thinks we have hit a known bug. We'll see. Thanks for your info.

attmidsteam Mon, 04/30/2007 - 04:29
User Badges:
  • Silver, 250 points or more

If you have a bug ID, please post it so I can see if we were hitting the same thing. Thanks!

dfiorefms Mon, 04/30/2007 - 05:17
User Badges:

Howdy,


I applied it last week (Monday?) via the CLI. No problem at all. I always use the CLI for sig and service pak updates and never have a problem with it.


Hope this helps.

attmidsteam Mon, 04/30/2007 - 05:26
User Badges:
  • Silver, 250 points or more

The CLI is fine for one or two sensors but when you need to apply an update to 120+ sensors it is just not an option. The problem we were running into however is that the VMS DB was getting out of step with the sensor version causing heartache (since if there is a version mismatch, VMS will refuse to work further with the sensor). Having to take an extra couple of hours to go back and 'fix' 30+ sensors is lame.

dfiorefms Mon, 04/30/2007 - 06:07
User Badges:

Yes it is lame. I only have 2 to deal with. Has any one tried the newest version of CSM with the 5.1 E1 pak? Maybe this will overcome the limits of VMS...

john.stephens Mon, 04/30/2007 - 09:34
User Badges:

With the VMS problems, did you already confirm that your VMS server is running the correct service pack? It needs service pack 2 for the IPS MC 2.2. I remember reading somewhere about VMS having issues if it didn't have the right service pack. We are running service pack 2-8 and I'm not experiencing any issues. Just another thing to check on, if you haven't already.

attmidsteam Mon, 04/30/2007 - 09:41
User Badges:
  • Silver, 250 points or more

Yes, we've had SP2 for IDS MC 2.2 on for a couple of months now and it only helped a few of our issues. Lately we've been getting pushback on fixes for VMS and received the CSM upgrade song & dance. Cisco hasn't provided any information on a migration utility from VMS->CSM despite much prompting so we're in no hurry to go to CSM yet.

hoogen_82 Sun, 05/06/2007 - 01:20
User Badges:
  • Silver, 250 points or more

Anybody facing an issue of not being able to add the IPS sensor when updated to E1. I am unable to do it from my VMS as it always tell me that VMS is not able to recognize the version.


Thanx for any help offered.

-Hoogen

attmidsteam Sun, 05/06/2007 - 04:22
User Badges:
  • Silver, 250 points or more

Make sure you have the latest version of VMS, there as a known bug in an earlier version of VMS where VMS would not recognize the AV version statement in the sensor version line. We have a TAC case open right now due to VMS and the sensor reporting different things after we pushed E1 then s283, VMS reported 5.1(4)E1s283, while the sensors reported 5.1(5)E1s283. So make sure there are no version conflicts between the sensor and VMS as VMS balks with any minor changes. Hope this helps!

Actions

This Discussion