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 access switch:
- Save any special interface configs:
curl -ks -H "Authorization: Bearer $JWT_AUTH_TOKEN" ${CNAASURL}/api/v1.0/device/currentswitch/interfaces > migrate-received.json
- Remove device from NMS (use factory default if the switch is still online to clear the config)
- ZTP new switch (with same name)
- Re-apply any interface configs, download migrate-interfaces.py ( compatible with nms v1.x to convert output json to input json )
python3 migrate-interfaces.py < migrate-received.json > migrate-send.json
curl ks -H "Authorization: Bearer $JWT_AUTH_TOKEN" ${CNAASURL}/api/v1.0/device/newswitch/interfaces -X PUT -d migrate-send.json -H "Content-Type: application/json"
- Sync config to switch
- Update serial etc in NI?
- Update monitoring etc if management IP changed
Replace dist switch (in core/dist configuration):
- Update mgmtdomain so it does not reference the switch you want to replace, instead set both device_a_id and device_b_id to the id of the device in the pair that you are not going to replace: curl ks -H "Authorization: Bearer $JWT_AUTH_TOKEN" ${CNAASURL}/api/v1.0/mgmtdomain/1 -X PUT -d '{"device_b_id": 8}'
- Delete the switch you want to replace with the API, factory_reset: false since it's not supported on DIST devices.
- Re-sync all core switches so they remove linknet config and add ZTP vlans
- Physically replace the switch and wait for the new switch to show up in DISCOVERED state
- Init the switch with the exact same hostname (so that git settings will be applied)
- Update the mgmtdomain so it references both switches in the pair again (revert of step 1)
- Update serial etc in NI?
- Update monitoring etc if management IP changed