RaymundoEC's Posts

RaymundoEC · ‎08-11-2021

Ok try to install the Agent apart, also try to dig if the agent is the cause, sometimes bad drivers make this kind of behavior so also check from the vendor what is adequate for the hardware, reinsta...

Ok try to install the Agent apart, also try to dig if the agent is the cause, sometimes bad drivers make this kind of behavior so also check from the vendor what is adequate for the hardware, reinstall nsxt from each esxi could be an option but is a quick task, so better to verify if the problem is related to drivers or anything else first, take a look on $tail -f /var/log/vmkernel logs to get a better idea. hope this helps

RaymundoEC · ‎08-11-2021

my two cents are: that is not recommended, the reason the upgrade is part of an automated process (ESXi hosts, nsxmgrmg, edges, etc.), and sequence should be care, also is recommended to have mode t...

my two cents are: that is not recommended, the reason the upgrade is part of an automated process (ESXi hosts, nsxmgrmg, edges, etc.), and sequence should be care, also is recommended to have mode than one EDGE VM. check this for more info in formal way: https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.0/nsxt_30_upgrade.pdf

RaymundoEC · ‎08-10-2021

it uses one arm for each segment you create for TKGI

RaymundoEC · ‎06-08-2021

most probably is not the version of the license that you are adding to this is corresponding with the product.

RaymundoEC · ‎06-08-2021

Hi there folks, I have a kind of issue and need somebody to chide me on this, I have a deployment of vSphere with Tazu and the networking is made by NSX-T, so I create a T0 and T1 is being config...

Hi there folks, I have a kind of issue and need somebody to chide me on this, I have a deployment of vSphere with Tazu and the networking is made by NSX-T, so I create a T0 and T1 is being configured thru API call from the wizard, so my question is if this wizard takes the .1 IP address and the GW is defined in the routing peering on the physical side how can be possible to change or handle this? do I have today to the networking guy hey delete the GW and give the governance of this flooring Ip segments (Egress and Ingress) and from there just set up a static route to let the physical network know how to reach this network so that I would be able to change or use .1 on CIDRs on wizard of SCVM? or there is about there a magic trick that I'm missing? PD I also tried to segment the CIDRs but using this I can not reach the network segment since again in an infinity loop from the wizard for SCVM it took the first IP that corresponds to GW and then this guys needs to set the GW in the physical gear and then this is overlapped and then everyone is unhappy. thanks in advance!

RaymundoEC · ‎01-25-2021

check on vmkernel.log to see what it paints there host dst and scr, also did you try to redeploy the EDGE?

RaymundoEC · ‎01-25-2021

look for the success stories on VMware NSX page that could be your best bet, If where you I will take the info and try to meet with them in a VMUG or directly.

RaymundoEC · ‎01-25-2021

thanks man!

RaymundoEC · ‎01-19-2021

thanks for this work, Francois.

RaymundoEC · ‎01-19-2021

questions: "deactivate cluster" could be supported in 2.x? this will be a check box or something in the future, meaning make it easy, os could be invoked thru API call?

RaymundoEC · ‎01-19-2021

very helpful thanks!

RaymundoEC · ‎01-18-2021

Salut, vérifiez la configuration que la VM reçoit de votre VMware Workstation, bien qu'elle puisse utiliser le pont, recherchez l'option suivante Hôte uniquement: Un réseau privé partagé (Host-only:...

Salut, vérifiez la configuration que la VM reçoit de votre VMware Workstation, bien qu'elle puisse utiliser le pont, recherchez l'option suivante Hôte uniquement: Un réseau privé partagé (Host-only: A private network shared); Assurez-vous également que votre FW hôte ne bloque pas le trafic de la machine virtuelle Linux. J'espère que cela peut vous aider.

RaymundoEC · ‎01-18-2021

some answers: R1. yes you can propagate on-prem routes to your VPC routing table. R2.not so sure what you ask here but will give my 2 cents, VPC connection to TGW is thru a vpn which is transparent...

some answers: R1. yes you can propagate on-prem routes to your VPC routing table. R2.not so sure what you ask here but will give my 2 cents, VPC connection to TGW is thru a vpn which is transparent and is not managed by you, also but from the networking piece as far as I know you can have multiple VRFs connected to TGW, from BGP if you have more than 100 routes per VRF are supported only, there is not any kind of traffic/policy control on TGW. cheers

RaymundoEC · ‎01-18-2021

there is not like a rule on this since all the deployments are different NICs are different, servers are different, an internal bus is different, Processor is different, so what I can say is try to ...

there is not like a rule on this since all the deployments are different NICs are different, servers are different, an internal bus is different, Processor is different, so what I can say is try to test by yourself to get a real approximation to the benchmark that u are looking, so for example by the nature of the EDGE VM factor is 10GB/sec max but is not always saturated 8-9GB depending on traffic, so that is why you should test by your env., also another approximation could be to take the number of NSXV ESG so for this is 1M cps, so for EDGE VM in case of NSXT you get lots of improvements in datapath so I infer that numbers could be bigger. hope this helps to approximate to an answer for the baseline fits you.

RaymundoEC · ‎01-01-2021

most Linux flavors have ssh "integrated" no need for special things for it.

RaymundoEC · ‎01-01-2021

check this doc: https://nsx.techzone.vmware.com/resource/nsx-t-vds-7-guide#sec2-sub3 also, check the ref guide on page 24 for more details on finding the "why": https://communities.vmware.com/...

check this doc: https://nsx.techzone.vmware.com/resource/nsx-t-vds-7-guide#sec2-sub3 also, check the ref guide on page 24 for more details on finding the "why": https://communities.vmware.com/t5/VMware-NSX-Documents/VMware-NSX-T-Reference-Design/ta-p/2778093

RaymundoEC · ‎12-28-2020

check on this KB: https://kb.vmware.com/s/article/78223 regards.

RaymundoEC · ‎12-28-2020

Try by using this API call: https://vdc-download.vmware.com/vmwb-repository/dcr-public/787988e9-6348-4b2a-8617-e6d672c690ee/a187360c-77d5-4c0c-92a8-8e07aa161a27/api_includes/method_DeleteInfraSegmen...

Try by using this API call: https://vdc-download.vmware.com/vmwb-repository/dcr-public/787988e9-6348-4b2a-8617-e6d672c690ee/a187360c-77d5-4c0c-92a8-8e07aa161a27/api_includes/method_DeleteInfraSegment.html from this doc. https://code.vmware.com/apis/1083/nsx-t hope it helps.

RaymundoEC · ‎12-22-2020

your best bet is to try to check thru vCenter what are the constructs for VMs and command line from ESXi to check DFW but will be a job to get everything in one shot.

RaymundoEC · ‎12-22-2020

N-S traffic is the one that will enter thru the EDGES, in terms of rules you need to verify if you are using a deny to all other traffic this depends on your approach so to make it simple VM1 ->VM2 ...

N-S traffic is the one that will enter thru the EDGES, in terms of rules you need to verify if you are using a deny to all other traffic this depends on your approach so to make it simple VM1 ->VM2 will have a rule of deny/allow traffic on DFW but if this VM1 needs to reach something outside the overlay if this is the case or the vSphere environment (scope of the DFW) then you will have a DFW rule as well, also check that EDGES doe not have any FW active. my 2 cents .

All

RaymundoEC's Posts

Re: Host installation failed after updating HPE Agentless Management Service

Re: upgrade edge node manually

Re: the IP and DNS required for the TKGI deployment?

Re: NSX-T license error

vSphere with Tanzu and NSXT CIRDs routed overlap GW ip

Re: NSX-T EDGE fp-eth got deleted after vMotion : How we can recover

Re: Deploy NSX-T at a university

Re: NSX-T 3.1 Multi-Location Design Guide (Federation + Multisite)

Re: NSX-T Edge Bridge: Almost everything you wanted to know

Re: NSX-T 3.1 Multi-Location Design Guide (Federation + Multisite)

Re: NSX Advanced Load Balancer (by Avi Networks) Encyclopedia

Re: installation debian network adapter bridged

Re: VMC on AWS T0 Transitive Routes for Connected VPC?

Re: NSX-T Load testing Edge Transport Nodes (VMs)

Re: NSX-T 3 Backups

Re: VLAN Backed segments are not visible in vCenter

Re: Bare Metal Host Transport Node

Re: Unable to delete segment or router links in NSX 3.1.0

Re: Recover NSX?

Re: Nsxt DFW allow all northbound traffic