--- title: "Add an IBM node" description: "Add an IBM XIV, SVC, z/OS or WebSphere node for agentless scanning." product: "Guardian" edition: "Classic" type: "workflow" url: "https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/add-a-single-node/agentless/ibm-node/" --- # Add an IBM node Add an IBM XIV, SVC, z/OS or WebSphere node for agentless scanning. Guardian supports four types of IBM nodes: XVI, SVC, Z/OS, and WebSphere. Applies to: `Guardian Classic` ## Add an IBM XIV, SVC, or Z/OS node Adding an IBM XIV, SVC, or Z/OS node to your Guardian instance lets you monitor and track the configuration of a storage or computing device. This enables you to oversee performance metrics, identify potential issues, and ensure that the device passes your organisation's security and operational policies. To add an IBM XIV, SVC, or Z/OS node for Agentless scanning, complete the following steps: 1. In the Guardian web application, navigate to the **Add Nodes** tab (**Inventory** > **Add Nodes**). The **Add Nodes** page is displayed. ![Add nodes tab](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/add-nodes-tab.png) 2. Type 'IBM' in the search bar. 3. Select the 'IBM' node type you want to add and click the **Go Agentless** button to proceed. The **Connect Agentlessly to [Node Type]** page is displayed. ![Go agentless ibm](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/go-agentless-ibm.png) 4. Here, complete the following options: ![Connect agentlessly ibm](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/connect-agentlessly-ibm.png) **Connection Manager group** drop-down list : The Connection Manager group that is responsible for scanning your IBM node. Select a Connection Manager group from the drop-down list. **Node Name** field : The name of the node. The value you enter here will be used as the display name in Guardian. **Hostname / IP Address** field : The hostname or IP address of your node. !!! note Typically, this is the fully qualified domain name (**FQDN**). However, it could also be the IP address. **SSH Port (Optional)** field : The Secure Shell (**SSH**) port number that the Connection Manager uses to communicate with the target nodes for scanning. If no value is provided, Guardian will default to port 22. !!! note If you enter a port number that is different to the default (port 22), make sure that it matches the port number that the administrator of the target node is using to run their SSH server. **Select credential type** radio buttons : The credentials to be used when authenticating Guardian's access to the node. The following options are available: - **SSH Key** – Option to use an SSH key to authenticate Guardian's access to the node. Enter the **Username**, then copy the displayed command and run it on the node to create the necessary files. For more information, see [Key-Based Authentication](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/add-a-single-node/agentless/network-device-node/index.md#key-based-authentication). - **Password** – Option to use credentials stored in the Guardian vault or Secret Server. Select one of the options below: - **Guardian Credentials Vault** – Use credentials stored in your Guardian instance. Select an option from the **Credentials** drop-down list. Additionally, you can select 'Add New Credential' to display the **Create Credential** dialog if you anticipate using these same credentials for other nodes or integrations. For more information, see [Create Credential](https://docs.cloudhouse.com/guardian/classic/inventory/credentials/credentials/index.md#create-credential). !!! note The **Credentials** tab was introduced in V4.3.46.0 of Guardian. For more information, see [July 2024 Quarterly Release](https://docs.cloudhouse.com/guardian/classic/what-s-new/3-archive/2024/quarterly-releases/q2/july-feature-2024/index.md). !!! warning This option is only displayed if you have the **Credentials** feature enabled. If you don't, you'll be prompted to enter a **Username** and **Password** for authentication. - **Secret Server** – Use credentials stored in your organisation's existing Secret Server account. Select an option from the **Secret Server Items** drop-down list. The credentials displayed are based on the Secret Server integration. For more information, see [Secret Server Integration](https://docs.cloudhouse.com/guardian/classic/control/integrations/secret-server-integration/index.md). !!! note The Secret Server feature was introduced in V4.3.54.0 of Guardian. For more information, see [April 2025 Quarterly Release](https://docs.cloudhouse.com/guardian/classic/what-s-new/2-previous-release/2025/quarterly/q2/april-2025/index.md). !!! warning This option is only displayed if you have the Secret Server feature enabled. If you don't, you'll be prompted to enter a **Username** and **Password** for authentication. - **Microsoft Entra ID** – Option to use the Azure CLI service principle credentials that are configured to use SSH. Enter the following information: - **Username** field – The username of the service principal configured to use SSH. - **Azure CLI service principal password** field – The password of the service principal configured to use SSH. - **Azure CLI service principal tenant** field – The tenant ID of the service principal configured to use SSH. - **Azure CLI login command (Optional)** field – The az login command for Azure CLI. !!! note This option is only available if you have the **Microsoft Entra ID** feature enabled. - **Service Account** – Option to use the same credentials currently being used by the selected Connection Manager. No further input is needed. 5. Once you've completed the above options click **Scan Node** to add the IBM node to your Guardian instance. Now, Guardian performs an initial scan of the node. You can wait on this page for the scan to finish, at which point you will see a **View Scan** button. To view the results of this initial scan, click **View Scan**. However, you can also navigate elsewhere while Guardian performs its initial scan of the node. You can then view the status of the scan on the [**Job History**](https://docs.cloudhouse.com/guardian/classic/control/job-history/job-history/index.md) page (**Inventory** > **Job History**). For more information on what to do next after adding a node, see below. ## Add an IBM WebSphere node Adding an IBM WebSphere node to your Guardian instance lets you monitor and track the configuration of an application server. This enables you to oversee performance metrics, manage deployments, monitor application health, and ensure that the WebSphere environment passes your organisation's security and operational policies. To add an IBM WebSphere node for Agentless scanning, complete the following steps: 1. In the Guardian web application, navigate to the **Add Nodes** tab (**Inventory** > **Add Nodes**). The **Add Nodes** page is displayed. ![Add nodes tab](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/add-nodes-tab.png) 2. Type 'IBM WebSphere' in the search bar. 3. Select 'IBM WebSphere' and click the **Go Agentless** button to proceed. The **Connect Agentlessly to IBM WebSphere** page is displayed. ![Go agentless ibm web](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/go-agentless-ibm-web.png) 4. Here, complete the following options: ![Connect agentlessly ibm web](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/connect-agentlessly-ibm-web.png) **Connection Manager group** drop-down list : The Connection Manager group that is responsible for scanning your IBM Websphere node. Select a Connection Manager group from the drop-down list. **Node Name** field : The name of the node. The value you enter here will be used as the display name in Guardian. **Hostname / IP Address** field : The hostname or IP address of your node. !!! note Typically, this is the fully qualified domain name (**FQDN**). However, it could also be the IP address. **SSH Port (Optional)** field : The Secure Shell (**SSH**) port number that the Connection Manager uses to communicate with the target nodes for scanning. If no value is provided, Guardian will default to port 22. !!! note If you enter a port number that is different to the default (port 22), make sure that it matches the port number that the administrator of the target node is using to run their SSH server. **Websphere install path (Optional)** field : The folder, relative to your domain name's document root folder. For example, `/server-name`. By default, if no value is provided, the following install path will be used `/opt/IBM/WebSphere`. **Profile name** field : The profile name of the machine. **Cell name** field : The name of the administrative domain, managed by a WebSphere Deployment Manager. **WEBSPHERE node name** field : The logical groupings of application servers on the machine. **JVM name** field : The Java Virtual Machine (**JVM**) name. **Select credential type** radio buttons : The credentials to be used when authenticating Guardian's access to the node. The following options are available: - **SSH Key** – Option to use an SSH key to authenticate Guardian's access to the node. Enter the **Username**, then copy the displayed command and run it on the node to create the necessary files. For more information, see [Key-Based Authentication](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/add-a-single-node/agentless/network-device-node/index.md#key-based-authentication). - **Password** – Option to use credentials stored in the Guardian vault or Secret Server. Select one of the options below: - **Guardian Credentials Vault** – Use credentials stored in your Guardian instance. Select an option from the **Credentials** drop-down list. Additionally, you can select 'Add New Credential' to display the **Create Credential** dialog if you anticipate using these same credentials for other nodes or integrations. For more information, see [Create Credential](https://docs.cloudhouse.com/guardian/classic/inventory/credentials/credentials/index.md#create-credential). !!! note The **Credentials** tab was introduced in V4.3.46.0 of Guardian. For more information, see [July 2024 Quarterly Release](https://docs.cloudhouse.com/guardian/classic/what-s-new/3-archive/2024/quarterly-releases/q2/july-feature-2024/index.md). !!! warning This option is only displayed if you have the **Credentials** feature enabled. If you don't, you'll be prompted to enter a **Username** and **Password** for authentication. - **Secret Server** – Use credentials stored in your organisation's existing Secret Server account. Select an option from the **Secret Server Items** drop-down list. The credentials displayed are based on the Secret Server integration. For more information, see [Secret Server Integration](https://docs.cloudhouse.com/guardian/classic/control/integrations/secret-server-integration/index.md). !!! note The Secret Server feature was introduced in V4.3.54.0 of Guardian. For more information, see [April 2025 Quarterly Release](https://docs.cloudhouse.com/guardian/classic/what-s-new/2-previous-release/2025/quarterly/q2/april-2025/index.md). !!! warning This option is only displayed if you have the Secret Server feature enabled. If you don't, you'll be prompted to enter a **Username** and **Password** for authentication. - **Microsoft Entra ID** – Option to use the Azure CLI service principle credentials that are configured to use SSH. Enter the following information: - **Username** field – The username of the service principal configured to use SSH. - **Azure CLI service principal password** field – The password of the service principal configured to use SSH. - **Azure CLI service principal tenant** field – The tenant ID of the service principal configured to use SSH. - **Azure CLI login command (Optional)** field – The az login command for Azure CLI. !!! note This option is only available if you have the **Microsoft Entra ID** feature enabled. - **Service Account** – Option to use the same credentials currently being used by the selected Connection Manager. No further input is needed. 5. Once you've completed the above options click **Scan Node** to add the IBM WebSphere node to your Guardian instance. Now, Guardian performs an initial scan of the node. You can wait on this page for the scan to finish, at which point you will see a **View Scan** button. To view the results of this initial scan, click **View Scan**. However, you can also navigate elsewhere while Guardian performs its initial scan of the node. You can then view the status of the scan on the [**Job History**](https://docs.cloudhouse.com/guardian/classic/control/job-history/job-history/index.md) page (**Inventory** > **Job History**). For more information on what to do next after adding a node, see below. ## Where next - [*Read* **Node Scan Results** What every scan of a node collected.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/nodes/node-scan-results/index.md) - [*Organise* **Node groups** Group nodes by type, location and more.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/node-groups/node-groups/index.md) - [*Tune* **Scan options** Choose what each scan collects.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/scan-options/scan-options/index.md) - [*Compare* **Configuration differencing** Compare nodes, groups and scans.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/configuration-differencing/configuration-differencing/index.md) - [*Govern* **Policies** Define the configuration you expect.](https://docs.cloudhouse.com/guardian/classic/control/policies/policies/index.md) - [*Connect* **Integrations** Sync nodes and act on events.](https://docs.cloudhouse.com/guardian/classic/control/integrations/integrations/index.md)