can't get script to appear on Ignite Advanced tab "Available Scripts"

[Scott Lindstrom_2]

As indicated on some other posts on this forum I have added a script I'd like to be available to execute when we Ignite a server.

I ran "manage_index -a -s /var/opt/ignite/recovery/MR_DR_postload.sh"; this added this line to /var/opt/ignite/data/INDEX:

scripts {
"/var/opt/ignite/recovery/MR_DR_postload.sh"
}

When I Ignited the box no scripts are listed under the "Available scripts" side of the Advanced tab.

Based on another post I read I also put thsi INDEX file in /var/opt/ignite/data/Rel_B.11.23. But there was no change doing that.

Am I placing this file in the wrong place - or something else really obvious?

[IN-PX - C007 · Accepted solution]

Hi Scott,
there are several options where you can add the scripts, the question is where it should show up.

The syntax is fine:
Syntax:
scripts {
"/var/opt/ignite/recovery/MR_DR_postload.sh"
}

1. For all installations
Put it in /var/opt/ignite/INDEX


2. In a specific Installation type (all 11.23 f.e.)
Put it in the config.local (f.e. /var/opt/ignite/data/Rel_B.11.23/config.local)

3. For a specific client
add it to the config file
under /var/opt/ignite/clients/

Syntax:
init _hp_custom_scripts="Current Post Configuration Scripts"
_hp_custom_scripts visible_if FALSE
(_hp_custom_scripts=="Current Post Configuration Scripts") {
post_config_script+="/var/opt/ignite/clients//user_defined_scripts/postconfig-script.sh"
} # end "Current Post Configuration Scripts"


For all cases make sure the directory is shared and accessable.

For Ignite Version C.7.9.261 is a bug around if you use it at least in the client specific config file, you will need to add _hp_cfg_detail_level="ipvstf" to your config file or the scripts will not be used automatically (Patch Request QXCR1001013876 - not public vissible yet for more details).

hth

Stephan

[Scott Lindstrom_2]

Stephan - adding it to /var/opt/ignite/INDEX on the server where the ignite images are stored worked perfectly.

Making changes on the server itself (and making a new make_net_recovery) does not seem to work as well.

Thanks!

Scott