Drac connexion from server itself

Question

Hi,   I'm having troubles connecting to my DRAC interfaces, from the machines themselves. I already had a similar problem with DRAC iface shared with the OS ethernet iface ; it wasn't possible to connect from a machine to its own DRAC. Recently, I setup new machines with dedicated cables on the DRAC iface, and I was hoping everything to work nicely, but I still have the same problem. Here is some config : [root@streamer004 ~]# ifconfig eth0 eth0      Link encap:Ethernet  HWaddr 00:1D:09:70:7B:0C           inet addr:192.168.168.104  Bcast:192.168.171.255  Mask:255.255.252.0   [root@streamer004 ~]# ipmitool lan print 1 -U ipmi Password: ...  IP Address Source       : Static AddressIP Address              : 192.168.169.104...   [root@streamer004 ~]# route -n  192.168.0.0     192.168.171.254 255.255.0.0     UG    0      0        0 eth00.0.0.0         195.55.74.254   0.0.0.0         UG    0      0        0 bond1   [root@streamer004 ~]# ssh ipmi@192.168.169.104ssh: connect to host 192.168.169.104 port 22: No route to host # Successful test from streamer003 to streamer004. Both machine have exactly the same config. [root@streamer004 ~]# ssh ipmi@192.168.169.103ipmi@192.168.169.103's password:   Going through the route 192.168.0.0 should make it loop over 192.168.171.254 and come back on the DRAC iface, but for some reason, it doesn't work ; at least not from a machine to it own DRAC.   Anyone using dedicated DRAC iface (not shared with OS) having such weird problem ? Any solution ?   Thanks.

david.j.wood · Answer

I just tried connecting to a 2950 III's DRAC 5 from itself. The DRAC is using its dedicated interface - NIC sharing is, IMO, asking for trouble if the piggybacking implementation is anything less than perfect.

I had no problems.

Are you sure that the DRAC is set to use the dedicated interface? Check in the DRAC's BIOS. I think you can check this using racadm, but you can't set it using racadm - I think the correct syntax, at least for a DRAC 5, is racadm getconfig -g cfgLanNetworking - I believe that cfgNicSelection should be 2.

If that's not it, check the configuration on 192.168.171.254.

If that still doesn't solve the problem, look at what is happening using a network protocol analyser such as Wireshark. If you have switches capable of port mirroring, that will help tremendously. The ARP packets will be worth watching as well as the SSH packets. Indeed, if you're having problems, I'd start by trying to ping the DRAC rather than SSH to it - though make sure that 192.168.171.254 will allow ICMP (at least types 8 and 0) between the two networks.

elshaa · Answer

Thanks David.

The Drac looks to be dedicated "cfgNicSelection=2".

And indeed, I should have a deep look at the routing machine (192.168.171.254), the problem is very likely sitting here...

I'll comment if I find the solution.

PowerEdge Hardware General

Was this post helpful?