similar to: RE: RE: VLAN and BRIDGE HELP

While I am still in the process of working through this here are the steps I am taking to set up each machine. 1) Since each of my servers have multiple NIC ports I bond them together (see page 34 of the Administrators Guide) first. This is best down from the physical server and not via the remote console. If you do it remotely you will then have to reconfigure the management port before

Hi, After reading XenServer documents and debugging, I found the previous configuration is correct, here is the one I've configured to work: In XCP, as in XenServer, system's network configuration doesn't really matter, it only make sense before XCP starts and handles the network settings. So there is no need to configure VLAN on host machine, and you only need a minimal one active

Good day. Few month ago I reported bug when vif was added as PIF to database. Now I found way to reproduce this: xe vif-create network-uuid=$NET_UUID vm-uuid=$DOM0_UUID device=1 mac=f4:03:02:01:00:01 xe vif-plug uuid=$NEWVIF_UUID xe pif-scan host-uuid=$HOST_UUID xe pif-list root at lab-xh4:~# xe pif-list uuid ( RO) : 62cdddc5-89ad-38e0-e9af-879df66e409d

Package: src:xen-api Severity: wishlist I've tried to configure VLAN using XCP + openvswitch using Wheezy, though it's still not fully working, I think VLAN configuration on dom0 can be better documented. It's fair easy to configure VLAN in Debian. First you need to ensure that your physical switch is in trunk mode, which means it will pass all kinds of VLAN tagged network flow, and

Package: xcp-xapi Version: 1.3.2-9 Severity: normal Hi guys, Just a couple of things I noticed running through /usr/share/doc/xcp-xapi/README.Debian.gz as referenced by http://wiki.debian.org/XCP In "4/ Configuring Xen and XCP": sed -i "s/TOOLSTACK=/TOOLSTACK=xapi/" /etc/default/xen should be sed -i "s/TOOLSTACK=.*/TOOLSTACK=xapi/" /etc/default/xen Otherwise

Package: xcp-xe Version: 1.3.2-8 Severity: minor When autocomplete for bash is activated following misbehavior happens: xe pif-list params=device,m[Tab] expected behavior: autocomplete to xe pif-list params=device,management actual behavior: xe pif-list params=management ('device' removed) -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500,

Package: xcp-xapi Version: 1.3.2-6 Severity: minor Tags: upstream If xe pif-configure-ip called twice with different IP, it did not remove old IP from interface (but didn't store both addresses in database). (Checked for management interface) Steps to reproduce: xe pif-reconfigure-ip uuid=... ip=IP1 .... xe pif-reconfigure-ip uuid=(same) ip=IP2 ... 'ip addr show' shows both

Package: xcp-xapi Version: 1.3.2-9 Severity: normal Function wait_for_xapi in /etc/init.d/xcp-xapi does not work as intented. Symptoms: (on slave) /etc/init.d/xcp-xapi restart [....] Restarting The XenAPI server: xapiThe host toolstack is still initialising. Please wait. Cause: Line 'xe pif-scan host-uuid=${INSTALLATION_UUID}' called before xapi is fully synced with master.

Package: xcp-xapi Version: 1.3.2-6 Severity: normal After some time of rebooting and toolstack restart found very funny output in 'xe pif-lis': xe pif-list params=currently-attached,device device ( RO) : vif2.0 currently-attached ( RO): false device ( RO) : vif211.0 currently-attached ( RO): false device ( RO) : eth1

Hi all, I have been troubled with the traffic flow on the XCP 1.6 and XCP 0.5. - I have 4 servers in VLAN2 on port b12,b13,b14,b15 (these servers work on a XCP 0.5) - on port a3 have have mirrort al ports from a1,a2,a4-b24 - have a other HP server with XCP1.6 with (Debian 6.0.6 as host) and install snort. this has 2 eth carts in it. Eth0 is plugt in the VLAN2 network and

Package: xcp-xapi Version: 1.3.2-13 Severity: critical I get this bug when installing XCP and configuring the network portion of it. When I issue the following command: xe pif-reconfigure-ip uuid=$PIF_UUID mode=static IP=10.0.0.10 netmask=255.255.255.240 gateway=10.0.0.1 DNS=10.5.1.2,10.5.1.3 My network interface looks like this (Broken): eth2 Link encap:Ethernet HWaddr 00:50:ec:24:c7:43

Package: src:xen-api Version: 1.3.2-9 Severity: wishlist Hi, In /usr/share/doc/xcp-xapi/README.Debian.gz, line 149: 149 PIF_UUID=`xe pif-list device=eth0` 150 xe pif-reconfigure-ip uuid=$PIF_UUID mode=static \ 151 IP=1.2.3.4 netmask=255.255.255.0 gateway=1.2.3.1 The command for acquiring the pif-uuid is missing a --minimal parameter, which makes it output the UUID only. -- Regards,

Hi, In XenServer5.6 FP1 beta, I have switched default bridge to open vswitch, I wonder how to use "xe tunnel-create" to create a GRE tunnel. my commands: xe tunnel-create pif-uuid=eth0_uuid network-uuid=network_created_by_xe_network_create then I got an uuid which is "access-PIF" of output from "xe tunnel-list". what should I do next? how to set remote_ip

Hello, I have been playing with the XCP for a while now, and must say I''m very exited about the technology. I had no prior experience with Xen so it has taken me a while to understand the concepts, but now I feel most important issues are solved and I''ve purchased some hardware to build my (tiny) cloud on. The box is a Supermicro 1026TT-IBXF, so I have 2 x Ethernet and 1 x

>> -----Original Message----- >> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Rich Greenwood >> Sent: Monday, 18 May, 2020 08:34 >> To: centos at centos.org >> Subject: Re: [CentOS] ether-wake >> >> Some switch hardware can generate the packets directly, negating the need >> for a box on every VLAN. Meraki hardware can do it, but

hi all, im peter, i found the post here http://www.gossamer-threads.com/lists/xen/users/229738 i build a small test env, with 2 vm in 1 server with xcp 1.1.0 i use xe network-create and xe vlan-create to build the vlan for each vm. then i got 2 bridge like xapi1 and xapi2, and in the ovs-vsctl list port i can see all these info about fake-bridge and vlan tag is correct. but when i start 2

Hello, i have 3 XCP 1.0.0 hosts in a pool, one of them is not enabled: xe host-param-list uuid=402f07f4-99c0-4501-9787-8dee8984e313 uuid ( RO) : 402f07f4-99c0-4501-9787-8dee8984e313 name-label ( RW): xcp1.domain.com name-description ( RW): Default install of XenServer allowed-operations (SRO):

Hi John, I've been chatting with Aron Xu, a Debian Developer from Beijing. He has been trying XCP. Chatting with him, we agreed that there's really not enough documentation when we want to work with VLAN networking and XCP. So we are trying to address this before Wheezy is released. Thanks to Aron, we have a beginning of a small howto for the dom0 (I changed only a bit of his style

hi all , i use ubuntu 12.04 with xcp , all config run very well except vlan i use xe network-create and xe vlan-create to build vlan 3000 then startup a vm in this network, xapi0 fakebridge and vif1.0 all looks well, use ovs-vsctl list port i can see xapi0 and vif1.0 have beed taged with 3000 but i can not access the internent~~~ somebody can help me with this? thanks.

Hello, I am using XCP 1.0 and am accessing it with XenCenter. I have three NIC''s and I have bonded two of them through the XenCenter frontend. I then create a VLAN using XenCenter and attach it to the bond0. I create a VM and create its NIC to use VLAN 10, which it does and when the VM boots the NIC shows Active inside of XenCenter. When I look at the XCP host it shows VLAN 10 as an