Setup Guide C5000
Setup Guide C5000
Setup Cluster 6
Rack the Cohesity Cluster 6
Cable the Cohesity Cluster C5000 Series 6
Verify Cluster Setup Prerequisites 23
Set Up Nodes 24
Initial Cluster Creation 25
Configure the Primary or Secondary Network in Cohesity cluster with Multicast
Disabled 30
Record Chassis Information 31
Post-Deployment Tasks 32
Change the Default Admin Password 32
Configure Cluster (Required) 34
Verify Cluster Capacity 34
Upgrade the Cluster 34
Check the Resolution of the Cluster FQDN 34
Additional Documentation 35
Cohesity Support 38
Reach Cohesity Support 38
Reach Cohesity Support by Email 38
Support/Service Assistance 38
Cohesity Software Running on Partner Hardware 39
Documentation Feedback 40
Pre-Setup Tasks
The section includes the following pre-setup topics:
Required Cohesity Software Version 4
Verify Network Requirements 4
Fill Out Worksheets 5
Note: This list assumes a Cohesity cluster with four nodes. Adjust the numbers to
reflect your Cohesity cluster.
l Reserve IP addresses for the nodes in the cluster on a single subnet (the cluster
subnet). Most hardware platforms require two IP addresses for each node. For
example, if you have a four node cluster, reserve eight IP addresses—four for node
IP addresses and four for VIP addresses.
l Open firewall ports to allow the Cohesity cluster to transmit and receive data. For
more information, see Manage Firewall Ports.
l Verify that the cluster subnet can communicate with the source's subnet.
l Reserve high speed ports (one for each node) on one switch. Minimum of 10GbE
required.
l Reserve high speed ports (one for each node) on another switch. Minimum of 10GbE
required.
l Reserve IP addresses for the IPMI interfaces. Most hardware platforms require one
IP address for each node. All the IPMI IP addresses must be in the same subnet,
either in the IPMI subnet or the cluster subnet.
l Reserve 1GbE ports (one for each node) for the IPMI or iRMC Interfaces on a switch.
For more information on Networking Requirements, see Cohesity Networking Quick Start
Guide.
Setup Cluster
The section includes the following initial cluster setup topics:
Rack the Cohesity Cluster 6
Cable the Cohesity Cluster C5000 Series 6
Verify Cluster Setup Prerequisites 23
Set Up Nodes 24
Initial Cluster Creation 25
Configure the Primary or Secondary Network in Cohesity cluster with Multicast
Disabled 30
Record Chassis Information 31
Important: Cohesity recommends two people lift the system into the rack rails.
Note: The C5000 Series has 40GB NICs SKUs. Please note that 4X10G breakout
cables are not supported on the C5000 Series platform.
When you receive your Cohesity C5000 Series appliance, you will find the SFP+ NICs
installed in the PCIe slot. When you set up your appliance, you will use ports P1 and P2 to
create bond0.
The following table enumerates the port numbering on the NIC cards.
P4 P3 P2 P1
1. Connect four network cables to the 10GbE ports of a single switch. Connect the other
ends of the four network cables to the left 10GbE ports of the Cohesity cluster as
shown in the figure above. Note that you can substitute a Fiber Optic SFP+ cable for
the coaxial cable.
2. Connect four network cables to the 10GbE ports of a different switch as shown in the
figure above. Connect the other ends of the four network cables to the right 10GbE
ports of the Cohesity cluster.
3. Connect the four blue Cat 6 network cables to 1GbE ports in a switch as shown in the
figure above. Connect the other ends of the cables to the IPMI 1GbE ports in the
Cohesity cluster.
4. Connect the power cables to two different power sources.
Note: Cohesity does not recommend having a Cohesity cluster with a mixture of
nodes with SFP+ 10GbE ports and nodes with RJ45 10GbE ports. This is currently
an untested configuration.
The following table enumerates the port numbering on the NIC cards.
P1 P2 P3 P4
1. Connect four Cat 6 network cables to the RJ45 10GbE ports of a single switch. Connect
the other ends of the four Cat 6 network cables to the left RJ45 10GbE ports of the
Cohesity cluster as shown in the figure above. (These Cat 6 network cables are
represented in black in the preceding figure. The actual Cat 6 cables shipped with the
Cohesity cluster may be a different color.)
2. Connect four Cat 6 network cables to the RJ45 10GbE ports of a different switch as
shown in the figure above. Connect the other ends of the four Cat 6 network cables to
the right RJ45 10GbE ports of the Cohesity cluster. (These Cat 6 network cables are
represented in black in the preceding figure. The actual Cat 6 cables shipped with the
Cohesity cluster may be a different color.)
3. Connect four Cat 6 network cables to 1GbE ports in a switch as shown in the figure
above. Connect the other ends of the cables to the IPMI 1GbE ports in the Cohesity
cluster. (These Cat 6 network cables are represented in blue in the preceding figure.)
Note: In the figure above, the IPMI ports are connected to a switch in a
different VLAN than the RJ45 10GbE switches. However, you may choose to
connect the IPMI cables into dedicated 1GbE switch(es) or you can connect
the IPMI cables into same RJ45 10GbE switches used for the primary and
secondary network.
Note: Cohesity does not recommend having a Cohesity cluster with a mixture of
nodes with SFP+ 10GbE ports and nodes with RJ45 10GbE ports. This is currently
an untested configuration.
The following table enumerates the port numbering on the NIC cards.
P4 P3 P2 P1
1. Connect four SFP28 network cables to the SFP28 25GbE ports of a single switch.
Connect the other ends of the four SFP28 network cables to the left SFP28 25GbE
ports of the Cohesity cluster as shown in the figure above. Note that you can
substitute a Fiber Optic SFP28 cable for the coaxial cable.
2. Connect four SFP28 network cables to the SFP28 25GbE ports of a different switch as
shown in the figure above. Connect the other ends of the four SFP28 network cables
to the right SFP28 25GbE ports of the Cohesity cluster.
3. Connect the four blue Cat 6 network cables to 1GbE ports in a switch as shown in the
figure above. Connect the other ends of the cables to the IPMI 1GbE ports in the
Cohesity cluster.
4. Connect the power cables to two different power sources.
The following table enumerates the port numbering on the NIC cards.
P2 P1
1. Connect four QSFP+ network cables to the QSFP+ 40GbE ports of a single switch.
Connect the other ends of the four QSFP+ network cables to the left QSFP+ 40GbE
ports of the Cohesity cluster as shown in the figure above. Note that you can
substitute a Fiber Optic SFP+ cable for the coaxial cable.
2. Connect four QSFP+ network cables to the QSFP+ 40GbE ports of a different switch as
shown in the figure above. Connect the other ends of the four QSFP+ network cables
to the right QSFP+ 40GbE ports of the Cohesity cluster.
3. Connect the four blue Cat 6 network cables to 1GbE ports in a switch as shown in the
figure above. Connect the other ends of the cables to the IPMI 1GbE ports in the
Cohesity cluster.
4. Connect the power cables to two different power sources.
Note:
l Cohesity does not recommend having a Cohesity cluster with different
network configurations. All nodes in a cluster should have a similar
network configuration and connections.
l Nodes with Cohesity Data Cloud and 100GbE or 40GbE ports do not
support QSFP28/+ to 4xSFP28/+ breakout cables.
The following table enumerates the port numbering on the NIC cards.
P2 P1
1. Connect four QSFP28 network cables to the QSFP28 100GbE ports of a single switch.
Connect the other ends of the four QSFP28 network cables to the left QSFP28 100GbE
ports of the Cohesity cluster as shown in the figure above. Note that you can
substitute a Fiber Optic SFP+ cable for the coaxial cable.
2. Connect four QSFP28 network cables to the QSFP28 100GbE ports of a different switch
as shown in the figure above. Connect the other ends of the four QSFP28 network
cables to the right QSFP28 100GbE ports of the Cohesity cluster.
3. Connect the four blue Cat 6 network cables to 1GbE ports in a switch as shown in the
figure above. Connect the other ends of the cables to the IPMI 1GbE ports in the
Cohesity cluster.
4. Connect the power cables to two different power sources.
Note: Nodes with Cohesity Data Cloud and 100GbE or 40GbE ports do not
support QSFP28/+ to 4xSFP28/+ breakout cables.
5.
The following table enumerates the port numbering on the NIC cards.
P2 P1
1. Connect four SFP+ network cables to the SFP+ 10GbE ports of a single switch.
Connect the other ends of the four SFP+ network cables to the left SFP+ 10GbE ports
of the Cohesity cluster as shown in the figure above. Note that you can substitute a
Fiber Optic SFP+ cable for the coaxial cable.
2. Connect four SFP+ network cables to the SFP+ 10GbE ports of a different switch as
shown in the figure above. Connect the other ends of the four SFP+ network cables to
the right SFP+ 10GbE ports of the Cohesity cluster.
3. Connect the four blue Cat 6 network cables to 1GbE ports in a switch as shown in the
figure above. Connect the other ends of the cables to the IPMI 1GbE ports in the
Cohesity cluster.
4. Connect the power cables to two different power sources.
The following table enumerates the port numbering on the NIC cards.
P2 P1
1. Connect four SFP28 network cables to the SFP28 25GbE ports of a single switch.
Connect the other ends of the four SFP28 network cables to the left SFP28 25GbE
ports of the Cohesity cluster as shown in the figure above. Note that you can
substitute a Fiber Optic SFP28 cable for the coaxial cable.
2. Connect four SFP28 network cables to the SFP28 25GbE ports of a different switch as
shown in the figure above. Connect the other ends of the four SFP28 network cables
to the right SFP28 25GbE ports of the Cohesity cluster.
3. Connect the four blue Cat 6 network cables to 1GbE ports in a switch as shown in the
figure above. Connect the other ends of the cables to the IPMI 1GbE ports in the
Cohesity cluster.
4. Connect the power cables to two different power sources.
l Ensure that you have a 34'' deep rack to install a C5000 Series hardware model.
l Ensure that the 10GbE port that you connect to and the Cohesity cluster
nodes' NIC connections are within the same VLAN or broadcast domain.
l Ensure that the switch supports multicast (required for Cohesity's auto-discovery
function).
l The laptop used to configure the Cohesity cluster must be configured with one NIC
only. If the laptop has multiple NICs configured, disable all but one to set up the
Cohesity cluster.
l OS X requirements:
l Bonjour (for Windows, which provides mDNS service discovery to resolve the
name)
l Safari browser (for Mac OS)
l Using the figure below, locate and pull out the serial number tab and record the
Cluster Setup S/N.
Set Up Nodes
After you verify that all prerequisites are met, you can set up the nodes that will be part of
the Cohesity cluster.
To set up Nodes for the Cohesity cluster:
http://chassis-SN-node-1.local/
the confirmation. If prompted, type the system administrator password for the
laptop.
5. The first page shows the number of chassis and nodes that were discovered. This
page also lists the requirements for setting up the Cohesity cluster.
Ensure that you have all the necessary information and click Get Started.
See Node Detection and Cluster Creation Issues if no node is detected.
6. Select the nodes you want to set up. Click Select all available to select all available
nodes, or select the corresponding check boxes. The node that you are connected to is
automatically selected. You need a minimum of three nodes to create a Cohesity
cluster.
Click Select Nodes to continue.
See Node Detection and Cluster Creation Issues if some nodes are not displayed.
7. The Set Up Nodes page shows all nodes that you selected. Using the information from
your completed worksheet, fill in all IP and IPMI IP fields.
Click Continue to Cluster Settings.
Note: Ensure that the MTU is set with the same value end to end and there is no
mismatch.
Cluster Name Specify a unique name for the Cohesity cluster. Only alphanumeric characters and hyphens
are allowed. A hyphen cannot be the first or last character. Length cannot exceed 32
characters. No other characters are allowed.
Cluster Subnet Specify the IP address of the subnet gateway for the Cohesity cluster.
Gateway
Cluster Subnet Specify the subnet mask for the subnet that the Cohesity cluster is a part of.
Mask
IPMI Subnet Specify the IP address of the Subnet Gateway for the IPMI or iRMC network interfaces.
Gateway
Note: From 6.5.1 release onwards, configuring IPMI while creating a Cohesity
(Optional from
cluster is optional. You can either specify the IPMI configuration while creating
6.5.1 release and
the Cohesity cluster or after creating the cluster.
later)
IPMI Subnet Specify the Subnet Mask for the IPMI or iRMC Subnet.
Mask
(Optional from
6.5.1 release and
later)
IPMI Username Specify the IPMI username to connect to the IPMI interface for each of the nodes in the
Cohesity cluster. The cluster uses the IPMI username to get system health information
(Optional from
about the nodes in the cluster.
6.5.1 release and
later) All nodes in the cluster must use the same IPMI username and IPMI password.
Only alphanumeric characters and hyphens are allowed, but a hyphen cannot be the first
character. The length cannot exceed 32 characters.
l The Cohesity cluster does not depend on the IPMI configuration to get system
health information about the nodes. For ease of managing the nodes remotely, you
can configure IPMI.
l The IPMI username and password can be set for each node in the cluster and can
be different than the IPMI credentials configured for the cluster. The username
length should not exceed 16 characters.
IPMI Password Specify the IPMI password to connect to the IPMI interface for each node in the Cohesity
cluster.
(Optional from
6.5.1 release and All nodes in the cluster must use the same IPMI username and IPMI password.
later)
The password can be 8 to 16 characters. It cannot include the following characters: dollar
sign ($), asterisk (*), quote ("), single quote (`) or backslash (\).
Cohesity recommends to change the default password after creating the cluster. For more
information, see Change the Default Admin Password.
The IPMI password can be set for each node in the cluster, and the password can be
different from the IPMI password configured for the cluster. The password can be 8 to 16
characters. It can include at least the following three characters:
l Upper case
l Lower case
l Numbers
DNS Servers The IP addresses of the Domain Name System (DNS) servers that the Cohesity cluster
should use. Separate multiple IPs with commas. Ensure that the Active Directory DNS IP
address (if applicable) is listed first. Verify that the specified DNS server can resolve the
NTP servers and other entities in the system.
NTP Servers Cohesity recommends using the external Google Public Network Time Protocol (NTP)
server and specifying multiple servers ( time1.google.com, time2.google.com,
time3.google.com, time4.google.com). Avoid using the pool.ntp.org or
time.nist.org NTP servers, as they are sometimes unavailable and their IP addresses
tend to change. If using an internal NTP server, use only one server (and no external
servers). Specify the IP address or the Fully Qualified Domain Name of the NTP server(s).
The Cohesity cluster uses the specified NTP server to synchronize the time on all nodes in
the cluster.
Also, toggle on Use Authentication Key to secure the communication between the
NTP server and the Cohesity cluster. In the Key ID field, enter the Key id associated with
the SHA-1 key and in the Key field, enter the SHA-1 key.
Configure Apps Specify the private IPv4 address for the app subnets. The default IP 192.168.0.0/16 is used
management for app subnets. If the default IP 192.168.0.0/16 is allocated to a node network, cluster
network (From network, or any other network, provide any other private network IP range.
7.0 release
Only a private IP range with a minimum subnet size /24 and a maximum subnet size /12 is
onwards)
supported.
The Cohesity cluster supports AES256 software encryption. The Cohesity cluster
provides a built-in Key Management Service (KMS) that automatically generates
keys.
After Encryption is turned on, the following options are available:
a. The Rotation Period is how often the Cohesity cluster's encryption key is
rotated. After the time period is reached, the old encryption key is replaced by
a new key and the data on the Cohesity cluster remains as it was originally
encrypted. The Rotation Period default value is 30 days. You can change this to
the desired value.
b. Toggle FIPS on to operate the Cohesity cluster under Federal Information
Processing Standard 140-2 certification.
3. A partition and default Storage Domain are created automatically. Cohesity adds all
currently selected nodes to the partition.
l Specify a fully qualified domain name (FQDN). For a Cohesity cluster hosted
directly on Cohesity hardware, specify a FQDN that DNS round robin resolves to
the specified VIPs.
In situations where the customer has not yet added the FQDN with VIPs to DNS,
in versions 6.4 and later, enter the FQDN but do not add the VIPs (see next
point).
Note: Best practice warrants a DNS entry for the cluster's FQDN and
VIPs to achieve optimum cluster performance.
5. Wait several minutes to allow services to restart, and then click the displayed URL
and log in to the Cohesity cluster using the default System Admin account called
admin, and the default password, admin.
6. Accept the license agreement. Then you will be asked to validate the license either by
connecting to Helios or deploying On Prem and providing the license key. If you do
not already have a valid license key, see How to Apply a Cohesity License Key to
Activate a Cluster. Cohesity Support portal credentials are required.
From 6.4.1 release onwards, perform the following steps:
l Read the EULA License Agreement and click Agree.
l Select SaaS or On Prem configurations and click Connect.
For more information on licensing feature, see Cohesity License.
7. In the Change Password dialog box, enter and confirm the new password for the
System Admin account. The minimum length of the password must be 8 characters.
An Overview Dashboard page displays.
See Node Detection and Cluster Creation Issues if the cluster creation process is
stuck or succeeds with warnings. If Cohesity detects an issue, make corrections
before continuing.
After you see the Overview Dashboard page, the next step is to configure the Cohesity
cluster.
1. Configure networking on each node using the configure_network.sh script and the
iris_cli. In general, using the iris_cli is preferred if available. For more details, see
Networking Workflows.
2. Run the following command in the iris_cli to create a Cohesity cluster:
For example:
For more information on Networking Requirements, see Cohesity Networking Quick Start
Guide.
l To check the cluster creation status using the CLI, see the How to check or monitor
the status of Cluster creation KB article.
l To check the cluster creation status using the Cohesity cluster, do the following:
l Log in to the Cohesity cluster and navigate to Settings > Summary.
l Verify the Cohesity cluster details on the Summary page.
Post-Deployment Tasks
The section includes the following post-deployment topics:
Change the Default Admin Password 32
Configure Cluster (Required) 34
Verify Cluster Capacity 34
Upgrade the Cluster 34
Check the Resolution of the Cluster FQDN 34
Additional Documentation 35
Note: Cohesity recommends changing the iLO default credentials. For more
information, see iLO Default Credentials.
Using the Cohesity UI or Cohesity CLI, you can set the password for the support user. You
cannot retrieve the password once it is set. Therefore, ensure that you set a strong
password that is longer and easy to remember. In case, if you want to reset the support
user password and have forgotten the existing password then
To set the support user password:
3. Toggle the button for Sudo Access depending on the user requirement. For more
information, see Enable or Disable Linux Sudo Access.
Also, from the Cohesity CLI, you can use the following iris_cli command to change the
support user password:
Without sudo access, the support user has read-only access privilege and limited read-write
access privilege. To perform advanced operations that require privileged access, you need
to enable Linux sudo access to the support user account.
Note: Apart from the admin user, if you use a local user account to enable Linux
sudo access to the support user, ensure that you configure the local user account
with Manage Linux user sudo access privilege.
Also, from the Cohesity CLI, you can use the following iris_cli command to enable Linux
sudo access for the support user:
Tip: For detailed information about cluster security, see Cohesity Security
Hardening Guide.
1. Start a browser and enter the Cohesity cluster domain name in the browser address
bar.
2. Log in to the Cohesity cluster.
3. Select System > Storage and verify that the available storage.
1. Securely connect (SSH) in to the hypervisor host that is going to mount the view.
2. Ping the FQDN you specified for the cluster:
ping <myClusterFQDN>
If packets are received and the request does not time out, the FQDN was found. If the
request times out, fix the networking problem.
Additional Documentation
For more information about using the Cohesity cluster, Cohesity features and the Cohesity
command line interface, visit docs.cohesity.com.
l Multicast is enabled on the network switch that the Cohesity cluster Nodes are
connected to.
l All of the following are reachable from the network switch:
l Default gateway
l DNS server
l NTP server
Resolution
No Node is Detected
Possible cause
The network switch configuration prevented mDNS from being received/transmitted.
Resolution
Attempt to connect the laptop to another Node's management port to narrow down which
network cable, switch port, or Node network port has an issue so you can resolve it.
Resolution
Once the connectivity issue is resolved, setup should proceed.
Cohesity Support
l Email Cohesity Support with a brief description of the problem. If the Cohesity
software is running on a hardware platform, include your product's chassis serial
number.
l Log in to the Cohesity Support Portal. Click OPEN CASES and Create Case.
l On the Cohesity UI, click Support that appears in the footer.
1. Mention CCS in the subject and select CCS as the Issue Type.
2. Provide the case information.
3. Edit the Case Subject as CCS (AWS_Region): <Input Issue Subject
Information>.
4. Update the Issue Type field to CCS.
Additionally, provide the Cluster ID and the Support Token information if a SaaS
connector is involved.
Support/Service Assistance
First contact the Service Provider that you have contracted for service and support. If you
work directly with Cohesity and have a product warranty/entitlement, repair pricing or
technical support related question, see your options below:
l To find solutions to your product issues or for suggestions or best practices, visit
Cohesity Knowledge Base.
l To open a Service Request online, go to Cohesity Support Portal, log in to the portal,
and go to My Cohesity > Submit a Case.
l To monitor your open cases, log in to the portal, click My Cases on the upper right
side of the home page. This page should have all the case statuses and updates. You
can also view individual case status.
1. The customer may contact Cohesity Support first if the issue cannot be determined as
a hardware issue.
Documentation Feedback
We encourage you to provide feedback so that we can improve our documentation. Click
here to send us your feedback!
Ensure that you provide the following details in your email:
l Document name
l Topic name
l Page number