← Back to team overview

fuel-dev team mailing list archive

Re: Controller node ip is not pinging from Compute node

 

Gentle Reminder!

From: Gandhirajan Mariappan (CW)
Sent: Tuesday, June 17, 2014 5:42 PM
To: fuel-dev@xxxxxxxxxxxxxxxxxxx; 'Miroslav Anashkin'
Cc: DL-GRP-ENG-SQA-Open Stack; Prakash Kaligotla; eshumakher@xxxxxxxxxxxx; adanin@xxxxxxxxxxxx; izinovik@xxxxxxxxxxxx
Subject: Controller node ip is not pinging from Compute node

Hi Fuel Dev,

Controller node IP address-management (192.168.0.3) is not pinging from Compute node(10.24.41.2), whereas Controller node's Public IP address (10.24.41.3) can be able to ping from Compute node(10.24.41.2). Also, all the configuration files in Compute node are referring 192.168.0.3 which is not even pinging. Kindly let us know how to proceed on this.


root@node-5:/etc/nova# ping 192.168.0.3
PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data.
>From 192.168.0.2 icmp_seq=1 Destination Host Unreachable
>From 192.168.0.2 icmp_seq=2 Destination Host Unreachable
>From 192.168.0.2 icmp_seq=3 Destination Host Unreachable
>From 192.168.0.2 icmp_seq=4 Destination Host Unreachable
>From 192.168.0.2 icmp_seq=5 Destination Host Unreachable
>From 192.168.0.2 icmp_seq=6 Destination Host Unreachable
^C
--- 192.168.0.3 ping statistics ---
8 packets transmitted, 0 received, +6 errors, 100% packet loss, time 7038ms
pipe 3

root@node-5:/etc/nova# ping 10.24.41.3
PING 10.24.41.3 (10.24.41.3) 56(84) bytes of data.
64 bytes from 10.24.41.3: icmp_req=1 ttl=64 time=0.721 ms
64 bytes from 10.24.41.3: icmp_req=2 ttl=64 time=0.264 ms
64 bytes from 10.24.41.3: icmp_req=3 ttl=64 time=0.256 ms


Thanks and Regards,
Gandhi Rajan

Follow ups

References