IPS-sig-S342-req-E2 Borked ASDM

Unanswered Question
Jul 3rd, 2008
User Badges:


My IDSMs are running 6.1(1)E2 and today loaded S342. When I attempted to connect via ASDM-IDM launcher 1.5(31) I got the initial page then a "Error Connecting to Sensor. Failed to create sensor - <hostname>:443 Exiting IDM" After installing & reinstalling IDM then mucking with Java I finally downgraded one sensor to S341 and can now connect.

Now all I have to do is figure out why MARS isn't retrieving the events.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
GrumpyBear Thu, 07/03/2008 - 12:07
User Badges:

MARS retrieval failure was caused by the self-signed certificates expiring, coincidentally, today so I regenned them but had not added them to MARS via Test Discovery

GrumpyBear Mon, 07/14/2008 - 09:06
User Badges:

I just manually downloaded S344 from CCO and applied it to the sensor via the GUI and now things are behaving

GrumpyBear Tue, 07/29/2008 - 10:27
User Badges:

Once again S347 has borked the ASDM - Sigh - I'll have to open a TAC case on this.

GrumpyBear Thu, 07/31/2008 - 11:40
User Badges:

CSCso21050 - not fixed in 6.1 apparently.

Solution - ReImage to 6.0(5)E2 - sigh

TAC asked me to shutdown blade & unseat it for 30 minutes to let the HDD spin down


This Discussion