We’re migrating product documentation to docs.vmware.com, starting with Carbon Black Cloud. Learn more.

Cb Response 6.2.3 Server / Cluster Management Guide [Japanese]

Cb Response 6.2.3 Server / Cluster Management Guide [Japanese]

This Japanese translation of the Cb Response Server/Cluster Management Guide explains how to manage Cb Response servers and clusters. It includes the following topics:

  • Server Overview – Provides an overview of the Cb Response server technology stack, daemons, configuration, and logs.
  • Installing the Cb Response Server – Explains how to install/initialize a new Cb Response server, as well as how to upgrade, troubleshoot, and uninstall the server.
  • Server Backup and Restoration – Explains how to perform various backup and restore procedures.
  • Ports and Protocols – Provides a collection of tables that detail port and protocol information for several different server communications.
  • Installing a Cb Response Cluster – Introduces Cb Response clusters and explains how to configure clusters, add minions to existing clusters, remove minion nodes from clusters, and upgrade cluster nodes
  • Using CBCLUSTER as a Non-Root User – Describes how to use the CBCLUSTER command as a non-root user.

See the Comments section below for changes since the previous Japanese translation.

Labels (1)
Attachments
0 Kudos
Comments

The following changes have been made to the Cb Response Server Cluster Management Guide since the previous Japanese translation (6.2):

  1. Added a “List of Tasks” section in addition to the standard table of contents.
  2. In the “Installing a Cb Response Server” chapter, added a caution note indicating that the home directory of the cb service account must be /var/cb. Otherwise, critical files will not be found during upgrade.
  3. In the “Installing a Cb Response Server” chapter, edited the “Upgrading Cluster Nodes” section to describe new behavior in the cbcluster start and cbupgrade commands related to the presence of RPMNEW files.
  4. In the “Installing a Cb Response Server” chapter, edited the “Upgrading Cluster Nodes” section to indicate that “iptables” has been replaced by “firewall” for this release in the cbcheck command, and the relevant cb.conf setting has also been changed to “ManageFirewall”.
  5. In the “Installing a Cb Response Server” chapter, edited the “To install and initialize a new server” procedureto show a new yum baseurl and correct the syntax for the RPM license filename.
  6. In the "Uninstalling a Cb Response Server" section, made changes to the list of files that must be manually removed to complete a server uninstall procedure. This change was made because of product changes, include the upgrade of the Python version in Cb Response to 2.7. [CB-18079]
  7. In the “Ports and Protocols” chapter, the API port (default=443) for master-to-minion communication has been added. [CB-16951]
  8. In the "Server Backup and Restoration" chapter, several corrections have been made [CB-17344, CB-18129]:
  • Removed erroneous "sfd" in the backup procedure for Yum files.
  • Removed Logrotate steps, which are no longer relevant.
  • Removed RabbitMQ cookie step, which is no longer relevant.
  • Corrected a missing dash (was single, should be double) before selinux in the command for Cb installer backups.
  • Corrected the note associated with the Postgres Database step -- the step is relevant when doing a configuration-only backup, not a full backup.
  • Removed multiple obsolete statements and steps that described matching the number of Solr data shards on the server to be restored with those on the backup image.
  • In the Restore Postgres database step, removed pg_catalog.setval('sensor_activity_id_seqsensor_comm_failures_id_seq', 1, false);, which is no longer valid.
  • Removed a step for clearing purge times in the restore section.
  • In the "Configuration Restore" section, updated instructions for acquiring a new server token to include the path to the correct version of python (/usr/share/cb/virtualenv/bin/python). Without the path, this step will point to the wrong python version and cause the command to fail.
Article Information
Author:
Creation Date:
‎11-14-2018
Views:
813