Yeah, it's one of my favorites now. HTTP, RDP, TELNET, and SSH from one pane of glass. It also does Rsh, Xdmcp, VNC, FTP, SFTP, File transers, Mosh, Aws S3, and WSL. Never used it for those though. MobaXterm. God bless!
Do you ever check/clean your fiber? I know you work with it a fair bit, and I'd love to see how you deal with it. I've done research and whatnot, but I don't get to play with fiber much myself, so I'd be cool to see someone who knows what they're doing show off their tips and tricks.
We were beginning to roll them out but now we're going with the AP5020's. We'll have a whole video on our WiFi refresh in the coming months. God bless!
Hey brother! Grace & Peace 2 U from NC! Thanks 4 another great video! Do U keep pre-configured settings, like security and redundancy configs, on a flash drive and just plug it in to configure new switches then configure VLAN's accordingly manually or do you configure all settings manually on each switch in the stack? I always learn new things from your videos! Be well, blessed and safe and To God Be the Glory!! 🙏🏽
I should, but no. I do keep the latest firmware on a USB drive for initial updating. But keeping a copy of my template config is a good idea too! Keep dry over there. God bless!
Yes. We home each switch stack back to two core switches, each of which is geographically separated. That way we can lose the data center OR the hospital basement and still keep connectivity. God bless!
@@NetworkAdminLife It takes less than a minute. Usually 30 seconds after a utility power failure. It needs time for the generators to spin up and run at full power before taking on the load. If it's pre-planned I'd imagine the switch over is quicker. This is one of the reasons why the tests are actually two fold. One is to test the UPS batteries and inverters to make sure they're working properly by taking on a real load and monitor the actual available run times. Second is the generators. You'd be surprised the aging batteries die sooner than expected and watch the servers instantly shut off without warning before the generators are able to take over. The more advanced UPS systems would perform weekly self tests and warn the admins of a possible battery failure. Maintenance and being pro-active is the key.
To the creator of this video: Based on what you said in the video, you have a scenario where devices (The new clinic) are located (or going to be located) in building A. You then say that you need to connect them to the datacenter, which is located in building B. Usually, in such scenarios, the Building A devices are first connected to a switch inside of Building A. This switch is then connected to a switch in the datacenter, Building B, via a single cable (or maybe with another one for redundancy considerations). However, the way you describe it at the beginning of the video, each and every device in building A is going to be directly connected to a switch in the datacenter, i.e. each device will have its own cable running from building A to building B, and there will not be a switch in building A. This kind of topology does not make sense for a multi-building-campus network. I must have misunderstood your explanation of how building A devices will connect to the datacenter in building B. Would you please clarify this?
Typically speaking facilities like this want to see HA setups. So it would need at least 2 trunks between A&B, to 2 switches in B and 2 in A, etc going down the chain so that only the final device connections only have the 1 uplink to their switch, that has 2 uplinks
That comment feels incredibly AI generated, but I mean, those switches are quite clearly being provisioned in the "datacentre" before moving to the clinic building.
I don't see the issue, 2 fibres from the backbone out to an external building, fully managed switches on both ends on their own VLAN, 2 switches in the external building each on their own fibre and linked/stacked, the switches can also be (re)mapped remotely, so plenty of redundancy and failover - the 2 switches in the rack are in there for setup and test purposes, ready to be deployed to the external building
Building A = Datacenter, building B= MDF (alternate data center), building C= new clinic. The switch is currently in building A for setup purposes. Once moved, it will have redundant fiber links back to building A and building C. Four fiber strands to each building, A and B. This will protect from building A going down OR building B going down but not both. The only thing we don't have protection from is a backhoe digging up the fiber conduit out to that end of the campus. You strike me as someone who may be on the Autism spectrum. My son is Autistic. God bless!
@@NetworkAdminLife makes sense to me, if it all goes wrong you can always throw some thin net out the window and hang it in the trees to the other buildings, boy those switches are not cheap but then again you don't mess around when it comes to medical type systems - A nice big network storm will take down most systems
