Hi Team,
I had came up with one issue in centos7, in my centos7 server i have 2 interfaces (ens0,ens1), i did ifdown of ens1, i can reach my machine and it is as expected. now i did ifdown on ens0, both the interfaces are down and so i cant reach my machine as expected, now i did ifup ens0, still not able to reach my machine , i did ifup on ens1 still not able to reach the machine which is not expected!!
i did network restart and then i am able to reach my machine back, i want to understand why was my machine not reachable after bringing up the ports.
please throw some light buddies!!
Network not reachable after ifdown and ifup of interfaces?
Re: Network not reachable after ifdown and ifup of interfaces?
How are the two interfaces setup?
Re: Network not reachable after ifdown and ifup of interfaces?
Hi please find my network config:
cat ens51
DEVICE=ens51
ONBOOT=yes
HOTPLUG=no
NM_CONTROLLED=no
PEERDNS=no
MASTER=bond0
SLAVE=yes
BOOTPROTO=none
ETHTOOL_OPTS="--config-ntuple $DEVICE rx-flow-hash udp4 sdfn; -G $DEVICE rx 2048 tx 2048"
MTU=9050
cat ens50
DEVICE=ens50
ONBOOT=yes
HOTPLUG=no
NM_CONTROLLED=no
PEERDNS=no
MASTER=bond0
SLAVE=yes
BOOTPROTO=none
ETHTOOL_OPTS="--config-ntuple $DEVICE rx-flow-hash udp4 sdfn; -G $DEVICE rx 2048 tx 2048"
MTU=9050
Thanks and Regards
Akhil
cat ens51
DEVICE=ens51
ONBOOT=yes
HOTPLUG=no
NM_CONTROLLED=no
PEERDNS=no
MASTER=bond0
SLAVE=yes
BOOTPROTO=none
ETHTOOL_OPTS="--config-ntuple $DEVICE rx-flow-hash udp4 sdfn; -G $DEVICE rx 2048 tx 2048"
MTU=9050
cat ens50
DEVICE=ens50
ONBOOT=yes
HOTPLUG=no
NM_CONTROLLED=no
PEERDNS=no
MASTER=bond0
SLAVE=yes
BOOTPROTO=none
ETHTOOL_OPTS="--config-ntuple $DEVICE rx-flow-hash udp4 sdfn; -G $DEVICE rx 2048 tx 2048"
MTU=9050
Thanks and Regards
Akhil
Re: Network not reachable after ifdown and ifup of interfaces?
In first post you did mention two interfaces: ens0 and ens1. You also mention CentOS 7, although you have posted to CentOS 8 Forum.
Now you show three differently named interfaces: ens50, ens51, and bond0
If you have a bond with two slaves and you turn off both slaves, then the bond turns off too.
If you restart the slaves but not the bond, it probably stays off.
Now you show three differently named interfaces: ens50, ens51, and bond0
If you have a bond with two slaves and you turn off both slaves, then the bond turns off too.
If you restart the slaves but not the bond, it probably stays off.
Re: Network not reachable after ifdown and ifup of interfaces?
Hello Jlehtone,
i meantioned ens0 and ens1 as an example, sorry for that if it is confusing, yah ihad noticed that bond0 is not up and if i make it up then i am able to ping it. thanks for the support
i meantioned ens0 and ens1 as an example, sorry for that if it is confusing, yah ihad noticed that bond0 is not up and if i make it up then i am able to ping it. thanks for the support
Re: Network not reachable after ifdown and ifup of interfaces?
Your bond status can be seen by reading cat /proc/net/bonding/bond0
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke