Relevence to get multiple I.P. addresses of one NIC

Hi we have cluster servers and web servers that we assign multiple I.P. addresses to one single NIC. Is there any way with relevance to retrieve all the NIC names with all the the assigned I.P. Addresses.

Result should look like
Hostname NIC\Addresses
Jupiter Nic#1 - 10.10.10.7,10.10.11.7
Nic#2 - 10.7.8.10
Mars Nic#1 - 10.10.10.29,10.10.11.18,10.10.11.77
Nic#2 - 10.7.8.10

Thanks
Rene

This should be it:

( (friendly name of it) & " - " & (concatenation ", " of (it as string as trimmed string) of addresses of it) ) of adapters whose(exists addresses of it) of network

I fixed the above relevance, it should give you what you need.

1 Like

jgstew

Trying your solution,

( (friendly name of it) & " - " & (concatenation ", " of (it as string as trimmed string) of addresses of it) ) of adapters whose(exists addresses of it) of network

This is so so close, Unfortunately I only get a result of only one IP assigned to the server.

Jupiter Nic#1 - 10.10.10.7
Nic#2 - 10.7.8.10

Where I would like to get the Nics with multiple IP’s assigned to them listed not just one IP

This is how I would expect to see the results…

Jupiter Nic#1 - 10.10.10.7,10.10.11.7
Nic#2 - 10.7.8.10

Thanks a lot.
Rene

That is what the relevance should do as far as I know. I do wonder if the relevance just doesn’t see the multiple addresses for a single NIC?

I haven’t tested this on a machine with multiple IPs, but it is written so it should work.

Yea it doesnt seem to see the aditional IP’s. I am going to run this through my AVP support and see if there is a workaround or if we need to put in a RFE.

Thanks for your help.
Rene

1 Like

Which OS are you trying this relevance on?

I agree that it might be a bug or some other odd limitation. I’d need to poke around some more to be sure, but it seems possible.

Server 2003,2008,2012… Thanks so much in looking into this.

1 Like

Sorry for the delay, My current issue is a lack access to Win2012 machines with multiple NICs to test this on.

What version of the client are you running?

What version of the Fixlet Debugger are you testing this with?