TMS zl Module Release Notes ST.1.0.090213

Known Issues

Release ST.1.0.090213

■ PR_0000015081 — When using the Web browser interface for the software update feature,

the Latest Status field is not automatically refreshed. Refreshing the browser displays the

Latest Status correctly but also clears the download form. Although no longer needed by the

TMS zl Module to perform the software update, the clearing of the download form removes

some information from view.

■ PR_0000015153 — When using the TMS zl Module CLI, two commands provide an insert-at

<position> extended option: access-policy and nat. There is no error checking on the position

number provided - it is assumed that a policy or rule exists at that location. For example,

when using insert-at 1 there must be at least one policy or rule available. There must be a

valid policy or rule at the position number for whatever number is specified. If one does not

exist, an error is reported, but the zone information is not included in the error message.

■ PR_0000015448 — In the TMS zl Module CLI, when the attempt is made to modify the protocol

or port number in a connection-settings command, the CLI displays the following message:

Success: Updated connection timeout: <custom name>, but when the show

connection-settings timeout command is issued, the protocol or the port number wasn't

changed.

Example:

1. Configure at least one custom connection-settings timeout

ProCurve Switch (tms-module-D:config)# connection-settings timeout new-ftp tcp

550 10001

2. Update the running Custom Timeout with a different protocol and a different port number

ProCurve Switch (tms-module-D:config)#connection-settings timeout new-ftp udp

8 0 0

10001

3. Review the message displayed in the CLI:

Success: Updated connection timeout: new-ftp

4. Run the command

ProCurve Switch (tms-module-D:config)# show connection-settings timeout

The protocol and the port number of the custom connection timeout should be updated, but they

are not.

■ PR_0000015462 — The VLAN name is not checked for special characters. If a VLAN name

is created with special characters, when the VLAN name is displayed in the Web browser

interface, problems can occur in the display of the VLAN name. The workaround is to use

alphanumeric VLAN names, avoiding spaces and characters such as: @, #, $, ^, &, *, (, and ).

To include a blank space in a VLAN name, enclose the name in single or double quotes (‘...’

or “...”).