Hide
Services/Collaborations
Campus Network as a Service
Change process:
- Open ticket/set ticket to "in progress"
- If template change: Update template in lab first, test and then go to prod
- If settings change: Update settings in prod instance
- Dry run, if change might have a big impact implement on just a single device first or ask a colleague to verify diff as well
- Notify NOC if something might break
- Live run
- Check monitoring
- Update/close ticket
Firmware upgrade process:
- Open ticket/set ticket to "in progress"
- Verify in lab and document expected downtimes
- Upgrade isolated building/location first, wait 1 day
- Upgrade first half/partition of network
- Upgrade second half/partition of network
- Check monitoring
- Update/close ticket
Replace switch:
- Save any special interface configs: curl -ks -H "Authorization: Bearer $JWT_AUTH_TOKEN" ${CNAASURL}/api/v1.0/device/eosaccess/interfaces
- Remove device from database
- ZTP new switch with same name
- Re-apply any interface configs ( migrate-interfaces.py compatible with nms v1.x to convert output json to input json , then curl ks -H "Authorization: Bearer $JWT_AUTH_TOKEN" ${CNAASURL}/api/v1.0/device/eosaccess/interfaces -X PUT -d outputfile.json -H "Content-Type: application/json" )
- Update serial etc in NI?
- Update monitoring etc if management IP changed