I use 'J9643A HP 5412 ZL SWITCH WITH PREMIUM SOFTWARE' as main switch.
Normaly I use 28 vlans. Today I log into switch (ssh). Using menu interface I added new 8 vlans.
(New vlan id numbers 301 to 308. Previous 26 vlans use id numbers lower than 301, and last two use vlan id =999, 1000.)
Then I wanted to assign this new vlans to interfaces and went to (2. Switch Configuration... --> 7. VLAN Menu... --> 3. VLAN Port Assignment) and noticed lack of last two vlan's (id=999, 1000). I figured out that is because some limit in "menu" tool, so I decided to remove two or three of newly created vlans. I went to (2. Switch Configuration... --> 7. VLAN Menu... --> 2. VLAN Names ) select 301 vlan and choose [Delete] option.
This caused switch freeze and crash/reboot (at least I'm convinced that it freezes and it took long, long ~120seconds before start of reboot process.)
My switch has: Version: K.15.02.0005
After 'show tech' (attachment) and SwitchRelease Notes study I'm convinced such incidents was resolved since Version K.15.04.0002:
* Crash (PR_0000055261)—In some situations the switch might reboot unexpectedly with a message similar to the following.
SubSystem 0 went down: 06/22/10 09:24:00
NMI event SW:IP=0x00e953d8 MSR:0x02029200 LR:0x00eb25c8
cr: 0x24000400 sp:0x02e30aa8 xer:0x20000000
Task='InetServer' Task ID=0xaad5000
I post, because maybe some find that information useful, but I also have some questions:
Is lack of some vlan's in menu interface (in 2. Switch Configuration... --> 7. VLAN Menu... --> 3. VLAN Port Assignment) that I described bug ? (Do anyone manage more than 28 vlans with menu interface?)
[... In some situations the switch might ...] what are these 'some situations' from Release Notes, and is it possible that my vlan changes in menu interface and reboot was unrelated?
Will command "no vlan ..." cause _exactly_ the same behavior as 'menu' tool? ( I would like prevent any reboots ).
Do vlans id=301 ... 308 are somehow reserved ?
What is Task='InetServer' responsible for ? (Is it responsible for www interface, so disabling www access might be temporary fix?)
Is there reason not to update to the newest (K.15.06.0006) as a long term solution?
#K.15.02.0005#PR_0000055261#InetServer#Crash