topic AUTOCONFIGURE problem in Operating System - OpenVMS

AUTOCONFIGURE problem

Domen Setar — Thu, 29 Jul 2010 09:06:17 GMT

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

Re: AUTOCONFIGURE problem

Volker Halle — Thu, 29 Jul 2010 10:29:46 GMT

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.

Re: AUTOCONFIGURE problem

P Muralidhar Kini — Fri, 30 Jul 2010 02:18:39 GMT

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