Name the networks accordingly and you will find the networks at a glance in dashboard. If you have multiple organizations/networks you need to have a well established naming concept. ... View more

Well, when you go to University it is supposed that you already know the alphabet.  This is true also about the Meraki - when you embrace a cloud solution like Meraki, you like the fact that you can click in a nice dashboard but then when you scale, you find out that it does not work and also the old way of making excel templates also don't work, and you can only use APIs. And you must be ready to use the APIs.    The script is in Python and uses the meraki library. I am sure if you'll search in the community you'll find some video guides of how to get started with Python, and then Meraki APIs. I've posted a xx$ worth script, if you want to use of it.. feel free.  ... View more

Because I thought that it might be useful for me in the future. I might have some misses here and there, or not very efficient, but if you're like me and have 40 organizations.. then...     dashboard = meraki.DashboardAPI(x_cisco_meraki_api_key, suppress_logging=True) organizations = dashboard.organizations.getOrganizations() SWITCH = True # Set to True if you want to display the vlans from MX APPLIANCE = True # set to True if you want to display the vlans from MS print("Organization,Network,Type,Subnet,Vlan name,Vlan ID") for org in organizations: networks = dashboard.organizations.getOrganizationNetworks(organizationId=org["id"]) devices = dashboard.organizations.getOrganizationDevices(organizationId=org["id"], productTypes=["appliance", "switch"]) for network in networks: if "appliance" in network["productTypes"] and APPLIANCE is True: networkSettings = dashboard.networks.getNetworkSettings(networkId=network["id"]) try: singleVlan = dashboard.appliance.getNetworkApplianceSingleLan(networkId=network["id"]) print(f"{org['name']},{network['name']},MX,{singleVlan['subnet']},,1") except Exception as e: pass try: vlans = dashboard.appliance.getNetworkApplianceVlans(networkId=network["id"]) for vlan in vlans: print(f"{org['name']},{network['name']},MX,{vlan['subnet']},{vlan['name']},{vlan['id']}") except Exception as e: pass if "switch" in network["productTypes"] and SWITCH is True: switchStacks = dashboard.switch.getNetworkSwitchStacks(networkId=network["id"]) switches = [switch for switch in devices if switch["productType"] == "switch" and switch["networkId"] == network["id"]] for stack in switchStacks: for serial in stack['serials']: for index, switch in enumerate(switches): switches.pop(index) stackVlans = dashboard.switch.getNetworkSwitchStackRoutingInterfaces(networkId=network["id"], switchStackId=stack["id"]) for stackVlan in stackVlans: print(f"{org['name']},{network['name']},MS-stack,{stackVlan['subnet']},{stackVlan['name']},{stackVlan['vlanId']}") for switch in switches: switchVlans = dashboard.switch.getDeviceSwitchRoutingInterfaces(serial=switch["serial"]) for switchVlan in switchVlans: print(f"{org['name']},{network['name']},MS-nonstack,{switchVlan['subnet']},{switchVlan['name']},{switchVlan['vlanId']}")       ... View more

IP band? Or IP subnet? Are you looking for the IP subnet on the WAN interface or the IP subnets configured as L3 on the MXes (Addresses and VLANs) or maybe on L3 switches? If is one of the above, the information can be easily extracted by leveraging APIs. ... View more

Meraki switches are meant to be managed from the cloud. What you are referring to, most probably is the meraki-cli python module that is emulated kind of CLI interface. But that module is making use of Meraki API - and there is no api endpoint for your request.  However, your request is easily done with a script and you will not have to copy/paste anything. ... View more

Well, support did not give me any commands.. but just put me on the right path.  1. your switch should already have aaa new-model in the config, otherwise it will not work. Then inspect your AAA commands and the AAA commands that the application will configure on the switch.  The application will configure new VTY Lines and add the authentication group MERAKI: line vty 32 33 access-class MERAKI_VTY_IN in access-class MERAKI_VTY_OUT out authorization exec MERAKI login authentication MERAKI rotary 50 transport input ssh   Then it will add some aaa to authenticate locally:  aaa authentication login MERAKI local aaa authorization exec default local aaa authorization exec MERAKI local   And if you have the aaa authorization config-commands then this config does not allow meraki-user to authorize, and therefore you must have a special rule to allow "meraki-user" to get privilege level 15. aaa authorization commands 0 default group tacacs+ local aaa authorization commands 1 default group tacacs+ local aaa authorization commands 15 default group tacacs+ local   In my case, it was an authorisation problem. In your case it seems the authentication is not working. Do you have the aaa new-model enabled already?   ... View more

I'll second Brandon's opinion. One more thing that I've observed over the time - the old Cisco phones did not like to be plugged into PoE and have also the external power adapter. Other than that, the wiring guys may buy a PoE tester, they're absolutely not cheap... but may identify problems without killing just another phone... ... View more