VMware NSX-T Logical Routing 101 - Part 1. Everything you need to get started. 

Glad it was helpful! Thanks for watching and you have a great day

Thanks so much for the kind comment. You have a great day.

Glad it helped and thanks for watching.. Have a great day

You're very welcome! Thanks for watching. Have a good one.

Glad it was helpful! Have a good one

Wow, thanks! Appreciate the kind comment. Have a great day.

Thanks for your Comment. You have a great day..

Thanks very much. Have a great day

My pleasure. Keep watching more to come.. Have a great day

Thank you! Cheers!

Glad to hear that. You have a great day

Thanks for watching, Have a great day,,

Glad you like them! You have a great day,

Thank you. Have a great day

Glad it was helpful! Have a good one

Glad it was helpful!. Keep watching and have a great day..

Great suggestion! Iam working on a Federation presentation, should be done soon. A demo may be a bit of a challenge, but I can see what I can do.. Have a good day and pass the word.

No problem. Have a great day

You're welcome! Thanks for watching. Have a good one.

Got it on a my list. Have a great day

I will add it to the list. Thanks for watching and have a great day

@@TechUnGlued thank you. I am suggesting this because in cloud director, tenant create only T1 edge. They need to establish vpn,nat and another services. I am wonder how this looks and works with combination t0(which we use for external connectivity). Also if t0 and t1 is for multitenancy why we cant configure outside access on t1, why we need to configure it on t0? Thank you

Thanks for watching.. As I mentioned I will add it to the list. I am working on a few projects now, and will see if I can do this video sooner. The main thing here is not to compare it to NSX-V (totally different),, VPN service is supported on the T1 gateway. You must make sure you associate the T1 now with an Edge cluster, because the T1 VPN/NAT services will require an SR component.. When you create the VPN service and associate it with the T1, you must make sure that the T1 "Route Advertisement" includes you IPsec end points and NAT ip' so that the T0 is aware of it. The T0 must then have "Route Redistrbution" enabled for these T1 services so the ouside world is away of it... Just like we did with the routing.. T0 is the G/W that is connected to the physical environment (the SR component on the Edge(s)) and your T1 must go through the T0 to get to the outside world.. Hope this helps..

@@TechUnGlued hello, thank you for your answer. Ofcourse when i creating t1 gw i associate with t0 and have edge cluster.on my phsycal infra i have one vlan/subnet of public ip /24 which i am giving to customer.behind customer t1 gateway is customer private networks. But t1 is connected to t0 via link which is automaticly created. Where i define this public ip from public pool to can use for example tenannt a t1 router. When i establish vpn from customer to datacenter t1 router i must choose t1 customer public ip. But on t1 there is no external interface like on t0? Thank you for answers

First. If you are going to do SNAT/DNAT on the T1 you need to associate a cluster with it. Preferrably a different edge cluster that the T0 has. Then create the NAT rule (SNAT/DNAT) on the T1.. In order for the outside IP (used in the NAT rules) to be advertised to the outside world, you need to set "Route Advertise" on the T1 Advertise "All NAT IP's". This will inform the T0 g/W about the ip you are NATting. Then you must configure the route Redistribution on the T0 to redistribute the Advertised T1 "NAT IP".. I hope this helps. I will do a video on it, after I finish some projects.. Thanks

You are correct. You can try it out. Just create a segment and connect 2 VM's to it. Don't hook the segment to aT1 or T0 G/W and the 2 VM's will be able to talk to each other. I think I demo'd that in my switching video.. Thanks for watching and have a good one.