From: Rahul on
I have ethernet adapters that have twin MAC addresses: one for the regular
use and the other for a Baseboard Management Controller (IPMI) that can be
used to reboot hung machines etc.

All my normal eth cards are assigned to a 10.0.x.x network by DHCP. So far
so good.

Now if I try to set the second IP address to something in the 10.0.x.x
range then things work. Say 10.0.5.3. I can ping the same physical server
(and the same physical card) on twin IP addresses from any remote machine.

arp from the remote pinging machine shows:
Address HWaddress Flags Mask Iface
10.0.0.3 00:26:B9:58:E6:46 C eth0
10.0.4.3 00:26:B9:58:E6:48 C eth0

10.0.0.3 is the normal ethernet IP assigned via DHCP and 10.0.4.3 is for
the BMC.

But let's say I wanted the BMC to respond on the 172.16.x.x subnet. I can
set this address fine. Say, 172.16.0.3 But if I try to ping 172.16.0.3 then
there is no response.

Surprisingly, arp still shows both addresses but the remote ping does not
work.

Address HWaddress Flags Mask Iface
10.0.0.3 00:26:B9:58:E6:46 C eth0
172.16.0.3 00:26:B9:58:E6:48 C eth0

Do I have to do something else to make this work? How do I have two subnets
on the same adapter?

--
Rahul
From: Enrico on
Il Wed, 30 Jun 2010 22:08:26 +0000, Rahul ha scritto:

> Do I have to do something else to make this work? How do I have two
> subnets on the same adapter?

I think you should assign an IP of 172.16.0.0 network on the same
interface. Eg.

ifconfig eth0:1 172.16.0.4/16

(you can use " netmask 255.255.0.0" in place of /16)

man ifconfig

Enrico
From: David Schwartz on
On Jun 30, 3:08 pm, Rahul <nos...(a)nospam.invalid> wrote:

> I have ethernet adapters that have twin MAC addresses: one for the regular
> use and the other for a Baseboard Management Controller (IPMI) that can be
> used to reboot hung machines etc.

Did you properly configure the BMC with a default route, netmask, and
so on?

DS
From: Rahul on
David Schwartz <davids(a)webmaster.com> wrote in
news:7af58078-aa68-45c3-a04c-d0620fdd4b43(a)o14g2000pri.googlegroups.com:

>
> Did you properly configure the BMC with a default route, netmask, and
> so on?

Yup. I think so.

ipmitool lan set 1 ipsrc static
ipmitool lan set 1 ipaddr 172.16.0.3
ipmitool lan set 1 netmask 255.255.0.0

I think this was sucessful because the same set of steps do work if I just
change the 172.16.0.3 to 10.0.4.3.

Also, even if I use the 172.16.0.3 subnet the arp on the remote machine
does recognise the correct mapping between the IP and the MAC.

i.e. arp figures out that 172.16.0.3 is associated with 00:26:B9:58:E6:48
(the right MAC)

There is one thing that I wasn't sure about though: "the default gateway".
Not sure what to set it to. i.e. in the command

ipmitool lan set 1 defgw ipaddr ??
ipmitool lan set 1 defgw netmask ??

But I was thinking that was not really required since when I use the
10.0.x.x subnet it just works without setting this.

--
Rahul
From: Rahul on
Enrico <enrico204(a)virgilio.it> wrote in news:4c2bc51a$0$31372
$4fafbaef(a)reader1.news.tin.it:

> I think you should assign an IP of 172.16.0.0 network on the same
> interface. Eg.
>
> ifconfig eth0:1 172.16.0.4/16
>
> (you can use " netmask 255.255.0.0" in place of /16)
>
> man ifconfig
>

Thanks Enrico! But that assignment is already being done by the ipmi
commands. Should I be doing it again at the kernel level?


--
Rahul