Hello, on a stack of two HPE 1920/24 ports switch (Ref: JG924A), I need to do a LACP aggregation of two ports G1 / 0/1 and G2 / 0/1, what can I do?Hello, on a stack of two HPE 1920/24 ports switch (Ref: JG924A), I need to do a LACP aggregation of two ports G1 / 0/1 and G2 / 0/1, what can I do?
Re: STACK HPE 1920
Re: STACK HPE 1920
Hi,
Please refere below link pg. 191 topic: Configuring link aggregation and LACP.
https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=c04463799
Thanks!
Re: HPE 1920s (JL384A) PoE compatibility issues
Hi,
In this case you need to log a case with support to check the limitations of the product.
Thanks!
Re: STACK HPE 1920
Hi,
Has my solution helped you resolve the query or do you need more assistance.
Thanks!
Re: STACK HPE 1920
thanks but ,
We have stack witch tow switch ( switch 1 and switch 2 )
I need to create a aggregation LACP with tow interfaces ( interface one 1/0/1 on switch 1 and interface tow 2/0/2 on a switch 2 ) ?
Re: STACK HPE 1920
Hi,
Sorry to say but you cannot have both properties combined in this model.
Thanks!
Supported QSFP (smartNIC) to 4 SFP+(HP Procurve 3500yl) converter
Hi,
I am trying to connect smartNIC to HP 3500 yl switch. The smartNIC has QSFP interface and the switch seems to have 4 SFP+ supported interfaces. I bought a QSFP to SFP+ breakout but the switch complained with "Non-HPE transceiver". I updated the firmware to K16_02_0027 but still it didnt support "allow-unsupported-transceiver" command. Please suggest the supported cables or any other ways to make this work.
The smartNIC is Netronome Agilio CX 2 x 40GbE.
Thank you
Re: Supported QSFP (smartNIC) to 4 SFP+(HP Procurve 3500yl) converter
I don't believe the HP ProCurve 3500yl supports the "allow unsupported transceivers" feature (no matter the HP ProVision software version it is running on, K.16.02.0031 or older).
The HP ProCurve 3500 yl switch series has one Open Module slot on the back. This slot supports, as example, the HP 10GbE 2-port SFP+ / 2-port CX4 yl Module (SKU: J9312A), this optional module supports up to 2 SFP+ Transceivers or DACs, this is the list:
- HPE X132 10G SFP+ LC ER TransceiverJ9153A
- HPE X132 10G SFP+ LC LR TransceiverJ9151A
- HPE X132 10G SFP+ LC LRM TransceiverJ9152A
- HPE X132 10G SFP+ LC SR TransceiverJ9150A
- HPE X242 10G SFP+ to SFP+ 1m Direct Attach Copper Cable J9281B
- HPE X242 10G SFP+ to SFP+ 3m Direct Attach Copper Cable J9283B
- HPE X242 10G SFP+ to SFP+ 7m Direct Attach Copper Cable J9285B
- HP X244 10G XFP to SFP+ 1m Direct Attach Copper Cable J9300A
- HP X244 10G XFP to SFP+ 3m Direct Attach Copper Cable J9301A
- HP X244 10G XFP to SFP+ 5m Direct Attach Copper Cable J9302A
are you working with such module?
Re: Supported QSFP (smartNIC) to 4 SFP+(HP Procurve 3500yl) converter
Thanks for the reply. But the switch already has 4 SFP+ ports (dual-personality ports) already (without any expansion slots required) right? I need a QSFP to 4 x SFP+ connection cable that would be supported by HP.
Re: Supported QSFP (smartNIC) to 4 SFP+(HP Procurve 3500yl) converter
wrote: But the switch already has 4 SFP+ ports (dual-personality ports) already (without any expansion slots required) right?
No, you are not right.
The HP ProCurve 3500yl Switch series (for details see QuickSpecs) doesn't provide SFP+ (10G/1G) slots on frontplane, only SFP (1G) slots on frontplane...and to be honest I never saw a 10G port "dual personality" (that's a detail...when you see "dual personality" ports then you have 1G RJ45 for copper Cat.5E/6 cabling paired with 1G SFP for SFP Transceiver...no with any 10G).
If you need SFP+ (thus 10G) slots you must equip your HP ProCurve 3500yl switch with the module I wrote you about in my first reply (it is a module for the slot on the back of the switch).
Dual personality ports are either 1G copper (RJ45) or 1G SFP Transceiver (generally for fiber optics SR/LR connectivity). DACs and SFP+ Transceviers can't work on those slots...even if the (physical) form factor is the same.
For a list of supported DACs (for the optional module) see above my first reply.
Re: Supported QSFP (smartNIC) to 4 SFP+(HP Procurve 3500yl) converter
Oh I see. Thanks for the clarification that SFP+ is not supported by HP 3500 yl switches. And the HP 10GbE 2-port SFP+ / 2-port CX4 yl Module (SKU: J9312A) module supports just 2 ports SFP+. But I need 4 port SFP+ support. Also I need a DAC cable to go from QSFP (from smartNIC) to 4 SFP+ (towards J9312A) module. The listsed cables doesnt seem to be of that type. Is there any such solution available that is well supported by the switch?
Thanks
Re: Supported QSFP (smartNIC) to 4 SFP+(HP Procurve 3500yl) converter
Re: Supported QSFP (smartNIC) to 4 SFP+(HP Procurve 3500yl) converter
Thank you so much for your help :).
Re: V1920 - Gateway configuration via Web GUI
Thank you!
find serial number switch HP 1820
Re: find serial number switch HP 1820
Hi,
You can refer below article:
https://support.hpe.com/hpesc/public/docDisplay?docId=mmr_sf-EN_US000005269
Thanks!
Re: STACK HPE 1920
Hi,
Has my post helped you to answer your query?
Thanks!
Re: HP 1920S web interface problem
My problem seems has been happened because feature/bug that has been resolved in 2.08
Version 02.08 Management VLAN CR_0000247836
Symptom/Scenario:
If a second VLAN (non-management VLAN) is created, the clients connected to thatnon-management VLAN can establish an HTTP connection to the management interface of the switch whensuch a connection should only be allowed from the management VLAN
I will try to insert into my config
'network mgmt_vlan 1725'
Re: HP 1920S and snmp community
It may be resolved in PD2.08 and in PD2.12
https://support.hpe.com/hpesc/public/docDisplay?docId=a00101229en_us
Re: Uploading SSL certificate to 1920S
I faced the same problem on my unit and solved it. The user manuals says this:
SSL Trusted Root Certificate PEM File:
A PEM-encoded SSL certificate that has been digitally signed by a certificate authority.SSL Server Certificate PEM File:
A PEM-encoded SSL certificate that has been signed by another server.
However, the text in the user manual makes no sense. It seems to me that the translator or writer had no idea how these settings work.
You need to upload the certificate with SSL Trusted Root Certificate PEM File and then afterwards the private key with SSL Server Certificate PEM File and it will finally work.
I think HPE should rename "SSL Trusted Root Certificate PEM File" to "SSL Certificate PEM File" and "SSL Server Certificate PEM File" to "SSL Server Private Key PEM File" to make it clear.
I could not get it to work with certificate chains though, only with the leaf certificate itself.