- Upgrades the device to desired ios version
- Uses chassi serial number to download correct config file.
- Some cisco devices use "golden.cfg" after the reset button I pressed while booting. This file simply sets basic config for the device so I can me remotely accessed.
- DHCP server gives the device tftp link to "bootstrap.cfg"
- the config is applied and the even managers starts
- It downloads "bootstrap.tcl" and "golden.cfg"
- the TCL script is executed
- Find chassi serial number
- upgrades ios if needed
- downloads the desired config as "serial_number".cfg
- device reboots with new config file.
I use this in live production for CPEs: ASR920, ISR1100 and 8xx series. The "bootstrap.cfg" has two EEMs for downloading the TCL script. This is because the ASR920 needs some additional input when downloading TCl files. This is just an ugly fix to get around this. All other models will just fail on this and go to next step in "bootstrap_init" EEM.
- https://github.com/lodpp/cisco-catalyst-bootstrap
- https://supportforums.cisco.com/blog/12218591/automating-cisco-live-2014-san-francisco
Feel free to contact me if you have any questions. [email protected]