<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:59:18 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-6333] Router&apos;s network status turns to &quot;down&quot; if it has different &quot;accecpt_port&quot; with client/server</title>
                <link>https://jira.whamcloud.com/browse/LU-6333</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Router&apos;s network status turns to &quot;down&quot; if it has different &quot;accecpt_port&quot; with client(or server)&lt;/p&gt;

&lt;p&gt;Here is the test steps:&lt;br/&gt;
1. successfully setup router with 3 different interfaces, accept_port=7988 ,the status shows the networks are all up; &lt;br/&gt;
2. load lnet on client which has the default accept_port 988,  also has router mentioned in the configure file&lt;br/&gt;
3. on client side, do lctl ping, then check the router network status and found it was down.&lt;/p&gt;

&lt;p&gt;on router:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;[root@eagle-54vm5 tests]# modprobe lnet
LNet: HW CPU cores: 1, npartitions: 1
alg: No test for adler32 (adler32-zlib)
alg: No test for crc32 (crc32-table)
[root@eagle-54vm5 tests]# lctl network up
LNet: Added LNI 192.168.200.82@tcp [8/256/0/180]
LNet: Added LNI 192.168.201.101@tcp1 [8/256/0/180]
LNet: Added LNI 192.168.202.116@tcp2 [8/256/0/180]
LNet: Accept secure, port 7988
LNET configured
[root@eagle-54vm5 tests]# lnetctl net show
net:
    - net: lo
      nid: 0@lo
      status: up
    - net: tcp
      nid: 192.168.200.82@tcp
      status: up
      interfaces:
          0: eth1
    - net: tcp1
      nid: 192.168.201.101@tcp1
      status: up
      interfaces:
          0: eth2
    - net: tcp2
      nid: 192.168.202.116@tcp2
      status: up
      interfaces:
          0: eth3
[root@eagle-54vm5 tests]# lnetctl net show
net:
    - net: lo
      nid: 0@lo
      status: up
    - net: tcp
      nid: 192.168.200.82@tcp
      status: up
      interfaces:
          0: eth1
    - net: tcp1
      nid: 192.168.201.101@tcp1
      status: down
      interfaces:
          0: eth2
    - net: tcp2
      nid: 192.168.202.116@tcp2
      status: down
      interfaces:
          0: eth3
[root@eagle-54vm5 tests]# 
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;on client:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;[root@eagle-54vm3 tests]# more /etc/modprobe.d/lustre-lnet-client1.conf 
alias eth1 e1000e
alias scsi_hostadapter ahci
alias eth0 e1000e
alias ib0 ib_ipoib

#options lnet accept=all networks=&quot;tcp1(eth1)&quot; accept_port=7988 routes=&quot;tcp0 192
.168.201.101@tcp1&quot; config_on_load=1
options lnet accept=all networks=&quot;tcp1(eth1)&quot; routes=&quot;tcp0 192.168.201.101@tcp1&quot; config_on_load=1

[root@eagle-54vm3 tests]# modprobe lnet
LNet: HW CPU cores: 1, npartitions: 1
alg: No test for adler32 (adler32-zlib)
alg: No test for crc32 (crc32-table)

[root@eagle-54vm3 tests]# 
[root@eagle-54vm3 tests]# LNet: Added LNI 192.168.201.180@tcp1 [8/256/0/180]
LNet: Accept all, port 988
[root@eagle-54vm3 tests]# lnetctl net show
net:
    - net: lo
      nid: 0@lo
      status: up
    - net: tcp1
      nid: 192.168.201.180@tcp1
      status: up
      interfaces:
          0: eth1
[root@eagle-54vm3 tests]# lnetctl route show
route:
    - net: tcp
      gateway: 192.168.201.101@tcp1
[root@eagle-54vm3 tests]# lnetctl route show -v
route:
    - net: tcp
      gateway: 192.168.201.101@tcp1
      hop: 1
      priority: 0
      state: down
[root@eagle-54vm3 tests]# lctl ping 192.168.201.101@tcp1
failed to ping 192.168.201.101@tcp1: Input/output error
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
</description>
                <environment>lustre-b2_7 build # 29</environment>
        <key id="28974">LU-6333</key>
            <summary>Router&apos;s network status turns to &quot;down&quot; if it has different &quot;accecpt_port&quot; with client/server</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="1" iconUrl="https://jira.whamcloud.com/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="wc-triage">WC Triage</assignee>
                                    <reporter username="sarah">Sarah Liu</reporter>
                        <labels>
                    </labels>
                <created>Thu, 5 Mar 2015 07:26:43 +0000</created>
                <updated>Fri, 6 Mar 2015 17:27:17 +0000</updated>
                                            <version>Lustre 2.7.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                            <comments>
                            <comment id="108912" author="isaac" created="Thu, 5 Mar 2015 17:24:41 +0000"  >&lt;p&gt;I don&apos;t think this is a bug. LNet doesn&apos;t negotiate accept_port settings over the wire. It&apos;s the admin&apos;s responsibility to set it up consistently. It&apos;s impossible to negotiate it without using 3rd party services at well-known port.&lt;/p&gt;</comment>
                            <comment id="108985" author="sarah" created="Thu, 5 Mar 2015 22:16:58 +0000"  >&lt;p&gt;I understand that the admin should keep the port consistently, but if adding a new client into an existing network  with unmatched port will cause the remote router down,  it doesn&apos;t make sense to me.&lt;/p&gt;</comment>
                            <comment id="109078" author="isaac" created="Fri, 6 Mar 2015 17:27:17 +0000"  >&lt;p&gt;If that is the case, it does not make any sense. But are you sure it was the client with unmatched accept_port that &lt;b&gt;caused&lt;/b&gt; the router to mark its interfaces down? In other words, the router interfaces would stay in &quot;up&quot; state as long as there&apos;s no client with unmatched accept_port?&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzx7pr:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>17733</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10060" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Severity</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10022"><![CDATA[3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>