Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Symptom: "When I select the Vnet and then the subnet it uses the .4 IP , which is already allocated to another device. The .4 address is the next available IP within the CIDR, but it is not available for use. Is it possible to change that IP to somet...
Cisco CSR1000V, where it's used and how does it performThe Cisco CSR1000V can deliver up to 20Gbps of throughput on a single x86 commercially available server, delivers up to 5Gbps of encrypted traffic inside public cloud providers, and with its rich...
Microsoft Azure Government Cloud is an isolated and dedicated cloud platform, which enables government agencies and government approved contractors to host sensitive data. Connectivity from on-premises locations to Azure Government Cloud must be se...
Hello,
To mitigate this issue you can allow incoming Phase 1 traffic into CSR from AWS VPN device and that will resolve the issue as now AWS VPN end point renegotiate phase 1 rekey few minutes earlier than 8-hour expiry instead of Cisco router.
We a...
Hello,
The BYOL listing is an unlicensed CSR that is throttled to 100kbps by default, you must obtain a 60-day demo license from www.cisco.com/go/license and install it on the CSR
After the 60-days the router will default back to 100kbps, unless lic...
Hello,
The issue you are seeing is due to the fact that the second interface comes up in DHCP mode and obtains a "default-router" IP when negotiating its IP address.
You need to make sure you "not" use DHCP for the second interface, you can also con...
Hello Tobias,
The issue you are describing is going to be outside our CSR platform expertise. It sounds like CSR is running fine and HA is also running fine, and now you are trying find a solution to a networking/VPN issue you are facing.
Our team wi...
Hello,
From the google server perspective (8.8.8.8), it would not have a return path to networks 172.16.0.50 and 172.27.15.5. The 172.27.1.5 address is NAT'ed by the AWS IGW EIP address and that is how a successful ping is possible. In this case, if ...
