Director 4.x Release Notes

Known Issues and Limitations

Version: SG-ME 4.2.2.1 build 26501
Release Date: 07/24/2006
Revision: 1.00 on 07/24/2006

Known Issues

• Management Console:


• Non ASCII characters: The Management Console does not support non ASCII character sets. Entering any such character using any text editor results in a crash of the CLI. (B#45386a)


• Font display: Certain fonts are not displayed properly in the Management Console. This occurs because Director GUI uses JRE 1.4.1_07, which does not have support for these fonts. (B#56199a)


• International SGME versions: Only the English version of SGME is supported for use with the Management Console. (B#56218a)


• Memory: Memory constraint issues might occur on the PC running the Director Management Console while refreshing the domain. This is generally caused if there is a large amount of user activity as the domain view size approaches the upper limit (500). (B#49010)


• Hardware Errors: If you see error messages similar to the following:

(syslog) Oct 7 18:37:49 <kern.crit> director kern: wd0f: aborted command, interface CRC error reading fsbn 457216 of 457216-457343 (wd0 bn 6463888; cn 6412 tn 9 sn 25), retrying

(syslog) Oct 7 18:37:49 <kern.crit> director kern: wd0: soft error (corrected)

Consider upgrading the Director hardware. Older systems use IDE drives. PCI, IDE, and DMA drives are unreliable with many combinations of hardware.

• Overlays: Overlays have a version number, indicating the release in which the overlays were created. Before you use an SGOS 2.x or SGOS 3.x overlay with SGOS 4.x systems, change the overlay type with the command:

Director (config remote-config overlay overlay_name# type SG3 | SG4)

where type specifies whether the overlay is SGOS 3.x or SGOS 4.x. If you don't make a choice, the defaults are to SGOS 3.x for a Proxy SG Appliance running 3.x, and SGOS 4.x if you upgrade from SGOS 3.2.4. (Note that SGOS 2.x is not supported with this version of Director.)

No error checking is done by the type option, so changing the type can result in an SGOS 4.x overlay that does not work on SG4.x boxes or cannot be viewed through the Director Management Console. (B#45831, B#46076)


• VPM, using SGOS 3.1.x: When VPM is started in view-only mode, you can add policy layers through the policy menu; however, you cannot install the policy in view mode. (B#49291)


• CLI: If the configuration daemon goes down, the CLI session might not allow a privileged user to acquire a configuration lock. The workaround is to close the CLI session and open a new session. (B#48933a)


• Inline commands: If the data portion of an inline command has the config prompt (such as "mc-16#(config)"), then the Director and the Proxy SG will have problems in communicating. (B#47018a)


• Domains: If you reconnect to a domain using SSH RSA and then inadvertently provide invalid credentials (if, for example, you changed properties on the wrong domain), a subsequent refresh will succeed. If you close and re-launch the Director Management Console, the connection fails because of the invalid credentials. To correct this problem, select the domain properties and provide the valid credentials. (B#49518)


• SNMP: SNMP does not return a valid sysObjectID value for 800-1 platforms running Director. (B#56858)


• Configuration: If the configuration daemon goes down, the CLI session might not allow a privileged user to write the configuration to a new file. To workaround this problem, close the CLI session and open a new session. (B#56971)


• Profiles:


• Virtual IP Addresses and Failover Settings: You should make sure Virtual IP addresses and Failover settings are not used on the reference ProxySG Appliance used for pulling profiles. The system might crash. (B#49571)


• Bridging: Bridge configuration settings should not be set on the reference ProxySG used for pulling profiles. (B#49225)


• Bandwidth-Class Settings: If a profile was created using a a build prior to build 22688 (SGOS 4.x builds only) and included bandwidth-class settings in the access log, the profile should not be pushed to a system running SGOS 4.x with a build number 22688 or greater.(B#50408)

Limitations

• The following command can only be executed by the user logged into the administrator account:
  director (config) # archive generate key testname show
  If another account attempts to execute this command, even if it has the appropriate privileges, the command fails and the following error message is displayed:
  director (config) # archive generate key test2 show
% Error while generating key "test2"


• If the logging is set to notice_minor, the username and the remote host address are logged in the syslog along with the CLI command being executed by the user. If logging is set to the default notice setting, the username and remote host address are not logged in the syslog.


• You can distribute up to 10,000 URLs to 500 ProxySG Appliances. If you are distributing more than 200 URLs, use the urls-from command instead of adding each URL individually.


• The timeout for configuration management commands might not be long enough in some cases, particularly when commands are executed on large groups or the entire domain. In some multibox configuration instances, the timeout should be increased. (B#45223a)


• Director Management Console: Only the Policy Summary view has visual reference to a specific ProxySG or its absence. However, all advanced configuration files use this functionality, including those managed through the CLI. Thus, when a record of the ProxySG is removed, you should do a complete query on all advanced configuration files through the CLI and manually change any reference to a deleted device. (B#44773a).


• Windows XP collapses similar icons together into a single entry, meaning that the collapsed Director icon displays a rocket with the label "(3) Launch Anywhere GUI". (B#44668a)


• Overlays should contain no more than 500 commands. (B#44540a)


• The Jobs Summary pane might not display the status of some jobs or some jobs might appear to be running indefinitely if Director cannot obtain data from ProxySGs referenced in the jobs. (B#45419a)


• When using the QVE menu and creating IM alert settings, do not enter carriage returns. Only text entered before the carriage return is saved.(B#49959a)