View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001341||RackTables||IPv4/IPv6/SLB||public||2014-10-09 04:18||2017-04-08 21:45|
|Priority||normal||Severity||feature||Reproducibility||unable to reproduce|
|Platform||OS||ubuntu||OS Version||14.04 lts|
|Target Version||Fixed in Version|
|Summary||0001341: add attributes to ip interfaces or ports|
|Description||The chance of adding extra attributes to objects, today, is really handy and helpful.|
Now, how difficult is it to add extra attributes to interfaces or ports?
In our company (service provider) we mostly deal with routers (tons of them, +1700) rather than servers and those have multiple interfaces with different kind of configurations:
- different MTU values
- different protocols and/or parametrization:
- ospf and different areas, timers, etc
- vrrp: timers, priorities
- bfd, etc
- QoS policies might also be different depending on the interface
- ACLs ... and so on.
So, the ability of adding personalized attributes to both ports and/or interfaces would be just great!
What do you think?
Hi! Just for the record, I'm not a programmer but I'm willing to help if needed. If only you could somehow guide me with this, I'll be glad to do it ...
|I would value the ability to add 802.1Q tags to a port on a switch object which would permit me to keep track of what ports are access ports to a particular VLAN or what VLANs are trunked across a port.|
I would also like the functionality described by hackmaster.
I find the 802.1q management configured in racktables to be too much for what I want. I'd just like to manually record which ports are tagged/untagged and on what vlans.
I would consider -if this feature goes on- the ability to also map interfaces to ports. For example, when creating an interface (L3) one would have the chance of selecting which port (L2) is such an interface using. This will be particularly useful if a port has -for example- encapsulation attribute with dot1q. If so, multiple interfaces (L3) could use the same port (L2) where the VLAN ID will be the segregation feature.
So, in the end, a possible attribute for an interface would be a feasible L2 port.
This has also been stated in this issue: https://bugs.racktables.org/view.php?id=1715
|2014-10-09 04:18||laimaretto||New Issue|
|2014-10-09 04:18||laimaretto||Status||new => assigned|
|2014-10-09 04:18||laimaretto||Assigned To||=> andriyanov|
|2014-10-09 04:20||laimaretto||Tag Attached: interface|
|2014-10-09 04:20||laimaretto||Tag Attached: port|
|2014-10-09 04:20||laimaretto||Tag Attached: attributes|
|2014-10-09 04:38||laimaretto||Note Added: 0002525|
|2014-11-29 20:22||hackmaster||Note Added: 0002569|
|2015-06-23 20:57||bbrass||Note Added: 0002889|
|2017-02-13 19:24||infrastation||Tag Detached: attributes|
|2017-04-08 21:45||laimaretto||Note Added: 0003595|