Have never seen any one explaining things about NSX-T in such a simple way. Keep it up.
@fas2603 Жыл бұрын
Very Good Explanation. I have lots of routing backgrounds but no NSX-T. So this was really good for me
@surenderamohan60244 жыл бұрын
Thanks for a wonderful explanation... NSX-T in particular is very dark but you have explained very well... Thanks for the good work and keep sharing...
@NRDYTech4 жыл бұрын
Thank you Surendera! I found it difficult when I first started, so I hope these videos help everyone learn quicker than I did :)
@izzetcanyagc82813 жыл бұрын
Very good explanation about topic and these video series are not like other boring courses keep going 👍
@thomasc22463 жыл бұрын
Not enaugh view dude. Great explanation thank you. Helps me for my VCF deployments.
@MrPankajkr064 жыл бұрын
Very simply put...I like the demo towards the end . Thanks 👍
@SoCal_Flip2 жыл бұрын
One thing to mention, I believe a DR is also instantiated on the Edge Node as well.
@jagannathsamal64222 жыл бұрын
Thank you for this nice explanation about NSX routing.
@affreenmjha41132 жыл бұрын
Great explanation. Please demo more of the CLI commands that we can use for NSX-T troubleshooting.
@NRDYTech2 жыл бұрын
Thanks! 8 months later, I've released a troubleshooting course for NSX-T where I go over more CLI! You can find it here - use NRDYNATION coupon code for 70% OFF! courses.techbytes.io/p/vmware-nsx-t-troubleshooting-fundamentals
@affreenmjha41132 жыл бұрын
@@NRDYTech you are awesome!
@leonmflai3 жыл бұрын
Good sharing. Tks
@glen8442 Жыл бұрын
Awsome content and great explanation! Im a fan 👌
@scottreeve57163 жыл бұрын
This is great. I could use some more detail as to how to provision North of Tier0. At 6:25 it shows the Tier0 GW having 10.25.21.0/24 and 10.25.22.0/24 interfaces and addresses. I don't know how to do that. Just need to use simple static routing to make an off ramp to/from the non-nsx environment.
@hdhillon7742 жыл бұрын
Thanks lot, really good explanation...appreciated
@leeweixin48244 жыл бұрын
Thank you for sharing. Very clear explanation
@hryfrks2 жыл бұрын
Great video, thanks for that!!
@sucram653 жыл бұрын
I just found you channel a few days ago, and it's very relevant to what I've been been struggling with with regard to Cloud Foundation. Could you do another one of these with static routing please?
@NRDYTech3 жыл бұрын
I'll add it to the list! I haven't done a lot with static routing myself, but it's definitely an area I'm missing on the YT :)
@aniszekri7492 жыл бұрын
@@NRDYTech hello any update please, i did not have bgp for my lab i'd like to use static route but i fail :(
@NRDYTech2 жыл бұрын
@@aniszekri749 I'll try to do a video on static route config in NSX-T, just have to find some time
@aniszekri7492 жыл бұрын
@@NRDYTech thanks a lot, in my lab i have not a BGP :( and i configure static route but not work. if you have a tips or a document. please help me
@miltonaece2 жыл бұрын
Great explanation. Can you please share this document?
@gopakumar99093 жыл бұрын
Excellent mate
@sampatalhat65723 жыл бұрын
Hey..All videos are really awesome.. but how I can get in touch with you?
@sylverhawk97304 жыл бұрын
Great content, keep up the good work!!
@NRDYTech4 жыл бұрын
Thank you Haris!
@tambahako6283 жыл бұрын
Thank you for making this video, Mike! It definitely helps my NSX-T journey. I have an exam coming up soon and have seen two answers to the question below. Where are Distributed Firewall logs containing access decisions stored? A. NSX API B. NSX Edge C. NSX Manager D. Hypervisor transport node Some say answer is C and others say it's D What answer would you choose?
@benjay56553 жыл бұрын
i guess Im asking randomly but does someone know a way to log back into an instagram account?? I was dumb forgot the account password. I would love any tricks you can give me!
@andersjaiden14673 жыл бұрын
@Ben Jay Instablaster =)
@benjay56553 жыл бұрын
@Anders Jaiden Thanks for your reply. I found the site through google and im waiting for the hacking stuff atm. Takes quite some time so I will reply here later when my account password hopefully is recovered.
@benjay56553 жыл бұрын
@Anders Jaiden It did the trick and I now got access to my account again. I am so happy:D Thank you so much you saved my ass :D
@andersjaiden14673 жыл бұрын
@Ben Jay glad I could help :)
@dhruvsharma3359 Жыл бұрын
how do we advertise the subnets into BGP neighborship ?
@flesz_3 жыл бұрын
Question about bgp and edges. In our production we have 2 edges and 2 switches. Each edge has bgp peering to each switch. The network is /29. We want to add another edge , but /29 is not enough now and needs expanding. Whats the best way to achieve it without downtime?
@NRDYTech3 жыл бұрын
I haven't thought about this much, but since you can specify different uplink subnets on a per edge basis, perhaps you can deploy a third edge, use a different subnet (not the /29), and use that edge to replace one of your existing edges? I would test it in a lab, but it should work.
@singhsantosh333 жыл бұрын
GOOD THINGS COME IN SMALL PACKAGES :)
@liamchurchman12403 жыл бұрын
Hi could you explain the difference between a tier-0/tier-1 setup like this, and having a tier0/tier-1 setup with a transit connection to a service router? (Which can also be classed as a tier-0 router right?) thanks!
@NRDYTech3 жыл бұрын
Hi Liam! Keep in mind, a T0 does not equal a SR..there is a component of the T0 which is the SR, but also the DR component as well. Same for the T1 as well! It sounds like what you're referring to is often called "Inter-SR Routing". I haven't done anything on this specifically, but basically, this just allows you to have your T0 in Active/Active, and route to other SR components on other edge nodes via a special iBGP/Internal connection formed when Inter-SR is enabled. Perhaps one day I'll do a vid - if I can find the time :)
@liamchurchman12403 жыл бұрын
@@NRDYTech Hi! Thank you so much for the quick response. So, if you had a tier-0 router this could have an SR component, which would be configured as part of the NSX Edge? But the Tier-0 itself wouldn't be part of the edge? I'm just trying to get my head around it so I can explain it to some of my colleagues, as I work for a 3rd party vendor that does service chaining/insertion with NSX.
@liamchurchman12403 жыл бұрын
What I'm getting from this is... - Traffic traversing a tier-1 would need to go via a tier-0 only if it needs east/west connectivity between hosts/segments that it isn't directly connected to? - Traffic needing to go directly out to the physical network from a VM, would go to it's tier-1 DR-> tier-0 DR -> tier-0 SR in the Edge _> Out to physical network? Unless the tier-1 DR is configured to do NAT etc.. in which case it would have its own tier-1 SR automatically created on the edge? Seems strange you would want a tier-1 to have its own SR, if you're running a 2 tier routing topology. Could lead to sub-optimal routing surely, unless you are running a single tier with your tier0/1 DR Please correct me if I am wrong.
@mohamedbennani41223 жыл бұрын
Hi, I recently installed NSX manager, but the web interface is inaccesible "403 FORBIDDEN", & the http service is stoped, even trying to start it with "start http service", but CLI show that an error is occured, Any suggestions ??
@NRDYTech3 жыл бұрын
I haven't seen this before. What kind of resources did you assign to the NSX-T Manager? How much CPU/RAM/etc? It sounds like there's possibly some issues there.
@mohamedbennani41223 жыл бұрын
@@NRDYTech I've installed small NSX manager, which require 4 CPU & 16 GB of RAM, in a server with 2200 MHz for 1 CPU that equal 8800 MHz for 4 CPU, but at vCenter I've seen that NSX manager VM processing with 11000 MHz, could it be the problem ?
@NRDYTech3 жыл бұрын
@@mohamedbennani4122 That is possibly your problem - not enough CPU for the manager. When I boot up my manager, it will easily take 10000 MHz for a while until it fully boots, then it will settle down and consume less. If you only have 8800MHz, it must be maxing out your CPU. Try setting a CPU reservation for your manager VM of something like 5 or 6000 MHz, see if that helps. My lab boxes have 13-14GHz for whatever it is worth.
@mohamedbennani41223 жыл бұрын
@@NRDYTech I'll keep you in touch, thank you so much
@mohamedbennani41223 жыл бұрын
@@NRDYTech I've just tried it, but it's not working, http service won't run, anu suggestions ?