Open topic with navigation

# Prerequisites for Adding a Host (for each Host Type)

As announced in the 23.1 release, the Collectors feature and the Connectors in Transformation Hub (CTH) feature have been deprecated, and from the ArcSight Platform 24.2 release on, only existing collectors and CTH deployments are supported. You can continue managing your collectors and CTHs in the platform, but you cannot create any new ones.

Connection Information for Adding a Host

Host Type | Required Information
--- | ---
Appliance with Local Connectors (includes ArcSight Management Center Appliance, Connector Appliance, or Logger Appliance (L7700)) | Hostname (FQDN) or IP address. Hostname or IP must be resolvable by ArcSight Management Center: either through DNS for a hostname, or directly for an IP address. If hostname is used, the hostname entered must match the hostname from the host’s SSL certificate. If the FQDN fails to resolve, restart the web service. Authentication credentials (username and password) for logging into the host. If the host is configured for external authentication, such as LDAP or RADIUS, use the external authentication credentials, if possible, or use the fall back credentials. Note: See Node Authentication Credentials for more information about authentication credentials.
| Authentication credentials (username and password) for any local containers. If the appliance includes multiple containers, then the credentials for each container must be identical. For example, if the username and password for one container managed by a Connector Appliance is myusername and mypassword, then myusername and mypassword must be the credentials for all local containers managed by the same Connector Appliance.
Appliance without Local Connectors (includes Logger Appliance (non-L7700)) | Hostname (FQDN) or IP address. Hostname or IP must be resolvable by ArcSight Management Center: either through DNS for a hostname, or directly for an IP address. If hostname is used, the hostname entered must match the hostname from the host’s SSL certificate. If the FQDN fails to resolve, restart the web service. Authentication credentials (username and password) for logging into the host. If the host is configured for external authentication, such as LDAP or RADIUS, use the external authentication credentials, if possible, or use the fall back credentials. Note: See Node Authentication Credentials for more information about authentication credentials.
Software Form Factor (includes Software ArcSight Management Center, Software Connector Appliance, or Software Logger) | Hostname (FQDN) or IP address. Hostname or IP must be resolvable by ArcSight Management Center: either through DNS for a hostname, or directly for an IP address. If hostname is used, the hostname entered must match the hostname from the host’s SSL certificate. If the FQDN fails to resolve, restart the web service. Authentication credentials (username and password) for logging into the host. If the host is configured for external authentication, such as LDAP or RADIUS, use the external authentication credentials if possible, or use the fall back credentials. Note: See Node Authentication Credentials for more information about authentication credentials. Port number assigned to the product.
Connector (includes SmartConnectors of all types) | Hostname (FQDN) or IP address. Hostname or IP must be resolvable by ArcSight Management Center: either through DNS for a hostname, or directly for an IP address. If the FQDN fails to resolve, restart the web service. Authentication credentials (username and password) for the connector. Note: See Node Authentication Credentials for more information about authentication credentials. Optionally, specify an inclusive port range separated by a hyphen (such as 9004-9008) to scan a port range for all connectors. Note: If the port range includes multiple connectors, then the credentials for each connector in the range must be identical. For example, if the username and password for one connector in the range was myusername and mypassword, then myusername and mypassword must be the credentials for every connector in the port range. Note: Prior to adding a software-based SmartConnector as a host, you must prepare the Smart Connector as explained in SmartConnectors on ArcMC.
Collector | Hostname (FQDN) or IP address. Hostname or IP must be resolvable by ArcSight Management Center: either through DNS for a hostname, or directly for an IP address. If the FQDN fails to resolve, restart the web service. Authentication credentials (username and password) for the Collector. Note: See Node Authentication Credentials Node Authentication Credentials for more information about authentication credentials. Optionally, specify an inclusive port range separated by a hyphen (such as 48080-48088) to scan a port range for all Collectors. Note: If the port range includes multiple Collectors, then the credentials for each Collector in the range must be identical. For example, if the username and password for one connector in the range was myusername and mypassword, then myusername and mypassword must be the credentials for every Collector in the port range.
Transformation Hub - Non-Containerized Deployment | Hostname (FQDN) or IP address. Hostname or IP must be resolvable by ArcSight Management Center: either through DNS for a hostname, or directly for an IP address. If the FQDN fails to resolve, restart the web service. Port number for the Transformation Hub (default 32080) In order to add Transformation Hub as a host, the active user must belong to an ArcMC permission group with rights to do so. By default, the admin user has such rights. Note: Prior to performing the Add Host process, you need to generate the ArcMC certificate with complete FQDN and download the .crt file, then copy the certificate file to your Kubernetes master node. See Preparing to Add Transformation Hub as a Host for details on this process.
Transformation Hub - OPTIC Management Toolkit (OMT) | Virtual FQDN or Virtual IP (VIP) address. VIP must be resolvable by ArcSight Management Center: either through DNS for a hostname, or directly for a VIP address. If the FQDN fails to resolve, restart the web service. Port number for the Transformation Hub (default 32080) The following Kubernetes cluster parameters: Cluster Port (default 443) Cluster Username and Password Contents of the certificate file. For more details, see here. In order to add Transformation Hub as a host, the active user must belong to an ArcMC permission group with rights to do so. By default, the admin user has such rights.

- An SSL Certificate: An SSL certificate must be generated for any of the following host types to be managed:

- Connector Appliance or Software Connector Appliance

- Logger Appliance or Software Logger

- Transformation Hub (any version)

- ArcSight Management Center Appliance or Software ArcSight Management Center

  The hostname in the certificate must match the hostname you are adding to ArcMC. For more information on generating certificates for these host types, consult the ArcSight Administrator’s Guide for each product. If a host to be added already has a certificate installed, you can use the existing certificate, as long as the hostname on the certificate matches the hostname of the host you are adding.

  Note: If the hostname does not match the hostname in the SSL certificate, you can regenerate a matching certificate by doing one of the following:

  - For a hardware appliance, in System Admin > Network, click the NICS tab. Under Host Settings, note the entry in the Hostname field. This is the value you should use to add the host to ArcMC. Click Restart Network Service. Then, in the navigation menu, under Security, pick SSL Server Certificate. Click Generate Certificate. A new certificate will be generated that matches the hostname from the NICS tab.

  - For software form factor, in System Admin > SSL Server Certificate, under Enter Certificate Settings, verify that the hostname from the NICS tab noted previously is entered in the Hostname field. Then, click Generate Certificate. A new certificate will be generated that matches the hostname from the NICS tab.

- Check for Agent Installation: Check the table under Installing the ArcMC Agent to determine if the ArcMC Agent needs to be installed on a host prior to adding it to ArcMC. For some host types, the Agent will be installed automatically upon adding a host.

  Note: Perl is required for the automatic installation of the ArcMC Agent. Ensure that Perl is installed on the host prior to attempting to add the host to ArcMC.