Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!ub!boulder!daemon
From: BILLW@mathom.cisco.com (WilliamChops Westfield)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: Feature/bug in password handling
Message-ID: <25990@boulder.Colorado.EDU>
Date: 11 Sep 90 00:27:50 GMT
Sender: daemon@boulder.Colorado.EDU
Lines: 19


    A minor related complaint is that the "enable-password" command doesn't
    need to be entered as a complete name.  "enable" is sufficient.  I got
    caught by this when enabling CLNS via the terminal configuration and
    transposed "clns enable" to "enable clns".  It took a while to figure out
    what I did.  It makes for great fun trying to figure out what happened when
    you can't become enabled and the new password was written to NVRAM.

You can always delete a fogotten enabled or line-zero password by installing
the "debug" jumper on the CPU card.  This causes the system to come up in
diagnostic mode, which doens't read the NVM.  Then you can erase the NVM
and start over.

In 8.2, "enable" is a command distinct from "enable-password", so entering
"enable clns" won't cause this problem any more.

Bill Westfield
csico Systems.
-------