WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Re: [quagga-users 9274] My eth0 is NOT down -- but quagga sa

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Re: [quagga-users 9274] My eth0 is NOT down -- but quagga says it is?
From: "Code Monkey" <have.an.email@xxxxxxxxx>
Date: Sat, 12 Jan 2008 00:50:57 +0100
Delivery-date: Fri, 11 Jan 2008 15:51:28 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=kSOQvPv56YtD9U5DpAoL/PAybPqjF13UNQGgPgVoPhI=; b=d7+mXfHKIqBzvruQrO+hCbMhjhk7m+J72fvsZKRRrAzFtGi7vf0WHj71hZUgLUKZ2Pg3z0zVwxhvbzgpn3kQVmWsaFm4hHoVX4CXLIBFOY4aHgcfsYM6I68r/UsWNQiXpvDdccecTdgafp70ezzQ+rzfXGHV6Rq5jaHtJ6Bfy/c=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=C9DSc5KbEhr7u0/EjVHA03WVfVCIakNQLFSBrs0X/yLbrolrzbNdLRxSYkGqT0WBg5DMhcZGRZvFFd4K6JtBd8Ru7aS3TV7srD9CX0VEw5w/0dBnB+0Dc60aS1t909OCCW0BLnePjLVAb/nsfH3cGQMQyxzz43Jz+HM+Qpvgv7k=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <935ead450801100617y47c8fe52t9ad6e98771dcfed7@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <9f785d120801100600t3babde4ap441d6b4b1b8fe79@xxxxxxxxxxxxxx> <935ead450801100617y47c8fe52t9ad6e98771dcfed7@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

Quagga refuses to recognize my eth0 interface that seems to work
perfectly otherwise. Sentiment on quagga list seems to be that this is
a Xen problem, so here is my problem:

On 1/10/08, Jeffrey Ollie <jeff@xxxxxxxxxx> wrote:
> On 1/10/08, Code Monkey <have.an.email@xxxxxxxxx> wrote:
> >
> > I have quagga on some servers, I have Xen on some servers, now I want
> > to run quagga on the Xen dom0 to distribute the domU addresses.
> >
> > I copied configs from quaggas running elsewhere, and I don't
> > understand why quagga is saying that my eth0 is down!
> >
> > There is one domU running for the moment, but I'm not trying to do
> > OSPF with the domUs, just between the dom0 and the cisco router.
>
> This is probably because "eth0" is no longer a direct reference to
> your Ethernet hardware under Xen.  Xen renames the real physical
> interface to something like "peth0"  and then sets up a virtual
> interface named "eth0" for dom0 to communicate with.  The virtual
> interfaces of all of the Xen domains are all then bridged together
> with the physical interface.  I'm not sure which version of Linux
> you're running, but they seem to have changed the ifconfig command to
> hide some of the details from you (perhaps there is a switch that will
> show more of the configuration).

This is a Debian etch system, other information below.

Linux ${hostname} 2.6.18-5-xen-686 #1 SMP Mon Dec 24 20:49:58 UTC 2007
i686 GNU/Linux

I don't want to use bridges, I want quagga to advertise the /32s of my domUs.

# grep -v '^#' /etc/xen/xend-config.sxp  | grep .
(network-script network-route)
(vif-script     vif-route)
(dom0-min-mem 128)
(dom0-cpus 0)

I tried peth0, exact same thing. Nowhere on the machine have I found a
reference to anything else than eth0 (ifconfig, /proc/net/dev...)
where should I look?

Thanks for any help!




Other information below:


${hostname}:/etc/quagga# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:30:48:94:3D:A6
         inet addr:${my_/24}.158  Bcast:${my_/24}.159  Mask:255.255.255.248
         inet6 addr: fe80::230:48ff:fe94:3da6/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:88139 errors:0 dropped:0 overruns:0 frame:0
         TX packets:44944 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:100
         RX bytes:113267125 (108.0 MiB)  TX bytes:4818771 (4.5 MiB)
         Base address:0x5000 Memory:d2200000-d2220000

lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         inet6 addr: ::1/128 Scope:Host
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:278 errors:0 dropped:0 overruns:0 frame:0
         TX packets:278 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:18518 (18.0 KiB)  TX bytes:18518 (18.0 KiB)

lo:0      Link encap:Local Loopback
         inet addr:${my_/24}.146  Mask:255.255.255.255
         UP LOOPBACK RUNNING  MTU:16436  Metric:1

vif4.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
         inet addr:${my_/24}.158  Bcast:89.255.255.255  Mask:255.255.255.255
         inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:36196 errors:0 dropped:0 overruns:0 frame:0
         TX packets:75042 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:2319351 (2.2 MiB)  TX bytes:111411335 (106.2 MiB)

${hostname}:/etc/quagga# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
${my_/24}.79    0.0.0.0         255.255.255.255 UH    0      0        0 vif4.0
${my_/24}.152   0.0.0.0         255.255.255.248 U     0      0        0 eth0
0.0.0.0         ${my_/24}.153   0.0.0.0         UG    0      0        0 eth0
${hostname}:/etc/quagga# ping ${my_/24}.153
PING ${my_/24}.153 (${my_/24}.153) 56(84) bytes of data.
64 bytes from ${my_/24}.153: icmp_seq=1 ttl=64 time=0.368 ms
64 bytes from ${my_/24}.153: icmp_seq=2 ttl=64 time=0.286 ms
64 bytes from ${my_/24}.153: icmp_seq=3 ttl=64 time=0.704 ms

--- ${my_/24}.153 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.286/0.452/0.704/0.182 ms

${hostname}:/etc/quagga# cat /etc/quagga/ospfd.conf
hostname ${hostname}
password ${password}
enable password ${password}

interface eth0
 ip ospf priority 0
!
router ospf
 ospf router-id ${my_/24}.146
 network ${my_/24}.152/29 area 0
 ospf abr-type cisco
 redistribute connected

log file /var/log/quagga/ospfd.log
${hostname}:/etc/quagga# /etc/init.d/quagga stop
Stopping Quagga daemons (prio:0): (waiting) .. ospfd (zebra) (bgpd)
(ripd) (ripngd) (ospf6d) (isisd).
Removing all routes made by zebra.
Nothing to flush.
${hostname}:/etc/quagga# /etc/init.d/quagga start
Loading capability module if not yet done.
Starting Quagga daemons (prio:10): ospfd.
${hostname}:/etc/quagga# telnet localhost ospfd
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.

Hello, this is Quagga (version 0.99.5).
Copyright 1996-2005 Kunihiro Ishiguro, et al.


User Access Verification

Password:
${hostname}> show ip ospf interface
eth0 is down
 ifindex 0, MTU 0 bytes, BW 0 Kbit <>
 OSPF not enabled on this interface
${hostname}> exit

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>