cancel
Showing results for 
Search instead for 
Did you mean: 

VPAR hanging issue

kgpenator
Advisor

VPAR hanging issue

Hi all,

I am getting my server hanging intermediately when we are running any DIsk related commands and Vpar related commands.Also for any diagnostic commands .EMS are  sending alerts for every 30 min.Kindly what may be the problem?

 

OSTNAME: xyzabc
SYSTEM: ia64
MODEL: ia64 hp superdome server SD64B
SERIAL #: USE4619LJX
SYSTEM ID: 1984473796
PARTITION #: 0
VPAR NAME: xyzabc
CPU SPEED: 1598 MHz
TOTAL CPUS: 48 processor(s)
MEMORY: 43598 MB
HP-UX VERSION: B.11.23 64 Bit
USER LICENSE: unlimited-user license
LAST BOOT: Jul 31 14:12
UP TIME: 57 days, 20:14 hours
LAST PATCH: Jul 31 14:03
TRUSTED SYSTEM: Yes
VOLUME MANAGER: Logical Volume Manager (LVM)

5 REPLIES
Stephan.
Honored Contributor

Re: VPAR hanging issue

Did you at least read the EMS notification?

 

Disk at hardware path 9/0/2/1/0/4/0.0.0 : I/O request failed.    
Probable Cause / Recommended Action:

     The bus device reset may have occurred or the device has failed. The bus
     device reset could have occurred because the power was cycled or that the
     device is a part of an enclosure and a device in that enclosure was pulled
     out or put in, or that the interface card had a problem and it reset the
     bus. If these errors continue, there may be a problem with the device or
     the card.  
kgpenator
Advisor

Re: VPAR hanging issue

We are unable to access the console of the server also?What may be the cause?

Stephan.
Honored Contributor

Re: VPAR hanging issue

Your

Disk at hardware path 9/0/2/1/0/4/0.0.0 

may have a problem ...

 

Follow the instructions here: When Good Disks Go Bad: Dealing with Disk Failures Under LVM

kgpenator
Advisor

Re: VPAR hanging issue

We are unable to access OS  through MP console . Is this relative to that problem?

Here i am attaching the SYSlog.log also.Pls reply.

Thank you for your quick response

Stephan.
Honored Contributor

Re: VPAR hanging issue

Is the vPar still reachable aka OS up and running, can you login?

 

MP could be something complete different, I would not mix up the problems and go one by one which means start first with the disk.

 

Your syslog.log did not attach - I'm not sure about the list of allowed attachments but renaming it to .txt should work or zip it if it is bigger.