Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About melvyn-lee
melvyn-lee
Here to help
Member since Nov 18, 2021
Jun 8 2022
Community Record
9
Posts
1
Kudos
1
Solution
Badges
May 27 2022
2:47 AM
Hi Brash. You are absolutely correct, deleting the two firewall rules allowed me to delete the VLAN. The error message was no help at all. Many thanks for your help, greatly appreciated.
... View more
May 27 2022
2:44 AM
Hi ww. Deleting two firewall rules pertaining to the VLAN subnet then allowed me to delete the VLAN. Many thanks for your help, it's greatly appreciated.
... View more
May 27 2022
2:41 AM
Hi PhilipDAth. Many thanks for your advice. I did have a 1:1 NAT that referred to the VLAN subnet but I had already deleted it. I discovered that a Firewall Rule also had reference to that subnet. Once I deleted the rule I was able to delete the VLAN. Thanks Again, your advice is greatly appreciated
... View more
May 26 2022
7:09 AM
I am having difficulty deleting an existing VLAN within the Addressing & VLAN page on the dashboard of my MX64 Router / Firewall. When I try to delete the VLAN the following error message is generated "There were errors in saving this configuration. The IP address range 192.168.201.0/24 does not apply to any configured local or VPN subnets", despite the fact the subnet is listed. I note that the appearance of the subnet table on the Addressing & VLAN page has changed since Firmware Upgrade MX17.7, which took place a week ago. I suspect the upgrade has caused the problem but the only way I could prove it would be to restore the previous version although I am reluctant to do that. Has anyone experienced a similar VLAN problem ? I have raised a Support Case and am awaiting a response.
... View more
Nov 25 2021
7:51 AM
That's OK, as long as both are selected it will facilitate the format / standards selected at the Meraki end. So if IKEv1 and IKEv2 are ticked at the AWS end and IKEv2 is selected at the Meraki end then your peer connection will run on IKEv2. Note that any changes made at the AWS end take a good 5 - 10 minutes to fully register.
... View more
Nov 25 2021
7:24 AM
Yes the Public IP address and the Remote ID cell entry are the same and the IKE version was changed from IKEv1 to IKEv2. MX14.53 worked on IKEv1 whereas MX15.range of firmware runs on IKEv2. Make sure IKEv2 is selected at the VPN tunnel options on the AWS console as well
... View more
Nov 25 2021
6:25 AM
1 Kudo
I had similar problems despite entering the external IP address for the AWS virtual gateway in the remote ID cell. Once I changed the IKE Version from IKEv1 to IKEv2 all our non meraki peers into AWS became stable. n.b Ensure the VPN tunnel connection options in the AWS Console has the IKEv2 selection button ticked. Allow at least 10 minutes for settings to register. I hope this helps
... View more
Nov 25 2021
6:20 AM
I had similar problems despite entering the externalIP address for the AWS virtual gateway in the remote ID cell. Once I changed the IKE Version from IKEv1 to IKEv2 all our non meraki peers into AWS became stable. n.b Ensure theVPN tunnel connection options has the IKEv2 selection button ticked. Allow at least 10 minutes for settings to register.
... View more
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 3759 | Nov 25 2021 6:25 AM |
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 1 | 3759 |
© 2024 Cisco Systems, Inc.
