 Hi! In this tutorial, we will see how to configure remote monitoring of i-series OS using patrol for i-series. To begin the configuration, select i-series as the monitoring solution, select the latest version, select i-series remote monitoring as the monitor profile and i-series as the monitor type. Click add to configure a remote host. In the host names field, you can enter the host in any of the listed formats. The first format is a simple host name. It can either be a fully qualified domain name or just a host name. The second acceptable format is a host IP address. We can also enter a host name or an IP address with a published host name. This published host name is used to create the device of the host in the TrueSight console. Here, Mercury and Mars devices will be created for server 1 and the IP address respectively. If we want to apply the same configuration for multiple hosts, we can also enter comma separated entries of hosts or IP addresses that share the same credentials. If you have a large number of hosts, you can configure them from a file. We can enter the absolute part to the file that includes comma separated list of hosts in the acceptable formats that we just discussed. This is my sample file that contains the host details. For this demo, I will use a simple host name for the configuration. Enter the user name to connect to the remote host. Enter the password. Re-enter the password for confirmation. Select this option to enable secure connection to the ICD's host over SSL. Now, select the monitoring option as per your requirement. The standard monitoring option enables monitoring of the system, pool, user and batch monitor types only. The advanced monitoring option allows you to configure monitor types of your choice. Here, you can configure system, user, pool, batch, ASP, network interface, active jobs, message queue, history log, output queue, schedule jobs, subsystem, objects, job queue and network connection for monitoring. You need to explicitly select or deselect the monitor types in the advanced configuration section to enable or disable the respective monitor type configuration. For this demo, I'll select system and subsystem monitor types. As you can see, we do not require any additional configuration for the system monitor type. Now, I'll select the subsystem monitor type and enter the subsystem names that I want to monitor. I'll monitor the queue batch subsystem. In library, if we keep the default value, the KM searches for queue batch subsystem in all the libraries. I'll enter the library name. We'll monitor the queue batch subsystem from the QGPL library and exclude all other libraries. Click OK to save the configuration. We can now see the instance in the true site console. This is how you can configure a remote monitoring of ICDs OS using patrol for ICDs. Thank you for watching this video.