X4200 ILOM Firmware upgrade
Hello *,
after I upgraded the Firmware for the ILOM Systemboard to 1.1.1. The RemoteControl Redirection doesnt worked....
I have check this with JRE 5.0 update 10 firefox / Iexplorer and 2 different hosts.
The error message is:
Exception in thread "Thread-12" java.lang.ArrayIndexOutOfBoundsException: 1
at com.ami.redirection.keymap.KeyMap.loadKeymapIntoHash(KeyMap.java:328)
at com.ami.redirection.keymap.KeyMap.<init>(KeyMap.java:52)
at com.ami.redirection.USBKeyProcessor.<init>(USBKeyProcessor.java:28)
at com.ami.redirection.KeymouseRedir.<init>(KeymouseRedir.java:71)
at com.ami.redirection.RedirSession.startHIDRedir(RedirSession.java:178)
at com.ami.javarconsole.ui.HIDEventHandler.startKeyboardRedirection(HIDEventHandle r.java:161)
at com.ami.javarconsole.ui.HIDEventHandler.handleEvent(HIDEventHandler.java:42)
at com.ami.javarconsole.ui.SessionEventDispatcher.handleEvent(SessionEventDispatch er.java:250)
at com.ami.javarconsole.ui.SessionEventDispatcher.run(SessionEventDispatcher.java: 209)
at java.lang.Thread.run(Unknown Source)
The Version is:
SP Firmware Version1.1.1
SP Firmware Build Number15632
SP Firmware DateMon Jan 8 14:28:54 PST 2007
SP Filesystem Version0.1.14
I hope anybody can help me ...
Mfg
Marcel Werner
# 1
Hi,
now , I`ve the same problem :-( .
After the ILOM-update 1.1.1 the redirection doesn`t work .
Any ideas ?
Server : X4100 , Solaris 10
Host : Blade2000, Sol10 (11/06) , Mozilla 1.7 ,
The redirection was fine, befor the update .
Greetings
Message was edited by:
franknfurter
# 2
Ditto here with an x4100 using the 1.3 web release to upgrade to ILOM 1.1.1. Trying to start redirection seems to hang the web interface also.
# 3
X4100, same problem. after upgrading to 1.1.1. and then trying the remote console, webserver of ilom seems to hang. all that helps to get the webserver running again is to reset ilom by console.
after downgrading to 1.0.5 the remote console is working again, BUT: by upgrading ilom to 1.3 the serial number information of the machine got lost - and now I've at least 2 problems:
how can I get the update done with a working remote console
AND
how can I re-enter the serial number information so that it's displayed in ilom again?
# 4
Now it works !!!
I`ll forward a mail from a sunie :-) :
We found if we disconnected the gateway or set the gateway in sp to 0.0.0.0, the java console can start normally. So we guess the new sp sends data to gateway first, other than client's ip directly, even if they are in one subnet. If the gateway cannot forward the data from sp, it will keep waiting.
With a properly configure of SP network, the JavaRConsole cannot be launched.(with gateway connected in LAN)
1. make the gateway disconnected to the LAN, the JavaRConsole can start correctly.
3. Set SP's gateway to whatever an existed IP, which doesn't have function of forwarding data, JavaRConsole failed to launch.
4. Set SP's gateway to a non-existed IP, or set it to 0.0.0.0, JavaRConsole can start correctly.
We guess that our gateway which is our router doesn't have function of forwarding data, when the gateway is configured in SP, SP(JavaRConsole) will send data to gateway(?), not the brower end IP directly. Once the gateway is not in the LAN, SP will look for the destination IP directly, so the JavaRConsole can start normally.
Greetings
franknfurter
# 5
This is a known issue:
Customers who...
* upgrade ILOM firmware directly from sw1.0 (6464) to sw1.2 (12029) or later
* receive SFX4100/SFX4200 systems with sw1.2.1 (r12513) installed
* downgrade newer ILOM firmware to sw1.0 (6464)
...may experience issues displaying FRUID information.
This issue will be automatically corrected after upgrading to the next ILOM firmware release (sw1.3) due out in Q1CY07 (for those customers that do the SW 1.0 to SW 1.2.1 Upgrade). Do not downgrade newer firmware to sw1.0 (6464).
To avoid this problem, please upgrade systems with sw1.0 (6464) in two steps:
1. from sw1.0 to sw1.1, then
2. upgrading to sw1.2 or later
Automatic recovery: applying the SFX4100/SFX4200 sw1.3 ILOM firmware update (available Q1CY07) will automatically correct the issue for those customers that upgraded from SW 1.0 to SW 1.2.1. and did not do the intermediate step of going to 1.1 firstly. For customers that already have a system with 1.2.1 installed out of the box, Automatic Recovery is not an option.
Manual recovery: use the 'servicetool' command available in the 'sunservice' linux account provided with ILOM sw1.1 or later, to update the missing information (see below for detailed information).
Example of updating two specific FRU entries:
--fru_product_serial_number --fru_product_part_number
Log into the sunservice account on ILOM with sw1.1 or later:
Note that the sunservice account's password is the same as the root account.
ssh <ilom ip> -l sunservice
password:
--fru_product_serial_number --fru_product_part_number
Servicetool is going to update the mainboard FRU product serial number.
Do you want to continue (y|n)? y
When entering values, do not use quotes; If you require embedded quotes, escape them with three backslashes; e.g. \\\"
What is the new product serial number? 0539AMF008
The product serial number has been updated.
The new serial number is: "0539AMF008"
Servicetool is going to update the mainboard FRU product part number.
Do you want to continue (y|n)? y
When entering values, do not use quotes; If you require embedded quotes, escape them with three backslashes; e.g. \\\"
What is the new product part number? 602-2993-02
The product part number has been updated.
The new part number is: "602-2993-02"
Updating FRUs... done
# 6
> This is a known issue:
...
> This issue will be automatically corrected after
> upgrading to the next ILOM firmware release (sw1.3)
> due out in Q1CY07 (for those customers that do the SW
> 1.0 to SW 1.2.1 Upgrade). Do not downgrade newer
> firmware to sw1.0 (6464).
Huh? The issue we're discussing here was caused by sw1.3.
sw1.3 installs ILOM 1.1.1 which is when the problems start.
-David
# 7
>
> To avoid this problem, please upgrade systems with
> sw1.0 (6464) in two steps:
>
>1. from sw1.0 to sw1.1, then
> 2. upgrading to sw1.2 or later
>
thanks for this info. I have read through enough release notes by now to have found this myself but am still left with issues:
1 - Where do I download the firmware image and pre-flash script? Several docs say these downloads are at http://www.sun.com/servers/entry/x4100/downloads.jsp
On this page I do not see a link for a pre-flash script nor do I see a download for a 1.1 firmware. The downloads for X4100/X4100 are "Sun Fire X4100 and Sun Fire X4200 Servers Supplemental 1.3" and 1.2.1 and 1.2. There is no download for v1.1.
2 - It is very unclear what I need to upgrade and in what order to get from 1.0 (build 6464) to 1.1. Do I update only the ILOM? The mobo BIOS? the MSI BIOS and firmware? The docs are very scattered and unclear.
Any guidance would be appreaciated.
thanks, Jon
# 8
Tried the issue with that gateway-setting (like forwarded by franknfurter):
1) Yes, as lon as my client is in the same network as the ILOM and the ILOM's gateway-setting is 0.0.0.0 I can use remote console from my client.
2) But, WITH a router BETWEEN my client and the ILOM and the ILOM's gateway (Linux host with IPTABLES) correctly set to the routers (ILOM-side-)address, it fails.
my setup:
client 10.1.10.19/255.255.0.0
gateway 10.1.1.1/255.255.0.0
gateway(other side) 10.2.255.254
ilom 10.2.253.244/255.255.0.0
With that, ILOMs Webpages work, but after klicking that 'Launch Redirection' Button, it's over.
Now I put a Network Sniffer in ILOM's network and had to notize that the ILOM, when it comes to answer my client,
(OK) send packets correctly to the gateway's MAC address, BUT
(NOT OK?) in the IP header, the destination address is 169.254.10.0 !?!?
I compared this with the same session on an ILOM running an old Firmware and that address never shines up in the network capture.
I never used that address 169.254.10.0 in any setup. Looks like one of that auto-dhcp-addresses Windows sometimes makes use of. But again: I did not set it in, nor did I activate DHCP or something.
So what is ILOM/JavaRemoteConsole doing here?
3) Additionally, I did the same along with another gateway (Cisco ASA)
Again, the ILOM somewhere in the session tries to answer to that strange IP 169.254.10.1.
The ASA as gateway behaves little different than the Linux IPTABLES machine: It answers the ILOM's SYN Packet (aimed to 169.254.10.1) with a RST, ACK answer.
The ILOM again tries to SYN the 169.254.10.1, the ASA gives it an RST, ACK.
This happens 5 times and THEN, guess what:
The 169.254.10.1 no longer appears in the capture, ILOM talks as it should with my client through the ASA and that works fine.
Unfortunately I need to get it run through the Linux gateway, so my problem isn't solved anyway...
# 9
Just upgraded to the latest firmware to address issues with 3rd party ram and I'm now hitting up against this brick wall.Anyone got any response from sun as to why this is now borked?
# 10
"Anyone got any response from sun"
... not in these forums.They're for user-to-user discussions,
and are pointedly NOT a part of official techsupport from the company.
Find your closest support center
http://www.sun.com/secure/contact/
and contact the company, directly.
Use the privileges afforded by the system warranty and open a support case.
# 11
I opened a case on Monday. If I get any useful response, I will post it here.
# 12
SUN support now confirmed that this is a known issue.
Additionally, they told me it's happening only when the client is a Windows machine. It's working on clients running Solaris.
Anyway, they told me that they do work on a fix.
But what's unknown is the time that fix will be available.
Workarounds for now:
1) step back to older Firmware (but keep an eye on that serial number loss issue)
or
2) await the fix.
Regards,
Michael
# 13
I just had Sun support help me through some sticky issues that came up after upgrading to the 1.3 firmware on one of my X4200s. One thing that you might try, to start with, is to clear out whatever Java / Java Web Start caches you might have. But what solved my (slightly different) problem was to reset the service processor itself ("reset /SP", or just pull the plug on the whole machine). Apparently it was in some weird slightly-broken state after the update, and resetting the SP brought everything back to normal.
# 14
Hello *,
now the sunsupport told me a workaround.....
Thats not a feature that is a BUG :-)
Ok we have installed in all maschins(Linux Ubuntu/ SuSE / Debian) the locale de_DE.UTF-8 and on Windows de_DE.
The suni said me please switch to de_AT what that locale is Austria and maybe it works fine.
It seem so only the de_DE(I dont now I think java use this) is the problem.
The second topic:
The gateway.
I configured a gataway that doesnt exsits at access time --> not worked
I configured a gataway that has the same address like the server from I will connected > not worked
I configured a gateway that exists and is gateway > worked
I configured a gateway 0.0.0.0 --> worked
So thats was it ...
Mfg
Marcel
