- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Web and Unmanaged
- >
- Incidente con mi Switch -HPE OfficeConnect Switch ...
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
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
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
06-22-2019 02:28 PM
06-22-2019 02:28 PM
Incidente con mi Switch -HPE OfficeConnect Switch 1920S 48G 4SFP JL382A
Dear good afternoon, Request your support today, change and restart unexpectedly the following message, I need your support to prevent the case.
***************************************************
* Start FASTPATH Stack Information *
***************************************************
pid: 1129
TID: 0xb67204c0
Task Name: bcmINTR
si_signo: 11
si_errno: 0
si_code: 1
si_addr: (nil)
Date/Time: 5/2/1970 7:59:47
SW ver: PD.01.05
------------ CALL STACK INFO ------------
$001b9804$ log_error_code + 0x60
$0006bcdc$ hapiBroadAssert + 0x14
$00e8f778$ sal_assert_set + 0x30
$00ffccec$ soc_dma_done_chain + 0x224
$0101a194$ soc_cmicm_intr + 0x200
$00e8bb1c$ bcm_hr2_dual_port_mode_reinit + 0x748
$00640c40$ osapi_task_wrapper + 0x168
/lib/libpthread.so.0 [0xb6f717e8]
-----------------------------------------
Stack Size: 20480 Bytes
Stack Base Address: 0xB671C000
***************************************************
* End FASTPATH Stack Information *
***************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2019 02:36 PM
06-24-2019 02:36 PM
Re: Incidente con mi Switch -HPE OfficeConnect Switch 1920S 48G 4SFP JL382A
Do yourself a favour: update your JL382A Software Version ASAP.
***************************************************
* Start FASTPATH Stack Information *
***************************************************
pid: 1129
TID: 0xb67204c0
Task Name: bcmINTR
si_signo: 11
si_errno: 0
si_code: 1
si_addr: (nil)
Date/Time: 5/2/1970 7:59:47
SW ver: PD.01.05
------------ CALL STACK INFO ------------
$001b9804$ log_error_code + 0x60
$0006bcdc$ hapiBroadAssert + 0x14
$00e8f778$ sal_assert_set + 0x30
$00ffccec$ soc_dma_done_chain + 0x224
$0101a194$ soc_cmicm_intr + 0x200
$00e8bb1c$ bcm_hr2_dual_port_mode_reinit + 0x748
$00640c40$ osapi_task_wrapper + 0x168
/lib/libpthread.so.0 [0xb6f717e8]
-----------------------------------------
Stack Size: 20480 Bytes
Stack Base Address: 0xB671C000
***************************************************
* End FASTPATH Stack Information *
***************************************************
Your HPE OfficeConnect 1920S is actually running an old (the first ever released for the HPE 1920S) PD.01.05 Software version built on February, 20th 2017...more than two years old...update to latest PD.02.09 Software version built on May, 14th 2019, few weeks ago.
If you're going to open a support case (once the product is registered) then I bet HPE/Aruba will ask you to update accordingly.
References here (Read CAREFULLY every Release Notes, especially the one related to the first PD.02.xx to understand how to move from PD.01.xx to PD.02.xx safely). Another useful page could be this one.
I'm not an HPE Employee