Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About GoOn
GoOn
Getting noticed
Member since Jun 25, 2021
Apr 19 2024
Community Record
24
Posts
9
Kudos
1
Solution
Badges
Apr 19 2024
5:48 AM
Hello everyone! Excuse me if this question is banal, but I wanna be sure before buying, since the expense is not actually low. I have an office with an MX65W installed. Now the company create a new site, and both have to be connected in VPN. If I buy an MX68CW, can I establish a VPN site-to-site connection using Meraki Auto VPN tunneling? Is there any incompatibility beween the two models? Thanks in advance
... View more
Labels:
- Labels:
-
Auto VPN
Jan 20 2023
8:05 AM
Hello to everyone! Since the last night, I receive the following error trying to call my API, for every request: VPN status, switches status and access points too. System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send.. ---> System.IO.IOException: Authentication failed because the remote party has closed the transport stream. in System.Net.TlsStream.EndWrite(IAsyncResult asyncResult) in System.Net.PooledStream.EndWrite(IAsyncResult asyncResult) in System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar) It started going in error whithout changes by my side. I use the NuGet package Meraki.Dashboard by Anthony Langsworth (GitHub - NTTLimitedRD/Meraki.Dashboard: A strong-typed, mockable Cisco Meraki Dashboard API .Net Standard client library.) The authentication call below is correctly working MerakiDashboardClient MerDashboardClient = MerakiDashboardClientFactory.Create(StrMerakiApiKey) but I receive the error at string StrJsonAvailab = await MerDashboardClient.Client.GetAsync("https://api.meraki.com/api/v1/organizations/" + StrMerakiOrganizationId + "/appliance/vpn/statuses?networkIds[]=" + StrDeviceId); This code was working until last night, I repeat: nothing changed on my side... Anyone has the same issue? I already checked under Organization -> Configure -> Settings on my dashboard and I found the API correctly enabled and Last used value, under my profile page -> API access, is reporting a few minutes ago. Thanks in advance!
... View more
Oct 27 2021
9:11 AM
4 Kudos
It seems that the settings "IGMP snooping" and "Flood unknown multicast traffic" set to "Enable" do the job!
... View more
Oct 27 2021
8:01 AM
UDLD on port where SNOM cells are connected could be a problem? If Yes, I saw its property could be set "Alert Only" or "Enforce": how to completely disable it?
... View more
Oct 26 2021
11:42 PM
Multicast for sure, I don't know if they use other methods in addition. In Switch settings I already disabled "IGMP snooping" and "Flood unknown multicast traffic", but without success!
... View more
Oct 26 2021
12:12 AM
I have a phone system that uses DECT IP cordless phones. The system also has SNOM M900 DECT IP cells to cover the headquarters offices. If I connect a cell on HP or Aruba switches all is working fine. If I connect the same cell on MS220 or MS120 Meraki switches, cell is currently available, reachable by its IP address, seems it works fine for all except it's unable to find other cells and start muli-cell working system, that is needed to maintain call active when a cordless move from an area covered by a cell to another area covered by another one. Telephones and cells are on a dedicated VLAN and the port where I connect cells are set as "Access", with that VLAN. It's quite interesting also that cells connected to an HP switch, connected in cascade to an MS220, are working fine. If I connect a cell directly to the MS220 (on an Access port), I have the issue described. Any suggestion? Thanks in advance!
... View more
Oct 8 2021
2:21 AM
Yes, thanks. But I have to avoid that incoming traffic will come in!
... View more
Oct 7 2021
12:48 PM
I want to avoid clients based on non-meraki peer can access my clients. Them are the origin. So, I don't have those remote clients in my list, because the are on a non-meraki peer. I have only my clients in my list. So, how can I block the remote ones to acces to mine?
... View more
Oct 7 2021
12:22 PM
But on Group Policies you have the possibility to indicate the destination only, not the origin. I think to have difficulties to understand "group policy with stateless rules assigned to a vlan", sorry!
... View more
Oct 7 2021
9:52 AM
We have a VPN tunnel with a non-Meraki peer, with subnet 192.168.aaa.0/24. I have to block a source ip address range to access one destination on my subnet (192.168.bbb.ccc/32). Please note that I defined a VLAN with the subnet 192.168.bbb.0/24. If I try insert the following rule on the firewall: Deny | Any | 192.168.aaa.0/24 | 192.168.bbb.ccc/32 | Any | Some comment I receive the following error: The IP address range 192.168.aaa.0/24 does not apply to any configured local or VPN subnets. So, how to filter them via Firewall policy, not Group policy? Many thanks in advance!
... View more
Oct 1 2021
3:20 AM
On the source I have some VLANs configured, on the destination (the IP I ping) not, single LAN
... View more
Sep 30 2021
9:11 AM
Your routing vlans are configured on the mx? => where can I find this info? Did you disconnect/reconnect your client to the network? => my (the source) yes, the destination not!
... View more
Sep 30 2021
7:25 AM
192.168.3.5 and 255.255.255.0
... View more
Sep 30 2021
4:03 AM
I built a new group policy with these layer 3 rules: Then I applied it to my device opening clients page, then my device page, and selecting it (I found it with its' name + "(from appliance)") in the Group policy dropdown menu and then save. If now I reopen my device page, I can find the new group correctyl applied, clicking on "Show details" I view the rules I posted here. I waited 5 minutes, but I'm anyway still able to ping 192.168.100.83, and also 192.168.1.45 So, what's wrong???
... View more
Sep 20 2021
12:52 AM
Finally it works also with media converters! I elaborate on it, and I found that the MS120 wasn't connected to MS220 directly, but it was connected to the HP instead. So: MX --> MS220 -- fiber --> HP -- media converter --> MS120. and the HP had incorrect VLAN configured ports. For instance, HP uses another terminology: a Trunk port that has to transmit packets of some VLAN must be Trunk tagged, mine was Untagged! Thanks to all for the support!
... View more
Sep 15 2021
11:49 PM
I just ordered a fiber cable, I already have a transceiver to use with it. Tomorrow I can test the direct connection between two switches without media converter. I'll let you know! Thanks
... View more
Sep 15 2021
3:02 PM
Thanks for your reply! I have this on ports connecting each other switch Type Trunk Native VLAN 1 Allowed VLANs all And this is the configuration on the port connecting the device (3 is my new VLAN): Port status Enabled Type Access VLAN 3 Voice VLAN -- Access policy Open
... View more
Sep 15 2021
1:07 PM
Hello to all! I'm new in configuring switches and I would appreciate any help to solve my problem. In our headquarter site we have a Meraki MX, two Meraki switches (an MS220 + an MS120) and an Hp maganed switch. The MX is connected directly to the MS220, MS120 is connected to the MS220 via fiber (SFP on the 220) and a media converter to ethernet on the 120, and the Hp is connected to the MS220 via fiber on the SFP. In the past year we implemented VLANs, but we connected devices on the MS120 and hp only to the default VLAN. There were devices on to the other VLAN only connected via MS220. Now I need another VLAN and to use it for devices either connected on the MS220, on the MS120 and the Hp. I created the VLAN and set its gateway and DHCP. If I assign a port of the MS220 to the new VLAN (Access mode), when I connect a device on that port everything works fine: IP assigned by DHCP on the correct subnet, access to the internet as expected. If I do the same on a port on the MS120, when I connect a device it sets to a bad address 169.xxx.xxx.xxx and it's unable to connect to everything! The gateway port is Trunk (native VLAN the default), and on the port where I connect a device I tried to set it Trunk all VLAN allowed, Access on the new VLAN, Trunk only the new VLAN allowed and the new VLAN the default one, but no way! Same on the Hp, where I configured the new VLAN! Probably on the HP some additional configuration is needed, but on the MS120 I expected no problems! Someone can help me? Many thanks in advance!!
... View more
Jun 28 2021
8:12 AM
4 Kudos
MTU size was definitively the problem! Set to 1300, SQL connection is now working fine!! You all was a lot quicker and gave me a better support than the Meraki official one! Thanks to all!
... View more
Jun 27 2021
12:54 AM
Hello to everybody! Thank you for your replies!! The VPN connection is stable over a 10 minutes of ping -t process. Also the support engineer said that there are no issues on VPN tunneling. My MTU are set to 1500 now, that I'm having the issue. At what value I have to set it?
... View more
Jun 25 2021
8:16 AM
Thanks! Is there any setting that can be done to solve it?
... View more
Jun 25 2021
7:32 AM
1 Kudo
Hello to everybody! I'm subscribed to this community since I'm experiencing a blocking issue with my security appliance, and the support is lacking to help: it's a month since we opened a case, and we are still without a solution. Since the upgrade from version MX 14.53 to 15.42.1 of our MX65W, the VPN connection with a remote Non-Meraki peer was degraded. It's always impossibile to connect to remote SQL sever, to whom it was possible with 14.53. The error returned now is: "The connection with the server was established successfully, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - Wait time expired.) (Microsoft SQL Server, error: 258)" Also navigation on shared folder, physically based on the remote peer (on a server on the remote peer) is very slow, and sometimes Windows is unable to open it. Is there someone can help me? Many thanks in advance!
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 2949 | Sep 20 2021 12:52 AM |
My Top Kudoed Posts
© 2024 Cisco Systems, Inc.
