How to use a module type profile to replace an inventory item???

[marcusyuri]

I am testing 4.3.0 Beta version and using the Module Type Profile feature to model transceivers. A very commom inventory item use case is to document transceivers as inventory itens associated with a device instance interface.

To test I create a simple Module Type Profile:

{
  "properties": {
    "ethernet_pmd": {
      "description": "Ethernet Physical Medium",
      "enum": [
        "1000Base-T",
        "10GBase-LR",
        "100GBase-LR4",
        "10GBase-ER"
      ],
      "title": "Ethernet PMD",
      "type": "string"
    },
    "form_factor": {
      "description": "Transceiver Form Factor",
      "enum": [
        "XFP",
        "SFP",
        "SFP+",
        "QSFP28"
      ],
      "title": "Transceiver Form Factor",
      "type": "string"
    },
    "min_rx": {
      "description": "Minimum Receive Power (dBm)",
      "title": "Minimum Receiver Power",
      "type": "number"
    },
    "max_rx": {
      "description": "Maximum Receive Power (dBm)",
      "title": "Maximum Receiver Power",
      "type": "number"
    }
  },
  "required": [
    "ethernet_pmd",
    "form_factor"
  ]
}

And then create a module type to represent one vendor specific transceiver model. Since the inventory item is now deprecated, I am trying to create an instance of the transceiver using this module type, but now I see a new question: The module can only be assigned to the device if it has an module bay created, but it looks akward, since I must model the device using one module bay for each interface that I want to assign an transceiver instance.

I wandering what is the intend way to use this feature to replace the inventory item???

[jeremystretch]

I must model the device using one module bay for each interface that I want to assign an transceiver instance.

Correct, and this reflects reality: Each SFP must be installed into a specific bay. While we often equate these bay with interfaces, there is no direct association. For instance, a 4x10GE SFP might be configured as four independent physical interfaces.This approach also provides some validation around the installation of such modules, preventing (for example) the installation of 49 SFPs into a 48-port switch.

[bmerry]

Thanks @jeremystretch. I've got a couple of related questions about what you'd consider best practice:

1. How would you model a DAC or AOC cable where there isn't a separate transceiver? Would you just treat the transceiver on each end of the cable as a module, duplicating information like the part number and serial number?
2. We currently have physical ports with no transceivers, but we still need to model the interfaces because they are associated with IP addresses (to allow for future expansion). Should we create the interfaces directly on the device (migrating them to the module once a transceiver is installed)? Or use a "dummy" module type for an unpopulated slot?

[michaelmcdonald]

^ question 1 is something I'm curious about as well. Anybody come up with a thought out and clear way to model DAC cables in this instance?