Re: [onap-discuss] http://:667 Site Can't Be Reached - Debug

2018-02-15 Thread PLATANIA, MARCO (MARCO)
Hi Stephen,

What kind of response do you get when you try to access that port? We don’t 
have a specific way to debug that service. We noticed that sometimes cloud-init 
doesn’t run as expected. In these cases we just reboot the affected VM.

Marco

From:  on behalf of "Gooch, Stephen" 

Date: Thursday, February 15, 2018 at 3:17 PM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] http://:667 Site Can't Be Reached 
- Debug

Hello,

After deploying the vFWCL demo, all three VMs are active and respond to a ping 
from external network.  However when attempting to look at the SNK VM’s graph 
on port :667, nothing is displayed.

Is there a procedure for debugging the lack of html service on port 667?

Br,
- Stephen

Stephen Gooch | Senior Member of Technical Staff | Wind River
+1.510.965.7909 , Skype ID: Stephen.gooch

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


Re: [onap-discuss] http://:667 Site Can't Be Reached - Debug

2018-02-15 Thread bharath thiruveedula
Hi Stephen

To just give initial pointers to debug, the service that is running in sink VM 
and which is listening on 667 port is darkstat. As you might know, darkstat is 
network traffic monitoring tool. In this usecase it monitors packets coming to 
eth1 interface. Can you check whether darkstat is installed properly or not? If 
installed properly, then can you check the status?

And see any errors in cloud init output(/var/log/cloud-init-output.log) in sink 
vm?

Best Regards
Bharath T

Get Outlook for iOS<https://aka.ms/o0ukef>

From: onap-discuss-boun...@lists.onap.org  
on behalf of Gooch, Stephen 
Sent: Friday, February 16, 2018 1:47:30 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] http://:667 Site Can't Be Reached 
- Debug

Hello,

After deploying the vFWCL demo, all three VMs are active and respond to a ping 
from external network.  However when attempting to look at the SNK VM’s graph 
on port :667, nothing is displayed.

Is there a procedure for debugging the lack of html service on port 667?

Br,
- Stephen

Stephen Gooch | Senior Member of Technical Staff | Wind River
+1.510.965.7909 , Skype ID: Stephen.gooch

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


[onap-discuss] http://:667 Site Can't Be Reached - Debug

2018-02-15 Thread Gooch, Stephen
Hello,

After deploying the vFWCL demo, all three VMs are active and respond to a ping 
from external network.  However when attempting to look at the SNK VM's graph 
on port :667, nothing is displayed.

Is there a procedure for debugging the lack of html service on port 667?

Br,
- Stephen

Stephen Gooch | Senior Member of Technical Staff | Wind River
+1.510.965.7909 , Skype ID: Stephen.gooch

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