The suggested proper way of modeling real-life devices is to completely remove the relation between netbox and device, and replace it with a separate table to represent the physical components that an IP address represents. This may in fact be just a shadow image of the ENTITY-MIB::entPhysicalTable (for devices that support this).
A simple switch will have a single chassis entity that would point to the device record (which the netbox record would previously point to). A virtual switch may have multiple chassis entities in this table.
This has **huge** implications for how NAV works in many ways, since the Netbox -> Device relation is quite ingrained in code and other data models.
The suggested proper way of modeling real-life devices is to completely remove the relation between netbox and device, and replace it with a separate table to represent the physical components that an IP address represents. This may in fact be just a shadow image of the ENTITY- MIB::entPhysica lTable (for devices that support this).
A simple switch will have a single chassis entity that would point to the device record (which the netbox record would previously point to). A virtual switch may have multiple chassis entities in this table.
This has **huge** implications for how NAV works in many ways, since the Netbox -> Device relation is quite ingrained in code and other data models.