Results 1 to 4 of 4

Thread: Both LAN Ports show connected but uplink one port

  1. #1

    Both LAN Ports show connected but uplink one port

    Hi,
    I've Supermicro Server board SM-X10DRL-I with Intel E5-2609v3 Processor, 8GB DDR4 Reg RAM and have dual i1210onboard Gigabit LAN Ports.
    Problem is with LAN Ports. These LAN Ports works with SUSE SLES 12SP1 & 12SP3.
    But when I install SUSE SLES for SAP application, it shows both LAN are connected but One LAN ports communicate while another doesn't response. If i unplug the working port and restart the server then second ports starts communication but first port stop responding.

    Needs help

  2. Re: Both LAN Ports show connected but uplink one port

    Hi Zaman,

    welcome to the forums.

    "SUSE SLES for SAP Applications" is ambiguous, which *version* are you trying? "cat /etc/os-release" should provide descriptive output.

    Could you additionally provide the messages from dmesg/syslog/journal regarding these ports (please include those from first NIC initialization after boot, as well as what is reported when you plug/unplug the cables during your test(s)).

    The information from "ip link list", "ethtool <device>" and "ethtool -i <device>" (for both network devices) might be helpful, too.

    Regards,
    J
    From the times when today's "old school" was "new school"

    If you find this post helpful and are logged into the web interface, show your appreciation and click on the star below...

  3. #3

    Re: Both LAN Ports show connected but uplink one port

    Hi Jmozdzen,

    Please find below your required information
    "
    linux-6fyq:~ # cat /etc/os-release
    NAME="SLES"
    VERSION="12-SP3"
    VERSION_ID="12.3"
    PRETTY_NAME="SUSE Linux Enterprise Server 12 SP3"
    ID="sles"
    ANSI_COLOR="0;32"
    CPE_NAME="cpe:/o:suse:sles_sap:12:sp3"


    [ 11.643363] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 11.689166] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
    [ 14.495327] igb 0000:05:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
    [ 14.599122] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 14.623313] igb 0000:06:00.0 eth1: igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
    [ 14.727075] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
    [ 14.739360] NET: Registered protocol family 17
    [ 43.149149] pagecache limit set to 0.Feature is supported only for SLES for SAP appliance
    [ 156.494555] fuse init (API version 7.23)
    [ 755.684595] igb 0000:05:00.0 eth0: igb: eth0 NIC Link is Down
    [ 801.767074] igb 0000:05:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
    [ 821.175577] igb 0000:06:00.0 eth1: igb: eth1 NIC Link is Down
    [ 836.316626] igb 0000:06:00.0 eth1: igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

    linux-6fyq:~ # ip link list
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 0c:c4:7a:72:88:cc brd ff:ff:ff:ff:ff:ff
    3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 0c:c4:7a:72:88:cd brd ff:ff:ff:ff:ff:ff

    linux-6fyq:~ # ethtool eth0
    Settings for eth0:
    Supported ports: [ TP ]
    Supported link modes: 10baseT/Half 10baseT/Full
    100baseT/Half 100baseT/Full
    1000baseT/Full
    Supported pause frame use: Symmetric
    Supports auto-negotiation: Yes
    Advertised link modes: 10baseT/Half 10baseT/Full
    100baseT/Half 100baseT/Full
    1000baseT/Full
    Advertised pause frame use: Symmetric
    Advertised auto-negotiation: Yes
    Speed: 1000Mb/s
    Duplex: Full
    Port: Twisted Pair
    PHYAD: 1
    Transceiver: internal
    Auto-negotiation: on
    MDI-X: off (auto)
    Supports Wake-on: pumbg
    Wake-on: g
    Current message level: 0x00000007 (7)
    drv probe link
    Link detected: yes

    linux-6fyq:~ # ethtool eth1
    Settings for eth1:
    Supported ports: [ TP ]
    Supported link modes: 10baseT/Half 10baseT/Full
    100baseT/Half 100baseT/Full
    1000baseT/Full
    Supported pause frame use: Symmetric
    Supports auto-negotiation: Yes
    Advertised link modes: 10baseT/Half 10baseT/Full
    100baseT/Half 100baseT/Full
    1000baseT/Full
    Advertised pause frame use: Symmetric
    Advertised auto-negotiation: Yes
    Speed: 1000Mb/s
    Duplex: Full
    Port: Twisted Pair
    PHYAD: 1
    Transceiver: internal
    Auto-negotiation: on
    MDI-X: off (auto)
    Supports Wake-on: pumbg
    Wake-on: g
    Current message level: 0x00000007 (7)
    drv probe link
    Link detected: yes

    linux-6fyq:~ # ethtool -i eth0
    driver: igb
    version: 5.4.0-k
    firmware-version: 3.16, 0x800004d7
    expansion-rom-version:
    bus-info: 0000:05:00.0
    supports-statistics: yes
    supports-test: yes
    supports-eeprom-access: yes
    supports-register-dump: yes
    supports-priv-flags: no

    linux-6fyq:~ # ethtool -i eth1
    driver: igb
    version: 5.4.0-k
    firmware-version: 3.16, 0x800004d9
    expansion-rom-version:
    bus-info: 0000:06:00.0
    supports-statistics: yes
    supports-test: yes
    supports-eeprom-access: yes
    supports-register-dump: yes
    supports-priv-flags: no
    "

    Waiting for your positive response & Best regards

    Zaman

  4. Re: Both LAN Ports show connected but uplink one port

    Hi Zaman,

    the output shows that the cards both negotiate successfully, so from a "link layer 2" perspective, they seem to be fine.

    What exactly is it that is not working? You wrote
    But when I install SUSE SLES for SAP application, it shows both LAN are connected but One LAN ports communicate while another doesn't response. If i unplug the working port and restart the server then second ports starts communication but first port stop responding.
    What's it you're doing to confirm "port stop responding"? I guess "ping", but to two distinct addresses (one per port) or a common address?

    Let me take a step back... are you running these ports in a "link aggregation" / bond / port bundle configuration? Any VLANs involved? How's the network configuration of the system, as compared to those "working SLES12SP1/SLES12SP3" configurations?

    Regards,
    J
    From the times when today's "old school" was "new school"

    If you find this post helpful and are logged into the web interface, show your appreciation and click on the star below...

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •