- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- AUTOCONFIGURE problem
Operating System - OpenVMS
1748089
Members
4922
Online
108758
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
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
тАО07-29-2010 02:06 AM
тАО07-29-2010 02:06 AM
AUTOCONFIGURE problem
Hi admins,
I'm using OpenVMS V8.3-1H1 on Integrity servers. I'm using SAN disk on them. I make some snapshots on daily basis for backups. To refresh disk configuration I'm running commands:
$ mc sysman io scsi
$ mc sysman io a
Sometimes it happens (with no cause) that "io a" command takes almost 20 minutes to execute. Only server reboot helps. After reboot "io a" takes only few seconds to execute.
Does anyone know how to solve this problem without rebooting server?
Best regards
Domen
I'm using OpenVMS V8.3-1H1 on Integrity servers. I'm using SAN disk on them. I make some snapshots on daily basis for backups. To refresh disk configuration I'm running commands:
$ mc sysman io scsi
$ mc sysman io a
Sometimes it happens (with no cause) that "io a" command takes almost 20 minutes to execute. Only server reboot helps. After reboot "io a" takes only few seconds to execute.
Does anyone know how to solve this problem without rebooting server?
Best regards
Domen
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2010 03:29 AM
тАО07-29-2010 03:29 AM
Re: AUTOCONFIGURE problem
Domen,
could you use SYSMAN> IO AUTO/LOG to find out, finding and configuring which devices takes a long time ?
Could 'scanning the whole SAN' sometimes take more time ?
Volker.
could you use SYSMAN> IO AUTO/LOG to find out, finding and configuring which devices takes a long time ?
Could 'scanning the whole SAN' sometimes take more time ?
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2010 07:18 PM
тАО07-29-2010 07:18 PM
Re: AUTOCONFIGURE problem
Hi Domen,
>> Sometimes it happens (with no cause) that "io a" command takes almost
>> 20 minutes to execute. Only server reboot helps. After reboot "io a"
>> takes only few seconds to execute.
Looks like SYSMAN is taking a lot of time when configuring device (or set of
devices). Also this problem happens once in a while as you are not seeing this
behavior after a reboot.
First thing here is to identify for which device, SYSMAN is taking a lot of time.
As Volker has suggested, you need to use the "MC SYSMAN IO AUTO/LOG"
command so that SYSMAN would log information about the various devices
that are getting loaded. This way when the problem reoccurs, you would know
which of the device is taking lot of time to get loaded.
Also, you can use the /SELECT, /EXCLUDE qualifier along with "MC SYSMAN IO
AUTO" to try out different combinations.
How frequently does this problem occur ?
Regards,
Murali
>> Sometimes it happens (with no cause) that "io a" command takes almost
>> 20 minutes to execute. Only server reboot helps. After reboot "io a"
>> takes only few seconds to execute.
Looks like SYSMAN is taking a lot of time when configuring device (or set of
devices). Also this problem happens once in a while as you are not seeing this
behavior after a reboot.
First thing here is to identify for which device, SYSMAN is taking a lot of time.
As Volker has suggested, you need to use the "MC SYSMAN IO AUTO/LOG"
command so that SYSMAN would log information about the various devices
that are getting loaded. This way when the problem reoccurs, you would know
which of the device is taking lot of time to get loaded.
Also, you can use the /SELECT, /EXCLUDE qualifier along with "MC SYSMAN IO
AUTO" to try out different combinations.
How frequently does this problem occur ?
Regards,
Murali
Let There Be Rock - AC/DC
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