EasyManua.ls Logo

HP ProCurve 3500yl - Page 202

HP ProCurve 3500yl
219 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
191
Software Fixes in Release K.11.12 - K.13.49
Release K.13.12
802.1X (PR_0000002036) — 802.1X with Funk Steel Belted RADIUS server causes the
switch to fail to assign the VLAN that it was sent with the "Tunnel-Private-Group-Id"
parameter.
Module Selftest (PR 0000001273) — After a reboot, ports 1-24 or ports 25-48 on the
ProCurve 3500yl, or ports 1-24 on the 6200yl switches, may become unresponsive followed
by green and amber port LEDs remaining lit. The ports recover automatically. The log file
will show the following messages.
chassis: Ports 1-24: Slave ROM Tombstone: 0x13000601
chassis: Ports 1-24: Lost Communications detected - Heart Beat
Lost(4A)
chassis: Ports 1-24 Downloading
chassis: Ports 1-24 Download Complete
chassis: Ports 1-24 Ready
SNMP (PR_1000772026) — The wrong OID is set for a redundant power supply (RPS)
failure.
CLI (PR_0000002177) — When a ProCurve switch yl 10-GbE module (J8694A) is inserted
into a 3500yl or 6200yl switch, the switch may prompt, "Do you want to save the config?,"
even when no changes to the config have been made.
Loopback Interface (PR_0000002165) — A ping or Telnet session to a loopback address
may fail intermittently. A traceroute to the loopback address completes successfully. This
may cause some protocol packets to fail to reach the loopback address.
CLI (PR_1000745509) — Output from the CLI command show ipv6 neighbors vlan <x> is
not displaying the correct age, and it may erroneously display the State Age as "stale" after
a recent learn.
ICMP (PR_1000764033) — ICMP TTL expired messages are being sent with a source
address of the interface from which the message is sent rather than the from the interface
that receives the expired packet.
Web (PR_1000761014) — The Web interface truncates 16 character passwords to 15
characters.
MIB (PR_1000770084) — Several OIDs in MIB violate RFC 2737 and RFC 4133. The
affected OIDs are:
.iso.org.dod.internet.mgmt.mib-2.entityMIB.entityMIBObjects.entityPhysic
al.entPhysicalTable.entPhysicalEntry.entPhysicalHardwareRev
.iso.org.dod.internet.mgmt.mib-
2.entityMIB.entityMIBObjects.entityPhysical.entPhysicalTable.entPhys
calEntry.entPhysicalFirmwareRev

Table of Contents

Related product manuals