Explorer Frequently Asked Questions and Debugging Tricks (r1.5)

Article:TECH65156  |  Created: 2009-01-19  |  Updated: 2013-12-18  |  Article URL http://www.symantec.com/docs/TECH65156
Article Type
Technical Solution

Product(s)

Environment

Issue



Explorer Frequently Asked Questions and Debugging Tricks (r1.5)


Solution



General Explorer Questions and Tricks:
 

 

 
How can I move an Explorer into its own process?
 
You may download a script that isolates a specific Explorer, all Explorers in a specified process, or all Explorers on a host from Technote 315729 (below).
 
Review the README for syntax and examples of the script.
 
In order to do this manually:
 
The following set of commands will move the NetApp Explorer into its own process, which is named "NetApp_Exp_solo":
 
Note that the maximum number of characters in the new process name is *16*.
 
# cd /opt/VRTSccs/VRTShal/bin
# ./halagentcfg stop-process --process-name ArrayExplorers
# ./halagentcfg move-explorer --explorer-name NetAppExplorer --process-name NetApp_Exp_solo
# ./halagentcfg start-all
 

 

 
Ok, now show me how I'd move all but one of the Explorers running in a process into their own processes?
 
Let's say we wanted to move all of the Explorers running in the HostExplorers process into their own processes, leaving one behind.
 
# ./halagentcfg stop-process --process-name HostExplorers
# ./halagentcfg list-processes --process-name HostExplorers -a
Process    [HostExplorers]
 Explorer [HostExplorer]
 Explorer [StorageExplorer]
 Explorer [TapeDeviceExplorer]
 
Let's move the HostExplorer and the StorageExplorer out, leaving the TapeDeviceExplorer still in the HostExplorers process.
 
# ./halagentcfg move-explorer --explorer-name HostExplorer --process-name HostExplorer_s
Process: HostExplorer_s Explorer: HostExplorer moved.
# ./halagentcfg move-explorer --explorer-name StorageExplorer --process-name StorageExp_s
Process: StorageExp_s Explorer: StorageExplorer moved.
# ./halagentcfg start-all
# ./halagentcfg list-processes -a
Process    [ApplicationExplorers]      RUNNING      17417
 Explorer [DB2Explorer]               RUNNING                Normal
 Explorer [DmpExplorer]               RUNNING                Normal
 Explorer [EMCPowerPathExplorer]      RUNNING                Normal
 Explorer [FSExplorer]                RUNNING                Normal
 Explorer [OracleExplorer]            RUNNING                Normal
 Explorer [SunVMExplorer]             RUNNING                Normal
 Explorer [SybaseExplorer]            RUNNING                Normal
 Explorer [VcsExplorer]               RUNNING                Normal
 Explorer [VxVmExplorer]              RUNNING                Normal
Process    [ArrayExplorers]            RUNNING      17468
 Explorer [EMCClariionExplorer]       RUNNING                Normal
 Explorer [EMCSymmetrixExplorer]
 Explorer [HPEvaExplorer]             RUNNING                Normal
 Explorer [HiCommandExplorer]         RUNNING                Normal
 Explorer [IBMDS8000Explorer]         RUNNING                Normal
 Explorer [IBMSharkExplorer]          RUNNING                Normal
 Explorer [NetAppExplorer]            RUNNING                Normal
Process    [CIMVAILExplorers]          RUNNING      17409
 Explorer [CIMVAILExplorer]           RUNNING                Normal
Process    [FCExplorers]               RUNNING      17490
 Explorer [BrocadeSwitchExplorer]     RUNNING                Normal
 Explorer [CiscoSwitchExplorer]       RUNNING                Normal
 Explorer [CntSwitchExplorer]         RUNNING                Normal
 Explorer [GsSwitchExplorer]          RUNNING                Normal
 Explorer [SnmpSwitchExplorer]        RUNNING                Normal
 Explorer [VmwareExplorer]            RUNNING                Normal
Process    [HALCHM]                    RUNNING      17999
 Explorer [HALCHM]                    RUNNING                Normal
Process    [HALMIGA]                   RUNNING      17459
 Explorer [SALToHALMigration]         RUNNING                Normal
Process    [HostExplorer_s]            RUNNING      28159
 Explorer [HostExplorer]              RUNNING                Normal
Process    [HostExplorers]             RUNNING      28182
 Explorer [TapeDeviceExplorer]        RUNNING                Normal
Process    [McDataSwitchExplorer]      RUNNING      17447
 Explorer [McDataSwitchExplorer]      RUNNING                Normal
Process    [StorageExp_s]              RUNNING      28166
 Explorer [StorageExplorer]           RUNNING                Normal
Process    [HALLHM]                    RUNNING*     16782
 Explorer [HALLHM]                    RUNNING*               Normal
 

 

 

 
How can I change the polling intervals of Explorers?
 
Here's the command sequence to change the polling interval of the StorageExplorer programmatically (note the ".". characters):
 
halsecurity login
halcmd -A  StorageExplorer
reg.
open -rw
rsv -s Devices "PollingIntervalInMinutes"="180"
close -commit
.
quit
 
This is the effect on the StorageExplorer, with the value set to 180 (3 hours):
 
C:\Program Files\VERITAS\CommandCentral Storage\HAL\bin>halcmd -A StorageExplorer -c dev.ld
       Device Name                                Mode   State
       -----------                                ----   -----
       Devices                                   Normal  NORMAL
               LastRefreshTime                  2008-06-19 17:38:53:140
               LastRefreshEndTime               2008-06-19 17:38:53:156
               NextScheduledRefreshTime         2008-06-19 20:38:53:000
       Devices\hba-0:0                           Normal  NORMAL
               AutoDiscovered = (boolean) 1
               DeviceType = (string) Normal
               LastRefreshTime                  2008-06-19 17:38:53:140
               LastRefreshEndTime               2008-06-19 17:38:53:140
               NextScheduledRefreshTime         2008-06-19 20:38:53:000
       Devices\hba-1:0                           Normal  NORMAL
               AutoDiscovered = (boolean) 1
               DeviceType = (string) Normal
               LastRefreshTime                  2008-06-19 17:38:53:140
               LastRefreshEndTime               2008-06-19 17:38:53:140
               NextScheduledRefreshTime         2008-06-19 20:38:53:000
 

 

 

 
How do I retrieve XML from Explorers?
 
The following commands will retrieve the XML from the StorageExplorer, and write it to the output file /tmp/storage_exp.xml. Note that the Explorer from which you wish to retrieve the XML must be running in order for the command to succeed.
 
./halsecurity login
./halcmd -A StorageExplorer -c "data.gao -f /tmp/storage_exp.xml"
 
In order to fetch the XML from an attached Managed Host, add the -h flag:
 
./halsecurity login
./halcmd -A StorageExplorer -h magellan22.veritas.com -c "data.gao -f /tmp/storage_exp.xml"
 

 

 

 
How can I find out when an explorer last started and ended a discovery cycle, and when the next cycle is scheduled?
 
$INSTALLDIR/halcmd -A -c dev.ld
 
So the following invocation will tell us the last time the StorageExplorer performed a discovery, and when the next discovery is scheduled to run:
 
# ./halcmd -A StorageExplorer -c dev.ld
       Device Name                                Mode   State
       -----------                                ----   -----
       Devices                                   Normal  NORMAL
               LastRefreshTime                  2008-05-06 20:43:14:029
               LastRefreshEndTime               2008-05-06 20:43:14:035
               NextScheduledRefreshTime         2008-05-06 20:48:14:000
 

 

 
How can I force a Management Server or Managed Host Explorer refresh from the Management Server?
 
# pwd
/opt/VRTSccs/VRTShal/bin
# ./halcmd -A HALCHM -c 'agent.ra -r HostExplorer@squeaky.engba.symantec.com'
command = IDL:Veritas/HAL/CHM/AgentManagement_1_0:1.0::refresh-agent
task_id = (string) DCT-64-20080604051052_0166b
 

 

 

 
Advanced Explorer Topics
 

 

 
How do I debug Explorer memory leak, high CPU, and coring problems?
 
Settings Summary -> Product Diagnostics -> CC Resource Usage
 
To view the information for one of the attached Managed Hosts, select the "Customize" option in the "Scope" pane. This will pop up a "Customize" window, which will contain a "Scope" dropdown, from which you can select your desired MH.
 

 

 
How do I debug Explorer high CPU utilization problems?
 
It can take a long time and lots of CPU power to discover lots of LUNs. It also takes a lot of time to generate the XML for lots of LUNs.
 
But there is no magic here.
 
You must determine whether it is the StorageExplorer that is causing the high CPU utilization. This is done by using "ps" or some other tool to identify the process that is using the CPU. Assuming that the process is one of the processes in which several Explorers are running, we need to separate each of the Explorers into its own process. Then we can use the same tools to identify which Explorer is using the CPU.
 
Next, we need to know how long an Exploration takes, and when the next one is scheduled. Let's say it IS the StorageExplorer that is taking the CPU, as we suspect.
 
"./halcmd -A StorageExplorer -c dev.ld" returns three interesting fields:
 
   LastRefreshTime                  (the time the most recent discovery cycle started)
   LastRefreshEndTime               (the time the most recent discovery cycle ended)
   NextScheduledRefreshTime         (the time the next upcoming discovery cycle is scheduled to begin.
 
So let's say we run this command, and it returns this:
 
# ./halcmd -A StorageExplorer -c dev.ld
       Device Name                                Mode   State
       -----------                                ----   -----
       Devices                                   Normal  NORMAL
               LastRefreshTime                  2008-05-08 13:48:57:129
               LastRefreshEndTime               2008-05-08 13:48:57:289
               NextScheduledRefreshTime         2008-05-08 13:53:57:000
 
From this, we know that the PollingIntervalInMinutes is 5, and that the previous refresh took a fraction of a second. (It'll be longer on a host with HBAs.)
 

 



Legacy ID



314426


Article URL http://www.symantec.com/docs/TECH65156


Terms of use for this information are found in Legal Notices