Everything seems to be working well now, I think my issue with ssh and other ports are related to a firewall. Thank you very much for helping me solve this issue. I will let you know if I come across anything else.
Ronny On Tue, Jul 12, 2011 at 1:02 PM, Ronny Bull <[email protected]> wrote: > Here are the steps I just performed: http://pastebin.com/0zZAfHaf > > I can now ping the address from another machine but cannot ssh to it or > telnet to any open ports. > > Ronny > > > > > On Tue, Jul 12, 2011 at 12:02 PM, Rob Hoes <[email protected]> wrote: > >> Yes, that is correct.**** >> >> ** ** >> >> Cheers,**** >> >> Rob**** >> >> ** ** >> >> *From:* Ronny Bull [mailto:[email protected]] >> *Sent:* 12 July 2011 17:01 >> *To:* Rob Hoes >> *Cc:* [email protected] >> >> *Subject:* Re: [Xen-API] XCP: VLAN Issue**** >> >> ** ** >> >> Rob, >> >> If I understand you correctly I am to remove the ip address assigned to >> xenbr1 ie (eth1) which is associated with the following PIF: >> >> 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 >> >> Which is connected to the trunked port on the switch. >> >> And instead I am to assign that IP address to the following PIF: >> >> 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 >> >> Which will allow me to communicate to dom0 over that PIF (201) on the VLAN >> as well as allow me to assign VM's to that network. Since currently the ip >> address that is assigned to eth1 has no idea what vlan it belongs on. So I >> would leave the real eth1 (-1) interface without an IP >> >> Thank you for your time with this, >> >> Ronny**** >> >> On Tue, Jul 12, 2011 at 11:39 AM, Rob Hoes <[email protected]> wrote:** >> ** >> >> [cc: xen-api list]**** >> >> **** >> >> Hi Ronny,**** >> >> **** >> >> If you want an IP address in dom0 that is on a VLAN (is that what you >> want?), you need to configure the VLAN PIF, i.e. the PIF that has VLAN != >> -1, the one I mentioned in my previous email. The IP address will then be on >> the bridge associated with that VLAN PIF, which would have a name starting >> with “xapi”. The bridge xenbr1 is associate with eth1, which is a trunk port >> in your case, so traffic on a VLAN will not end up at xenbr1 (only untagged >> traffic will).**** >> >> **** >> >> Does that make sense?**** >> >> **** >> >> Cheers,**** >> >> Rob**** >> >> **** >> >> *From:* Ronny Bull [mailto:[email protected]] >> *Sent:* 12 July 2011 16:01 >> *To:* Rob Hoes >> *Subject:* Re: [Xen-API] XCP: VLAN Issue**** >> >> **** >> >> Rob, >> >> The ifconfig output from the XCP server >> >> ifconfig >> eth0 Link encap:Ethernet HWaddr 00:25:90:24:69:59 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:141495 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:75020 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:17492967 (16.6 MiB) TX bytes:30338689 (28.9 MiB) >> Interrupt:20 Memory:fba00000-fba20000 >> >> eth1 Link encap:Ethernet HWaddr 00:25:90:24:69:58 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:436201 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:95975 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:174084168 (166.0 MiB) TX bytes:14070571 (13.4 MiB) >> Interrupt:16 Memory:fb900000-fb920000 >> >> 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:127927 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:127927 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:39993933 (38.1 MiB) TX bytes:39993933 (38.1 MiB) >> >> tap2.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:58 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:80973 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:500 >> RX bytes:6087 (5.9 KiB) TX bytes:8969122 (8.5 MiB) >> >> tap3.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:2080 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:84963 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:500 >> RX bytes:331057 (323.2 KiB) TX bytes:14167561 (13.5 MiB) >> >> tap4.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:3036 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:46900 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:500 >> RX bytes:230841 (225.4 KiB) TX bytes:3500104 (3.3 MiB) >> >> tap5.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:46758 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:135103 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:500 >> RX bytes:3217616 (3.0 MiB) TX bytes:132366893 (126.2 MiB) >> >> tap6.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:486 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:46057 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:500 >> RX bytes:52961 (51.7 KiB) TX bytes:4682101 (4.4 MiB) >> >> tap7.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:842 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:45220 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:500 >> RX bytes:114794 (112.1 KiB) TX bytes:3142817 (2.9 MiB) >> >> tap8.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:1896 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:43421 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:500 >> RX bytes:359081 (350.6 KiB) TX bytes:2944250 (2.8 MiB) >> >> tap9.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:39 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:44876 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:500 >> RX bytes:4970 (4.8 KiB) TX bytes:3112078 (2.9 MiB) >> >> tap10.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:67 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:44810 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:500 >> RX bytes:7210 (7.0 KiB) TX bytes:3101504 (2.9 MiB) >> >> tap11.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:55 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:44789 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:500 >> RX bytes:5949 (5.8 KiB) TX bytes:3099327 (2.9 MiB) >> >> tap12.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:698 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:80422 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:500 >> RX bytes:104983 (102.5 KiB) TX bytes:8904041 (8.4 MiB) >> >> vif2.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:80970 overruns:0 carrier:0 >> collisions:0 txqueuelen:32 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> >> vif3.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:80969 overruns:0 carrier:0 >> collisions:0 txqueuelen:32 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> >> vif4.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:44905 overruns:0 carrier:0 >> collisions:0 txqueuelen:32 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> >> vif5.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:44903 overruns:0 carrier:0 >> collisions:0 txqueuelen:32 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> >> vif6.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:44901 overruns:0 carrier:0 >> collisions:0 txqueuelen:32 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> >> vif7.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:44899 overruns:0 carrier:0 >> collisions:0 txqueuelen:32 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> >> vif8.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:44895 overruns:0 carrier:0 >> collisions:0 txqueuelen:32 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> >> vif9.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:44890 overruns:0 carrier:0 >> collisions:0 txqueuelen:32 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> >> vif10.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:44823 overruns:0 carrier:0 >> collisions:0 txqueuelen:32 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> >> vif11.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:44789 overruns:0 carrier:0 >> collisions:0 txqueuelen:32 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> >> vif12.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:80111 overruns:0 carrier:0 >> collisions:0 txqueuelen:32 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> >> vif14.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF >> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 >> RX packets:20823 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:99649 errors:0 dropped:14 overruns:0 carrier:0 >> collisions:0 txqueuelen:32 >> RX bytes:2837628 (2.7 MiB) TX bytes:13126667 (12.5 MiB) >> >> xapi1 Link encap:Ethernet HWaddr 00:25:90:24:69:58 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:80977 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:8965513 (8.5 MiB) TX bytes:0 (0.0 b) >> >> xapi2 Link encap:Ethernet HWaddr 00:25:90:24:69:58 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:42321 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:2784532 (2.6 MiB) TX bytes:0 (0.0 b) >> >> xapi3 Link encap:Ethernet HWaddr 00:25:90:24:69:58 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:43582 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:3176545 (3.0 MiB) TX bytes:0 (0.0 b) >> >> xapi4 Link encap:Ethernet HWaddr 00:25:90:24:69:58 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:45295 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:3136906 (2.9 MiB) TX bytes:0 (0.0 b) >> >> xapi5 Link encap:Ethernet HWaddr 00:25:90:24:69:58 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:0 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:0 (0.0 b) TX bytes:0 (0.0 b) >> >> xapi6 Link encap:Ethernet HWaddr 00:25:90:24:69:58 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:46295 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:3422793 (3.2 MiB) TX bytes:0 (0.0 b) >> >> xenbr0 Link encap:Ethernet HWaddr 00:25:90:24:69:59 >> inet addr:150.156.193.205 Bcast:150.156.193.255 >> Mask:255.255.255.0 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:92591 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:66957 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:14506583 (13.8 MiB) TX bytes:29778363 (28.3 MiB) >> >> xenbr1 Link encap:Ethernet HWaddr 00:25:90:24:69:58 >> inet addr:150.156.201.35 Bcast:150.156.201.255 >> Mask:255.255.255.0 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:275918 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:30 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:25731590 (24.5 MiB) TX bytes:1260 (1.2 KiB) >> >> To be more specific I am having trouble connecting to xenbr1 by it's IP. >> So you are saying that I need to remove that IP from xenbr1 and assign it to >> the PIF for VLAN 201 instead so that I may access dom0 again with the >> 150.156.201.35 IP address? >> >> Thanks, >> >> Ronny**** >> >> On Tue, Jul 12, 2011 at 8:00 AM, Ronny Bull <[email protected]> wrote:**** >> >> Rob,**** >> >> The interface does have an ip assigned 150.156.201.35**** >> >> Ronny**** >> >> On Jul 12, 2011 6:13 AM, "Rob Hoes" <[email protected]> wrote: >> > Hi Ronny, >> > >> > The output of xe pif-list below looks fine. It is normal to have a PIF >> with VLAN=-1: this is the interface that does not tag/untag packets going >> through it. You do have another PIF for VLAN 201 in the pif-list right above >> it: >> > >> > 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 >> > >> > Putting VIFs on the Network for that PIF puts those VIFs on VLAN 201. If >> you want to communicate with dom0 over VLAN 201, you need to put an IP >> address on this PIF using "xe pif-reconfigure-ip >> uuid=d14427c2-4940-0db1-7d96-f55434af319e mode=...". >> > >> > Cheers, >> > Rob >> > >> > From: [email protected] [mailto: >> [email protected]] On Behalf Of Ronny Bull >> > Sent: 11 July 2011 20:11 >> > To: [email protected] >> > Subject: [Xen-API] XCP: VLAN Issue >> > >> > 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. >> > >> > 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 [email protected] http://lists.xensource.com/mailman/listinfo/xen-api
