nautobot-app-ssot
nautobot-app-ssot copied to clipboard
Hardware Serial Number
Environment
- nautobot version: 1.5.x
- nautobot-ssot-ipfabric version: 2.0.0
- ipfabric version: 6.x
Summary
IP Fabric records two serial numbers:
- "Unique Serial Number"
- Column
sn
- Column
- "Serial Number"
- Column
snHw
(Hardware Serial Number)
- Column
Nautobot has a single serial number for a device under "Hardware" with a description of "Chassis serial number".
Currently, the SSOT syncs the IPF sn
and not the snHw
which is not correct from the description above.
Proposed Functionality
- Add new custom field
IPFabric Serial Number
orIPFabric Unique Serial Number
? - Sync jobs still use the
sn
field as this is a unique value and ensures all data is sync'ed correctly. - Update sync jobs to use
snHw
for the Device Serial Number - Add
sn
data to custom field.
Open Questions
- Can Nautobot have duplicate Serial Numbers?
- YES
- Can this be configurable?
-
CONFIG.get("default_device_serial_number", "sn" or "snHw")
-
- How do we migrate users?
- SN might be an important field for their current automation.
Use Case
Device: L71FW9
Hostname,Unique serial number,Serial Number
hostname,sn,snHw
L71FW9/root,FOSVM1HHJXBALLD7/root,FOSVM1HHJXBALLD7
L71FW9/ipf,FOSVM1HHJXBALLD7/ipf,FOSVM1HHJXBALLD7
Is this a network device serial number?
In IP Fabric sn
column or Unique Serial Number
is an IP Fabric unique SN. In many cases the Hardware Serial Number (snHw
) matches the sn
however some devices that have virtualized devices will be changed to snHw/<vsys or context name>
.
Example:
L71-FW12/root
role: Network Device
model: Default-fortinet
status: Active
vendor: Fortinet
location_name: L71
serial_number: FGVMEV7OFHYVLX5D_root
Note: This is an old snapshot; newer snapshots use FGVMEV7OFHYVLX5D/root instead of FGVMEV7OFHYVLX5D_root
This is an issue also with Cisco SD-WAN devices the sn and snHw are completely different.