# NSX-T 3.1 Segments in opennebula

**URL:** <https://forum.opennebula.io/t/nsx-t-3-1-segments-in-opennebula/9824>\
**Category:** Installation & Configuration\
**Created:** [August 8, 2021, 7:35pm UTC](https://forum.opennebula.io/t/nsx-t-3-1-segments-in-opennebula/9824 "2021-08-08T19:35:04Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mohammadreza\_ghasemi](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/mohammadreza_ghasemi/32/6672_2.png) [@mohammadreza\_ghasemi](https://forum.opennebula.io/u/mohammadreza_ghasemi)\
**Post date:** [August 8, 2021, 7:35pm UTC](https://forum.opennebula.io/t/nsx-t-3-1-segments-in-opennebula/9824/1 "2021-08-08T19:35:04Z")

</div>

Hi,  
We are moving from NSX-v to NSX-T 3.1, on nsx-v we had no problem with network creation and corresponding network created successfuly in nsx-v portal, but in NSX-T 3.1 each network is a segment that is created in a specific TZ, when we create a nwe network in opennebula 6 which is connected to vCenter 7 and NSX-T 3.1, we can see the corresponding opaque network in vCenter network panel, but nothing is added in NSX-T portal in segment section,  
after searching through the nsx driver we realized that opennebula calls an NSX api “api/v1/logicalswitches” while I think it should call another API to create a segment,  
Can someone help us.

Thank you