One thing that can be suggestive is naming conventions... It has to have meaning to you and the organization. I have seen some pretty interesting naming conventions and although I make no promises that what I have is the end all of naming conventions, but since I have been doing this for while I find this a pretty good system and easy to understand. So let's get started!
Well..if you were wondering if changing the IP address of Cisco FMC still works of when I originally posted six years ago...It does! I was running FMC 7.4.2.2 at the time and following my own advice works pretty well. It's also funny that although working working with a different company, we had the same goal -- Migrating data centers!
Something kind of interesting I stumbled on was moving some virtual machines around to a different ESXi host that doesn't have to same storage backend. So they were copied over manually and then imported within VMware vCenter. The machines were running Red Hat and although they were connecting to the same network the operating system was using a different interface name like ens33 instead of ens192.
Microsoft DNS servers have a pretty cool feature called DNS zone scopes which was introduced back with Server 2016 and higher. I knew about this feature a while ago as I had to make it work with a project and it worked wonderful back in 2018. Recently it came up again on a different project that I'm working and although a different use case it also worked like it should. So here's to zone scopes!
So we are kicking the tires a bit and going right into a lab that I've got on my Cisco_CML repository. When I was looking through the CCIE exam topics this lab that I did about ~3 weeks ago does not really fit into the CCIE docs, but I think its a good way to kick the tires. If you got Cisco Modeling Labs for the first time this is a good lab to try it out.