[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-API] Re: [Xen-users] XCP Set MTU not work after change XCP 1.0beta -> XCP 1.0 RC2

To: Rob Hoes <Rob.Hoes@xxxxxxxxxx>
From: "martinu@xxxxxxxxxxxx" <martinu@xxxxxxxxxxxx>
Date: Sun, 20 Feb 2011 00:03:24 +0100
Cc: "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sat, 19 Feb 2011 16:06:54 -0800
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>

Hello,

unplug and plug has no effect (restart of cnode1 too):

[root@cnode1 ~]# xe network-param-listuuid=e54ccf40-5941-7154-d07c-cb31ae9298b7

uuid ( RO)                : e54ccf40-5941-7154-d07c-cb31ae9298b7
         name-label ( RW): storage1 bond0
   name-description ( RW):
          VIF-uuids (SRO):
          PIF-uuids (SRO): 5d9ea69a-cd9b-1d30-8a15-383d691d86d0
                MTU ( RW): 9000
             bridge ( RO): xapi1
       other-config (MRW):
              blobs ( RO):
               tags (SRW):


[root@cnode1 ~]# xe pif-list
uuid ( RO)                  : 2e836c5a-4355-50f8-4f58-0229a582680f

device ( RO): eth1currently-attached ( RO): falseVLAN ( RO): -1network-uuid ( RO): 18cd44c0-e526-c574-a25f-42360b69bab1



uuid ( RO)                  : 5d9ea69a-cd9b-1d30-8a15-383d691d86d0

device ( RO): bond0currently-attached ( RO): trueVLAN ( RO): -1network-uuid ( RO): e54ccf40-5941-7154-d07c-cb31ae9298b7



uuid ( RO)                  : be7d34b8-0d6b-ae67-1977-d0f67b979372

device ( RO): eth2currently-attached ( RO): falseVLAN ( RO): -1network-uuid ( RO): b533b0f7-6cd5-ab97-0288-08051288e914



uuid ( RO)                  : 21e1ee4c-7e8b-5eaf-6c78-49232051f58f

device ( RO): eth0currently-attached ( RO): trueVLAN ( RO): -1network-uuid ( RO): 80282403-d8b2-cbab-37eb-0996b02cdb27



uuid ( RO)                  : 517618b3-c577-8700-f38a-718cb83be975

device ( RO): eth3currently-attached ( RO): falseVLAN ( RO): -1network-uuid ( RO): 05326577-1011-232c-e12e-0a7ea06b9ba5


[root@cnode1 ~]# xe pif-unplug uuid=5d9ea69a-cd9b-1d30-8a15-383d691d86d0
[root@cnode1 ~]# xe pif-unplug uuid=2e836c5a-4355-50f8-4f58-0229a582680f
[root@cnode1 ~]# xe pif-unplug uuid=be7d34b8-0d6b-ae67-1977-d0f67b979372
[root@cnode1 ~]# xe pif-unplug uuid=517618b3-c577-8700-f38a-718cb83be975
[root@cnode1 ~]# xe pif-plug uuid=517618b3-c577-8700-f38a-718cb83be975
[root@cnode1 ~]# xe pif-plug uuid=be7d34b8-0d6b-ae67-1977-d0f67b979372
[root@cnode1 ~]# xe pif-plug uuid=2e836c5a-4355-50f8-4f58-0229a582680f
[root@cnode1 ~]# xe pif-plug uuid=5d9ea69a-cd9b-1d30-8a15-383d691d86d0

[root@cnode1 ~]# /sbin/ifconfig

bond0 Link encap:Ethernet HWaddr 00:23:20:CA:F8:B3UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

         RX packets:11426 errors:0 dropped:0 overruns:0 frame:0
         TX packets:85 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0RX bytes:1433300 (1.3 MiB) TX bytes:53881 (52.6 KiB)

eth0 Link encap:Ethernet HWaddr D4:85:64:4C:4C:E6UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

         RX packets:305822 errors:0 dropped:0 overruns:0 frame:0
         TX packets:69391 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000RX bytes:24347518 (23.2 MiB) TX bytes:10660693 (10.1 MiB)

eth1 Link encap:Ethernet HWaddr D4:85:64:4C:4C:E7UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

         RX packets:3797 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:470828 (459.7 KiB)  TX bytes:0 (0.0 b)

eth2      Link encap:Ethernet  HWaddr D4:85:64:4C:5C:08
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:3798 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:470952 (459.9 KiB)  TX bytes:0 (0.0 b)

eth3      Link encap:Ethernet  HWaddr D4:85:64:4C:5C:09
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:3831 errors:0 dropped:0 overruns:0 frame:0
         TX packets:85 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:491520 (480.0 KiB)  TX bytes:53881 (52.6 KiB)

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:5444 errors:0 dropped:0 overruns:0 frame:0
         TX packets:5444 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:4498698 (4.2 MiB)  TX bytes:4498698 (4.2 MiB)

xapi1     Link encap:Ethernet  HWaddr D4:85:64:4C:4C:E7
         inet addr:172.16.132.4  Bcast:172.16.132.255  Mask:255.255.255.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:0 (0.0 b)  TX bytes:252 (252.0 b)

xenbr0    Link encap:Ethernet  HWaddr D4:85:64:4C:4C:E6
         inet addr:X.X.X.X  Bcast:X.X.X.255  Mask:255.255.255.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:249310 errors:0 dropped:0 overruns:0 frame:0
         TX packets:69397 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:20957574 (19.9 MiB)  TX bytes:10661673 (10.1 MiB)

Rob Hoes napsal(a):

Hi,

That is correct. After changing the MTU on a Network, all PIFs and VIFs on the 
Network need to be unplugged and plugged again for the MTU change to happen.

Cheers,
Rob

On 19 Feb 2011, at 03:27, Adrian Costin wrote:

Hi,

I've tested this in RC3 (should be the same for RC2) and while 
network-param-set does not have any effect on the actual PIFs, doing pif-unplug 
and then pif-plug will set the correct MTU on the interface.

I think this is the expected behavior, as network-param-set will just update 
the database. The actual configuration of the physical interface takes place on 
pif-plug.

Best regards,
Adrian Costin


-----Original Message-----
From: xen-api-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-api-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Todd Deshane
Sent: Saturday, February 19, 2011 4:03 AM
To: Jan MartinÅ
Cc: xen-users mailing list; xen-api@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] Re: [Xen-users] XCP Set MTU not work after change XCP 1.0beta 
-> XCP 1.0 RC2

adding xen-api to the CC.

dropping xen-devel from the CC.

2011/2/18 Jan MartinÅ <martinu@xxxxxxxxxxxx>:

Hello,

this command:

xe network-param-set uuid=xxxxx MTU=9000

sets MTU=9000 on bond and his slave PIFs.

After change XCP 1.0beta to XCP 1.0 RC2, command has no effect to PIFs.

Thanks for the report.

Are others seeing this as well?

There was an rc3, but I don't think that it changed much in this space. Maybe 
Jon can comment to be sure.

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api
<ATT00001..txt>



--
S pozdravem

Jan MartinÅ
VSHosting s.r.o.
Telefon: 246 035 835
Email: martinu@xxxxxxxxxxxx
www.vshosting.cz


_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

Follow-Ups:
- Re: [Xen-API] Re: [Xen-users] XCP Set MTU not work after change XCP 1.0beta -> XCP 1.0 RC2
  - From: Christian Fischer

References:
- Re: [Xen-users] XCP Set MTU not work after change XCP 1.0beta -> XCP 1.0 RC2
  - From: Todd Deshane
- RE: [Xen-API] Re: [Xen-users] XCP Set MTU not work after change XCP 1.0beta -> XCP 1.0 RC2
  - From: Adrian Costin
- Re: [Xen-API] Re: [Xen-users] XCP Set MTU not work after change XCP 1.0beta -> XCP 1.0 RC2
  - From: Rob Hoes

Prev by Date: Re: [Xen-API] Facing error to download rc3
Next by Date: [Xen-API] åå: xen-api Digest, Vol 57, Issue 25
Previous by thread: Re: [Xen-API] Re: [Xen-users] XCP Set MTU not work after change XCP 1.0beta -> XCP 1.0 RC2
Next by thread: Re: [Xen-API] Re: [Xen-users] XCP Set MTU not work after change XCP 1.0beta -> XCP 1.0 RC2
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.