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 JGillett
JGillett
New here
Member since Mar 13, 2018
Mar 13 2018
Community Record
6
Posts
0
Kudos
0
Solutions
Badges
Mar 13 2018
3:08 PM
unfortunately, I have about 10 locations that will be in a full mesh. Do you know if you can configure the vMX100 in an HA configuration across different availability zone similar to the Cisco CSR1000v? That might be an option.
... View more
Mar 13 2018
3:02 PM
If i left both active, wouldn't I potentially run into an asymmetric routing issue since both will be advertising the subnets in the VPC, but the return route would only be through the active vMX?
... View more
Mar 13 2018
2:55 PM
What if I provision two vMX100. The primary in AZ1 and the secondary in AZ2. Once provisions, the secondary will be shutdown. I will then using amazon to monitor the vMX100 in AZ1. If that fails, I will update the routing table to reflect the interface of the secondary vMX100 in AZ2, Power on the vMX100 in AZ2 and the move the elastic IP to that interface.
... View more
Mar 13 2018
2:36 PM
I have thought about that as well. Unfortunately, we are deploying systems across all five AZ's in the N.Virginia region. That could get quite a bit costly.
... View more
Mar 13 2018
2:23 PM
We are in the process of deploying a vMX100 to one of our VPC's. This VPC is located in the N. Virginia region and we will be deploying systems across multiple availability zones. The primary concern I have is with regard to the deployment of the vMX100 in only one availability zone. If that availability zone goes offline, then I will lose connectivity to the remaining availability zone. My question is whether or not there is a way to deploy the vMX100 in an HA configuration across two AZ's in order to provide redundancy. Some alternatives, I have considered is deploying the vMX100 in my primary AZ, creating an ami of the system. I would setup monitoring of the EC2 instance in the primary AZ. If the instances fails, I would launch the AMI in another AZ, move the elastic IP to that instance and update the route tables. My plan would to have all this triggered by the monitoring. A second thought was to use an elastic load balancer as a type of VRRP between the two AZs, both from and internal and external perspective. I appreciate any thoughts on this.
... View more
Mar 13 2018
2:15 PM
© 2024 Cisco Systems, Inc.
