cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
649
Views
2
Helpful
4
Replies

Pane is dead signal 7 error of ISE installation in Cisco SNS 3700

dil2
Level 1
Level 1

Hi we are installing ISE 3.3 on a SNS3715 server. i have connected to KVM console on the web browser by connecting to the dedicated management port. I have saved my ISO file in my laptop and created mapped virtual drive mKVM-Mapped DvD by selecting local ISO file in my laptop. selected option for ISE installation using keyboard and mouse. after 2 hours running the installation, I got "pane is dead signal 7" error message. anyone got this similar issue and a way to fix this please. 

4 Replies 4

Arne Bier
VIP
VIP

It's possible that the ISO is corrupted. Have run an MD5 checksum against it on your laptop?  On Windows you can do this in powershell

certutil -hashfile Cisco-ISE-3.3.0.430.SPA.x86_64.iso MD5

According to software.cisco.com it should be 4bd259c5fb63bb0e089e690be8817043

Hi Arne, yes. I did check this against the value we see in download portal. 

Arne Bier
VIP
VIP

That seems to be a Linux kickstart error message - just searching the web didn't find a conclusive answer - but in a situation like this, where the SNS server is a black box, there is no reason for a simple install NOT to work. Did you fiddle around in the BIOS or CIMC at all?  I'd open a Cisco TAC case.

davidgfriedman
Level 1
Level 1

We used to have this happen a lot when we had SNS-3695-K9 and SNS-3655-K9 units. When we opened Cisco TAC cases for it, I swear they told us it was something related to network timeouts specifically related to those models.  Since you're running SNS-3715-K9 (if I read your post correctly), then it isn't just a problem for 3655 models.  

I read you're using Web console. Have you tried:
a) switching to the java console, as their mount supposedly transfers data far faster than the web console?
b) using a pc or server closer (fewer hops away) from your SNS-3715-K9 appliance?  Ours was a data center away.  We tried a VM with a browser which was in the same data center and it worked a bit more reliably. 

FWIW, we still prefer using USBs we burned (and edited the files to fix the "cdrom" vs "hdXXXXX" load line.  The USBs could re-image in an hour then get to the setup login, whereas over the web console / java console it could take anywhere from 4-12+ hours.

Regards,
David