Re: gatekeeper migration and discover

this is being done on an aix host



I am migrating 7 luns from an existing emc san array to another emc san array…and need to remove the old luns

6 luns are gatekeepers and 1 lun is data — 40 G

I ran config manager on the host and the new luns are showing up from the new array….

I will perform a migratepv to move the data from old 40 Gig disk to the new 40G disk

at this point I will remove disk from vg and rmdev the disk from the aix odm

question is

how to remove the other 6 old 3 meg gatekeep devices?

do I need to move the data from the old pv to the new pv via migratepv

or do I just remove the old gk devices by rmdeving them and them unzoning them?

also, there was a mention of a discovery that is recommended to be done…

how do I do a discovery?

do I run discover after I rmdev all the luns?

Related:

gatekeeper migration and discover

this is being done on an aix host



I am migrating 7 luns from an existing emc san array to another emc san array…and need to remove the old luns

6 luns are gatekeepers and 1 lun is data — 40 G

I ran config manager on the host and the new luns are showing up from the new array….

I will perform a migratepv to move the data from old 40 Gig disk to the new 40G disk

at this point I will remove disk from vg and rmdev the disk from the aix odm

question is

how to remove the other 6 old 3 meg gatekeep devices?

do I need to move the data from the old pv to the new pv via migratepv

or do I just remove the old gk devices by rmdeving them and them unzoning them?

also, there was a mention of a discovery that is recommended to be done…

how do I do a discovery?

do I run discover after I rmdev all the luns?

Related:

This is regarding the Unity Refresh

Hello Everyone:

The last week, we create an Consistency Group and a ThinClone set created for the same also scheduled snapshot at 4:30AM daily . The Snapshots are refreshed in thin clone in daily basis and in and presented to AIX Server and customer could recognize the thin Clone volumes in the OS and start up the Oracle DB.

Now, we did tests with the refresh option in the GUI for the Snapshot Set and everything worked so very well.

The only point, is that we don’t see any option to schedule the refresh of the snapshot set …. Any possibility ?

Somebody, can say me if there is any way to schedule the refresh by cron using CLI ? … or any other method ??

Thank you in advance for your help

Related:

Prevention policy for DB2

I need a solution

I see under the AIX prevention the only DB prevention policy for MySQl.  Is there a best practice or template  for DB2? We are trying to set up prevention for an AIX 7.2 server running IBM DB2. We have a policy in place for the  OS – but want one geared toward the Data Base.

0

Related:

Vipr SRM: Powerpath information is missing in reports for AIX hosts

Article Number: 493469 Article Version: 2 Article Type: Break Fix



ViPR SRM 4.0,ViPR SRM 3.7,ViPR SRM 3.6

Powerpath information is missing in reports for AIX hosts because the collector is missing the INQ tar archive to push to the AIX host as part of discovery.

The “physical hosts” Solution Pack instalation was not complete and directory APG/Collecting/Stream-Collector/Generic-RSC/./conf/scripts/aix was not correctly created. Instead, a file called aix was created.

The RSC collector log shows the following error messages:

INFO — [2016-12-06 08:17:37 CET] — Collecting$CollectingJobHook::preparingJob(): Launching collecting configuration GENERIC-SCRIPTS for context X.X.X.X

SEVERE — [2016-12-06 08:17:37 CET] — AbstractStreamHandlerJob::prepareNextStep(): Error executing handler FileTransferRetriever containing 1 sub handlers

com.watch4net.apg.ubertext.parsing.StreamHandlerException: Path /opt/APG/Collecting/Stream-Collector/Generic-RSC/./conf/scripts/aix leads to a file instead of a directory

Delete and reinstall the “Physical Host” Solution Pack on the collector host:

Make sure that when you go to Centralized Management->Solution Packs->Infrastructure->Physical hosts, you can see Instance(generic-hosts) Component(scripts) among the installed blocks.

Related:

Cisco: Boot from SAN host occasionally unable to access disks at bootup

Article Number: 493084 Article Version: 2 Article Type: Break Fix



Connectrix MDS-9148,Connectrix MDS-Series Firmware 5.X 5.2(8)

This issue only applies to Cisco MDS 9148 switches in NPV mode. It can affect hosts with operating systems, such as AIX, that do not perform SAN error recovery.

A boot from SAN host attached to an NPV switch will fail to see its storage disks sometimes after booting.

AIX hosts that experience this issue can log ABTS and LED 554 “UNKNOWN BOOTDISK” errors.

Cisco bug CSCuv39237

The following type of messages are seen on the NPV switch at the timestamp the host tried to access disk from the show npv status command:

 50) Event:E_DEBUG, length:182, at 257245 usecs after Tue Jan 1 1:02:03 2015 [538976288] npivp_mts_hdlr_fwd_device_flogi_update(1738): Unable to match the fwd response for device FLOGI with any of the outstanding responses, ignoring the resp, error: fu unknown error 51) Event:E_DEBUG, length:106, at 243893 usecs after Tue Jan 1 1:02:03 2015 [538976288] F(4,fc1/1) npivp_flogi_ac_send_flogi_acc: storing flogi fsm state for pwwn: 01:01:01:01:01:01:01:01 

This issue can be intermittent. It stems from a timing issue that can be resolved by causing the host to send another FLOGI. This can be initiated by rebooting the affected host.

Workaround:

Reboot affected host an additional time.

Related:

AppSync: On AIX, a Post Mount script that successfully runs is reported as failing in the Service Plan events and causes the service plan to fail.

Article Number: 485825 Article Version: 2 Article Type: Break Fix



AppSync 2.2 SP3,AppSync

On AIX, a Post Mount script that successfully runs is reported as failing in the Service Plan events and causes the service plan to fail.

The events in the service plan will be similar to:


Mon 06/27/2016 02:27:23 PM,Post-mount script,User script results: script generated message here.,

Mon 06/27/2016 02:27:24 PM,Post-mount script,”User script results: script generated message here.,

Mon 06/27/2016 02:27:28 PM,Post-mount script,User script /home/oracle/directory/myPostScript.bash failed to run on host hostname1.,

Mon 06/27/2016 02:27:28 PM,Post-mount script,”Failed to run user script /home/oracle/directory/myPostscript.bash. The reason is

script generated message here.

Mon 06/27/2016 02:27:29 PM,Post-mount script,Post-mount script phase for serviceplan_name completed with errors,

Mon 06/27/2016 02:27:30 PM,Post-mount script,Error occurred during the execution of service plan serviceplan_name

On AIX, data is sent to the error stream even if the script is successful.

AppSync interprets this as an error.

This issue is resolved in AppSync 3.0.1

Please upgrade to AppSync 3.0.1

Related: