Hi, Brian:
       At first, thanks a lot for you help. In our laboratory, the IP 10.2.0.3 
that we found in base_vcpe_vgw.env file, and yes 10.2.0.3 that is allocated by 
sub network vcpe_net_cpe_public_201807060636 in vgw1 instance,  and 10.2.0.1 is 
the vDNS IP that is also allocated by subnetwork 
vcpe_net_cpe_public_201807060636.

      We check out vcpe script and preload_templates files , and we not found  
"the CPE_SIGNALING IP on the vGW via preload. “. And we vDNS, vGw, vbrg’s 
network information are show in there pictures.
     
     the vgw’s network information:

 

      the vdns’s network information:
     

    the vbrg’s network information:
     


     Brian, Kang, please check these network information are right?


     We run vcpe.py customer again in last night, and we found that’s another 
error happened, the error message is  "statusMessage": "Received a Bad Sync 
Response from Sniro/OOF.” That’s seem to we meet different error. So we hope to 
you can provide the running flow after the vcpe script call MSO restful API, 
the url or picture is ok. 







> 在 2018年7月12日,02:13,FREEMAN, BRIAN D <bf1...@att.com> 写道:
> 
> Found the configuration problem on vDNS/vDHCP
>
> https://jira.onap.org/browse/TEST-104 <https://jira.onap.org/browse/TEST-104>
>
> Should have a fix pushed soon but you can also manually fix the config file.
>
> I suspect the heat.yml for the vGW isnt quite right because it works without 
> the DHCP on the CPE_PUBLIC side for the first vGW.
>
> Brian
>
>
> From: FREEMAN, BRIAN D 
> Sent: Wednesday, July 11, 2018 9:59 AM
> To: onap-discuss@lists.onap.org; FREEMAN, BRIAN D <bf1...@att.com>; 
> lcl7...@163.com
> Subject: RE: [onap-discuss] [integration] create another vgw instance error
>
> I think the DHCP on that side of the vGW might not be working correctly.
>
> I checked over the data in the integration environment and test data from 
> Kang and I think we are setting the CPE_SIGNALING IP on the vGW via preload.
>
>                                 {
>                                   "name": "vgw_private_ip_2",
>                                   "value": "10.2.0.5"
>                                 },
>
>
> Add vgw_private_ip_2 to the VGW2BRG-fa:16:3e:8a:bd:93 preload (or whatever 
> your BRG MAC Address is)
>
> And see if that unblocks the second vGW
>
> Brian
>
>
> From: onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org> 
> <onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org>> On Behalf 
> Of FREEMAN, BRIAN D
> Sent: Tuesday, July 10, 2018 11:23 AM
> To: onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org>; 
> lcl7...@163.com <mailto:lcl7...@163.com>
> Subject: Re: [onap-discuss] [integration] create another vgw instance error
>
> ***Security Advisory: This Message Originated Outside of AT&T ***
> Reference http://cso.att.com/EmailSecurity/IDSP.html 
> <http://cso.att.com/EmailSecurity/IDSP.html> for more information.
> 
> Chenglong,
>
> Not sure why the neutron stack is rejecting that create since that IP should 
> be assigned by the vdns VM on the CPE_PUBIC subnet not by the neutron heat 
> stack call.
> BTW the vGW1 should have gotten 10.2.0.2 not 10.2.0.3 if it was the first 
> gateway to come up.
>
> The dhcp addresses on the CPE_PUBLIC subnet are assigned by the vdns VNF and 
> the log file is:
>       "output": "/var/log/kea-dhcp4.log"
>
> Also look in  /var/lib/kea/kea-leases4.csv to see if you are getting the DHCP 
> lease assignments expected.
>
> Kang did get multiple vGW/vBRGs working but he did have to change his scripts 
> for it. He is expected back on Thursday and can probably provide better 
> insight if we cant solve it before then.
>
> Brian
>
>
>
> From: onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org> 
> <onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org>> On Behalf 
> Of Liu Chenglong
> Sent: Monday, July 09, 2018 11:21 PM
> To: onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org>
> Cc: Liu Chenglong <lcl7...@163.com <mailto:lcl7...@163.com>>
> Subject: [onap-discuss] [integration] create another vgw instance error
>
> Hello:
>
>     When we test vcpe use case, we had create a Vxlan tunnel success with a 
> vbrg instance and a vgw named vgw1 instance. So we want to create another 
> VxLANs tunnel. First, we create a new vbrg instance and success.  But there 
> is an error when create the vgw instance named vgw2, the error message is: 
> "Received vfModuleException from VnfAdapter: category='INTERNAL' 
> message='Exception during create VF 0 : Stack error (CREATE_FAILED): Resource 
> CREATE failed: Conflict:      resources.vgw_private_2_port: IP address 
> 10.2.0.3 already allocated in subnet 
> bb73e612-d22c-4537-a978-cf2ac9a7e8be\nNeutron server returns request_ids: 
> ['req-8e0af890-9aa0-47bd-b950-8a cc6378f7dd'] - stack successfully deleted' 
> rolledBack='true'". 
>     The error message show this information "IP address 10.2.0.3 already 
> allocated ", we check the ip address and found that is the first vgw1's ip, 
> so it seems vDHCP instance don't allocate right IP address to vgw2 instance. 
> So we want to know how to find where is ip address allocate and how to solve 
> this error.
>
>
> Regards,
> Chenglong
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11062): https://lists.onap.org/g/onap-discuss/message/11062
Mute This Topic: https://lists.onap.org/mt/23205574/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to