Setup a new network device
This page is currently a draft.
Material may not yet be complete, information may presently be omitted, and certain parts of the content may be subject to radical, rapid alteration. More information pertaining to this may be available on the talk page.
Material may not yet be complete, information may presently be omitted, and certain parts of the content may be subject to radical, rapid alteration. More information pertaining to this may be available on the talk page.
Checklist to not get lost when setting up a new network device
Initial setup
NOTE: We can now use ZTP to handle many of these steps for Juniper QFX-series switches. See ZTP Network Device Provision for more info.
- Add to Netbox (dc-ops)
- Include serial number and asset tag
- Set Netbox status to 'planned'
- Connect power/console/mgmt
- Update console server's port (& test it)
- Assign mgmt IP and loopback IP(s) in Netbox
- Run DNS cookbook to add reverse DNS entries
- Add base config
- Management IP
- Static route to management router (in mgmt vrf where appropriate)
- Auth setup (user(s), ssh enabled)
- Add to Homer
- Push initial configuration
- Upgrade to latest recommended OS version
- Save rescue configuration
- request system configuration rescue save
- Set Netbox status to 'active'
- Run the sre.puppet.sync-netbox-hiera cookbook to import location to hiera
Monitoring
- Add to LibreNMS - LibreNMS#Add a device to LibreNMS
- You can set the "Disable alerting" and "Ignore alert tag" in the device's setting if it's not ready for prime time.
- Add to Rancid (Puppet: modules/rancid/files/core/router.db)
- Add to Icinga and Prometheus
- Puppet: hieradata/common.yaml - infra_devices
- Puppet: hieradata/common/monitoring.yaml
- Puppet: modules/netops/manifests/monitoring.pp