This post is more than 5 years old
7 Posts
0
696
June 17th, 2009 02:00
Windows Host agents failing
Hi,
I am currently rolling out the ECC Master and Host agents to all of our Windows hosts.
Out for 180 hosts deployed I have had problems with 10 of them, from checking the MNR logs I can see they all of them are getting the same error that relates to the HBA's.
The host agent will start but then fails to do the doscover and goes offline.
In the mnragent_FATAL.LOG we see the following errors:
Fault address: 6C6F52D1 01:000042D1 C:\WINDOWS\system32\HBAAPI.DLL
Thread 2036 (failed thread):
Logical addr Function
0001:000042D1 (HBAAPI.DLL) HBA_SendCTPassThruV2
0001:00005277 (HBAAPI.DLL) HBA_SendCTPassThru
Also in the discovery MNR logs the last entries before it fails are:
MGG_WIDESKY 10:35:30 C P T 408 (14.89 MB) [discoverAdaptersAndPorts] => Starting a new discovery
MGG_WIDESKY 10:35:30 C P T 408 (14.89 MB) [[API-Call]] => Issuing SymExtHostHbaGet()
MGG_WIDESKY 10:35:30 C P T 408 (14.89 MB 4.000000K) [[API-Call]] => Path of hbaFileName is:
MGG_WIDESKY 10:35:30 C P T 408 (14.89 MB) [[API-Call]] => D:\ECC\exec\MNR610\\HBA_FILE
SDK 10:35:30 SDK 1 P E 408 (67.18 MB 53540.000000K) swrx_exceptionhandler::UnhandledExceptionFilter => F
- atal exception occured on this thread. Process is now terminating. Refer to file
- 'D:\ECC\exec\MNR610\mnragent_FATAL.LOG'
Has anyone seen this before?
Thanks
Adam
I am currently rolling out the ECC Master and Host agents to all of our Windows hosts.
Out for 180 hosts deployed I have had problems with 10 of them, from checking the MNR logs I can see they all of them are getting the same error that relates to the HBA's.
The host agent will start but then fails to do the doscover and goes offline.
In the mnragent_FATAL.LOG we see the following errors:
Fault address: 6C6F52D1 01:000042D1 C:\WINDOWS\system32\HBAAPI.DLL
Thread 2036 (failed thread):
Logical addr Function
0001:000042D1 (HBAAPI.DLL) HBA_SendCTPassThruV2
0001:00005277 (HBAAPI.DLL) HBA_SendCTPassThru
Also in the discovery MNR logs the last entries before it fails are:
MGG_WIDESKY 10:35:30 C P T 408 (14.89 MB) [discoverAdaptersAndPorts] => Starting a new discovery
MGG_WIDESKY 10:35:30 C P T 408 (14.89 MB) [[API-Call]] => Issuing SymExtHostHbaGet()
MGG_WIDESKY 10:35:30 C P T 408 (14.89 MB 4.000000K) [[API-Call]] => Path of hbaFileName is:
MGG_WIDESKY 10:35:30 C P T 408 (14.89 MB) [[API-Call]] => D:\ECC\exec\MNR610\\HBA_FILE
SDK 10:35:30 SDK 1 P E 408 (67.18 MB 53540.000000K) swrx_exceptionhandler::UnhandledExceptionFilter => F
- atal exception occured on this thread. Process is now terminating. Refer to file
- 'D:\ECC\exec\MNR610\mnragent_FATAL.LOG'
Has anyone seen this before?
Thanks
Adam
No Events found!
Allen Ward
4 Operator
•
2.1K Posts
0
June 19th, 2009 08:00
For a default install you would look in C:\ecc\exec\MNR610. If you installed to a different drive or location you would have to check there.
Once you are there you will see several different log types. I usually sort my directory view by date modified to easily pick pu the most recently updated files. You should see the MNR.log and MNR_err.log near the top. Depending on what you are experiencing you may also see SDK_FATAL_ERROR.txt. If you see this, check it first. If not, check the error log.
If you are having trouble with the Master agent you can also check the equivalent files in the MGA610 folder.
Please note that the MGA and MNR part of the folder names are specific to Windows and the 610 part is specific to CC 6.1. If you are running 6.0 you would look for MNR600. If you have upgraded to CC 6.1 from previous versions you will likely see the old folders still in the same directory so be careful to pick the right version.
Allen Ward
4 Operator
•
2.1K Posts
0
June 17th, 2009 08:00
Have you confirmed your HBA driver levels (and firmware levels) against the compatibility matrix?
Adamgr81
7 Posts
0
June 19th, 2009 06:00
I initially ruled drivers out becuase it had worked fine on a majoriety of the servers that have exactly teh same HBA model driver and F/W as the failed ones.
However I tested today on a failed host and upgraded the drivers to 5.5.31.0 which has fixed the problem.
Thanks for your help
Adam
dstarm
1 Rookie
•
124 Posts
0
June 19th, 2009 07:00
Allen Ward
4 Operator
•
2.1K Posts
0
June 19th, 2009 09:00
The MGA is valid for Master Agents on all platforms. It's only the MNR that is Windows specific. For a host agent on AIX for example it would be MAR.
In the older versions of CC (e.g. 5.2) the Master Agents had different acronyms for different platforms.
dstarm
1 Rookie
•
124 Posts
0
June 19th, 2009 09:00
Allen Ward
4 Operator
•
2.1K Posts
0
June 19th, 2009 10:00
It's been a loooooong week!