Hello,
We are currently migrating a customer to the CSR 1000v in AWS but are having issues automating the deployment. I found some conflicting documentation that first stated that the RestAPI wasn't available on the CSR1000v AMI but found that it in fact was when checking the AMI once it was booted and running. I wasn't however able to utilize the restapi without first logging in and creating a user since the CSR is booted and accessed initially using a key and the ec2-user. I was hoping for help answering the following questions:
- Can a user be specified prior to booting the CSR 1000v for the first time so that the RestAPI can be accessed on first boot without requiring ssh login to manually create that user and if so how?
- I saw that there was documentation with an example on how to achieve HA using EEM to perform a route change. One of the documents indicated it was using a helper linux vm to execute these route changes, the other document made it seem as though the EEM applet was actually performing the route table change without accessing a helper vm. Are there any aws api tools accessible on the CSR in TCL form or any other that would allow the CSR to send SNS messages to aws or other API calls natively without the use of a linux helper vm?
- The CSR 1000v document for openstack shows the ability to provide some running configuration modifications prior to first boot using the
ovf-env.xml and or iosxe_config.txt. What if any properties can be specified to be applied to the running-config on boot of the CSR instance and how does one specify these properties?
Thanks for any help in these matters. We have found the CSR to satisfy our requirements, just need to fit the CSR into our deployment stratagies.
