About mrfixit

mrfixit · ‎09-27-2021

Hi, all, I know this is a old thread, but I wanted to provide some part numbers: Verizon M2MSIM-TRI-NR-D - Able to activate on Verizon, does not work in MX68CW with or without APN. Does work in MX67C and MG21E. M2MTRI-NONRUG-GD-D - Able to activate on Verizon and works with APN vzwinternet in MX68CW (and MX67C). M2MTRI-NONRUG-GT-A - Suggested by Verizon, but unable to procure or test SIM card. Thank you to all who participated in this thread. Your comments helped me fight with Verizon to get this working. SIM card types do matter.

mrfixit · ‎02-19-2021

So, I think I found the "why" in this problem. In the GUI, these functions are on two different pages: Addressing & VLANs and DHCP. But, in the API, these two sections are one function: updateNetworkVlan: { "id": 99, "networkId": "xxxxxxxxxxxxx", "name": "xxxxxxxxxxxxx", "applianceIp": "10.154.99.1", "subnet": "10.154.99.0/24", "fixedIpAssignments": {}, "reservedIpRanges": [ { "start": "10.154.99.1", "end": "10.154.99.49", "comment": "Reserved Range" } ], "dnsNameservers": "x.x.x.x\nx.x.x.x.x", "dhcpHandling": "Run a DHCP server", "dhcpLeaseTime": "1 day", "dhcpBootOptionsEnabled": false, "dhcpOptions": [] } Updating via API works as expected as I can change all of the second octets. But is there a way to change these addresses in the portal without getting an error? Thank you.

mrfixit · ‎02-19-2021

Hi, all, I just cloned a new small MX from an existing working small MX and I'm going through the pages creating the new network. On the Addressing and VLAN page, when I update a VLAN, I get: There were errors in saving this configuration: The first IP address 10.154.99.1 is not in the subnet 10.188.99.0/24. The last IP address 10.154.99.49 is not in the subnet 10.188.99.0/24. So I go to the DHCP page and make an update there. Then I get: There were errors in saving this configuration: The first IP address 10.188.99.1 is not in the subnet 10.154.99.0/24. The last IP address 10.188.99.49 is not in the subnet 10.154.99.0/24. We have a bunch of VLANs and subsequently a bunch of DHCP servers. I have tried changing DHCP Client addressing to: "Do not respond to DHCP requests", but still the same errors. How can I change the second octet on all my entries in Addressing and DHCP without having to start from scratch? Thank you.

mrfixit · ‎02-11-2021

I believe I've pinpointed the concern. The APN on the MX is modifiable in the portal, but the APN on the MG requires modification at the unit itself. Even if safe mode is enabled, the APN cannot be changed from the portal. Our activated SIMs require a custom APN. So local configuration will be required. Thank you.

mrfixit · ‎02-09-2021

Hi, all, just got a hold of a MG21E on trial. Testing the setup procedures. We'd ultimately like to drop ship these units to an IT contractor to install an MX, MR and an MG together. I followed the instructions here https://documentation.meraki.com/MG/MG_Installation_Guides/MG21%2F%2FMG21E_Installation_Guide Like with the MXs, is there a "remote provisioning" procedure where a technician can insert the SIM card, plug it into an MX LAN port to connect to the cloud and get its settings, then connect it to MX WAN2? Or, is a local connection with local configuration always required before installation? Any best practices for rolling these out with a Meraki bundle? Thanks in advance. -MM

mrfixit

Community Record

Badges

Re: MX68CW and Verizon SIM Card Issue

Re: Cloning MX Catch 22 - Can't update Addressing or DHCP

Cloning MX Catch 22 - Can't update Addressing or DHCP

Re: Remotely deploy an MG21/MG21E?

Remotely deploy an MG21/MG21E?

Cloning MX Catch 22 - Can't update Addressing or DHCP