These are chat archives for allegro/ralph

Apr 2017
Ramon Buckland
Apr 14 2017 11:33
Creating a linlk between an ethernet card, (Cu, SFP etc) and a switch port, is largely about having the "known" number of switch ports declared on that asset.
Just off the top of my head. You would want to use the interface numbering scheme of that switch (this assists with driving automation). i.e.
HP Switch IRF - TenGigabitEthernet2/0/4 Cisco .. ethernet1/10 etc.
and linking these declared "components, or items" to the Devices' ethernet (or other) component.
In addition, we would also want to create "logical" ethernet devices for a computer - in the case of an LACP bond for example.. where
2 x NICs on the server - are linked to their respective interfaces on the switch(es), and then create the
bond0 on the server (with parents of the 2x physical) and on the switch similarly, port-channel9 (cisco) .. linked to the parented switch ports and then link these two logicals .. server1/bond0 and switch1/port-channel9
Apr 14 2017 14:53
the first part functionality - having declared number of ports - absolutely makes sense. keep in mind that normal servers would also need it as well, so really just declaring the number of ports for a "datacenter" asset would do. Sort of like the predetermined "U" height for a model of a datacenter asset. something like that would probably work pretty well.
as far as the second part, that would be nice, but not really necessary in my opinion. others might find that more useful than myself.
Apr 14 2017 14:58
I think the hardest part about this is making it appear "on both sides". That's what i struggled with the most, and gave up. If you make a connection between Server A Port1 and Server B Port2 (on Server A), that should show up on Server B Port2 as well
@rbuckland let me know if/how i could help. I'll try when i have some spare time
Ramon Buckland
Apr 14 2017 15:00
Thanks @spencewb16_twitter. I will startup coding some things once I import all the assets I am working on.