Comware

 View Only
Back to discussions
Expand all | Collapse all

Compatability of 5130 EI and 5140 EI IRF switches and JD089B SFP RF-45 transceiver

This thread has been viewed 41 times

  • 1.  Compatability of 5130 EI and 5140 EI IRF switches and JD089B SFP RF-45 transceiver

    Posted Feb 05, 2024 05:33 PM

    Hi All,

    I am having issues getting a JD089B SFP RJ-45 transceiver working on either a 5130 EI or 5140 EI IRF stack. I have tried on both normal SFP port (on the 5130 EI) as well as combo port (on the 5140 EI) with no luck. Has anyone else had this issue.

    The transceiver is recognised when inserted (line protocol UP shown within the console) and running display transceiver interface shows the following info (from a 5130-24G-SFP-4SFP+ EI switch

    However when i plug an ethernet cable from a pc to the transceiver, no link lights come up. I have tried enabling/disabling the interface, changing MDI/MDIX mode, setting link speed to 1Gb/100Mb, and on the combo port changing mode to copper/fibre/auto without any luck. Have tried Cat6A, Cat6 and Cat5e cables, both straight through and cross-over with no luck.

    The transceivers are below. I have bought and inserted 8 of them, and cannot get 2 of them working. I havent tried the other 6, but i wouldnt think all 8 are faulty. Possibly some compatibility issue (although product specifications say the JD089B is compatible transceiver for the 5130/5140 switches). Any help resolving this issue would be appreciated

    Regards,

    James



  • 2.  RE: Compatability of 5130 EI and 5140 EI IRF switches and JD089B SFP RF-45 transceiver

    Posted Feb 06, 2024 02:35 AM

    Hi James, it sounds like you know what you are doing so I probably can't add much.

    I have other Comware models and use copper modules. Always in ten gig ports in my case. There I have to specify the speed as 1G but no other commands.

    There are plenty of restrictions on copper transceivers stated for other switches (some CX allow in the top row only for example) but I'm not aware here.

    The only things I can think to try are to put the module in a SFP+ port (which might have more power going to it) and to put two in a single switch and put a cable between them (to rule out something funny with the test PC).




  • 3.  RE: Compatability of 5130 EI and 5140 EI IRF switches and JD089B SFP RF-45 transceiver

    Posted Feb 06, 2024 05:33 AM

    Hello

    I have 5510 models that accept and use 1GBase-T SFPs with no problem :

    display inter g1/0/11
GigabitEthernet1/0/11
Current state: UP
Line protocol state: UP
IP packet frame type: Ethernet II, hardware address: 943f-c248-xxxx
Description: "xxxxx"
Bandwidth: 1000000 kbps
Loopback is not set
Media type is twisted pair, Port hardware type is 1000_BASE_T_AN_SFP
1000Mbps-speed mode, full-duplex mode
Link speed type is autonegotiation, link duplex type is autonegotiation

    can you give us the "display interface" when SFP inserted and cable plugged in ?

    What firmware version do you use ?



    ------------------------------
    Frederic MEUNIER
    ------------------------------



  • 4.  RE: Compatability of 5130 EI and 5140 EI IRF switches and JD089B SFP RF-45 transceiver

    Posted Feb 11, 2024 04:59 PM

    Hi Ian/Frmeunier,

    I tried inserting the transceiver into the SFP+ port, setting link speed to 1Gbps, but still no link/activity.

    In regards to testing (this is on a 5140 24G 4SFP+ 1-slot HI 2-member IRF switch), i had the pc plugged into ethernet port 1/0/18 (combo port) and ran dis int:

    <xxx>dis int GigabitEthernet 1/0/18
    GigabitEthernet1/0/18
    Current state: UP
    Line protocol state: UP
    IP packet frame type: Ethernet II, hardware address: 5477-8a79-xxxx
    Description: xxx
    Bandwidth: 1000000 kbps
    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
    Maximum frame length: 10000
    Allow jumbo frames to pass
    Broadcast max-ratio: 100%
    Multicast max-ratio: 100%
    Unicast max-ratio: 100%
    Known-unicast max-ratio: 100%
    PVID: xxx
    MDI type: Automdix
    Port link-type: Access
     Tagged VLANs:   None
     Untagged VLANs: xxx
    Port priority: 0
    Last link flapping: 0 hours 4 minutes 56 seconds
    Last clearing of counters: Never
    Current system time:2024-02-09 14:17:10 Brisbane+10:00:00
    Last time when physical state changed to up:2024-02-09 14:12:14 Brisbane+10:00:00
    Last time when physical state changed to down:2024-02-09 14:12:11 Brisbane+10:00:00
     Peak input rate: 159 bytes/sec, at 2024-02-09 14:16:30
     Peak output rate: 93 bytes/sec, at 2024-02-09 14:16:25
     Last 300 seconds input: 1 packets/sec 127 bytes/sec 0%
     Last 300 seconds output: 0 packets/sec 87 bytes/sec 0%
     Input (total):  751 packets, 54491 bytes
             0 unicasts, 629 broadcasts, 122 multicasts, 0 pauses
     Input (normal):  751 packets, - bytes
             0 unicasts, 629 broadcasts, 122 multicasts, 0 pauses
     Input:  0 input errors, 0 runts, 0 giants, 0 throttles
             0 CRC, 0 frame, - overruns, 0 aborts
             - ignored, - parity errors
     Output (total): 210 packets, 33618 bytes
             0 unicasts, 0 broadcasts, 210 multicasts, 0 pauses
     Output (normal): 210 packets, - bytes
             0 unicasts, 0 broadcasts, 210 multicasts, 0 pauses
     Output: 0 output errors, - underruns, - buffer failures
             0 aborts, 0 deferred, 0 collisions, 0 late collisions
             0 lost carrier, - no carrier
    IPv4 traffic statistics:
     Last 300 seconds input rate: 0 packets/sec, 0 bytes/sec
     Last 300 seconds output rate: 0 packets/sec, 0 bytes/sec
     Input: 0 packets, 0 bytes
     Output: 0 packets, 0 bytes
    IPv6 traffic statistics:
     Last 300 seconds input rate: 0 packets/sec, 0 bytes/sec
     Last 300 seconds output rate: 0 packets/sec, 0 bytes/sec
     Input: 0 packets, 0 bytes
     Output: 0 packets, 0 bytes

    i then inserted the RJ-45 SFP transceiver into 1/0/19 (fibre combo port) and seen the following on the console:

    <xxx>%Feb  9 14:20:00:901 2024 xxx OPTMOD/4/MODULE_IN: GigabitEthernet1/0/19: The transceiver is 1000_BASE_T_AN_SFP.

    i then ran dis int for port 19 and got:

    <xxx>dis int GigabitEthernet 1/0/19
    GigabitEthernet1/0/19
    Current state: DOWN
    Line protocol state: DOWN
    IP packet frame type: Ethernet II, hardware address: 5477-8a79-xxxx
    Description: GigabitEthernet1/0/19 Interface
    Bandwidth: 1000000 kbps
    Loopback is not set
    Media type is twisted pair, Port hardware type is 1000_BASE_T_AN_SFP
    Unknown-speed mode, unknown-duplex mode
    Link speed type is autonegotiation, link duplex type is autonegotiation
    Flow-control is not enabled
    Maximum frame length: 10000
    Allow jumbo frames to pass
    Broadcast max-ratio: 100%
    Multicast max-ratio: 100%
    Unicast max-ratio: 100%
    Known-unicast max-ratio: 100%
    PVID: xxx
    MDI type: Automdix
    Port link-type: Access
     Tagged VLANs:   None
     Untagged VLANs: xxx
    Port priority: 0
    Last link flapping: Never
    Last clearing of counters: Never
    Current system time:2024-02-09 14:20:53 Brisbane+10:00:00
    Last time when physical state changed to up:-
    Last time when physical state changed to down:2024-02-07 01:49:14 Brisbane+10:00:00
     Peak input rate: 0 bytes/sec, at 2024-02-07 11:52:10
     Peak output rate: 0 bytes/sec, at 2024-02-07 11:52:10
     Last 300 seconds input: 0 packets/sec 0 bytes/sec -%
     Last 300 seconds output: 0 packets/sec 0 bytes/sec -%
     Input (total):  0 packets, 0 bytes
             0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
     Input (normal):  0 packets, - bytes
             0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
     Input:  0 input errors, 0 runts, 0 giants, 0 throttles
             0 CRC, 0 frame, - overruns, 0 aborts
             - ignored, - parity errors
     Output (total): 0 packets, 0 bytes
             0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
     Output (normal): 0 packets, - bytes
             0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
     Output: 0 output errors, - underruns, - buffer failures
             0 aborts, 0 deferred, 0 collisions, 0 late collisions
             0 lost carrier, - no carrier
    IPv4 traffic statistics:
     Last 300 seconds input rate: 0 packets/sec, 0 bytes/sec
     Last 300 seconds output rate: 0 packets/sec, 0 bytes/sec
     Input: 0 packets, 0 bytes
     Output: 0 packets, 0 bytes
    IPv6 traffic statistics:
     Last 300 seconds input rate: 0 packets/sec, 0 bytes/sec
     Last 300 seconds output rate: 0 packets/sec, 0 bytes/sec
     Input: 0 packets, 0 bytes
     Output: 0 packets, 0 bytes

    i then moved the current ethernet cable for the pc from ethernet combo port 18 to the fibre-to-RF45 SFP fibre combo port 19 and ran dis int

    <xxx>%Feb  9 14:22:04:739 2024 xxx IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/18 changed to down.
    %Feb  9 14:22:04:744 2024 xxx IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/18 changed to down.

    <xxx>dis int GigabitEthernet 1/0/19
    GigabitEthernet1/0/19
    Current state: DOWN
    Line protocol state: DOWN
    IP packet frame type: Ethernet II, hardware address: 5477-8a79-xxxx
    Description: GigabitEthernet1/0/19 Interface
    Bandwidth: 1000000 kbps
    Loopback is not set
    Media type is twisted pair, Port hardware type is 1000_BASE_T_AN_SFP
    Unknown-speed mode, unknown-duplex mode
    Link speed type is autonegotiation, link duplex type is autonegotiation
    Flow-control is not enabled
    Maximum frame length: 10000
    Allow jumbo frames to pass
    Broadcast max-ratio: 100%
    Multicast max-ratio: 100%
    Unicast max-ratio: 100%
    Known-unicast max-ratio: 100%
    PVID: xxx
    MDI type: Automdix
    Port link-type: Access
     Tagged VLANs:   None
     Untagged VLANs: xxx
    Port priority: 0
    Last link flapping: Never
    Last clearing of counters: Never
    Current system time:2024-02-09 14:23:12 Brisbane+10:00:00
    Last time when physical state changed to up:-
    Last time when physical state changed to down:2024-02-07 01:49:14 Brisbane+10:00:00
     Peak input rate: 0 bytes/sec, at 2024-02-07 11:52:10
     Peak output rate: 0 bytes/sec, at 2024-02-07 11:52:10
     Last 300 seconds input: 0 packets/sec 0 bytes/sec -%
     Last 300 seconds output: 0 packets/sec 0 bytes/sec -%
     Input (total):  0 packets, 0 bytes
             0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
     Input (normal):  0 packets, - bytes
             0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
     Input:  0 input errors, 0 runts, 0 giants, 0 throttles
             0 CRC, 0 frame, - overruns, 0 aborts
             - ignored, - parity errors
     Output (total): 0 packets, 0 bytes
             0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
     Output (normal): 0 packets, - bytes
             0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses
     Output: 0 output errors, - underruns, - buffer failures
             0 aborts, 0 deferred, 0 collisions, 0 late collisions
             0 lost carrier, - no carrier
    IPv4 traffic statistics:
     Last 300 seconds input rate: 0 packets/sec, 0 bytes/sec
     Last 300 seconds output rate: 0 packets/sec, 0 bytes/sec
     Input: 0 packets, 0 bytes
     Output: 0 packets, 0 bytes
    IPv6 traffic statistics:
     Last 300 seconds input rate: 0 packets/sec, 0 bytes/sec
     Last 300 seconds output rate: 0 packets/sec, 0 bytes/sec
     Input: 0 packets, 0 bytes
     Output: 0 packets, 0 bytes

    As you can see the switch recognises the transceiver when inserted, but just does not bring up a link when an ethernet cable is inserted. I also tested a single brand new 5140 24G SFP 4SFP+ EI switch without any config/latest firmware on it, and got the same result

    Current firmware on IRF is most current release:

    <xxx>dis version
    HPE Comware Software, Version 7.1.070, Release 6628P43
    Copyright (c) 2010-2023 Hewlett Packard Enterprise Development LP
    HPE 5140 24G 4SFP+ 1-slot HI Sw R9L61A uptime is 0 weeks, 2 days, 16 hours, 57 minutes
    Last reboot reason : User reboot

    Boot image: flash:/5140hi-cmw710-boot-r6628p43.bin
    Boot image version: 7.1.070, Release 6628P43
      Compiled Aug 10 2023 11:00:00
    System image: flash:/5140hi-cmw710-system-r6628p43.bin
    System image version: 7.1.070, Release 6628P43
      Compiled Aug 10 2023 11:00:00
    Feature image(s) list:
      flash:/5140hi-cmw710-freeradius-r6628p43.bin, version: 7.1.070, Release 6628P43
        Compiled Aug 10 2023 11:00:00


    Slot 1:
    Uptime is 0 weeks,2 days,16 hours,57 minutes
    5140 24G 4SFP+ 1-slot HI Sw with 2 Processors
    BOARD TYPE:         5140 24G 4SFP+ 1-slot HI Sw
    DRAM:               2048M bytes
    FLASH:              512M bytes
    PCB 1 Version:      VER.B
    Bootrom Version:    121
    CPLD 1 Version:     002
    Release Version:    HPE 5140 24G 4SFP+ 1-slot HI Sw R9L61A-6628P43
    Patch Version  :    None
    Reboot Cause  :     UserReboot
    [SubSlot 0] 16GE+8COMBO+4SFP Plus

    Slot 2:
    Uptime is 0 weeks,2 days,16 hours,57 minutes
    5140 24G 4SFP+ 1-slot HI Sw with 2 Processors
    BOARD TYPE:         5140 24G 4SFP+ 1-slot HI Sw
    DRAM:               2048M bytes
    FLASH:              512M bytes
    PCB 1 Version:      VER.B
    Bootrom Version:    121
    CPLD 1 Version:     002
    Release Version:    HPE 5140 24G 4SFP+ 1-slot HI Sw R9L61A-6628P43
    Patch Version  :    None
    Reboot Cause  :     UserReboot
    [SubSlot 0] 16GE+8COMBO+4SFP Plus
    <xxx>


    Original Message


  • 5.  RE: Compatability of 5130 EI and 5140 EI IRF switches and JD089B SFP RF-45 transceiver

    Posted Feb 12, 2024 03:51 AM

    Hi James

    Can you post the result of "display curr int g1/0/19"



    ------------------------------
    Frederic MEUNIER
    ------------------------------

    Original Message


  • 6.  RE: Compatability of 5130 EI and 5140 EI IRF switches and JD089B SFP RF-45 transceiver

    Posted Feb 12, 2024 07:41 PM

    Hi Frederic,

    Output below:

    <xxx>dis curr int GigabitEthernet 1/0/19
    #
    interface GigabitEthernet1/0/19
     port link-mode bridge
     port access vlan xxx
     combo enable auto
    #
    return
    <xxx>

    have also included the all command below:

    [xxx]dis curr int GigabitEthernet 1/0/19 all
    #
    interface GigabitEthernet1/0/19
     port link-mode bridge
     description GigabitEthernet1/0/19 Interface
     enable snmp trap updown
     enable log updown
     undo bandwidth
     undo evb enable
     evb vdp timer resource-wait-delay exponent 20
     evb vdp timer keepalive exponent 20
     port link-type access
     port access vlan xxx
     undo port outbound-vlan-tag enable
     undo vlan mapping nni
     undo port private-vlan
     voice-vlan qos 6 46
     voice-vlan mode auto
     undo voice-vlan enable
     undo mac-vlan enable
     undo mac-vlan trigger enable
     undo port pvid forbidden
     combo enable auto
     mdix-mode automdix
     speed auto
     speed auto downgrade
     duplex auto
     undo loopback
     transceiver tx-enable
     undo source-interface
     undo shutdown
     undo port-isolate enable
     undo link-delay down
     undo link-delay up
     undo port link-flap protect enable
     undo storm-constrain broadcast
     undo storm-constrain multicast
     undo storm-constrain unicast
     undo storm-constrain control
     storm-constrain enable trap
     storm-constrain enable log
     undo port auto-power-down
     undo port up-mode
     undo priority-flow-control
     undo priority-flow-control no-drop dot1p
     undo priority-flow-control dscp-mapping
     jumboframe enable 10000
     flow-interval 300
     undo flow-control
     undo eee enable
     undo dampening
     broadcast-suppression 100
     multicast-suppression 100
     unicast-suppression 100
     unicast-suppression 100 known
     undo bpdu-drop any
     undo macsec desire
     macsec include-sci
     undo macsec maintenance-mode enable
     undo mka apply policy
     macsec confidentiality-offset 0
     macsec replay-protection enable
     macsec replay-protection window-size 0
     macsec validation mode check
     undo mka enable
     mka priority 0
     undo mka psk
     macsec cipher-suite gcm-aes-128
     mka timer mka-life 6
     undo port ifmonitor crc-error
     undo port ifmonitor input-error
     undo port ifmonitor output-error
     undo port ifmonitor rx-pause
     undo port ifmonitor tx-pause
     undo port ifmonitor sdh-error
     undo port ifmonitor sdh-b1-error
     undo port ifmonitor sdh-b2-error
     undo port ifmonitor input-usage
     undo port ifmonitor output-usage
     crc-error bit-error-ratio transfer-protocol bfd
     undo igmp-snooping fast-leave
     undo igmp-snooping overflow-replace
     undo igmp-snooping source-deny
     undo port multicast-vlan
     undo igmp-snooping router-port-deny
     undo igmp-snooping group-limit
     undo igmp-snooping group-policy
     undo igmp-snooping static-router-port all
     undo igmp-snooping static-group all
     undo igmp-snooping host-join all
     stp enable
     undo stp root-protection
     undo stp loop-protection
     stp loopback-protection
     undo stp edged-port
     undo stp no-agreement-check
     undo stp config-digest-snooping
     undo stp tc-restriction
     undo stp role-restriction
     stp compliance auto
     stp transmit-limit 10
     stp point-to-point auto
     undo stp port bpdu-protection
     undo stp port bpdu-filter
     lldp enable
     lldp compliance admin-status cdp disable
     undo lldp encapsulation
     undo lldp check-change-interval
     undo lldp management-address-format
     lldp admin-status txrx
     undo lldp tlv-config basic-tlv port-id
     undo cdp voice-vlan
     undo lldp source-mac vlan
     undo lldp management-address arp-learning
     undo lldp management-address nd-learning
     undo lldp notification remote-change enable
     undo lldp notification med-topology-change enable
     lldp tlv-enable basic-tlv port-description
     lldp tlv-enable basic-tlv system-name
     lldp tlv-enable basic-tlv system-description
     lldp tlv-enable basic-tlv system-capability
     undo lldp tlv-enable dot1-tlv dcbx
     lldp tlv-enable dot1-tlv port-vlan-id
     undo lldp tlv-enable dot1-tlv protocol-vlan-id
     undo lldp tlv-enable dot1-tlv vlan-name
     undo lldp tlv-enable dot1-tlv management-vid
     lldp tlv-enable dot1-tlv link-aggregation
     undo lldp tlv-enable dot1-tlv congestion-notification
     undo lldp tlv-enable dot1-tlv evb
     lldp tlv-enable dot3-tlv mac-physic
     lldp tlv-enable dot3-tlv power
     lldp tlv-enable dot3-tlv max-frame-size
     undo lldp tlv-enable dot3-tlv eee
     lldp tlv-enable med-tlv capability
     lldp tlv-enable med-tlv network-policy
     lldp tlv-enable med-tlv power-over-ethernet
     lldp tlv-enable med-tlv inventory
     undo lldp tlv-enable dot3-tlv link-aggregation
     undo lldp agent nearest-nontpmr encapsulation
     undo lldp agent nearest-nontpmr check-change-interval
     undo lldp agent nearest-nontpmr management-address-format
     lldp agent nearest-nontpmr admin-status disable
     undo lldp agent nearest-nontpmr notification remote-change enable
     undo lldp agent nearest-nontpmr tlv-enable basic-tlv port-description
     undo lldp agent nearest-nontpmr tlv-enable basic-tlv system-name
     undo lldp agent nearest-nontpmr tlv-enable basic-tlv system-description
     undo lldp agent nearest-nontpmr tlv-enable basic-tlv system-capability
     undo lldp agent nearest-nontpmr tlv-enable dot1-tlv dcbx
     undo lldp agent nearest-nontpmr tlv-enable dot1-tlv port-vlan-id
     undo lldp agent nearest-nontpmr tlv-enable dot1-tlv link-aggregation
     undo lldp agent nearest-nontpmr tlv-enable dot1-tlv congestion-notification
     lldp agent nearest-nontpmr tlv-enable dot1-tlv evb
     undo lldp agent nearest-nontpmr tlv-enable dot3-tlv mac-physic
     undo lldp agent nearest-nontpmr tlv-enable dot3-tlv power
     undo lldp agent nearest-nontpmr tlv-enable dot3-tlv max-frame-size
     undo lldp agent nearest-nontpmr tlv-enable dot3-tlv eee
     undo lldp agent nearest-nontpmr tlv-enable med-tlv capability
     undo lldp agent nearest-nontpmr tlv-enable med-tlv network-policy
     undo lldp agent nearest-nontpmr tlv-enable med-tlv power-over-ethernet
     undo lldp agent nearest-nontpmr tlv-enable med-tlv inventory
     undo lldp agent nearest-nontpmr tlv-enable dot3-tlv link-aggregation
     undo lldp agent nearest-customer encapsulation
     undo lldp agent nearest-customer check-change-interval
     undo lldp agent nearest-customer management-address-format
     lldp agent nearest-customer admin-status disable
     undo lldp agent nearest-customer notification remote-change enable
     lldp agent nearest-customer tlv-enable basic-tlv port-description
     lldp agent nearest-customer tlv-enable basic-tlv system-name
     lldp agent nearest-customer tlv-enable basic-tlv system-description
     lldp agent nearest-customer tlv-enable basic-tlv system-capability
     undo lldp agent nearest-customer tlv-enable dot1-tlv dcbx
     lldp agent nearest-customer tlv-enable dot1-tlv port-vlan-id
     lldp agent nearest-customer tlv-enable dot1-tlv link-aggregation
     undo lldp agent nearest-customer tlv-enable dot1-tlv congestion-notification
     undo lldp agent nearest-customer tlv-enable dot1-tlv evb
     undo lldp agent nearest-customer tlv-enable dot3-tlv mac-physic
     undo lldp agent nearest-customer tlv-enable dot3-tlv power
     undo lldp agent nearest-customer tlv-enable dot3-tlv max-frame-size
     undo lldp agent nearest-customer tlv-enable dot3-tlv eee
     undo lldp agent nearest-customer tlv-enable med-tlv capability
     undo lldp agent nearest-customer tlv-enable med-tlv network-policy
     undo lldp agent nearest-customer tlv-enable med-tlv power-over-ethernet
     undo lldp agent nearest-customer tlv-enable med-tlv inventory
     undo lldp agent nearest-customer tlv-enable dot3-tlv link-aggregation
     qos priority 0
     qos wrr weight
     qos wrr be group 1 weight 1
     qos wrr af1 group 1 weight 2
     qos wrr af2 group 1 weight 3
     qos wrr af3 group 1 weight 4
     qos wrr af4 group 1 weight 5
     qos wrr ef group 1 weight 9
     qos wrr cs6 group 1 weight 13
     qos wrr cs7 group 1 weight 15
     link-aggregation port-priority 32768
     undo lacp period
     undo lacp mode
     undo lacp transparent enable
    #
    return
    [xxx]

    Regards,

    James


    Original Message


  • 7.  RE: Compatability of 5130 EI and 5140 EI IRF switches and JD089B SFP RF-45 transceiver

    Posted Feb 13, 2024 04:39 AM

    Hi James

    Did you try to force the combo ?

    "combo enable fiber" (to force using the SFP)



    ------------------------------
    Frederic MEUNIER
    ------------------------------

    Original Message


  • 8.  RE: Compatability of 5130 EI and 5140 EI IRF switches and JD089B SFP RF-45 transceiver

    Posted Feb 13, 2024 04:33 PM

    yes, i have tried all 3:

    combo enable auto

    combo enable fiber

    combo enable copper

    without any success


    Original Message


  • 9.  RE: Compatability of 5130 EI and 5140 EI IRF switches and JD089B SFP RF-45 transceiver

    Posted Feb 14, 2024 02:50 AM
    Hi, I was intrigued and did a lot of searching and there isn't any info on this that I could find. As I have other platforms that have limits on the use of certain optics I assume those ports can't provide enough power to drive a copper gbic. I have CX switches that have the same behaviour for LRM.

    So assuming you haven't hit a very unlucky batch, and you've tried connecting between two ports to eliminate external factors, I would conclude this isn't going to work. The lack of docs means only Aruba support could say for certain. 

    If they didn't work in the SFP+ ports it would suggest an issue with the transceiver but i guess that can be tested with a different switch model.








    Original Message


  • 10.  RE: Compatability of 5130 EI and 5140 EI IRF switches and JD089B SFP RF-45 transceiver

    Posted Feb 14, 2024 08:09 AM

    Hi James

    That's weird because JD089B is clearly officially supported !

    And Comware is really permissive ! I managed to use roughly any SFP (whatever vendor) in this kind of switches.

    Did you try, as Ian proposed "to put two in a single switch and put a cable between them " (but in the SFP slots , not SFP+) ?

    or between 1 SFP T  (g1/0/19) and port g1/0/18 ?

    (STP should block one, but link and protocol should be up)

    Did you try to open a case on Aruba Support Portal ?



    ------------------------------
    Frederic MEUNIER
    ------------------------------

    Original Message


  • 11.  RE: Compatability of 5130 EI and 5140 EI IRF switches and JD089B SFP RF-45 transceiver

    Posted Feb 16, 2024 12:17 AM

    As suggested, i tried putting the RJ45 transceivers into 2 SFP ports on the same IRF switch member (this time combo port 1/0/19 and 1/0/20) and connected an ethernet cable between them. BOOM. > link light/activity on the SFP ports > console displayed:

    %Feb 16 14:21:57:316 2024 xxx IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/20 changed to up.
    %Feb 16 14:21:57:322 2024 xxx IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/20 changed to up.
    %Feb 16 14:21:57:414 2024 xxx STP/6/STP_DETECTED_TC: Instance 0's port GigabitEthernet1/0/19 detected a topology change.
    %Feb 16 14:21:57:430 2024 xxx IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/19 changed to up.
    %Feb 16 14:21:57:463 2024 xxx IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/19 changed to up.

    I also then tried between this member 1 IRF switch and another member 1 IRF switch, and i also got line/protocol UP.

    Thus, it seems that these transceivers can only be used for connecting between switches, not for end device connectivity (pcs/servers). Unless there is a specific setting that needs to be set on the pc/server NIC that i am unaware of. Maybe there is some particular protocol that they use that requires them to be used as pairs. Admittedly, i havent yet tried using this SFP RJ-45 transceiver to connect direct to another standard RJ-45 ethernet port (to eliminate as to whether they need to be used in pairs or not). I primarily bought these for connecting some pcs to this switch, not for switch-to-switch connections, thus i may need to just build an auxiliary switch for this purpose.

    If anyone has one of these RJ45 (JD089B) transceivers and has a chance, can they try connecting one to either a 5130/5140 SFP/IRF switch and see if they can get simple connectivity/link to a pc/server.

    Regards,

    James


    Original Message


  • 12.  RE: Compatability of 5130 EI and 5140 EI IRF switches and JD089B SFP RF-45 transceiver

    Posted Feb 16, 2024 04:53 AM

    Hi James

    Well, on my side, copper SFPs are used to successfully connect servers (on 5510 switches)

    Maybe the problem is on the client side ? (since you already tried different patch cords, with no success)

    How much time do you wait for the link to go up ? Is STP (any flavor) active on the switches ?



    ------------------------------
    Frederic
    ------------------------------

    Original Message


Related Content