Filter
Top Products
204
Software Fixes in Release K.11.12 - K.13.49
Release K.13.46
J9143B – ProCurve 1000-BX-U SFP-LC Mini-GBIC
For more information, see “Release K.13.45 Enhancements” on page 144.
■ Transceivers (PR_0000010525) — Intermittent self test failure may occur if transceivers
are hot-swapped in and out of the switch in too short a time frame. Note that even with this
fix, transceivers should always be allowed to initialize fully prior to removal and subsequent
re-insertion.
Best Practice Tip: Upon hot insertion of a transceiver, the Mode LED will come on for two
seconds while the transceiver is initialized. Once the Mode LED has extinguished, it is safe to
remove the transceiver.
■ Selftest Failure (PR_0000010937) — Rarely, the switch may experience self test failure
of all the modules. Messages like the following will be visible in the event log. Re-seating the
modules may allow successful self-test to occur.
W <date/time stamp> 00374 chassis: Slot # Failed to
boot-timeout-(SELFTEST)
Release K.13.46
The following problems were resolved in release K.13.46. (Never released.)
■ sFlow (PR_0000003723) — The switch uses the loopback as the sFlow agent address, even
after explicit configuration of the VLAN IP address and the collector receiving the sFlow
packets.
■ SCP/SFTP (PR_0000009174) — Failure to upload a configuration via SFTP/SCP may
occur. As a result, it is possible that the switch may become unresponsive or crash with a
message similar to the following.
Software exception at cfg_edit.cc:313 – in ‘swinitTask’, task ID =
0xa9bbcc0
■ SCP (PR_0000011488) — The switch does not return the scp/sftp session after new
software is uploaded.
■ CLI (PR_0000009997) — The CLI response to the boot set-default flash <primary | secondary>
configuration setting is inconsistent between the zl (5400zl/8212zl) and yl (3500yl/6200yl)
switches, potentially causing issues for customers running scripts.
■ Password Encryption (PR_0000011828) — The Password Manager portion of the
Include Credentials feature is using SHA-0 Instead of SHA-1 for creation of the hash value.
In order to accommodate customers that have worked around this issue, this fix will translate
the configuration and correctly report the use of SHA-0 in the config after a software update
containing this fix.
Example line from password encryption config prior to the fix: