similar to: Network issue with xend

Displaying 20 results from an estimated 300 matches similar to: "Network issue with xend"

2012 Aug 16
0
Messages related libvirtd and bond
Hi, In one of our xen server, I am using two bonding. bond0 : Is for trunk, where the vlans are attached , port eth0 & eth1 is attached to bond0 bond1 : eth2 & eth3 are attached to bond1, where physical ip has been set . In the /etc/xen/xend-config.sxp, I am using (network-script *multi-network-bridge*) , the
2007 Apr 18
1
[Bridge] Bridging vlans...
<I apologize if this arrives twice... I sent it first from an non-subscribed address, don't know if that'll get to the list or not --JJ> Hi folks, I have an implementation question regarding bridging on a linux box between a catalyst trunk port and a cisco 26something w/802.1q subinterfaces. So right now, there's no vlan trunking going on on the link my bridging firewall sits
2012 Mar 02
1
KVM, VLAN and Bridges and bonding
Hi all, I use CentOS5.x + Xen in production for virtualization. I use it with bridged vlan networks and bonding (active-backup) like that: eth0 eth1 | | ------- | bond0-------bond0.10---------bond0.12 ... | | | | vlanbr10 vlanbr12 dom0 | | ------------- -------------- | |
2007 Apr 18
0
[Bridge] problems with bridging and dhcp
Hello, I'm trying to use bridging in our servers and found a problem with dhcp. Some clients manage to get an IP from the server, using DHCPDISCOVER/DHCPREQUEST. However others use BOOTREQUEST and these don't seem to get an answer. The server sends a BOOTREPLY but the clients continue to send BOOTREQUEST for ever. There are also some (occasional) messages from the dhcp server like
2010 Jul 03
4
Problem pinging the xen guest after live migration
Hi , I am getting the delay in pinging (from different network) , the guest after live migration . Here is the scenario: 0. OS : RHEL5.4 86_64 1. Host-A. Port eth1 , it is trunked with three subnets xxx.xx.15.xxx xxx.xx.16.xxx xxx.xx.17.xxx Guest created on 15, 16 ,17 subnets. Gust15-A created on subnet 15 Gust16-A
2019 Feb 06
2
Pb with bounding
Hi, We have a Dell server with 4 Ethernet interface. I would to aggregate them in a bond. Everything work but the default gateway doesn?t work on the ? bond0 ? interface and I have no links. My configuration: - CentOS 7: :/etc/sysconfig/network-scripts# uname -a Linux nas-mtd2 3.10.0-957.5.1.el7.x86_64 #1 SMP Fri Feb 1 14:54:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux - NetworkManager disabled:
2007 Mar 26
1
VLan help! :D?
Hi all, i need config xen with this ___________ __________ |VM1 |----------------bridge1-------------------| | |__________ | | | ____________ | |-----BALBLA |VM2 |
2003 Jun 03
1
etherchannel/port group/bonding plus vlan works well
I figured I should post this because before I went to do it I searched the web for caveats etc and didn''t really find much. So anyway, I set up bonding + vlan for a project. Computer is dell powerdge 350 with 2 intel 82559 10/100 nic running stock 2.4.20. I tried both the eepro100 and the e100 drivers for the nics, both work 802.1q and bonding are modules. Switch is cisco 2924xl-en
2017 Apr 19
0
anaconda/kickstart: bonding device not created as expected
On 18/04/2017 15:54, Frank Thommen wrote: > Hi, > > I am currently struggling with the right way to configure a bonding > device via kickstart (via PXE). > > I am installing servers which have "eno" network interfaces. Instead of > the expected bonding device with two active slaves (bonding mode is > balance-alb), I get a bonding device with only one active slave
2011 Sep 14
1
puppet kick getting hostname not match with the server certificate
OS - RHEL5.7 Installation Source - epel-testing repo Puppet server version - 2.6.6 puppetd version - 2.6.6 I searched Google and none of the answers were a match for my set up... I can do ''puppetd --test'' from the client and things work as expected. When doing puppet kick hostname I get the following: Triggering hostname Host hostname failed: hostname not match with the server
2011 Jul 25
2
MDB Files
Hi. I have a problem with Ms Access *.MDB files. When I tried to edit forms it takes at least 60 seconds to edit that forms also to edit query. Application is working fine. But editing ... horrible. I added these lines in my smb.conf file but nothing oplocks = no level2 oplocks = no strict locking = no fake oplocks = no veto oplock files =
2011 Dec 09
1
Samba 3.0, fuse-hdfs and write problems
Hi folks, I research at the moment a connection over fuse and samba for hadoop-cluster. Its my private playground, but I have some issues I can't figure out why they happen. I use RHEL5.7, packetlist: rpm -qa|grep samba samba-3.0.33-3.29.el5_7.4.x86_64 samba-common-3.0.33-3.29.el5_7.4.x86_64 2 servers, one provides samba-shares and one I use as client. Samba-Server (HOST2): FuseFS:
2011 Sep 13
5
Puppet not pushing file
I have set up puppet on Ubuntu/Debian servers with no problem. I am trying to get puppet working in a RHEL environment. I have the client installed and the certificate is signed so I know the two are talking but for some reason I can not get puppet to push the file on to the client. What am I missing? OS - RHEL5.7 Installation Source - epel-testing repo Puppet server version - 2.6.6 puppetd
2007 Jun 14
0
Multiple NIC usage in RHEL5
Hello all, I''m using Red Hat Enterprise Linux 5 (with RH Virtualization) and a Dell Poweredge 2950 with 10 NICs. My virtual operating systems are all RHEL4, and I''ve installed 4 instances. I''m trying to set up the virtual operating systems so that the physical NICs are allocated to certain operating systems. Using the following tutorial:
2011 Feb 12
0
xen 3.4.3 on CentOS 5.5 dom0: multiple nic issue -- eth1 won''t restart
Hi Folks: I have a strange problem with multiple (2) NICs on a CentOS 5.5 dom0 setup running xen 3.4.3 and have been struggling to fix it for some time. I could not find anything by googling or searching through this list but that is probably because I couldn''t figure out the correct search terms. After I configure my bridges the command "system network restart" fails for eth1
2007 Dec 04
1
Xen not applying custom network script on startup
I'm seeing an issue with xend not running a custom network script automatically, but works when I run it manually. In /etc/xen/xend-config.sxp I've changed: (network-script network-bridge) TO: (network-script network-custom) Here is /etc/xen/scripts/network-custom: # !/bin/bash # network-custom script=/etc/xen/scripts/network-bridge case $1 in start) $script start vifnum=0
2007 Jul 04
8
VLAN configuration
Hi to the ML. I''m new to VLAN configuration, and combining it to XEN is a bit difficult. I want to use VLAN because it''s possible to "arping" from a domU to an other, and VLAN looks like; the only solution to prevent that. May be I''m wrong if someone got a solution, I may be interrested. I''ve also tryed ebtables, but nothing to prevent arp
2008 Feb 01
3
No peth interface for xenbr4 and xenbr5
Hello all, I have a Xen server with 6 network interfaces, I want a bridge on all of them. I use a personal network script like this : #!/bin/bash dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0 "$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=xenbr1 "$dir/network-bridge" "$@"
2007 May 24
5
bonding + VLANs -> Oops/panic, no VLAN on 100 Mbit cards [SOLVED]
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
2007 May 24
5
bonding + VLANs -> Oops/panic, no VLAN on 100 Mbit cards [SOLVED]
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