No connectivity on second network interface

Issues related to configuring your network
Post Reply
Alessandro_P
Posts: 3
Joined: 2022/02/11 03:55:30

No connectivity on second network interface

Post by Alessandro_P » 2022/02/11 04:46:29

Hi all,
I have a problem with network connectivity on second network interface of server with centos 7. I've configured a static ip address 10.3.1.4/24 on it. There's two other hosts in this subnet (10.3.1.0/24) and they can ping each other successfully, but centos server can't ping them and they can't ping it.
I would appreciate if anyone could point me in the right direction.
Thanks in advance!
File: ifcfg-eno2

HWADDR=74:46:A0:F5:E8:14
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
IPADDR=10.3.1.4
PREFIX=24
DEFROUTE=yes
PEERDNS=no
PEERROUTES=no
IPV4_FAILURE_FATAL=no
IPV6INIT=no
NAME=eno2
UUID=16c9d014-3257-42f6-bd0a-43f99b4dba2c
ONBOOT=yes
ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 74:46:a0:f5:e8:10 brd ff:ff:ff:ff:ff:ff
3: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 74:46:a0:f5:e8:14 brd ff:ff:ff:ff:ff:ff
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
link/ether 52:54:00:05:e1:62 brd ff:ff:ff:ff:ff:ff
5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN mode DEFAULT group default qlen 1000
link/ether 52:54:00:05:e1:62 brd ff:ff:ff:ff:ff:ff
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group defaul t qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group defa ult qlen 1000
link/ether 74:46:a0:f5:e8:10 brd ff:ff:ff:ff:ff:ff
inet 10.1.1.202/24 brd 10.1.1.255 scope global noprefixroute dynamic eno1
valid_lft 603893sec preferred_lft 603893sec
inet6 fe80::f262:c5c2:d2c0:e35e/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group defa ult qlen 1000
link/ether 74:46:a0:f5:e8:14 brd ff:ff:ff:ff:ff:ff
inet 10.3.1.4/24 brd 10.3.1.255 scope global noprefixroute eno2
valid_lft forever preferred_lft forever
inet6 fe80::7646:a0ff:fef5:e814/64 scope link
valid_lft forever preferred_lft forever
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:05:e1:62 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 sta te DOWN group default qlen 1000
link/ether 52:54:00:05:e1:62 brd ff:ff:ff:ff:ff:ff

Whoever
Posts: 1362
Joined: 2013/09/06 03:12:10

Re: No connectivity on second network interface

Post by Whoever » 2022/02/11 20:48:09

Results of the command:
ip route
?

Alessandro_P
Posts: 3
Joined: 2022/02/11 03:55:30

Re: No connectivity on second network interface

Post by Alessandro_P » 2022/02/12 08:04:18

ip route
default via 10.1.1.1 dev eno1 proto dhcp metric 100
10.1.1.0/24 dev eno1 proto kernel scope link src 10.1.1.202 metric 100
10.3.1.0/24 dev eno2 proto kernel scope link src 10.3.1.4 metric 101
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1

User avatar
jlehtone
Posts: 4540
Joined: 2007/12/11 08:17:33
Location: Finland

Re: No connectivity on second network interface

Post by jlehtone » 2022/02/12 11:00:10

Does the server hear anything with tcpdump -vv -nn -i eno2 when the other subnet members talk/ping it?

Alessandro_P
Posts: 3
Joined: 2022/02/11 03:55:30

Re: No connectivity on second network interface

Post by Alessandro_P » 2022/02/12 21:15:09

The problem is solved. It was unrelated to Centos. Seems like some kind of bug in network module of blade enclosure. Network connectivity appeared when I deleted server profile and then remade it again from scratch.
Thank you for your time and willingness to help!

Post Reply