View Issue Details

IDProjectCategoryView StatusLast Update
1203RackTablesIPv4/IPv6/SLBpublic2014-03-25 14:44
Reporterjzehnter Assigned Toandriyanov  
Status assignedResolutionopen 
Product Version0.20.7 
Summary1203: Opportunity to assign user-defined attributes to ip-addresses and vlans
DescriptionHi Guys,

the opportunity to add user-defined attributes for objects ( Configuration : Attributes ) is very useful.

I would like to have these feature for assigning additional attributes to ip addresses/spaces and vlans as well.

So i can assign ip addresses/spaces attributes like customer or contract ids from our crm system to have an references between these systems, like for traffic-accounting.

Thank you!

For any questions feel free, to contact me.
TagsNo tags attached.




2014-03-25 11:35

reporter   ~0002231

Hello. Tags/attributes assigning to VLANs is possible, but the priority of this task is minor.

Attributes for IP networks have much cleaner perspective to be implemented.

The common workaround for your case is to create an object type named 'client' and to assign IPs and attributes to objects of that type. The VLAN id could either be assigned to an IP network or to an object (using a custom attribute).


2014-03-25 13:09

reporter   ~0002233


thanks for your quick response.

But your workaround is only usable, when there aren´t any other objects in this ip subnet, isn´t it?

So the object "client1" has allocated i.e. 8 IP´s.

But in our system (ISP) it is possible, that the customer have an IP-Subnet (/29) and there are object, which we manage.

Example: net-id gateway server1 managed by customer himself server2 managed by us

So in my racktables installation i have two object created, both managed by us:
gateway + server2

In your workaround the IP (and would have both two allocated objects: client1 (for attribute linking) and gateway (really object)

i don´t know if this workaround is usable in my case?


2014-03-25 13:22

reporter   ~0002235

Yes, it is usable for sure.
It is an IP being associated to object, not a network.

So your client object would have one IP address
You may also create a physical port in a client object and document the customer physical connection.

The network would have these IP addesses:
1: gateway object
2: client object
3: server2 object

There also could be a VLAN id binded to that network.


2014-03-25 13:40

reporter   ~0002237

Thanks, now i understand the workaround better.
For every IP, which isn´t bind to an in racktables created object, i create the dummy object "client" und add there the user-defined attributes (like customer-id, contract-id).

For every explicit created object (i.e. managed by me) i can add the attribute anyway.

But there is one more problem in my intfrastructure.

the gateway-object in our customer´s subnets are mostly a backbone-devices which belongs to our internal infrastructure.
the "gateway" in customer A´s and customer B´s subnet is often the same physical machine and therefore the same object ( i. e. "core-router") with ip addresses in many customer subnets.

in the workaround i can´t assign these gateway-object an customer-specific attribute.

Therefore it would very useful for me, to assign attributes to ip addresses them self.

i will discuss the workaround in a internal meeting, which is decisive for the introduction, in a few minutes.

Thanks for your quick response/help


2014-03-25 14:44

reporter   ~0002239

Sorry, I didn't get the problem.

you say:
> in the workaround i can´t assign these gateway-object an customer-specific attribute.

If your gateway is not specific for a particular customer, why do you want to set those attributes for it? Assign customer attributes only to the customer objects. You can distinguish customer objects from your backbone equipment by naming schema and/or tags.

All the objects having IPs in a network will be displayed in the network's page.

Issue History

Date Modified Username Field Change
2014-03-25 09:46 jzehnter New Issue
2014-03-25 09:46 jzehnter Status new => assigned
2014-03-25 09:46 jzehnter Assigned To => andriyanov
2014-03-25 11:35 andriyanov Note Added: 0002231
2014-03-25 13:09 jzehnter Note Added: 0002233
2014-03-25 13:22 andriyanov Note Added: 0002235
2014-03-25 13:40 jzehnter Note Added: 0002237
2014-03-25 14:44 andriyanov Note Added: 0002239