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 AZEIDLER
AZEIDLER
Comes here often
Member since Aug 11, 2018
Sep 17 2018
Community Record
7
Posts
0
Kudos
0
Solutions
Badges
Aug 25 2018
2:22 PM
Hi, We have a rasonable number of MX64 deployed and operational (around 50) At this point we need to deploy a long list of FW rules (around 100 rules) to all devices. Manualy configuring 100 FW rules on 50 devices does not seems to be practical. I have tested the template, but noticed that the VLAN´s and Static routes (which are unique for each site) are overwriten by the template. I need a method to configure the same FW rules on all devices, without making other changes. Any suggestion? Any method to avoid the template to change other parameters ? Thanks
... View more
Aug 12 2018
12:57 PM
After this issue happened on several devices we have changed the WAN to static (on same IP) and the problem has not happened again.
... View more
Aug 11 2018
6:55 PM
We tested this beta NO-NAT functionality . There is an issue, confirmed by Meraki TAC: ICMP does not work , which mens the servers on MPLS are not able to ping the host on LAN . This was considered unnaceptable and the "TRANSIT VLAN to MPLS " solution was used. The only remark with this solution is that the route 0.0.0.0 0.0.0.0 , by default, points to the Internet Interface, We had to create routes to private IP ranges (10.0.0.0 /8, for example) to make OUTBOUND traffic flow via the Transit VLAN . The LAN subnets also had to be redirected to transit VLAN on MPLS router for INBOUND traffic
... View more
Aug 11 2018
6:44 PM
Hi, No chance of another device pluggd. We have built a specific VLAN for WAN connection with only the Router and the MX64 connected to it; Not tested DNS during failure, but since it´s a very large network, DNS servers should be reliabel
... View more
Aug 11 2018
6:39 PM
Hi. Below the outputs: ROUTER r>sh ip dhcp conf IP address Detection method Detection time VRF 10.124.113.26 Ping Aug 09 2018 11:21 AM ROUTER>sh ip dhcp bind Bindings from all pools not associated with VRF: IP address Client-ID/ Lease expiration Type Hardware address/ User name
... View more
Aug 11 2018
2:01 PM
Hi , We are facing the following situation on a MX-64 deployment The WAN and Internet connectivity is provided by a MPLS network. The MPLS router is C819G -4G-G-K9 that was configured to provide the WAN IP address to MX64 (configured as DHCP on Internet interface) : ! ip dhcp excluded-address 10.124.113.25 ip dhcp pool MERAKI network 10.124.113.24 255.255.255.252 default-router 10.124.113.25 dns-server 10.105.160.101 10.105.160.102 ! In this case, the WAN IP provided to Meraki is 10.124.113.26 (the only IP available on this DHCP range) In a few sites, the Meraki changes the status to "BAD INTERNET" and the following output is obtained on router, indicating that the IP provided is in the conflict list ROUTER >sh ip dhcp conf IP address Detection method Detection time VRF 10.124.113.26 Ping Aug 09 2018 11:21 AM The MX64 WAN IP address respond to ping for a period of time, and then stop responding. At this time, the Dasboard reports "UNREACHABLE" The situation is resolved whent the DHCP process is restarted on routrer. Any Idea what can cause the DHCP conflict ?
... View more
Aug 11 2018
1:27 PM
HELLO CAUEFW, FYI ... Cisco System Engineer supporting us on this case has recomended a wireshark sniffer during the MX-64 first register. We have also agreed to collect the logs on the Internet proxy/ FW to identify if we have blocks. RGDs
... View more
© 2024 Cisco Systems, Inc.
