Community Record
6
Posts
0
Kudos
0
Solutions
Badges
even with the 8 x MIMO ?
... View more
Since there is a boost in the number of MIMO. What is the maximum number of clients one can connect to these access points? Previously for MR52, I find that the sweet spot without compromising is around 65 devices. Any thoughts on this? Can i assume that ideally, it can handle around 120 concurrent devices? Since the MIMO got doubled?
... View more
Jul 26 2018
1:07 AM
So this is what i have gathered by far. VPC peering does not pass external routes. As such peering other VPC to the vMX is not going to help. Amazon is proposing a couple of things - Transit VPC - AWS direct connect - Cisco CSR router. I believe the above-mentioned solution is the only way out unless somehow xMX supports NAT-ing.
... View more
Mar 19 2018
5:47 PM
Hey PhilipDAth, That is exactly what i did. So basically in my setup of MX -> VMX -> VPC. My VMX was able to reach both MX and VPC. However, my MX wasn't able to reach the VPC. So according to Meraki support, they are able to see my ping going out. Just that the VPC attached via peering to the VMX does not have a route back. AWS tech confirmed that the VPC is not supposed to pass routes which it doesn't know about. Thus setting of default route wouldn't work. They are recommending the usage of transit VPC.
... View more
Mar 19 2018
8:10 AM
Hi Guys, I have set up a vMX on a VPC in AWS. The vMX is able to communicate with another VPC through peering. However, if i were to have a site to site VPN configured for the vMX to a physical MX. The clients behind the physical MX were not able to reach the VPC. According to AWS, VPC peering doesn't support L3 routing information which is why i wasn't able to reach the VPC. Any recommendation? This is my setup. MX -> VMX -> VPC Also what is the best way to connect up my VMX to multiple VPC across multiple AWS accounts.
... View more
