Installation guide

47
Software Fixes in Releases Y.11.01 - Y.11.16
Release Y.11.14
TLB Miss: Virtual Addr=0x00000000 IP=0x800ab0f8 Task='mSnmpCtrl'
Task ID=0x85d26d00 fp:0x00000000 sp:0x85d26a60 ra:0x800aadc8
sr:0x1000fc01
■ Crash (PR_0000044286) — When the switch is configured as a stack member, it will reboot
continuously when the following configuration options are applied.
• A default gateway is configured on the stack member
• An IP address is configured on VLAN 1 of the stack member
• The stack member adds a new SNMP community name (in addition to "public"), with
manager MIB view
• The stack commander adds the same new community name, with manager MIB view
• The stack commander adds a trap receiver for community name "public"
The switch will log a crash message similar to the following.
SubSystem 0 went down: 01/01/90 00:00:47
TLB Miss: Virtual Addr=0x00000009 IP=0x800bd660 Task='mSnmpEvt'
Task ID=0x81e040d0 fp:0x00000000 sp:0x81e03f18 ra:0x800bd5d0
sr:0x1000fc01
■ SSH (PR_0000041757) — If the switch is configured for SSH with an Operator username
but no Operator password (e.g. password operator user-name <username>), users are not able
to log into the switch. The switch requires a password but no password is configured, so
there is no way to log in.
■ SSH (PR_0000041760) — If the switch is configured for SSH with a username that includes
a colon (:), users are not able to log into the switch.
■ STP (PR_0000041155) — When spanning tree is disabled, the switch floods spanning tree
BPDUs received on a port that is tagged for VLAN 1.
Release Y.11.14
The following problems were resolved in build Y.11.14. (Never Released.)
■ CLI (PR_0000044704) — The switch does not properly adjust terminal size display, if the
user telnets to the switch and then changes the terminal size. This can cause the username
to display when the password is requested, instead of a blank field.
■ SSH (PR_0000045801) — If an Operator username is configured without an Operator
password, and a Manager username and password are not configured, then a user who logs
in with the Operator username will get Manager access. Best practice tip: Always set the
Manager username and password first, before setting an Operator username and password,
to ensure that a Manager password is required for Manager access.