- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- HPE Aruba Networking & ProVision-based
- >
- Re: Unexpected Reboot 5406zl
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
Discussions
Forums
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
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
тАО01-10-2017 09:31 AM
тАО01-10-2017 09:31 AM
Unexpected Reboot 5406zl
Dear
After performing some basic configuration on the 5406zl machine, it stops responding and restarts automatically.
Please help me, thanks
Firmware version:
Software revision: K.15.18.0006
ROM Version: K.15.30
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2017 01:31 PM - edited тАО01-10-2017 05:17 PM
тАО01-10-2017 01:31 PM - edited тАО01-10-2017 05:17 PM
Re: Unexpected Reboot 5406zl
Or...if you don't care to diagnose or you are in a hurry...consider to update Switch software using the latest available Software Version of the K15.18 branch.
Why?
Because your switch is currently running the initial release of that branch (August 2015): actually the latest available is the K.15.18.0013 (September 2016).
Eventually consider to upgrade to latest software versions respectively of K.16.01 or K.16.02 branch.
Then verify if the issue can be reproduced or if it happens randomly again.
I'm not an HPE Employee

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2017 05:25 AM
тАО01-11-2017 05:25 AM
Re: Unexpected Reboot 5406zl
Thank you dear
Sorry for not logging up, today I could access the switch and I could get a show tech. Attachment reset history
Show boot-history
Mgmt Module 1 - Saved Crash Information (most recent first):
===================================================================== ===========
ID: 7c746ab9
Active system went down: 11/30/16 12:32:53 K.15.18.0006 349
Health Monitor: Invalid Instr Misaligned Mem Access
HW Addr = 0x00000000 IP = 0x0 Task = 'mSnmpCtrl' Task ID = 0xa996880
Sp: 0x33bbbe0 lr: 0x86400
Msr: 0x02029200 xer: 0x00000000 cr: 0x24000400
ID: 02cd6d34
Active system went down: 11/30/16 12:30:15 K.15.18.0006 349
Health Monitor: Invalid Instr Misaligned Mem Access
HW Addr = 0x00000000 IP = 0x0 Task = 'mSnmpCtrl' Task ID = 0xa996880
Sp: 0x42070b8 lr: 0x86400
Msr: 0x02029200 xer: 0x00000000 cr: 0x24000400
ID: a8878f8c
Active system went down: 05/09/16 18:20:13 K.15.18.0006 349
Health Monitor: Invalid Instr Misaligned Mem Access
Hw Addr = 0x00000000 IP = 0x0 Task = 'mSnmpCtrl' Task ID = 0xa996880
Sp: 0x42080a0 lr: 0x86400
Msr: 0x02029200 xer: 0x00000000 cr: 0x24000400
ID: 941be1b6
Active system went down: 09/02/16 18:26:06 K.15.18.0006 349
Health Monitor: Invalid Instr Misaligned Mem Access
? [45; 1H? [45; 1H; [1; 45? 45; 1HHW Addr = 0x00000000 IP = 0x0 Task = 'mSnmpCtrl' Task ID = 0xa996880
Sp: 0x42072a0 lr: 0x86400
Msr: 0x02029200 xer: 0x00000000 cr: 0x24000400
Type Core Dump File Name
------------ ----------------------------
MM1 M_ID128AS1BS.cor
CRASHLogfileshow
... Crash Log File Header ..........................
Product: HP J8697A
Name: HP Switch 5406zl
Date: Aug 12 2015 10:18:07
Build: 349
Version: K.15.18.0006
Directory: / ws / swbuildm / rel_quebec_qaoff / code / buil
CPU: PPC85XX
SerialNum: ID128AS1BS
Crash rec size = 1472
Crash rec index = 0
Boot type = POWER ON
WillBootType = UNKNOWN BOOT
..................................................
No Saved Crash Information
CRASHData
--- Length 26
--- Rec Ptr ff58398
No Crash data available!
PMGRPOrtmapsshow
PMGR Physical PORTS UP (pmgr_pports_up):
A2..A3 A5..A7 A9..A11 A15 A17..A18 A21..A23 B1..B4 B6 B8..B12 B15..B22 C1..C6 C12..C15 C20 C24..D3 D6 .. D10 D13 D19..E1 F1 F9 F13..F15
PMGR Physical PPORTS FORWARDING (pmgr_pports_forwarding):
A2..A3 A5..A7 A9..A11 A15 A17..A18 A21..A23 B1..B4 B6 B8..B12 B15..B22 C1..C6 C12..C15 C20 C24..D3 D6 .. D10 D13 D19..E1 F1 F9 F13..F15
PMGR Logical LPORTS FORWARDING (pmgr_lports_forwarding):
A2..A3 A5..A7 A9..A11 A15 A17..A18 A21..A23 B1..B4 B6 B8..B12 B15..B22 C1..C6 C12..C15 C20 C24..D3 D6 .. D10 D13 D19..E1 F1 F9 F13..F15
PMGR Trunk Allocation Map (pmgr_trunks_allocated.map):
DOES PMGR need Dynamic Reconfig of PPORTS? DO NOT
? [45; 1 H] [2 H] [45; 1 H [├О'; 45.5 [├О': 1H pmgr_pports_need_up_request:
Show workaround-nic-82566dm
Workaround NIC-82566dm: Enabled
Slot 1
CRASHLogfileshow
Slot a:
-------
... Crash Log File Header ..........................
Product: HP CARD68
Name: HP Switch card id: 68
Date: Aug 12 2015 10:02:51
Build: 300
Version: K.15.18.0006
Directory: / ws / swbuildm / rel_quebec_qaoff / code / buil
CPU: arm11
SerialNum: SG1287R30T
Crash rec size = 1384
Crash rec index = 0
Boot type = POWER ON
WillBootType = UNKNOWN BOOT
..................................................
I hope that with this information can help me with the diagnosis, as I said, no configuration can be done on the switch, for example when creating, delete or assign a vlan to a port, the machine restarts unexpectedly.
Here is a summary of the log
Check the status of the fans and power supplies and they are OK
Thanks!!!
show logging -a -s -d
Keys: W=Warning I=Information
M=Major D=Debug E=Error
---- Event Log listing: All Events Recorded ----
[45;1H[2K[45;1H[1;45r[45;1HI 12/12/16 20:48:20 00061 system: -----------------------------------------
I 12/12/16 20:48:20 00062 system: Mgmt Module 1 went down without saving crash
information
M 12/12/16 20:48:20 03001 system: System reboot due to Power Failure
D 12/12/16 20:48:21 00080 dhcp: entity enabled
D 12/12/16 20:48:22 00138 tftp: TFTP daemon enabled
D 12/12/16 20:48:22 00410 SNTP: Client enabled
W 12/12/16 20:48:43 00274 chassis: Slot A PoE controller 4 selftest failure.
W 12/12/16 20:48:43 00274 chassis: Slot A PoE controller 5 selftest failure.
W 12/12/16 20:48:43 00274 chassis: Slot A PoE controller 6 selftest failure.
W 12/12/16 20:48:56 00566 ports: port C2 PD Denied power due to insufficient
power allocation.
W 12/12/16 20:48:56 00564 ports: port D1 PD Invalid Signature indication.
W 12/12/16 20:48:56 00566 ports: port C3 PD Denied power due to insufficient
power allocation.
W 01/03/17 06:53:05 00564 ports: port C18 PD Invalid Signature indication.
W 01/03/17 06:54:51 00564 ports: port C18 PD Invalid Signature indication.
W 01/03/17 18:19:30 00071 chassis: Power Supply failure: Supply: 2, Failures: 1
E 01/03/17 18:19:31 02703 OSPF: ADJCHG: Neighbor with Router ID 10.252.124.33 on
vlan-500 moved to Down state - adjacency lost.
W 01/03/17 18:19:32 00576 chassis: 50V Power Supply 2 is Faulted. Failures: 1
W 01/03/17 18:19:42 00071 chassis: Power Supply OK: Supply: 2, Failures: 1
W 01/03/17 18:19:42 00576 chassis: 50V Power Supply 2 is OK. Failures: 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2017 12:54 PM
тАО01-11-2017 12:54 PM
Re: Unexpected Reboot 5406zl
I reiterate what I already wrote above...update your switch!
The bug you are experiencing was recognized and fixed (HP provided a practical workaround too) since the software version release K.15.18.0007 (November 2015):
Active system went down: 09/10/15 12:55:32 K.15.18.0006 349
Health Monitor: Invalid Instr Misaligned Mem Access HW Addr=0x00000000 IP=0x0 Task='mSnmpCtrl' Task ID=0xa995840 sp:0x4206ea8 lr:0x86400 msr:0x02029200
xer: 0x00000000 cr: 0x24000400
I'm not an HPE Employee
