MerakiMX64 on prem, vMX100 in Azure and two server farms, one in classic and one in modern architect
The company that I am working for is implementing MerakiMX on-prem and in Azure.
On prem I have:
- one MerakiMX64 with subnet 192.168.20.0/24 and a Client1 with ip: 192.168.20.2 that is behind MerakiMX64
On Azure I have:
- one vMX100 on a vnet called meraki-lan. The vMX100 has IP: 18.104.22.168, subnet 22.214.171.124/24
- one server farm that is deployed in classic architecture (older one). The servers are connected to a vnet1 that is in classic deployment. Subnet for the servers 126.96.36.199/25. There is one more subnet called GatewaySubnetV1 188.8.131.52/29, this one is used to make a vpn-site-to-site connection via virtual gateway to GatewaySubnetV2.
- one server farm that is deployed in modern architecture. The servers are connected to a vnet2 that is in modern deployment . Subnet for the servers 184.108.40.206/25. There is one more subnet called GatewaySubnetV2 220.127.116.11/29, this subnet is used to make a vpn site-to-site connection with the GatewaySubnetV1 18.104.22.168/29
I have done peering between meraki-lan and vnet1 and meraki-lan and vnet2. There is a routing table that I have put the local subnet 192.168.20.0/24 and associated that subnet to vnet2.
Now everything works as it should between 192.168.20.0/24 and server farm that is deployed in modern architecture, vnet2. From Client1 I am accessing all servers on vnet2 (modern architecture)
However I am not able to communicate between the MerakiMX64 or Client1 to servers in vnet2(classic architecture). I am not able to find how to make an association from meraki-lan to vnet1 (classic architecture).