Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

XG430 10G Flexi Port link not coming up - replacement of the module

During HA-Rebuild and Upgrade to 19.5.1 I noticed a log in System logs: "PortA4 up" on the peer node at a time when it was unexpected.

I then noticed on the physical interface, that the LED of that Port were off while the other 3 were blinking.

It is 10G Copper with SFP Plus Cable.

I replaced the cable with the same result. After 15 or more minutes I checked the device again and the port was up and running - as can be seen from the below output and screenshots.

I checked the Troubleshooting tests for network issues, but I found no log information or debug procedere else than this one: https://support.sophos.com/support/s/article/KB-000036345?language=en_US

Are there useful logs to analyze this?

This was the port status when it was off:

PortA3    Link encap:Ethernet  HWaddr C8:4F:86:FC:00:0D  
          inet6 addr: fe80::ca4f:86ff:fefc:d/64 Scope:Link
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:772884 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1243396 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:447511125 (426.7 MiB)  TX bytes:782974630 (746.7 MiB)

PortA4    Link encap:Ethernet  HWaddr C8:4F:86:FC:00:0D  
          inet6 addr: fe80::ca4f:86ff:fefc:e/64 Scope:Link
          UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

and than when it was on.

--

XG430_WP02_SFOS 19.5.1 MR-1-Build278 HA-Primary# ifconfig PortA4
PortA4    Link encap:Ethernet  HWaddr C8:4F:86:FC:00:0D
          inet6 addr: fe80::ca4f:86ff:fefc:e/64 Scope:Link
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:7259882 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8158434 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5353399207 (4.9 GiB)  TX bytes:7343072503 (6.8 GiB)

XG430_WP02_SFOS 19.5.1 MR-1-Build278 HA-Primary# ifconfig PortA3
PortA3    Link encap:Ethernet  HWaddr C8:4F:86:FC:00:0D
          inet6 addr: fe80::ca4f:86ff:fefc:d/64 Scope:Link
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:9608423 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6768176 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7102495310 (6.6 GiB)  TX bytes:1499533574 (1.3 GiB)

The 4 Ports are in a LACP LAG.

That is the problematic port:
XG430_WP02_SFOS 19.5.1 MR-1-Build278 HA-Primary# ethtool PortA4
Settings for PortA4:
        Supported ports: [ FIBRE ]
        Supported link modes:   10000baseT/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: No
        Supported FEC modes: Not reported
        Advertised link modes:  10000baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: No
        Advertised FEC modes: Not reported
        Speed: 10000Mb/s
        Duplex: Full
        Port: Direct Attach Copper
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: off
        Supports Wake-on: g
        Wake-on: g
        Current message level: 0x0000000f (15)
                               drv probe link timer
        Link detected: yes

One other Port:

XG430_WP02_SFOS 19.5.1 MR-1-Build278 HA-Primary# ethtool PortA3
Settings for PortA3:
        Supported ports: [ FIBRE ]
        Supported link modes:   10000baseT/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: No
        Supported FEC modes: Not reported
        Advertised link modes:  10000baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: No
        Advertised FEC modes: Not reported
        Speed: 10000Mb/s
        Duplex: Full
        Port: Direct Attach Copper
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: off
        Supports Wake-on: g
        Wake-on: g
        Current message level: 0x0000000f (15)
                               drv probe link timer
        Link detected: yes

--



This thread was automatically locked due to age.
Parents Reply Children
  • the job was to replace it. that brings more questions than just adding it, due to existing config on it. That is the undocumented part.

    I found, the new module has much more recent firmware. I supposed, the module is getting updatey by SFOS updates but it seems it isn't.

    old, replaced module:

    ethtool -i PortA4
    driver: i40e
    version: 2.10.19.82
    firmware-version: 5.05 0x800028ac 0.0.0
    expansion-rom-version:
    bus-info: 0000:02:00.3
    supports-statistics: yes
    supports-test: yes
    supports-eeprom-access: yes
    supports-register-dump: yes
    supports-priv-flags: yes

    new module, received in RMA:

    ethtool -i PortA4
    driver: i40e
    version: 2.10.19.82
    firmware-version: 7.20 0x80007a01 0.0.0
    expansion-rom-version:
    bus-info: 0000:02:00.3
    supports-statistics: yes
    supports-test: yes
    supports-eeprom-access: yes
    supports-register-dump: yes
    supports-priv-flags: yes

    Btw, all blue speed LED are working again on the replacement module(s).

    node1

    node2

  • That is a great news, meanwhile I'll check if we any documentation internally !
    Thank you for sharing your steps   cheers !

    Thanks & Regards,
    _______________________________________________________________

    Vivek Jagad | Team Lead, Global Support & Services 

    Log a Support Case | Sophos Service Guide
    Best Practices – Support Case


    Sophos Community | Product Documentation | Sophos Techvids | SMS
    If a post solves your question please use the 'Verify Answer' button.