Installation Procedures / Notes:

TM server installation:
Install HDvM, Register storage boxes (Add subsystem).. Note: so TM server must have n/w
connection to box as HDvM requires it.

Install HTM .. hcmdssrv /status to see status.

Install Agent for RAID on TM server (for monitoring Subsystems). This can be installed on
TM server or any other server attached to Storage.

Install Agent for platform on TM server (This is to monitor TM servers OS). The
installation asks for 3 components: Agent for RAID map, Agent for platform, Xchange agent
(not selected by default). Note this may ask for reboot after installation.

To register storage (called RAID) instance

Note Must give a command device to TM server from Storage being monitored and also
must install RMLIB on TM server. Then only it works. If RAID agent is installed on another
server, it must be given a cmd device similarly.

>jpcinssetup agtd inst USP-V

Asks for command device (use command jpctdlistraid command and paste the
\\.\Physicaldiskx to jpcinssetup window).

Note if another server is running the RAID instance, execute the above command from that
server.

Once instance is registered., start agent-instance by jpcstart all command. Monitor status
using jpcctrl list * command. Should remain Active.

Now go to Administration-Data polling-Refresh. The new agent should appear in the

window below. For RAID agent , it appears under HDvM column itself under related
agents column. Set polling interval for it and do a manual polling of it. It may take a couple
of hours (or 3 to 4 pollings) for Subsystem to appear under subsystem tree in resources
window. To see agent is working, go to Perf. Reporter window and run a report.. if metrics
are being shown.. agent is working.

If you have another storage box, have to create another instance. So one agent can have
multiple instances.

To stop/restart agent instance:

>jpcstop agtd inst=USP

>jpcstart agtd inst=USP
To remove instance:

>jpcinunsetup agtd inst USP-V.

This removes agent instance from jpcctrl list * view. but it still appears in GUI under Agents
in Perf. Reporter. How to delete it?

>jpcctrl delete <SID name> (have to try this .. not sure)

Platform or OS agent:

After installation, how to point to TM server? By default it points to itself.. you can check
this by issuing jpcnshostname command (so no need to do anything for platform agent
installed on TM server). To set it to TM server (on other servers) use the below command

>jpcnshostname s <Hostname of TM server>

Note here we are setting hostname of TM server.. by this we are telling Agent running on
this monitored server that when this TM server polls, you can supply it the required
information. Cos the agents dont report to TM server .. its the TM server that polls the
agents.

Once instance is registered., start agent-instance by jpcstart all command. Monitor status
using jpcctrl list * command. Should remain Active.

Now go to Administration-Data polling-Refresh. The new agent should appear in the

window below. Set polling interval for it and do a manual polling of it. To see agent is
working, go to Perf. Reporter window and run a report.. if metrics are being shown.. agent is
working.

For switch agent:

(Note - installed both SMI-Agent and switch agent on TM server itself)

- Installed SMI-Agent for switch... used all default options.

While installing SMI-Agent - In the proxy window- added switch IP, username/password
(admin/password) for switch thats being monitored... not sure if this is required.

>jpcinssetup agtw -inst SAN

Switch vendor - 1.Brocade

IP Address (for Brocade -> Proxy switch) --- this is actual IP of switch (just ignore the word
proxy)

Symbolic name - anything

Logic ID - admin
Password - password (switch defaults)

Target Switch WWN - this can be obtained from switch GUI (Switch admin window)

IP address (for brocade SMI Agent) -- IP of TM server itself (or whereever SMI-AGent is
installed)

SMI-A user - default

Passord - default (just press enter)

> jpcstart all

> jpcctrl list *

(repeat a few times and make sure switch agent instance is Active, make sure it doesnt turn
inactive after a while.)

Now go to Administration-Data polling-Refresh. The new agent should appear in the

window below. Set polling interval for it and do a manual polling of it. To see agent is
working, go to Perf. Reporter window and run a report.. if metrics are being shown.. agent is
working.