Expanding generic hosts for all switches, Setting up custom commands, About custom commands – HP Storage Essentials Enterprise Edition Software User Manual
Page 331: Important considerations, Expanding generic hosts, For all switches
HP Storage Essentials SRM 6.0 User Guide 293
Expanding Generic Hosts for All Switches
To display hidden generic hosts for a domain:
1.
Right-click a switch with a "+" icon. This "+" icon indicates the switch has hidden generic hosts.
2.
Select Discovered Element > Expand Generic Hosts for All Switches from the menu.
The hidden elements for the domain appear in upper right corner of the topology.
Setting Up Custom Commands
This section contains the following topics:
• Software Environment Variables for Scripting
About Custom Commands
Custom commands let you run a command that you create on the management server. The
command could point to an executable or a script that does not use the graphical user interface. For
example, assume you have already created a script that backs up a storage system. You could run
that script from System Manager.
You can also use environment variables in your scripts. For example, you could use the variables to
obtain information about a host, such as its total physical memory and the number of processors.
Important Considerations
Keep in mind the following:
•
Run scripts at your own risk. The management server lets you run any script, including those that
can disable the management server.
•
The custom command always runs on the management server unless you are running the telnet
utility. You can obtain information about an element on which you right-click by using the
software's environment variables. See ”
Software Environment Variables for Scripting
•
Custom commands only supports executables and scripts that do not use the graphical user
interface.
•
Management servers on Windows only: If you leave the remote console (cmd /k) open after
running a script, users can traverse the directory structure of the management server.
•
If you want a Perl script to run as a custom command on a UNIX system, you must prefix the
script with the Perl executable, for example, perl myscript.pl, where myscript.pl is the
script you want to run. A best practice is to prefix the script with the path to Perl and the Perl
executable, for example: perl/bin/perl myscript.pl, where perl/bin/ is the directory
containing the Perl executable, perl is the executable and myscript.pl is the script you
want to run.