pvlans

Similar Questions

• UCS 1.4 support for PVLAN

  Hi all

  Cisco UCS 1.4 Adviser supports PVLAN. But I see the following comment on PVLAN in point 1.4 of the UCS

  "UCS extends PVLAN support for virtualized (without vSwitch) deployments."

  "UCS release 1.4 (1) supports isolated PVLAN support for physical server paths or Palo NAC vNIC ports."

  Is that means PVLAN will not work for the virtual machine if VMs is connected to the UCS by Nexus1000v or vDS even if I use the card of PALO (M81KR)?

  Could someone can confirm that?

  Thank you very much!

  Hello

  Yes - PVLANs must be from end to end.

  You can extend the PVLAN set to 1000v and then to bare metal (attached to UCS) servers to a port promiscous * outside * UCS as a backup station or a L3 interface.

  Pls remember that promiscous ports are not supported in UCS. Only access isolated at the moment.

  With the M81KR adapter (Palo), you must create a diff for each interface isolated VLAN (as UCS cannot do isolated trunks yet).

  In you case you seem to have 1 isolated VLAN vNIC so 4 total giving to the 1000v running ESX.

  2 vNIC for VLAN regular (load sharing and redundancy)

  2 network cards for the VLAN isolated (load sharing and redundnacy).

  See attached a doc that talking abt doing which I think is what you're asking.

  Thank you

  -Matt

• Connecting two SG300 PVLAN context.

  We own two SG300-28, set at level to 1.4.0.88 firmware.

  We want to use in a configuration PVLAN/communities, connected to a router.

  On the first switch, I can verify that I have independent communities, who have the right external connection via the promiscuous port.

  Now, I have to connect the second switch (which has the same PVLAN and communities IDs) to the first, to share communities and the promiscuous port.

  But what should be the configuration on each port of the link between the switches?

  I tried a lot of things (even a simple trunk without VLAN, as said somewhere...)  but can't a working configuration...

  Please come back to this day.  It seems to me that you don't need private VLAN for anything good.  Maybe I don't understand the private VLAN correctly, but I do not understand why they are necessary for your specified requirements that seem to describe VLAN "regular":

  All theses stations looking for these constraints:

  • All stations can access the stations of their Department, but can not see the other resorts scalable.
  • All the station can access the Internet.

• Add several ID PVLAN to dvSwitch?

  Hi guys,.

  I have an existing with an existing primary PVLAN dvSwitch, I want to add multiple VLAN community, I tried some scripts without much luck, any help is appreciated.

  PowerCLI features you need are in Luc blogpost. You can cut and paste into your PowerCLI session or you can save them in a .ps1 file and load the file into your PowerCLI session by point of supply of the file. For example:

  PowerCLI C:\ >. .\dvSwitch.ps1

• VDS and Cisco 3750 - PVLANS

  I was not able to get the VDS to talk to the physical switch (Cisco 3750 running IOS 12.2 (53) SE). I tried many different configurations. Can what comments you make on how to get this working. Here are 3 different configurations I tried:

  Installation: I have 3 servers vSphere4 attached through 2 connections each to a Cisco3750. I created a dvSwitch and added the VLAN (100) primary and selected secondary 101 of VLAN (isolated) and the secondary VLAN 102 (community). Communication on the PVLANS work in the ESX servers as they are supposed to, but I can not connect on these PVLANS Cisco switch.

  The 3750 is in talks with the firewall on vlan 100, but will not speak for here ESX Servers configurations I tried and all have failed. What I am doing wrong?

  Configuration 1: (affecting the switchports promiscuity and the use of the mapping of layer 2 to pvlans)

  VLAN 100

  private - vlan primary school

  private - vlan association 101-102

  !

  VLAN 101

  name PVLAN_Isolated

  private - vlan isolated

  !

  VLAN 102

  name PVLAN_Community

  Community of private - vlan

  !

  interface FastEthernet1/0/1

  Description ESX_VM_Trunk_Ports

  switchport private - vlan mapping 100 101-102

  switchport mode private - vlan promiscuity

  spanning tree portfast

  spanning tree enable bpduguard

  !

  interface FastEthernet1/0/2

  Description ESX_VM_Trunk_Ports

  switchport private - vlan mapping 100 101-102

  switchport mode private - vlan promiscuity

  spanning tree portfast

  spanning tree enable bpduguard

  !

  interface FastEthernet1/0/3

  Description ESX_VM_Trunk_Ports

  switchport trunk encapsulation dot1q

  switchport private - vlan mapping 100 101-102

  switchport mode private - vlan promiscuity

  spanning tree portfast trunk

  spanning tree enable bpduguard

  !

  interface FastEthernet1/0/4

  Description ESX_VM_Trunk_Ports

  switchport trunk encapsulation dot1q

  switchport private - vlan mapping 100 101-102

  switchport mode private - vlan promiscuity

  spanning tree portfast trunk

  spanning tree enable bpduguard

  !

  interface FastEthernet1/0/5

  Description ESX_VM_Trunk_Ports

  switchport trunk encapsulation dot1q

  switchport private - vlan mapping 100 101-102

  switchport mode private - vlan promiscuity

  spanning tree portfast trunk

  spanning tree enable bpduguard

  !

  interface FastEthernet1/0/6

  Description ESX_VM_Trunk_Ports

  switchport trunk encapsulation dot1q

  switchport private - vlan mapping 100 101-102

  switchport mode private - vlan promiscuity

  spanning tree portfast trunk

  spanning tree enable bpduguard

  !

  interface Vlan100

  Description «PVLAN» primary

  74.X.X.X 255.255.252.0 IP address

  no ip redirection

  private - vlan mapping 101-102

  Configuration 2: (definition trunk port to the VLAN as its primary VLAN native)

  VLAN 100

  private - vlan primary school

  private - vlan association 101-102

  !

  VLAN 101

  name PVLAN_Isolated

  private - vlan isolated

  !

  VLAN 102

  name PVLAN_Community

  Community of private - vlan

  !

  !

  !

  interface FastEthernet1/0/1

  Description ESX_VM_Trunk_Ports

  switchport trunk encapsulation dot1q

  switchport trunk vlan 100 native

  switchport trunk allowed vlan 101 102

  switchport mode trunk

  Speed 100

  full duplex

  spanning tree portfast

  spanning tree enable bpduguard

  !

  interface FastEthernet1/0/2

  Description ESX_VM_Trunk_Ports

  switchport trunk encapsulation dot1q

  switchport trunk vlan 100 native

  switchport trunk allowed vlan 101 102

  switchport mode trunk

  Speed 100

  full duplex

  spanning tree portfast

  spanning tree enable bpduguard

  !

  interface FastEthernet1/0/3

  Description ESX_VM_Trunk_Ports

  switchport trunk encapsulation dot1q

  switchport trunk vlan 100 native

  switchport trunk allowed vlan 101 102

  switchport mode trunk

  Speed 100

  full duplex

  spanning tree portfast trunk

  spanning tree enable bpduguard

  !

  interface FastEthernet1/0/4

  Description ESX_VM_Trunk_Ports

  switchport trunk encapsulation dot1q

  switchport trunk vlan 100 native

  switchport trunk allowed vlan 101 102

  switchport mode trunk

  Speed 100

  full duplex

  spanning tree portfast trunk

  spanning tree enable bpduguard

  !

  interface FastEthernet1/0/5

  Description ESX_VM_Trunk_Ports

  switchport trunk encapsulation dot1q

  switchport trunk vlan 100 native

  switchport trunk allowed vlan 101 102

  switchport mode trunk

  Speed 100

  full duplex

  spanning tree portfast trunk

  spanning tree enable bpduguard

  !

  interface FastEthernet1/0/6

  Description ESX_VM_Trunk_Ports

  switchport trunk encapsulation dot1q

  switchport trunk vlan 100 native

  switchport trunk allowed vlan 101 102

  switchport mode trunk

  Speed 100

  full duplex

  spanning tree portfast trunk

  spanning tree enable bpduguard

  interface Vlan100

  Description «PVLAN» primary

  74.X.X.X 255.255.252.0 IP address

  no ip redirection

  private - vlan mapping 101-102

  config #3 (affecting the trunk port vlan native 2 - another thing that the vlan primary - on the trunk ports on ESX servers)

  VLAN 100

  private - vlan primary school

  private - vlan association 101-102

  !

  VLAN 101

  name PVLAN_Isolated

  private - vlan isolated

  !

  VLAN 102

  name PVLAN_Community

  Community of private - vlan

  !

  !

  !

  interface FastEthernet1/0/1

  Description ESX_VM_Trunk_Ports

  switchport trunk encapsulation dot1q

  switchport vlan trunk native 2

  switchport trunk allowed vlan 101 102

  switchport mode trunk

  Speed 100

  full duplex

  spanning tree portfast

  spanning tree enable bpduguard

  !

  interface FastEthernet1/0/2

  Description ESX_VM_Trunk_Ports

  switchport trunk encapsulation dot1q

  switchport vlan trunk native 2

  switchport trunk allowed vlan 101 102

  switchport mode trunk

  Speed 100

  full duplex

  spanning tree portfast

  spanning tree enable bpduguard

  !

  interface FastEthernet1/0/3

  Description ESX_VM_Trunk_Ports

  switchport trunk encapsulation dot1q

  switchport vlan trunk native 2

  switchport trunk allowed vlan 101 102

  switchport mode trunk

  Speed 100

  full duplex

  spanning tree portfast trunk

  spanning tree enable bpduguard

  !

  interface FastEthernet1/0/4

  Description ESX_VM_Trunk_Ports

  switchport trunk encapsulation dot1q

  switchport vlan trunk native 2

  switchport trunk allowed vlan 101 102

  switchport mode trunk

  Speed 100

  full duplex

  spanning tree portfast trunk

  spanning tree enable bpduguard

  !

  interface FastEthernet1/0/5

  Description ESX_VM_Trunk_Ports

  switchport trunk encapsulation dot1q

  switchport vlan trunk native 2

  switchport trunk allowed vlan 101 102

  switchport mode trunk

  Speed 100

  full duplex

  spanning tree portfast trunk

  spanning tree enable bpduguard

  !

  interface FastEthernet1/0/6

  Description ESX_VM_Trunk_Ports

  switchport trunk encapsulation dot1q

  switchport vlan trunk native 2

  switchport trunk allowed vlan 101 102

  switchport mode trunk

  Speed 100

  full duplex

  spanning tree portfast trunk

  spanning tree enable bpduguard

  interface Vlan100

  Description «PVLAN» primary

  74.X.X.X 255.255.252.0 IP address

  no ip redirection

  private - vlan mapping 101-102

  What I've found, is that Cisco 3750 s are PVLAN informed, but do not support promiscuous chutes for the ESX servers. Only the 4500, 4900 and 6500 s have the possibility of doing circuits PVLAN promiscuity due to their hardware ASICs.

• Implementation of PVLANs

  I tried to implement PVLANs on a vDS and in doing so, I followed the ESX Administrator's guide. I put in place a primary PVLAN (VLAN ID 1) and a secondary community PVLAN (ID, 11). Then, I associate a group of PVLAN the entry ports (1,11). The VM test on this group of port is not accessible. It is accessible, if I set the type PVLAN on PG 'None', it seems to me the dVS working properly.

  Physically, the dvUplink to connect to a Cisco C3750 switch. I would like to know what, if anything, must be stup on the physical switch to get traffic through the PVLAN. The C3750 PVLAN - capable, making PVLAN ID must be set to the physical switch as well. ?

  You will need to create the vlan plvan and community primary private private on the switch. Assign the address of your primary pvlan space.  Associate your vlan community private to your primary pvlan.  Then map your community to the primary pvlan pvlan.  Trunk your physical servers ESX, ports switch and add your plvan community.

  For example... I hope this helps.

  VLAN 1 is the primary PVLAN

  VLAN 11 is PVLAN community

  Choose a subnet for the PVLAN

  1. Installation switch #.

  VLAN 11

  name My_Cluster_PVLAN_Community

  Community of private - vlan

  VLAN 1

  name My_Cluster_PVLAN_Primary

  private - vlan primary school

  private - vlan association 11

  interface Vlan1

  Description My_Cluster_PVLAN_Primary

  xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx IP address

  no ip redirection

  private - vlan mapping 11

  Watch 48 ip xxx.xxx.xxx.xxx

  48 99 standby priority

  48 standby preempt

  end

  1. ESX switch ports.

  interface GigabitEthernet1/2

  Description ESX_VM_Trunk

  switchport

  switchport trunk encapsulation dot1q

  switchport trunk vlan 1 native

  switchport trunk allowed vlan 11

  switchport mode trunk

  no ip address

  Speed 1000

  full duplex

  spanning tree portfast trunk

  spanning tree enable bpduguard

  end

• Switches 2950 with private - vlan

  Hello experts!

  Do you know if switches 2950 private vlan suport? I have updated to IOS and try to configure PVLAN, but this model of switch is not the interface mode command "switchport private - vlan".

  Best regards

  Rodrigo has.

  2950 supports onboard PVLAN don't, which differs from the private VLAN.

  The following link has the support matrix for pvlan on all Cisco switches.

  http://www.Cisco.com/en/us/products/hw/switches/ps708/products_tech_note09186a0080094830.shtml

• Some feature ISE questions

  Hello guys,.

  I am relatively new to the ISE and would like to get some answers on the features and the administration, I could not find in the documentation. Would be great if you could help me :-).

  1. I would use MAB to printers and other devices of dot1x cabable not

  -Are there a way to automate the collection of MAC address? Otherwise I would manually create identitys for each unique device (like a wizzard or something, not .csv)

  -Si MAB is used, ISE has something as a feature of timestamp, where I can detect the devices 'dead '.

  2. we use private for guest access VLAN (just isolated or protected port on 2960 s)

  -Dynamic VIRTUAL local network port configuration works with ISE?

  Thank you and best regards,

  Tarek

  Hi Tarek,

  In regards to Automation collection of MAC addresses to be used for the MAB, there is not an integrated ISE for this solution. However, you could reduce the amount of work you'd have to do by doing something like sticky with port-security Mac first catch a MACs, then pull them right off the config to ISE manually. Even easier, clearing your arp cache and pull them out after it rebuilds. Do a little cleaning and there you go. It is not as automated as you prefer, but it is better than doing just one by one.

  For the PVLANs, I can't speak with confidence, but I can say that I do not believe it can dynamically assign PVLANs. I guess it's possible, but I saw nothing of if this has been done. I don't think that it can dynamically build the necessary to PVLANs associations. I would like to say that I was wrong on this one, but.

  Hope that helps,

  Ryan

• Traffic filtering and tagging

  Any body has used traffic filtering and marking for traffic filtering, such as the declining traffic, creating port includes restrictions by vm, or the creation of DMZ as sets of rules, etc.?

  Thank you

  Sam

  Well, you don't need NSX, this is a core feature of the distributed vSwitch available since vSphere 5.5, it allows you to create a layer 2 and layer rules firewall of 3/4 on distributed distributed groups of ports or ports.

  I used it to isolate the virtual machines on the DMZ network similar to what would achieve a PVLAN configuration and I would say that it works pretty good, at least on a small scale.

  Check out these links:

  http://blogs.VMware.com/vSphere/2014/03/vSphere-distributed-switch-traffic-filtering.html

  https://pubs.VMware.com/vSphere-60/topic/com.VMware.vSphere.networking.doc/GUID-67CA4C18-4F18-4E23-A5C7-BC33112D4433.html

• ESXI 5.5: Creating huge network separated on layer 2

  Hey,.

  I am interested in creating a network between the virtual machines of 300-500 connected to a single virtual machine separated in layer 2

  First of all I thought to insert all the machines in a portgroup and separate them with a VLAN, but it is not possible to connect the single to more than one virtual machine VLANs simultaneously

  Second, I tried to create a switch distributed with 300 exchanges (each portgroup has two ports - one for a virtual machine and the other for the unique virtual machine) but I found the maximum allowed per virtual machine network adapters is 10 so it is not possible to connect the virtual machine that is unique in more than 10 exchanges.

  I would be grateful for any other suggestions

  Thank you!

  What you want is an isolated PVLAN.

  This can be created on a dvSwitch. Put your unique virtual machine in the VLAN of promiscuity and all other virtual machines in the isolated PVLAN.

  Each of the virtual machines in the isolated PVLAN will be able to communicate with the virtual machine in the VLAN promiscuity but will not be able to communicate with any of the other virtual machines in the isolated PVLAN.

  It is quite easy to configure, change the settings of the dvSwitch and private VLANS tab, enter an id VLAN for the private VLAN on the right (this will be the promiscuous VLAN) and then to the left, enter an id for the VLAN secondary private and assign isolated. Now, create a portgroup to each of these VLANs and give them your virtual machines.

• Pass name id portgroup vlan

  Hello

  I have several vlan id so I want to get the names of portgroup, where id vlan is configured. We use dv-switches, so I don't want to ask the the vmhost.

  Kind regards

  Bergold

  Of course, but since they have a primary and a secondary VLAN, they are a little different.

  If the VLAN primary you are after, you can use:

  VDPortgroup-get | where {$_.} {Eq - VlanConfiguration.PrimaryVlanId $VLANID}

  If the VLAN secondary you're after, you can use:

  VDPortgroup-get | where {$_.} {Eq - VlanConfiguration.SecondaryVlanId $VLANID}

  So if you want to find all VLAN IDS $VLANID anyone, you can combine them:

  VDPortgroup-get | where {$_.} VlanConfiguration.VlanId - eq $VLANID - or $_. EQ - VlanConfiguration.PrimaryVlanId $VLANID - or $_. VLAN. { SecondaryVlanId - eq $VLANID}

  If you want to find all PVLANs you can use:

  Get-VDPortgroup | where {$_.} VlanConfiguration.VlanType - eq "PrivateVLAN"}

  
  

  Note that you have also the "VLAN Trunking" option in the user interface, which can be a range of VLANS. You can find them by:

  Get-VDPortgroup | où {$_. VlanConfiguration.VlanType - eq "Trunk"} | Select Name, @{N = "Beaches"; E={$_. VlanConfiguration.Ranges}}
  

• vDS causes

  Hello

  I need some suggestions on vDS

  I'm running vswitch so dv01 and VM02 running in a single port group SMV (100) can ping each other then I implement a vDS private VLAN insulation to stop the rattling of the other.

  at this point, I already have 100 name trunk portgroup in a physical switch that I already use in vswitch.

  my questions,

  1 - What are the settings needed to modify the physical switch to use a port trunk-ed even group that previously I was using as a normal portgroup in vswitch.

  2 - my all other management servers are physical like a DNS, Exchange - isolation vDS VLANS will allow them to access the DNS/Exchange?

  VirtualRay Hey,.

  If your PVLAN is 100 your physical switch must have the ability to manage the PVLANs, if not you will have to pass the PVLAN100 as the VLAN isolated inside your PVLAN stay there.

  PVLAN100

  -PVLAN 101 isolated

  -PVLAN 102 community

  PVLAN100 will be your wall switch or firewall.

  Re: Question of DMZ

  When I get to my system that has video on it that I will draw a diagram that hopefully will be able to help see a bit better

  (2.) your other physical servers as DNS, Exchange, ect will be able to speak to what is in your isolated or community if you have a road or a rule in your firewall to do.  If for example VPLAN 101 cannot speak of VPLAN100, who will be your firewall or switch. 102 PVLAN can talk about everything that is also in the same community and PVLAN100.  If pVLAN100 is running to your firewall, then you can put rules in place or the roads instead of having other VIRTUAL networks to talk about some things

  I hope this has helped

• vSphere vSwitch configuration issue

  I'm currently building a multiclient environment with two ESXi hosts in a data center. A SAN will come eventually if I want to start my basic with this thought in mind build before implemented. When comes the SAN, I just plug it in and not have to re-architect my network.

  I use a switch 24 ports of Cisco 2960 S, 1 of my ESXi hosts has 4 network cards and the other has 8 network cards. I don't know that I will NOT use the VMware vDistributed switch.

  The conversation I did with people, I am told I can't achieve any type of aggregation of links on the end of things Cisco and simply let VMware manage everything that LB/ft. I'm open to any argument on this point that I do not take a position be it.

  Since it is a multiple tenant environment, I am curious about vSwitch/PortGroup design with security in mind.

  #1 can I paste all network cards to a single vSwitch and use several groups of ports for each VLAN? It would be a safe method to keep the traffic between the VLANS segmented?

  #2 instead create a vSwitch for each VLAN and paste the appropriate vSwitch? (looks like a waste of the physical NIC for me)

  #3 should I allow all the VLANS or just specify those I want to pass through (security of mind is thought specify)

  More traffic will take place in the VLAN and WAN, maybe 5% of the traffic will be routed between the VLANS (I read that routing between vSwitches would have on my firewall if between two vSwitches)

  It will hit my Sonicwall firewall that has 6 network adapters. I thought that I would use two network cards on the Sonicwall assigned to different VLANS on my different vSwitches or exchanges (according to the method I). I know the side of the config of the Sonicwall well enough, but I want to keep all traffic to occur on the Cisco 2960 S if it resides on any network on this switch.

  Good,

  So until you have multi tenant VM isolated with no communication between them, you have two options.  (Option 1).  Take advantage of your physics of switching / VLAN / and Firewall to create the speration and control.  (Option 2).  Use PVLANS.

  If you want more information on PLANS to let me know and I'll send you a link to another post I did which addresses in detail about this.

  With this ISC here any visio drawing VERY fast just to get what you want to do.

  Diagram1

  

  Diagram2

  

  Digram3

  

  OK, so moving forward with your setup your life / configuration will be much easier if you could get 6-8 network interface cards on your first host that currently has 4 network cards, however if you can not lets talk about how you get to do what you want.

  Let's start with your ESXi host at 8 cards just to get the idea everywhere so the address that with 4 network cards then.

  So, you will want to create 3 vSwitches:

  (1.) one for management and vMotion this switch will have 2 vmnic assigned for all external communications

  (2.) one for iSCSI with 2 vmnic assigned for the multipath

  3.) for the virtual computer network and all the other networks, you will need for isolation / multi-tenent 4 network cards for the traffic of the virtual machine.  Feel free to borrow this switch network cards if you need it for other purposes

  Now as every vmnic on all vswitchs will be several VLANS through them, you will need to the trunk ports on the physical switch and tag all the VLANS which could pass these network cards. For example, management - VLAN 10, vMotion - VLAN 20 times will go on vmnic0 and or vmnic1.  If the ports that these network cards to connect must be resources shared with vlan 10 and 20 tag on them.  If you have other questinos on this topic let me know

  Ditto for iSCSI however group in the vSwitch iSCSI, most people put the ports in the access mode, which essentially qui essentiellement definit defines just one vlan to everything that is connected to this port by default so you don't require to a VLAN on the port

  Now for all VM networks.  Each of them will be have their own network and VLAN.  In defining a VLAN and a separate network, you can set each one to a different gateway which will your Sonicwall.  Your sonic wall you can create itineraries and or firewall rules to prohibit traffic between networks ect.  If you have any questinos on let me know.

  Now to get your SIN for talking to your virtual machine natively for backup and without going through a data store, you s VM you want this to happen to have two virtual network adapters.  On the normal network on what you want and another on the network backup Nas which will route to the NAS.

  Now for the ESXi host with 4 network cards, you will have more or less the same, the only difference is that your vSwitch0 will do more work that you will have all your networks routing VM, vMotion and ESXi management.  So you have to tag VLAN on ports these network cards work on your physical switch.

  If your planning to your NAS instead of iSCSI you NFS will be limited to only 1 GB throughput and would probably want to watch 10 GB nic if that is the case.  Anyway if that's what you want I would like to know or do not hesitate to ask.

  Also, it would really be a good idea to get a second switch, so you do not have a single point of failure.  CurrentY if you let go of that switch is down and you don't want that once you get a another switch you would simply divide all the vmnic redundent through two switches, both vmnic0 - switch1, vmnic1 - switch2.

  I hope this has helped, let us know if you have any questions.  No this is set in stone is just a quick drawing in order to give you some ideas on how you want to configure everything.

• Isolate the port on a vSphere standard switch traffic

  Hello

  I deploy an environment where I have a pool of 100 virtual machines that live on a switch standard vSphere isolated. The virtual machines to communicate with the rest of the world through a virtual double-NIC machine. This configuration does not work as expected, but I would go a little further and to isolate the connectivity network, such as each virtual machine can communicate with the system of double-NIC and not each other. The switch standard vSphere, the pool of 100 virtual machines are all located on the same VLAN and group ports. I spent some research time through documentation, but I did find a clean way to implement what I want. The best I can get to each of the virtual machines 100 puts their own VIRTUAL LAN, but it is ugly and will be difficult to maintain. Is there something easier that I missed?

  Thank you

  Steve

  PVLAN, but you will need the distributed virtual switch.

• Benefit of DCA on July 15 quick questions

  Hey all,.

  I will write my DCA 15 and had a few questions:

  1.), I have heard many people say that the lab is slow / lag / or sometimes has problems on top of that all the blogs I've read States time is your worst enemey on this test since you essentially about 8 min a question at the end of 26 questions in the time.  In this spirit, I found this on the following blog: http://blog.marccrawford.com/vcap5-dca/

  Use Adobe search for advanced search for something in all PDFs in a folder: when you start the test, open one of the files PDF and the go in editing-> advanced search. Select all PDF Documents in: and then click Browse for location... option.   Navigate to the folder containing the PDF of vSphere PDF files, and then click OK.  Enter your search term and click on the search button. This will allow you to quickly search through all of the PDF files with a single search. That being said, always know specifically for your research or you will end up with a large number of useless results. For example, if you want to find advanced settings to control Admission HA, knowing that the parameters start with das. will result in the targeted search hits. You can practice this technique before the test by downloading the PDF files using Adobe advanced against them.

  Someone has tested it on the review and find that it allows to save their time.  I was memorize pages and chapters of the sections that I believe that I might have to pick up so I can quickly return to it if an impasse, however if it works well and does not tax the lab system I could give it a go

  2.) what the article exhausted blue you feel is struck most, if it is breaking all NDA don't answer, just curious to what were other peoples experiences.

  3,) for my work as preparation for the exam, I took Jason Nash internship Pluralsight.com formally Trainsignal, Ran through the blue print and lab'ed everything I could, walked through the study of Chris Wahl record: http://wahlnetwork.com/2012/07/02/the-vcap5-dca-study-sheet/

  creating notes along the way, Ran in the DCA of Paul VCAP5-DCA objective 2.2 preparation guide - set up and maintain a VLAN, PVLANs and VLAN settings. Adventures in a virtual world, looked at all the other videos on topics that I could and read no matter what additional KB on the themes.  I work with VMware since version 2.5 so I do things everyday for awhile now, but worry not about the stuff you do not on a base on the day the day or the 1 stop stuff like port mirroring.  I have to drive 4 and 1/2 hours for the person testing center nearest professional view of you, so I really don't want to have to re - write this is there anything else that I missed or I can do please let me know, however, I'm almost to the point where I'm tired of study

  Thanks for any advice you can give,

  
  See you soon!

  NSX is not on the DCA550.

  What are the documents you are looking for?  PDF files provided in the review?

  I do not see a name associated with your profile, I guess that you contacted me on TT?