-
Hello, I made a quick search but I didn't find topic on this, maybe I didn't search enough ! Sorry in the case this has already be discussed. I'm using Netbox (it's really great btw ! ahaha) with Nokia SR devices. Nokia has another philosophy fort port/interface than Cisco and others. I'll explain: Port (L2) are physical port which are totally uncorrelated from IP interface (L3). L3 Interface are object with names. Example of port config:
Example of interface config:
That's exactly the same for LAG
And then the interface config:
In Netbox I can't attach a port (or a physical interface in the Netbox vocabulary) to a virtual Interface (L3 object we create to reflect the Nokia way of doing) since both object are at the same "level". In the same spirit, if I create a lag, I can add interfaces (physical or virtual), but If I name it "lag-1" it doesn't represent the L3 interface, If I call it "Test_Interface" it doesn't represent the real lag ... For the moment, we use physical interface for L2 Ports and virtual interface for L3 interface. But there is no link between them. Some of you are using Netbox with success to reflect Nokia philosophy ? This is driving me crazy lately. I hope I was clear enough ! Have a nice day everyone ! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
In Netbox, a named interface like "Test_Interface" would be created as an interface of type "virtual". Then you can set its parent interface to be the physical port, and you've got the linkage you wanted. The parent interface feature was added in v2.11.0: see section headed "Parent interface assignments" |
Beta Was this translation helpful? Give feedback.
In Netbox, a named interface like "Test_Interface" would be created as an interface of type "virtual". Then you can set its parent interface to be the physical port, and you've got the linkage you wanted.
The parent interface feature was added in v2.11.0: see section headed "Parent interface assignments"