Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: Cant ping to server..

  1. #1

    Cant ping to server..

    Hi.

    I have two nics.

    eth0 - public lan
    eth1 - backup lan

    when I change ip address in backup lan or eth1, I cant ping to server.

    please advise where seems to be wrong.

    thanks.

  2. Re: Cant ping to server..

    Quote Originally Posted by kimkhoo View Post
    Hi.

    I have two nics.

    eth0 - public lan
    eth1 - backup lan

    when I change ip address in backup lan or eth1, I cant ping to server.

    please advise where seems to be wrong.

    thanks.
    Can you post the output of "ip addr show" and "route -n". From where are you pinging? Is there a firewall between the server and the "pinging machine"? How did you change the IP, through YaST or..?

    Thomas

  3. #3

    Re: Cant ping to server..

    Hi Thomas,

    Highlighted in BLUE is for backup NIC.
    In GREEN, is the public NIC.
    I am not sure if it was configured in YAST. But when I change the IP now.. I used command line.
    Thanks in advance.

    server1:~ # ip add show
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
    inet 127.0.0.2/8 brd 127.255.255.255 scope host secondary lo
    2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP qlen 1000
    link/ether 90:e2:ba:4e:db:d4 brd ff:ff:ff:ff:ff:ff
    3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 90:e2:ba:4e:db:d5 brd ff:ff:ff:ff:ff:ff
    4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 90:e2:ba:4e:db:d6 brd ff:ff:ff:ff:ff:ff
    5: eth3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether 90:e2:ba:4e:db:d7 brd ff:ff:ff:ff:ff:ff
    6: eth4: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP qlen 1000
    link/ether 90:e2:ba:4e:db:d4 brd ff:ff:ff:ff:ff:ff
    7: eth5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 40:f2:e9:2b:75:db brd ff:ff:ff:ff:ff:ff
    inet 30.30.30.15/8 brd 30.255.255.255 scope global eth5

    8: eth6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 40:f2:e9:2b:75:dc brd ff:ff:ff:ff:ff:ff
    9: eth7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 40:f2:e9:2b:75:dd brd ff:ff:ff:ff:ff:ff
    11: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc pfifo state UP qlen 1000
    link/ether 90:e2:ba:4e:db:d4 brd ff:ff:ff:ff:ff:ff
    inet 193.18.58.35/24 brd 193.18.58.255 scope global bond0

    26: usb0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 42:f2:e9:2b:75:d9 brd ff:ff:ff:ff:ff:ff


    server1:~ # route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    0.0.0.0 193.18.58.254 0.0.0.0 UG 0 0 0 bond0
    30.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 eth5
    127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
    193.18.58.0 0.0.0.0 255.255.255.0 U 0 0 0 bond0

  4. Re: Cant ping to server..

    Quote Originally Posted by kimkhoo View Post
    Hi Thomas,

    Highlighted in BLUE is for backup NIC.
    In GREEN, is the public NIC.
    I am not sure if it was configured in YAST. But when I change the IP now.. I used command line.
    Thanks in advance.

    server1:~ # ip add show
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
    inet 127.0.0.2/8 brd 127.255.255.255 scope host secondary lo
    2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP qlen 1000
    link/ether 90:e2:ba:4e:db:d4 brd ff:ff:ff:ff:ff:ff
    3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 90:e2:ba:4e:db:d5 brd ff:ff:ff:ff:ff:ff
    4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 90:e2:ba:4e:db:d6 brd ff:ff:ff:ff:ff:ff
    5: eth3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether 90:e2:ba:4e:db:d7 brd ff:ff:ff:ff:ff:ff
    6: eth4: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP qlen 1000
    link/ether 90:e2:ba:4e:db:d4 brd ff:ff:ff:ff:ff:ff
    7: eth5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 40:f2:e9:2b:75:db brd ff:ff:ff:ff:ff:ff
    inet 30.30.30.15/8 brd 30.255.255.255 scope global eth5

    8: eth6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 40:f2:e9:2b:75:dc brd ff:ff:ff:ff:ff:ff
    9: eth7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 40:f2:e9:2b:75:dd brd ff:ff:ff:ff:ff:ff
    11: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc pfifo state UP qlen 1000
    link/ether 90:e2:ba:4e:db:d4 brd ff:ff:ff:ff:ff:ff
    inet 193.18.58.35/24 brd 193.18.58.255 scope global bond0

    26: usb0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 42:f2:e9:2b:75:d9 brd ff:ff:ff:ff:ff:ff


    server1:~ # route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    0.0.0.0 193.18.58.254 0.0.0.0 UG 0 0 0 bond0
    30.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 eth5
    127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
    193.18.58.0 0.0.0.0 255.255.255.0 U 0 0 0 bond0
    And when you say you can't ping the server then I assume you ping this IP 30.30.30.15? From where are you trying to ping, is that device on the same network range as 30.30.30.15/8?

    Thomas

  5. #5

    Re: Cant ping to server..

    Hi Thomas,

    Thanks for quick reply.
    Am ping from another server that is on different network segment.

    I ping by hostname.. # ping server1

    If no change in eth5 *(backup NIC), I can ping. It will return with hostname and ipaddress 193.18.58.35.

    Once I change backup ip add, I cant ping using hostname and ip add at all.

  6. Re: Cant ping to server..

    Quote Originally Posted by kimkhoo View Post
    Hi Thomas,

    Thanks for quick reply.
    Am ping from another server that is on different network segment.

    I ping by hostname.. # ping server1

    If no change in eth5 *(backup NIC), I can ping. It will return with hostname and ipaddress 193.18.58.35.

    Once I change backup ip add, I cant ping using hostname and ip add at all.
    After you change the ip of eth5, post the output of "ip addr show" and "route -n".

    Thomas

  7. #7

    Re: Cant ping to server..

    Hi Thomas,

    server1:~ # ifconfig eth5 172.29.50.52
    server1:~ # route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    0.0.0.0 193.18.58.254 0.0.0.0 UG 0 0 0 bond0
    127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
    172.29.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth5
    193.18.58.0 0.0.0.0 255.255.255.0 U 0 0 0 bond0
    server1:~ # ip add show
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
    inet 127.0.0.2/8 brd 127.255.255.255 scope host secondary lo
    2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP qlen 1000
    link/ether 90:e2:ba:4e:db:d4 brd ff:ff:ff:ff:ff:ff
    3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 90:e2:ba:4e:db:d5 brd ff:ff:ff:ff:ff:ff
    4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 90:e2:ba:4e:db:d6 brd ff:ff:ff:ff:ff:ff
    5: eth3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether 90:e2:ba:4e:db:d7 brd ff:ff:ff:ff:ff:ff
    6: eth4: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP qlen 1000
    link/ether 90:e2:ba:4e:db:d4 brd ff:ff:ff:ff:ff:ff
    7: eth5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 40:f2:e9:2b:75:db brd ff:ff:ff:ff:ff:ff
    inet 172.29.50.52/16 brd 172.29.255.255 scope global eth5

    8: eth6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 40:f2:e9:2b:75:dc brd ff:ff:ff:ff:ff:ff
    9: eth7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 40:f2:e9:2b:75:dd brd ff:ff:ff:ff:ff:ff
    11: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc pfifo state UP qlen 1000
    link/ether 90:e2:ba:4e:db:d4 brd ff:ff:ff:ff:ff:ff
    inet 193.18.58.35/24 brd 193.18.58.255 scope global bond0
    26: usb0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 42:f2:e9:2b:75:d9 brd ff:ff:ff:ff:ff:ff

  8. Re: Cant ping to server..

    Quote Originally Posted by kimkhoo View Post
    Hi Thomas,

    server1:~ # ifconfig eth5 172.29.50.52
    server1:~ # route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    0.0.0.0 193.18.58.254 0.0.0.0 UG 0 0 0 bond0
    127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
    172.29.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth5
    193.18.58.0 0.0.0.0 255.255.255.0 U 0 0 0 bond0
    server1:~ # ip add show
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
    inet 127.0.0.2/8 brd 127.255.255.255 scope host secondary lo
    2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP qlen 1000
    link/ether 90:e2:ba:4e:db:d4 brd ff:ff:ff:ff:ff:ff
    3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 90:e2:ba:4e:db:d5 brd ff:ff:ff:ff:ff:ff
    4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 90:e2:ba:4e:db:d6 brd ff:ff:ff:ff:ff:ff
    5: eth3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether 90:e2:ba:4e:db:d7 brd ff:ff:ff:ff:ff:ff
    6: eth4: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP qlen 1000
    link/ether 90:e2:ba:4e:db:d4 brd ff:ff:ff:ff:ff:ff
    7: eth5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 40:f2:e9:2b:75:db brd ff:ff:ff:ff:ff:ff
    inet 172.29.50.52/16 brd 172.29.255.255 scope global eth5

    8: eth6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 40:f2:e9:2b:75:dc brd ff:ff:ff:ff:ff:ff
    9: eth7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 40:f2:e9:2b:75:dd brd ff:ff:ff:ff:ff:ff
    11: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc pfifo state UP qlen 1000
    link/ether 90:e2:ba:4e:db:d4 brd ff:ff:ff:ff:ff:ff
    inet 193.18.58.35/24 brd 193.18.58.255 scope global bond0
    26: usb0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 42:f2:e9:2b:75:d9 brd ff:ff:ff:ff:ff:ff
    That looks okay to me... strange... The server you are pinging from, is it on the 172.29.0.0 0.0.0.0 255.255.0.0 network?

    Thomas

  9. #9

    Re: Cant ping to server..

    How does your pinging machine get the IP address of the server? If from
    DNS, are you updating DNS at the same time that you change the server's IP
    address? If not from DNS, are you updating the /etc/hosts file at the
    same time that you change the server's IP address?

    Pinging is a network layer (layer 3) test, so stick with layer three
    addresses (IPs) and test that. If that works, then move over to try
    application layer (layer seven) tests by verifying DNS is setup correctly.
    Avoid merely using hostnames; they are not reliable and are too-dependent
    on where your computer is, if they have a search list setup, etc.

    --
    Good luck.

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below...

  10. Re: Cant ping to server..

    Hi kimkhoo,

    if I understand your situation right, you're always pinging the "public" IP address of the server in question, while changing the IP address on the "backup" interface.

    One possible reason that pinging the server from your test machine breaks after changing the backup interface IP, is that the ping response, sent by the server, goes out the backup interface. The most likely reason for this would be that the pinging test machine uses a source IP address from the same subnet range as the backup interface of your server (172.29.0.0/16).

    Regards,
    J
    From the times when today's "old school" was "new school"

    If you find this post helpful and are logged into the web interface, show your appreciation and click on the star below...

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •