TMS zl Module Release Notes ST.1.0.090213

Known Issues

Release ST.1.0.090213

For example:

ProCurve Switch(tms-module-D:config)# vlan 20 ip

address Set IP parameters for communication within an IP network.

igmp Enable IGMP on the VLAN.

pim-sparse Enable PIM-SM on the device.

ProCurve Switch(tms-module-D:config)# vlan 20

ProCurve Switch(tms-module-D:vlan-20)# ip

address Set IP parameters for communication within an IP network.

igmp Enable IGMP on the VLAN.

rip Configure RIP on the VLAN.

ospf Configure OSPF settings.

pim-sparse Enables PIM-SM on the VLAN.

The impact to the user is that some commands cannot be typed in a single line and the VLAN

configuration context must be entered in order to configure some items.

■ PR_0000003186 — From the CLI, the schedule command does not auto-complete when the

Tab key is pressed as other commands from the command line do.

For example, the following command will not auto-complete to daily when the Tab key is pressed

after only dail is typed:

ProCurve Switch(tms-module-D:config)#schedule time1 dail

The impact to the user is that the entire parameter must be typed out.

■ PR_0000004155 — The two internal Ethernet ports of the TMS zl Module have an actual

speed of 10Gbps. However, in the SNMP MIB, they are reported as 10Mbps. This issue only

affects the reporting of the speed via SNMP. The actual speed is 10Gbps.

■ PR_0000004266 — There is a discrepancy between the Web browser interface and the CLI

in regards to how the subnet mask is specified in a static route configuration. The CLI requires

the subnet mask to be specified in dotted decimal format while the Web browser interface

uses CIDR addresses. No functionality is impacted.

■ PR_0000004577 — When the CLI command show logging local is used with paging disabled,

extra blank lines are seen. These blank lines should be ignored.

■ PR_0000004766 — When there are multiple syslog servers on the same IP address, differing

by facility or port, the user is unable to delete the specific entry in question because only the

syslog IP address is used for removing a syslog server. Having more than one syslog server

with the same IP address, the syslog server removed will be the first to appear on the list.

Example:

1. Add a syslog server

ProCurve Switch(tms-module-D:config)# logging syslog 192.168.1.59 513 facility

local0