Brocade Communications Systems BR-1020 Instrukcja Naprawy Pobierz pdf (Strona 31)

Brsocade Adapters Troubleshooting Guide 13

53-1001253-01

General HBA and CNA problems

5. If HCM is still unable to connect to the HCM agent after using the preceding steps, collect the

following data and send to your Support representative for analysis:

• Data collected from the previous step in SupportSaveController.do.

• Data from the HCM application SupportSave feature. Select Tools > SupportSave to

generate a supportsave file. The data file name and location displays when the

SupportSave feature runs.

• Adapter agent files on the adapter host (where the HCM agent is installed). Collect these

files using the following command:

tar cvfz hbaagentfiles.tgz /opt/hbaagent

Output collects to hbaagentfiles.tgz.

• Data collected on the adapter host from the bfa_supportsave feature using the following

command:

bfa_supportsave

Output collects to a file and location specified when the SupportSave feature runs.

Action: For Windows systems, perform the following steps on to help isolate the problem:

1. Verify that the agent is running by executing the appropriate status command for your

operating system described in the Brocade Adapters Installation and Reference Manual. Refer

to the section on modifying HCM agent operation.

2. If you receive a message that the hcmagent is stopped, restarting the agent should resolve the

problem. To restart, use the appropriate start command for your operating system which is also

described in the Brocade Adapters Installation and Reference Manual.

Note that one command described in the manual restarts the agent, but the agent will not

restart if the system reboots or the agent stops unexpectedly. Another command restarts the

agent, but the agent will restart if the system reboots.

3. If the HCM agent starts, verify which TCP port the agent is listening on by executing the

following command at the Windows command prompt:

netstat -nao | findstr 34568

Output similar to the following should display.

TCP 0.0.0.0:34568 0.0.0.0:0 LISTENING 1960

The value 1960 in the last column is the process identifier for the Windows process listening

on the TCP port. Note that this identifier may be different on your system.

4. Enter the following command to confirm that the process identifier bound to TCP port 34568 is

for the hcmagent.exe process:

tasklist /svc | findstr 1960

The following should display if the identifier from step 3 is bound to TCP port 34568:

hcmagent.exe 1960 hcmagent

5. If you are managing a Windows 2008 host system through HCM from a remote system, the

host’s firewall may be blocking TCP/IP port 34568.

Use Windows Firewall and Advanced Service (WFAS) to open port 34568.

1 2 ... 26 27 28 29 30 31 32 33 34 35 36 ... 109 110

Brak uwag

Brocade Communications Systems BR-1020 Instrukcja Naprawy Strona 31