- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: SANsurfer unable to connect to Hostname
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2006 09:29 PM
07-24-2006 09:29 PM
SANsurfer unable to connect to Hostname
I've a problem with SANsurfer on RHEL4 64 bits.
When I try connecting on localhost, I've a message "unable to connect to hostname xxxx" and the qlremote process crashes.
I tried with several SANsurfer packages (hp_sansurfer-2.00.30b78-1.x86_64.rpm & sansurfer-2.00.30b66-1.x86_64.rpm from HP, sansurfer2.0.30b69_linux_install_amd64.bin.gz from Qlogic)
Any ideas ?
Thanks a lot.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2006 07:06 PM
08-27-2006 07:06 PM
Re: SANsurfer unable to connect to Hostname
I've upgraded the kernel files, (and kernel sources), on my linux box, SuSE 9.3, and cannot get SANSurfer to connect to the HBA anymore. (FCA 2214DC.)
It seems like the agent won't start and that's why SANSurfer isn't able to connect. If I try to start the service manually:
# /usr/local/bin/qlremote
Debug: Configuration Path (/etc/)...
QLogic Management Suite
Remote Agent for Linux
Version 1.00.1279-27
Copyright 1999 - 2005 QLogic Corporation
All rights reserved.
Debug: OSS initialized...
Debug: Core initialized...
Debug: RPC initialized...
Debug: CorePollingLoop() starting...
Error: **NO** compatible HBAs found during scan - Terminating...
I don't know if this is the same problem as for you but I'll let you know about the progress for me.
/JB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2007 12:10 AM
06-21-2007 12:10 AM
Re: SANsurfer unable to connect to Hostname
I just installed
sansurfer-2.00.30b66-1.ia64.rpm from HP
And am getting similar error where I can't connect to local host and qlremote crashes error NO compatible HBA's
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2008 05:58 AM
10-17-2008 05:58 AM
Re: SANsurfer unable to connect to Hostname
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2008 10:49 PM
10-19-2008 10:49 PM
Re: SANsurfer unable to connect to Hostname
I (once again?) removed the present SanSurfer package and then reinstalled it. I don't remember the HP release but it included SanSurfer 5.0.1b31-1. Guess what? It worked...
/JB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2009 06:47 AM
02-11-2009 06:47 AM
Re: SANsurfer unable to connect to Hostname
I started getting the same problem and attempted re-install etc. with no joy.
Eventually re-seating the HBA seemed to fix it this time.