You opened a new thread with this question - which I answered, so this one is probably good to be closed :)
On Tue, 1 Jun 2021 at 22:40, Jeremy Hansen <[email protected]> wrote: > Thank you for your help. Set up a tagged VLAN and live migrations are > working like a champ now. > > My next issue… > > I launched a second guest and noticed it did not allocate a new public > IP. My expectation was that it would allocate another public IP and the > second instance would have its own virtual router/firewall/port forwarding, > etc, but that doesn’t seem to be the case. I can configured the firewall > on the existing virtual router to forward to the second instance, but I’d > prefer it just allocate another public IP from the range and allow me to > configure each instance as a separate entity. Is this possible? > > Thanks > -jeremy > > > > On Jun 1, 2021, at 4:32 AM, Alessandro Caviglione < > [email protected]> wrote: > > > > No, but if you're using Advanced Networking you've to manage the trunk > > configuration on the switch ports. > > Every Virtual Router has a public IP on a specific interface and a > specific > > VLAN and a private IP on another interface in another vlan that acts as a > > gateway for the instance. > > So, if VR and instance are in the same host, packets do not exit from > host > > and instance are reachable, but if they run on different hosts the > packets > > must go through a switch that should be configured to allow traffic on > that > > private VLAN. > > So, in fact, you can allow a single switch port to forward traffic on > > multiple VLAN, this is called Trunk. > > > > On Tue, Jun 1, 2021 at 12:31 PM Jeremy Hansen <[email protected]> wrote: > > > >> Ahh, so I just noticed that I could also migrate the router and when I > do > >> that, everything works as expected again. So is this how migrates work? > >> Do routers always have to move with the instance? > >> > >> -jeremy > >> > >> > >> On Jun 1, 2021, at 3:26 AM, Jeremy Hansen <[email protected]> wrote: > >> > >> One thing I noticed, and I don’t know if this is expected, but the > virtual > >> router my instance is using remains on the original VM host. If I log > in > >> to the guest instance while it’s on the second VM host, I can no longer > >> ping the private net gateway: > >> > >> <Screen Shot 2021-06-01 at 3.24.53 AM.png> > >> > >> and the virtual router can’t ping the private IP > >> > >> <Screen Shot 2021-06-01 at 3.23.34 AM.png> > >> > >> If I migrate the instance back, it ping reachable again: > >> > >> <Screen Shot 2021-06-01 at 3.26.36 AM.png> > >> > >> > >> Thanks > >> -jeremy > >> > >> > >> > >> On Jun 1, 2021, at 3:07 AM, Jeremy Hansen <[email protected]> wrote: > >> > >> Hmm. VM hosts are on the same vlan. Port configuration on both hosts is > >> exactly the same. I’m not saying it isn’t vlan related but I would > expect > >> neither host to work if it was a vlan issue? > >> > >> Thanks > >> > >> On Jun 1, 2021, at 2:47 AM, Alessandro Caviglione < > [email protected]> > >> wrote: > >> > >> I think that your switch doesn't have ports tagged with all required > >> VLANs... > >> > >> On Tue, Jun 1, 2021 at 11:20 AM Jeremy Hansen <[email protected]> > wrote: > >> > >> > >> I set up another VM host so now I have two VM hosts. I’m experimenting > >> with live migrations. It looks like the VM migrates, but I can no > longer > >> SSH to the guest once it’s migrated. I’m using an isolated network. I > >> setup firewall rules to allow all, along with port forwarding rules for > >> ssh. I’m using the CentOS 5.5 template. When I migrate to the second > VM > >> host, ping/icmp still works, but I’m unable to ssh to the VM guest. If > I > >> migrate back to the original VM host, everything is fine again. Any > clues > >> what I’m doing wrong on the second VM host or why rules would change on > the > >> migration? > >> > >> Thanks > >> -jeremy > >> > >> > >> > >> > >> > >> > > -- Andrija Panić
