[166906] in North American Network Operators' Group
Re: Meraki
daemon@ATHENA.MIT.EDU (Joshua Goldbard)
Tue Nov 19 12:30:36 2013
From: Joshua Goldbard <j@2600hz.com>
To: Hank Disuko <gourmetcisco@hotmail.com>
Date: Tue, 19 Nov 2013 17:30:24 +0000
In-Reply-To: <BLU180-W90FEB28A006AFDA2ABE4C2C9E70@phx.gbl>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
I've used them on a bunch of field deployments. Love'em. When clients have =
them it makes documenting any part of the experience a technician level tas=
k.
Need a pcap? Built into the GUI. Want the switch to SMS you when ports get =
knocked out? Built into the GUI. Do you like visuals that actually make som=
e goddamn sense? Meraki has it.
I never had to go into the command line for any reason, at least not so far=
.
I can say they had some issues detecting the ubiquiti access points at a cl=
ient site but I think that had more to do with faulty internal wiring than =
anything else.
Anyways, I like'em.
Cheers,
Joshua
Sent from my iPhone
On Nov 19, 2013, at 9:26 AM, "Hank Disuko" <gourmetcisco@hotmail.com> wrote=
:
> Hi folks,=20
>=20
> I've traditionally been a Cisco Catalyst shop for my switching gear.
>=20
> I am doing a significant hardware refresh in one of my offices, which wil=
l entail replacing about 20 access switches and a couple core devices. Pre=
tty simple L3 VLAN environment with VRRP/HSRP, on the physical end I have 1=
G fibre/copper and 10G fibre. My core switch of choice will likely be the =
Cat 4500 series.
>=20
> I'm considering Cisco's Meraki platform for my access layer and I'm looki=
ng for deployment stories of folks that have deployed Meraki in the past...=
good/bad/ugly kinda stuff.
>=20
> I know Meraki hardcores were upset when Cisco acquired them, but not exac=
tly sure why.
>=20
> Anyway, any thoughts would be useful. Thanks!
>=20
> -Hank
> =20
