# Interface Availability UNINITIALZED

**URL:** <https://community.f5.com/t/interface-availability-uninitialzed/30629>\
**Category:** Technical Forums\
**Tags:** devops, big-ip\
**Created:** [August 8, 2018, 7:14am UTC](https://community.f5.com/t/interface-availability-uninitialzed/30629 "2018-08-08T07:14:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Montasir\_Shovon](https://avatars.discourse-cdn.com/v4/letter/m/7bcc69/32.png) [@Montasir\_Shovon](https://community.f5.com/u/Montasir_Shovon)\
**Post date:** [August 8, 2018, 7:14am UTC](https://community.f5.com/t/interface-availability-uninitialzed/30629/1 "2018-08-08T07:14:13Z")

</div>

**BIG-IP(i5000s/i5800) Model hardware shows Interface Availability UNINITIALIZED. What is the meaning of this status & How can be it UP?**

---

<div class="post-metadata">

**Author:** ![KevinA\_246454](https://avatars.discourse-cdn.com/v4/letter/k/b19c9b/32.png) [@KevinA\_246454](https://community.f5.com/u/KevinA_246454)\
**Post date:** [August 8, 2018, 9:08am UTC](https://community.f5.com/t/interface-availability-uninitialzed/30629/2 "2018-08-08T09:08:18Z")

</div>

I have not seen this on the physical appliance. But for what is worth in the VE edition when a interface is uninitialized its because there is no vlan associated with the interface. Maybe check your logs system and ltm.

---

<div class="post-metadata">

**Author:** ![Montasir\_Shovon](https://avatars.discourse-cdn.com/v4/letter/m/7bcc69/32.png) [@Montasir\_Shovon](https://community.f5.com/u/Montasir_Shovon)\
**Post date:** [August 19, 2018, 5:33am UTC](https://community.f5.com/t/interface-availability-uninitialzed/30629/3 "2018-08-19T05:33:17Z")

</div>

Thank You.

---

<div class="post-metadata">

**Author:** ![youssef1](https://avatars.discourse-cdn.com/v4/letter/y/ed655f/32.png) [@youssef1](https://community.f5.com/u/youssef1)\
**Post date:** [August 19, 2018, 2:54pm UTC](https://community.f5.com/t/interface-availability-uninitialzed/30629/4 "2018-08-19T14:54:54Z")

</div>

Hi,

I already had this kind of behaviour but the problem is not comming from my conf but (Network Part).

So as told you Kevin, check that you configured a vlan with a specific Intervace number. Then if the problem persist check with network team that your interface is connected with right settings in netork side.

we often have this problem on the VE part: [https://devcentral.f5.com/questions/interfaces-uninitialized](https://devcentral.f5.com/questions/interfaces-uninitialized)

Maybe this post can help you. and as you can noticed it wad due to Network configuration (wrong vlan or wrong configuration…)

Got it working for Virtualbox in the ltm log I had the error message “unable to attatch to pci device” The default when adding a network interface in Virtualbox is “PCnet-FAST III”. I changed it to “Intel PRO/1000 MT Server” and now it works fine. Couldn’t find how to change the type of nework interface in vmware workstation so my problem still remains there.

So first of determine that network configuration is right (Speed, vlan, that you can see mack address of the swich…)

Regards