Hi David,
It is not necessary to know anything about the open vswitch.
You can do everything with the xe CLI, regardless whether you use the open
vswitch or the old linux bridging backend.
To destroy the networking objects, first make sure that no
VMs are running and unplug the PIFs (“xe pif-unplug”). Then remove VLANs with
“xe vlan-destroy”, remove bonds with “xe bond-destroy”, and remove VIFs with
“xe vif-destroy”. After that you can “xe pif-forget” the PIFs and “xe
network-destroy” the networks. We are planning to make this easier by
introducing a network reset command :)
Cheers,
Rob
From:
xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of David Le
Corfec
Sent: 20 July 2010 09:13
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] XCP - setting up network
Hi,
We are new to Xen (coming from vSphere), and testing XCP 0.5 (and XenServer).
We plan to use 1 pif for XCP access to our admin network and 2 other pifs (10
Gb) in bonding, with vlans on the bonding, to provide XCP access to our storage
network, and VMs access to our various networks.
I'm trying to get the most out of the XCP/XenServer admin docs, but I have some
questions:
- is it necessary to understand/use the Open vSwitch commands, or can you do
everything with the xe command ?
- is it possible to properly deconfigure the network configuration, going back
to the original state (with only an admin network), without reinstalling XCP ?
When I tried with the various "xe network-destroy", "xe
bond-destroy", xe pif-unplug", "xe pif-forget" ... I had
errors that there were still pifs on the network when destroying networks, and
I had errors that there were still networks on them when destroying pifs, like
a dependency circle. Or maybe I forgot to use the vlan commands, but I have
reinstalled since then. I haven't found a command to pretty print the various
network dependencies so I could reverse-walk them :(
- do you use a GUI to set up XCP networking, if so which one ? (I succeeded
with XenServer/XenCenter, but not with OpenXenCenter - maybe I didn't try hard
enough)
Regards,
David
