Re: [Xen-API] XCP: VLAN Issue

[Todd Deshane <todd.deshane@xxxxxxx>]

On Mon, Jul 11, 2011 at 3:11 PM, Ronny Bull <bullr@xxxxxxxxxx> wrote:
> I have an issue with VLANs that was in XCP 1.0.0 and also persisted after
> the upgrade to XCP 1.1.beta.  I updated to the beta because I spoke with
> someone in #xen-api that suggested that a fix to the issue would be
> implemented in 1.1, it seems it may have been overlooked or I have a
> different issue.
>

I think this appears similar to:
http://forums.citrix.com/thread.jspa?threadID=280048&start=30&tstart=0

Are these NICS in the XenServer 5.6 FP1 or FP2 HCL?

> Currently the server has 2 network cards:
>
> 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
> Connection (rev 05)
> 02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network
> Connection
>
> eth0 is the designated as the management interface and is connected to a
> port on VLAN 193
> eth1 is the interface used by the VM's and is connected to a trunked switch
> port to provide VLAN access to the VM's
>
> Before moving eth1 to a trunked port without vlanning I could ping it's ip
> address and ssh to it.  After moving it to the trunked port I have no
> connectivity to it whatsoever.  The only way I can get a response from it is
> to ping the static IP on the local machine.  The VM's are using the
> interface on the created VLANS almost perfectly however they sometimes
> exhibit strange behaviour such as loss of connectivity when connecting to
> another machine crossing over a vlan.
>
> I setup my vlans using the XenServer guide here is the output of pif-list:
>
> ******************************
> ****************************************************
>  xe pif-list
> uuid ( RO)                  : 3ebae448-8520-1d92-32b8-322be6018909
>                 device ( RO): eth0
>     currently-attached ( RO): true
>                   VLAN ( RO): -1
>           network-uuid ( RO): 0eb1efb3-60c4-f754-ccee-607ea7419524
>
>
> uuid ( RO)                  : 32ab2f2a-601e-766e-d71b-9ca1d7e6339f
>                 device ( RO): eth1
>     currently-attached ( RO): true
>                   VLAN ( RO): 200
>           network-uuid ( RO): cef0cc98-274d-102f-4441-7327c888dcd2
>
>
> uuid ( RO)                  : d14427c2-4940-0db1-7d96-f55434af319e
>                 device ( RO): eth1
>     currently-attached ( RO): true
>                   VLAN ( RO): 201
>           network-uuid ( RO): 85a9aba5-73ea-4008-0a28-395c96be30fd
>
>
> uuid ( RO)                  : e602777f-b4e9-e231-7858-81189c47c434
>                 device ( RO): eth1
>     currently-attached ( RO): true
>                   VLAN ( RO): -1
>           network-uuid ( RO): df87728a-e4a7-a16e-9f8c-c4c4c26dc35f
>
>
> uuid ( RO)                  : 753ee4aa-d286-b66b-d0c0-8c212ac0cca5
>                 device ( RO): eth1
>     currently-attached ( RO): true
>                   VLAN ( RO): 193
>           network-uuid ( RO): 7abbb9eb-2507-9a16-c547-2f3dd02bc1d9
>
>
> uuid ( RO)                  : 2fa498da-1749-2822-b194-bf2890491533
>                 device ( RO): eth1
>     currently-attached ( RO): true
>                   VLAN ( RO): 194
>           network-uuid ( RO): 54a0217e-e659-8fc6-7a5c-fef685fe9d7a
>
>
> uuid ( RO)                  : b80d7974-cc00-9db4-213e-e1df3a51f2a8
>                 device ( RO): eth1
>     currently-attached ( RO): true
>                   VLAN ( RO): 207
>           network-uuid ( RO): 0af4cb48-83e4-b417-cb5d-9df528dd587a
>
>
> uuid ( RO)                  : 2934f6a4-1d80-ad36-96a4-5962f669c4f9
>                 device ( RO): eth1
>     currently-attached ( RO): true
>                   VLAN ( RO): 795
>           network-uuid ( RO): 2ce5fe35-ea10-e1a7-c9e3-4f5bfd5c55ab
> *********************************************************************************
>
> I suspected that the issue may lie here:
>
> ************************************************************************************
> uuid ( RO)                  : e602777f-b4e9-e231-7858-81189c47c434
>                 device ( RO): eth1
>     currently-attached ( RO): true
>                   VLAN ( RO): -1
>           network-uuid ( RO): df87728a-e4a7-a16e-9f8c-c4c4c26dc35f
> ************************************************************************************
>
> where the eth1 interface is assigned a VLAN value of -1 when it should be on
> the 201 network.  When I try to do
>
> xe pif-param-set uuid=e602777f-b4e9-e231-7858-81189c47c434 VLAN=201
>
> I get:
>
> Error: Field 'VLAN' is read-only.
>
> How can I assign the interface to the correct VLAN so I can use it again for
> traffic to the server?
>
>
> _______________________________________________
> xen-api mailing list
> xen-api@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/mailman/listinfo/xen-api
>
>



-- 
Todd Deshane
http://www.linkedin.com/in/deshantm
http://www.xen.org/products/cloudxen.html
http://runningxen.com/

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