<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><meta name="Generator" content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal">I previously reported that a Cisco, given the mandatory brocade-privlvl (which it doesn’t understand), will simply default to disable. This assertion appears to be incorrect. On some devices/versions it puts you in disable, in some it puts you in enable, and on some it flat out denies access telling you authorization failed. Serves me right, expecting consistency when Heasley flat out warned me not to! Brocades new method of using optional av pairs will serve them better - one has to wonder if Cisco makes it work incorrect on purpose. </p>
<p class="MsoNormal"> </p><p class="MsoNormal">Feb 21 21:30:32.346: AAA/AUTHOR (0x12B): Pick method list 'default' - FAIL</p><p class="MsoNormal">Feb 21 21:30:32.390: AAA/AUTHOR/EXEC(0000012B): Authorization FAILED</p>
</div></body></html>
<pre>E-Mail to and from me, in connection with the transaction
of public business, is subject to the Wyoming Public Records
Act and may be disclosed to third parties.