> For the complete documentation index, see [llms.txt](https://docs.cloudeka.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudeka.id/deka-prime/menu-instance/configuration-nics.md).

# Configuration NICs

On the NICs configuration, you can add and delete NICs used by the virtual machine on the instance. There are several types of adapters used.

<table><thead><tr><th width="233">Adapter Type</th><th>Information</th></tr></thead><tbody><tr><td><strong>E1000</strong></td><td>This adapter card is used for compatibility and easy installation on various operating systems.</td></tr><tr><td><strong>E1000E</strong></td><td>This adapter card is a development of the E1000 and is used for high network loads.</td></tr><tr><td><strong>SRIOVETHERNETCARD</strong></td><td>This adapter card allows virtual machines on the Instance to increase network performance and reduceoverhead virtualization.</td></tr><tr><td><strong>VMXNET2</strong></td><td>This adapter card is used for high performance and efficiency, especially in throughput dan latency.</td></tr><tr><td><strong>VMXNET3</strong></td><td>This adapter card is used for high performance and supports many features such as parallel networking, network offloading, and high scalability.</td></tr><tr><td><strong>VMXNET3VRDMA</strong></td><td>This adapter card is used to add Remote Direct Memory Access (RDMA) allowing very fast data transfer without burdening the CPU so it is suitable forhigh throughput andlow latency.   </td></tr></tbody></table>

## Add NICs

The following are the steps for adding a NIC used on a virtual machine in an instance:

* On the NICs page, press the Edit button.

<figure><img src="https://lh7-us.googleusercontent.com/VYWOorlM2HqXohLC0D-eauEHMTIaByWTm1sgo4Jsdqia1m1dh6_jMNPylyUjLQiG_c_YLpJbkIPYFpP95v8zvcTZKeTpds_m2YEH5dO_G4FutCPxXBqYg5fj5_mmIYYBiQPg3SmLcaaAPWpVczTUdws" alt=""><figcaption><p> Add NICs</p></figcaption></figure>

* The NICs for “\[instance-name]” window appears, press the New button.

<figure><img src="https://lh7-us.googleusercontent.com/8n4vqMn9HoI0ztetM0FqmkoTfB2KB6iQhcOfJ0RHb2KI8kiFGBZkD_M8sM6DKeBegpNg7fhvn_4N4jFPpQWJwVFXXbP4-2tGZoT_A1oGsZklh1fl6d6ojS13crqQOnfK3KGQj6CwtfhmzWszMq0tGTc" alt=""><figcaption><p> Add NICs</p></figcaption></figure>

* Determine the Adapter Type, Network used and IP Mode used. Press the Save button to save changes.

<figure><img src="https://lh7-us.googleusercontent.com/kNbEpFvUKx5j6p6WWwKT10QJlAgvxARJubRdW-l9ZyODV1CS9GUKcdUeATQHMbNVIQSIL24uMcJG2KIf8mBX-zpD8JZll4-KYgioKcRLn3mFXlLD2Vxs1JU7aImmDt6ycHbVUQa49u2iFeTYwKAmo5I" alt=""><figcaption><p> Add NICs</p></figcaption></figure>

## Delete NICs

The following are the steps for deleting additional NICs used by an instance:

* Press the Edit button on the NICs Tab page.

<figure><img src="https://lh7-us.googleusercontent.com/99L5MMtvxpTsrl6rR00VMD817_0WSmYMYHmK8QIoLyMQgd3HWFwgPOdps78dsqptCv6-46KH34Y4ULILA4-aYS7ekfY3mthfDfSe8pCQLZgwKdms-ylF_m9-yPHTj0kHUuD2Asg5ehAmssNnIVF1mKY" alt=""><figcaption><p>Delete NICs</p></figcaption></figure>

* The NICs for “\[instance-name]” window appear, select the deleted NIC and press the Delete button to delete the NIC, and press the Save button to save the changes.

<figure><img src="https://lh7-us.googleusercontent.com/1_mzbSU-Efba-wtlWW0OQM2yYQRp_EbqiIfbl77dcy0GmHSv_stB7qrUXcLny1IL5zGdXVKk_KRhYdWXI8_sX4fWUz4h4uXT4vsgEgsBOoXIa82HtZp6L6IGV2Jfd5hW0R_DkPdDtYNWg6tk07RLzH8" alt=""><figcaption><p>Delete NICs</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cloudeka.id/deka-prime/menu-instance/configuration-nics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.