How to Enable Debugging for vhba/vn Agent Issues

Asset ID:	1-71-1517121.1
Update Date:	2017-07-11
Keywords:

Solution Type Technical Instruction Sure

Solution 1517121.1 : How to Enable Debugging for vhba/vn Agent Issues

Applies to:

Oracle Fabric Interconnect F1-15 - Version All Versions and later
Oracle Fabric Interconnect F1-4 - Version All Versions and later
Information in this document applies to any platform.

Goal

Learn how to enable debugging for vn2 or vhbaagent if either of these processes is consuming excessive CPU or memory or these agents are not responding.

Fix

1. From the admin prompt type:

admin#show tech-support

2. Scroll down to the process field:

3. See on which IOcard (slot) the vn2 or the vhba agent is using more CPU or memory or if these agents are not
responding. Before restarting the agent or resetting the IOcard itself,

4. Execute the following commands to collect more information in the logs.

Setting the agent on:

admin#set diagnostics iop <iop slot number> agent-dbg on

5. Perform the rescan on the director for that vhba having issues (i.e. not coming up, staying down even after resetting that vhba or not seeing the Targets or LUN's)

admin#set vhba <vhba> rescan

6. Setting the agent off:

admin#set diag iop <iop slot number> agent-dbg off

Restart the agent or reset the IOcard if necessary now.

Attachments

This solution has no attachment