Working with Network on CentOS/RHEL 07 - Part 05

Home

NetworkManager And Network Scripts

- In previous RHEL 5.X and RHEL 6.X releases, the default way to configure networking was using network scripts. The term network scripts is commonly used for the script /etc/init.d/network and any other installed scripts it calls.

- Administrators who are used to these scripts can certainly continue to use them.

- Run the script only with the “systemctl” utility which will clear any existing environment variables and ensure clean execution. The command takes the following form:

systemctl start| stop| restart| status network

- Do not run any service by calling /etc/init.d/servicename start| stop| restart| status directly. As, “NetworkManager Daemon” is started first and /etc/init.d/network checks with “NetworkManager Daemon” to avoid tampering with NetworkManager's connections.

- NetworkManager is intended to be the primary application using sysconfig configuration files and /etc/init.d/network is intended to be secondary playing a fallback role.

- The /etc/init.d/network script is not event-driven hence it was moved to secondary role in RHEL 7, it runs either:

- Manually (by one of the systemctl commands start| stop| restart network)

- On boot and shutdown if the network service is enabled (as a result of the command systemctl enable network).

- Being a manual process and does not react to events that happen after boot.

- Scripts “ifup” and “ifdown” can be used as it was in previous releases of RHEL overall sequence of events that will happen are as below,

- If the device is managed by NetworkManager and it is already connected, nothing is done.

- If the device is not managed by NetworkManager, then the scripts will start the connection using the older, non-NetworkManager mechanisms that they have used since the time before NetworkManager existed.

- The /etc/sysconfig/directory is a location for configuration files and scripts. Most network configuration information is stored there, with the exception of VPN, mobile broadband and PPPoE configuration, which are stored in /etc/NetworkManager/ subdirectories.

- Interface specific information is stored in ifcfg files in the /etc/sysconfig/network-scripts/ directory.

- The file /etc/sysconfig/network is for global settings.

- Information for VPNs, mobile broadband and PPPoE connections is stored in /etc/NetworkManager/system-connections/.

- In Red Hat Enterprise Linux 7 when you edit an ifcfg file, NetworkManager is not automatically aware of the change and has to be prompted to notice the change.

- So considering this point below traditional practice becomes invalid and should not be used,

- Modify ifcfg-interface file in /etc/sysconfig-network-scripts folder

-Network service restart, i.e. restart “NetworkManager Daemon” (Note:- If a sequence of ifdown and ifup utilities if used in this sequence then changes will be applied properly to the required interface)

- Changes in ifcfg-interface file in /etc/sysconfig-network-scripts folder will not be reflected.

- Below is an example of the flow, Have a look on existing configuration of interface,

[root@testvm07002 network-scripts]# ip a sh dev enp0s10

5: enp0s10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000

    link/ether 08:00:27:94:3e:02 brd ff:ff:ff:ff:ff:ff

    inet 192.168.50.6/24 brd 192.168.50.255 scope global dynamic enp0s10

       valid_lft 736sec preferred_lft 736sec

    inet6 fe80::a00:27ff:fe94:3e02/64 scope link

       valid_lft forever preferred_lft forever

[root@testvm07002 network-scripts]# pwd

/etc/sysconfig/network-scripts

[root@testvm07002 network-scripts]# ls

ifcfg-enp0s10   ifcfg-enp0s9  ifdown-eth   ifdown-post    ifdown-Team      ifup-aliases  ifup-ipv6   ifup-post    ifup-Team      init.ipv6-global

ifcfg-enp0s3    ifcfg-lo      ifdown-ippp  ifdown-ppp     ifdown-TeamPort  ifup-bnep     ifup-isdn   ifup-ppp     ifup-TeamPort  network-functions

ifcfg-enp0s3-1  ifdown        ifdown-ipv6  ifdown-routes  ifdown-tunnel    ifup-eth      ifup-plip   ifup-routes  ifup-tunnel    network-functions-ipv6

ifcfg-enp0s8    ifdown-bnep   ifdown-isdn  ifdown-sit     ifup             ifup-ippp     ifup-plusb  ifup-sit     ifup-wireless  route-enp0s3-1

[root@testvm07002 network-scripts]# cat ifcfg-enp0s10

TYPE=Ethernet

BOOTPROTO=dhcp

DEFROUTE=yes

IPV4_FAILURE_FATAL=no

IPV6INIT=yes

IPV6_AUTOCONF=yes

IPV6_DEFROUTE=yes

IPV6_FAILURE_FATAL=no

NAME=enp0s10-connection

UUID=4474b5b1-e576-45bd-babb-c3ce22d41166

ONBOOT=yes

HWADDR=08:00:27:94:3E:02

PEERDNS=yes

PEERROUTES=yes

IPV6_PEERDNS=yes

IPV6_PEERROUTES=yes

- Now modify configuration of interface as below,

[root@testvm07002 network-scripts]# vi ifcfg-enp0s10

[root@testvm07002 network-scripts]# cat ifcfg-enp0s10

TYPE=Ethernet

NAME=enp0s10

BOOTPROTO=static

HWADDR=08:00:27:94:3E:02

ONBOOT=yes

IPADDR=192.168.248.184

NETMASK=255.255.255.0

GATEWAY=192.168.248.1

IPV6INIT=no

[root@testvm07002 network-scripts]# ip a sh dev enp0s10

5: enp0s10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000

    link/ether 08:00:27:94:3e:02 brd ff:ff:ff:ff:ff:ff

    inet 192.168.50.6/24 brd 192.168.50.255 scope global dynamic enp0s10

       valid_lft 589sec preferred_lft 589sec

    inet6 fe80::a00:27ff:fe94:3e02/64 scope link

       valid_lft forever preferred_lft forever

- Now we will do the NetworkManager daemon restart similar to method used in earlier version of RHEL 5/6 and check for the IP address on interface you will not see the changes reflected,

[root@testvm07002 network-scripts]# systemctl restart NetworkManager.service

[root@testvm07002 network-scripts]# ip a sh dev enp0s10

5: enp0s10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000

    link/ether 08:00:27:94:3e:02 brd ff:ff:ff:ff:ff:ff

    inet 192.168.50.6/24 brd 192.168.50.255 scope global dynamic enp0s10

       valid_lft 401sec preferred_lft 401sec

    inet6 fe80::a00:27ff:fe94:3e02/64 scope link

       valid_lft forever preferred_lft forever

- As NetworkManager Daemon needs to be explicitly communicated for the changes in the Interface configuration scripts above Daemon restart will not help, Now we will see how we can get the changes communicated to Daemon.

- Reload the interface using ifdown and ifup commands as these commands directly contact daemon for the restart who manages the interface actually.

[root@testvm07002 network-scripts]# ifdown enp0s10

[root@testvm07002 network-scripts]# ip a sh dev enp0s10

5: penp0s10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000

    link/ether 08:00:27:94:3e:02 brd ff:ff:ff:ff:ff:ff

[root@testvm07002 network-scripts]# ifup enp0s10

Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/6)

[root@testvm07002 network-scripts]# ip a sh dev enp0s10

5: enp0s10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000

    link/ether 08:00:27:94:3e:02 brd ff:ff:ff:ff:ff:ff

    inet 192.168.248.184/24 brd 192.168.248.255 scope global enp0s10

       valid_lft forever preferred_lft forever

    inet6 fe80::a00:27ff:fe94:3e02/64 scope link

       valid_lft forever preferred_lft forever

- Changes will be reflected properly this time as communication about interface configuration changes has been carried out by ifdown and ifup commands.

- Below are the logs printed in the journalctl for restart of "NetworkManager Daemon", Studying this logs in detail separately would be required,

Apr 05 10:49:18 testvm07002 systemd[1]: Stopping Network Manager...

Apr 05 10:49:18 testvm07002 NetworkManager[17449]: <info> caught signal 15, shutting down normally.

Apr 05 10:49:19 testvm07002 NetworkManager[17449]: <info> exiting (success)

Apr 05 10:49:19 testvm07002 systemd[1]: Starting Network Manager...

Apr 05 10:49:21 testvm07002 NetworkManager[17560]: <info> NetworkManager (version 0.9.9.1-29.git20140326.4dba720.el7_0) is starting...

Apr 05 10:49:21 testvm07002 NetworkManager[17560]: <info> Read config: /etc/NetworkManager/NetworkManager.conf

Apr 05 10:49:21 testvm07002 NetworkManager[17560]: <info> WEXT support is disabled

Apr 05 10:49:22 testvm07002 NetworkManager[17560]: ifcfg-rh: Acquired D-Bus service com.redhat.ifcfgrh1

Apr 05 10:49:22 testvm07002 NetworkManager[17560]: <info> Loaded plugin ifcfg-rh: (c) 2007 - 2013 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.

Apr 05 10:49:22 testvm07002 NetworkManager[17560]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.

Apr 05 10:49:22 testvm07002 NetworkManager[17560]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ...

Apr 05 10:49:22 testvm07002 NetworkManager[17560]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-enp0s3 ...

Apr 05 10:49:22 testvm07002 NetworkManager[17560]: ifcfg-rh:     read connection 'enp0s3'

Apr 05 10:49:22 testvm07002 NetworkManager[17560]: ifcfg-rh: Ignoring connection 'enp0s3' / device '08:00:27:41:a7:79' due to NM_CONTROLLED=no.

Apr 05 10:49:22 testvm07002 NetworkManager[17560]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-enp0s9 ...

Apr 05 10:49:23 testvm07002 NetworkManager[17560]: ifcfg-rh:     read connection 'enp0s9-connection'

Apr 05 10:49:23 testvm07002 NetworkManager[17560]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-enp0s8 ...

Apr 05 10:49:23 testvm07002 NetworkManager[17560]: ifcfg-rh:     read connection 'enp0s8-connection'

Apr 05 10:49:23 testvm07002 NetworkManager[17560]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-enp0s3-1 ...

Apr 05 10:49:23 testvm07002 NetworkManager[17560]: ifcfg-rh:     read connection 'enp0s3'

Apr 05 10:49:23 testvm07002 NetworkManager[17560]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-enp0s10 ...

Apr 05 10:49:23 testvm07002 NetworkManager[17560]: ifcfg-rh:     error: File '/etc/sysconfig/network-scripts/ifcfg-enp0s10' had neither TYPE nor DEVICE keys.

Apr 05 10:49:23 testvm07002 NetworkManager[17560]: <info> monitoring kernel firmware directory '/lib/firmware'.

Apr 05 10:49:23 testvm07002 NetworkManager[17560]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-adsl.so

Apr 05 10:49:24 testvm07002 NetworkManager[17560]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so

Apr 05 10:49:24 testvm07002 NetworkManager[17560]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-wwan.so

Apr 05 10:49:24 testvm07002 systemd[1]: Started Network Manager.

Apr 05 10:49:24 testvm07002 systemd[1]: Starting Network Manager Wait Online...

Apr 05 10:49:24 testvm07002 NetworkManager[17560]: <info> WiFi enabled by radio killswitch; enabled by state file

Apr 05 10:49:24 testvm07002 NetworkManager[17560]: <info> WWAN enabled by radio killswitch; enabled by state file

Apr 05 10:49:24 testvm07002 NetworkManager[17560]: <info> WiMAX enabled by radio killswitch; enabled by state file

Apr 05 10:49:24 testvm07002 NetworkManager[17560]: <info> Networking is enabled by state file

Apr 05 10:49:26 testvm07002 NetworkManager[17560]: <info> (lo): link connected

Apr 05 10:49:26 testvm07002 NetworkManager[17560]: <info> (lo): carrier is ON

Apr 05 10:49:26 testvm07002 NetworkManager[17560]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1)

Apr 05 10:49:26 testvm07002 NetworkManager[17560]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0

Apr 05 10:49:27 testvm07002 NetworkManager[17560]: <info> (enp0s3): link connected

Apr 05 10:49:27 testvm07002 NetworkManager[17560]: <info> (enp0s3): carrier is ON

Apr 05 10:49:27 testvm07002 NetworkManager[17560]: <info> (enp0s3): new Ethernet device (driver: 'e1000' ifindex: 2)

Apr 05 10:49:27 testvm07002 NetworkManager[17560]: <info> (enp0s3): exported as /org/freedesktop/NetworkManager/Devices/1

Apr 05 10:49:27 testvm07002 NetworkManager[17560]: <info> (enp0s3): found matching connection 'enp0s3'

Apr 05 10:49:27 testvm07002 NetworkManager[17560]: <info> (enp0s3): device state change: unmanaged -> disconnected (reason 'connection-assumed') [10 30 41]

Apr 05 10:49:27 testvm07002 NetworkManager[17560]: <info> Activation (enp0s3) starting connection 'enp0s3'

Apr 05 10:49:27 testvm07002 NetworkManager[17560]: <info> Activation (enp0s3) Stage 1 of 5 (Device Prepare) scheduled...

Apr 05 10:49:27 testvm07002 NetworkManager[17560]: <info> (enp0s8): link connected

Apr 05 10:49:27 testvm07002 NetworkManager[17560]: <info> (enp0s8): carrier is ON

Apr 05 10:49:28 testvm07002 NetworkManager[17560]: <info> (enp0s8): new Ethernet device (driver: 'e1000' ifindex: 3)

Apr 05 10:49:28 testvm07002 NetworkManager[17560]: <info> (enp0s8): exported as /org/freedesktop/NetworkManager/Devices/2

Apr 05 10:49:28 testvm07002 NetworkManager[17560]: ifcfg-rh:     read connection 'enp0s8'

Apr 05 10:49:28 testvm07002 NetworkManager[17560]: <info> (enp0s8): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41]

Apr 05 10:49:28 testvm07002 NetworkManager[17560]: <info> (enp0s8): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41]

Apr 05 10:49:28 testvm07002 NetworkManager[17560]: <info> Activation (enp0s8) starting connection 'enp0s8'

Apr 05 10:49:28 testvm07002 NetworkManager[17560]: <info> Activation (enp0s8) Stage 1 of 5 (Device Prepare) scheduled...

Apr 05 10:49:28 testvm07002 NetworkManager[17560]: <info> (enp0s9): link connected

Apr 05 10:49:28 testvm07002 NetworkManager[17560]: <info> (enp0s9): carrier is ON

Apr 05 10:49:29 testvm07002 NetworkManager[17560]: <info> (enp0s9): new Ethernet device (driver: 'e1000' ifindex: 4)

Apr 05 10:49:29 testvm07002 NetworkManager[17560]: <info> (enp0s9): exported as /org/freedesktop/NetworkManager/Devices/3

Apr 05 10:49:29 testvm07002 NetworkManager[17560]: <info> (enp0s9): found matching connection 'enp0s9-connection'

Apr 05 10:49:29 testvm07002 NetworkManager[17560]: <info> (enp0s9): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41]

Apr 05 10:49:29 testvm07002 NetworkManager[17560]: <info> (enp0s9): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41]

Apr 05 10:49:29 testvm07002 NetworkManager[17560]: <info> Activation (enp0s9) starting connection 'enp0s9-connection'

Apr 05 10:49:29 testvm07002 NetworkManager[17560]: <info> Activation (enp0s9) Stage 1 of 5 (Device Prepare) scheduled...

Apr 05 10:49:30 testvm07002 NetworkManager[17560]: <info> (enp0s10): link connected

Apr 05 10:49:30 testvm07002 NetworkManager[17560]: <info> (enp0s10): carrier is ON

Apr 05 10:49:30 testvm07002 NetworkManager[17560]: <info> (enp0s10): new Ethernet device (driver: 'e1000' ifindex: 5)

Apr 05 10:49:30 testvm07002 NetworkManager[17560]: <info> (enp0s10): exported as /org/freedesktop/NetworkManager/Devices/4

Apr 05 10:49:30 testvm07002 NetworkManager[17560]: ifcfg-rh:     read connection 'enp0s10'

Apr 05 10:49:30 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41]

Apr 05 10:49:31 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41]

Apr 05 10:49:31 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) starting connection 'enp0s10'

Apr 05 10:49:31 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 1 of 5 (Device Prepare) scheduled...

Apr 05 10:49:31 testvm07002 NetworkManager[17560]: <info> Activation (enp0s3) Stage 1 of 5 (Device Prepare) started...

Apr 05 10:49:31 testvm07002 NetworkManager[17560]: <info> (enp0s3): device state change: disconnected -> prepare (reason 'none') [30 40 0]

Apr 05 10:49:31 testvm07002 NetworkManager[17560]: <info> Activation (enp0s3) Stage 2 of 5 (Device Configure) scheduled...

Apr 05 10:49:31 testvm07002 NetworkManager[17560]: <info> Activation (enp0s3) Stage 1 of 5 (Device Prepare) complete.

Apr 05 10:49:31 testvm07002 NetworkManager[17560]: <info> Activation (enp0s8) Stage 1 of 5 (Device Prepare) started...

Apr 05 10:49:31 testvm07002 NetworkManager[17560]: <info> (enp0s8): device state change: disconnected -> prepare (reason 'none') [30 40 0]

Apr 05 10:49:31 testvm07002 NetworkManager[17560]: <info> Activation (enp0s8) Stage 2 of 5 (Device Configure) scheduled...

Apr 05 10:49:31 testvm07002 NetworkManager[17560]: <info> Activation (enp0s8) Stage 1 of 5 (Device Prepare) complete.

Apr 05 10:49:31 testvm07002 NetworkManager[17560]: <info> Activation (enp0s9) Stage 1 of 5 (Device Prepare) started...

Apr 05 10:49:31 testvm07002 NetworkManager[17560]: <info> (enp0s9): device state change: disconnected -> prepare (reason 'none') [30 40 0]

Apr 05 10:49:31 testvm07002 NetworkManager[17560]: <info> Activation (enp0s9) Stage 2 of 5 (Device Configure) scheduled...

Apr 05 10:49:31 testvm07002 NetworkManager[17560]: <info> Activation (enp0s9) Stage 1 of 5 (Device Prepare) complete.

Apr 05 10:49:31 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 1 of 5 (Device Prepare) started...

Apr 05 10:49:31 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: disconnected -> prepare (reason 'none') [30 40 0]

Apr 05 10:49:31 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 2 of 5 (Device Configure) scheduled...

Apr 05 10:49:31 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 1 of 5 (Device Prepare) complete.

Apr 05 10:49:32 testvm07002 NetworkManager[17560]: <info> Activation (enp0s3) Stage 2 of 5 (Device Configure) starting...

Apr 05 10:49:32 testvm07002 NetworkManager[17560]: <info> (enp0s3): device state change: prepare -> config (reason 'none') [40 50 0]

Apr 05 10:49:32 testvm07002 NetworkManager[17560]: <info> Activation (enp0s3) Stage 2 of 5 (Device Configure) successful.

Apr 05 10:49:32 testvm07002 NetworkManager[17560]: <info> Activation (enp0s3) Stage 2 of 5 (Device Configure) complete.

Apr 05 10:49:32 testvm07002 NetworkManager[17560]: <info> Activation (enp0s8) Stage 2 of 5 (Device Configure) starting...

Apr 05 10:49:32 testvm07002 NetworkManager[17560]: <info> (enp0s8): device state change: prepare -> config (reason 'none') [40 50 0]

Apr 05 10:49:32 testvm07002 NetworkManager[17560]: <info> Activation (enp0s8) Stage 2 of 5 (Device Configure) successful.

Apr 05 10:49:32 testvm07002 NetworkManager[17560]: <info> Activation (enp0s8) Stage 2 of 5 (Device Configure) complete.

Apr 05 10:49:33 testvm07002 NetworkManager[17560]: <info> Activation (enp0s9) Stage 2 of 5 (Device Configure) starting...

Apr 05 10:49:33 testvm07002 NetworkManager[17560]: <info> (enp0s9): device state change: prepare -> config (reason 'none') [40 50 0]

Apr 05 10:49:33 testvm07002 NetworkManager[17560]: <info> Activation (enp0s9) Stage 2 of 5 (Device Configure) successful.

Apr 05 10:49:33 testvm07002 NetworkManager[17560]: <info> Activation (enp0s9) Stage 2 of 5 (Device Configure) complete.

Apr 05 10:49:33 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 2 of 5 (Device Configure) starting...

Apr 05 10:49:33 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: prepare -> config (reason 'none') [40 50 0]

Apr 05 10:49:33 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 2 of 5 (Device Configure) successful.

Apr 05 10:49:33 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 2 of 5 (Device Configure) complete.

Apr 05 10:49:33 testvm07002 NetworkManager[17560]: <info> Activation (enp0s3) Stage 3 of 5 (IP Configure Start) scheduled.

Apr 05 10:49:33 testvm07002 NetworkManager[17560]: <info> Activation (enp0s8) Stage 3 of 5 (IP Configure Start) scheduled.

Apr 05 10:49:33 testvm07002 NetworkManager[17560]: <info> Activation (enp0s9) Stage 3 of 5 (IP Configure Start) scheduled.

Apr 05 10:49:33 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 3 of 5 (IP Configure Start) scheduled.

Apr 05 10:49:34 testvm07002 NetworkManager[17560]: <info> Activation (enp0s3) Stage 3 of 5 (IP Configure Start) started...

Apr 05 10:49:34 testvm07002 NetworkManager[17560]: <info> (enp0s3): device state change: config -> ip-config (reason 'none') [50 70 0]

Apr 05 10:49:34 testvm07002 NetworkManager[17560]: <info> Activation (enp0s3) Stage 5 of 5 (IPv4 Configure Commit) scheduled...

Apr 05 10:49:34 testvm07002 NetworkManager[17560]: <info> Activation (enp0s3) Stage 5 of 5 (IPv6 Commit) scheduled...

Apr 05 10:49:34 testvm07002 NetworkManager[17560]: <info> Activation (enp0s3) Stage 3 of 5 (IP Configure Start) complete.

Apr 05 10:49:34 testvm07002 NetworkManager[17560]: <info> Activation (enp0s8) Stage 3 of 5 (IP Configure Start) started...

Apr 05 10:49:34 testvm07002 NetworkManager[17560]: <info> (enp0s8): device state change: config -> ip-config (reason 'none') [50 70 0]

Apr 05 10:49:34 testvm07002 NetworkManager[17560]: <info> Activation (enp0s8) Stage 5 of 5 (IPv4 Configure Commit) scheduled...

Apr 05 10:49:34 testvm07002 NetworkManager[17560]: <info> Activation (enp0s8) Stage 5 of 5 (IPv6 Commit) scheduled...

Apr 05 10:49:34 testvm07002 NetworkManager[17560]: <info> Activation (enp0s8) Stage 3 of 5 (IP Configure Start) complete.

Apr 05 10:49:34 testvm07002 NetworkManager[17560]: <info> Activation (enp0s9) Stage 3 of 5 (IP Configure Start) started...

Apr 05 10:49:34 testvm07002 NetworkManager[17560]: <info> (enp0s9): device state change: config -> ip-config (reason 'none') [50 70 0]

Apr 05 10:49:34 testvm07002 NetworkManager[17560]: <info> Activation (enp0s9) Beginning DHCPv4 transaction (timeout in 45 seconds)

Apr 05 10:49:35 testvm07002 NetworkManager[17560]: <info> dhclient started with pid 17604

Apr 05 10:49:35 testvm07002 NetworkManager[17560]: <info> Activation (enp0s9) Stage 3 of 5 (IP Configure Start) complete.

Apr 05 10:49:35 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 3 of 5 (IP Configure Start) started...

Apr 05 10:49:35 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: config -> ip-config (reason 'none') [50 70 0]

Apr 05 10:49:36 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Beginning DHCPv4 transaction (timeout in 45 seconds)

Apr 05 10:49:37 testvm07002 NetworkManager[17560]: <info> dhclient started with pid 17606

Apr 05 10:49:37 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 5 of 5 (IPv6 Commit) scheduled...

Apr 05 10:49:37 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 3 of 5 (IP Configure Start) complete.

Apr 05 10:49:37 testvm07002 NetworkManager[17560]: <info> Activation (enp0s3) Stage 5 of 5 (IPv4 Commit) started...

Apr 05 10:49:38 testvm07002 NetworkManager[17560]: <info> (enp0s3): device state change: ip-config -> ip-check (reason 'none') [70 80 0]

Apr 05 10:49:38 testvm07002 NetworkManager[17560]: <info> Activation (enp0s3) Stage 5 of 5 (IPv4 Commit) complete.

Apr 05 10:49:38 testvm07002 NetworkManager[17560]: <info> Activation (enp0s3) Stage 5 of 5 (IPv6 Commit) started...

Apr 05 10:49:39 testvm07002 NetworkManager[17560]: <info> Activation (enp0s3) Stage 5 of 5 (IPv6 Commit) complete.

Apr 05 10:49:39 testvm07002 NetworkManager[17560]: <info> Activation (enp0s8) Stage 5 of 5 (IPv4 Commit) started...

Apr 05 10:49:40 testvm07002 NetworkManager[17560]: <info> (enp0s8): device state change: ip-config -> ip-check (reason 'none') [70 80 0]

Apr 05 10:49:40 testvm07002 NetworkManager[17560]: <info> Activation (enp0s8) Stage 5 of 5 (IPv4 Commit) complete.

Apr 05 10:49:40 testvm07002 NetworkManager[17560]: <info> Activation (enp0s8) Stage 5 of 5 (IPv6 Commit) started...

Apr 05 10:49:40 testvm07002 NetworkManager[17560]: <info> Activation (enp0s8) Stage 5 of 5 (IPv6 Commit) complete.

Apr 05 10:49:41 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 5 of 5 (IPv6 Commit) started...

Apr 05 10:49:41 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: ip-config -> ip-check (reason 'none') [70 80 0]

Apr 05 10:49:41 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 5 of 5 (IPv6 Commit) complete.

Apr 05 10:49:43 testvm07002 dhclient[17604]: Internet Systems Consortium DHCP Client 4.2.5

Apr 05 10:49:43 testvm07002 dhclient[17604]: Copyright 2004-2013 Internet Systems Consortium.

Apr 05 10:49:43 testvm07002 dhclient[17604]: All rights reserved.

Apr 05 10:49:43 testvm07002 dhclient[17604]: For info, please visit https://www.isc.org/software/dhcp/

Apr 05 10:49:43 testvm07002 dhclient[17604]: Apr 05 10:49:43 testvm07002 NetworkManager[17560]: <info> (enp0s3): device state change: ip-check -> secondaries (reason 'none') [80 90 0]

Apr 05 10:49:43 testvm07002 NetworkManager[17560]: <info> (enp0s8): device state change: ip-check -> secondaries (reason 'none') [80 90 0]

Apr 05 10:49:43 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: ip-check -> secondaries (reason 'none') [80 90 0]

Apr 05 10:49:44 testvm07002 NetworkManager[17560]: <info> (enp0s3): device state change: secondaries -> activated (reason 'none') [90 100 0]

Apr 05 10:49:44 testvm07002 NetworkManager[17560]: <info> NetworkManager state is now CONNECTED_LOCAL

Apr 05 10:49:44 testvm07002 NetworkManager[17560]: <info> Policy set 'enp0s3' (enp0s3) as default for IPv4 routing and DNS.

Apr 05 10:49:44 testvm07002 NetworkManager[17560]: <info> Activation (enp0s3) successful, device activated.

Apr 05 10:49:45 testvm07002 dbus[550]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'

Apr 05 10:49:45 testvm07002 NetworkManager[17560]: <info> (enp0s8): device state change: secondaries -> activated (reason 'none') [90 100 0]

Apr 05 10:49:45 testvm07002 NetworkManager[17560]: <info> NetworkManager state is now CONNECTED_GLOBAL

Apr 05 10:49:45 testvm07002 NetworkManager[17560]: <info> Activation (enp0s8) successful, device activated.

Apr 05 10:49:45 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: secondaries -> activated (reason 'none') [90 100 0]

Apr 05 10:49:45 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) successful, device activated.

Apr 05 10:49:46 testvm07002 dhclient[17606]: Internet Systems Consortium DHCP Client 4.2.5

Apr 05 10:49:46 testvm07002 dhclient[17606]: Copyright 2004-2013 Internet Systems Consortium.

Apr 05 10:49:46 testvm07002 dhclient[17606]: All rights reserved.

Apr 05 10:49:46 testvm07002 dhclient[17606]: For info, please visit https://www.isc.org/software/dhcp/

Apr 05 10:49:46 testvm07002 dhclient[17606]: Apr 05 10:49:47 testvm07002 dhclient[17604]: Listening on LPF/enp0s9/08:00:27:b6:50:f3

Apr 05 10:49:47 testvm07002 dhclient[17604]: Sending on   LPF/enp0s9/08:00:27:b6:50:f3

Apr 05 10:49:47 testvm07002 NetworkManager[17560]: <info> (enp0s9): DHCPv4 state changed nbi -> preinit

Apr 05 10:49:47 testvm07002 dhclient[17604]: Sending on   Socket/fallback

Apr 05 10:49:47 testvm07002 dhclient[17604]: DHCPREQUEST on enp0s9 to 255.255.255.255 port 67 (xid=0x3f47d70b)

Apr 05 10:49:47 testvm07002 dhclient[17604]: DHCPACK from 192.168.248.200 (xid=0x3f47d70b)

Apr 05 10:49:49 testvm07002 NetworkManager[17560]: Internet Systems Consortium DHCP Client 4.2.5

Apr 05 10:49:49 testvm07002 NetworkManager[17560]: Copyright 2004-2013 Internet Systems Consortium.

Apr 05 10:49:49 testvm07002 NetworkManager[17560]: All rights reserved.

Apr 05 10:49:50 testvm07002 NetworkManager[17560]: For info, please visit https://www.isc.org/software/dhcp/

Apr 05 10:49:49 testvm07002 dhclient[17606]: Listening on LPF/enp0s10/08:00:27:94:3e:02

Apr 05 10:49:49 testvm07002 dhclient[17606]: Sending on   LPF/enp0s10/08:00:27:94:3e:02

Apr 05 10:49:49 testvm07002 dhclient[17606]: Sending on   Socket/fallback

Apr 05 10:49:49 testvm07002 dhclient[17606]: DHCPDISCOVER on enp0s10 to 255.255.255.255 port 67 interval 3 (xid=0x404cd379)

Apr 05 10:49:49 testvm07002 dhclient[17606]: DHCPREQUEST on enp0s10 to 255.255.255.255 port 67 (xid=0x404cd379)

Apr 05 10:49:49 testvm07002 dhclient[17606]: DHCPOFFER from 192.168.50.3

Apr 05 10:49:49 testvm07002 NetworkManager[17560]: <info> (enp0s10): DHCPv4 state changed nbi -> preinit

Apr 05 10:49:49 testvm07002 dhclient[17606]: DHCPACK from 192.168.50.3 (xid=0x404cd379)

Apr 05 10:49:50 testvm07002 NetworkManager[17560]: <info> (enp0s9): DHCPv4 state changed preinit -> reboot

Apr 05 10:49:50 testvm07002 NetworkManager[17560]: <info>   address 192.168.248.202

Apr 05 10:49:50 testvm07002 NetworkManager[17560]: <info>   plen 24 (255.255.255.0)

Apr 05 10:49:50 testvm07002 NetworkManager[17560]: <info>   server identifier 192.168.248.200

Apr 05 10:49:50 testvm07002 NetworkManager[17560]: <info>   lease time 1200

Apr 05 10:49:51 testvm07002 dhclient[17604]: bound to 192.168.248.202 -- renewal in 576 seconds.

Apr 05 10:49:51 testvm07002 dbus[550]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'

Apr 05 10:49:51 testvm07002 NetworkManager[17560]: <info> Activation (enp0s9) Stage 5 of 5 (IPv4 Configure Commit) scheduled...

Apr 05 10:49:51 testvm07002 NetworkManager[17560]: <info> Activation (enp0s9) Stage 5 of 5 (IPv4 Commit) started...

Apr 05 10:49:51 testvm07002 NetworkManager[17560]: <info> (enp0s9): device state change: ip-config -> ip-check (reason 'none') [70 80 0]

Apr 05 10:49:51 testvm07002 NetworkManager[17560]: <info> Activation (enp0s9) Stage 5 of 5 (IPv4 Commit) complete.

Apr 05 10:49:52 testvm07002 NetworkManager[17560]: <info> (enp0s9): device state change: ip-check -> secondaries (reason 'none') [80 90 0]

Apr 05 10:49:54 testvm07002 NetworkManager[17560]: <info> (enp0s10): DHCPv4 state changed preinit -> bound

Apr 05 10:49:54 testvm07002 dhclient[17606]: bound to 192.168.50.6 -- renewal in 474 seconds.

Apr 05 10:49:55 testvm07002 NetworkManager[17560]: <info>   address 192.168.50.6

Apr 05 10:49:55 testvm07002 NetworkManager[17560]: <info>   plen 24 (255.255.255.0)

Apr 05 10:49:55 testvm07002 NetworkManager[17560]: <info>   gateway 192.168.50.1

Apr 05 10:49:55 testvm07002 NetworkManager[17560]: <info>   server identifier 192.168.50.3

Apr 05 10:49:55 testvm07002 NetworkManager[17560]: <info>   lease time 1200

Apr 05 10:49:55 testvm07002 NetworkManager[17560]: <info>   nameserver '10.66.9.204'

Apr 05 10:49:55 testvm07002 NetworkManager[17560]: <info>   nameserver '10.66.15.201'

Apr 05 10:49:55 testvm07002 NetworkManager[17560]: <info>   domain name 'in.ril.com'

Apr 05 10:49:55 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 5 of 5 (IPv4 Configure Commit) scheduled...

Apr 05 10:49:55 testvm07002 nm-dispatcher.action[17616]: Script '/etc/NetworkManager/dispatcher.d/00-netreport' took too long; killing it.

Apr 05 10:49:56 testvm07002 nm-dispatcher.action[17616]: Script '/etc/NetworkManager/dispatcher.d/00-netreport' took too long; killing it.

Apr 05 10:49:57 testvm07002 nm-dispatcher.action[17616]: Script '/etc/NetworkManager/dispatcher.d/00-netreport' took too long; killing it.

Apr 05 10:49:59 testvm07002 nm-dispatcher.action[17616]: Script '/etc/NetworkManager/dispatcher.d/11-dhclient' took too long; killing it.

Apr 05 10:49:59 testvm07002 NetworkManager[17560]: <warn> Dispatcher script "/etc/NetworkManager/dispatcher.d/00-netreport" failed with timed out: Script '/etc/NetworkManager/dispatcher.d/00-netreport' timed out.

Apr 05 10:50:00 testvm07002 NetworkManager[17560]: <warn> Dispatcher script "/etc/NetworkManager/dispatcher.d/11-dhclient" failed with timed out: Script '/etc/NetworkManager/dispatcher.d/11-dhclient' timed out.

Apr 05 10:50:00 testvm07002 NetworkManager[17560]: <info> (enp0s9): device state change: secondaries -> activated (reason 'none') [90 100 0]

Apr 05 10:50:00 testvm07002 nm-dispatcher.action[17616]: Script '/etc/NetworkManager/dispatcher.d/11-dhclient' took too long; killing it.

Apr 05 10:50:01 testvm07002 NetworkManager[17560]: <info> Activation (enp0s9) successful, device activated.

Apr 05 10:50:02 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 5 of 5 (IPv4 Commit) started...

Apr 05 10:50:03 testvm07002 dbus-daemon[550]: dbus[550]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'

Apr 05 10:50:03 testvm07002 dbus-daemon[550]: dbus[550]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'

Apr 05 10:49:45 testvm07002 systemd[1]: Starting Network Manager Script Dispatcher Service...

Apr 05 10:49:51 testvm07002 systemd[1]: Started Network Manager Script Dispatcher Service.

Apr 05 10:50:04 testvm07002 NetworkManager[17560]: Internet Systems Consortium DHCP Client 4.2.5

Apr 05 10:50:04 testvm07002 NetworkManager[17560]: Copyright 2004-2013 Internet Systems Consortium.

Apr 05 10:50:05 testvm07002 NetworkManager[17560]: All rights reserved.

Apr 05 10:50:05 testvm07002 NetworkManager[17560]: For info, please visit https://www.isc.org/software/dhcp/

Apr 05 10:50:03 testvm07002 nm-dispatcher.action[17616]: Script '/etc/NetworkManager/dispatcher.d/11-dhclient' took too long; killing it.

Apr 05 10:50:03 testvm07002 NetworkManager[17560]: <info> startup complete

Apr 05 10:50:03 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 5 of 5 (IPv4 Commit) complete.

Apr 05 10:50:03 testvm07002 NetworkManager[17560]: <warn> Dispatcher script "/etc/NetworkManager/dispatcher.d/00-netreport" failed with timed out: Script '/etc/NetworkManager/dispatcher.d/00-netreport' timed out.

Apr 05 10:50:03 testvm07002 NetworkManager[17560]: <warn> Dispatcher script "/etc/NetworkManager/dispatcher.d/11-dhclient" failed with timed out: Script '/etc/NetworkManager/dispatcher.d/11-dhclient' timed out.

Apr 05 10:50:04 testvm07002 NetworkManager[17560]: <warn> Dispatcher script "/etc/NetworkManager/dispatcher.d/00-netreport" failed with timed out: Script '/etc/NetworkManager/dispatcher.d/00-netreport' timed out.

Apr 05 10:50:04 testvm07002 NetworkManager[17560]: <warn> Dispatcher script "/etc/NetworkManager/dispatcher.d/11-dhclient" failed with timed out: Script '/etc/NetworkManager/dispatcher.d/11-dhclient' timed out.

Apr 05 10:50:06 testvm07002 nm-dispatcher.action[17616]: Script '/etc/NetworkManager/dispatcher.d/00-netreport' took too long; killing it.

Apr 05 10:50:05 testvm07002 systemd[1]: Started Network Manager Wait Online.

Apr 05 10:50:07 testvm07002 NetworkManager[17560]: Listening on LPF/enp0s9/08:00:27:b6:50:f3

Apr 05 10:50:07 testvm07002 NetworkManager[17560]: Sending on   LPF/enp0s9/08:00:27:b6:50:f3

Apr 05 10:50:07 testvm07002 NetworkManager[17560]: Sending on   Socket/fallback

Apr 05 10:50:07 testvm07002 NetworkManager[17560]: DHCPREQUEST on enp0s9 to 255.255.255.255 port 67 (xid=0x3f47d70b)

Apr 05 10:50:08 testvm07002 NetworkManager[17560]: DHCPACK from 192.168.248.200 (xid=0x3f47d70b)

Apr 05 10:50:08 testvm07002 NetworkManager[17560]: Listening on LPF/enp0s10/08:00:27:94:3e:02

Apr 05 10:50:08 testvm07002 NetworkManager[17560]: Sending on   LPF/enp0s10/08:00:27:94:3e:02

Apr 05 10:50:08 testvm07002 NetworkManager[17560]: Sending on   Socket/fallback

Apr 05 10:50:08 testvm07002 NetworkManager[17560]: DHCPDISCOVER on enp0s10 to 255.255.255.255 port 67 interval 3 (xid=0x404cd379)

Apr 05 10:50:08 testvm07002 NetworkManager[17560]: DHCPREQUEST on enp0s10 to 255.255.255.255 port 67 (xid=0x404cd379)

Apr 05 10:50:08 testvm07002 NetworkManager[17560]: DHCPOFFER from 192.168.50.3

Apr 05 10:50:09 testvm07002 NetworkManager[17560]: DHCPACK from 192.168.50.3 (xid=0x404cd379)

Apr 05 10:50:09 testvm07002 NetworkManager[17560]: bound to 192.168.248.202 -- renewal in 576 seconds.

Apr 05 10:50:08 testvm07002 nm-dispatcher.action[17616]: Script '/etc/NetworkManager/dispatcher.d/00-netreport' took too long; killing it.

Apr 05 10:50:10 testvm07002 NetworkManager[17560]: bound to 192.168.50.6 -- renewal in 474 seconds.

- Below are the logs printed in the journalctl for "ifdown enp0s10", Studying this logs in detail separately would be required,

Apr 05 10:54:40 testvm07002 NetworkManager[17560]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-enp0s10 ...

Apr 05 10:54:40 testvm07002 NetworkManager[17560]: ifcfg-rh:     read connection 'enp0s10'

Apr 05 10:54:40 testvm07002 NetworkManager[17560]: <info> Auto-activating connection 'enp0s10'.

Apr 05 10:54:40 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) starting connection 'enp0s10'

Apr 05 10:54:40 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 1 of 5 (Device Prepare) scheduled...

Apr 05 10:54:40 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 1 of 5 (Device Prepare) started...

Apr 05 10:54:40 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: disconnected -> prepare (reason 'none') [30 40 0]

Apr 05 10:54:40 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 2 of 5 (Device Configure) scheduled...

Apr 05 10:54:40 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 1 of 5 (Device Prepare) complete.

Apr 05 10:54:41 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 2 of 5 (Device Configure) starting...

Apr 05 10:54:41 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: prepare -> config (reason 'none') [40 50 0]

Apr 05 10:54:42 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 2 of 5 (Device Configure) successful.

Apr 05 10:54:42 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 2 of 5 (Device Configure) complete.

Apr 05 10:54:52 testvm07002 NetworkManager[17560]: <warn> (enp0s10) firewall zone add/change failed [6]: (4) Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Apr 05 10:54:52 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 3 of 5 (IP Configure Start) scheduled.

Apr 05 10:54:52 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 3 of 5 (IP Configure Start) started...

Apr 05 10:54:52 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: config -> ip-config (reason 'none') [50 70 0]

Apr 05 10:54:52 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 5 of 5 (IPv4 Configure Commit) scheduled...

Apr 05 10:54:52 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 3 of 5 (IP Configure Start) complete.

Apr 05 10:54:52 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 5 of 5 (IPv4 Commit) started...

Apr 05 10:54:52 testvm07002 avahi-daemon[543]: Joining mDNS multicast group on interface enp0s10.IPv4 with address 192.168.248.184.

Apr 05 10:54:52 testvm07002 avahi-daemon[543]: New relevant interface enp0s10.IPv4 for mDNS.

Apr 05 10:54:52 testvm07002 avahi-daemon[543]: Registering new address record for 192.168.248.184 on enp0s10.IPv4.

Apr 05 10:54:53 testvm07002 avahi-daemon[543]: Registering new address record for fe80::a00:27ff:fe94:3e02 on enp0s10.*.

Apr 05 10:54:54 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: ip-config -> ip-check (reason 'none') [70 80 0]

Apr 05 10:54:55 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 5 of 5 (IPv4 Commit) complete.

Apr 05 10:54:55 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: ip-check -> secondaries (reason 'none') [80 90 0]

Apr 05 10:54:56 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: secondaries -> activated (reason 'none') [90 100 0]

Apr 05 10:54:56 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) successful, device activated.

Apr 05 10:54:56 testvm07002 dbus-daemon[550]: dbus[550]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'

Apr 05 10:54:56 testvm07002 dbus[550]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'

Apr 05 10:54:56 testvm07002 systemd[1]: Starting Network Manager Script Dispatcher Service...

Apr 05 10:54:59 testvm07002 dbus-daemon[550]: dbus[550]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'

Apr 05 10:54:59 testvm07002 dbus[550]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'

Apr 05 10:54:59 testvm07002 systemd[1]: Started Network Manager Script Dispatcher Service.

Apr 05 10:55:00 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: activated -> deactivating (reason 'user-requested') [100 110 39]

Apr 05 10:55:00 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: deactivating -> disconnected (reason 'user-requested') [110 30 39]

Apr 05 10:55:00 testvm07002 NetworkManager[17560]: <info> (enp0s10): deactivating device (reason 'user-requested') [39]

Apr 05 10:55:00 testvm07002 avahi-daemon[543]: Withdrawing address record for fe80::a00:27ff:fe94:3e02 on enp0s10.

Apr 05 10:55:00 testvm07002 avahi-daemon[543]: Withdrawing address record for 192.168.248.184 on enp0s10.

Apr 05 10:55:00 testvm07002 avahi-daemon[543]: Leaving mDNS multicast group on interface enp0s10.IPv4 with address 192.168.248.184.

Apr 05 10:55:00 testvm07002 avahi-daemon[543]: Interface enp0s10.IPv4 no longer relevant for mDNS.

Apr 05 10:55:03 testvm07002 nm-dispatcher.action[17840]: Script '/etc/NetworkManager/dispatcher.d/00-netreport' took too long; killing it.

Apr 05 10:55:05 testvm07002 nm-dispatcher.action[17840]: Script '/etc/NetworkManager/dispatcher.d/00-netreport' took too long; killing it.

- Below are the logs printed in the journalctl for "ifup enp0s10", Studying this logs separately would be required,

Apr 05 10:58:53 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) starting connection 'enp0s10'

Apr 05 10:58:53 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 1 of 5 (Device Prepare) scheduled...

Apr 05 10:58:53 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 1 of 5 (Device Prepare) started...

Apr 05 10:58:53 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: disconnected -> prepare (reason 'none') [30 40 0]

Apr 05 10:58:53 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 2 of 5 (Device Configure) scheduled...

Apr 05 10:58:53 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 1 of 5 (Device Prepare) complete.

Apr 05 10:58:53 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 2 of 5 (Device Configure) starting...

Apr 05 10:58:53 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: prepare -> config (reason 'none') [40 50 0]

Apr 05 10:58:54 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 2 of 5 (Device Configure) successful.

Apr 05 10:58:54 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 2 of 5 (Device Configure) complete.

Apr 05 10:59:00 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 3 of 5 (IP Configure Start) scheduled.

Apr 05 10:59:00 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 3 of 5 (IP Configure Start) started...

Apr 05 10:59:00 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: config -> ip-config (reason 'none') [50 70 0]

Apr 05 10:59:00 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 5 of 5 (IPv4 Configure Commit) scheduled...

Apr 05 10:59:00 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 3 of 5 (IP Configure Start) complete.

Apr 05 10:59:00 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 5 of 5 (IPv4 Commit) started...

Apr 05 10:59:00 testvm07002 avahi-daemon[543]: Joining mDNS multicast group on interface enp0s10.IPv4 with address 192.168.248.184.

Apr 05 10:59:00 testvm07002 avahi-daemon[543]: New relevant interface enp0s10.IPv4 for mDNS.

Apr 05 10:59:00 testvm07002 avahi-daemon[543]: Registering new address record for 192.168.248.184 on enp0s10.IPv4.

Apr 05 10:59:01 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: ip-config -> ip-check (reason 'none') [70 80 0]

Apr 05 10:59:01 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) Stage 5 of 5 (IPv4 Commit) complete.

Apr 05 10:59:02 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: ip-check -> secondaries (reason 'none') [80 90 0]

Apr 05 10:59:02 testvm07002 avahi-daemon[543]: Registering new address record for fe80::a00:27ff:fe94:3e02 on enp0s10.*.

Apr 05 10:59:02 testvm07002 NetworkManager[17560]: <info> (enp0s10): device state change: secondaries -> activated (reason 'none') [90 100 0]

Apr 05 10:59:02 testvm07002 NetworkManager[17560]: <info> Activation (enp0s10) successful, device activated.

Apr 05 10:59:03 testvm07002 dbus-daemon[550]: dbus[550]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'

Apr 05 10:59:03 testvm07002 dbus[550]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'

Apr 05 10:59:03 testvm07002 systemd[1]: Starting Network Manager Script Dispatcher Service...

Apr 05 10:59:05 testvm07002 dbus-daemon[550]: dbus[550]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'

Apr 05 10:59:05 testvm07002 dbus[550]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'

Apr 05 10:59:05 testvm07002 systemd[1]: Started Network Manager Script Dispatcher Service.

- AS per RHEL 7 documentation, flow for updating “NetworkManager Daemon” with changes in file would be as below,

- Modify ifcfg-interface file in /etc/sysconfig-network-scripts folder

- Reload complete list of interface profiles by scanning for changes in those files using nmcli command.

nmcli connection reload

- Reload only one interface profile to apply modifications in it using nmcli command.

nmcli connection load /etc/sysconfig/network-scripts/ifcfg -ifname

- No need to NetworkManager daemon restart, Changes made using tools such as n mcli do not require a reload but do require the associated interface to be put down and then up again. Same can be done using nmcli command itself.

nmcli dev disconnect interface-name

- Changes ifcfg-interface file in /etc/sysconfig-network-scripts folder will be reflected.

- Below is the detailed example, Have a look on existing configuration of interface,

[root@testvm07002 network-scripts]# cat ifcfg-enp0s10

TYPE=Ethernet

NAME=enp0s10

BOOTPROTO=static

HWADDR=08:00:27:94:3E:02

ONBOOT=yes

IPADDR=192.168.248.184

NETMASK=255.255.255.0

GATEWAY=192.168.248.1

IPV6INIT=no

[root@testvm07002 network-scripts]# ip a sh dev enp0s10

5: enp0s10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP

    link/ether 08:00:27:94:3e:02 brd ff:ff:ff:ff:ff:ff

    inet 192.168.248.184/24 brd 192.168.248.255 scope global enp0s10

       valid_lft forever preferred_lft forever

    inet6 fe80::a00:27ff:fe94:3e02/64 scope link

       valid_lft forever preferred_lft forever

- Now modify configuration of interface as below,

[root@testvm07002 network-scripts]# vi ifcfg-enp0s10

[root@testvm07002 network-scripts]# cat ifcfg-enp0s10

TYPE=Ethernet

BOOTPROTO=dhcp

DEFROUTE=yes

IPV4_FAILURE_FATAL=no

IPV6INIT=yes

IPV6_AUTOCONF=yes

IPV6_DEFROUTE=yes

IPV6_FAILURE_FATAL=no

NAME=enp0s10-connection

UUID=4474b5b1-e576-45bd-babb-c3ce22d41166

ONBOOT=yes

HWADDR=08:00:27:94:3E:02

PEERDNS=yes

PEERROUTES=yes

IPV6_PEERDNS=yes

IPV6_PEERROUTES=yes

- Now we will need to disconnect and reconnect the interface using command line tools as the command line tools that will be used will directly communicate changes to NetwormManager Daemon,

[root@testvm07002 network-scripts]# nmcli dev disconnect enp0s10

[root@testvm07002 network-scripts]# ip a sh dev enp0s10

5: enp0s10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000

    link/ether 08:00:27:94:3e:02 brd ff:ff:ff:ff:ff:ff

[root@testvm07002 network-scripts]# nmcli dev connect enp0s10

Device 'enp0s10' successfully activated with '4474b5b1-e576-45bd-babb-c3ce22d41166'.

[root@testvm07002 network-scripts]# ip a sh dev enp0s10

5: enp0s10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000

    link/ether 08:00:27:94:3e:02 brd ff:ff:ff:ff:ff:ff

    inet 192.168.50.6/24 brd 192.168.50.255 scope global dynamic enp0s10

       valid_lft 1200sec preferred_lft 1200sec

    inet6 fe80::a00:27ff:fe94:3e02/64 scope link

       valid_lft forever preferred_lft forever

- On bootup, /etc/init.d/network reads through all the ifcfg files and for each one that has “ONBOOT = yes”, it checks whether NetworkManager is already starting the DEVICE from that ifcfg file. If NetworkManager is starting that device or has already started it, nothing more is done for that file, and the next “ONBOOT = yes” file is checked. If NetworkManager is not yet starting that device then the initscripts will continue with their traditional behavior and call ifup for that ifcfg file. The end result is that any ifcfg file that has “ONBOOT = yes” is expected to be started on system bootup, either by NetworkManager or by the initscripts.

- It is recommended not to store backup i fcfg files in the same location as the live ones. The script literally does ifcfg -* with an exclude only for these extensions: . o l d , . o ri g , . rpmnew, . rpmo ri g , and . rpmsave. The best way is not to store backup files anywhere within the /etc/ directory.

Note:- Have a look on below file /usr/share/doc/initscripts-version/sysconfig.txt

Back To Top

Home