Integrity Servers
cancel
Showing results for 
Search instead for 
Did you mean: 

RX5670 and add-on hardware

 
SOLVED
Go to solution
ItaniumBob
Advisor

RX5670 and add-on hardware

I've noticed the RX5670 even refused to boot (red fault light blinks) when some hardware is plugged in. For example, I have two USB mice, the first one causes it to not boot, the other one works fine.

Also, and more importantly, some storage adapters (like the LSI SAS3442X-R) causes the same problem -- it doesn't boot, it just sits with the fault light blinking. As soon as I take the device out it works.

I really need this SAS controller to work. There are Itanium drivers for it, and its one of two PCI-X SAS options with Itanium support on the market (the other is the 8x version of the one I have).

Why does the Itanium fail to even fully boot with this device installed? But more importantly, is there any way around it? Will something like a system firmware update fix it? I am pretty desperate here, any advice is greatly appreciated!

Thanks
11 REPLIES 11
Matti_Kurkela
Honored Contributor
Solution

Re: RX5670 and add-on hardware

Get the management processor error logs from the machine: it will tell you *why* the fault light is blinking.

For instructions on how to access the management processor, please see:
http://docs.hp.com/en/A6837-96001/ch04s02.html#aes-126-ptn

For more information about the management processor commands, please see:
http://docs.hp.com/en/5991-6006/index.html

If you use a PC with terminal emulator software to access the management processor, the terminal emulator software usually has an option to capture the received data into a file. Activate this option, then use the SL command of the management processor, select the error log with no filtering. If it allows a choice of different display modes, the Text mode is the most informative one. The other modes are useful only if you are sending the dump to HP: they have the tools to decode the more compact forms of the dump.

MK
MK
Jesse Dougherty
Honored Contributor

Re: RX5670 and add-on hardware

I don't think SAS is supported on the rx5670
ItaniumBob
Advisor

Re: RX5670 and add-on hardware

That doc is very useful, however I am having difficulty still.

So I am trying to access the MP via telent. I have all three Core IO cards in. The NIC for the OS is going into my switch and works great -- Win Svr 2003 has internet access. I also have the MP NIC connected to the same switch. Or am I required to connect directly to another remote machine NIC via crossover cable? Also, from a remote machine, how do i access the MP? I can start up telnet, but what is the IP address I connect to?

Thanks
rick jones
Honored Contributor

Re: RX5670 and add-on hardware

I have no idea if this might be part of the problem, but HP Integrity systems will check things like inrush current on PCI slots and if a card is misbehaving will power down that slot from firmware - at least on systems with support for PCI hotplug. I've also had occasion where cards can cause the system (in this case it was Integrity blades and a non-Integrity supported mezz card) to not even post - which could very well be the behaviour on rack-mount systems without hotplug support. I cannot recall if the rx5670 supported PCI hotplug or not.
there is no rest for the wicked yet the virtuous have no pillows
ItaniumBob
Advisor

Re: RX5670 and add-on hardware

Thanks, I really would like to get access to the MP so I can get the logs... That doc basically says to get the MAC address of the MP board, create an arp mapping for it, ping it so that the MP board is configured, and then telnet into it. However, this is not working for me.

To remove all possible problems, I plugged the MP NIC and my PC NIC into each other using a cross over cable (also tried a hub and a switch). I changed my PC NIC to a private LAN address, 192.168.1.1 for example. Added a static arp entry for something private and non-routable: 192.168.1.2. Pinged it, no response. Tried to telnet, no response.

The MP board is actually not the one shipped with the server. I had to buy it later, but even though, I tried the MAC address on the sticker on the back of the server, and on the MP board itself. Also the MP number is in the form of 123456-7890AB, however the arp command wants it in the format of 12-34-56-78-90-AB. In case endian was an issue, I tried lots of formats... 21-43-65-87-09-BA, 56-34-21-AB-90-78, etc.

Nothing works, I just can't get a response from the machine. I know the MP board works because:

1) The LAN light on the NIC connection is enabled and detected LAN speed.
2) There is a green LED which constantly blinks on the board inside the server.
3) Pressing the "TRANSFER OF CONTROL" button on the board inside the server reboots the machine. However, I was unable to get any reaction from the "RESET" button -- not sure there will be a visible reaction though?

So this is where I am at. I need to view server logs, and also would like to update the firmware. But I can't do anything because I can't seem to access the MP. Can somebody please give me some advice here?

Thanks
rick jones
Honored Contributor

Re: RX5670 and add-on hardware

There should be a good old fashioned serial port on the MP too :)

With your back-to-back setup you might run a packet sniffer on the PC and see what traffic if any comes from the MP LAN port upon initial power-up. I don't recall if those older MP's supported DHCP, or if they would do a gratuitous ARP on init but it is worth a look.
there is no rest for the wicked yet the virtuous have no pillows
ItaniumBob
Advisor

Re: RX5670 and add-on hardware

Thanks so much for the sniffing idea. I installed NetMon and went through the steps. Assigned my local IP to 192.168.1.1, and arp mapping of 12-34-56-78-90-AB to 192.168.1.2. When I pinged, I got this response:

ARP:Request, 10.0.3.250 asks for 192.168.1.2

For some reason the MP isn't changing it's IP address (for all I know this might be a bug with the older MP firmware). It is stuck at this IP address. Once I remapped the MAC address to that IP address I've been able to telnet, and ftp update the MP firmware until eventually I did a system firmware update. Woo thanks!

Anyway on to the original question. The hardware failure... the hardware I am most interested in getting working in the RX5670 is the LSI SAS3442X-R. This card works in a different x64 server just fine. Also I am successfully using the LSI LSI20320-R-B-F in the RX5670 without issue.

For the test I fully updated all firmwares (System, BMC, MP) and I removed all other cards in expansion slots. The only cards installed were the Core IO cards. From a cold boot, I get the below log, I let it loop once before I shutdown. It is a constant loop if I leave the machine running.

I've tried this card in every single PCI-X expansion slot. I have firmly seated it (multiple times). I have used other PCI-X devices just fine in the same slots, and as I said before, I've used the offending card in other machines.

If you can give any advice I would really appreciate it! Or if you know of a different PCI-X external SAS controller which works OK inside the RX5670 I would greatly appreciate it!

Thanks

BMC 2 0x204A395EB4020180 FFFF010304140300 Type-02 140301 1311489
17 Jun 2009 21:23:00
BMC 2 0x204A395EB9020190 FFFF027000120300 Type-02 127002 1208322
17 Jun 2009 21:23:05
BMC 2 0x204A395EB90201A0 FFFF0007110A0300 Type-02 0a0700 657152
17 Jun 2009 21:23:05
BMC 2 0x204A395EB90201B0 FFFF0007120A0300 Type-02 0a0700 657152
17 Jun 2009 21:23:05
BMC 2 0x204A395EB90201C0 FFFF0007130A0300 Type-02 0a0700 657152
17 Jun 2009 21:23:05
BMC 2 0x204A395EB90201D0 FFFF010943090300 Type-02 090901 592129
17 Jun 2009 21:23:05
BMC 2 0x204A395EBA0201E0 FFFF010944080300 Type-02 080901 526593
17 Jun 2009 21:23:06
BMC 2 0x204A395EBA0201F0 FFFF010945080300 Type-02 080901 526593
17 Jun 2009 21:23:06
BMC 2 0x204A395EBA020200 FFFF010946080300 Type-02 080901 526593
17 Jun 2009 21:23:06
BMC 2 0x204A395EBA020210 FFFF000B4F090300 Type-02 090b00 592640
17 Jun 2009 21:23:06
SFW 2 0xC14A395EBC020220 FFFF000A001D0300 Type-02 1d0a00 1903104
17 Jun 2009 21:23:08
SFW 0 1 0x5680006300E00230 0000000000000000 BOOT_START
17 Jun 2009 21:23:08
SFW 0 0 0x0000002000E00000 0000000000000000 BOOT_CPU_EARLY_CONFIG_START
SFW 2 0 0x0000002002E00000 0000000000000000 BOOT_CPU_EARLY_CONFIG_START
SFW 3 0 0x0000002003E00000 0000000000000000 BOOT_CPU_EARLY_CONFIG_START
BMC 2 0x204A395EBC020250 FFFF0006E8040300 Type-02 040600 263680
17 Jun 2009 21:23:08
SFW 1 0 0x0000002001E00000 0000000000000000 BOOT_CPU_EARLY_CONFIG_START
BMC 2 0x204A395EBC020260 FFFF0006E9040300 Type-02 040600 263680
17 Jun 2009 21:23:08
BMC 2 0x204A395EBC020270 FFFF0006EA040300 Type-02 040600 263680
17 Jun 2009 21:23:08
BMC 2 0x204A395EBC020280 FFFF0006EB040300 Type-02 040600 263680
17 Jun 2009 21:23:08
BMC 2 0x204A395EBC020290 FFFF0006EC040300 Type-02 040600 263680
17 Jun 2009 21:23:08
BMC 2 0x204A395EBC0202A0 FFFF0006ED040300 Type-02 040600 263680
17 Jun 2009 21:23:08
BMC 2 0x204A395EBD0202B0 FFFF0006EE040300 Type-02 040600 263680
17 Jun 2009 21:23:09
BMC 2 0x204A395EBD0202C0 FFFF0006EF040300 Type-02 040600 263680
17 Jun 2009 21:23:09
SFW 0 0 0x1600000E00E00000 00000000000F0000 BOOT_CELL_MONARCH_SEL_START
SFW 2 0 0x1600000E02E00000 00020000000F0000 BOOT_CELL_MONARCH_SEL_START
SFW 3 0 0x1600000E03E00000 00030000000F0000 BOOT_CELL_MONARCH_SEL_START
SFW 1 0 0x1600000E01E00000 00010000000F0000 BOOT_CELL_MONARCH_SEL_START
SFW 1 0 0x0300005D01E00000 0000000000000002 BOOT_SLAVE_RENDEZ_HANDLER_START
SFW 0 1 0x3600000C00E00000 0000000000000000 BOOT_CELL_MONARCH
SFW 2 0 0x0300005D02E00000 0000000000000002 BOOT_SLAVE_RENDEZ_HANDLER_START
SFW 0 1 0x3600026100E00000 0000000000000000 BOOT_CPU_PRESENT
SFW 3 0 0x0300005D03E00000 0000000000000002 BOOT_SLAVE_RENDEZ_HANDLER_START
SFW 1 1 0x3600026101E00000 0000000000000001 BOOT_CPU_PRESENT
SFW 2 1 0x3600026102E00000 0000000000000002 BOOT_CPU_PRESENT
SFW 3 1 0x3600026103E00000 0000000000000003 BOOT_CPU_PRESENT
SFW 0 0 0x0000000800E00000 0000000000000000 BOOT_CELL_CONFIG_START
SFW 0 0 0x0000024B00E00000 0000000000000000 BOOT_EARLY_PLATFORM_CHECK
SFW 0 0 0x0300000600E00000 0000000000000000 BOOT_BUS_CONFIG_VALUE
SFW 0 0 0x1600004400E00000 0100000000200400 BOOT_NEW_BUS_CONFIG_VALUE
BMC 2 0x204A395EC00202D0 FFFF027000120300 Type-02 127002 1208322
17 Jun 2009 21:23:12
SFW 2 0 0x0000002002E00000 0000000000000000 BOOT_CPU_EARLY_CONFIG_START
SFW 1 0 0x0000002001E00000 0000000000000000 BOOT_CPU_EARLY_CONFIG_START
SFW 3 0 0x0000002003E00000 0000000000000000 BOOT_CPU_EARLY_CONFIG_START
SFW 0 0 0x0000002000E00000 0000000000000000 BOOT_CPU_EARLY_CONFIG_START
SFW 2 0 0x1600000E02E00000 00020000000F0000 BOOT_CELL_MONARCH_SEL_START
SFW 1 0 0x1600000E01E00000 00010000000F0000 BOOT_CELL_MONARCH_SEL_START
SFW 3 0 0x1600000E03E00000 00030000000F0000 BOOT_CELL_MONARCH_SEL_START
SFW 0 0 0x1600000E00E00000 00000000000F0000 BOOT_CELL_MONARCH_SEL_START
SFW 0 1 0x3600000C00E00000 0000000000000000 BOOT_CELL_MONARCH
SFW 0 1 0x3600026100E00000 0000000000000000 BOOT_CPU_PRESENT
SFW 1 1 0x3600026101E00000 0000000000000001 BOOT_CPU_PRESENT
SFW 2 1 0x3600026102E00000 0000000000000002 BOOT_CPU_PRESENT
SFW 3 1 0x3600026103E00000 0000000000000003 BOOT_CPU_PRESENT
SFW 0 0 0x0000000800E00000 0000000000000000 BOOT_CELL_CONFIG_START
SFW 0 0 0x0000024B00E00000 0000000000000000 BOOT_EARLY_PLATFORM_CHECK
SFW 2 0 0x0300005D02E00000 0000000000000002 BOOT_SLAVE_RENDEZ_HANDLER_START
SFW 1 0 0x0300005D01E00000 0000000000000002 BOOT_SLAVE_RENDEZ_HANDLER_START
SFW 3 0 0x0300005D03E00000 0000000000000002 BOOT_SLAVE_RENDEZ_HANDLER_START
SFW 0 0 0x0300000600E00000 0100000000200400 BOOT_BUS_CONFIG_VALUE
SFW 0 0 0x0000005600E00000 0000000000000000 BOOT_SCR_TEST_START
SFW 0 0 0x0000024C00E00000 0000000000000000 BOOT_PLATFORM_CHECK
SFW 0 0 0x0000003E00E00000 0000000000000000 BOOT_LDB_INIT
SFW 0 0 0x1600001D00E00000 0000000000000000 BOOT_CPU_CONFIG
SFW 2 0 0x1600005E02E00000 000000000000021D BOOT_SLAVE_RENDEZ_INT_RECEIVED
SFW 2 0 0x1600001D02E00000 0000000000000002 BOOT_CPU_CONFIG
SFW 1 0 0x1600005E01E00000 000000000000021D BOOT_SLAVE_RENDEZ_INT_RECEIVED
SFW 3 0 0x1600005E03E00000 000000000000021D BOOT_SLAVE_RENDEZ_INT_RECEIVED
SFW 1 0 0x1600001D01E00000 0000000000000001 BOOT_CPU_CONFIG
SFW 3 0 0x1600001D03E00000 0000000000000003 BOOT_CPU_CONFIG
SFW 2 0 0x1600005F02E00000 0000000000000002 BOOT_SLAVE_RENDEZ_STAGE_1
BMC 2 0x204A395EC90202E0 FFFF0103FDC00300 Type-02 c00301 12583681
17 Jun 2009 21:23:21
SFW 1 0 0x1600005F01E00000 0000000000000001 BOOT_SLAVE_RENDEZ_STAGE_1
SFW 3 0 0x1600005F03E00000 0000000000000003 BOOT_SLAVE_RENDEZ_STAGE_1
SFW 0 0 0x160002AF00E00000 000000000000001F SETTING_PROC_TIMEOUT
SFW 0 0 0x0000010B00E00000 0000000000000000 PDH_MISC_REG_TEST_START
SFW 0 1 0x2000008100E00000 0000000000000000 IO_DISCOVERY_START
SFW 0 0 0x0400008600E00000 000000FFFF00FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008600E00000 000000FFFF01FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008600E00000 000000FFFF02FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008600E00000 000000FFFF03FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008600E00000 000000FFFF04FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008600E00000 000000FFFF05FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008600E00000 000000FFFF06FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008600E00000 000000FFFF07FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008700E00000 000000FFFF00FF83 IO_LBA_INIT
SFW 0 0 0x0400008700E00000 000000FFFF01FF83 IO_LBA_INIT
SFW 0 0 0x0400008700E00000 000000FFFF02FF83 IO_LBA_INIT
SFW 0 0 0x0400008700E00000 000000FFFF03FF83 IO_LBA_INIT
SFW 0 0 0x0400008700E00000 000000FFFF04FF83 IO_LBA_INIT
SFW 0 0 0x0400008700E00000 000000FFFF05FF83 IO_LBA_INIT
SFW 0 0 0x0400008700E00000 000000FFFF06FF83 IO_LBA_INIT
SFW 0 0 0x0400008700E00000 000000FFFF07FF83 IO_LBA_INIT
SFW 0 2 0x5680028500E002F0 0000000000000000 MC_INITIALIZED_RSE
17 Jun 2009 21:23:40
SFW *7 0xC14A395EDD020310 003FA17000130300 Type-02 137001 1273857
17 Jun 2009 21:23:41
SFW 0 *7 0xF680009800E00320 0000000000000000 MC_INITIATED
17 Jun 2009 21:23:41
SFW 0 2 0x568002A100E00340 28000000FFF21130 MC_PSP
17 Jun 2009 21:23:41
SFW 0 2 0x5680011500E00360 0000000000000000 UNCORRECTED_MC
17 Jun 2009 21:23:41
SFW 0 2 0x568002B000E00380 2009061700212341 MC_TIMESTAMP
17 Jun 2009 21:23:41
SFW 0 2 0x5680028A00E003A0 0000000000000000 MC_LOG_PROC
17 Jun 2009 21:23:41
SFW 0 2 0x5680028200E003C0 0000000000000000 MC_CACHE_CHECK
17 Jun 2009 21:23:42
SFW 0 2 0x5680028100E003E0 1080000003000141 MC_BUS_CHECK
17 Jun 2009 21:23:42
SFW 0 2 0x5680028E00E00400 00000000FED2604B MC_MOD_ERR_TARGET_ID
17 Jun 2009 21:23:42
SFW 0 2 0x5680028400E00420 00000000FFEC1B90 MC_IIP
17 Jun 2009 21:23:42
SFW 0 2 0x5680028700E00440 0000100000002018 MC_IPSR
17 Jun 2009 21:23:42
SFW 0 2 0x5680028900E00460 0000000000000000 MC_LOG_MEM
17 Jun 2009 21:23:42
SFW 0 2 0x5680028800E00480 0000000000000000 MC_LOG_IO
17 Jun 2009 21:23:43
SFW 0 2 0x568002A000E004A0 0000000000000000 MC_POST_PROCESS_PLAT
17 Jun 2009 21:23:45
SFW 0 2 0x5680029700E004C0 0000000000000060 MC_PCI_BUS_ID
17 Jun 2009 21:23:45
SFW 0 *3 0x7680010700E004E0 0000000000000000 OS_MCA_NOT_REGISTERED
17 Jun 2009 21:23:45
BMC 2 0x204A395EE1020500 FFFF027000120300 Type-02 127002 1208322
17 Jun 2009 21:23:45
SFW 2 0xC14A395EE3020510 FFFF000A001D0300 Type-02 1d0a00 1903104
17 Jun 2009 21:23:47
SFW 2 1 0x5680006302E00520 0000000000000000 BOOT_START
17 Jun 2009 21:23:48
SFW 2 0 0x0000002002E00000 0000000000000000 BOOT_CPU_EARLY_CONFIG_START
SFW 1 0 0x0000002001E00000 0000000000000000 BOOT_CPU_EARLY_CONFIG_START
SFW 3 0 0x0000002003E00000 0000000000000000 BOOT_CPU_EARLY_CONFIG_START
SFW 0 0 0x0000002000E00000 0000000000000000 BOOT_CPU_EARLY_CONFIG_START
SFW 2 0 0x1600000E02E00000 00020000000F0000 BOOT_CELL_MONARCH_SEL_START
SFW 1 0 0x1600000E01E00000 00010000000F0000 BOOT_CELL_MONARCH_SEL_START
SFW 3 0 0x1600000E03E00000 00030000000F0000 BOOT_CELL_MONARCH_SEL_START
SFW 0 0 0x1600000E00E00000 00000000000F0000 BOOT_CELL_MONARCH_SEL_START
SFW 0 1 0x3600000C00E00000 0000000000000000 BOOT_CELL_MONARCH
SFW 0 1 0x3600026100E00000 0000000000000000 BOOT_CPU_PRESENT
SFW 1 1 0x3600026101E00000 0000000000000001 BOOT_CPU_PRESENT
SFW 2 1 0x3600026102E00000 0000000000000002 BOOT_CPU_PRESENT
SFW 3 1 0x3600026103E00000 0000000000000003 BOOT_CPU_PRESENT
SFW 0 0 0x0000000800E00000 0000000000000000 BOOT_CELL_CONFIG_START
SFW 0 0 0x0000024B00E00000 0000000000000000 BOOT_EARLY_PLATFORM_CHECK
SFW 2 0 0x0300005D02E00000 0000000000000002 BOOT_SLAVE_RENDEZ_HANDLER_START
SFW 1 0 0x0300005D01E00000 0000000000000002 BOOT_SLAVE_RENDEZ_HANDLER_START
SFW 3 0 0x0300005D03E00000 0000000000000002 BOOT_SLAVE_RENDEZ_HANDLER_START
SFW 0 0 0x0300000600E00000 0100000000200400 BOOT_BUS_CONFIG_VALUE
SFW 0 0 0x0000005600E00000 0000000000000000 BOOT_SCR_TEST_START
SFW 0 0 0x0000024C00E00000 0000000000000000 BOOT_PLATFORM_CHECK
SFW 0 0 0x0000003E00E00000 0000000000000000 BOOT_LDB_INIT
SFW 0 0 0x1600001D00E00000 0000000000000000 BOOT_CPU_CONFIG
SFW 2 0 0x1600005E02E00000 000000000000021F BOOT_SLAVE_RENDEZ_INT_RECEIVED
SFW 1 0 0x1600005E01E00000 000000000000021F BOOT_SLAVE_RENDEZ_INT_RECEIVED
SFW 2 0 0x1600001D02E00000 0000000000000002 BOOT_CPU_CONFIG
SFW 1 0 0x1600001D01E00000 0000000000000001 BOOT_CPU_CONFIG
SFW 3 0 0x1600005E03E00000 000000000000021F BOOT_SLAVE_RENDEZ_INT_RECEIVED
SFW 3 0 0x1600001D03E00000 0000000000000003 BOOT_CPU_CONFIG
SFW 2 0 0x1600005F02E00000 0000000000000002 BOOT_SLAVE_RENDEZ_STAGE_1
SFW 1 0 0x1600005F01E00000 0000000000000001 BOOT_SLAVE_RENDEZ_STAGE_1
SFW 3 0 0x1600005F03E00000 0000000000000003 BOOT_SLAVE_RENDEZ_STAGE_1
SFW 0 0 0x160002AF00E00000 000000000000001F SETTING_PROC_TIMEOUT
SFW 0 0 0x0000010B00E00000 0000000000000000 PDH_MISC_REG_TEST_START
SFW 0 1 0x2000008100E00000 0000000000000000 IO_DISCOVERY_START
SFW 0 0 0x0400008600E00000 000000FFFF00FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008600E00000 000000FFFF01FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008600E00000 000000FFFF02FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008600E00000 000000FFFF03FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008600E00000 000000FFFF04FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008600E00000 000000FFFF05FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008600E00000 000000FFFF06FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008600E00000 000000FFFF07FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008700E00000 000000FFFF00FF83 IO_LBA_INIT
SFW 0 0 0x0400008700E00000 000000FFFF01FF83 IO_LBA_INIT
BMC 2 0x204A395EED020540 FFFF0103FDC00300 Type-02 c00301 12583681
17 Jun 2009 21:23:57
SFW 0 0 0x0400008700E00000 000000FFFF02FF83 IO_LBA_INIT
SFW 0 0 0x0400008700E00000 000000FFFF03FF83 IO_LBA_INIT
SFW 0 0 0x0400008700E00000 000000FFFF04FF83 IO_LBA_INIT
SFW 0 0 0x0400008700E00000 000000FFFF05FF83 IO_LBA_INIT
SFW 0 0 0x0400008700E00000 000000FFFF06FF83 IO_LBA_INIT
SFW 0 0 0x0400008700E00000 000000FFFF07FF83 IO_LBA_INIT
SFW 0 2 0x5680028500E00550 0000000000000000 MC_INITIALIZED_RSE
17 Jun 2009 21:24:15
SFW *7 0xC14A395F00020570 003FA17000130300 Type-02 137001 1273857
17 Jun 2009 21:24:16
SFW 0 *7 0xF680009800E00580 0000000000000000 MC_INITIATED
17 Jun 2009 21:24:16
SFW 0 2 0x568002A100E005A0 28000000FFF21130 MC_PSP
17 Jun 2009 21:24:16
SFW 0 2 0x5680011500E005C0 0000000000000000 UNCORRECTED_MC
17 Jun 2009 21:24:16
SFW 0 *3 0x7680010700E005E0 0000000000000000 OS_MCA_NOT_REGISTERED
17 Jun 2009 21:24:16
BMC 2 0x204A395F00020600 FFFF027000120300 Type-02 127002 1208322
17 Jun 2009 21:24:16
SFW 2 0xC14A395F02020610 FFFF000A001D0300 Type-02 1d0a00 1903104
17 Jun 2009 21:24:18
SFW 2 1 0x5680006302E00620 0000000000000000 BOOT_START
17 Jun 2009 21:24:18
SFW 2 0 0x0000002002E00000 0000000000000000 BOOT_CPU_EARLY_CONFIG_START
SFW 1 0 0x0000002001E00000 0000000000000000 BOOT_CPU_EARLY_CONFIG_START
SFW 0 0 0x0000002000E00000 0000000000000000 BOOT_CPU_EARLY_CONFIG_START
SFW 3 0 0x0000002003E00000 0000000000000000 BOOT_CPU_EARLY_CONFIG_START
SFW 2 0 0x1600000E02E00000 00020000000F0000 BOOT_CELL_MONARCH_SEL_START
SFW 1 0 0x1600000E01E00000 00010000000F0000 BOOT_CELL_MONARCH_SEL_START
SFW 0 0 0x1600000E00E00000 00000000000F0000 BOOT_CELL_MONARCH_SEL_START
SFW 3 0 0x1600000E03E00000 00030000000F0000 BOOT_CELL_MONARCH_SEL_START
SFW 3 0 0x0300005D03E00000 0000000000000002 BOOT_SLAVE_RENDEZ_HANDLER_START
SFW 2 0 0x0300005D02E00000 0000000000000002 BOOT_SLAVE_RENDEZ_HANDLER_START
SFW 1 0 0x0300005D01E00000 0000000000000002 BOOT_SLAVE_RENDEZ_HANDLER_START
SFW 0 1 0x3600000C00E00000 0000000000000000 BOOT_CELL_MONARCH
SFW 0 1 0x3600026100E00000 0000000000000000 BOOT_CPU_PRESENT
SFW 1 1 0x3600026101E00000 0000000000000001 BOOT_CPU_PRESENT
SFW 2 1 0x3600026102E00000 0000000000000002 BOOT_CPU_PRESENT
SFW 3 1 0x3600026103E00000 0000000000000003 BOOT_CPU_PRESENT
SFW 0 0 0x0000000800E00000 0000000000000000 BOOT_CELL_CONFIG_START
SFW 0 0 0x0000024B00E00000 0000000000000000 BOOT_EARLY_PLATFORM_CHECK
SFW 0 0 0x0300000600E00000 0100000000200400 BOOT_BUS_CONFIG_VALUE
SFW 0 0 0x0000005600E00000 0000000000000000 BOOT_SCR_TEST_START
SFW 0 0 0x0000024C00E00000 0000000000000000 BOOT_PLATFORM_CHECK
BMC 2 0x204A395F09020640 FFFF018304140300 Type-02 148301 1344257
17 Jun 2009 21:24:25
BMC 2 0x204A395F0B020650 FFFF000943090300 Type-02 090900 592128
17 Jun 2009 21:24:27
BMC 2 0x204A395F0B020660 FFFF000944080300 Type-02 080900 526592
17 Jun 2009 21:24:27
BMC 2 0x204A395F0B020670 FFFF000945080300 Type-02 080900 526592
17 Jun 2009 21:24:27
BMC 2 0x204A395F0B020680 FFFF000946080300 Type-02 080900 526592
17 Jun 2009 21:24:27
kris rombauts
Honored Contributor

Re: RX5670 and add-on hardware

seems that during the I/O discovery/initialization the machine experiences a MCA (hardware crash):

SFW 0 1 0x2000008100E00000 0000000000000000 IO_DISCOVERY_START
SFW 0 0 0x0400008600E00000 000000FFFF00FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008600E00000 000000FFFF01FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008600E00000 000000FFFF02FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008600E00000 000000FFFF03FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008600E00000 000000FFFF04FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008600E00000 000000FFFF05FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008600E00000 000000FFFF06FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008600E00000 000000FFFF07FF83 IO_LBA_DISCOVERED
SFW 0 0 0x0400008700E00000 000000FFFF00FF83 IO_LBA_INIT
SFW 0 0 0x0400008700E00000 000000FFFF01FF83 IO_LBA_INIT
SFW 0 0 0x0400008700E00000 000000FFFF02FF83 IO_LBA_INIT
SFW 0 0 0x0400008700E00000 000000FFFF03FF83 IO_LBA_INIT
SFW 0 0 0x0400008700E00000 000000FFFF04FF83 IO_LBA_INIT
SFW 0 0 0x0400008700E00000 000000FFFF05FF83 IO_LBA_INIT
SFW 0 0 0x0400008700E00000 000000FFFF06FF83 IO_LBA_INIT
SFW 0 0 0x0400008700E00000 000000FFFF07FF83 IO_LBA_INIT
SFW 0 2 0x5680028500E002F0 0000000000000000 MC_INITIALIZED_RSE
17 Jun 2009 21:23:40
SFW *7 0xC14A395EDD020310 003FA17000130300 Type-02 137001 1273857


So looks like systemfw does not communicate well with this card or vice versa. Given the RX5670 is quit old and only had support for SCSI adapters at the time and this card is rather newer (SAS) and never been a card that has been tested/supported on this system I'm afraid you're not going to get this working after the torough testing you already did to eliminate some other factors. It looks like there are indeed IA64 drivers available for that card but at systemfw level something isn't working well together it seems....


Kris
rick jones
Honored Contributor

Re: RX5670 and add-on hardware

I am unable to speak to the system logs - even when the rx5670 was a current system I was/am a SW guy not HW :) As for not changing its IP address, if the MP is "old enough" it does not have DHCP support and will have to have its IP set manually - from the main prompt one gets with a Ctrl-B, I would suspect "CM" and then "LC" (for Lan Config).

there is no rest for the wicked yet the virtuous have no pillows
ItaniumBob
Advisor

Re: RX5670 and add-on hardware

Such a shame. Was really hoping to avoid buying a new server...

I'd like to provide this information to HP in the form of a bug report. Hopefully they can fix it in the next firmware revision. What is the best way to do this?

For now, I got an rx2660 and am working on setting it up. Thanks for all the help!
kris rombauts
Honored Contributor

Re: RX5670 and add-on hardware

The RX5670 is since some years off the pricelist and typically there are no plans to develop newer f/w releases on those platforms especially not for adding support for more cards. It's unfortunate for your plan but at the time when this sever was introduced there wasn't any real implementation yet of SAS really like you see nowadays, it was nothing but parallell SCSI where that is now phased out and replaced by SAS (and cheaper SATA where acceptable).


Kris