- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: VPAR hanging issue
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2011 02:31 AM
10-28-2011 02:31 AM
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)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2011 03:03 AM
10-28-2011 03:03 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2011 03:05 AM
10-28-2011 03:05 AM
Re: VPAR hanging issue
We are unable to access the console of the server also?What may be the cause?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2011 03:13 AM
10-28-2011 03:13 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2011 03:31 AM
10-28-2011 03:31 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2011 03:39 AM
10-28-2011 03:39 AM
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.