Buy or Renew
Buy or Renew
Duo Security forums now LIVE! Get answers to all your Duo Security questions. Learn more
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
472
Views
0
Helpful
4
Replies

IPS-sig-S342-req-E2 Borked ASDM

GrumpyBear
Level 1
Level 1

‎07-03-2008 11:56 AM - edited ‎03-10-2019 01:41 PM

Hello,

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.

Labels:
0 Helpful
4 Replies 4

GrumpyBear
Level 1
Level 1

‎07-03-2008 12:07 PM

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

0 Helpful

GrumpyBear
Level 1
Level 1

‎07-14-2008 09:06 AM

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

0 Helpful

GrumpyBear
Level 1
Level 1
In response to GrumpyBear

‎07-29-2008 10:27 AM

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

0 Helpful

GrumpyBear
Level 1
Level 1
In response to GrumpyBear

‎07-31-2008 11:40 AM

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

0 Helpful
Customers Also Viewed These Support Documents
Review Cisco Networking products for a $25 gift card