[tac_plus] Brocade Fabric OS

Daniel Schmidt daniel.schmidt at wyo.gov
Mon Nov 6 20:43:12 UTC 2017


I finally got it, after spending more time than I would like to admit.
HomeLF needs to be 128, because I don't understand what it is yet.
brcd-role can be optional.  brcd-AV-Pair1 and 2 do not appear to work as
optional.

        service = exec {
         brcd-role = admin
         brcd-AV-Pair1 = "homeLF=128;LFRoleList=admin:
1,3,4;securityAdmin:5,6"
         brcd-AV-Pair2 = "chassisRole=admin"
        }

Commas in an av pair.  The one delimiter that I thought I could count on
never being in an av pair.  When I get time, I will write a fix for
do_auth.  Also, I finally implemented netaddr to support / notation.  Not
sure if anybody besides me uses it anymore though,

On Mon, Nov 6, 2017 at 12:49 PM, Daniel Schmidt <daniel.schmidt at wyo.gov>
wrote:

> brcd-role will work with optional, but I can't seem to get ChassisRole to
> work either way.  Then again, I don't understand FabricOS at all - maybe I
> need to create a chassis first or something.  Thanks though.
>
> On Mon, Nov 6, 2017 at 12:20 PM, heasley <heas at shrubbery.net> wrote:
>
>> Mon, Nov 06, 2017 at 11:40:03AM -0700, Daniel Schmidt:
>> > A long shot, but......
>> >
>> > brcd-role seems to work find for exec in Fabric OS.  I get a role no
>> > problem.  I need a Chassis Role.  The example is not at all right:
>> >
>> > http://www.brocade.com/content/html/en/administration-guide/
>> fos-740-admin/GUID-7A0B5B7E-8FDD-4E78-80FC-2B13A2ED767A.html
>> >
>> > I've tried it six ways to Sunday, as shell, exec... can't get it to
>> work.
>> >
>>
>> perhaps set them to optional?  i've seen implementations that
>> differentiate;
>> clearly they should not, but ...
>>
>
>

-- 

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.shrubbery.net/pipermail/tac_plus/attachments/20171106/65ce6f4d/attachment.html>


More information about the tac_plus mailing list