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

Displaying 20 results from an estimated 4000 matches similar to: "Bug#682216: Bug #682216 document about VLAN configuration on dom0"

2012 Jul 20
2
Bug#682216: document about VLAN configuration on dom0
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
2012 Jul 19
1
Bug#682120: xen-api: missing --minimal in example command
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,
2012 Jul 19
1
Bug#682122: xcp-xapi: README.Debian has a few misleading commands
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
2012 Dec 05
4
Bug#695221: xcp-xapi: xe pif-reconfigure-ip doesn't work with non 255.255.255.0 subnet netmask
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
2008 Jun 09
0
RE: RE: VLAN and BRIDGE HELP
You are very welcome. One thing that I am working on now involves removing the step toward the beginning: xe pif-reconfigure-ip uuid=<UUID of the bond created above> mode=static gateway=<GATEWAY> IP=<IP ADDRESS> netmask=<NETMASK> DNS=<DNS SERVER ADDRESS> I do not believe that this step is necessary since we will not use the pif directly. We will use
2008 Jun 09
1
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
2012 Jul 20
0
Bug#682216: Documenting VLAN networking setup with XCP
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
2012 Jul 06
1
Bug#680500: xcp-xe: Tab in autocomple of params for 'xe pif-list params=' erase some arguments
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,
2012 Jul 12
2
Bug#681343: xcp-xapi: wait_for_xapi() function in init.d script does not work
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.
2012 Jun 13
2
Bug#677395: xcp-xapi: xe pif-configure-ip does not remove old ip from interface
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
2012 Jun 24
1
Bug#678723: xcp-xapi: vif-interfaces added to database as PIF's
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
2012 Jul 07
1
Bug#680588: xcp-xapi: startup race condition between xcp-xapi and xcp-networkd on slave
Package: xcp-xapi Version: 1.3.2-8 Severity: important Tags: patch Found race condition (specific only to slave hosts): xcp-xapi can start earlier than xcp-networkd due lack of dependency in init.d script. Syptoms: After reboot slave's xcp does not work: xe (anything): The host failed to acquire an IP address on its management interface and therefore cannot contact the master. log:
2010 Oct 08
2
Polycom getting DCHP address from wrong VLAN
Hello, I have been tearing my hair out on this issue for 2 days, any help would be appreciated. We have a normal network and a Cisco SGE2010P switch - a 48 port PoE switch There are two VLANs, 1(data) & 50(VoIP). When Polycoms are connected to the switch with VLAN 50 hard coded in the config they grab a DHCP address from VLAN 1, the PVID for the switch port. The ports have membership in
2012 Jul 06
4
Bug#680528: xcp-xapi: /etc/init.d/xendomains cause xapi to hand during boot
Package: xcp-xapi Version: 1.3.2-8 Severity: important During startup /etc/init.d/xendomains script is called. That script is installed with xen-utils-common witch xcp-xapi is depends on. That script calls /usr/sbin/xen as xen list &> /dev/null This 'xen' seems to call xapi: xen list ^Z [1]+ Stopped xen list root at lab-xh3:~# ps f PID TTY STAT TIME
2010 Apr 07
6
using ipoib with xcp
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
2010 Jan 20
0
XCP 0.1.1
I knew it couldn''t possibly go right. First attempt at upgrading a 0.1.0 host trashed the networking config majorly. In defense of 0.1.1, I did have an odd networking config (since XCP had problems with the built in Broadcom ports, I pif-forgetted them and let Linux handle them. If it weren''t for the mutant network config, I bet 0.1.1 would have done ok. More seriously,
2013 Mar 01
0
XCP 1.6 don’t pass throug all traffic to (tpcdump) snort
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
2013 Mar 06
0
Bug#702337: possible documentation issue
It appears that this issue may be a result of documentation problems When I was having this problem, I had xenbr0 declared in my /etc/network/interfaces file. I have now stripped out everything in the interfaces file except the loopback interface, rebooted, and now my xcp+openvswitch system appears to be adding domUs to the bridge automatically, so the problem is no longer there. Specifically,
2013 Feb 10
0
Processed: serious bug with networking
Processing commands for control at bugs.debian.org: > severity 695221 serious Bug #695221 [xcp-xapi] xcp-xapi: xe pif-reconfigure-ip doesn't work with non 255.255.255.0 subnet netmask Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 695221: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695221
2013 Feb 11
0
Processed: Back to important
Processing commands for control at bugs.debian.org: > severity 695221 important Bug #695221 [xcp-xapi] xcp-xapi: xe pif-reconfigure-ip doesn't work with non 255.255.255.0 subnet netmask Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 695221: