HP StorageWorks Fabric Manager 5.x Administrator Guide (AA-RUQSF-TE, September 2005)

ManualsBrandsHP ManualsStorageB-series Embedded Switches

231

232

233

234

235

236

237

238

239

240

Fabric Manager 5.x administrator guide 235

• Fabric Manager server running under Windows or Solaris when using switch-based authentication:

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

• Fabric Manager server running under Solaris when using NIS authentication:

<attribute name="DomainName">yourdomain.com</attribute>

<attribute name="NISServer">"your_NISServer"</attribute>

• Fabric Manager server running under Solaris when using local password authentication:

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

XML file. 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

For example:

Client access to switches

If the client cannot access some of the switches, check the IP connectivity between the client/server, the

client/switch, and the server/switch; then check the web server on the switch by launching Advanced Web

Tools on that switch.

Client-side CPU usage

If the client-side CPU usage is too heavy and has an unusually sluggish or slow response, check the

recommended configuration.

Capturing and reporting client-side issues

For all problems with Fabric Manager, follow these steps:

1. For Windows: Generate fmsupportshow output by selecting Start Menu > Programs > Fabric

Manager > Utilities > Capture FM Support Information.

A command window opens (see Figure 164 on page 233) and runs the fmsupportshow.bat file.

For Solaris: Run the following script to capture the problem:

<installdir>/bin/fmsupportshow.sh

Scripts are located in the $FM_HOME/bin directory. See Figure 165 on page 234 for an example of

the fmsupportshow utility output for Solaris.

2. Obtain a screenshot of the client (if reporting a GUI problem)

3. Include any fabric and switch activities: firmware downloads, reboots, segmentation, merge, and the

like.

4. Include any actions executed from Fabric Manager.

2004-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]

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

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

[stsun] using [brocade] domain

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

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

failed for [brocade/stsun]