Although we believe that the reported incidents were probably caused by
user error, such errors are easy to make. All LocalDirector customers should
check to see that their enable passwords are being enforced properly. Use the
enable command to enter privileged mode, and give an
invalid password. If the invalid password is not accepted, you are not
If the invalid password is accepted, make sure you have an enable
password set, using the write terminal command. If
your enable password appears as a string of zeroes followed by the word
"encrypted", then you have no enable password set. If you have a password set,
or if you are absolutely sure that you had a password that had been set and
saved to the nonvolatile configuration, but that password has now disappeared
without any intervention on your part, please contact Cisco Systems immediately
via e-mail to "firstname.lastname@example.org."
In the unlikely event that there actually is a software error, that
error probably affects all 1.6.x versions of the LocalDirector software.
However, version 1.6.3 is the only 1.6.x version that has been released to
Cisco's general customer base, and Cisco discourages the use of other 1.6.x
versions because of possible software instability.
Because the LocalDirector code is almost entirely separate from the
code used in other Cisco products, it is nearly impossible that any product
other than the LocalDirector is affected by any software error, although of
course user errors can happen with any product. Classic \cisco IOS, as used on
Cisco routers, shares absolutely no password or configuration management code
with the LocalDirector, and is therefore definitely not
affected. WAN-BU and WBU products, including Catalyst switches and FastPacket
switches, are likewise definitely not affected.
No other Cisco products are currently known to be affected by these