similar to: Bug#682216: document about VLAN configuration on dom0

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

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,

Hello. I''m running linux box with Slackware 9.1 and compiled kernel 2.4.31 with "yes" to VLANs and "yes" to all QoS. On this box i have more ethernet interfaces: eth0 eth1 eth2 and so as more vlan interfaces: eth0.100 eth1.3 eth1.4 This is entrace(uplink) router to our whole network and my goal is to shape users on this machine. I want for this purpose use HTB so

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

As the issue concerns both the -user (configuration) and -devel (OOPS), I''m sending this message to both lists. Some time ago I complained about two problems: - VLANs are not working on machines with 100 Mbit cards - I get a kernel Oops (sometimes panic) when I try to use bonding and VLANs with Xen The root of the issue is the same in both cases: VLAN interfaces must *not* be

As the issue concerns both the -user (configuration) and -devel (OOPS), I''m sending this message to both lists. Some time ago I complained about two problems: - VLANs are not working on machines with 100 Mbit cards - I get a kernel Oops (sometimes panic) when I try to use bonding and VLANs with Xen The root of the issue is the same in both cases: VLAN interfaces must *not* be

Hi all, Is it possible to have native VLAN (802.1q) and a VLAN x at the same time in DOMU''s? This is what I have configured on my DOM0 (xen2): Eth0 (connected by a 801.1q trunk to Cisco 2950 switch) Created vlan100 : vconfig eth0 100 Created bridge : brctl addbr br100 Attach switchport: brctl addif br100 eth0.100 Attach a DOMU : brctl addif br100 vif2.0 I now have bridge br100

Hi Rahul, If you're certain that your problem isn't as Stephen suggested, you might want to have a look at this: --- (From http://ebtables.sourceforge.net/brnf-faq.html <http://ebtables.sourceforge.net/brnf-faq.html> ) How do I let vlan-tagged traffic go through a vlan bridge port and the other traffic through a non-vlan bridge port? Suppose eth0 and eth0.15 are ports of br0.

Hi, I want to add 2 vlans by the following steps: 1. add the vlan interfaces: vconfig add eth0 100 --vlan100 vconfig add eth0 101 --vlan101 2. modify the network-bridge script by the websit, http://wiki.xensource.com/xenwiki/XenNetworking#head-04ebcc1760dbc4678e83b116afa310dc0612dc39 Comment each time ifup or ifdown commands are executed.The reason is that ifdown ends with

I have a strange problem with VLANs with Xen 3.0.4. I signalled it on Xen-users list, but found no definitive solution to it. I configure VLANs so that they are available in dom0; domUs don''t know that they use VLANs. I use a stock "network-bridge" comming from Xen for setting up networking: #!/bin/bash dir=$(dirname "$0") "$dir/network-bridge"

Hello, can anybody help me how to configure vlans? There are vlans: vlan2 vlan3 vlan30 Server has one nic - eth0. vlan2 should be dom0 eth0(peth0) for management Each vlan3 and vlan30 should be has its own bridge. How to make it? Br Peter _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Package: xcp-xapi Version: 1.3.2-15 Severity: important New wheezy box Follow the setup instructions for xcp-xapi, choosing openvswitch networking Only loopback is defined in /etc/network/interfaces (the way it should be for XCP) IP address, router, DNS has been configured statically with pif-reconfigure-ip After reboot, the IP address is assigned correctly on the bridge interface but some

I am wanting to verify that I am properly using the MASQ for a series of hosts. I have 2 providers, and my providers file has the contents: #NAME NUMBER MARK DUPLICATE INTERFACE GATEWAY OPTIONS COPY l3 1 100 main eth0.100 1.18.139.1 track,loose,fallback eth1 ws 2 200 main eth0.101 1.155.136.193

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

After some digging in openvswitch code. My wild guess is that vlan tag reconfiguring triggered iface_configure_qos (vswitchd/bridge.c), which in turn called netdev_set_policing to reset ingress policing rate. Although there's no ingress_policing_rate set in my case, existing ingress qdisc still remove by default. Could some openvswitch guy help to confirm and suggest how to fix or workaround?

Dear XCP lovers, We have installed XCP 1.1 on our BladeCenter and it is working like a charm. Except when creating a VLAN, the xenserver needs to be switched to bridge mode and back to openvswitch. As I understood, this is a bug in xenserver 5.6 SP2 and will be fixed in the xencenter 6.0 which will come with XCP 1.5. Is there a date when the beta version will be released ? Concerning our VLAN

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Try it without any --delete options. On 03/27/2015 09:31 AM, Aron Rotteveel wrote: > I am now running with --delete --numeric-ids --relative but the > problem still persists. > > -- Best regards / Met vriendelijke groet, > > Aron Rotteveel > > 2015-03-27 14:22 GMT+01:00 Kevin Korb <kmk at sanitarium.net >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Try also removing --delete-excluded. Without those two options there should be no reason for rsync to require gigs of RAM. Well, unless the other system has rsync 2.x. On 03/27/2015 07:29 AM, Aron Rotteveel wrote: > Yes, I removed "--no-inc-recursive", without success. > > -- Best regards / Met vriendelijke groet, > >

Hi, I am experiencing segfaults when transferring files via rsync though sudo. Setup: - Backupserver initiates the rsync command with --delete -vvv --no-inc-recursive --numeric-ids --delete-excluded --relative --rsync-path=/home/backupuser/rsync-wrapper.sh - rsync-wrapper.sh (on the client) contains /usr/bin/sudo /usr/bin/rsync "$@"; - user "backupuser" has sudo access to the

Hi all ls centos supporting vlan setup? ls it reliable? how can I do it? Thank you --------------------------------- Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail -------------- next part -------------- An HTML attachment was scrubbed... URL: