- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: IBM Shark - EMS
Disk Enclosures
1753792
Members
5816
Online
108799
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО04-11-2002 07:19 AM
4 REPLIES 4
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-11-2002 08:54 AM
тАО04-11-2002 08:54 AM
Re: IBM Shark - EMS
Illegal Request is a generic SCSI error that indicates that the disk (or array, in your case) didn't understand a message sent to it.
The usual cause is monitoring software for some other unit (such as VA7400, XP512, FC60) is running on your host, and it's trying to ask the Shark for status or something. The IBM is rejecting the request.
Look for something that runs at that time of day (in crontab) to try to isolate which utility is causing the error.
Otherwise, I wouldn't really worry about the error - it doesn't mean much.
My sympathies on having to use a Shark!
Good luck!
The usual cause is monitoring software for some other unit (such as VA7400, XP512, FC60) is running on your host, and it's trying to ask the Shark for status or something. The IBM is rejecting the request.
Look for something that runs at that time of day (in crontab) to try to isolate which utility is causing the error.
Otherwise, I wouldn't really worry about the error - it doesn't mean much.
My sympathies on having to use a Shark!
Good luck!
No matter where you go, there you are.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-15-2002 12:17 PM
тАО04-15-2002 12:17 PM
Re: IBM Shark - EMS
It's problibly better not to monitor the shark disks from EMS. (What happens if the machine can suddenly see ALL the disks? EMS will go bonkers trying to communicate.) It's problibly better to use the IBM ESS Expert to watch your disks. (No sense impacting the performance of your HP box...)
Hope it helps
John
Hope it helps
John
Spoon!!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-03-2002 04:43 AM
тАО05-03-2002 04:43 AM
Re: IBM Shark - EMS
Tim,
I have seen a similar problem. There have been some timing issues with the Shark, from what I understand.
I was seeing similar EMS errors on the same lun at the same time of day. I ended upswapping the primary and alternate paths for that lun and the problem vanished.
It's an easy enough change with low impact.
MP
I have seen a similar problem. There have been some timing issues with the Shark, from what I understand.
I was seeing similar EMS errors on the same lun at the same time of day. I ended upswapping the primary and alternate paths for that lun and the problem vanished.
It's an easy enough change with low impact.
MP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-06-2002 10:10 AM
тАО05-06-2002 10:10 AM
Solution
Tim,
EMS and ESS Sharks do not play together nicely. You can use to the following to disable monitoring of the Shark from EMS:
--------------------------------------------------------------------------------
Document Information Table
--------------------------------------------------------------------------------
PROBLEM
With EMS (Event Monitoring Service) activated, a disk is reporting an
error. It will be several days until this disk can be replaced.
How can the reporting of the error messages to the logs be stopped
until the disk is replaced?
CONFIGURATION
Operating System - HP-UX
Version - 11.11, 11.00, 10.20
Subsystem - EMS 3.20
STM (Support Tools Manager) Version A.22.00 (IPR0009) or
Newer
RESOLUTION
****************** DISABLE EMS BY HARDWARE INSTANCE ******************
Disable an EMS HW monitor for a single instance (enabled in IPR0009)
The startmon_client program reads the file:
/var/stm/data/tools/monitor/disabled_instances
The above file is read before the *.sapcfg file is read, and so there
is no startup of the monitor for the specific instance listed in the
disabled_instances file.
The disabled_instances file is a text file with each fully qualified
instance listed, one instance per line. In addition, wildcards can be
used in the instance names to specify more than more instance. For
example: /storage/events/disks/default/* could be used to specify
all the instances associated with the default disk resource names.
For those instances listed in the disabled_instances file, no monitoring
requests will show up in the list displayed by the monconfig "C)heck
monitoring" command.
NOTE: This does not mean that the monitor will stop polling
the device. It just means that any events will not be
forwarded to the log files, based on information in the
*.sapcfg files.
In order to use the disabled_instances file, the user must perform the
following:
1. Run monconfig K)ill monitoring.
2. With editor of your choice, Add/delete/modify instances at
/var/stm/data/tools/monitor/disabled_instances.
3. Run monconfig; select the "E)nable Monitoring" command.
4. Wait for monitoring to be re-enabled.
5. Do a C)heck monitors.
The resource class that was disabled should show up in the
list with no description of what to do with events. (ie.
There are no monitoring requests.)
NOTE: The PSM (Peripheral Status Monitor) associated with the
event monitor cannot be disabled via this technique. This
ONLY disables the event monitor.
,Gene
EMS and ESS Sharks do not play together nicely. You can use to the following to disable monitoring of the Shark from EMS:
--------------------------------------------------------------------------------
Document Information Table
--------------------------------------------------------------------------------
PROBLEM
With EMS (Event Monitoring Service) activated, a disk is reporting an
error. It will be several days until this disk can be replaced.
How can the reporting of the error messages to the logs be stopped
until the disk is replaced?
CONFIGURATION
Operating System - HP-UX
Version - 11.11, 11.00, 10.20
Subsystem - EMS 3.20
STM (Support Tools Manager) Version A.22.00 (IPR0009) or
Newer
RESOLUTION
****************** DISABLE EMS BY HARDWARE INSTANCE ******************
Disable an EMS HW monitor for a single instance (enabled in IPR0009)
The startmon_client program reads the file:
/var/stm/data/tools/monitor/disabled_instances
The above file is read before the *.sapcfg file is read, and so there
is no startup of the monitor for the specific instance listed in the
disabled_instances file.
The disabled_instances file is a text file with each fully qualified
instance listed, one instance per line. In addition, wildcards can be
used in the instance names to specify more than more instance. For
example: /storage/events/disks/default/* could be used to specify
all the instances associated with the default disk resource names.
For those instances listed in the disabled_instances file, no monitoring
requests will show up in the list displayed by the monconfig "C)heck
monitoring" command.
NOTE: This does not mean that the monitor will stop polling
the device. It just means that any events will not be
forwarded to the log files, based on information in the
*.sapcfg files.
In order to use the disabled_instances file, the user must perform the
following:
1. Run monconfig K)ill monitoring.
2. With editor of your choice, Add/delete/modify instances at
/var/stm/data/tools/monitor/disabled_instances.
3. Run monconfig; select the "E)nable Monitoring" command.
4. Wait for monitoring to be re-enabled.
5. Do a C)heck monitors.
The resource class that was disabled should show up in the
list with no description of what to do with events. (ie.
There are no monitoring requests.)
NOTE: The PSM (Peripheral Status Monitor) associated with the
event monitor cannot be disabled via this technique. This
ONLY disables the event monitor.
,Gene
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP