<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 12/30/20 12:09, Vijay Khemka wrote:<br>
    </div>
    <blockquote type="cite" cite="mid:CAJTGxZESn=fr4OxP70JNAM0hnmR5vE7xC11ScbfbdeNiwd5bgA@mail.gmail.com">
      
      <div dir="ltr"><br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Wed, Dec 23, 2020 at 7:59
            AM Thu Nguyen <<a href="mailto:thu@amperemail.onmicrosoft.com" moz-do-not-send="true">thu@amperemail.onmicrosoft.com</a>>
            wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">Hi All,<br>
            <br>
            <br>
            I'm verifying NCSI with my Mt.Jade platform.<br>
            <br>
            In Mt.Jade platform, we have the shared NIC in eth0
            interface and <br>
            dedicated RGMII in eth1 interface.<br>
            <br>
            I used below steps to enable NC-SI in Mt.Jade.<br>
            <br>
            1. Add definition in DTS for MAC0:<br>
            <br>
            &mac0 {<br>
                   status = "disabled";<br>
                   status = "okay";<br>
                   pinctrl-names = "default";<br>
                   pinctrl-0 = <&pinctrl_rmii1_default>;<br>
                   clocks = <&syscon ASPEED_CLK_GATE_MAC1CLK>,<br>
                            <&syscon ASPEED_CLK_MAC1RCLK>;<br>
                   clock-names = "MACCLK", "RCLK";<br>
                   use-ncsi;<br>
            };<br>
            <br>
            2. Add build configure to enable OEM Command to get MAC for
            NCSI.<br>
            <br>
            CONFIG_NCSI_OEM_CMD_GET_MAC=y<br>
            <br>
            After these steps, My system can detect OCP card, can get
            MACs and both <br>
            eth0 and eth1 interfaces are up.<br>
            <br>
            I can access BMC Web use both ip of eth0 or eth1. The same
            for Redfish.<br>
            <br>
            BUT I can only use ipmitool with eth0. Ipmitool command not
            work with <br>
            eth1 interface.<br>
            <br>
            <br>
            Check the setting of phosphor-ipmid-net in<br>
            <br>
meta-phosphor/recipes-phosphor/ipmi/phosphor-ipmi-config/channel_access.json<br>
            <br>
meta-phosphor/recipes-phosphor/ipmi/phosphor-ipmi-config/channel_config.json<br>
          </blockquote>
          <div>You have to configure in this file for eth1 as well. <br>
          </div>
        </div>
      </div>
    </blockquote>
    <p>Because these files in
      meta-phosphor/recipes-phosphor/ipmi/phosphor-ipmi-config/ are
      already configured for eth1.</p>
    <p>So I don't think I need configure "channel_config.json".</p>
    <p>I missed below setting in phosphor-ipmi-net_%.bbappend<br>
    </p>
    <p>+ALT_RMCPP_IFACE = "eth1"<br>
      +SYSTEMD_SERVICE_${PN} += " \<br>
      +        ${PN}@${ALT_RMCPP_IFACE}.service \<br>
      +        ${PN}@${ALT_RMCPP_IFACE}.socket \</p>
    <p>This cause IPMId also listen in eth1.<br>
    </p>
    <blockquote type="cite" cite="mid:CAJTGxZESn=fr4OxP70JNAM0hnmR5vE7xC11ScbfbdeNiwd5bgA@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <br>
            I can see that ipmid is configured to listen on both
            interface eth0 and <br>
            eth1.<br>
          </blockquote>
          <div>How do you make sure it is listening on both interface </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <br>
            Do I miss any configuration here?<br>
            <br>
            <br>
            Check the journal log, I saw some errors and warning from
            NCSI:<br>
            <br>
            Dec 23 10:14:50 mtjade kernel: ftgmac100 1e660000.ethernet
            eth0: NCSI: <br>
            Handler for packet type 0x82 returned -19<br>
            <br>
            Dec 23 10:15:05 mtjade kernel: ftgmac100 1e660000.ethernet
            eth0: NCSI: <br>
            'bad' packet ignored for type 0x8b<br>
            Dec 23 10:15:05 mtjade kernel: ftgmac100 1e660000.ethernet
            eth0: NCSI: <br>
            'bad' packet ignored for type 0x8b<br>
            Dec 23 10:15:05 mtjade kernel: ftgmac100 1e660000.ethernet
            eth0: NCSI: <br>
            'bad' packet ignored for type 0x8b<br>
            Dec 23 10:15:05 mtjade kernel: ftgmac100 1e660000.ethernet
            eth0: NCSI: <br>
            'bad' packet ignored for type 0x8b<br>
            <br>
            Because NC-SI interface is up, so I just ignore these
            errors.<br>
          </blockquote>
          <div><br>
          </div>
          <div>These errors can be ignored, it doesn't harm in any
            communication. We need </div>
          <div>to fix this  into the kernel.</div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <br>
            <br>
            Regards.<br>
            <br>
            Thu Nguyen.<br>
            <br>
            <br>
            <br>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <p>Regards.</p>
    <p>Thu Nguyen.<br>
    </p>
    <p><br>
    </p>
  </body>
</html>