public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: "Liu, Changcheng" <changcheng.liu@intel.com>
To: linux-rdma@vger.kernel.org
Subject: MCX516A-CCAT failed to set ip
Date: Mon, 14 Oct 2019 20:39:11 +0800	[thread overview]
Message-ID: <20191014123911.GA711781@jerryopenix> (raw)

Hi all,
   I’m using MCX516A-CCAT in RHEL-7.6 with kernel 4.19.45.
   The network script always failed to configure the NIC with static ip. There was no problem when using CX314A to get the ip address with the simliar network script.
   Could anyone give me some info to check why the network script failed to set the ip address?

   Detail:
     Network script:
       [rdma@rdmarhel0 network-scripts]$ cat ifcfg-ens801f0
       DEVICE=ens801f0
       BOOTPROTO=static
       HWADDR=24:8a:07:60:90:e1
       IPADDR=192.168.100.101
       NETMASK=255.255.255.0
       ONBOOT=yes

       [rdma@rdmarhel0 network-scripts]$ cat ifcfg-ens801f1
       DEVICE=ens801f1
       BOOTPROTO=static
       HWADDR=24:8a:07:60:90:e0
       IPADDR=173.168.100.101
       NETMASK=255.255.255.0
       ONBOOT=yes

     Restart network command:
       [rdma@rdmarhel0 ~]$ sudo service network restart

     Error output:
       Restarting network (via systemctl):  Job for network.service failed because the control process exited with error code.
       See "systemctl status network.service" and "journalctl -xe" for details.

    Further check:
       [rdma@rdmarhel0 ~]$ systemctl status network.service
       network.service - LSB: Bring up/down networking
          Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
          Active: failed (Result: exit-code) since Mon 2019-10-14 16:43:38 CST; 5min ago
            Docs: man:systemd-sysv-generator(8)
         Process: 20373 ExecStop=/etc/rc.d/init.d/network stop (code=exited, status=0/SUCCESS)
         Process: 26051 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)

       Oct 14 16:43:38 rdmarhel0 network[26051]: RTNETLINK answers: File exists
       Oct 14 16:43:38 rdmarhel0 network[26051]: RTNETLINK answers: File exists
       Oct 14 16:43:38 rdmarhel0 network[26051]: RTNETLINK answers: File exists
       Oct 14 16:43:38 rdmarhel0 network[26051]: RTNETLINK answers: File exists
       Oct 14 16:43:38 rdmarhel0 network[26051]: RTNETLINK answers: File exists
       Oct 14 16:43:38 rdmarhel0 network[26051]: RTNETLINK answers: File exists
       Oct 14 16:43:38 rdmarhel0 systemd[1]: network.service: control process exited, code=exited status=1
       Oct 14 16:43:38 rdmarhel0 systemd[1]: Failed to start LSB: Bring up/down networking.
       Oct 14 16:43:38 rdmarhel0 systemd[1]: Unit network.service entered failed state.
       Oct 14 16:43:38 rdmarhel0 systemd[1]: network.service failed.

    [rdma@rdmarhel0 ~]$ journalctl -xe
       -- Unit network.service has begun starting up.
       Oct 14 16:43:37 rdmarhel0 network[26051]: Bringing up loopback interface:  [  OK  ]
       Oct 14 16:43:37 rdmarhel0 network[26051]: Bringing up interface eno1:  [  OK  ]
       Oct 14 16:43:37 rdmarhel0 network[26051]: Bringing up interface ens785f0:  [  OK  ]
       Oct 14 16:43:37 rdmarhel0 network[26051]: Bringing up interface ens785f1:  [  OK  ]
       Oct 14 16:43:38 rdmarhel0 NetworkManager[14879]: <info>  [1571042618.1158] audit: op="connection-activate" uuid="e9345cc8-be74-0dd5-85a4-8260e310b66b" name="System ens801f0" result="fail" reason="No suitable d
       Oct 14 16:43:38 rdmarhel0 network[26051]: Bringing up interface ens801f0:  Error: Connection activation failed: No suitable device found for this connection.
       Oct 14 16:43:38 rdmarhel0 network[26051]: [FAILED]
       Oct 14 16:43:38 rdmarhel0 network[26051]: Bringing up interface ens801f1:  [  OK  ]
       Oct 14 16:43:38 rdmarhel0 network[26051]: RTNETLINK answers: File exists
       Oct 14 16:43:38 rdmarhel0 network[26051]: RTNETLINK answers: File exists
       Oct 14 16:43:38 rdmarhel0 systemd[1]: network.service: control process exited, code=exited status=1
       Oct 14 16:43:38 rdmarhel0 systemd[1]: Failed to start LSB: Bring up/down networking.
       -- Subject: Unit network.service has failed
       -- Defined-By: systemd
       -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
       -- 
       -- Unit network.service has failed.
       -- 
       -- The result is failed.
       Oct 14 16:43:38 rdmarhel0 systemd[1]: Unit network.service entered failed state.
       Oct 14 16:43:38 rdmarhel0 systemd[1]: network.service failed.
       Oct 14 16:43:38 rdmarhel0 polkitd[14826]: Unregistered Authentication Agent for unix-process:26045:493383 (system bus name :1.338, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-
       Oct 14 16:43:38 rdmarhel0 sudo[26025]: pam_unix(sudo:session): session closed for user root

Regards,
Changcheng

                 reply	other threads:[~2019-10-14 12:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191014123911.GA711781@jerryopenix \
    --to=changcheng.liu@intel.com \
    --cc=linux-rdma@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox