As part of an IT Asset Management task, frequently network interfaces of deployed computers are catalogued.
UCO has representations for wireless connectivity addresses, using these classes:
observable:MACAddress
observable:BluetoothAddress
observable:WifiAddress
observable:MACAddressFacet
observable:BluetoothAddressFacet
observable:WifiAddressFacet
However, those two non-leaf classes (MACAddress and MACAddressFacet) have no corresponding child class for an address that would be associated with an ethernet jack. This is a frequent need in device cataloguing, especially for making records of 1G vs. 10G jacks on servers, and making maps of which network interface presented in a server's OS corresponds with which jack.
Is there a way to represent ethernet jacks that I'm missing? If we need to define classes for ethernet, do we also need classes for other "hard-wire" networking forms, like the various SFP kinds?
As part of an IT Asset Management task, frequently network interfaces of deployed computers are catalogued.
UCO has representations for wireless connectivity addresses, using these classes:
observable:MACAddress
observable:BluetoothAddress
observable:WifiAddress
observable:MACAddressFacet
observable:BluetoothAddressFacet
observable:WifiAddressFacet
However, those two non-leaf classes (
MACAddress
andMACAddressFacet
) have no corresponding child class for an address that would be associated with an ethernet jack. This is a frequent need in device cataloguing, especially for making records of 1G vs. 10G jacks on servers, and making maps of which network interface presented in a server's OS corresponds with which jack.Is there a way to represent ethernet jacks that I'm missing? If we need to define classes for ethernet, do we also need classes for other "hard-wire" networking forms, like the various SFP kinds?