Modeling Juniper MPC sub modules

[RichardVReyden]

Modelling sub modules
I am trying to model a child module which has a number (4) of interfaces on it but the sub-module number is not the same for each interface.  For the first 2 ports it is 0 or 2 and the other ports it is 1 or 3 depending if it is inserted in the first or second module slot on the parent module.

I would like to have something like:

manufacturer: Juniper
model: MIC-3D-4XGE-XFP
interfaces:

name: xe-{module}/{module}/0
name: xe-{module}/{module}/1
name: xe-{module}/{module}+1/0
name: xe-{module}/{module}+1/1
This plugs into a module with 2 module slots with positions of 0 and 2

This would generate interfaces if both parent slots are filled:
xe-0/0/0
xe-0/0/1
xe-0/1/0
xe-0/1/1
xe-0/2/0
xe-0/2/1
xe-0/3/0
xe-0/3/1

Any thoughts on how to achieve this, I could create an action to update them when created but was hoping to have a native way of doing it.
Thanks
Richard

[MattDRogers]

You can either manually name the interfaces when you model MICs (sub-modules) that could possibly have PIC positions 2 and 3, or model each MIC with two module bays and then model each PIC as a module with two interfaces:

Device: Juniper MX240/480/960
 - FPC 0: MPC3E-3D-NG 
  - MIC 0: MIC-3D-4XGE-XFP
    - PIC 0: 2x 10GE  XFP
       - xe-0/0/0
       - xe-0/0/1
    - PIC 1: 2x 10GE  XFP
       - xe-0/1/0
       - xe-0/1/1
  - MIC 1: MIC-3D-4XGE-XFP
     - PIC 2: 2x 10GE  XFP
        - xe-0/2/0
        - xe-0/2/1
     - PIC 3: 2x 10GE  XFP
        - xe-0/3/0
        - xe-0/3/1

With these types, I think I gave up and just manually named the interfaces just to avoid breaking a MIC into PICs. This doesn't really scale if you have like hundreds or thousands to model. But it'll get the job done.

I modeled the PIC method on the netbox demo site here: https://demo.netbox.dev/dcim/devices/112/interfaces/