Comware

 View Only
  • 1.  Unknown-duplex

    Posted Feb 27, 2018 05:35 AM

    Hi,

    in switch logs we are getting unknown-duplex

    %%10LLDP/5/LLDP_DUPLEX_INCONSISTENT(l): -Slot=2; The mode of duplex mismatch discovered on GigabitEthernet2/0/7 (Full-duplex), with @▒▒V▒ (Unknown-duplex).

    Are these symbols normal switch behaviour? Thanks



  • 2.  RE: Unknown-duplex

    Posted Mar 03, 2018 11:06 PM

    What model switch do you have?



  • 3.  RE: Unknown-duplex

    Posted Mar 05, 2018 03:05 AM

    Comware Software, Version 5.20.99, Release 2222P08
    Copyright (c) 2010-2017 Hewlett Packard Enterprise Development LP
    HP A5120-48G-PoE+ EI Switch with 2 Interface Slots 



  • 4.  RE: Unknown-duplex

    Posted Apr 11, 2018 05:05 AM

    Anyone?

    It started to show after firmware upgrade, here are one more line:

    %%10LLDP/5/LLDP_DUPLEX_INCONSISTENT(l): -Slot=2; The mode of duplex mismatch discovered on GigabitEthernet2/0/30 (Full-duplex), with  (▒DM ▒ (Unknown-duplex).



  • 5.  RE: Unknown-duplex

    Posted Apr 22, 2018 08:48 PM

    I am also getting this on random ports. HP A5120-48G-PoE+ EI Switch. Comware Software, Version 5.20.99, Release 2222P07. Started happening after upgrading to this version. 

    %Apr 23 08:12:15:928 2018 ***_Edge_Stack LLDP/5/LLDP_DUPLEX_INCONSISTENT: -Slot=2; The mode of duplex mismatch discovered on GigabitEthernet2/0/17 (Full-duplex), with  D[xú (Unknown-duplex).

    %Apr 23 08:05:09:255 2018 ***_Edge_Stack LLDP/5/LLDP_DUPLEX_INCONSISTENT: The mode of duplex mismatch discovered on GigabitEthernet1/0/5 (Full-duplex), with  D[x! (Unknown-duplex).



  • 6.  RE: Unknown-duplex

    Posted Nov 26, 2018 03:54 AM

     

    Similar issue. User reports problems:

    HPE Comware Platform Software
    Comware Software, Version 5.20.99, Release 2222P10
    Copyright (c) 2010-2018 Hewlett Packard Enterprise Development LP
    HP A5500-24G EI Switch with 2 Interface Slots uptime is 12 weeks, 4 days, 12 hours, 15 minutes
    %Nov 26 08:35:55:716 2018 netz-service.sys.swch.roacf21m LLDP/5/LLDP_DUPLEX_INCONSISTENT: -Slot=1; The mode of duplex mismatch discovered on GigabitEthernet1/0/11 (Full-duplex), with  ▒ʸ\▒w (Unknown-duplex).
    >dis int gig 1/0/11
     GigabitEthernet1/0/11 current state: UP
     IP Packet Frame Type: PKTFMT_ETHNT_2, Hardware Address: 4001-c65e-65a1
     Description: GigabitEthernet1/0/11 Interface
     Loopback is not set
     Media type is twisted pair
     Port hardware type is  1000_BASE_T
     1000Mbps-speed mode, full-duplex mode
     Link speed type is autonegotiation, link duplex type is autonegotiation
     Flow-control is not enabled
     The Maximum Frame Length is 9216
     Broadcast MAX-ratio: 100%
     Unicast MAX-ratio: 100%
     Multicast MAX-ratio: 100%
     Allow jumbo frame to pass
    dis mac-address | inc 1/0/11
    f8ca-b85c-8261 1        Learned        GigabitEthernet1/0/11    AGING

     => Dell laptop



  • 7.  RE: Unknown-duplex

    Posted Nov 20, 2019 05:56 AM

    Wondering if this was ever resolved as I currently have about 50 switches with the same issue



  • 8.  RE: Unknown-duplex

    Posted Nov 25, 2019 07:42 AM

    Hi,

    was wondering if the issue is related to flow-control?
    HP A5500 - Autonegotiation and Flow Control 

    Maybe try and fiddle with the flow-control configuration on the affected interfaces. That is:

    interface Gi1/0/<some_affected_interfacenumber> 
      flow-control  
    \\ to enable TxRx flowcontrol OR
      flow-control receive enable 
    \\ to enable Rx flowcontrol only.


  • 9.  RE: Unknown-duplex

    Posted Dec 03, 2019 10:32 AM

    Same issue here.

    I have several HPE 5120-48G and HPE 5120-24G with different firware versions (P08 to P11).
    I don't have this issue with my HPE-5130 switches.

    I have done tests and here's what I've noticed :

    - Have an access to the network even with this error message
    - No error message with some devices (not computers)
    - "undo lldp enable" on the ports -> no error message (it may be obvious but it can maybe help)

    If anyone has an idea on how to "fix" this issue or an explanation about why it appears, it'd be glad to hear it.