Brocade Fabric Manager Administrator's Guide v6.1.0 (53-10000610-02, June 2008)

ManualsBrandsHP ManualsStorageHP DC04 SAN Director Switch

371

372

373

374

375

376

377

378

379

380

350 Fabric Manager Administrator’s Guide

53-10000610-02

Client issues

• Fabric Manager server running under Solaris or Linux when using local password

authentication:

• Fabric Manager server running under Windows, Solaris, or Linux when using RADIUS

authentication:

<attribute name="LoginModule">RADIUS</attribute>

<attribute name="RADIUSServerIP">yourRADIUSserver</attribute>

<attribute name="RADIUSServerPort">RADIUSportnumbers</attribute>

<attribute name="SharedSecret">your_sharedsecret</attribute>

NOTE

If you are using the local password authentication, the DomainName attribute is missing from

the XML file. Also, if you are using the NIS authentication, there is an extra parameter in the

XML file called NISServer.

3. Check the Fabric Manager server log for any errors:

<installdir>/server/server/fmserver/log/server.log

Example

2006-05-27 17:11:19,256 INFO

[com.brocade.fabman.auth.server.FMAuthRemoteServer] Creating New Login

Session: user = [stsun], client host = [192.168.42.139], session id= [2]

2006-05-27 17:11:19,272 INFO

[com.brocade.fabman.auth.server.WinNTLoginModule] Authenticating user [stsun]

using [brocade] domain

2006-05-27 17:11:20,272 ERROR

[com.brocade.fabman.auth.server.WinNTLoginModule] Authentication failed for

[brocade/stsun]

Account lockout

For switches running Fabric OS v5.1.x or later, if the Fabric Manager server is using switch-based

authentication while the password policies are enabled on the switch and the lockout threshold is

set, then unsuccessful Fabric Manager client login attempts might lock out the switch password.

The error message given is:

No indication is given that the switch password is locked out.

Changed authentication method

If you change the authentication method from Windows domain to either RADIUS or switch-based

authentication, and then revert back to Windows domain authentication, subsequent Fabric

Manager client logins fail with “java.lang.UnsatisfiedLinkError” or

“java.lang.NoClassDefFoundError.”

This happens only on Windows installations, when the Windows domain authentication method is

the authentication method when the server starts up. If the RADIUS, NIS, local password,

switch-based, or any other authentication method is in effect when the server starts up, there is no

restriction on switching the authentication type.