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 Zinkt
Zinkt
Conversationalist
Member since Oct 27, 2022
Oct 31 2022
Community Record
7
Posts
0
Kudos
0
Solutions
Badges
Oct 28 2022
8:38 AM
Thanks alot for your time and suggestions. I will study vpn translation.
... View more
Oct 27 2022
7:58 PM
Hi @alemabrahao this is new topology (only Site:A and Site:B) Site:A Meraki HUB is sending logs to Syslogs server via 192.168.1.1. Site:B Meraki HUB is not sending logs to syslogs server via 192.168.100.1. Possible Cause Site:A Meraki HUB is advertising Site:A local work 192.168.0.0/16. Site:B Meraki HUB is going traffic via Site:A Meraki HUB (Hub to Hub, not via MPLS) Site:B Meraki HUB traffic logs sending to syslog server with Site:A MerakiHUB source IP. Temporary Solution After Site:A Meraki Hub advertise only 192.168.0.0/24 (exclude 10.15.200.0/24 network), Site:B Meraki HUB can send logs to syslog server. But Site:A Meraki Hub need to advertise all 192.168.0.0/16 network for its branch office.
... View more
Oct 27 2022
10:40 AM
Thank you. SiteA-BranchA topology is same as this one. Anyway, will chk routing again. Thanks @alemabrahao
... View more
Oct 27 2022
10:29 AM
Thank you for your info @alemabrahao Sorry for my diagram to make you confused. Will upload revised one. RT are WAN routers that connect to each sites via MPLS. RT to Office icon is just internal network. Regarding routing,if I advertise only 192.168.0.0/24, BranchA site will not be able to reach to Site C w/o default route.
... View more
Oct 27 2022
10:12 AM
SiteA LAN Network is 192.168.0.0/24. SiteC netwok is Data center 192.168.0.0/16. If SiteA hub advertise only 192.168.0.0/24, SiteB MX can send syslog to syslog server well via its WAN interface SiteB to SiteA to SiteC MPLS( not via hub to hub peer auto vpn) But i think I better to advertise 192.168.0.0/16 on SiteA hub.
... View more
Oct 27 2022
9:41 AM
Hi @alemabrahao Thank your for your reply. When I perform packet captures via Internet interface, no traffic found to syslog server. But with S2S vpn interface, traffic found to syslog server and SrcIP is 6.xxx.xxx.xxx. Traceroute to syslog server from SiteB hub is working well via 192.168.100.2(RT).
... View more
Oct 27 2022
9:00 AM
Hi I'm new to Cisco Meraki. I have two HUBs and two spokes using S2S VPN in my same organization name as below. HUB:A - Spoke:BranchA (Site-A) - using passthrough mode (HUB:A) - direct P2P connect with router (via Meraki WAN1 :IP 192.168.10.1/30) - using routed mode (Spoke:A) - advertising 192.168.0.0/16 in vpn setting as local network HUB:B - Spoke:BranchB (Site-B) - using passthrough mode (HUB:B) - direct P2P connect with router (via Meraki WAN1 :IP 192.168.100.1/30) - using routed mode (Spoke:B) - advertising only its upstream network (192.168.100.0/30) in vpn setting as local network Our syslog server IP is 192.168.200.254 located at Site-C. HUB:A is sending logs well to syslog server via its WAN IP: 192.168.10.1 , but HUB:B is not sending logs to syslog server via its WAN IP: 192.168.100.1. I found it's sending logs to syslogs sever via Meraki dashboard IP: 6.xxx.xxx.xxx. and all the syslog traffic of HUB:B is going to HUB:A which is adverstising 192.168.0.0/16 network. please help and let me know if my info is not complete. Note: - Site-A, Site-B and Site-C are connected via MPLS. - IP are example. - Sorry for my draft diagram
... View more
© 2024 Cisco Systems, Inc.
