Hi Alessandro, If the switchports for storage are in access mode then indeed you can't present another VLAN there. You might be able to create a new logical interface on Xen in the same VLAN with the new IP range, but that's not something I've tried before (works fine on ESX and KVM though).
I'd always recommend to use Trunked ports everywhere, keeping your L2 fabric as simple as possible and all the intelligence down in the hypervisor and not in the switch, this gives you much more flexibility. But of course, other ways of setting up are always valid, that's just my preferred one based on experience. Regards, Alex -----Original Message----- From: Alessandro Caviglione <c.alessan...@gmail.com> Sent: 07 May 2021 10:50 To: users@cloudstack.apache.org Subject: Re: Primary storage migration Thank you Alex, iscsi subnet is present on same switch fabric so we can add it, but since xenserver port are actually in ACCESS with specific VLAN, how can I add an IP with a tagged VLAN on xenserver? On Fri, May 7, 2021 at 10:29 AM Alex Mattioli <alex.matti...@shapeblue.com> wrote: > Hi Alessandro, > > Is the new iSCSI subnet present in the same L2 switching fabric? In > that case you just need a VLAN interface on the 10.0.0.x network. If > it is in a separate switching fabric then you can add a couple extra > NICs to your host and connect to that network. > > Migration wise, as long as the XenServer host can mount SRs from both > storage servers then it should be able to migrate your VMs and volumes > across. > > Regards, > Alex > > > > > -----Original Message----- > From: Alessandro Caviglione <c.alessan...@gmail.com> > Sent: 07 May 2021 10:22 > To: users@cloudstack.apache.org > Subject: Primary storage migration > > Hi guys, > I've a big doubt for next few weeks. > Actually we're running CS 4.13 and one of the cluster we're managing > is based on xenserver 7.2. > Today, primary storage is provided through NFS share in 192.168.200.x > subnet but we've want to migrate to another storage that provide iSCSI > lun on 10.0.0.x subnet. > This iscsi subnet is an isolated subnet so no routing is possible. > What you suggests to do? > Is it possible to add a couple of nics to xenserver for iscsi and > manage it on CS? > > Thank you! >
