IP Address for Loopback Adapter

[tsorgie]

On our Windows 2k3 servers we install a loopback interface at the address 192.168.68.8 on each machine. We just installed Hyperic and are testing it out, and we've noticed that when we add a new platform, and then remove it sometimes a different one gets deleted. We are wondering if having the loopback address in common on each machine could be contributing to the problems we're having, or if you may have other thoughts.

[john_hyperic]

This would, in fact cause problems. HQ uses the IP address and FQDN to
find platforms. Having multiple platforms with the same IP address
would certainly cause problems. Right now, we ignore the common
loopback address of 127.0.0.1. Sounds like we need to add more checking
to see if there are other loopback addresses to ignore.

[john_hyperic]

Logged http://jira.hyperic.com/browse/HHQ-271

[Douglas MacEachern]

We should probably just filter out all loopback addresses (for the use
that John mentioned), they will still show up as network interfaces.
Before I make that change, can you post the output of the following
command run from the agent directory:

.\jre\bin\java -jar pdk\lib\sigar.jar ifconfig

Thanks.

Thomas Sorgie wrote:
> On our Windows 2k3 servers we install a loopback interface at the address 192.168.68.8 on each machine. We just installed Hyperic and are testing it out, and we've noticed that when we add a new platform, and then remove it sometimes a different one gets deleted. We are wondering if having the loopback address in common on each machine could be contributing to the problems we're having, or if you may have other thoughts.
>

[tsorgie]

Hey guys,

Thanks for the fast response -- ok so here is the output for two of my servers.. you'll see that we have the "Microsoft Loopback Adapter" installed on both of them. I noticed that across all of our machines the MAC address for the microsoft loopback is always consistent (perhaps you can use that for detecting it as a loopback).

----MACHINE 1

Microsoft Loopback Adapter
eth0 Link encap:Ethernet HWaddr 02:00:4C:4F:4F:50
inet addr:192.168.68.8 Bcast:255.255.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:0
RX packets:3 errors:0 dropped:0 overruns:-1 frame:-1
TX packets:3 errors:0 dropped:0 overruns:-1 carrier:-1
collisions:-1
RX bytes:126 (126 ) TX bytes:126 (126 )

BASP Virtual Adapter
eth1 Link encap:Ethernet HWaddr 00:0D:56:FD:2E:BE
inet addr:10.200.25.1 Bcast:255.255.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:0
RX packets:3729851 errors:0 dropped:0 overruns:-1 frame:-1
TX packets:3448388 errors:0 dropped:0 overruns:-1 carrier:-1
collisions:-1
RX bytes:1628235836 (1.5G) TX bytes:1226784243 (1.1G)

Intel(R) PRO/1000 MT Server Adapter
eth2 Link encap:Ethernet HWaddr 00:04:23:A5:CD:CC
inet addr:10.205.25.1 Bcast:255.255.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:0
RX packets:1780560 errors:0 dropped:0 overruns:-1 frame:-1
TX packets:652633 errors:0 dropped:0 overruns:-1 carrier:-1
collisions:-1
RX bytes:871489721 (831M) TX bytes:115800148 (110M)

MS TCP Loopback interface
lo0 Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:0.0.0.0 Mask:255.0.0.0
UP BROADCAST LOOPBACK RUNNING MULTICAST MTU:1520 Metric:0
RX packets:670506 errors:0 dropped:0 overruns:-1 frame:-1
TX packets:670504 errors:0 dropped:0 overruns:-1 carrier:-1
collisions:-1
RX bytes:46525062 ( 44M) TX bytes:46525062 ( 44M)





----MACHINE 2

Microsoft Loopback Adapter
eth0 Link encap:Ethernet HWaddr 02:00:4C:4F:4F:50
inet addr:192.168.68.8 Bcast:255.255.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:0
RX packets:27 errors:0 dropped:0 overruns:-1 frame:-1
TX packets:27 errors:0 dropped:0 overruns:-1 carrier:-1
collisions:-1
RX bytes:2334 (2.3K) TX bytes:2334 (2.3K)

BASP Virtual Adapter
eth1 Link encap:Ethernet HWaddr 00:15:C5:E7:84:62
inet addr:10.10.25.4 Bcast:255.255.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:0
RX packets:600218 errors:0 dropped:0 overruns:-1 frame:-1
TX packets:908518 errors:0 dropped:0 overruns:-1 carrier:-1
collisions:-1
RX bytes:69617657 ( 66M) TX bytes:144975122 (138M)

MS TCP Loopback interface
lo0 Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:0.0.0.0 Mask:255.0.0.0
UP BROADCAST LOOPBACK RUNNING MULTICAST MTU:1520 Metric:0
RX packets:7434450 errors:0 dropped:0 overruns:-1 frame:-1
TX packets:7429584 errors:0 dropped:0 overruns:-1 carrier:-1
collisions:-1
RX bytes:1049480662 (1.0G) TX bytes:1049480662 (1.0G)


Now i also have another problem -- when running these commands on a third machine - i noticed that the output seems to be completely incorrect. Would you prefer that i open a new thread/bug for that -- or continue to append here. (Basically the IP address/loopback address and macs were all reversed -- pretty strange).

thanks for the fast response..

tom.

[Douglas MacEachern]

Thomas Sorgie wrote:
> Hey guys,
>
> Thanks for the fast response -- ok so here is the output for two of my servers.. you'll see that we have the "Microsoft Loopback Adapter" installed on both of them. I noticed that across all of our machines the MAC address for the microsoft loopback is always consistent (perhaps you can use that for detecting it as a loopback).
>
...
Thanks for the info Thomas. Looks like we would need to check the
description for "Microsoft Loopback Adapter", because unlike the default
"MS TCP Loopback interface", it doesn't have the LOOPBACK flag set I
would have used to filter out loopback addresses.
> Now i also have another problem -- when running these commands on a third machine - i noticed that the output seems to be completely incorrect. Would you prefer that i open a new thread/bug for that -- or continue to append here. (Basically the IP address/loopback address and macs were all reversed -- pretty strange).
>
Please do open a bug in JIRA for this, under the SIGAR component. Thanks.

[tsorgie]

Logged bug: http://jira.hyperic.com/browse/SIGAR-23 for the sigar adapters issue.