HP white papers say that the Itanium rx2800 does not support HP-UX 11.23 / v2. My user really wants a rx2800 and has has to run 11.23 / v2. Can I load the v3 DC-OE on the rx2800.. then use the virtual machine program to somehow run v2 on this rx2800?
Any help would be appreciated on how to get this box running v2.
Thanks
Jesse
Cypress Tech
Hi everyone.
I need help with this Superdome.
A few days ago, a client reported an error of this machine, indicating that one of the partitions did not start.
I requested a SEL and he reported the following:
MPFSDIA64_1 - ESBCE.CP1.BH14 - DEH49266WJ
=========================================
(c) Copyright 2008 Hewlett-Packard Development Company, L.P.
Welcome to the
Management Processor
HP 9000 and Integrity Superdome Server SD64B
Supported firmware-updateable entity combination: Recipe 8.8e
MP MAIN MENU:
CO: Consoles
VFP: Virtual Front Panel
CM: Command Menu
CL: Console Logs
SL: Show Logs
FW: Firmware Update
HE: Help
X: Exit Connection
[SPi3] MP> sl
EVENT LOG MENU:
FPL: Forward Progress Log
SEL: System Event Log
LIVE: Live Events
MPEL: MP Event Log
CLR: Clear FPL and SEL
Q: Quit
[SPi3] MP:VW> sel
Welcome to the System Event Log (SEL) Viewer
The following SEL navigation commands are available:
F: Display first (oldest) block
L: Display last (newest) block
J: Jump to specified entry and display previous block
+: Display next (forward in time) block
-: Display previous (backward in time) block
<cr>: Repeat previous +/- command
<sp>: Repeat previous +/- command
?: Display help
<Ctrl-b>: Exit viewer
The following event format options are available:
K: Keyword
R: Raw hex
T: Text
The following event filter options are available:
A: Alert level
C: Cell
U: Unfiltered
MP:VWR (<cr>,<sp>,+,-,?,F,L,J,D,K,R,T,A,C,U,<Ctrl-b>) > t
Switching to text format.
MP:VWR (<cr>,<sp>,+,-,?,F,L,J,D,K,R,T,A,C,U,<Ctrl-b>) > a
Alert Level Filter:
0: Minor Forward Progress
1: Major Forward Progress
2: Informational
3: Warning
5: Critical
7: Fatal
Q: Quit
For example, selecting an alert level threshold of 3
selects all events with alert levels of 3 or higher.
Please select alert level threshold: 2
Switching to alert level 2 filter.
MP:VWR (<cr>,<sp>,+,-,?,F,L,J,D,K,R,T,A,C,U,<Ctrl-b>) >
Log Entry 94531: 01/03/2020 13:45:04
Alert level 3: Warning
Keyword: ARF_XBC_PORT_FE
An FE was found on an XBC port during an ARF traversability test.
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000c00e00000000
0x6380150980e033b1 0x0000c00e00000000
0x6b00150980e033b2 0x010000005e0f4560
Log Entry 94530: 01/03/2020 13:45:04
Alert level 2: Informational
Keyword: ARF_REROUTING_PORT_TO_CELL
Indicates that a bad route is being routed around
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0f00f00a00000000
0x43801c1580e033af 0x0f00f00a00000000
0x4b001c1580e033b0 0x010000005e0f4560
MP:VWR (<cr>,<sp>,+,-,?,F,L,J,D,K,R,T,A,C,U,<Ctrl-b>) > d
Log Entry 94499: 01/03/2020 13:45:03
Alert level 2: Informational
Keyword: ARF_FOUND_XBC_EDGE_LST_B_VTX2
fabric found a differencing graph edges while checking for route arounds
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000c00d00000000
0x438017b080e03371 0x0000c00d00000000
0x4b0017b080e03372 0x010000005e0f455f
Log Entry 94500: 01/03/2020 13:45:03
Alert level 2: Informational
Keyword: ARF_P1_DO_ROUTE_AROUNDS
Forward progress indicating fabric route arounds are to be performed
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000100000000003
0x43801a7980e03373 0x0000100000000003
0x4b001a7980e03374 0x010000005e0f455f
Log Entry 94501: 01/03/2020 13:45:03
Alert level 2: Informational
Keyword: ARF_REROUTING_PORT_TO_CELL
Indicates that a bad route is being routed around
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0c00f00900000000
0x43801c1580e03375 0x0c00f00900000000
0x4b001c1580e03376 0x010000005e0f455f
Log Entry 94502: 01/03/2020 13:45:03
Alert level 3: Warning
Keyword: ARF_XBC_PORT_FE
An FE was found on an XBC port during an ARF traversability test.
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000800d00000000
0x6380150980e03377 0x0000800d00000000
0x6b00150980e03378 0x010000005e0f455f
Log Entry 94503: 01/03/2020 13:45:03
Alert level 3: Warning
Keyword: ARF_XBC_PORT_FE
An FE was found on an XBC port during an ARF traversability test.
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000800d00000000
0x6380150980e03379 0x0000800d00000000
0x6b00150980e0337a 0x010000005e0f455f
Log Entry 94504: 01/03/2020 13:45:03
Alert level 3: Warning
Keyword: ARF_CSR_ROUTE_XBC_LINK_BAD
An XBC link was found to be unexpectedly not connected.
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000800900000000
0x6380150c80e0337b 0x0000800900000000
0x6b00150c80e0337c 0x010000005e0f455f
Log Entry 94505: 01/03/2020 13:45:03
Alert level 2: Informational
Keyword: ARF_REROUTING_PORT_TO_CELL
Indicates that a bad route is being routed around
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0d00f00900000000
0x43801c1580e0337d 0x0d00f00900000000
0x4b001c1580e0337e 0x010000005e0f455f
Log Entry 94506: 01/03/2020 13:45:03
Alert level 3: Warning
Keyword: ARF_XBC_PORT_FE
An FE was found on an XBC port during an ARF traversability test.
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000800d00000000
0x6380150980e0337f 0x0000800d00000000
0x6b00150980e03380 0x010000005e0f455f
Log Entry 94507: 01/03/2020 13:45:03
Alert level 2: Informational
Keyword: ARF_REROUTING_PORT_TO_CELL
Indicates that a bad route is being routed around
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0e00f00900000000
0x43801c1580e03381 0x0e00f00900000000
0x4b001c1580e03382 0x010000005e0f455f
Log Entry 94508: 01/03/2020 13:45:03
Alert level 3: Warning
Keyword: ARF_XBC_PORT_FE
An FE was found on an XBC port during an ARF traversability test.
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000c00d00000000
0x6380150980e03383 0x0000c00d00000000
0x6b00150980e03384 0x010000005e0f455f
Log Entry 94509: 01/03/2020 13:45:03
Alert level 2: Informational
Keyword: ARF_REROUTING_PORT_TO_CELL
Indicates that a bad route is being routed around
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0f00f00900000000
0x43801c1580e03385 0x0f00f00900000000
0x4b001c1580e03386 0x010000005e0f455f
Log Entry 94510: 01/03/2020 13:45:03
Alert level 3: Warning
Keyword: ARF_XBC_PORT_FE
An FE was found on an XBC port during an ARF traversability test.
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000c00d00000000
0x6380150980e03387 0x0000c00d00000000
0x6b00150980e03388 0x010000005e0f455f
Log Entry 94511: 01/03/2020 13:45:04
Alert level 3: Warning
Keyword: ARF_CHECK_XBC_FE_ERR_PRESENT
Fabric errors are present on a cell's link to the fabric.
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000d00e00000001
0x63801bf880e03389 0x0000d00e00000001
0x6b001bf880e0338a 0x010000005e0f4560
Log Entry 94512: 01/03/2020 13:45:04
Alert level 2: Informational
Keyword: ARF_DELETE_EDGE_PORT_NOT_FOUND
Fabric firmware experienced a problem while modifying its graph data structures.
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000d00e00000000
0x438019df80e0338b 0x0000d00e00000000
0x4b0019df80e0338c 0x010000005e0f4560
Log Entry 94513: 01/03/2020 13:45:04
Alert level 3: Warning
Keyword: ARF_CHECK_XBC_FE_ERR_PRESENT
Fabric errors are present on a cell's link to the fabric.
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000d00e00000001
0x63801bf880e0338d 0x0000d00e00000001
0x6b001bf880e0338e 0x010000005e0f4560
Log Entry 94514: 01/03/2020 13:45:04
Alert level 3: Warning
Keyword: ARF_CHECK_XBC_FE_ERR_PRESENT
Fabric errors are present on a cell's link to the fabric.
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000c00e00000001
0x63801bf880e0338f 0x0000c00e00000001
0x6b001bf880e03390 0x010000005e0f4560
Log Entry 94515: 01/03/2020 13:45:04
Alert level 2: Informational
Keyword: ARF_DELETE_EDGE_PORT_NOT_FOUND
Fabric firmware experienced a problem while modifying its graph data structures.
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000c00e00000000
0x438019df80e03391 0x0000c00e00000000
0x4b0019df80e03392 0x010000005e0f4560
Log Entry 94516: 01/03/2020 13:45:04
Alert level 3: Warning
Keyword: ARF_CHECK_XBC_FE_ERR_PRESENT
Fabric errors are present on a cell's link to the fabric.
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000c00e00000001
0x63801bf880e03393 0x0000c00e00000001
0x6b001bf880e03394 0x010000005e0f4560
Log Entry 94517: 01/03/2020 13:45:04
Alert level 2: Informational
Keyword: ARF_FOUND_XBC_EDGE_LST_B_VTX1
fabric found a differencing graph edges while checking for route arounds
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000c00a00000000
0x438017af80e03395 0x0000c00a00000000
0x4b0017af80e03396 0x010000005e0f4560
Log Entry 94518: 01/03/2020 13:45:04
Alert level 2: Informational
Keyword: ARF_FOUND_XBC_EDGE_LST_B_VTX2
fabric found a differencing graph edges while checking for route arounds
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000d00e00000000
0x438017b080e03397 0x0000d00e00000000
0x4b0017b080e03398 0x010000005e0f4560
Log Entry 94519: 01/03/2020 13:45:04
Alert level 2: Informational
Keyword: ARF_FOUND_XBC_EDGE_LST_B_VTX1
fabric found a differencing graph edges while checking for route arounds
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000d00a00000000
0x438017af80e03399 0x0000d00a00000000
0x4b0017af80e0339a 0x010000005e0f4560
Log Entry 94520: 01/03/2020 13:45:04
Alert level 2: Informational
Keyword: ARF_FOUND_XBC_EDGE_LST_B_VTX2
fabric found a differencing graph edges while checking for route arounds
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000c00e00000000
0x438017b080e0339b 0x0000c00e00000000
0x4b0017b080e0339c 0x010000005e0f4560
Log Entry 94521: 01/03/2020 13:45:04
Alert level 2: Informational
Keyword: ARF_P1_DO_ROUTE_AROUNDS
Forward progress indicating fabric route arounds are to be performed
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000200000000003
0x43801a7980e0339d 0x0000200000000003
0x4b001a7980e0339e 0x010000005e0f4560
Log Entry 94522: 01/03/2020 13:45:04
Alert level 2: Informational
Keyword: ARF_REROUTING_PORT_TO_CELL
Indicates that a bad route is being routed around
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0c00f00a00000000
0x43801c1580e0339f 0x0c00f00a00000000
0x4b001c1580e033a0 0x010000005e0f4560
Log Entry 94523: 01/03/2020 13:45:04
Alert level 3: Warning
Keyword: ARF_XBC_PORT_FE
An FE was found on an XBC port during an ARF traversability test.
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000d00e00000000
0x6380150980e033a1 0x0000d00e00000000
0x6b00150980e033a2 0x010000005e0f4560
Log Entry 94524: 01/03/2020 13:45:04
Alert level 2: Informational
Keyword: ARF_REROUTING_PORT_TO_CELL
Indicates that a bad route is being routed around
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0d00f00a00000000
0x43801c1580e033a3 0x0d00f00a00000000
0x4b001c1580e033a4 0x010000005e0f4560
Log Entry 94525: 01/03/2020 13:45:04
Alert level 3: Warning
Keyword: ARF_XBC_PORT_FE
An FE was found on an XBC port during an ARF traversability test.
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000d00e00000000
0x6380150980e033a5 0x0000d00e00000000
0x6b00150980e033a6 0x010000005e0f4560
Log Entry 94526: 01/03/2020 13:45:04
Alert level 3: Warning
Keyword: ARF_XBC_PORT_FE
An FE was found on an XBC port during an ARF traversability test.
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000c00e00000000
0x6380150980e033a7 0x0000c00e00000000
0x6b00150980e033a8 0x010000005e0f4560
Log Entry 94527: 01/03/2020 13:45:04
Alert level 3: Warning
Keyword: ARF_CSR_ROUTE_XBC_LINK_BAD
An XBC link was found to be unexpectedly not connected.
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000d00a00000000
0x6380150c80e033a9 0x0000d00a00000000
0x6b00150c80e033aa 0x010000005e0f4560
Log Entry 94528: 01/03/2020 13:45:04
Alert level 2: Informational
Keyword: ARF_REROUTING_PORT_TO_CELL
Indicates that a bad route is being routed around
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0e00f00a00000000
0x43801c1580e033ab 0x0e00f00a00000000
0x4b001c1580e033ac 0x010000005e0f4560
Log Entry 94529: 01/03/2020 13:45:04
Alert level 3: Warning
Keyword: ARF_XBC_PORT_FE
An FE was found on an XBC port during an ARF traversability test.
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000c00e00000000
0x6380150980e033ad 0x0000c00e00000000
0x6b00150980e033ae 0x010000005e0f4560
Log Entry 94530: 01/03/2020 13:45:04
Alert level 2: Informational
Keyword: ARF_REROUTING_PORT_TO_CELL
Indicates that a bad route is being routed around
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0f00f00a00000000
0x43801c1580e033af 0x0f00f00a00000000
0x4b001c1580e033b0 0x010000005e0f4560
Log Entry 94531: 01/03/2020 13:45:04
Alert level 3: Warning
Keyword: ARF_XBC_PORT_FE
An FE was found on an XBC port during an ARF traversability test.
Reporting Entity: System Firmware located in cabinet 1, slot 0, cpu 0
Actual Data: 0x0000c00e00000000
0x6380150980e033b1 0x0000c00e00000000
0x6b00150980e033b2 0x010000005e0f4560
*********************** End of log ***********************
MP:VWR (<cr>,<sp>,+,-,?,F,L,J,D,K,R,T,A,C,U,<Ctrl-b>) >
You can see that there are several alarms with WARNING, but I cannot identify if it is a hardware error or is of another type.
Please, all help will be appreciated.
Greetings.
What could be the cause of slow startup on an HP-UX server?
Dear,
Please share me plan/procedure to rollback to previous state from below command.
vgcfgrestore -n vg00 -l
With Best Regards,
Kauser
Dear All,
I want to reset iLO of specific balde ( blade# 2) in Superdome-2 server. I have run the bellow command but shown error.
SMDC-SD2-APP04> RESET ILO 2
Invalid Arguments
RESET BLADE { <bay number> }: Reset the blade bay by momentarily removing all
power.
Here server model is CB900s i4 . Mention that OS or server can not be rebooted because live system is running here.
Please assist on this if anyone has exact solution
Dear HPUX Experts,
We have rx6000 server and palnning to upgrade CPU on this box. We would like to know how many CPU slots are occupied, how many free slots availabe for upgrade.
Please assist how to find this infor from command line or thro any GUI?
Thank you.
Hi All,
I need help for collectiong the HBA card location from OS end. Here system is Superdome-2 32s, OS : HP-UX 11.31
Please assist on this issue .
Dear Concern,
Please share me procedure to enable user activity auditing in HP-UX 11.31 system without converting the system in trusted mode and make it persistent after reboot.
Thanks.
With Best Regards,
Kauser
Dear Concern,
Our system is running on HP-UX 11.31 system. System rebooted last two days few time and from below log, we have found below entries.
# cat /etc/shutdownlog
12:35 Thu Feb 6, 2020. Reboot: (by sdbmblv2!oracle)
12:08 Fri Feb 7, 2020. Reboot: (by sdbmblv2!oracle)
As per my understanding, these entries mean "oracle" user reboot the system twice. My query is can "oracle" user reboot the system as it is only a normal user not superuser priviledge?
With Best Regards,
Kauser
Hi All,
One blade in enclosure-1 is shown Management Processor: Error . Mention that this sytem is Superdome-2 and has 2 Enclosure and complex firmware version is 3.8.0
Now enclosure is functiong with live production. Here reported blade is under nPar partition.
Already I have run on OA at online by command : RESET iLO 2 but don't execute because firmware version is not supported.
So if we reset the blade by command RESET BLADE 2, we must down all os and nPar but we can't do that.
So if I reset OA , it oly reset OA ilO and blade iLO OR reboot OS including network ??
Select -->Enclosure -->Active Onboard Administrator -->Virtual Button --->>>reset
Please need opinoin from expert end.
We are trying to install nano on HP-UX 11.31 from the orting centre. It is a brand new Itanium server. After resolving the dependancies and missing libraries it appears to run but has a string of messages sent to the terminal where we are trying to run it. They look like the following
"Cannot remove alias 'kterm terminal emulator which supports graphics'
Name collision 'kterm terminal emulator which supports graphics' between
and kterm terminal emulator which supports graphics
Cannot remove alias 'kterm terminal emulator which supports graphics'
Name collision 'kterm terminal emulator which supports graphics' between
and kterm terminal emulator which supports graphics
Cannot remove alias 'kterm terminal emulator which supports graphics'
Name collision 'FM series MS-DOS V3.1 (TERM)' between
FM series MS-DOS V3.1 (TERM)
and FM series MS-DOS V3.1 (TERM)"
This prevents us from using it. Any ideas?
Hi,
one of our HP RX2660 server went down with system not booting, even no display, and SEL showed fatal error, as shown is last,
The problem isolated to motherboard (by testing the CPU in other system and it worked fine), We ordered new motherboard and need to install, But I don't have any experience before, so can anyone guide me the procedure? if any settings need to be backup from old board or the new board will work itself?
Log Entry 176: 27 Nov 2019 07:55:06
Alert Level 7: Fatal
Keyword: BOOT_NOT_DETECTED
No events were received from system firmware
Logged by: Baseboard Management Controller;
Sensor: Processor
Data1: FRB2/Hang in POST failure
0x205DDE2BDA020C90 FFFF036F00070300
I have found the new err log in ilo of BL890
Keyword: DMP_TO_AMP_COMM_LOST
the ilo peer to peer lan communication between dmp and amp was lost
Data: ASCII message - DMP5AMP8
A98020E040E10056 38504D4135504D44
Who can tell me what does this mean?
Hi,
I'm using 02 HPE Integrity rx2800 i2 Servers.
I access to server system heath via iLO3 in order see status of server components but there is not any information about hard dirves.
Does any one know the reason, and how can I see my HD?
Thanks.
Like my websit Online Remipoker
ir volume : primary ok secondary missing apres echange du disque idem
ioscan : un disque (autre path) en supplement
Raid Level : RAID 1
Volume sas address : 0x5605d6c74ffa0d2
Device Special File : /dev/rdsk/c5t4d0
Raid State : DEGRADED
Raid Status Flag : ENABLED
Raid Size : 139236
Rebuild Rate : 0.00 %
Rebuild Progress : 100.00 %
Participating Physical Drive(s) :
SAS Address Enc Bay Size(MB) Type State
0x5000c500838e0205 1 1 286102 PRIMARY ONLINE
0x0 0 0 286102 SECONDARY MISSING
I'm using 02 HPE Integrity rx2800 i2 Servers. Each of them is running two hard disks in RAID10 configuration.
I'd like to add one more disk to server, of course not into the exsisting RAID10.
I was succesful in inserting disk to first server, but It failed when doing with second server.
The server didn't boot at an early state. May be the RAID controller was stalling when scanning the bus for harddisks and preventing the host from booting. I guess so.
I didn't see any alarms.
I have tried with another disk, but the same status.
I did the following steps to insert new disk:
- Insert new disk to server.
- Shutdown C-LES
- Reboot server and enter EFI shell
- Use drvcfg command to enter RAID configuration tool. ( the command is 'drvcfg -s 9a 9c')
- Select the new unused harddisk from the menu driven interface and and add it to the RAID controller
- Boot the server as normal, but cannot boot.
Does anyone know the reason, and how can I troubleshoot?
Thanks.
Please join us for the Online Expert Day on June 16-17 , 2020. Our Experts will be Live for 24 hours.
More detailed information is available here
Our 3rd party vulnerability scanner found SSL v2 and SSL v3 in our HP-UX 11..31 systems and flagged them as medium vulnerability.
How do you diable SSL v2 or SSL v3 in HP-UX? Is there a way to check if they are even used?
Thanks!
Eclipse Keto FRANCE AVISOn the off chance that you need the ideal outcome from the pills of diet, at that point you need to peruse all the directions which are composed on the pack of the item. Prior to Eclipse Keto FR the specific 3 hours to each morning meal and supper, take it with water which is best since it is effortlessly broken up in the fluid as opposed to some other. You should maintain the safety measures of the pills else it is up to you as an abundance of everything is terrible. Click Here@>> https://www.buyonlinecare.com/eclipse-keto-fr/