similar to: Documentation on setup of VLAN

Hi All I need some real help in using virt-install. I have a fedora8 o/s + Xen installed and wanted to have RHEL4 as the Guest Domain. I have mounted the CD1 of RHEL4 and wanted to install this as guest domain using virt-install and not able to do and seeking help. Please let me know if the parameters to virt-install are correct and if not please let me know the correct parameters. Contents of

Any help is greatly appreciated.   Thanks Chandra Sekhar --- On Sun, 11/16/08, Chandra Sekhar <sekhar_15@yahoo.com> wrote: From: Chandra Sekhar <sekhar_15@yahoo.com> Subject: [Xen-users] Error while running virt-install To: xen-users@lists.xensource.com Date: Sunday, November 16, 2008, 11:23 PM Hi All I need some real help in using virt-install. I have a fedora8 o/s + Xen

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

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

we would like setup VLAN on CENTOS 5.X and 4.x. Only VLAN will active, but primary LAN NOT active. E.g "eth0" inactive, but "eth0.2" active. I have been tried several ways, but never successful. Any ideal? ______________________________________________________________________________________________________ ?????????Yahoo!??????2.0?????????????

Hi all, I have installed rhcs on a CentOS 4.4 server with clvmd. When server reboots display a segmentation fault on line 504 in /etc/rc.d/rc.sysinit file, here: if [ -x /sbin/lvm.static ]; then 500 if /sbin/lvm.static vgscan --mknodes --ignorelockingfailure > /dev/null 2>&1 ; then 501 action $"Setting up Logical Volume Management:"

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 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

Hi, I''ve setup a Xen server host (suse, xen 3.0.2) with vlan as follows: server-eth0 <-> vlanXY <-> vbridgeXY <-> domU-eth0 That is: vlan''s are managed in the physical host (for better security). The setup is working, i.e. I can connect to/from domU-eth0 from hosts in the same vlan. The problem is: it seems I loose "many" packets.

All, We are pleased to announce the release of OCFS2 1.2.9-1 for RHEL4 and RHEL5 on x86, x86_64, ppc64 and ia64 architectures. This release includes bug fixes, most of which have been backported from the mainline kernel. Some of the more interesting ones have been described in detail. For the full list of changes, please refer to the news.

All, We are pleased to announce the release of OCFS2 1.2.9-1 for RHEL4 and RHEL5 on x86, x86_64, ppc64 and ia64 architectures. This release includes bug fixes, most of which have been backported from the mainline kernel. Some of the more interesting ones have been described in detail. For the full list of changes, please refer to the news.

Hi, We are running a server as an nfs head connect to a clariion, every couple of days we have our box fall over with the following msg in syslog. Has anyone had this happen to there boxen? rhel4 u4 May 8 12:23:52 ruchba kernel: Assertion failure in log_do_checkpoint() at fs/jbd/checkpoint.c:363: "drop_count != 0 || cleanup_ret != 0" May 8 12:23:52 ruchba kernel: ------------[ cut

I had sent my reply to centos-devel, but as there is discussion here - here it is ... Lance ---------- Forwarded message ---------- Date: Tue, 14 Dec 2004 12:47:18 +0000 (GMT) From: Lance Davis <lance at uklinux.net> Reply-To: centos-devel at caosity.org To: John Newbigin <jn at it.swin.edu.au> Cc: centos-devel at caosity.org Subject: [CentOS-devel] Re: [Centos] Issues/thoughts re

Hi All, If I have a vlan-Id on an interface with an ipv6 address, then I am unable to ping a real router. The problem is that the Neighbour Solicitation originated from the Centos machine is missing the Vlan-Id in the packet. Therefore a real router will drop such a packet. I have tried this with Centos 4.7 and with Centos 5.5 with the same result. If I originate the first Neighbour

And additionally here are the detailed port configs on the switch end: hq>show interface Gi1/0/3 switchport Name: Gi1/0/3 Switchport: Enabled Administrative Mode: trunk Operational Mode: trunk Administrative Trunking Encapsulation: dot1q Operational Trunking Encapsulation: dot1q Negotiation of Trunking: On Access Mode VLAN: 48 (VLAN0048) Trunking Native Mode VLAN: 48 (VLAN0048) Administrative

>-----Original Message----- >From: Ben Greear [mailto:greearb@candelatech.com] >Sent: Monday, October 06, 2003 10:24 PM >To: Bart De Schuymer >Cc: netdev@oss.sgi.com; vlan@wanfear.com; bridge >Subject: [VLAN] Re: [PATCH/RFC] Let {ip,arp}tables "see" bridged VLAN >tagged{I,AR}P packets > > >Bart De Schuymer wrote: >> - add some code in

Hello everyone. I'm trying to set a up a wins and a browser on my residential student network. The network and my current configuration is as follow: #Network # .---------------. # | Samba Server | # *************** |---------------| ######* Server VLAN *<------| WINS | # *************** | Domain Master | #

Hi Boris, what I'd like to know is the actual VLAN configuration of the switch port (link-type and tagged and untagged VLANs). When I look at the switchport coniguration here I get (among other things): ... Port link-type: trunk Tagged VLAN ID : 8, 1624 Untagged VLAN ID : 10 ... Here is my suspicion: Your ports have an access link-type with an untagged VLAN ID of 48. That would

On Sun, Jan 25, 2015 at 8:38 AM, Andrew Holway <andrew.holway at gmail.com> wrote: > On 25 January 2015 at 15:12, Boris Epstein <borepstein at gmail.com> wrote: > >> OK... but why does it need to be a trunk port? >> > > Because a trunk port will "trunk" the vlan. > > A VLAN is basically a 4 byte "tag" that gets injected into the packet

-----Original Message----- >From: Tommy Christensen [mailto:tommy.christensen@tpack.net] >Sent: Wednesday, October 08, 2003 10:09 AM >To: Christian Darnell >Cc: 'Linux 802.1Q VLAN'; Bart De Schuymer; netdev@oss.sgi.com; bridge >Subject: Re: [Bridge] RE: [VLAN] Re: [PATCH/RFC] Let {ip, arp}tables >"see" bridged VLAN tagged{I,AR}P packets > > > >This