Filter
Top Products
56 Brocade SMI Agent User’s Guide
53-1001778-01
Troubleshooting
5
Troubleshooting
• How do I prevent the SMI Agent process from getting terminated on Solaris when I start the
agent in a Bourne shell and then log out?
• If the Brocade SMI Agent hangs, how do I capture the thread dump?
• Why is there no change in the status of a non-proxy Brocade_Switch when a LAN cable from
the non-proxy switch is unplugged?
• What does the error message "Host Message: Duplicate connection to fabric ...." mean?
How do I prevent the SMI Agent process from getting terminated on Solaris when I start the agent
in a Bourne shell and then log out?
When you starts the agent in a Bourne shell (/bin/sh), the process dies upon user session logout.
To prevent this, start the SMI Agent using the following command:
/usr/bin/nohup start_server
Note that in the C shell, background jobs are by default immune to being killed by a shell exit.
If the Brocade SMI Agent hangs, how do I capture the thread dump?
On Linux: Type the following command:
kill -3 pid
where pid is the process ID of the Brocade SMI Agent.
On Solaris: Press CTRL key + backslash (\) key.
On Windows: Press CTRL key + BREAK key.
Why is there no change in the status of a non-proxy Brocade_Switch when a LAN cable from the
non-proxy switch is unplugged?
Communication from proxy to target switches is in-band. So even if the LAN cable from a non-proxy
switch is unplugged, the agent can still talk to that target switch via the fibre connecting this proxy
switch and the non-proxy switch.
The Brocade SMI Agent does not send out any alerts for this.
What does the error message "Host Message: Duplicate connection to fabric ...." mean?
This is an informative error message that occurs when the provider.xml file is configured with IP
addresses of different switches in the same fabric. The Brocade SMI Agent tries to connect to each
entry in the provider.xml file. If a connection to the fabric already exists, then this message occurs.
Only one switch entry per fabric is sufficient in the provider.xml file.