Re: [Freeipmi-users] ipmiping newbie question

[Albert Chu]

Hi Rene,

> As you can see Server A can't even ping itself.  Any idea as to 
> what I am missing here?

Unlike normal 'ping', ipmiping and rmcpping cannot actually ping the
machine you are on.  Ipmiping and rmcpping must send a packet onto the
network so it can reach the service processor sitting on the network
card.  So this failure is expected.  However, I can see where someone
new to ipmi wouldn't see this immediately.  I will put a note about this
in the manpages.

> If I understand the way this works correctly Server B can actually be
> powered off with no OS and as long as the server is connected to the
> network and has power it should replay to the ipmiping and other
> commands correct?

You're correct.  As long as the service processor is configured properly
(I would assume the 'lancfg' program would do it) an OS on the remote
machine shouldn't be required.  Have you tried having the cross-over
cable connected to both eth0 and eth1?  The IPMI NIC may be on eth0 not
eth1?

Could you also try 'rmcpping' just for kicks?  It could indicate one
thing is mis-configured while another isn't.

I'll also forward your e-mail off to another IBM IPMI user I know.  He
may know something subtle that I don't.

Al

--
Albert Chu
address@hidden
925-422-5311
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory


----- Original Message -----
From: Rene Salmon <address@hidden>
Date: Tuesday, March 28, 2006 3:13 pm
Subject: [Freeipmi-users] ipmiping newbie question

> Hi list,
> 
> Could not find enough docs to help me with this so I am hopping 
> some one 
> can point me in the right direction on setting this up.
> 
> I have two IBM e325 servers one has freeipmi installed on it and 
> the 
> other does not.
> 
> Server A has freeimpi installed and it has an IPMI IP address of 
> 192.168.0.10 which was setup by IBM utility lancfg.
> Server A has two interfaces eth0 and eth1
> 
> eth0 => public IP
> eth1 => no IP assigned by the OS but it does have a crossover 
> ethernet 
> cable connecting it to server B.
> 
> Server B is up an running and it has IPMI IP address of 
> 192.168.0.11 
> setup by IBM utility lancfg.
> Server B has two interfaces eth0 and eth1
> 
> eth0=> no IP assigned by the OS.
> eth1=> no IP assigned by the OS but it does have a crossover 
> ethernet 
> cable connecting it to server A.
> 
> 
> If I understand the way this works correctly Server B can actually 
> be 
> powered off with no OS and as long as the server is connected to 
> the 
> network and has power it should replay to the ipmiping and other 
> commands correct?
> 
> When I log into Server A and type ipmiping I get nothing:
> 
> Server A# ipmiping 192.168.0.11
> ipmiping 192.168.0.11 (192.168.0.11)
> response timed out: rq_seq=5
> --- ipmiping 192.168.0.11 statistics ---
> 2 requests transmitted, 0 responses received in time, 100.0% packet 
> loss
> Server A# ipmiping 192.168.0.10
> ipmiping 192.168.0.10 (192.168.0.10)
> response timed out: rq_seq=51
> --- ipmiping 192.168.0.10 statistics ---
> 2 requests transmitted, 0 responses received in time, 100.0% packet 
> loss
> 
> As you can see Server A can't even ping itself.  Any idea as to 
> what I 
> am missing here?
> 
> Thanks
> Rene
> 
> 
> 
> 
> 
> -- 
> -
> --
>         Rene Salmon
>         Tulane University
>         Center for Computational Science
>         Richardson Building 310
>         New Orleans, LA 70118
>         http://www.ccs.tulane.edu
>         Tel 504-862-8393
>         Fax 504-862-8392
> 
> 
> 
> _______________________________________________
> Freeipmi-users mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/freeipmi-users
>