Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-103925

[RFE] The NetworkManager logs do not indicate whether the NIC link down event was caused by an internal or external issue.

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • None
    • rhel-net-mgmt
    • 3
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Hide

      Definition of Done:

      Please mark each item below with ( / ) if completed or ( x ) if incomplete:

      ( ) The acceptance criteria defined below are met.

          Given a device managed by NetworkManager, 

          When the device link transitions to "down" state, 

          Then the NetworkManager log must include a clear, plain-text message explaining the cause
          And the reason must distinguish between user disabled networking, carrier loss (cable unplugged) or DHCP lease failure. 


      ( ) Integration test case is available upstream.


      ( ) Code is reviewed and merged upstream.


      ( ) Preliminary testing is done.

      Show
      Definition of Done: Please mark each item below with ( / ) if completed or ( x ) if incomplete: ( ) The acceptance criteria defined below are met.     Given a device managed by NetworkManager,      When the device link transitions to "down" state,      Then the NetworkManager log must include a clear, plain-text message explaining the cause     And the reason must distinguish between user disabled networking, carrier loss (cable unplugged) or DHCP lease failure.  ( ) Integration test case is available upstream. ( ) Code is reviewed and merged upstream. ( ) Preliminary testing is done.
    • Pass
    • Automated
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      Enhancing the Network Manager could enable it to record each link flipping event, thereby indicating whether such occurrences were attributable to internal components or external factors. 

          1. Example*

      When executing "nmcli networking off," the ethtool status for the interface shows "Link detection: no," indicating a Layer 1 problem. However, this is not actually the case.

      +++++++++++++++++++++++++++

      1. ethtool enp1s0

      Settings for enp1s0:
             Supported ports: [  ]
             Supported link modes:   Not reported
             Supported pause frame use: No
             Supports auto-negotiation: No
             Supported FEC modes: Not reported
             Advertised link modes:  Not reported
             Advertised pause frame use: No
             Advertised auto-negotiation: No
             Advertised FEC modes: Not reported
             Speed: Unknown!
             Duplex: Unknown! (255)
             Auto-negotiation: off
             Port: Other
             PHYAD: 0
             Transceiver: internal
             Link detected:  no <----------

      +++++++++++++++++++++++++++

      • From the logs, we also could not understand why the ethtool "Link detected: no". There is confusion in the logs making it hard to understand. 

      +++++++++++++++

      Jul 16 08:49:12 rhel9 NetworkManager[729]: <info>  [1752635952.0054] dhcp4 (enp1s0): state changed new lease, address=192.168.122.214
      Jul 16 08:49:12 rhel9 systemd[1]: Starting Network Manager Script Dispatcher Service...
      Jul 16 08:49:12 rhel9 systemd[1]: Started Network Manager Script Dispatcher Service.
      Jul 16 08:49:22 rhel9 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
      Jul 16 08:59:32 rhel9 NetworkManager[729]: <info>  [1752636572.2229] manager: disable requested (sleeping: no  enabled: yes)
      Jul 16 08:59:32 rhel9 NetworkManager[729]: <info>  [1752636572.2230] device (enp7s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
      Jul 16 08:59:32 rhel9 NetworkManager[729]: <info>  [1752636572.2236] manager: NetworkManager state is now ASLEEP
      Jul 16 08:59:32 rhel9 NetworkManager[729]: <info>  [1752636572.2237] audit: op="networking-control" arg="off" pid=13409 uid=0 result="success"
      Jul 16 08:59:32 rhel9 NetworkManager[729]: <info>  [1752636572.2237] device (lo): state change: activated -> deactivating (reason 'sleeping', managed-type: 'external')
      Jul 16 08:59:32 rhel9 NetworkManager[729]: <info>  [1752636572.2241] device (enp1s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
      Jul 16 08:59:32 rhel9 systemd[1]: Starting Network Manager Script Dispatcher Service...
      Jul 16 08:59:32 rhel9 systemd[1]: Started Network Manager Script Dispatcher Service.
      Jul 16 08:59:32 rhel9 NetworkManager[729]: <info>  [1752636572.2415] device (lo): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'external')
      Jul 16 08:59:32 rhel9 NetworkManager[729]: <info>  [1752636572.2425] device (enp1s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
      Jul 16 08:59:32 rhel9 NetworkManager[729]: <info>  [1752636572.2430] dhcp4 (enp1s0): canceled DHCP transaction
      Jul 16 08:59:32 rhel9 NetworkManager[729]: <info>  [1752636572.2430] dhcp4 (enp1s0): activation: beginning transaction (timeout in 45 seconds)
      Jul 16 08:59:32 rhel9 NetworkManager[729]: <info>  [1752636572.2431] dhcp4 (enp1s0): state changed no lease
      +++++++++++++++

       

       

              rhn-engineering-vbenes Vladimir Benes
              rhn-support-bas Balakrishnan S
              Network Management Team Network Management Team
              Vladimir Benes Vladimir Benes
              Votes:
              1 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: