I was pretty sure the private key was mismatching the public key used during the installation, but this doesn’t seem to be the case. Security group can be an issue, even though he’s able to access the VMs via the private network.
Is the path to the private key correct when you try to access them via the public IP? I can’t think of other possible causes. Marco From: <[email protected]> on behalf of "FREEMAN, BRIAN D" <[email protected]> Date: Thursday, November 30, 2017 at 9:38 AM To: "Arun Arora (c)" <[email protected]>, "[email protected]" <[email protected]> Subject: Re: [onap-discuss] VFW/vLB External Network Connect fails ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hmm – cant help – dont know if your environment is doing security groups that blocks by default. Perhaps Marco has run into this problem before. Brian From: Arun Arora (c) [mailto:[email protected]] Sent: Thursday, November 30, 2017 9:33 AM To: [email protected]; FREEMAN, BRIAN D <[email protected]> Subject: RE: VFW/vLB External Network Connect fails No, the keypair is fine. Also I am using the keypair I created and not the one which comes as default in demo's env file. I am able to ssh on VM on its ONAP network interface in any scenario but not on external network interface when the VM had interfaces for both networks created by Demo Stack. Thanks Arun From: FREEMAN, BRIAN D Sent: Thursday, November 30, 7:58 PM Subject: RE: VFW/vLB External Network Connect fails To: Arun Arora (c), [email protected]<mailto:[email protected]> We usually only log in via the external IP for testing – seems strange that behavoir would change by detaching interfaces but we it is a VPP application so the protected/unprotected vNICs shouldn’t really be setup for login. Is the problem that the public key used in preload doesnt match the private.key you are using ? Brian From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Arun Arora (c) Sent: Thursday, November 30, 2017 9:14 AM To: [email protected]<mailto:[email protected]> Subject: [onap-discuss] VFW/vLB External Network Connect fails Hi All, While trying to create vFW and vLB/ vDNS demos I am facing the following issue in both demos: For both demos able to create the stack which creates 3 VMs and their associated networks In vFW demo, vFirewall application VM has both ‘protected’ and ‘unprotected’ networks configured on its interfacesIn vLB/ vDNS demo, Load-Balance VM has both ‘lb01_private’ and ‘pktget01_private’ networks configured on its interfaces Issue: SSH on both VMs (“vFirewall application VM” and “Load-Balance VM”) fails when its done using their External Interface IP or the IPs from the networks created with the demo stacks (i.e. ‘protected’, ‘unprotected’, ‘lb01_private’ or ‘pktget01_private’)I can only SSH then through the IP assigned by ONAP networkFurther to this, if any interface on ‘protected’ and ‘unprotected’ is detached from vFirewall application VM, and VM is restarted then SSH using external interface works!! Same happens for Load-Balance VM! Is this issue seen by anyone? Any pointers to resolve this? Thanks, Arun
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
