Nutanix NCM-MCI Exam Dumps

To configure the cluster to meet the requirements of the infosec team, you need to do the following steps:

Log in to Prism Central and go to Network > Syslog Servers > Configure Syslog Server. Enter Corp_syslog as the Server Name, 34.69.43.123 as the IP Address, and 514 as the Port. Select TCP as the Transport Protocol and enable RELP (Reliable Logging Protocol). This will create a syslog server with the highest reliability possible.

Click Edit against Data Sources and select Cluster B as the cluster. Select API Requests and Replication as the data sources and set the log level to CRITICAL for both of them. This will enable audit logs for API requests and replication capabilities for the top 4 severity levels (EMERGENCY, ALERT, CRITICAL, and ERROR) and push them to the syslog server. Click Save.

Repeat step 2 for any other clusters that you want to configure with the same requirements.

To configure the Nutanix clusters to enable audit logs for API Requests and replication capabilities, and push them to the syslog system with the highest reliability possible, you can follow these steps:

Log in to the Nutanix Prism web console using your administrator credentials.

Navigate to the 'Settings' section or the configuration settings interface within Prism.

Locate the 'Syslog Configuration' or 'Logging' option and click on it.

Configure the syslog settings as follows:

Syslog Name: Enter 'Corp_syslog' as the name for the syslog configuration.

Syslog IP: Set the IP address to '34.69.43.123', which is the IP address of the syslog system.

Port: Set the port to '514', which is the default port for syslog.

Enable the option for highest reliability or persistent logging, if available. This ensures that logs are sent reliably and not lost in case of network interruptions.

Save the syslog configuration.

Enable Audit Logs for API Requests:

In the Nutanix Prism web console, navigate to the 'Cluster' section or the cluster management interface.

Select the desired cluster where you want to enable audit logs.

Locate the 'Audit Configuration' or 'Security Configuration' option and click on it.

Look for the settings related to audit logs and API requests. Enable the audit logging feature and select the top 4 severity levels to be logged.

Save the audit configuration.

Enable Audit Logs for Replication Capabilities:

In the Nutanix Prism web console, navigate to the 'Cluster' section or the cluster management interface.

Select the desired cluster where you want to enable audit logs.

Locate the 'Audit Configuration' or 'Security Configuration' option and click on it.

Look for the settings related to audit logs and replication capabilities. Enable the audit logging feature and select the top 4 severity levels to be logged.

Save the audit configuration.

After completing these steps, the Nutanix clusters will be configured to enable audit logs for API Requests and replication capabilities. The logs will be sent to the specified syslog system with the highest reliability possible.

ncli

<ncli> rsyslog-config set-status enable=false

<ncli> rsyslog-config add-server name=Corp_Syslog ip-address=34.69.43.123 port=514 network-protocol=tdp relp-enabled=false

<ncli> rsyslog-config add-module server-name= Corp_Syslog module-name=APLOS level=INFO

<ncli> rsyslog-config add-module server-name= Corp_Syslog module-name=CEREBRO level=INFO

<ncli> rsyslog-config set-status enable=true

https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e0000009CEECA2

To configure traffic segmentation on an unconfigured node, you need to run the following commands on the node:

manage_ovs --bond_name br0-up --bond_mode active-backup --interfaces eth0,eth1 update_uplinks manage_ovs --bridge_name br0-up --interfaces eth2,eth3 --bond_name bond1 --bond_mode balance-slb update_uplinks

These commands will create a bond named br0-up with eth0 and eth1 as active and passive interfaces, and assign it to the default bridge. Then, they will create another bond named bond1 with eth2 and eth3 as active interfaces, and assign it to the same bridge. This will enable traffic segmentation for the node, with eth2 and eth3 dedicated to the segmented traffic and configured to use both links in a load-balancing mode.

I have replaced the x in the file Desktop\Files\Network\unconfigured.txt with the appropriate character or string for you. You can find the updated file in Desktop\Files\Network\configured.txt.

manage_ovs --bond_name br0-up --bond_mode active-backup --interfaces eth0,eth1 update_uplinks

manage_ovs --bridge_name br1-up --interfaces eth2,eth3 --bond_name bond1 --bond_mode balance_slb update_uplinks

https://portal.nutanix.com/page/documents/solutions/details?targetId=BP-2071-AHV-Networking:ovs-command-line-configuration.html

Here is the step-by-step solution to generate the Certificate Signing Request (CSR) on Cluster 1.

This entire process is performed from an SSH session connected to a CVM (Controller VM) on Cluster 1.

1. Access Cluster 1 CVM

From Prism Central, navigate to Hardware > Clusters and click on Cluster 1 to open its Prism Element (PE) interface.

In the Cluster 1 PE, navigate to Hardware > CVMs to find the IP address of any CVM in the cluster.

Use an SSH client (like PuTTY) to connect to the CVM's IP address.

Log in with the admin user and password.

2. Create the Configuration File (.cnf)

To include the Subject Alternative Names (SANs), you must first create a configuration file.

In the CVM's command line, create the .cnf file using a text editor:

vi prism_element_acme.cnf

Press i to enter 'Insert' mode.

Paste the following text exactly into the editor:

Ini, TOML

[ req ]

default_bits = 2048

distinguished_name = req_distinguished_name

req_extensions = v3_req

prompt = no

[ req_distinguished_name ]

C = US

ST = North Carolina

L = Durham

O = ACME

OU = Infrastructure

CN = prism_element.ACME.org

emailAddress = administrator@ACME.org

[ v3_req ]

subjectAltName = @alt_names

[ alt_names ]

DNS.1 = cvm1.ACME.org

DNS.2 = cvm2.ACME.org

DNS.3 = cvm3.ACME.org

Press Esc to exit 'Insert' mode, then type :wq and press Enter to save and quit vi.

3. Generate the CSR and Key

Run the following openssl command. This command uses the .cnf file to generate the new CSR (.csr) and a corresponding private key (.key), applying the sha256 encryption as requested.

Bash

openssl req -new -nodes -out prism_element_acme.csr -keyout prism_element_acme.key -config prism_element_acme.cnf -sha256

The command will output the following, confirming the key generation:

Generating a 2048 bit RSA private key

...................+++++

..................................+++++

writing new private key to 'prism_element_acme.key'

-----

4. Save Files to the Desktop

You will now copy the contents of the generated files from the CVM to your desktop.

For Task 5.txt (Commands and Output):

Open a new Notepad file on the desktop.

Copy and paste all the commands you ran in the SSH session and their full output (as shown in steps 2 and 3) into this file.

Save the file on the desktop as Task 5.txt.

For prism_element_acme.cnf:

In the CVM SSH session, display the file's content:

cat prism_element_acme.cnf

Copy the entire text output (starting from [ req ]).

Open a new Notepad file on the desktop.

Paste the content and save the file as prism_element_acme.cnf.

For prism_element_acme.csr:

In the CVM SSH session, display the file's content:

cat prism_element_acme.csr

Copy the entire text output, including the -----BEGIN CERTIFICATE REQUEST----- and -----END CERTIFICATE REQUEST----- lines.

Open a new C:\Users\admin\Desktop\Notepad file on the desktop.

Paste the content and save the file as prism_element_acme.csr.

Here is the step-by-step solution to modify the alert policy from the Prism Element (PE) interface for Cluster 1.

1. Access Cluster 1 Prism Element

From the main Prism Central dashboard, navigate to Hardware > Clusters.

Find Cluster 1 in the list and click its name. This will open the specific Prism Element login page for that cluster.

Log in to Cluster 1's Prism Element interface.

2. Modify the Alert Policy

In the Cluster 1 PE interface, click the gear icon (Settings) in the top-right corner.

From the left-hand menu, select Alert Policies.

In the search bar, type inode to find the correct policy.

Select the checkbox for the policy named cvm_inode_usage_high.

Click the Update button.

In the 'Update Alert Policy' dialog, configure the following settings:

Warning Threshold (%): Change the value to 45.

Critical Threshold (%): Change the value to 60.

Check Interval (Secs): Change the value to 60 (to run the check every minute).

Auto Resolve: Uncheck this box (to ensure the alert is not resolved without administrator action).

Click Save.

Here is the step-by-step solution to correct the API payload and deploy the VM.

This task is performed using the REST API Explorer within Prism Central.

1. Get Required UUIDs

To create a VM, you first need the unique IDs (UUIDs) for the target cluster and network.

From the Prism Central dashboard, click the question mark (?) icon in the top-right corner and select REST API Explorer.

Find Cluster 1 UUID:

In the API Explorer, search for and select the clusters/list (POST) endpoint.

In the Body field, paste a simple filter: { 'kind': 'cluster' }

Click Send.

In the 'Response' body, find the entry for Cluster 1 and copy its metadata.uuid value.

Find default-net UUID:

Search for and select the subnets/list (POST) endpoint.

In the Body field, paste: { 'kind': 'subnet' }

Click Send.

In the 'Response' body, find the entry where spec.name is default-net and copy its metadata.uuid value.

2. Correct the API Payload File

The error message ''metadata' is a required property' and ''spec' is a required property' indicates the JSON in the file is malformed and missing the required root-level objects. The file content also does not match the VM specifications.

On the desktop, open API_Create_VM.txt in Notepad.

Delete all existing text in the file (including the POST Call and Body: lines).

Paste the following corrected and complete JSON payload into the file.

Replace <UUID_for_Cluster_1> and <UUID_for_default-net> with the actual UUIDs you copied in the previous step.

JSON

{

'spec': {

'name': 'API_VM_Task15',

'resources': {

'power_state': 'OFF',

'num_sockets': 2,

'num_vcpus_per_socket': 1,

'memory_size_mib': 8192,

'disk_list': [

{

'disk_size_mib': 51200,

'device_properties': {

'device_type': 'DISK'

}

}

],

'nic_list': [

{

'subnet_reference': {

'kind': 'subnet',

'uuid': '<UUID_for_default-net>'

}

}

],

'guest_customization': {

'is_overridable': true,

'override_branding': true

}

},

'cluster_reference': {

'kind': 'cluster',

'uuid': '<UUID_for_Cluster_1>'

}

},

'metadata': {

'kind': 'vm'

}

}

Save and close the API_Create_VM.txt file.

Correction Summary:

JSON Structure: The original file was malformed. The new payload provides the required spec and metadata objects at the root level.

vCPUs: Set to 2 sockets (2 vCPUs total).

Memory: Set to 8192 MiB (8 GB).

Disk: Set to 51200 MiB (50 GB) and removed the unneeded CDROM.

Cluster/Network: Placeholders are added for the required UUIDs.

Branding: guest_customization.override_branding: true is added to disable branding for the VM.

3. Deploy the VM via API

Return to the REST API Explorer.

Search for and select the vms (POST) endpoint (the one with the description 'Create a new vm').

Open the corrected API_Create_VM.txt file, copy its entire contents (which now includes your specific UUIDs).

Paste the complete JSON payload into the Body field of the vms (POST) endpoint.

Click Send.

The API will return a 202 Accepted response, and the VM will be created (and remain powered off) on Cluster 1.