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

RX2620 access MP via Serial Console?

 
SOLVED
Go to solution
boje
Regular Advisor

RX2620 access MP via Serial Console?

Hi!

I am trying to access the MP via Serial cable. But when i connect with Putty i can login as root, and root password. I should then use Ctrl+B to get the menu. But i only get the character ^B. Can someone help me?

Br
Patrik
22 REPLIES 22
Torsten.
Acclaimed Contributor

Re: RX2620 access MP via Serial Console?

You are using the console port on the black 1-to-3 cable?

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
boje
Regular Advisor

Re: RX2620 access MP via Serial Console?

No, i am using a HP serial cable to te serial port A. It is marked as "Console".
I do not have any management card in my machine. Unfortunately.

Br
Patrik
Torsten.
Acclaimed Contributor

Re: RX2620 access MP via Serial Console?

This was my guess ... the management card is what? The MP!

Without MP no MP access ...

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Torsten.
Acclaimed Contributor

Re: RX2620 access MP via Serial Console?

This was my guess ... the management card is what? The MP!

Without MP no MP access ...

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
boje
Regular Advisor

Re: RX2620 access MP via Serial Console?

Hi Torsten!

Im sorry, i do not know what i am looking for. What is it called the menu you can access and check hardware and such things? No management card no MP menu with CM menu?
The reason is that i need to check my power supplies. I am getting these messages by email about "Power redundancy lost". And i searched this forum for help, found some threads and is now trying to get some status from power supplies. The both LED´s on the power supplies is GREEN. And i have checked the cables. Both cables have power.

This is the message:
>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Tue Aug 5 14:42:41 2008

scar sent Event Monitor notification information:

/system/events/ia64_corehw/core_hw is >= 3.
Its current value is CRITICAL(5).



Event data from monitor:

Event Time..........: Tue Aug 5 14:42:41 2008
Severity............: CRITICAL
Monitor.............: ia64_corehw
Event #.............: 104011
System..............: scar

Summary:
Power Unit : Redundancy lost or not present.


Description of Error:

The number of Power supplies has gone from N+1 (redundant) to N
(non-redundant) if a Power supply was removed, or the number of Power
supplies is < N+1.

Probable Cause / Recommended Action:

The minimum number of power supplies required to power the unit is
currently installed and operating. There are no redundant I/O power
supplies available in case of failure. If redundancy is desired another
Power supply should be added.

For information on the sensor that generated this event, refer to FRU ID
in Event Details section.

Additional Event Data:
System IP Address...: 10.10.10.10
Event Id............: 0x48984ac100000004
Monitor Version.....: B.01.00
Event Class.........: System
Client Configuration File...........:
/var/stm/config/tools/monitor/default_ia64_corehw.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
None
Additional System Data:
System Model Number.............: ia64 hp server rx2620
EMS Version.....................: A.04.20
STM Version.....................: C.56.00
System Serial Number............: SERIAL
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/ia64_corehw.htm#104011

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v


Event Details :

Event Date .............: Tue Aug 5 14:42:20 2008
Sensor Number ..........: 0x4f
Sensor Type ............: Power Unit
Sensor Class ...........: Discrete (type 0Bh)
Sensor Reading/Offset...: 0x01 (Offset)
Event Type.............: Assertion
Entity ID ..............: 19
Generic Message.........:
Power Unit : Redundancy lost
Entity FRU Id Info......:
power unit / power domain (Sensor ID: Power Redundancy)



>---------- End Event Monitoring Service Event Notification ----------<

Br
Patrik

Torsten.
Acclaimed Contributor
Solution

Re: RX2620 access MP via Serial Console?

The problem is, the MP was only optional for tis server.

Let's try something different - from hp-ux run

# echo "sel dev all;info;wait;il"|cstm

and post the result.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
boje
Regular Advisor

Re: RX2620 access MP via Serial Console?

Hi!

Yes, i did not buy this server, but it was stupid to not buy management card. I think its a must have. Anyway, here is the results:

root@scar:/root: echo "sel dev all;info;wait;il"|cstm
Running Command File (/usr/sbin/stm/ui/config/.stmrc).

-- Information --
Support Tools Manager


Version C.56.00

Product Number B4708AA

(C) Copyright Hewlett Packard Co. 1995-2007
All Rights Reserved

Use of this program is subject to the licensing restrictions described
in "Help-->On Version". HP shall not be liable for any damages resulting
from misuse or unauthorized use of this program.

cstm>sel dev all;info;wait;il
-- Updating Map --
Updating Map...
-- Converting multiple raw log files to text. --
Preparing the Information Tool Log for each selected device...

.... scar : 10.10.10.10 ....

-- Information Tool Log for system on path system --

Log creation time: Tue Aug 5 16:56:13 2008

Hardware path: system


Product ID : ia64 hp server rx2620
Current Product Number : AB332AR
Original Product Number : N/A
System Firmware Revision : 03.17
BMC Revision : v03.48
System Serial Number: : SERIAL

System Software ID : ID



For additional information about the system and the CPUs, please run the
following command:

/usr/contrib/bin/machinfo



Field Replaceable Unit Identification (FRUID):

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for IPF_MEMORY on path memory --

Log creation time: Tue Aug 5 16:56:13 2008

Hardware path: memory


Basic Memory Description

Module Type: MEMORY
Page Size: 4096 Bytes
Total Physical Memory: N/A
Total Configured Memory: 24576 MB
Total Deconfigured Memory: N/A

Memory Board Inventory

DIMM Location Size(MB) DIMM Location Size(MB)
-------------------- -------- -------------------- --------
DIMM 0A 2048 DIMM 0B 2048
DIMM 1A 2048 DIMM 1B 2048
DIMM 2A 2048 DIMM 2B 2048
DIMM 3A 2048 DIMM 3B 2048
DIMM 4A 2048 DIMM 4B 2048
DIMM 5A 2048 DIMM 5B 2048

Total: 24576 (MB)

===========================================================================

Memory Error Log Summary

DIMM Location Error Address Error Type Page Count
---------------------- ---------------- ---------- ------------- -----
DIMM 2B 0x40d0305a80 Single-Bit 0x40d0305 1
DIMM 2B 0x4060d29480 Single-Bit 0x4060d29 1
DIMM 2B 0x406017d980 Single-Bit 0x406017d 1
DIMM 2B 0x3d0bfbb00 Single-Bit 0x3d0bfb 1
DIMM 2B 0x391b3f680 Single-Bit 0x391b3f 1
DIMM 2B 0x374d7e900 Single-Bit 0x374d7e 1
DIMM 2B 0x368734980 Single-Bit 0x368734 1
DIMM 2B 0x302fe6380 Single-Bit 0x302fe6 1
DIMM 2B 0x240924000 Single-Bit 0x240924 1
DIMM 2B 0x220351b80 Single-Bit 0x220351 1
DIMM 2B 0x20ff2c180 Single-Bit 0x20ff2c 1
DIMM 2B 0x10df7e200 Single-Bit 0x10df7e 1
DIMM 2B 0x107b7c380 Single-Bit 0x107b7c 1
DIMM 2B 0x537f200 Single-Bit 0x537f 1
DIMM 2B 0x4932000 Single-Bit 0x4932 1
DIMM 2B 0x4767880 Single-Bit 0x4767 1
DIMM 2B 0x4762d00 Single-Bit 0x4762 1
DIMM 2B 0x15099f980 Single-Bit 0x15099f 2

System start: Fri Aug 1 08:04:03 2008.
Last error detected: Fri Aug 1 08:04:03 2008.
Logging interval: 900 seconds.
18 address(es) with errors logged in memory error log.

The Logtool Utility provides full details about the memory error log.

Page Deallocation Table (PDT)

DIMM Location Error Address Error Type Page
---------------------- ---------------- ---------- -------------
DIMM 2B 0x15099f980 Single-Bit 0x15099f

PDT Entries Used: 1
PDT Entries Free: 99
PDT Total Size: 100


=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for Bus Adapter on path 0 --

Log creation time: Tue Aug 5 16:56:13 2008

Hardware path: 0


Product ID: Bus Adapter
Hardware Path: 0
PCI Vendor ID: 0x103c
PCI Device ID: 0x1229

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for PCI Bus Adapter on path 0/0 --

Log creation time: Tue Aug 5 16:56:13 2008

Hardware path: 0/0


Product ID: PCI Bus Adapter
Hardware Path: 0/0
PCI Vendor ID: 0x103c
PCI Device ID: 0x122e

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for IDE Bus Adapter on path 0/0/2/0 --

Log creation time: Tue Aug 5 16:56:13 2008

Hardware path: 0/0/2/0


Product ID: IDE Bus Adapter
Hardware Path: 0/0/2/0
PCI Vendor ID: 0x1095
PCI Device ID: 0x649

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for IDE Interface on path 0/0/2/0.0 --

Log creation time: Tue Aug 5 16:56:13 2008

Hardware path: 0/0/2/0.0


Product ID: IDE Interface
Hardware Path: 0/0/2/0.0
PCI Vendor ID: 0x1095
PCI Device ID: 0x649

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for Optical Storage Device on path 0/0/2/0.0.0.0 --

Log creation time: Tue Aug 5 16:56:13 2008

Hardware path: 0/0/2/0.0.0.0


Product Id: DV-28E-B Vendor: TEAC
Device Type: Optical Storage Device Firmware Rev: 2.2B
Device Qualifier: TEACDV-28E-B Logical Unit: 0
Serial Number: N/A
Capacity (M Byte): 4170.85
Block Size: 2048
Max Block Address: 2135476
Error Logs
Read Errors: N/A Buffer Overruns: N/A
Read Reverse Errors: N/A Buffer Underruns: N/A
Write Errors: N/A Non-Medium Errors: N/A
Verify Errors: N/A

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for IDE Interface on path 0/0/2/0.1 --

Log creation time: Tue Aug 5 16:56:13 2008

Hardware path: 0/0/2/0.1


Product ID: IDE Interface
Hardware Path: 0/0/2/0.1
PCI Vendor ID: 0x1095
PCI Device ID: 0x649

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for PCI Bus Adapter on path 0/1 --

Log creation time: Tue Aug 5 16:56:13 2008

Hardware path: 0/1


Product ID: PCI Bus Adapter
Hardware Path: 0/1
PCI Vendor ID: 0x103c
PCI Device ID: 0x122e

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for MPT SCSI Adapter on path 0/1/1/0 --

Log creation time: Tue Aug 5 16:56:13 2008

Hardware path: 0/1/1/0


Device File : /dev/mpt2
Device ID : 0x0030
Vendor ID : 0x1000
PCI Revision ID : 8
Subsystem ID : 0x1324
Subsystem Vendor ID : 0x103c
Firmware Version : 01.03.35.65 IO
Firmware Image Size : 39968 bytes
SCSI Initiator ID : 7
PCI Configuration Space Registers
Status = 0x0230 Command = 0x0157
Class Code = 0x10000 (SCSI Controller)
Cache Line Size = 0x20
Latency Timer = 0x40
Expansion ROM Address = 0x90100000


=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for SCSI Disk on path 0/1/1/0.0.0 --

Log creation time: Tue Aug 5 16:56:13 2008

Hardware path: 0/1/1/0.0.0


Product Id: MAX3073NC Vendor: HP 73.4G
Device Type: SCSI Disk Firmware Rev: HPC1
Device Qualifier: HP73.4GMAX3073NC Logical Unit: 0
Serial Number: X1016219 0615
Capacity (M Byte): 70007.20
Block Size: 512
Max Block Address: 143374737
Smart Enabled: TRUE
Error Logs
Read Errors: 0 Buffer Overruns: N/A
Read Reverse Errors: N/A Buffer Underruns: N/A
Write Errors: 0 Non-Medium Errors: 52
Verify Errors: 0

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for SCSI Disk on path 0/1/1/0.1.0 --

Log creation time: Tue Aug 5 16:56:13 2008

Hardware path: 0/1/1/0.1.0


Product Id: MAX3073NC Vendor: HP 73.4G
Device Type: SCSI Disk Firmware Rev: HPC1
Device Qualifier: HP73.4GMAX3073NC Logical Unit: 0
Serial Number: X1016570 0615
Capacity (M Byte): 70007.20
Block Size: 512
Max Block Address: 143374737
Smart Enabled: TRUE
Error Logs
Read Errors: 0 Buffer Overruns: N/A
Read Reverse Errors: N/A Buffer Underruns: N/A
Write Errors: 0 Non-Medium Errors: 52
Verify Errors: 0

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for MPT SCSI Adapter on path 0/1/1/1 --

Log creation time: Tue Aug 5 16:56:13 2008

Hardware path: 0/1/1/1


Device File : /dev/mpt3
Device ID : 0x0030
Vendor ID : 0x1000
PCI Revision ID : 8
Subsystem ID : 0x1324
Subsystem Vendor ID : 0x103c
Firmware Version : 01.03.35.65 IO
Firmware Image Size : 39968 bytes
SCSI Initiator ID : 7
PCI Configuration Space Registers
Status = 0x0230 Command = 0x0157
Class Code = 0x10000 (SCSI Controller)
Cache Line Size = 0x20
Latency Timer = 0x40
Expansion ROM Address = 0x90000000


=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for PCI 1000Base-T LAN Adapter on path 0/1/2/0 --

Log creation time: Tue Aug 5 16:56:14 2008

Hardware path: 0/1/2/0


Product ID: HP PCI-X 1000Base-T Dual-port Built-in
Device ID: 0x1079
Revision ID: 0x0003
Vendor ID: 0x8086 ( Intel Corporation )
Class Code: 0x020000 (Reserved)
Base Class: 0x0002 ( Network Controller )
Sub-Class/Interface: 0x00/0x00 ( Ethernet )
Device Status: 0x0230
Bit 5: 66 MHz Capable
Bit 9-10: DEVSEL timing 01 - medium
Subsystem Vendor ID: 0x103c
Subsystem ID: 0x12cd

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for PCI 1000Base-T LAN Adapter on path 0/1/2/1 --

Log creation time: Tue Aug 5 16:56:14 2008

Hardware path: 0/1/2/1


Product ID: HP PCI-X 1000Base-T Dual-port Built-in
Device ID: 0x1079
Revision ID: 0x0003
Vendor ID: 0x8086 ( Intel Corporation )
Class Code: 0x020000 (Reserved)
Base Class: 0x0002 ( Network Controller )
Sub-Class/Interface: 0x00/0x00 ( Ethernet )
Device Status: 0x0230
Bit 5: 66 MHz Capable
Bit 9-10: DEVSEL timing 01 - medium
Subsystem Vendor ID: 0x103c
Subsystem ID: 0x12cd

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for PCI Bus Adapter on path 0/2 --

Log creation time: Tue Aug 5 16:56:13 2008

Hardware path: 0/2


Product ID: PCI Bus Adapter
Hardware Path: 0/2
PCI Vendor ID: 0x103c
PCI Device ID: 0x122e

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for Fibre Channel Interface on path 0/2/1/0 --

Log creation time: Tue Aug 5 16:56:14 2008

Hardware path: 0/2/1/0


Product ID: Fibre Channel Interface
Hardware Path: 0/2/1/0
Module Type: Bus Adapter
Vendor ID: 0x103c
PCI Device ID: 0x1029
PCI Subsystem Vendor ID: 0x103c
PCI Subsystem ID: 0x128c
Topology: Direct Fabric Attach (N_Port to F_Port)
Channel N_PORT_ID: 0x10900
N_Port Port World Wide Name: 50060B00001160BE
N_Port Node World Wide Name: 50060B00001160BF
Tachyon TL/TS Major Revision:2
Tachyon TL/TS Minor Revision:3
Memory Address Base: 0x98040000
ROM Alternate Addr Base: 0x98020000
Lower I/O Address Base: 0x3100
Upper I/O Address Base: 0x3000

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for PCI Bus Adapter on path 0/3 --

Log creation time: Tue Aug 5 16:56:14 2008

Hardware path: 0/3


Product ID: PCI Bus Adapter
Hardware Path: 0/3
PCI Vendor ID: 0x103c
PCI Device ID: 0x122e

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for Fibre Channel Interface on path 0/3/1/0 --

Log creation time: Tue Aug 5 16:56:14 2008

Hardware path: 0/3/1/0


Product ID: Fibre Channel Interface
Hardware Path: 0/3/1/0
Module Type: Bus Adapter
Vendor ID: 0x103c
PCI Device ID: 0x1029
PCI Subsystem Vendor ID: 0x103c
PCI Subsystem ID: 0x128c
Topology: Direct Fabric Attach (N_Port to F_Port)
Channel N_PORT_ID: 0x10900
N_Port Port World Wide Name: 50060B0000111B9C
N_Port Node World Wide Name: 50060B0000111B9D
Tachyon TL/TS Major Revision:2
Tachyon TL/TS Minor Revision:2
Memory Address Base: 0xb0040000
ROM Alternate Addr Base: 0xb0020000
Lower I/O Address Base: 0x6100
Upper I/O Address Base: 0x6000

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for SCSI Tape on path 0/3/1/0.1.29.255.0.0.0 --

Log creation time: Tue Aug 5 16:56:14 2008

Hardware path: 0/3/1/0.1.29.255.0.0.0


Device Qualifier: HPUltrium
Product ID: Ultrium 1-SCSI Hardware Path:
0/3/1/0.1.29.255.0.0.0
Device Type: SCSI Tape Logical Unit Number: 0
Vendor: HP Product Rev Level: E38W
Firmware Revision: 007.047 Tape Load Count: 0
Correctable Errors: 0 Uncorrectable Errors: 0
Mfg Date Code: N/A Servo Revision: H/W.REV
Serial Number: HU76C00024
Compression Status: Enabled Compression Ratio:
[instant] N/A
[average] 1.0 : 1
Capacity [M Byte]: 0
Drive Status: Good

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for SCSI Tape on path 0/3/1/0.1.29.255.0.0.1 --

Log creation time: Tue Aug 5 16:56:14 2008

Hardware path: 0/3/1/0.1.29.255.0.0.1


Device Qualifier: HPUltrium
Product ID: Ultrium 1-SCSI Hardware Path:
0/3/1/0.1.29.255.0.0.1
Device Type: SCSI Tape Logical Unit Number: 1
Vendor: HP Product Rev Level: E38W
Firmware Revision: 007.047 Tape Load Count: 0
Correctable Errors: 0 Uncorrectable Errors: 0
Mfg Date Code: N/A Servo Revision: H/W.REV
Serial Number: HUB6D048JK
Compression Status: Enabled Compression Ratio:
[instant] N/A
[average] 1.0 : 1
Capacity [M Byte]: 0
Drive Status: Good

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for SCSI Tape on path 0/3/1/0.1.30.255.0.0.0 --

Log creation time: Tue Aug 5 16:56:14 2008

Hardware path: 0/3/1/0.1.30.255.0.0.0


Device Qualifier: HPUltrium
Product ID: Ultrium 1-SCSI Hardware Path:
0/3/1/0.1.30.255.0.0.0
Device Type: SCSI Tape Logical Unit Number: 0
Vendor: HP Product Rev Level: E38W
Firmware Revision: 007.047 Tape Load Count: 0
Correctable Errors: 0 Uncorrectable Errors: 0
Mfg Date Code: N/A Servo Revision: H/W.REV
Serial Number: HU72L12100
Compression Status: Enabled Compression Ratio:
[instant] N/A
[average] 1.0 : 1
Capacity [M Byte]: 0
Drive Status: Good

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for SCSI Tape on path 0/3/1/0.1.30.255.0.0.2 --

Log creation time: Tue Aug 5 16:56:14 2008

Hardware path: 0/3/1/0.1.30.255.0.0.2


Device Qualifier: HPUltrium
Product ID: Ultrium 1-SCSI Hardware Path:
0/3/1/0.1.30.255.0.0.2
Device Type: SCSI Tape Logical Unit Number: 2
Vendor: HP Product Rev Level: E38W
Firmware Revision: 007.047 Tape Load Count: 0
Correctable Errors: 0 Uncorrectable Errors: 0
Mfg Date Code: N/A Servo Revision: H/W.REV
Serial Number: HUB7H0136X
Compression Status: Enabled Compression Ratio:
[instant] N/A
[average] 1.0 : 1
Capacity [M Byte]: 0
Drive Status: Good

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for PCI Bus Adapter on path 0/4 --

Log creation time: Tue Aug 5 16:56:14 2008

Hardware path: 0/4


Product ID: PCI Bus Adapter
Hardware Path: 0/4
PCI Vendor ID: 0x103c
PCI Device ID: 0x122e

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for PCI Gigabit Ethernet Link on path 0/4/1/0 --

Log creation time: Tue Aug 5 16:56:14 2008

Hardware path: 0/4/1/0


Product ID: HP A6825-60101 PCI 1000Base-T Adapter
Device ID: 0x1645
Revision ID: 0x0015
Vendor ID: 0x14e4 ( Broadcom Corporation )
Class Code: 0x020000 (Reserved)
Base Class: 0x0002 ( Network Controller )
Sub-Class/Interface: 0x00/0x00 ( Ethernet )
Device Status: 0x02b0
Bit 5: 66 MHz Capable
Bit 7: Fast Back-to-Back Capable
Bit 9-10: DEVSEL timing 01 - medium
Subsystem Vendor ID: 0x103c
Subsystem ID: 0x128a

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for PCI Bus Adapter on path 0/5 --

Log creation time: Tue Aug 5 16:56:14 2008

Hardware path: 0/5


Product ID: PCI Bus Adapter
Hardware Path: 0/5
PCI Vendor ID: 0x103c
PCI Device ID: 0x122e

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for IPMI Controller on path 250/0 --

Log creation time: Tue Aug 5 16:56:14 2008

Hardware path: 250/0


Product ID: IPMI Controller
Hardware Path: 250/0
PCI Vendor ID: 0x4950
PCI Device ID: 0x4930

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for RS-232 Interface on path 250/1 --

Log creation time: Tue Aug 5 16:56:14 2008

Hardware path: 250/1


Product ID: RS-232 Interface
Hardware Path: 250/1
PCI Vendor ID: 0x504e
PCI Device ID: 0x5030

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for RS-232 Interface on path 250/2 --

Log creation time: Tue Aug 5 16:56:14 2008

Hardware path: 250/2


Product ID: RS-232 Interface
Hardware Path: 250/2
PCI Vendor ID: 0x504e
PCI Device ID: 0x5030

=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=-+-=

-- Information Tool Log for ACPI Device on path 250/3 --

Log creation time: Tue Aug 5 16:56:14 2008

Hardware path: 250/3


Product ID: ACPI Device
Hardware Path: 250/3
PCI Vendor ID: 0x4143
PCI Device ID: 0x5049
-- Information Tool Log for each selected device --
View - To View the file.
Print - To Print the file.
SaveAs - To Save the file.
Enter Done, Help, Print, SaveAs, or View: [Done] #.
root@scar:/root:
Torsten.
Acclaimed Contributor

Re: RX2620 access MP via Serial Console?

Not really useful. ;-(

Now try this from your serial connection:

press "ESC" followed by "(" and "return".

I only did this from the EFI shell so far ...
but should also work with running OS - just be carful and don't reset the system by accident ;-)

You will get a prompt - type "se" now:

cli>se

Press ESC ) to close this session.



Example:

fs0:\> (
cli>help
CLI Commands:
C [] - Change Password
CON - Display Console selection
FPL - Read Forward Progress Log
H - Help (this text)
I - Send any IPMI message
req fmt: rsSA netfnlun chk1 rqSWID rqSeq cmd [data] chk2
resp fmt: rqSWID netfnlun chk3 rsSa rqSeqrsLun cmd ccode [data] chk4
INFO - Display BMC FW Revision
IPMI - Send any IPMI message
req fmt: netfnlun cmd [data]
resp fmt: ccode [data]
LOC [0,1] - Locator LED Control
P [0,1] - Power Control
Q - Quit/Logout
RS [s] - Reset System [and switch to sys console]
SD - Read SDR Repository
SE - Read System Event Log
TOC [s] - Send an INIT/TOC [and switch to sys console]

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   

Re: RX2620 access MP via Serial Console?

Hi Boje,

If you check the power supply physically from the front panel and make sure the power LED is remained GREEN. Then it might not power supply issue.

Try to read the link below: (it's for 11.23 OE)

http://www12.itrc.hp.com/service/patch/patchDetail.do?admit=109447627+1217985843259+28353475&patchid=PHSS_37623

From the sentences 8 & 10, it did mentioned after update your OnlineDiag it will solve your current power supply issue.

8) SR QXCR1000592036
On all non-cellular IPMI based machines
the reminder events for power supply is
not getting generated by the
ia64_corehw monitor.

10)SR QXCR1000592627
On all non-cellular IPMI based machines
the ia64_corehw monitor when making the
GET_SENSOR_READING IPMI call on
sensor 0xCF is returning a reading of
0x02. This is resulting in generating
reminder event #104011(redundancy in
power), even though there is no problem
in the power units. Hence the monitor
should ignore the sensor 0xCF when
recheck of the sensor happens.


You hardly check the power supply status without MP. Through stm is another way to view through ps status but not all model will list the ps status out.


Hope it will help you. Thanks
boje
Regular Advisor

Re: RX2620 access MP via Serial Console?

First reply to Torsten: I do not which to reset my system :D
Can i access any power supply information from the CLI menu?

This is the problem. When i receive the message about "Redundancy lost", i go down to the cellar and check the sever. On the server there is 4 LED´s, the number 4 LED is RED. And system in blinking AMBER. But if i wait a moment it will turn GREEN again. I will check next time if the LED on power supplies changes color also.

Br
Patrik
Torsten.
Acclaimed Contributor

Re: RX2620 access MP via Serial Console?

You will get more information from the system event logs (cli).

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
rick jones
Honored Contributor

Re: RX2620 access MP via Serial Console?

Somewhere on docs.hp.com should be the users manuals for the rx2620, and those should describe how to administer the system and get logs and whatnot with just the motherboard serial ports and no MP.

WRT the on again off again reports of power redundancy lost, perhaps a power supply is "marginal" or perhaps a cable is _just_ a little loose.

I'm not sure if MP's for the rx2620 are still on the HP CPL, but I suspect that if they are not, you could find one second-hand. It is something one can install in the field. I've done a few on rx1600's before.
there is no rest for the wicked yet the virtuous have no pillows
Torsten.
Acclaimed Contributor

Re: RX2620 access MP via Serial Console?

You can also inspect the power supply LEDs (look behind the front bezel).

The upper means AC present, the lower means power supply is on.

But, IIRC if a CPU fan fails the system may disable a power supply to ensure cooling - this could be another reason.

Better to check the logs ...

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Torsten.
Acclaimed Contributor

Re: RX2620 access MP via Serial Console?

About the CLI:

http://docs.hp.com/en/AD117-9003A/ch05s06.html

The diag LEDs are showing the status too, see (scroll down):

http://docs.hp.com/en/AD117-9003A/ch05s05.html

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
boje
Regular Advisor

Re: RX2620 access MP via Serial Console?

Thx for all replies.
For starters, i will try to acccess CLI from the SERIAL A port again. Using Esc + (
or Esc + Shift + 8
Should i login with root first or try access CLI first? When i connect the cable i get prompt for login directly when pressing return. If i do not manage to access CLI i must call HP support and ask for help with this issue. According to LED it is some problem with CPU?
I will assign points to all of you helpful guys.
Br Patrik
Torsten.
Acclaimed Contributor

Re: RX2620 access MP via Serial Console?

"According to LED it is some problem with CPU?"

What is the status of the all the diag LEDs?
(off/green/red)

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
boje
Regular Advisor

Re: RX2620 access MP via Serial Console?

Sorry, here is the status of the LED´s on the front of server:
OFF OFF GREEN RED System flashing: AMBER

This is the logs from CLI, i managed to access from serial cable now:

cli>sl e
# Sev Generator/Sensor Description Event ID Data, Timestamp
---- - ---------------- ------------ ----------- --------------------------
0010 - Pwr Spply 2 Ctrl Enabled 45-08:09:01 2008-08-06 00:11:27
0020 - Power Redundancy Regained 4F-09:0B:00 2008-08-06 00:11:27
0030 - CPU0 Fan OK EC-0A:07:00 2008-08-06 00:11:28
0040 - Pwr Spply 2 Ctrl Disabled 45-08:09:00 2008-08-06 00:15:36
0050 - Power Redundancy Lost 4F-09:0B:01 2008-08-06 00:15:36
0060 - CPU0 Fan Fail (crit) EC-0A:07:02 2008-08-06 00:15:37
0070 - Pwr Spply 2 Ctrl Enabled 45-08:09:01 2008-08-06 00:19:04
0080 - CPU0 Fan OK EC-0A:07:00 2008-08-06 00:19:04
0090 - Power Redundancy Regained 4F-09:0B:00 2008-08-06 00:19:05
00A0 - Pwr Spply 2 Ctrl Disabled 45-08:09:00 2008-08-06 00:23:45
00B0 - CPU0 Fan Fail (crit) EC-0A:07:02 2008-08-06 00:23:45
00C0 - Power Redundancy Lost 4F-09:0B:01 2008-08-06 00:23:45
00D0 - Pwr Spply 2 Ctrl Enabled 45-08:09:01 2008-08-06 01:34:18
00E0 - CPU0 Fan OK EC-0A:07:00 2008-08-06 01:34:19
00F0 - Power Redundancy Regained 4F-09:0B:00 2008-08-06 01:34:19
0100 - SEL Time Set Set FD-C0:03:01 2008-08-06 06:06:47
0110 - Pwr Spply 2 Ctrl Disabled 45-08:09:00 2008-08-06 12:46:34
0120 - CPU0 Fan Fail (crit) EC-0A:07:02 2008-08-06 12:46:34
0130 - Power Redundancy Lost 4F-09:0B:01 2008-08-06 12:46:35
0140 - Pwr Spply 2 Ctrl Enabled 45-08:09:01 2008-08-06 13:14:53
0150 - CPU0 Fan OK EC-0A:07:00 2008-08-06 13:14:54
0160 - Power Redundancy Regained 4F-09:0B:00 2008-08-06 13:14:54
0170 - Pwr Spply 2 Ctrl Disabled 45-08:09:00 2008-08-06 13:26:31
0180 - CPU0 Fan Fail (crit) EC-0A:07:02 2008-08-06 13:26:32
0190 - Power Redundancy Lost 4F-09:0B:01 2008-08-06 13:26:32
01A0 - Pwr Spply 2 Ctrl Enabled 45-08:09:01 2008-08-06 13:27:51
01B0 - CPU0 Fan OK EC-0A:07:00 2008-08-06 13:27:52
01C0 - Power Redundancy Regained 4F-09:0B:00 2008-08-06 13:27:52
01D0 - SEL Time Set Set FD-C0:03:01 2008-08-06 14:06:49
01E0 - Pwr Spply 2 Ctrl Disabled 45-08:09:00 2008-08-06 17:24:13
01F0 - CPU0 Fan Fail (crit) EC-0A:07:02 2008-08-06 17:24:14
0200 - Power Redundancy Lost 4F-09:0B:01 2008-08-06 17:24:14
0210 - Pwr Spply 2 Ctrl Enabled 45-08:09:01 2008-08-06 18:02:41
0220 - Power Redundancy Regained 4F-09:0B:00 2008-08-06 18:02:42
0230 - CPU0 Fan OK EC-0A:07:00 2008-08-06 18:02:43
0240 - SEL Time Set Set FD-C0:03:01 2008-08-06 22:06:49
0250 - Pwr Spply 2 Ctrl Disabled 45-08:09:00 2008-08-06 23:08:48
0260 - CPU0 Fan Fail (crit) EC-0A:07:02 2008-08-06 23:08:49
0270 - Power Redundancy Lost 4F-09:0B:01 2008-08-06 23:08:49
0280 - Pwr Spply 2 Ctrl Enabled 45-08:09:01 2008-08-06 23:09:04
0290 - CPU0 Fan OK EC-0A:07:00 2008-08-06 23:09:05
02A0 - Power Redundancy Regained 4F-09:0B:00 2008-08-06 23:09:05
02B0 - Pwr Spply 2 Ctrl Disabled 45-08:09:00 2008-08-06 23:09:36
02C0 - CPU0 Fan Fail (crit) EC-0A:07:02 2008-08-06 23:09:37
02D0 - Power Redundancy Lost 4F-09:0B:01 2008-08-06 23:09:37
02E0 - Pwr Spply 2 Ctrl Enabled 45-08:09:01 2008-08-06 23:10:00
02F0 - CPU0 Fan OK EC-0A:07:00 2008-08-06 23:10:01
0300 - Power Redundancy Regained 4F-09:0B:00 2008-08-06 23:10:01
0310 - Pwr Spply 2 Ctrl Disabled 45-08:09:00 2008-08-07 02:36:09
0320 - CPU0 Fan Fail (crit) EC-0A:07:02 2008-08-07 02:36:10
0330 - Power Redundancy Lost 4F-09:0B:01 2008-08-07 02:36:10
0340 - Pwr Spply 2 Ctrl Enabled 45-08:09:01 2008-08-07 02:37:21
0350 - CPU0 Fan OK EC-0A:07:00 2008-08-07 02:37:22
0360 - Power Redundancy Regained 4F-09:0B:00 2008-08-07 02:37:22
0370 - SEL Time Set Set FD-C0:03:01 2008-08-07 06:06:50
0380 - Pwr Spply 2 Ctrl Disabled 45-08:09:00 2008-08-07 06:50:58
0390 - CPU0 Fan Fail (crit) EC-0A:07:02 2008-08-07 06:50:58
03A0 - Power Redundancy Lost 4F-09:0B:01 2008-08-07 06:50:58
cli>



Br
Patrik
boje
Regular Advisor

Re: RX2620 access MP via Serial Console?

Maybe easier if attached logs..

Br Patrik
Torsten.
Acclaimed Contributor

Re: RX2620 access MP via Serial Console?

The LED status means:

any any any red - FAN failed

this is confirmed by your logs:

CPU0 Fan Fail (crit)
Power Redundancy Lost
CPU0 Fan OK
Power Redundancy Regained
...

This is not a power problem, but a FAN problem. The power supply is disabled due to the failed fan.


Replace the fan and you are fine ...


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Torsten.
Acclaimed Contributor

Re: RX2620 access MP via Serial Console?

You will see a lot of FANs in your system.

LED status

any-any-green-red means CPU fan 0

This is the fan directly mounted on the CPU, you will need a new cpu module, because this is only 1 part.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
boje
Regular Advisor

Re: RX2620 access MP via Serial Console?

Yes thats what i thought.
I need to contact HP for a new fan. If i understand you correctly i will get a new fan and CPU mounted together.

Br Patrik
boje
Regular Advisor

Re: RX2620 access MP via Serial Console?

Hi again!

I have now replaced one fan, service did not know if it was the right fan replaced. But i will check logs now for more errors. If so i will report to HP again. Thank you for all replies. Managed to access console CLI trough Serial cable.

Br
Patrik