Not really. Having configured a number of meraki devices, they are lacking a huge amount of the features available in regular IOS. If you have a simple enterprise LAN environment they are great, but it's simply not possible to present all the features of IOS in a GUI without it turning into a huge mess. For ISP networks, forget it.
@@EricMagidson true. Look. It's great that they'll open up more options for IT departments that would've instead deployed other vendors who provide simpler experiences, but appeasing customers with a GUI comes at a cost and accommodates bad practices rather than breaking them. GUIs are incapable of being as flexible, fast, or reliable as a command line based interface. In the time it takes one to scroll down to "port isolation" I could've completely configured the entire port. It's also easier to automate and transport changes with command line. Never mind that if a technician doesn't know Cisco IOS, chances are high they shouldn't be configuring Cisco gear on an enterprise network to begin with... GUIs also have several dependencies that may make it impossible to manage a device in the event of a failure: one's disaster recovery plan should most certainly have options that don't involve logging into this GUI. GUIs are also extremely limited in available configuration options and become messy when including legacy support.
@@LegendaryJim To be honest, you are using what i call "Level 1" thought. The way i describe it is you just have a first level thought of "i'm faster than a gui" and your thought stops. Or you think "if you don't know Cisco IOS then you shouldn't be setting up networks". But here is where all of this fails. Let me give you a few examples. Even with some of the best network management ssh apps etc, i can find the switch that i want, the port that i want and i can do that all before you can even connect to a switch. I can also see if 9 switches are down at the same time or if it's just 1, 2 or 3 in a given area in just seconds. I type "Fin" and all my finance switches appear and with graphs and connectivity. This kind of task will not be available to a normal network guy without solarwinds or some other network monitoring app. second reason is you assume that meraki is only going to be used by network pros. No! they will of course set it up, but with this kind of setup the majority of basic level networking can then be performed by the desktop support teams or even helpdesk. VLAN changes, bouncing ports, confirming connectivity, ability to trace out an issue very fast "where are you" user: not sure "Gimme your pc name plz" User: xxxx "Oh yes according to this you are in warehouse 1.. That is why you cannot connect, we have that location on a different range. Or "my printer isn't working" says the user. You type in hostname of printer and find out that it's not plugged into a VLAN that should be for printers. "Sir did someone move this?" and then you get a yes. 2 seconds later you can see the port that was used is now empty and you change the config over to the new port. All of this done by a 1 guy you pay 50k and not by 3 guys you have to pay 100k.
Thanks Eric. I'm net+ certified working towards the ccna cert who is curious what a Meraki device is. Clear audio and explanation. Thank you
I have 4g sim outdoor cpe router I want to monitor can I use this Cisco meraki switch
I have a isp router which has a dns hijack, can this help? I have a basic understanding of networking,
I am not understanding what you are asking? Rebuild your router.
RIP CLI
Not really. Having configured a number of meraki devices, they are lacking a huge amount of the features available in regular IOS. If you have a simple enterprise LAN environment they are great, but it's simply not possible to present all the features of IOS in a GUI without it turning into a huge mess. For ISP networks, forget it.
never!! XD
@@singechamberlain2967 For Enterprise network there is VMware Velocloud SD WAN
at 8.10 you unfortunately exposed your public IP. I'd hide and reupload
Thanks i just hacked him and stole all of his bitcoin.
@@ragayclark you're such a bitch lol
It was a DHCP IP :)
@@EricMagidson Thats why you are the teacher.
GUI isn't a bonus, it's a detriment...
That is one opinion...
@@EricMagidson true. Look. It's great that they'll open up more options for IT departments that would've instead deployed other vendors who provide simpler experiences, but appeasing customers with a GUI comes at a cost and accommodates bad practices rather than breaking them. GUIs are incapable of being as flexible, fast, or reliable as a command line based interface. In the time it takes one to scroll down to "port isolation" I could've completely configured the entire port. It's also easier to automate and transport changes with command line. Never mind that if a technician doesn't know Cisco IOS, chances are high they shouldn't be configuring Cisco gear on an enterprise network to begin with... GUIs also have several dependencies that may make it impossible to manage a device in the event of a failure: one's disaster recovery plan should most certainly have options that don't involve logging into this GUI. GUIs are also extremely limited in available configuration options and become messy when including legacy support.
@@LegendaryJim To be honest, you are using what i call "Level 1" thought. The way i describe it is you just have a first level thought of "i'm faster than a gui" and your thought stops. Or you think "if you don't know Cisco IOS then you shouldn't be setting up networks". But here is where all of this fails. Let me give you a few examples. Even with some of the best network management ssh apps etc, i can find the switch that i want, the port that i want and i can do that all before you can even connect to a switch. I can also see if 9 switches are down at the same time or if it's just 1, 2 or 3 in a given area in just seconds. I type "Fin" and all my finance switches appear and with graphs and connectivity. This kind of task will not be available to a normal network guy without solarwinds or some other network monitoring app. second reason is you assume that meraki is only going to be used by network pros. No! they will of course set it up, but with this kind of setup the majority of basic level networking can then be performed by the desktop support teams or even helpdesk. VLAN changes, bouncing ports, confirming connectivity, ability to trace out an issue very fast "where are you" user: not sure "Gimme your pc name plz" User: xxxx "Oh yes according to this you are in warehouse 1.. That is why you cannot connect, we have that location on a different range. Or "my printer isn't working" says the user. You type in hostname of printer and find out that it's not plugged into a VLAN that should be for printers. "Sir did someone move this?" and then you get a yes. 2 seconds later you can see the port that was used is now empty and you change the config over to the new port. All of this done by a 1 guy you pay 50k and not by 3 guys you have to pay 100k.