JamesStreit
Enthusiast
Enthusiast

Can't add network resource

Jump to solution

Hi all,

Has anyone experienced not being able to add a network resource?

When I try to add a network, the list of port groups is empty.

When I had standard switch port groups, they would show up, but not distributed switch port groups.

The hosts and vCenter are version 6.0

2015-06-06 22.17.13_02.jpg

Thanks

Jim Streit

0 Kudos
1 Solution

Accepted Solutions
jessehuvmw
Enthusiast
Enthusiast

We didn't find the root cause in the logs. As Blake suggested, could you check whether 'Add Network' works in BDE CLI ?

You can login BDE Server as user serengeti ,then execute the following commands:

$ serengeti <ENTER>

serengeti>connect --host localhost:8443

Enter the username: root

Enter the password: ******

Connected

serengeti>network add --name mynetwork --portGroup my_port_group_name --dhcp

Cheers, Jesse Hu

View solution in original post

0 Kudos
13 Replies
jessehuvmw
Enthusiast
Enthusiast

Hi Jim,

BDE will list all port groups in the data center in which BDE vApp is deployed. But Uplink port will be ignored.

Could you check it and also upload the BDE logs for us to debug ?

bde ui log on vCenter Server:   /storage/log/vmware/vsphere-client/logs/vsphere_client_virgo.log

bde server side log on BDE Server:  /opt/serengeti/logs/*.log

Thanks.

Cheers, Jesse Hu
0 Kudos
JamesStreit
Enthusiast
Enthusiast

I've upgrade to BDE 2.2 and I'm getting the same results.

I have another BDE installation in a different cluster that uses standard switches and BDE works fine.

The management server is connected to the distributed switch portgroup, communicates fine and is registered with vCenter.

2015-06-09 10.43.54_02.jpg

Opened SR 15685292806 and have uploaded files.

06/09/2015  09:36 AM               259 ironfan.2015-06-09-14-36-02.log

06/09/2015  09:36 AM               259 ironfan.log

06/09/2015  10:11 AM             2,668 register-plugin.log

06/09/2015  09:37 AM           183,265 serengeti-boot.log

06/09/2015  11:44 AM           860,678 serengeti.log

06/09/2015  09:37 AM             1,591 vhm.log

06/09/2015  11:41 AM        36,975,559 vsphere_client_virgo.log

Thanks

Jim Streit

0 Kudos
JamesStreit
Enthusiast
Enthusiast

Update:  I've tried creating a port group with ephemeral bindings ... same results, empty pull-down.

0 Kudos
jessehuvmw
Enthusiast
Enthusiast

Hi Jim,

Could you grant me the permission to view your SR?  My account id is huhui14@gmail.com . Here is the guide https://ikb.vmware.com/contactcenter/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&external...

Cheers, Jesse Hu
0 Kudos
jessehuvmw
Enthusiast
Enthusiast

I can see the SR now. Please ignore previous comment.

Cheers, Jesse Hu
0 Kudos
zxnblake
Contributor
Contributor

Hi Jim:

Can you try to add the network through CLI? And then upload the new log files?

0 Kudos
jessehuvmw
Enthusiast
Enthusiast

We didn't find the root cause in the logs. As Blake suggested, could you check whether 'Add Network' works in BDE CLI ?

You can login BDE Server as user serengeti ,then execute the following commands:

$ serengeti <ENTER>

serengeti>connect --host localhost:8443

Enter the username: root

Enter the password: ******

Connected

serengeti>network add --name mynetwork --portGroup my_port_group_name --dhcp

Cheers, Jesse Hu
0 Kudos
JamesStreit
Enthusiast
Enthusiast

OK, adding the network from the CLI worked, but it still doesn't explain why the Web UI wasn't showing the port group.  I'll leave the SR open until root cause is found.

I wanted to use just a range of IP’s.  Here is what I ran;

I SSH'd to the Serengeti management server

serengeti

connect --host localhost:8443

network list  (this was empty)

network add --name DPG_2050 --portGroup DPG_2050 --ip 192.168.43.74-83 --dns 192.168.26.2 --gateway 192.168.43.254 --mask 255.255.255.0

network list  (now the network shows up)

Syntax is VERY important … took an extra couple minutes of trying and failing before noticing the capital “G” in portGroup  😉

I was able to successfully create a BDE cluster and I'm now currently running a test teragen job.


Thanks

Jim Streit

0 Kudos
jessehuvmw
Enthusiast
Enthusiast

Glad to know CLI works which means it's an issue of the BDE Web Client.

Is DPG_2050 a distributed switch port groups ?


And the CLI command params (e.g. --portGroup) is case sensitive. If you spell --portgroup, CLI doesn't report error but the value of the param is not used.  This issue is fixed in BDE 2.2.0.

Cheers, Jesse Hu
0 Kudos
selinacui
Contributor
Contributor

Hi Jim,

For the drop down list in web UI, it will query all port groups from VC, but the following port group will not in the list:

  • Uplink port group
  • It is not in the same data center with BDE server
  • It is not associate with any host

Can you describe how you create distributed port group?

Regards,

Selina

0 Kudos
JamesStreit
Enthusiast
Enthusiast

Yes, DPC_2050 is a distributed switch port group.

The installation will see standard switch port groups just fine.

Jim

0 Kudos
JamesStreit
Enthusiast
Enthusiast

Hi Selina,

DPG_2050 is not an uplink port group.

The BDE management server is using the same port group.

All of the hosts are configured identically and have access to the port group.  Other VM's are able to use the port group like normal.  After creating the BDE network resource from CLI I was able to build out a BDE cluster.  All of the VM's used the DPG_2050 port group and communication worked as expected.

2015-06-19 14.58.06_01.jpg

Jim

0 Kudos
selinacui
Contributor
Contributor

Hi Jim,

My distributed port group has the similar setting, but I cannot reproduce your issue. 

If you create that port group in web client, you need add host to the port group. But in window client, all these operations in one wizard. You can verify this step by selecting related objects->hosts. 

Screen Shot 2015-06-23 at 10.27.32 AM.png

Regards,

Selina

0 Kudos