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

[XenPPC] xend and routes

To: xen-ppc-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [XenPPC] xend and routes
From: Maria Butrico <butrico@xxxxxxxxxxxxxx>
Date: Wed, 06 Dec 2006 13:51:45 -0500
Delivery-date: Wed, 06 Dec 2006 10:53:06 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post: <mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
Reply-to: butrico@xxxxxxxxxxxxxx
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.8 (Windows/20061025)
We have several JS21, all with two ethernet interfaces, both interfaces in use. For example this is what things look like when we boot one such blade with the latest xen and linux for xen and before starting xend.

cso89:~ # ifconfig
ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:25:C9:4D:5A inet addr:192.168.4.9 Bcast:192.168.255.255 Mask:255.255.0.0
         UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:15436 errors:0 dropped:0 overruns:0 frame:0
         TX packets:679 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:1084295 (1.0 Mb)  TX bytes:62108 (60.6 Kb)
         Interrupt:17

eth1 Link encap:Ethernet HWaddr 00:11:25:C9:4D:5B inet addr:9.2.78.89 Bcast:9.2.78.255 Mask:255.255.255.0
         UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:14899 errors:0 dropped:0 overruns:0 frame:0
         TX packets:1514 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:1076900 (1.0 Mb)  TX bytes:171946 (167.9 Kb)
         Interrupt:18

lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:22 errors:0 dropped:0 overruns:0 frame:0
         TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:1480 (1.4 Kb)  TX bytes:1480 (1.4 Kb)



This is what the routing tables look like.

cso89:~ # netstat -rn
netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface 9.2.78.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 192.168.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U         0 0          0 lo
0.0.0.0 9.2.78.1 0.0.0.0 UG 0 0 0 eth1


Notice that the machine name, cso89 corresponds to ip address 9.2.78.89 and is on eth1. Notice also that there is a default route from the machine, the last one, in the table above. After we start xend this is the network interface table.

cso89:~ # ifconfig
ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:25:C9:4D:5A inet addr:192.168.4.9 Bcast:192.168.255.255 Mask:255.255.0.0
         UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:18 errors:0 dropped:0 overruns:0 frame:0
         TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:1333 (1.3 Kb)  TX bytes:650 (650.0 b)

eth1 Link encap:Ethernet HWaddr 00:11:25:C9:4D:5B inet addr:9.2.78.89 Bcast:9.2.78.255 Mask:255.255.255.0
         UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:15102 errors:0 dropped:0 overruns:0 frame:0
         TX packets:1605 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:1090820 (1.0 Mb)  TX bytes:190036 (185.5 Kb)
         Interrupt:18

lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:22 errors:0 dropped:0 overruns:0 frame:0
         TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:1480 (1.4 Kb)  TX bytes:1480 (1.4 Kb)

peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
         RX packets:19 errors:0 dropped:0 overruns:0 frame:0
         TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:1541 (1.5 Kb)  TX bytes:748 (748.0 b)
         Interrupt:17

vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
         RX packets:2 errors:0 dropped:0 overruns:0 frame:0
         TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:650 (650.0 b)  TX bytes:1333 (1.3 Kb)

xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
         RX packets:19 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:1348 (1.3 Kb)  TX bytes:0 (0.0 b)

This is as expected.  However notice what happened to our routing tables.

cso89:~ # netstat -rn
netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface 9.2.78.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth0 9.2.78.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 192.168.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U         0 0          0 lo
0.0.0.0 9.2.78.1 0.0.0.0 UG 0 0 0 eth0 0.0.0.0 9.2.78.1 0.0.0.0 UG 0 0 0 eth1


The next to last route is bogus and interferes with the proper operation of the machine as far as the network goes. I am not sure what the first route in the list above is all about, but seems strange as well. In any case it was not there before.





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