Campus Network Engineering Meeting Notes - Get consistent location information for network equipment
Full history of meeting notes on the agenda item "Get consistent location information for network equipment".
- 27JAN20: We discussed having consistent row, column and RU locations for equipment in datacenters and supernodes. CSSC has good row, column and RU information. We do not have this for Animal or 432NM. Will Crickman has created several quick searches in WiscIT on our dashboard. MFCOB and OneNeck probably have good location information. We have API access to query WiscIT for fields that are missing for location information of the network devices. We discussed the need to have a process for adds/changes/deletes. The goals for this is to figure out where devices are so we can make connections to them. We discussed using NetBox since it can model racks and WiscIT does not model racks. Can we create a mechanism/tool to get the information into WiscIT or NetBox. We discussed using the snmp location in the configuration of the network devices. We can then use the snmp location and put it into WiscIT or NetBox. We discussed adding fields to WiscIT for location of equipment but not everyone creates tickets for equipment install/removal/change. David is going to work on figuring out the pattern for the snmp location configuration. Keep agenda.
- 03FEB20: Ran out of time.
- 10FEB20: No change.
- 17FEB20: Ran out of time.
- 24FEB20: Ran out of time.
- 02MAR20: Ran out of time.
- 09MAR20: David talked to Mark Tinberg and Tom Christie about pushing more information into the Cherwell cmdb. David will go back to Mark Tinberg to ask about doing this for Animal Science and 432NM. NetBox is also being looked at for the future equipment tracking. If NetBox is going to be used we should not be spending time on the Cherwell cmdb. This will be discussed tomorrow at the tools meeting.
- 13APR20: Ran out of time.
- 20APR20: On hold until we decide if NetBox or some tool is going to be used to track network equipment location.
- 21SEP20: Consensus is to use OpenDCIM to track network equipment locations.
- 28SEP20: Waiting for OpenDCIM to be installed in test and production.
- 05OCT20: Waiting for OpenDCIM to be installed in test and production.
- 12OCT20: OpenDCIM has been installed in test.
- 19OCT20: Ran out of time.