- This topic is empty.
-
Posts
-
First of all…..fantastic website with stacks of resources. Thanks Guys!!!!
We’ve deployed ~20 V10LE’s connecting via the inbuilt RDP connection to a Windows Server 2008 R2 terminal server. Wired network – 100Mps.
Due to a compatibility issue with the Avocent switch boxes we’re using at site, I’ve updated the firmware to 6.5.0_30f, and configured a global wnos.ini, this all went smoothly (thanks to the Configuration Generator).
A couple of days later users have reported that over half of the terminals were sitting on a “Trap: Protection Fault 0x………” error message first thing in the morning when users came in. I’m told the hex number varied.
Is there a guide on how to interpret/decipher these traps? Or could someone shed some light on what this might mean?
We do run another environment with over ~100 V10LE’s connecting through VMView with exactly the same firmware revision else where, and there have been no problems there.
Cheers
BG
A Trap error is similar to a BSOD under Windows.
There is no reference to interpret the hex codes.
You should contact Wyse directly and ask for the latest 6.5 code with is 6.5_047 AFAIK.
There are several fixes in there related to Trap errors.CG
Not a drama. I’ll put in a call to Wyse.
Thanks for the reply (and for the fantastic site).
Quick Update:
Wyse have provided (eventually) the _47 firmware. I’m going to test/deploy it on Monday and will advise if this corrects the issue. Struggling to find the release notes for the _47 firmware. The zip file they provided on the had the boot and the wnos file.
Getting good information out of Wyse is like pulling teeth.
Deployed the _47 firmware this morning…..I guess we’ll wait and see if the Protection Faults have been resolved.
- You must be logged in to reply to this topic.