[onap-discuss] 答复: Re: VIM registration failure

[Vitaliy Emporopulo]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 答复: Re: VIM registration failure

[zhao.huabing]

Hi Kiruthiga,


Could you please get log of MSB internal api gateway using "sudo docker logs "? 
 It may help to investigate this issue.






Thanks,


Huabing











原始邮件



发件人： ;
收件人：李滋00164331;
抄送人： ;
日 期 ：2018年02月01日 19:45
主 题 ：Re: [onap-discuss] VIM registration failure


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

 

Hi LiZi,


 


Both AAI and Multicloud services are registered in MSB. But still we are 
getting the same error mentioned in the below mail.


 


All the request to MSB API is resulting in “Bad Gateway error”.  The external 
port of MSB-IAG server is either in CLOSE_WAIT or TIME_WAIT status while 
triggering  MSB API calls. If you could see in the error screenshot, during VIM 
registration request is sent to MSB-IAG server and it gives “Bad Gateway 
error”. Please help in fixing this issue.


 


Regards,


Kiruthiga



 



From: li.z...@zte.com.cn [mailto:li.z...@zte.com.cn] 
 Sent: Thursday, February 1, 2018 4:36 PM
 To: Kiruthiga R 
 Cc: onap-discuss@lists.onap.org
 Subject: Re: [onap-discuss] VIM registration failure




 



This message was identified as a phishing scam.



Feedback

Hi Kiruthiga,

Before you register VIM with ESR GUI, you need register the AAI's service to 
MSB. Also, you need register Multi-Cloud to MSB. You may check the registration 
result with MSB GUI (http://MSB_SERVER_IP/iui/microservices/default.html).  If 
they are not registered, please register with the following command.

 

curl -X POST \

-H "Content-Type: application/json" \

-d '{"serviceName": "aai-cloudInfrastructure", "version": "v11", "url": 
"/aai/v11/cloud-infrastructure","protocol": "REST", "enable_ssl":"true", 
"visualRange":"1", "nodes": [ {"ip": "ESR_SERVER_IP","port": "8443"}]}' \

http://MSB_SERVER_IP:10081/api/microservices/v1/services 

 

curl -X POST -H “Content-Type: application/json” -d ‘{“serviceName”: 
“multicloud”, “version”: “v0”, “url”: “/api/multicloud/v0”,”protocol”: “REST”, 
“nodes”: [ {“ip”: “’$MultiCloud_IP’”,”port”: “9001”}]}’ 
“http://$MSB_SERVER_IP:10081/api/microservices/v1/services“ 

 

Thanks,

LiZi

 

 


原始邮件



发件人： ;



收件人： ;



日 期 ：2018年02月01日 17:55



主 题 ：[onap-discuss]  VIM registration failure




___
onap-discuss mailing list
 onap-discuss@lists.onap.org
 
https://imsva91-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.onap.org%2fmailman%2flistinfo%2fonap%2ddiscuss=CAD20441-6424-9305-A7AC-9253E32E6B5F=f63efd9aed1e0a367f4bd39381444e47841a5725-599b5ddaa682f840307a6cbf4482e982d884cbe8
 
 


Hi Team,


 


We have installed Amsterdam release of ONAP. We were successfully able to 
demonstrate vFW heat template based instantiation. We are currently working on 
TOSCA based E2E service  instantiation. We have a customer vCER CSAR file with 
which  we were able to create and distribute network and E2E service. We were 
able to onboard vnf and ns packages using usecase-UI. While trying to do VIM 
registration through ESR GUI, we are facing ExtsysException: PUT cloud region 
to AAI failed. When we tried to debug, all request to MSB-IAG is resulting “Bad 
Gateway”.


 



 
 
 


The external port getting exposed to msb-iag is in CLOSE_WAIT state. Please 
help in resolving the port issue and to proceed VIM registration.


 


Regards,


Kiruthiga___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss