<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities: Message List - vShield &amp;#38; VLANs</title>
    <link>http://communities.vmware.com/community/vmtn/general/security?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Wed, 01 Jul 2009 22:57:17 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-07-01T22:57:17Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: vShield &amp;#38; VLANs</title>
      <link>http://communities.vmware.com/message/1300518?tstart=0#1300518</link>
      <description>&lt;br /&gt;
vShield will work with VLANs. As far as the configuration, if you are installing in a legacy vSwitch using the automated install (see Quick Start Guide) there is no additional configuration required. The automated install will apply the required configuration for the vShield to work with VLANs.&lt;br /&gt;
&lt;p /&gt;
 If you are doing a manual install/installing on vDS, all you have to do is configure the Unprotected and Protected port groups in VLAN trunking mode and select the VLAN range. Instructions for this can be located in page 33 and 34 of the Administration Guide (step 4 of the 'Create the Un/Protected dvPort Group" section)  &lt;br /&gt;
&lt;p /&gt;
&lt;a class="jive-link-external" href="http://www.vmware.com/support/pubs/vsz_pubs.html"&gt;http://www.vmware.com/support/pubs/vsz_pubs.html&lt;/a&gt; &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Wed, 01 Jul 2009 22:57:17 GMT</pubDate>
      <author>carlosVSZ</author>
      <guid>http://communities.vmware.com/message/1300518?tstart=0#1300518</guid>
      <dc:date>2009-07-01T22:57:17Z</dc:date>
      <clearspace:dateToText>4 months, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: vShield &amp;#38; VLANs</title>
      <link>http://communities.vmware.com/message/1298725?tstart=0#1298725</link>
      <description>Yes, there are some VLAN mentions in admin guide. Looks like vShield actually can manage multiple VLANs, but configuration details are still unclear.&lt;br /&gt;
&lt;br&gt;---&lt;br /&gt;
VMware vExpert '2009&lt;br /&gt;
&lt;a class="jive-link-external" href="http://blog.vadmin.ru"&gt;http://blog.vadmin.ru&lt;/a&gt;</description>
      <pubDate>Tue, 30 Jun 2009 14:15:28 GMT</pubDate>
      <author>Anton V Zhbankov</author>
      <guid>http://communities.vmware.com/message/1298725?tstart=0#1298725</guid>
      <dc:date>2009-06-30T14:15:28Z</dc:date>
      <clearspace:dateToText>4 months, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: vShield &amp;#38; VLANs</title>
      <link>http://communities.vmware.com/message/1298502?tstart=0#1298502</link>
      <description>&lt;br /&gt;
I believe its possible, vShield manager can server mutiple vlan only nic should able to read all the vlan tags. more insights can be checked in following docs&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.vmware.com/support/pubs/vsz_pubs.html"&gt;http://www.vmware.com/support/pubs/vsz_pubs.html&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
Will also check in my lab. &lt;br /&gt;
&lt;p /&gt;
Anuj Modi,&lt;br /&gt;
&lt;br /&gt;
If you found my answer to be useful, feel free to mark it as Helpful or Correct.&lt;br /&gt;
&lt;br /&gt;
The latest blogs and articles on Virtulization:&lt;br /&gt;
&lt;a class="jive-link-blog" href="http://communities.vmware.com/blogs/amodi" title="Internet is complete cloud of information and everyone go through most of this information which may be useful to him but sometimes when you really require that information you are unable to find handy. Creating this blog to make handy info...."&gt;http://communities.vmware.com/blogs/amodi&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://vsolutions.compare2shop.com/"&gt;http://vsolutions.compare2shop.com&lt;/a&gt;</description>
      <pubDate>Tue, 30 Jun 2009 10:52:29 GMT</pubDate>
      <author>anujmodi1</author>
      <guid>http://communities.vmware.com/message/1298502?tstart=0#1298502</guid>
      <dc:date>2009-06-30T10:52:29Z</dc:date>
      <clearspace:dateToText>4 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>vShield &amp;#38; VLANs</title>
      <link>http://communities.vmware.com/message/1298466?tstart=0#1298466</link>
      <description>Can vShield serve multiple VLANs?&lt;br /&gt;
&lt;br&gt;---&lt;br /&gt;
VMware vExpert '2009&lt;br /&gt;
&lt;a class="jive-link-external" href="http://blog.vadmin.ru"&gt;http://blog.vadmin.ru&lt;/a&gt;</description>
      <pubDate>Tue, 30 Jun 2009 10:33:12 GMT</pubDate>
      <author>Anton V Zhbankov</author>
      <guid>http://communities.vmware.com/message/1298466?tstart=0#1298466</guid>
      <dc:date>2009-06-30T10:33:12Z</dc:date>
      <clearspace:dateToText>4 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
  </channel>
</rss>

