Dell Brocade 825 Brocade Adapters Troubleshooting Guide - Page 70

HCM and HCM Agent problems, Failed to connect to agent on host... error when using HCM

Get Dell Brocade 825 PDF manuals and user guides View all Dell Brocade 825 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 70 highlights

2 HCM and HCM Agent problems Action: Check FCoE switch configuration using the appropriate Fabric OS command on the attached switch. Refer to the Fabric OS Command Reference Manual for information. Change configuration as necessary using appropriate Fabric OS command on the attached switch. Refer to the Fabric OS Command Reference Manual for information. 3. Possible Cause: The front-end Ethernet port on the FCoE switch is not configured as "switchport" or is not set to converged mode. Action: Use the appropriate Fabric OS command on the attached switch to display information about the VLAN interface. Refer to the Fabric OS Command Reference Manual for information. Action: Configure the FCoE port as a "switchport" using the appropriate Fabric OS command on the attached switch. Refer to the Fabric OS Command Reference Manual for information. Action: Configure the FCoE port to converged mode using the appropriate Fabric OS command on the attached switch. HCM and HCM Agent problems This section provides information to help resolve problems with HCM installation and operation. Failed to connect to agent on host... error when using HCM An "Adapter failed to connect to agent on host..." message indicates that the client application cannot connect to the HCM agent listening on the configured port (normally TCP port 34568). Refer to the following descriptions of possible causes and recommended actions to help resolve the problem. 1. Possible Cause: If the hcmagent process exited in VMware ESX 3.5 or 4.x, the HCM Agent may be configured to forward events to a remote Syslog host, but the outgoing UDP port 514 is blocked by the ESX firewall. Action: Perform the following steps. a. Run the following command to open port 514. esxcfg-firewall -o 514,udp,out,syslog b. Start the agent using the following command. hcmagentservice start 2. Other Possible Causes: • The HCM Agent is not running. • The HCM Agent is not accepting connections on the expected port. • The HCM Agent is not listening on the expected port. • Communication between the client and agent is blocked by a firewall preventing access to the port (usually only a consideration for remote HCM management). 46 Brocade Adapters Troubleshooting Guide 53-1002145-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
46
Brocade Adapters Troubleshooting Guide
53-1002145-01
HCM and HCM Agent problems
2
Action:
Check FCoE switch configuration using the appropriate Fabric OS command on the
attached switch. Refer to the
Fabric OS Command Reference Manual
for information. Change
configuration as necessary using appropriate Fabric OS command on the attached switch.
Refer to the
Fabric OS Command Reference Manual
for information.
3.
Possible Cause:
The front-end Ethernet port on the FCoE switch is not configured as
“switchport” or is not set to converged mode.
Action:
Use the appropriate Fabric OS command on the attached switch to display information
about the VLAN interface. Refer to the
Fabric OS Command Reference Manual
for information.
Action:
Configure the FCoE port as a “switchport” using the appropriate Fabric OS command on
the attached switch. Refer to the
Fabric OS Command Reference Manual
for information.
Action:
Configure the FCoE port to converged mode using the appropriate Fabric OS command
on the attached switch.
HCM and HCM Agent problems
This section provides information to help resolve problems with HCM installation and operation.
Failed to connect to agent on host... error when using HCM
An “Adapter failed to connect to agent on host...” message indicates that the client application
cannot connect to the HCM agent listening on the configured port (normally TCP port 34568). Refer
to the following descriptions of possible causes and recommended actions to help resolve the
problem.
1.
Possible Cause:
If the hcmagent process exited in VMware ESX 3.5 or 4.x, the HCM Agent may
be configured to forward events to a remote Syslog host, but the outgoing UDP port 514 is
blocked by the ESX firewall.
Action:
Perform the following steps.
a.
Run the following command to open port 514.
esxcfg-firewall -o 514,udp,out,syslog
b.
Start the agent using the following command.
hcmagentservice start
2.
Other Possible Causes:
•
The HCM Agent is not running.
•
The HCM Agent is not accepting connections on the expected port.
•
The HCM Agent is not listening on the expected port.
•
Communication between the client and agent is blocked by a firewall preventing access to
the port (usually only a consideration for remote HCM management).