RaymundoEC's Accepted Solutions

hey there, from what you pointed, this is just from the generation of the bundle, you should be able to get it from this place to whatever you want, either using cli or a gui, just make sure the support bundle .tgz is there in the same listed steps in the number 3 to be specific. Example from  NSX-T Command-Line Interface Reference : nsx> copy file support-bundle-0.tgz url scp://admin@192.168.210.200/home/admin/ admin@192.168.210.200's password: nsx> otherwise, you can follow this method on the documentation: Collect NSX Intelligence Support Bundles

I'm not super fan of doing it (I learn this on the hard way),  but still I possible check on this offcial blog post form Amit Aneja about this : Next-Generation Reference Design Guide for NSX-T | VMware also check DEsign guide of NSX-t int desing guide: VMware® NSX-T Reference Design

So if you are in the context of NSX-V, UDLR is Universal so DRL and UDRL is basically the same just difference that UDRL is and instance of DRL universal poryected between lets say two NSX Manager instances. so this is used when you enable the pairing of NSx-Managers in xVC NSX mode. my 2 pesos

I'm not an expert in PA but I believe they have white tech papers about models versus throughput supported so from there you can have an Idea on correct dimensioning. So on the policy just consider to map the VMs that are part of the Apps that required this kind of deep inspection from there you can set them to have redirected all traffic, so for the rest of VMs most probably NSX DFW will be enough and you will shine with an optimization of the use of PA instead of redirecting all to PA. so in plain English could be something like having prepared with PA engine while others without since SVM of PA is not possible to vMotioned as you mentioned before. hope this helps

1. will the existing logical network experience total lost of connectivity? R.- Data Plane will no be affected. 2. or the existing logical network will still be able to transmit traffic? R.- same as the previous answer. 3. does the existing logical network need to be deleted and recreate after re-deployment of controllers? R.- No since this will be instantiated at Transport Node, one way to validate this behavior is by doing in something practical as the HOLS. hope this helps --------------------------------------------------------------------------------------------------------- Was it helpful? Let us know by completing this short survey here.

well, my bad on logs, please check this link : Identity Firewall also, check this link from the AD side: https://girl-germs.com/?p=1538 if you have access to myVMware open a TSR what I read the GSS has lots of tricks to look under. hope this helps.

hi there, if you speak Spanish,and if possible, please be so kind to explain your problem in Spanish, otherwise I strongly recommend to use VMware HOL labs as lab not following the script provided for tasks in order to cover exam blue print for the exam, it simply works as a charm. If you need a guide for BP let me know and I can provide the one I use for that. regards.

Hi Assuming you have vSphere installed, then for default it creates a VSS for management, then if you plan a VLAN for management tag on that VSS there will be a vmkernel portgroup and the ip address of ESXi host for each of them, then install vCenter Server, add the ESXi hosts to the governance of vCenter, vCenter must be in same VLAN of ESXI host for management, then create a cluster with those ESXi hosts, after that create a VDS just be sure you have vnics avilable, when you create the VDS create the dvPortgroups for your VLANs tags and migrate management from VSS, note that your VLANS whatever they are mus be presented in all physical nics on physical machines, if not , no matters if you tag the VLAN they won't be available for any virtual switch VSS or VDS. VSS: Standard switch VDS : distributed switch regards.