- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- HPE Aruba Networking & ProVision-based
- >
- 5406zl compatibility with 8p 10g-gbe sfp+ v2 zl mo...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2019 01:17 AM
09-10-2019 01:17 AM
5406zl compatibility with 8p 10g-gbe sfp+ v2 zl module
Hi,
In our environment, we have two 5406zl (5406zl and e5406zl) chassis and would like to know if they are compatible to install with an 8p 10g-gbe sfp+ v2 zl module. Below is the chassis and version
SWITCH01# sh module
Chassis: 5406zl J8697A
...
SWITCH01# sh ver
Image stamp: /sw/code/build/btm(t3a)
Sep 10 2009 21:31:21
K.13.71
137
Boot Image: Primary
SWITCH01#
SWITCH02# sh module
Chassis: E5406zl J8697A
..
SWITCH02# sh ver
Image stamp: /ws/swbuildm/ec_rel_eureka_qaoff/code/build/btm(ec_rel_eureka_qaoff)
Apr 20 2012 12:34:21
K.15.06.0017
13
Boot Image: Primary
SWITCH02#
note:
Hp ProCurve 8-Port 10GbE SFP+ V2 5400zl 8200zl ZL Expansion Module -J9538A
https://www.nautilusnet.com/products/j9538a-hpe-8-port-10gbe-sfp-v2-zl-module-new.html
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2019 04:00 AM
09-10-2019 04:00 AM
Re: 5406zl compatibility with 8p 10g-gbe sfp+ v2 zl module
Hello,
The release notes of the switch contain information about the minimum supported software versions. Here for example on page 10
https://support.hpe.com/hpsc/doc/public/display?docId=a00059460en_us
We can see that module J9538A requires a minimum version K.15.02.0004.
That means that your SWITCH01 cannot run this module because it is running version K.13.71 from the year 2009.
SWITCH02 should support the module because it is running version K.15.06.0017.
The HW of the chassis itself is compatible.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2019 05:41 AM - edited 09-10-2019 08:08 AM
09-10-2019 05:41 AM - edited 09-10-2019 08:08 AM
Re: 5406zl compatibility with 8p 10g-gbe sfp+ v2 zl module
If I were you, considering the 10Gbps 8 ports Module you're planning to use on your HP ProCurve 5406zl switches [*], I would plan an update (with a minimum downtime) of current software versions to latest K.16.02.0027 (Carefully read relevant Release Notes for details about upgrading from so old software branches - K.13.71 and K.15.06 - to latest software branch K.16.02...especially for mandatory/required BootROM updates).
[*] I refer both to the oversubscription restriction that should be understood (read here just above Table 22 about 5400zl+J9538A) when using the J9538A Module on HP ProCurve 5400zl and to every possible software bug related to J9538A Module discovered and already fixed.
I'm not an HPE Employee
