---
title: "ODC Network Issue due to No Second HD"
slug: "odc-network-issue-due-to-no-second-hd"
description: "NetworkDefense/ODC/ready_to_release/HelpCenter"
tags: ["ODC 1.5.22"]
updated: 2023-03-20T06:14:29Z
published: 2023-03-20T06:14:29Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.txone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# ODC Network Issue Due to No Second HD

### Summary

ODC displays default network as ens32 instead of eth0 after installation, and there is no network connection after configuring the IP.

### Applicable Version

ODC 1.5.22

### Scenario 1

1. ODC network does not work after deployment, the network shows ens32 instead of eth0 ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%2854%29.png)
2. Check ODC status with command “env ls” • The error message shows no external disk detected ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%2857%29.png)

### Root Cause

1. ODC checks Hard Disk status before checking interface status
2. ens32 automatically becomes renamed as eth0 after ODC checks the interface status
3. In the virtual machine there is no second Hard Disk assigned to ODC ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%2858%29.png)
4. Since the checking stage gets stuck at the Hard Disk status, ODC is not able to run interface checking to rename the interface; therefore, the network won’t work because the NIC name (ens32) and configuration name (eth0) don’t match ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%2860%29.png)

### Workaround

1. Add a second Hard Disk that has at minimum 50GB of space ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%2862%29.png)
2. Reboot ODC ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%2864%29.png)
3. Check the network status with “iface ls” to make sure the NIC name has changed to eth0 ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%2865%29.png)
4. Check if ODC network is up and running ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%2866%29.png)

### Scenario 2

1. Followed by Scenario 1, after ODC is deployed without a second Hard Disk, ens32 is added to the network configuration with the command “iface add ens32” ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%2867%29.png)
2. Adding a second Hard Disk and rebooting ODC will not cause ens32 to be renamed eth0 since ODC has mapped the NIC (ens32) with the newly created network configuration (ens32)
3. Check ODC status after rebooting with a second Hard Disk added • The error message shows that ODC is checking the system interface’s IP ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%2868%29.png)

### Root Cause

1. ODC needs to have both the NIC, and the network configuration named eth0 to have the network working correctly
2. Since a configuration (ens32) is already mapped, ODC is not able to rename the NIC from ens32 to eth0

### Workaround

1. Remove ens32 from network configuration with the command “iface rm ens32”
2. Reboot ODC, at which point ODC will automatically rename ens32 to eth0 ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%2869%29.png)
3. Check ODC network status and make sure the NIC has been renamed to eth0 ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%2870%29.png)
4. Modify the eth0 network setting and reboot ODC for the changes to take effect
5. Check ODC network connection ![image.png](https://cdn.document360.io/f5889a21-4b9d-49ff-a4a7-03538c6b843a/Images/Documentation/image%2871%29.png)

For support assistance, please Contact Us at support@txone.com or your Support Provider.