Provisioning Flashcards
How does CVP push a configuration to switch?
CVP creates a configure session and runs the config session. We use “configure replace xxx” method to install the config
What is the most important to remember in the config session that CVP runs during pushing configlets?
it does a “rollback clean-config” and then pushes
Can we check the session config diffs, to see what lines will be added and removed if we execute/commit the current session config?
use the command “show session-config diff” from within a config session.
In simple provisioning process of a EOS device using CVP ZTP, when do we start streaming?
When the device in ZTP mode downloads the bootstrap script and installs the config. Ealrier we had to first provision and then start streaming, but now we start streaming during the ZTP stage itself.
What is important while creating a Image bundle?
- Image bundle must have a EOS image (.swi) file
- Make sure if you are including a EOS extension, that extension is compatible with the EOS image version in the image bundle
Different types of configlets?
- Static
- Generated
- Reconcile
When CVP says a particular configlet is not correct, what to do?
We can check using the configuration session in the device, create a config session and put the configuration in the configlet, it will tell you which line is the error
what does the CVP workflow for ZTP process look like?
During the CVP ZTP process, from where does the EOS agent download the option67 boot script?
http://cvp-ip/ztp/config
/ztp/config in CVP node, is a python script and this contains:
1. eAPI config
2. Configures TerminAttr
3. Configures the hostname (sw-x.x.x.x)
4. DNS and Default route
The EOS agent gets this python script and runs it. After running this script, EOS agent will try and request the startup config and at this point the device will be undefined container.
During the CVP ZTP process, how does the ZTP stop?
In ZTP mode, we can’t save to startup-config, so what CVP does is, once we move the device to a named container and push the configlets, it will save the configuration as cvp-config in the EOS device. Now the ZTP agent will see that there is a config called cvp-config and it will rename this to startup-config and now it will know that a valid config has been saved, and so it will reboot and come out ZTP mode.